["https:\/\/schema.org\/",[{"@type":"BlogPosting","@id":"https:\/\/www.attorneysofidaho.com\/blog\/meridian-dangerous-intersections\/#article","mainEntityOfPage":{"@id":"https:\/\/www.attorneysofidaho.com\/blog\/meridian-dangerous-intersections\/"},"headline":"Meridian Dangerous Intersections: What Official Data Shows","name":"Meridian Dangerous Intersections: What Official Data Shows","description":"See seven Meridian intersections in the latest official severe-crash analysis, the 2018\u20132022 counts, methodology limits, and current project context.","datePublished":"2026-01-29T18:41:26+00:00","dateModified":"2026-09-03T09:16:01+00:00","author":{"@type":"Organization","name":"Attorneys of Idaho","url":"https:\/\/www.attorneysofidaho.com\/about-us\/"},"publisher":{"@type":"Organization","name":"Attorneys of Idaho","logo":{"@type":"ImageObject","@id":"https:\/\/www.attorneysofidaho.com\/wp-content\/uploads\/2025\/07\/logo-footer.svg","url":"https:\/\/www.attorneysofidaho.com\/wp-content\/uploads\/2025\/07\/logo-footer.svg","width":0,"height":0}},"image":"https:\/\/www.attorneysofidaho.com\/wp-content\/uploads\/2026\/01\/Most-Dangerous-Intersections-for-Car-Accidents-in-Meridian.jpg","url":"https:\/\/www.attorneysofidaho.com\/blog\/meridian-dangerous-intersections\/","about":["Car Accidents"],"wordCount":1402,"articleBody":"Current official data can identify Meridian intersections with high counts of fatal or serious-injury crashes, but it cannot prove one junction is the city\u2019s \u201cmost dangerous.\u201d COMPASS\u2019s 2018\u20132022 Appendix D lists seven Meridian intersections with three to five such crashes and gives Meridian Road\/Amity Road five. The same memo\u2019s Table 4 says six for that location without explaining the difference. This guide uses Appendix D for its consistent row-level table, discloses both figures, and explains the method, limits, and current project context.Meridian intersections in one consistent official datasetThe COMPASS Regional Safety Action Plan was accepted in February 2025. Its High Injury Network analysis joined five calendar years of crash records to a modeled regional road and junction network. The table below includes every row classified as \u201cMeridian\u201d in Appendix D\u2019s high-K\/A intersection table. It excludes Meridian Road and Lake Hazel Road because COMPASS classifies that row as Ada County rather than Meridian.Why five appears in the table below: Technical Memorandum 4\u2019s Table 4, \u201cLocation-Specific Strategies\u2014Top 10 Locations,\u201d reports six K\/A crashes for Meridian Road\/Amity Road. Appendix D\u2019s dedicated intersection row reports five. The memo connects both tables to the same High Injury Network screening but gives no separate crash window, junction boundary, manual adjustment, or location note that reconciles the one-crash difference. Appendix D expressly documents an assumed reassignment at Idaho Center Boulevard\/Franklin Road, but provides no comparable explanation here. The source is therefore internally inconsistent. The current public COMPASS junction layer independently reports five at the Meridian\/Amity point\u2014zero fatal and five serious-injury crashes\u2014but does not explain Table 4\u2019s six. We retain Appendix D\u2019s five for the consistent row-level comparison and annualized calculation, preserve Table 4\u2019s six as an unresolved alternate figure, and do not add or average the two values.Meridian intersections in the COMPASS high-K\/A table, 2018\u20132022Five-year count groupIntersectionMajor-road ownerAnnualized historical count5Meridian Road (SH-69) \/ Amity RoadITD1.0 per year4Eagle Road \/ Overland RoadITD0.8 per year4Locust Grove Road \/ Overland RoadACHD0.8 per year4Ten Mile Road \/ Cherry LaneACHD0.8 per year3Fairview Avenue \/ Locust Grove RoadACHD0.6 per year3Meridian Road \/ Pine AvenueACHD0.6 per year3Meridian Road (SH-69) \/ Victory RoadITD0.6 per yearMeasure: Each displayed count is Appendix D\u2019s sum of crashes classified as fatal (K) or serious injury (A) during 2018\u20132022. The annualized column divides that five-year Appendix D count by five. It is a historical time average, not a traffic-exposure or accident-probability rate. Table 4\u2019s unreconciled six for Meridian\/Amity is disclosed but not used in the calculation. Ties are alphabetical; they are not broken with an unrelated score.How COMPASS assigned and selected the intersection crashesThe junction area is 150 feet, not an unlimited corridorCOMPASS treated a crash within 150 feet of a modeled junction as junction-related and assigned it exclusively to that junction. Other crashes went to the nearest segment. The network analysis focused on collectors and higher road classes, excluding local roads, interstates, and ramps. Regionwide, 148 fatal or serious-injury crashes were not joined because they were on local roads or outside the buffered features; 13 may have been poorly geocoded.The numerator is clear; a verified traffic denominator is notThe numerator is the K\/A crash count. The time denominator for the annualized figure is five years. The published intersection rows do not provide a verified vehicle, trip, annual-average-daily-traffic, or vehicle-mile denominator. The methodology\u2019s data dictionary expressly labels its crash-rate fields as not quality-controlled or verified. This article therefore groups intersections by the published count and does not say that one driver is more likely to crash at one listed junction than another.The High Injury Network score is not a crash rateThe plan also combines a normalized historical location score with a systemic risk score based on correlated roadway features. COMPASS weights those components equally and includes scores more than one standard deviation above the network. That model helps agencies screen locations; it does not establish causation, predict an individual crash, or decide civil responsibility. City-to-city counts and population rates belong in our separate Idaho car-accident statistics study.What current plans and maintenance notices do\u2014and do not\u2014showProject activity is not proof that a location remains dangerous or has become safe. It should be tracked separately from the historical crash table.Official Meridian-area project context checked September 2, 2026Official itemCurrent source statementImportant limitCherry Lane, Ten Mile Road to NW 8th StreetACHD\u2019s August 20, 2026 update lists the pavement-maintenance segment as complete.The project page does not describe a Ten Mile\/Cherry intersection redesign or publish post-project crash results.Major signalized arterial intersectionsCOMPASS recommends a package that may include protected left-turn phasing, leading pedestrian intervals, accessible pedestrian signals, restrictions on right turns on red, bike boxes, raised islands, or removal of channelized right turns.The strategy memorandum is a planning recommendation, not evidence that a specific item is funded, designed, approved, or built.Meridian Intersection and Pedestrian Safety Task ForceThe 2023 city task-force report says more than 140 sites were reviewed through crash data, field observations, lighting review, public feedback, and detailed intersection audits.The task force focused on people walking, bicycling, and using other non-vehicle modes. Its audit should not be merged with the later COMPASS K\/A count table as though the methods were identical.Roadway responsibility is shared among agencies. Check current construction notices with the owning agency identified in the data table instead of assuming a past plan is current.A severe-crash table cannot determine fault in a Meridian collisionHistorical location data does not show what a signal displayed, who had the right of way, whether visibility was obstructed, or how each road user acted in a particular crash. Those issues require case-specific evidence. Our guide to fault determinations after an Idaho car accident explains why a citation or police report is relevant but not a civil judgment.Call 911 when someone may be injured or traffic conditions make the scene unsafe.If it is safe, photograph the signals, signs, lane markings, vehicle positions, sight lines, debris, and temporary traffic controls.Record the exact intersection, travel direction, lane, date, and time.Save dash-camera files and identify nearby traffic, business, or doorbell video before routine deletion.Request the record from the correct agency; our Meridian accident-report guide explains the agency distinctions.If you were injured and want help assessing the evidence, our Idaho car-accident attorneys can explain the process. No table can promise a finding of fault or a case outcome. You may request a consultation when you are ready.Methodology and update schedulePrimary crash source: Idaho crash records analyzed by COMPASS for 2018\u20132022.Geography: Every high-K\/A Appendix D junction row labeled \u201cMeridian\u201d; source roadway owner labels are preserved.Selection: Count groups, descending; tied intersections shown alphabetically. This is not a census of all Meridian junctions.Calculation: Appendix D K\/A count divided by five for annualized historical context. No unverified traffic-exposure rate is republished.Source-consistency rule: Appendix D supplies every row-level comparison. Table 4\u2019s six-crash Meridian\/Amity figure is retained separately as unresolved; it is not merged with Appendix D\u2019s five.Last data check: September 2, 2026.Review owner: Attorneys of Idaho content operations.Next scheduled check: June 30, 2027, or earlier if COMPASS or ITD publishes a replacement High Injury Network dataset.Download the Attorneys of Idaho companion files: Meridian 2018\u20132022 severe-crash comparison CSV, Meridian current-project context CSV, and Meridian research methodology CSV. These Attorneys of Idaho research companions organize information from the cited sources; they are not official agency datasets or raw crash records.Sources and Legal ReferencesCOMPASS, Regional Safety Action Plan (current plan page; accepted February 2025; page updated May 4, 2026).COMPASS Technical Memorandum 3: Existing Conditions (October 8, 2024; 2018\u20132022 data, methods, exclusions, and definitions).COMPASS Technical Memorandum 4: Strategy Development (September 16, 2024; Table 4 reports six K\/A crashes at Meridian\/Amity, while Appendix D reports five and provides no reconciliation; also supports the intersection dataset and jurisdiction strategies).COMPASS, Final RSAP Junctions for Dashboard (current public junction layer; the Meridian\/Amity point reports five K\/A crashes: zero fatal and five serious injury; service metadata last edited June 3, 2025).City of Meridian, Intersection and Pedestrian Safety Task Force Report (2023).Ada County Highway District, 2026 Large Patch Program (updated August 20, 2026).Last reviewed and updated: September 2, 2026.This article provides general information, not legal advice. Crash histories and project plans can change, and a location-level statistic does not establish fault in an individual case.","isPartOf":{"@id":"https:\/\/www.attorneysofidaho.com\/blog\/meridian-dangerous-intersections\/"},"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.attorneysofidaho.com\/blog\/meridian-dangerous-intersections\/","url":"https:\/\/www.attorneysofidaho.com\/blog\/meridian-dangerous-intersections\/","mainEntity":{"@id":"https:\/\/www.attorneysofidaho.com\/blog\/meridian-dangerous-intersections\/#article"},"reviewedBy":{"@type":"Person","name":"J.W. Bond","url":"https:\/\/www.attorneysofidaho.com\/attorneys\/j-w-bond\/","jobTitle":"Founding Attorney and Partner"},"lastReviewed":"2026-09-02"}],{"@context":"https:\/\/schema.org\/","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Blog","item":"https:\/\/www.attorneysofidaho.com\/blog\/#breadcrumbitem"},{"@type":"ListItem","position":2,"name":"Meridian Dangerous Intersections: What Official Data Shows","item":"https:\/\/www.attorneysofidaho.com\/blog\/meridian-dangerous-intersections\/#breadcrumbitem"}]}]