Final NTSB investigations
49 cases where the sequence of events included Runway incursion veh/AC/person.
Cases per year
| 2008 | 8 |
|---|---|
| 2009 | 7 |
| 2010 | 1 |
| 2011 | 1 |
| 2012 | 3 |
| 2013 | 1 |
| 2015 | 4 |
| 2016 | 7 |
| 2017 | 1 |
| 2018 | 2 |
| 2019 | 1 |
| 2021 | 2 |
| 2023 | 7 |
| 2024 | 3 |
| 2025 | 1 |
Where
Open the mapLatest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"completionStatus\" = 'Completed'
AND c.\"mKey\" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '320' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\"))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1 WHERE c."completionStatus" = 'Completed' AND c."mKey" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '320' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
Run it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB WPR25LA087Accident · No injuriesClass 4 · LimitedFinal reportAmerican Legend AL3 · Upland, CAThe pilot’s failure to maintain adequate separation during landing, which resulted in a runway collision with another airplane.NTSB CEN25LA059Accident · No injuriesClass 3 · LimitedFinal reportCessna 182T · Pearland, TXThe AA-5 pilot’s failure to maintain separation from the 182T during approach and landing, which resulted in a ground collision during the landing roll. Contributing to the accident was the failure of the AA-5’s electrical system, which prevented the AA-5…NTSB CEN24LA256Accident · Minor injuriesClass 4 · LimitedFinal reportGlobe GC-1B · Lone Oak, TXThe pilot having to take evasive action during the takeoff run to avoid another airplane being pushed onto the runway in front of him, which resulted in the airplane overrunning the runway and impacting a fence.NTSB WPR24LA068Accident · No injuriesClass 3 · LimitedFinal reportCessna 421C · Carson City, NVAirport personnel’s failure to properly prioritize their response actions, including updating the airport’s automated weather observation system recording in a timely manner to notify incoming pilots of a runway closure, which resulted in an airplane striking…NTSB DCA24FA017Accident · No injuriesClass 2 · FieldFinal reportTextron 510 · Houston, TXThe takeoff by the flight crew of N269AA, without a takeoff clearance, which resulted in a collision with N510HM that was landing on an intersecting runway. Contributing to the accident was the N269AA crew’s expectation bias and distraction.NTSB DCA23LA192IncidentClass 4 · LimitedFinal reportLearjet 60 · Boston, MAThe Hop-a-Jet flight crew taking off without a takeoff clearance which resulted in a conflict with a JetBlue flight that had been cleared to land on an intersecting runway.NTSB DCA23LA185Incident · No injuriesClass 3 · LimitedFinal reportBombardier CL-600-2D24 · Burbank, CAThe interruption of the local controller’s workflow due to the necessitated management of a go-around of a third airplane that was approaching a different runway. Contributing to the incident was: 1) the controller’s decision to continue the landing of…NTSB DCA23LA179Incident · No injuriesClass 3 · LimitedFinal reportBoeing 737-823 · Sarasota, FLThe local controller’s failure to prioritize and properly monitor the runway and airport environment along with his erroneous assumption that ROU 1633 would depart from runway 14 before AAL2172 arrived to land on the same runway, which resulted in a loss of…NTSB DCA23FA149Incident · No injuriesClass 1 · FieldFinal reportBoeing 737-79P · Austin, TXthe local controller’s incorrect assumption that the Southwest Airlines (SWA) airplane would depart from the runway before the Federal Express airplane arrived on the same runway, which resulted in a loss of separation between both airplanes. Contributing to…NTSB DCA23LA133Incident · No injuriesClass 3 · LimitedFinal reportBoeing 777-222 · Honolulu, HIThe airport’s continued use of taxiway Kilo, despite an identified risk of pilots repeatedly failing to stop at a hold short line prior to two intersecting runways. Contributing were 1) the operator’s moving map display, which omitted a published restriction…NTSB DCA23LA125Incident · No injuriesClass 1 · LimitedFinal reportBoeing 737-900ER · Queens, NYThe American Airlines flight 106 (AAL106) crew’s surface navigation error due to distractions caused by their performance of concurrent operational tasks during taxi, which resulted in a loss of situational awareness. Contributing to the incident was the air…NTSB WPR21LA251Accident · Serious injuriesClass 4 · LimitedFinal reportStinson 108-3 · Stevenson, WAA runway incursion, which resulted in a go-around, and subsequent forced landing when the airplane was not able to climb at a rate sufficient to clear approaching rising terrain.NTSB OPS21LA003Incident · No injuriesClass 3 · LimitedFinal reportBoeing 737-8H4 · San Diego, CAThe blocked go-around radio instruction from the air traffic control tower to the arrival aircraft which resulted in the arrival aircraft continuing the landing approach. This led to a loss of separation between the landing aircraft and the aircraft awaiting…NTSB WPR19FA095Accident · 1 fatalClass 3 · FieldFinal reportNorth American T28 · Compton, CAThe failure of the T-28 pilot to see and avoid the Cessna while landing with reduced visibility due to sun glare, which resulted in a collision on the runway. Contributing to the accident was his failure to use the airport's common traffic advisory frequency…NTSB GAA19CA018Accident · No injuriesData collectionFinal reportPiper PA 16 · Manchester, WVA vehicle's incursion onto an active runway, which resulted in an evasive action by the pilot landing an airplane on that runway and a subsequent runway excursion.NTSB OPS18IA014IncidentClass 3 · IncidentFinal reportEmbraer EMB145 · Springfield, MOThe local controller failing to follow established facility directives and issuing a clearance for takeoff from a runway not under his control.NTSB GAA17CA443Accident · Minor injuriesData collectionFinal reportGrumman Acft ENG Cor-Schweizer G 164B · Berlin, MDThe ground crewman’s failure to visually check the runway before crossing it in a vehicle, which resulted in he and the vehicle being struck by the landing airplane.NTSB OPS17IA008IncidentClass 3 · IncidentFinal reportBombardier CL 600 2B19 · San Francisco, CAThe captain’s inadvertent turn onto the incorrect taxiway and subsequent entry onto an active runway without a clearance, which resulted in the runway incursion.NTSB OPS17IA003IncidentClass 2 · IncidentFinal reportDouglas DC 9 83 · Westfield, MAThe air traffic controller issuing the aircraft a clearance to land while there was a vehicle authorized to be on the same runway. Contributing to the incident was the air traffic controller's decision to not simulcast the local control and ground control…NTSB DCA16IA200Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320 211 · Rapid City, SDThe flight crew's misidentification of the desired landing runway due to excess altitude requiring an extended downwind, and failure to use all available navigation information.NTSB OPS16IA008IncidentClass 3 · IncidentFinal reportEmbraer S A EMB-505 · Dallas, TXThe controller's miscommunication of a clearance and failure to recognize and correct the readback resulting in the flight crew initiating takeoff without a clearance.NTSB OPS16IA009IncidentClass 3 · IncidentFinal reportCessna 172S · Honolulu, HIThe air traffic controller's decision to clear an aircraft to land on a runway occupied by another aircraft that had previously been instructed to line up and wait. Contributing to the runway incursion was the failure of the air traffic controller to visually…NTSB OPS16IA004Incident · No injuriesIncident investigationFinal reportAirbus A321 231 · Fort Lauderdale, FLThe air traffic controller's failure to ensure the runway surface area was clear of vehicles before clearing an aircraft for takeoff. Also causal was the flight crew's decision to initiate a takeoff while the Runway Status Lights (RWSL) Takeoff Hold Lights…NTSB OPS16IA002Incident · No injuriesIncident investigationFinal reportBombardier CL600 2D24 · Detroit, MIThe local controller's failure to visually scan and ensure that the runway surface was not occupied by a vehicle or other aircraft before issuing a takeoff clearance to the pilot. Contributing to this incident was the relieved controller's failure to monitor…NTSB ERA16CA057Accident · No injuriesData collectionFinal reportBoeing A75N1(PT17) · Farmington, DEBoth pilots' failure to maintain visual separation during landing at an uncontrolled airport. Contributing to the accident was the Mooney pilot's lack of prompt evasive action once the biplane had been spotted on the same runway. In addition, the biplane…NTSB GAA15CA262Accident · No injuriesData collectionFinal reportAero Commander 500 B · The Dalles, ORA motor vehicle's runway incursion causing the premature rotation of the departing airplane, which resulted in a tail strike.NTSB OPS15IA017Incident · No injuriesIncident investigationFinal reportBoeing 767 34AF · Miami, FLThe controller's issuance of a landing clearance to an arriving aircraft while another aircraft was in position on the same runway. Contributing to the incident was the controller's non-compliance with traffic advisory procedures, and insufficient…NTSB OPS15IA011Incident · No injuriesIncident investigationFinal reportEmbraer EMB 145LR · Chicago, ILThe flight crew's failure to manage cockpit tasks during taxi resulting in a loss of situation awareness and subsequently taxiing past a required turn point and onto an active runway without clearance. Contributing to the runway incursion was the ground…NTSB WPR13LA223Accident · 1 fatalLimited investigationFinal reportSchweizer G-164B · Biggs, CAThe pilot’s failure to adequately monitor the runway environment during taxi, which resulted in an on-ground collision.NTSB CEN13IA107Incident · No injuriesIncident investigationFinal reportSwearingen SA227-AC · Williston, NDThe snowplow driver’s failure to ensure that the runway was clear before driving onto it, which resulted in a runway incursion with a departing airplane.NTSB ERA13FA059Accident · 3 fatalField investigationFinal reportCessna 172N · Owls Head, METhe vehicle driver's failure to verify that the runway was not occupied by an airplane before crossing the runway, which resulted in the vehicle being struck by a departing airplane, and the pilot's continued takeoff with flight control damage, which…NTSB ANC12CA054Accident · No injuriesData collectionFinal reportCessna 172 · Skwentna, AKThe improper decision of the driver of the all-terrain vehicle to enter an active runway.NTSB OPS12IA167Incident · No injuriesIncident investigationFinal reportLearjet 45 · Chicago, ILThe tower local controller did not ensure that the runway was clear of conflict before directing the B737 to cross the runway, and other air traffic control personnel did not effectively intervene when the separation between the two airplanes became…NTSB OPS11IA273Incident · No injuriesIncident investigationFinal reportEmbraer ERJ190 · Denver, COThe 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.NTSB OPS10IA003Incident · No injuriesIncident investigationFinal reportDetroit, MIThe ground controller did not monitor the progress of the fire truck to ensure that the driver followed the expected route. A contributing factor was the ground controller's misunderstanding of the fire truck driver's requested destination on the airport.NTSB OPS09IA009Incident · No injuriesIncident investigationFinal reportBombardier DHC-8-202 · Cleveland, OHThe local controller did not visually scan the runways and ensure that the E145 had crossed runway 24L prior to issuing a takeoff clearance to the DH8, did not ensure separation between the two airplanes, and did not cancel takeoff clearance for the DH8 in a…NTSB OPS09IA008Incident · No injuriesIncident investigationFinal reportAirbus A320 · Boston, MAThe vehicle operator's failure to follow the designated haul route to the construction site and his failure to adhere to airport driving procedures, which led to missed visual cues and lack of required communication prior to crossing the active runway.…NTSB OPS09IA007Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Cleveland, OHThe ground controller did not issue taxi instructions in accordance with FAA Order 7110.65, paragraph 3-7-2. The local controller did not scan the runways prior to issuing a taxi into position and hold instruction to SWA1080 as required by FAA Order 7110.65…NTSB OPS09IA005Incident · No injuriesIncident investigationFinal reportBombardier CL-600-2B1 · Charlotte, NCThe Charlotte local control east controller's failure to ensure that the runway was clear prior to authorizing N409DR to enter the runway.NTSB OPS09IA004Incident · No injuriesIncident investigationFinal reportBE20 · Camp Springs, MDThe failure of the ground controller to coordinate the runway crossings with the local controller and her failure to scan the runway prior to issuing the crossing instructions. Contributing to the incident was the combination of the front line manager/tower…NTSB CEN09LA265Accident · Serious injuriesLimited investigationFinal reportT Bird T Bird II · Carlock, ILThe pilot's failure to gain sufficient altitude during the takeoff in order to avoid contacting the cameraman. Contributing to the accident was the pilot's lack of experience.NTSB ERA09CA024Accident · Minor injuriesData collectionFinal reportLange Flugzeugbau E1 Antares · Winter Haven, FLThe failure of the pilot of the other airplane to announce his intentions prior to takeoff, resulting in a runway incursion. Contributing to the accident was the limited forward visibility due to the runway slope.NTSB OPS09IA001Incident · No injuriesIncident investigationFinal reportPeoria, ILThe tower local controller's failure to provide adequate separation between EGF4075 and SKW5961 that landed on intersecting runways.NTSB OPS08IA015Incident · No injuriesIncident investigationFinal reportBombardier CL-600-2C1 · Allentown, PAThe failure of both tower controllers to maintain awareness of the position of N736GV and ensure that the aircraft was clear of the runway before issuing a takeoff clearance to ASH7138.NTSB CHI08CA277Accident · No injuriesData collectionFinal reportCessna 150L · Wadsworth, OHThe lack of radio communication with the airplane and the inadequate visual lookout by the driver of the vehicle.NTSB OPS08IA013Incident · No injuriesIncident investigationFinal reportPiper PA-46 · Fresno, CAThe tower controller's failure to ensure the runway was clear before allowing Skywest 69R to land. Factors contributing to the incident were the Malibu pilot's and tower controller's unfamiliarity with the airport layout.NTSB OPS08IA012Incident · No injuriesIncident investigationFinal reportCessna 172 · Reading, PAThe tower local controller permitted an aircraft to conduct a low approach and another aircraft to land on a closed runway. Contributing to the incident were the arrival radar controller who failed to correct the local controller when advised an aircraft…NTSB NYC08FA265Accident · No injuriesField investigationFinal reportCessna 550 · Reading, PAThe air traffic controller’s failure to properly monitor the runway environment. Contributing to the accident was the tractor operator’s failure to scan the active runway prior to crossing, and the Federal Aviation Administration’s inadequate emphasis on…NTSB DFW08LA144Accident · No injuriesLimited investigationFinal reportStinson 108-3 · Roanoke, TXThe departing pilot's inadequate visual lookout resulting in his airplane colliding with the landing airplane. Contributing to the accident was the trees/visual obstructions along the runway's approach path.