Beta This project is not live yet. We are waiting for our nonprofit status to be approved first. Everything here is a preview and may change.

Documents

Every claim on this site is supposed to trace back to a real source. This page indexes the evidence we host ourselves, not just link to, so the record survives even if ADOT, a news outlet, or anyone else changes or removes the original. Everything here also has full sourcing detail in our internal research log; this page is the public-facing summary.

Last updated 2026-09-13.

Traffic & Engineering Data

Federal fatal-crash data (NHTSA FARS): 19 fatal crashes, 22 deaths on this corridor, 2010 to 2024, with the exact query bounds. ADOT traffic volume (AADT). ADOT’s 2024 widening-feasibility GIS data, with a plain statement of what it does and doesn’t show. Read more →

Crash & Safety Data

ADOT’s statewide Crash Facts 2023 report, hosted here in full, plus the county-level numbers and why the state doesn’t publish route-level detail. Read more →

Prior Studies & Plans

ADOT’s June 2025 freight-corridor report, hosted in full, with the page reference for the Central Arizona Governments statement quoted on our home page. The one formal corridor study that exists nearby (2007, doesn’t reach this stretch), the 2018 ADOT study that covers a different part of SR 77 entirely, confirmation this corridor has never appeared in ADOT’s five-year construction programs, and a 2015 ADOT press release about the related southern widening project that’s no longer on ADOT’s own site. We recovered and archived it. Read more →

News Coverage

Local news coverage of crashes and maintenance work on this corridor, one widely reported crash that is on SR 77 but outside this segment (and why we don’t count it), and a disputed statistic we found circulating and chose not to use. Read more →

Corrections and updates

When we change a claim on this site because we got it wrong or found better information, we say so here rather than editing quietly. Newest first.

  • 2026-09-13: Our home page used to lead with ADOT’s widening-feasibility rating (“ADOT’s own data says this is feasible”). After reading the dataset’s own documentation and checking it statewide, we found the rating measures physical constraints only, not need, and that about 82 percent of rated Arizona segments carry the same “Yes.” It’s now presented as what it is: it rules out an engineering objection, it doesn’t make the case by itself. Details on the Traffic & Engineering Data page.
  • 2026-09-13: A January 2018 crash at milepost 92 was listed as “serious.” The source (KGUN9) reports it as fatal. Corrected.
  • 2026-09-13: An October 2025 crash near Catalina was listed alongside corridor crashes without qualification. It was a red-light collision at a signalized intersection in the already-widened section south of Oracle Junction. It’s now listed separately with that context, and we don’t count it toward this corridor.
  • 2026-09-13: We described a disputed news figure as “contradicted” by federal data. The federal data (through 2024) shows nothing like it in any prior year, but doesn’t yet cover late 2025, so “unverified” is the accurate word. Reworded.
  • 2026-09-13: The History page said ADOT reassigned the SR 77 number in 1938. ADOT didn’t exist until 1974; that was the Arizona Highway Department. Corrected. The same page now reflects that the San Manuel mine’s closure was phased (mining ended 1999, final closure by 2003) rather than a date sources simply disagree on, and notes the 2026 sale of the property for exploration.
  • 2026-09-13: References to “ADOT District 2” updated to ADOT’s current name for the office covering this area, the Southcentral District (Tucson).
  • 2026-09-13: The Get Involved page said the near-miss form was still in development. It’s live.
  • 2026-09-13: The Traffic & Engineering Data page misattributed a web-firewall block on NHTSA’s crash API to “ADOT’s host.” It’s NHTSA’s. It also described the AADT dataset as living in the same feature service as the widening data; it’s a separate service. Both corrected.

Leave a Comment