NTSB CAROL · Event
Event OPS11IA273
Aircraft involved
Probable cause & findings
The driver of the operation vehicle's misidentification of the runway for an adjacent taxiway, resulting in a runway incursion with an aircraft in position for takeoff.
Factual narrative
Air Canada Flight (ACA) number 1072, an Embraer RJ-190 on a scheduled 14 CFR Part 121 flight between DEN and Chicago O'Hare International Airport (ORD), Chicago, Illinois, had been cleared for takeoff from the approach end of runway 34R at DEN. At approximately 1334:40, after releasing the parking brake but prior to beginning takeoff roll, the pilot of ACA1072 observed headlights of a vehicle on runway centerline proceeding toward him on runway 34R. The pilot advised the control tower that a vehicle was on the runway after which the tower canceled ACA1072's takeoff clearance and directed ACA1072 to taxi off of runway 34R at taxiway F2 at approximately 1336:10. The vehicle on runway 34R was OPS6, a DEN Aviation Operations Vehicle operated by the DEN Aviation Operations Manager as the lead vehicle for the snow removal vehicle team. OPS6 had requested and had been authorized by the control tower personnel to proceed southbound on taxiway F in preparation for snow removal operations on runway 34R. Taxiway F parallels runway 34R. The operator of OPS6 misidentifed runway 34R for taxiway F and proceeded onto runway 34R at taxiway WC and traveled south on the runway. Once the tower personnel became aware of a vehicle on the runway, they contacted OPS6 as the lead vehicle of the snow removal team to advise him that a vehicle was on the runway. OPS6 did not initially realize that he was the vehicle on the runway. While coordinating with the tower, OPS6 attempted to visually identify the vehicle on runway 34R before realizing that his vehicle was the vehicle in question. The DEN air traffic control tower (ATCT) was equipped with airport surface detection equipment, model X (ASDE -X). The ASDE-X system was designed to aid in identifying and de-conflicting aircraft and vehicles on the airport to assist in air traffic controller situational awareness, and to prevent runway incursions. According to the DEN ASDE-X playback, OPS6 entered runway 34R at taxiway WC at approximately 1333:40 and proceed down runway 34R while ACA1072 was in takeoff position on the runway. The algorithms of the ASDE-X are set to prevent nuisance alerts for aircraft and/or vehicles traveling less than approximately 40 knots. As OPS6 was not traveling at such speed and ACA1072 was stationary, the ASDE-X did not alarm. Staffing in the DEN ATCT included an instructor controller and a developmental controller on local control (LC) 4 position. The LC4 position was providing ATC services for arrivals and departures on runways 34L and 34R at the time of the incident. According to air traffic controller statements, both the qualified controller and the developmental controller stated that the runway appeared to be clear prior to issuing a takeoff clearance to ACA1072. The developmental controller stated that he scanned the runway and the ASDE-X display in the tower and everything appeared clear. A runway incursion occurred when an aviation operations vehicle, operated as the lead vehicle for a snow removal team, entered an active runway without clearance as the airplane was about to begin its takeoff roll. The airplane's crew noticed the headlights of the vehicle approaching on the runway and did not initiate their takeoff roll. The tower controller was not aware of the vehicle on the runway until advised by the airplane's crew. The airport was equipped with ASDE-X, which did not alert of the runway incursion due to the slow closure rate of the vehicle to the stationary aircraft. Postincident investigation revealed that the driver of the operations vehicle misidentified the runway for an adjacent taxiway. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Airport personnel - C
Verbatim from NTSB's published report. Source file
NTSB_2010_OPS11IA273.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (runway incursion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- SKYbrary (Eurocontrol) 2023 · SKYbrary article
Runway Incursion — SKYbrary Knowledge Base
SKYbrary runway incursion review — taxonomy (operational error, vehicle/pedestrian, pilot deviation), severity categories A-D, mitigation technologies (ASDE-X, ASSC, RAAS, RIAAS).
- Semantic Scholar 2023 · Article (Future Transportation)
Investigating Runway Incursion Incidents at United States Airports
According to the Federal Aviation Administration (FAA), the number of runway incursions is increasing. Over the last two decades, the number of runway incursions at U.S.
- FAA-affiliated R&D (MITRE / Volpe / FAA Tech Center) 2022 · MITRE risk analysis
Runway Incursion Prevention Systems — Surface Domain Risk Analysis
MITRE risk analysis of runway-incursion prevention systems (RIPS) — ASDE-X / ASSC + Airport Surface Detection Equipment performance characterization. Findings drove FAA Surface Safety Action Plan.
- Semantic Scholar 2020 · Article (Journal of Physics: Conference Series)
Comparison of Detection Technology for Runway Incursion Prevention in Airport Hot Spot
The prevention of runway incursion in hot spot of airports has always been one of the research hot spots in the field of international civil aviation.
- Embry-Riddle Scholarly Commons 2020 · Journal article (IJAAA)
Analysis of Runway Incursion Trends: Implications for Cost-Benefit Analysis of Mitigation Investments
This causal-comparative and correlation study investigated the costs of runway incursion safety improvements in relation to their effectiveness to assess potential aviation system benefits.Two airport…
- Semantic Scholar 2020 · Article
Analysis of Runway Incursion Trends: Implications for Cost-Benefit Analysis of Mitigation Investments
Browse the full corpus — academia portal ↗