NTSB investigations, 2023
10 cases where the sequence of events included Runway incursion veh/AC/person.
Cases per year
| 2008 | 8 |
|---|---|
| 2009 | 7 |
| 2010 | 1 |
| 2011 | 4 |
| 2012 | 4 |
| 2013 | 3 |
| 2014 | 1 |
| 2015 | 6 |
| 2016 | 8 |
| 2017 | 1 |
| 2018 | 3 |
| 2019 | 2 |
| 2020 | 1 |
| 2021 | 5 |
| 2022 | 2 |
| 2023 | 10 |
| 2024 | 13 |
| 2025 | 15 |
| 2026 | 10 |
Where
Latest 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\") = 2023
AND c.\"mKey\" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '320' 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 year(c."eventDate") = 2023 AND c."mKey" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '320' 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 DCA24FA017Accident · No injuriesClass 2 · FieldFinal reportTextron 510 · Houston, TXThe takeoff by the flight crew of N269AA, without a takeoff clearance, which resulted in a collision with N510HM that was landing on an intersecting runway. Contributing to the accident was the N269AA crew’s expectation bias and distraction.NTSB DCA24WA009IncidentClass 5 · ForeignBoeing 737 · Marrakesh, MoroccoNTSB GAA23WA240IncidentClass 4 · ForeignPiper PA-31-350 · North Eleuthera, BahamasNTSB DCA24WA196Incident · No injuriesClass 5 · ForeignBoeing 737 · Osaka, JapanNTSB DCA23LA192IncidentClass 4 · LimitedFinal reportLearjet 60 · Boston, MAThe Hop-a-Jet flight crew taking off without a takeoff clearance which resulted in a conflict with a JetBlue flight that had been cleared to land on an intersecting runway.NTSB DCA23LA185Incident · No injuriesClass 3 · LimitedFinal reportBombardier CL-600-2D24 · Burbank, CAThe interruption of the local controller’s workflow due to the necessitated management of a go-around of a third airplane that was approaching a different runway. Contributing to the incident was: 1) the controller’s decision to continue the landing of…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 DCA23FA149Incident · No injuriesClass 1 · FieldFinal reportBoeing 737-79P · Austin, TXthe local controller’s incorrect assumption that the Southwest Airlines (SWA) airplane would depart from the runway before the Federal Express airplane arrived on the same runway, which resulted in a loss of separation between both airplanes. Contributing to…NTSB DCA23LA133Incident · No injuriesClass 3 · LimitedFinal reportBoeing 777-222 · Honolulu, HIThe airport’s continued use of taxiway Kilo, despite an identified risk of pilots repeatedly failing to stop at a hold short line prior to two intersecting runways. Contributing were 1) the operator’s moving map display, which omitted a published restriction…NTSB DCA23LA125Incident · No injuriesClass 1 · LimitedFinal reportBoeing 737-900ER · Queens, NYThe American Airlines flight 106 (AAL106) crew’s surface navigation error due to distractions caused by their performance of concurrent operational tasks during taxi, which resulted in a loss of situational awareness. Contributing to the incident was the air…