Spokane's Transit Navigation System Routed a Double-Decker Into a Bridge It Couldn't Clear
What happened
A double-decker bus operated by Spokane Transit Authority struck a low-clearance railroad viaduct on Cedar Street in Spokane, Washington in January 2026, shearing off the upper deck. Ten people were on board; seven were hospitalized with non-life-threatening injuries. The bus had not run into a malfunctioning structure. It ran into a bridge that was simply too low for a vehicle of that height, and no system had flagged the problem before the bus reached it.
The onboard navigation and CAD mapping system was reportedly what directed the route. CAD systems in transit operations are built for dispatch coordination and fleet tracking, not for computing whether a specific street segment is physically traversable by a specific vehicle type. That distinction matters here because a standard-height bus and a double-decker do not share the same set of valid routes. A clearance that passes for one vehicle fails for the other, and the system apparently made no distinction.
What the record reveals is a mismatch between what the system was trusted to do and what it was actually capable of doing. The navigation system gave a route. Nothing in the workflow between that output and the bus leaving its stop required anyone, or any downstream check, to confirm that the route was appropriate for the specific vehicle assigned to it. Operators treated the CAD map as authoritative for routing. STA's own response after the crash confirmed it should not have been used that way.
The agency moved quickly. It warned operators to stop using CAD maps for routing decisions and pulled double-deckers from service pending an investigation. The driver was cited for negligent driving. That citation places formal accountability on the person who followed the system's direction rather than on the process that gave the system routing authority it was not designed to carry. Both things can be true at once: the driver could have refused the route, and the system should never have been the one suggesting it.
The documentation gap here is specific. There is no indication that the system logged what vehicle profile was active when the route was generated, what clearance constraints it checked, or whether it was capable of checking them at all. A provable record of what a system did at the moment a routing decision was made, and what constraints it was asked to verify, would make the failure legible rather than just blame-assignable. Without that record, the same mismatch can recur any time a vehicle with unusual dimensions is dispatched on a route a general-purpose mapping tool produced without knowing what it was routing.
Reported impact
- Affected parties
- Not publicly disclosed
- Harm type
- Not publicly disclosed
- Scale
- Not publicly disclosed
- Financial impact
- Not publicly disclosed
- Regulatory action
- Not publicly disclosed
Classification
Relevant governance controls
Governance control mapping is not available for this record.
- No controls mapped
Not publicly disclosed
Control mapping is analytical. It does not state that any control would have prevented the incident.
Sources and evidence
This record was researched and written by the Index. The event is also catalogued in the following database, which is listed for cross-reference.