NTSB investigations, MI
2 cases where the sequence of events included Runway incursion veh/AC/person.
Cases per year
| 2009 | 1 |
|---|---|
| 2016 | 1 |
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 c.\"eventStateOrRegion\" = 'MI' AND c.\"eventCountry\" = 'USA'
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 c."eventStateOrRegion" = 'MI' AND c."eventCountry" = 'USA' 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 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…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.