Final NTSB investigations
59 cases where the sequence of events included 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.\"completionStatus\" = 'Completed'
AND c.\"mKey\" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '100' 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" = '100' 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 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 ERA09CA234Accident · No injuriesData collectionFinal reportCessna 172RG · Charleston, SCThe pilot's failure to extend the landing gear before landing. Contributing to the accident was the diversion of the pilot's attention to an airplane on a converging final approach course.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 CEN09LA095Accident · No injuriesLimited investigationFinal reportCessna 402 · Madison, WIThe pilot’s improper fuel management, which resulted in a loss of engine power during an instrument landing due to fuel exhaustion.NTSB CEN09LA039Accident · Minor injuriesLimited investigationFinal reportChamberlin Victor Wayne Minimax · Winnsboro, LAThe pilot’s failure to maintain clearance from static wires while maneuvering to avoid another airplane.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 OPS08IA014Incident · No injuriesIncident investigationFinal reportBoeing B744 · Atlantic OceanThe San Juan CERAP controllers failure to ensure the two aircraft were properly separated using non-radar separation standards.NTSB OPS08IA011Incident · No injuriesIncident investigationFinal reportLearjet 60 · Chicago, ILThe LC-10 controller's failure to ensure the appropriate separation between two airplanes operating on runways where flight paths intersect.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…