Final NTSB investigations
15 cases where the sequence of events included Navigation error.
Cases per year
| 2009 | 1 |
|---|---|
| 2013 | 1 |
| 2014 | 1 |
| 2017 | 2 |
| 2018 | 1 |
| 2021 | 2 |
| 2022 | 2 |
| 2023 | 1 |
| 2024 | 2 |
| 2025 | 2 |
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.\"completionStatus\" = 'Completed'
AND c.\"mKey\" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '280' 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."completionStatus" = 'Completed' AND c."mKey" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '280' 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 CEN25LA356Accident · Serious injuriesClass 3 · LimitedFinal reportSikorsky S-76 · Round Mountain, TXThe flight crew’s failure to properly identify the heliport in dark night conditions, which resulted in the flight crew attempting to land and a subsequent impact with trees and terrain.NTSB ERA25LA199Accident · Serious injuriesClass 4 · LimitedFinal reportCessna 182A · Ocala, FLThe pilot’s decision to depart on the flight with known electrical issues and his subsequent loss of situational awareness (geographic position), which resulted in his eventual decision to perform an off-airport landing.NTSB WPR24LA207Accident · Serious injuriesClass 4 · LimitedFinal reportPiper J3C-65 · Scheelite, CAThe pilot’s inadvertent entry to a box canyon where the airplane could not outclimb the rising terrain.NTSB WPR24FA104Accident · 1 fatalClass 3 · FieldFinal reportKolb Firestar KXP · Cave Junction, ORThe pilot's exceedance of the airplane's critical angle of attack during a turn, which resulted in an aerodynamic stall. Contributing to the accident was the pilot's use of potentially impairing substances with bipolar disorder, which resulted in a decreased…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 WPR23LA052Accident · No injuriesClass 4 · LimitedFinal reportRutan Long-EZ · Mountain Green, UTThe pilot’s flight into a valley with rising terrain that the airplane was incapable of out-climbing.NTSB ERA23LA031Accident · No injuriesClass 4 · LimitedFinal reportCessna 172P · Elizabethtown, KYThe pilot's decision to continue the taxi without visual reference to the surface, due to his vision being impaired by darkness and glare, which resulted in the airplane’s departure from the paved surface and impact with a ditch. Contributing was the flight…NTSB WPR21FA321Accident · 3 fatalClass 3 · FieldFinal reportCessna 182H · Bountiful, UTThe decision of both pilots to fly into a steep canyon, which resulted in the airplane being unable to maintain a sufficient altitude to clear rising terrain. Contributing to the accident was their delayed initial action in responding to the hazard, and their…NTSB ERA21LA101Accident · 1 fatalClass 3 · LimitedFinal reportBeech F33 · Columbia, SCThe pilot's in-flight loss of airplane control due to spatial disorientation during a missed approach in instrument meteorological conditions.NTSB CEN19CA017Accident · No injuriesData collectionFinal reportPiper PA28R · Hobbs, NMThe pilot's incorrect altimeter setting during the night visual approach, which resulted in a controlled flight into terrain.NTSB OPS18IA003IncidentClass 3 · IncidentFinal reportBombardier CL600 2D24 · Medford, ORThe incident was caused by the air traffic controller assigning an altitude below the published procedure altitude for the approach segment to be flown prior to the aircraft being established on a published portion of the approach. Contributing to the…NTSB WPR17LA195Accident · 1 fatalLimited investigationFinal reportWalker Edgar E Glastar · Cascade, IDThe pilot's inadequate flight planning, preparation, and navigation, which resulted in the airplane entering a canyon that the pilot was unable to exit by climbing the airplane. Also causal were his in-flight decision-making and his execution of the course…NTSB DCA14IA037Incident · No injuriesIncident investigationFinal reportBoeing 737 7H4 · Branson, MOThe 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 comply with procedures for use of navigation information and visual cues to verify the airport and runway…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 ANC09LA069Accident · No injuriesLimited investigationFinal reportCessna 172L · Anchorage, AKThe pilot's unfamiliarity with the airport environment, which resulted in his taxiing the airplane onto a no-taxi section of roadway and into a road sign. Contributing to the accident was the pilot's failure to avail himself of additional information that…