NTSB investigations
10 cases where NTSB found Approach aid coverage/avail.
Cases per year
| 2008 | 2 |
|---|---|
| 2009 | 1 |
| 2015 | 1 |
| 2016 | 1 |
| 2018 | 2 |
| 2019 | 2 |
| 2022 | 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.\"mKey\" IN (SELECT f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f.\"findingCode\", '030120')) 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 f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f."findingCode", '030120')) 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 WPR23LA065Accident · No injuriesClass 4 · LimitedFinal reportPiper PA42 · Lewistown, MTThe pilot’s improper landing flare, which resulted in a hard landing. Contributing to the accident was the out of service visual glideslope indicator and snow obscuring the runway markings.NTSB GAA19CA525Accident · Minor injuriesData collectionFinal reportCessna 182 · Charleston, WVThe pilot's improper approach path at night and his misjudgment of the landing point, which resulted in landing short of the runway and impact with the runway's engineered materials arrestor system.NTSB DCA19FA089Accident · Minor injuriesClass 3 · FieldFinal reportEmbraer EMB145 · Presque Isle, METhe flight crew’s decision, due to confirmation bias, to continue the descent below the decision altitude when the runway had not been positively identified. Contributing to the accident were (1) the first officer’s fatigue, which exacerbated his confirmation…NTSB GAA19CA001Accident · No injuriesData collectionFinal reportCessna 340 · Keokuk, IAThe pilot's failure to correctly identify the runway environment during an instrument approach at night in instrument meteorological conditions because he mistook building lights for runway lights, which resulted in landing short of the runway.NTSB OPS18IA015Incident · No injuriesClass 3 · IncidentFinal reportBoeing 747 · Chicago, ILInterference with the localizer signal resulting in a Multipath condition experienced by CAL5148 while conducting an ILS CAT III (autoland) approach. This condition resulted in a runway excursion and subsequent go-around. The interference was most likely…NTSB CEN16LA097Accident · No injuriesLimited investigationFinal reportPiper PA 28-140 · Sturtevant, WIThe pilot's failure to maintain a proper glidepath during a landing at dusk, which resulted in impact with a moving ground vehicle. Contributing to the accident was the inoperative precision approach path indicator.NTSB CEN16LA016Accident · Serious injuriesLimited investigationFinal reportCirrus Design SR22 · Lancaster, TXThe pilot’s failure to maintain a proper glidepath during a night visual approach, which resulted in impact with a power line. Contributing to the accident was an inoperative precision approach path indicator.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 ERA09FA053Accident · 2 fatalField investigationFinal reportCirrus Design SR22 · Tallahassee, FLThe pilot's failure to maintain adequate airspeed on final approach, which resulted in a low-altitude aerodynamic stall and spin. Contributing to the accident was the pilot's failure to fly the published instrument approach and his subsequent failure to…NTSB SEA08LA082Accident · Serious injuriesLimited investigationFinal reportRaytheon 1900D · Kayenta, AZThe flight crew's failure to execute a missed approach, which resulted in a runway excursion after landing. Contributing to the accident were the inoperative lights, weather conditions below published approach minimums, and the slush contaminated runway.