NTSB investigations
95 cases where the defining event was Runway incursion veh/AC/person.
Cases, newest first
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.\"mKey\" IN (SELECT e.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.\"isDefiningEvent\" AND e.\"tier2Number\" = '320') 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."mKey" IN (SELECT e.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e."isDefiningEvent" AND e."tier2Number" = '320') 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 DCA21WA103IncidentClass 5 · ForeignBoeing 737 · Buenos Aires, ArgentinaNTSB DCA20WA137Incident · No injuriesForeign investigationBoeing 737 · Palma, SpainThe government of Spain has notified the NTSB of an accident involving a Boeing 737 airplane that occurred on July 19, 2020. The NTSB has appointed a U.S. Accredited Representative to assist the government of Spain's investigation under the provisions of ICAO…NTSB DCA19WA174Incident · No injuriesForeign investigationBoeing 737 · Birmingham, United KingdomThe government of United Kingdom has notified the NTSB of an incident involving a BOEING 737 airplane that occurred on June 18, 2019. The NTSB has appointed a U.S. Accredited Representative to assist the government of United Kingdom's investigation under the…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 DCA19WA224Occurrence · No injuriesClass 5 · ForeignBoeing 737 · Hong Kong, ChinaNTSB 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 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 DCA16WA228Incident · No injuriesForeign investigationBoeing 777 · London, United KingdomThe Aircraft Accident Investigation Bureau (AAIB) of India has notified the NTSB of an accident involving a Boeing 777 that occurred on August 30, 2016. The NTSB has appointed a U.S. Accredited Representative to assist the AAIB's investigation under the…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 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 DCA15WA174Incident · No injuriesForeign investigationBombardier CL600 2D24 · Toronto, CanadaThe Transportation Safety Board of Canada (TSB-C) has notified the NTSB of an incident involving a Boeing 787 that occurred on August 03, 2015. The NTSB has appointed a U.S. Accredited Representative to assist the TSB-C's investigation under the provisions of…NTSB CEN15RA446Incident · No injuriesForeign investigationCessna 525 · Geneva, SwitzerlandNTSB 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 DCA15RA045Incident · No injuriesForeign investigationBoeing 757 - 236 · Warsaw, PolandThe State Commission on Aircraft Accident Investigation (SCAAI) of Poland has notified the NTSB of an incident involving a Boeing 757-236 that occurred on December 17, 2014. The NTSB has appointed a U.S. Accredited Representative to assist the SCAAI of…NTSB DCA14WA004Incident · No injuriesForeign investigationBoeing 777-200 · Changi, SingaporeThe Air Accident Investigation Bureau of Singapore has notified the NTSB of an incident involving a Boeing 777-200, 9V-SWG, which occurred on October 3, 2013. The NTSB has appointed a U.S. Accredited Representative to assist the AAIB investigation under the…NTSB DCA13WA109Incident · No injuriesForeign investigationBoeing 737-800 · Thessaloniki, GreeceThe Air Accident Investigation and Aviation Safety Board (AAIASB) of Greece, has notified the NTSB of an incident involving a Boeing 737-800 that occurred on June 15, 2013. The NTSB has appointed a U.S. Accredited Representative to assist the AAIASB…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 DCA12WA105Incident · No injuriesForeign investigationAirbus A319 · Okinawa, JapanOn July 5, 2012, about 1324 Japan Standard Time (0424 UTC), an Airbus A319-112, (B2332), operated by China Eastern Airlines Co., Ltd., was instruction to hold short of the runway at the Naha Airport (OKA), Okinawa, Japan; however, the flight crew taxied onto…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 OPS12WA150Incident · No injuriesForeign investigationEmbraer EMB-145LR · Toronto, CanadaOn November 18, 2011, American Eagle (EGF) flight 4125, an EMB-145, landed on runway 24L at Toronto Lester B. Pearson International Airport (CYYZ) and exited the runway at taxiway D4 with instructions to hold short of runway 24R. EGF4125 subsequently crossed…NTSB DCA11WA117Incident · No injuriesForeign investigationBoeing 737 · Dublin, IrelandThe Ireland Air Accident Investigation Unit (AAIU) has notified the NTSB of an incident involving a B737 and an A321 that occurred on May 21, 2011. The NTSB has appointed a U.S. Accredited Representative to assist the AAIU investigation under the provisions…NTSB CEN11RA295Accident · No injuriesForeign investigationEclipse EA500 · Saanen, SwitzerlandOn March 14, 2011, at 1205 UTC, an Eclipse Aircraft Corporation, EA500, U.S. Registration N177EA, collided with a parked vehicle during landing at Saanen Aerodrome, Bern, Switzerland. The pilot and four passengers were not injured. The airplane was…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 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 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.