NTSB investigations: Luscombe 8E
5 cases on aircraft the registry lists as Luscombe 8E, where the first occurrence was “Loss of control - in flight”. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1982 | 1 |
|---|---|
| 1985 | 1 |
| 1987 | 1 |
| 1994 | 1 |
| 2000 | 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 x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('8190112')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 250))
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 x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('8190112')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 250))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun 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 DEN00LA107Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Santa Fe, NMThe pilot's failure to maintain control of the aircraft. A factor was gusty wind conditions.NTSB LAX95LA055Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Hemet, CAThe other aircraft pilot's inadequate bounced landing recovery and his failure to maintain directional control.NTSB ATL87LA253Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Cartersville, GAThe plt reported a loss of power on climb out. An off arpt landing attempt resulted in impact with trees and substantial damage to the acft. Temperature and dewpoint were within the range for carburetor ice buildup. Examination of the acft revealed a cruise…NTSB FTW85FA209Accident · 2 fatalField investigationFinal reportLuscombe 8E · Verden, OKAt about 1700 CDT on 5/5/85, the acft was observed taking off at chickasha, OK. At sometime after 1700, an acft matching its description was observed flying low over a lake. A witness in that area observed it pulled up in a steep climb over the dam, until it…NTSB CHI82DA258Accident · No injuriesFinal reportLuscombe 8F · Belleville, MIDuring the approach the acft stalled about 20 ft AGL. The plt added power but the acft touched down short of the rwy & collided with a ditch.