NTSB investigations, 2016
8 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\") = 2016
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") = 2016 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 OPS17IA008IncidentClass 3 · IncidentFinal reportBombardier CL 600 2B19 · San Francisco, CAThe captain’s inadvertent turn onto the incorrect taxiway and subsequent entry onto an active runway without a clearance, which resulted in the runway incursion.NTSB OPS17IA003IncidentClass 2 · IncidentFinal reportDouglas DC 9 83 · Westfield, MAThe air traffic controller issuing the aircraft a clearance to land while there was a vehicle authorized to be on the same runway. Contributing to the incident was the air traffic controller's decision to not simulcast the local control and ground control…NTSB DCA16WA228Incident · No injuriesForeign investigationBoeing 777 · London, United KingdomThe Aircraft Accident Investigation Bureau (AAIB) of India has notified the NTSB of an accident involving a Boeing 777 that occurred on August 30, 2016. The NTSB has appointed a U.S. Accredited Representative to assist the AAIB's investigation under the…NTSB DCA16IA200Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320 211 · Rapid City, SDThe flight crew's misidentification of the desired landing runway due to excess altitude requiring an extended downwind, and failure to use all available navigation information.NTSB OPS16IA008IncidentClass 3 · IncidentFinal reportEmbraer S A EMB-505 · Dallas, TXThe controller's miscommunication of a clearance and failure to recognize and correct the readback resulting in the flight crew initiating takeoff without a clearance.NTSB OPS16IA009IncidentClass 3 · IncidentFinal reportCessna 172S · Honolulu, HIThe air traffic controller's decision to clear an aircraft to land on a runway occupied by another aircraft that had previously been instructed to line up and wait. Contributing to the runway incursion was the failure of the air traffic controller to visually…NTSB OPS16IA004Incident · No injuriesIncident investigationFinal reportAirbus A321 231 · Fort Lauderdale, FLThe air traffic controller's failure to ensure the runway surface area was clear of vehicles before clearing an aircraft for takeoff. Also causal was the flight crew's decision to initiate a takeoff while the Runway Status Lights (RWSL) Takeoff Hold Lights…NTSB OPS16IA002Incident · No injuriesIncident investigationFinal reportBombardier CL600 2D24 · Detroit, MIThe local controller's failure to visually scan and ensure that the runway surface was not occupied by a vehicle or other aircraft before issuing a takeoff clearance to the pilot. Contributing to this incident was the relieved controller's failure to monitor…