NTSB investigations
58 cases where the sequence of events included Wrong surface or wrong airport.
Cases, newest first
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.\"mKey\" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '284' 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."mKey" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '284' 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 DCA14IA016Incident · No injuriesIncident investigationFinal reportBoeing 747 - 409LCF · Wichita, KSthe flight crew's failure to properly identify the airport and runway of intended landing. Contributing to the incident was the flight crew's failure to follow company procedures for crosschecking navigational information and visual cues to verify the airport…NTSB ANC11LA008Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Platinum, AKThe pilot's misidentification of the airport's active runway, resulting in an off-runway landing and collision with a ditch/berm.NTSB WPR10CA035Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Angwin, CAThe pilot's failure to properly identify the runway surface for takeoff and his subsequent failure to abort the takeoff when he realized he was not on the runway. Contributing to the accident was the pilot’s failure to select the appropriate radio frequency…NTSB OPS10IA001Incident · No injuriesIncident investigationFinal reportBoeing 767 · Atlanta Hartsfield Intl. Apt. (KATL), GAThe flight crew’s failure to identify the correct landing surface due to fatigue. Contributing to the cause of the incident were (1) the flight crew’s decision to accept a late runway change, (2) the unavailability of the approach light system and the…NTSB CEN09CA422Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Hibbing, MNThe pilot mistakenly using a closed taxiway for takeoff, which resulted in the airplane striking a construction barricade.NTSB CEN09TA399Accident · No injuriesFinal reportCessna 182 · Cookson, OKThe pilot's failure to maintain clearance with the building while taxiing on a road.NTSB WPR09CA274Accident · No injuriesData collectionFinal reportPiper PA-38-112 · Grangeville, IDThe pilot's failure to maintain clearance from an obstacle during taxi.NTSB ANC08CA048Accident · No injuriesData collectionFinal reportCessna 172 · Anchorge, AKThe pilot's failure to maintain clearance from a road sign while taxiing from landing.