NTSB investigations
4 cases where NTSB found Approach lighting.
Cases per year
| 2008 | 1 |
|---|---|
| 2009 | 1 |
| 2015 | 1 |
| 2019 | 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\", '03012015')) 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", '03012015')) 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 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 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 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.