NTSB investigations, 2009
7 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
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\") = 2009
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") = 2009 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 OPS10IA003Incident · No injuriesIncident investigationFinal reportDetroit, MIThe ground controller did not monitor the progress of the fire truck to ensure that the driver followed the expected route. A contributing factor was the ground controller's misunderstanding of the fire truck driver's requested destination on the airport.NTSB OPS09IA009Incident · No injuriesIncident investigationFinal reportBombardier DHC-8-202 · Cleveland, OHThe local controller did not visually scan the runways and ensure that the E145 had crossed runway 24L prior to issuing a takeoff clearance to the DH8, did not ensure separation between the two airplanes, and did not cancel takeoff clearance for the DH8 in a…NTSB OPS09IA008Incident · No injuriesIncident investigationFinal reportAirbus A320 · Boston, MAThe vehicle operator's failure to follow the designated haul route to the construction site and his failure to adhere to airport driving procedures, which led to missed visual cues and lack of required communication prior to crossing the active runway.…NTSB OPS09IA007Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Cleveland, OHThe ground controller did not issue taxi instructions in accordance with FAA Order 7110.65, paragraph 3-7-2. The local controller did not scan the runways prior to issuing a taxi into position and hold instruction to SWA1080 as required by FAA Order 7110.65…NTSB OPS09IA005Incident · No injuriesIncident investigationFinal reportBombardier CL-600-2B1 · Charlotte, NCThe Charlotte local control east controller's failure to ensure that the runway was clear prior to authorizing N409DR to enter the runway.NTSB OPS09IA004Incident · No injuriesIncident investigationFinal reportBE20 · Camp Springs, MDThe failure of the ground controller to coordinate the runway crossings with the local controller and her failure to scan the runway prior to issuing the crossing instructions. Contributing to the incident was the combination of the front line manager/tower…NTSB CEN09LA265Accident · Serious injuriesLimited investigationFinal reportT Bird T Bird II · Carlock, ILThe pilot's failure to gain sufficient altitude during the takeoff in order to avoid contacting the cameraman. Contributing to the accident was the pilot's lack of experience.