NTSB investigations
83 cases where the defining event was Air traffic event.
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\" = '100') 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" = '100') 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 DCA18LA024AccidentClass 3 · LimitedFinal reportBoeing 777 · Jamaica, NYThe air traffic controller's improper instruction to the Egypt Air airplane flight crew to pass in an area where passing is prohibited, which led to a ground collision.NTSB DCA18WA028Incident · No injuriesForeign investigationBoeing 737 · Latvia, LatviaThe Transport Accident and Incident Investigation Bureau of Latvia has notified the NTSB of an incident involving a Boeing 737, which occurred on November 23, 2017. The NTSB has appointed a U.S Accredited Representative to assist under the provisions of ICAO…NTSB OPS17IA021IncidentClass 3 · IncidentFinal reportCessna 172S · New Orleans, LAThe air traffic controller not following Federal Aviation Administration directives to establish sequencing and spacing between aircraft operating to the same runway.NTSB OPS17IA014IncidentClass 3 · IncidentFinal reportEmbraer S A ERJ 170-200 LR · San Francisco, CAThe local controller's issuance of a landing clearance for runway 28L to the ERJ170, and the subsequent issuance of line up and wait instructions to the A320 for runway 28L, resulting in a runway incursion.NTSB OPS17IA010Incident · No injuriesIncident investigationFinal reportBoeing 777 · Mt. Wilson, CAThe incident was caused by the air traffic controller assigning the pilots a left turn instead of the required right turn after departure which placed the aircraft in an unsafe proximity with terrain and obstructions. Contributing to the incident was the air…NTSB DCA16WA188Incident · No injuriesForeign investigationBoeing 737 · Sofia, BulgariaThe Aircraft Accident Investigation Unit (AAIU) of Bulgaria has notified the NTSB of an incident involving a Boeing 737 that occurred on June 04, 2016. The NTSB has appointed a U.S. Accredited Representative to assist the AAIU investigation under the…NTSB OPS16IA010IncidentClass 3 · IncidentFinal reportMooney M20R · Jacksonville, FLThe air traffic controller's decision to issue climb instruction to one aircraft without ensuring the required separation with another could be maintained. Contributing to the incident was the air traffic controller's failure to issue a safety alert in a…NTSB DCA16WA079Incident · No injuriesForeign investigationBoeing 737 · Gran Canaria, SpainThe Comisión de Investigación de Accidentes e Incidentes de Aviación Civil (CIAIAC) of Spain has notified the NTSB of an incident involving a Boeing 737 airplane that occurred on January 07, 2016. The NTSB has appointed a U.S. Accredited Representative to…NTSB DCA16WA034Incident · No injuriesForeign investigationBoeing · Perth, AustraliaThe Australian Transportation Safety Board (ATSB) has notified the NTSB of an incident involving a Boeing 787 that occurred on December 04, 2015. The NTSB has appointed a U.S. Accredited Representative to assist the ATSB's investigation under the provisions…NTSB CEN15WA327Incident · No injuriesForeign investigationRaytheon Corporate Jets BAE 125 800 · Kerry, Ireland, IrelandThe incident investigation is under the jurisdiction and control of the government of Ireland. This report is for information purposes only and contains only information released by or obtained from the government of Ireland. Further information pertaining to…NTSB DCA15WA122Incident · No injuriesForeign investigationAirbus A321 - 211 · Barcelona, SpainThe Comision de Investigacion de Accidentes e Incidentes de Aviacion Civil (CIAIAC) has notified the NTSB of an incident involving an Airbus A321 and a Boeing 737-400 which occurred on April 28, 2015. The NTSB has appointed a U.S. Accredited Representative to…NTSB OPS14IA005Incident · No injuriesIncident investigationFinal reportEmbraer EMB 145XR · Newark, NJThe local controller’s failure to comply with Federal Aviation Administration separation requirements for aircraft operating on intersecting runways.NTSB OPS13IA071Incident · No injuriesIncident investigationFinal reportGulfstream GIV - Undesignat · Las Vegas, NVThe Federal Aviation Administration's (FAA) inadequate procedures, which did not require specific separation between aircraft operating on nonintersecting runways where flightpaths may intersect and led to an airborne conflict between two aircraft.…NTSB DCA13WA070Incident · No injuriesForeign investigationBoeing 737 · Brisbane, AustraliaThe Australian Transportation Safety Board (ATSB) has notified the NTSB of an accident involving a Boeing 737 airplane that occurred on February 25, 2013. The NTSB has appointed a U.S. Accredited Representative to assist the ATSB's investigation under the…NTSB ERA13LA042Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Sevierville, TNThe air traffic controller’s failure to comply with the required vectoring and safety alert procedures, which resulted in the airplane’s flight into rising terrain. Contributing to the accident was the Federal Aviation Administration’s continued practice of…NTSB OPS12IA849Incident · No injuriesIncident investigationFinal reportArlington, VAA hearback/readback error on the part of the tower traffic management coordinator, who did not understand the request being made by the approach control area supervisor and then communicated that misunderstanding to the local controllers. Contributing to the…NTSB OPS12WA430Incident · No injuriesForeign investigationGulfstream Aerospace GV SP (G550) · Ontario, CanadaN217AL, a private Cessna 750, was en route between San Jose, California (KSJC), and Bedford, Massachusetts (KBED) at FL430. N128GV, a private Gulfstream V, was en route between Bradley/Windsor Locks, Connecticut (KBDL), and San Francisco, California (KSFO),…NTSB OPS11IA819Incident · No injuriesIncident investigationFinal reportEmbraer EMB-135KL · Chicago, ILThe improper air traffic control takeoff clearance issued by the local controller because of his lack of monitoring and lack of awareness of the conflicting arrival airplane.NTSB OPS11IA673Incident · No injuriesIncident investigationFinal reportEmbraer EMB-145EP · Gulfport, MSthe Gulfport control tower local controller cleared two aircraft for takeoff from runways with intersecting departure flight paths without ensuring the first aircraft had passed the flight path intersection prior to clearing the second aircraft for takeoff.NTSB OPS11IA552Incident · No injuriesIncident investigationFinal reportEmbraer EMB-145LR · Chicago, ILThe air traffic controller’s failure to adhere to runway separation requirements and his issuance of an improper takeoff clearance. Contributing to the incident was the controller's failure to recall that there was an arrival inbound to a crossing runway.NTSB DCA11WA054Incident · No injuriesForeign investigationBoeing 767 · Fukuoka, JapanThe Japan Transport Safety Board (JTSB) has notified the NTSB of an incident involving a B767-300 and a DHC-8-402 that occurred on May 10, 2011. The NTSB has appointed a U.S. Accredited Representative to assist the JTSB investigation under the provisions of…NTSB OPS11IA401Incident · No injuriesIncident investigationFinal reportArlington, VAThe tower controller's loss of consciousness induced by lack of sleep, fatigue resulting from working successive midnight shifts, and air traffic control scheduling practices.NTSB OPS11IA410Incident · No injuriesIncident investigationFinal reportBoeing 757-232 · Atlanta, GAThe air traffic controllers’ failure to adhere to required radar identification procedures, which resulted in loss of separation between the departing Boeing 757 and three other airplanes. Contributing to the incident was the pilots’ inadequate preflight…NTSB OPS11IA173Incident · No injuriesIncident investigationFinal reportBoeing 737-832 · Covington, KYThe local controller's distraction with a helicopter south of the field.NTSB OPS11IA054Incident · No injuriesIncident investigationFinal reportDassault FALCON900EX · Teterboro, NJThe pilot of the F900 overshooting of the final approach course, which conflicted with traffic in the pattern. Contributing to the accident was the lack of appropriate coordination between the tower controller and the approach controller.NTSB OPS10IA538Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Los Angeles, CAFailure of the air traffic controller to exercise positive control of the situation by issuing clear and timely control instructions to the helicopter pilot. Contributing to the incident was delay by the helicopter pilot in responding to instructions issued…NTSB OPS10IA196Incident · No injuriesIncident investigationFinal reportAirbus Industrie A319-132 · Anchorage, AKThe approach controller's delayed transfer of communications on the A319 to the tower controller and failure to account for the aircraft's speed when he directed the crew to turn north. Contributing to the incident was the 747 crew's transfer of radio…NTSB OPS10IA132Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Houston, TXThe failure of the local controller to issue control instructions necessary to ensure positive control/standard separation of traffic operating within the Class B airspace.NTSB OPS10IA090Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Burbank, CAThe improper separation procedures by air traffic control.NTSB OPS10IA002Incident · No injuriesIncident investigationFinal reportAirbus A320 · Cortez, COThe failure of the ACA795 flight crew to monitor and/or switch to the appropriate air traffic control frequency.NTSB DCA10IA001Incident · No injuriesIncident investigationFinal reportAirbus A320 · Minneapolis, MNThe flight crew's failure to monitor the airplane’s radio and instruments and the progress of the flight after becoming distracted by conversations and activities unrelated to the operation of the flight.NTSB OPS09IA002Incident · No injuriesIncident investigationFinal reportTampa, FLThe controller's issuance of an improper climb clearance to the pilot of Berry Aviation flight 510. Contributing to the incident was the controller's distraction while he searched for a misplaced flight progress strip.NTSB OPS08IA008Incident · No injuriesIncident investigationFinal reportBoeing 737-300 · New York, NYThe probable cause of this incident was JFK air traffic control tower non-compliance with FAA separation requirements for operations on non-intersecting runways where flight paths intersect, and poor judgment by the LC2 controller in clearing LAN533 for…