Spokane Transit Authority Onboard Navigation System Reportedly Routed Double-Decker Bus to Low Bridge, Injuring Seven

In Spokane, Washington, a Spokane Transit Authority double-decker bus was reportedly routed by its onboard navigation/CAD mapping system onto Cedar Street and hit a low-clearance railroad viaduct, shearing the upper deck. Of 10 people aboard, seven were reportedly hospitalized with non-life-threatening injuries. STA reportedly later warned operators not to use CAD maps for routing and pulled double-deckers from service pending an investigation; the driver was cited for negligent driving.

Risk classification

• Primary risk domain: 7 AI system safety, failures, & limitations
• Primary risk subdomain: 7.3 Lack of capability or robustness

The onboard navigation software failed to perform reliably by routing a double-decker bus onto a street with a low-clearance viaduct that was physically impassable for the vehicle.

Additional risk subdomains

• 5.1 Overreliance and unsafe use: The driver relied on the CAD mapping software for routing instructions despite physical low-clearance warning signs on the road.

Causal factors

• Entity: AI
• Intent: Unintentional
• Timing: Post-deployment

The incident was caused by an incorrect routing decision made by the onboard CAD mapping and navigation software after it was deployed.

EU AI Act risk tier

• Risk tier: 2 High Risk

High Risk: The system is used as a safety component in public transit routing, which falls under critical infrastructure and traffic management.

AI system and alleged parties

• AI system: onboard navigation/CAD mapping system
• AI purpose: Navigation Assistant
• Behaviour type: Assistant
• Alleged developer: Unidentified vendor of Spokane Transit Authority onboard CAD/navigation routing software
• Alleged deployer: Spokane Transit Authority
• Alleged harmed parties: Spokane Transit Authority personnel, Spokane Transit Authority bus passengers

Harm severity

Severity ratings are based on this scale.

Highest direct severity in any category: Minor. Severity is scored from Negligible to Catastrophic in each harm category, for harm the reports describe as caused directly or indirectly by the AI system.

• Physical: direct Minor, indirect Negligible
• Infrastructure: direct Negligible, indirect Negligible
• Property: direct Minor, indirect Negligible
• Financial: direct Minor, indirect Negligible
• Environmental: direct Negligible, indirect Negligible
• Malicious content: direct Negligible, indirect Negligible
• Differential treatment: direct Negligible, indirect Negligible
• Civil rights: direct Negligible, indirect Negligible
• Democracy: direct Negligible, indirect Negligible
• Privacy: direct Negligible, indirect Negligible
• Psychological: direct Negligible, indirect Negligible
• Epistemic: direct Negligible, indirect Negligible
• Child sexual exploitation and abuse: direct Negligible, indirect Negligible

Physical

Reported: The report explicitly describes physical injuries to passengers on the bus.

Directly caused: Seven passengers were hospitalized with non-life-threatening injuries. Specific injuries included a student hit in the face by a falling ceiling panel and another passenger who had a tooth knocked out and a torn lip.

Property

Reported: The report explicitly describes severe damage to the double-decker bus.

Directly caused: The top foot of plexiglass, metal, and plastic composite of the 1.4 million dollar double-decker bus was sheared back and crumpled.

Financial

Reported: The report describes the high cost of the double-decker buses involved in the incident.

Directly caused: The crash caused significant financial damage to a bus valued at 1.4 million dollars, though the exact repair cost is not specified.

Inferred additional harm: The transit agency likely incurred indirect financial losses from pulling the double-decker fleet from service and conducting the investigation.

People affected

• Occurrences reported: 1
• People reportedly harmed: 7
• People reportedly exposed: 10

Potential causes

Management

• Overconfidence in Safety: Mocked clearance risks in ads instead of implementing robust routing checks.
• Delayed Fleet Grounding: Management waited four hours after the crash to pull buses from service.

Technology

• Flawed Onboard Navigation: Software routed a tall double-decker bus onto a low-clearance street.
• Lack of Height Integration: CAD routing system failed to account for the 13.5-foot height of the bus.

Data Inputs

• Incorrect CAD Map Data: CAD maps provided detour routing that was unsafe for double-decker buses.

Human Factors

• Overreliance on GPS: Driver followed software-directed detour instead of observing visual signs.
• Driver Negligence: Operator drove past low-clearance warning signs before hitting the viaduct.

Process and Methods

• Delayed Safety Alerts: Agency took over three hours to warn other drivers about the CAD map issue.
• Service Change Alignment: Detour routing coincided with a thrice-yearly scheduled service change.

Regulatory Environment

• Inadequate Bridge Warnings: Existing physical signs did not deter frequent collisions at this viaduct.

Information quality

• Classification confidence: High
• Reason for confidence: The report provides clear, detailed factual accounts of the crash, the injuries, the vehicle dimensions, and the role of the CAD mapping software. The transit agency's immediate action to suspend the software confirms its central role in the incident.
• Ambiguities identified: The exact technical reason why the CAD software routed the bus onto Cedar Street is not fully detailed, as the investigation was still pending.
• Alternative interpretations: The incident could be viewed purely as driver negligence since they passed a warning sign, but the software's active instruction to detour makes it a clear joint human-AI failure.

A localized public transit accident occurred when an onboard CAD mapping system incorrectly routed a double-decker bus under a low-clearance viaduct, causing seven injuries and property damage. The incident represents a local safety failure with negligible national security implications, as the system was human-controlled and the threat is an established routing issue.

• Overall national security impact: Minor
• Scope: Single nation
• Primary target: United States
• Alleged perpetrator: Unknown

Threat characteristics

• Imminence: Long-term. The immediate safety issue was resolved by suspending the CAD system, presenting only a long-term strategic safety concern for transit AI integration.
• Autonomy: Human-controlled. The CAD mapping system acted as a navigation assistant, but the human driver retained final control and responsibility for operating the vehicle.
• Novelty: Established threat. GPS and navigation software routing errors leading to vehicle collisions are well-documented and represent an established threat type.

Impact by dimension

• Physical security: Minor. The incident involved physical injuries to seven passengers and damage to a municipal transit bus and city infrastructure. However, the impact was strictly localized and easily managed by local authorities, posing no threat to critical national infrastructure.
• Information security: Negligible. There is no indication of information warfare, intelligence compromise, or systematic information manipulation in this incident.
• Sovereignty: Negligible. The incident was a localized municipal transit accident and did not threaten state authority, territorial control, or core government operations.
• Economic security: Negligible. While the accident caused physical damage to a 1.4 million dollar bus and led to temporary fleet suspensions, this economic impact is negligible at the national level.
• Societal stability: Negligible. The incident has no implications for societal stability, civil liberties, or population-scale human rights.