Final NTSB investigations
29 cases where the defining event was Air traffic event.
Cases per year
| 2008 | 1 |
|---|---|
| 2009 | 3 |
| 2010 | 6 |
| 2011 | 5 |
| 2012 | 2 |
| 2013 | 1 |
| 2014 | 1 |
| 2016 | 2 |
| 2017 | 3 |
| 2018 | 1 |
| 2021 | 1 |
| 2023 | 3 |
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 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."completionStatus" = 'Completed' AND 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 OPS24LA004IncidentClass 4 · LimitedFinal reportAirbus A321-271N · Long Beach, CAThe local controller’s poor judgment in prioritization of their ground traffic ahead of their airborne traffic, that became a distraction and led to a loss of situational awareness resulting in a near midair collision. Contributing to the incident was the…NTSB OPS23FA010IncidentClass 4 · FieldFinal reportBoeing 737-7BD · San Diego, CAThe local control controller’s poor judgment in duty prioritization which distracted them from monitoring arriving and departing traffic and resulted in a runway incursion and loss of same runway separation. Contributing was the operations supervisor’s…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 OPS21LA002Incident · No injuriesClass 3 · LimitedFinal reportAirbus A319-112 · St Petersburg-Clearwater, FLThe air traffic controller’s failure to properly scan the runway and local area, and their general loss of situational awareness, resulting in a near midair collision. Contributing to the incident was the Cessna 337 pilot's poor decision making when he failed…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 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 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 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 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 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 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 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…