NTSB investigations, 2010
6 cases where the defining event was Air traffic event.
Cases per year
| 2008 | 1 |
|---|---|
| 2009 | 3 |
| 2010 | 6 |
| 2011 | 6 |
| 2012 | 3 |
| 2013 | 2 |
| 2014 | 1 |
| 2015 | 3 |
| 2016 | 4 |
| 2017 | 4 |
| 2018 | 7 |
| 2019 | 3 |
| 2020 | 2 |
| 2021 | 2 |
| 2022 | 4 |
| 2023 | 7 |
| 2024 | 7 |
| 2025 | 4 |
| 2026 | 14 |
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 year(c.\"eventDate\") = 2010
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 year(c."eventDate") = 2010 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 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.