NTSB investigations: Luscombe 8E, 1994
5 cases on aircraft the registry lists as Luscombe 8E. 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
| 1964 | 20 |
|---|---|
| 1965 | 23 |
| 1966 | 21 |
| 1967 | 23 |
| 1968 | 14 |
| 1969 | 17 |
| 1970 | 22 |
| 1971 | 15 |
| 1972 | 9 |
| 1973 | 9 |
| 1974 | 7 |
| 1975 | 8 |
| 1976 | 7 |
| 1977 | 12 |
| 1978 | 4 |
| 1979 | 5 |
| 1980 | 1 |
| 1981 | 2 |
| 1982 | 5 |
| 1983 | 3 |
| 1984 | 2 |
| 1985 | 3 |
| 1986 | 2 |
| 1987 | 3 |
| 1988 | 2 |
| 1991 | 3 |
| 1992 | 3 |
| 1993 | 2 |
| 1994 | 5 |
| 1995 | 2 |
| 1996 | 2 |
| 1997 | 2 |
| 1998 | 3 |
| 1999 | 3 |
| 2000 | 1 |
| 2001 | 4 |
| 2002 | 1 |
| 2003 | 4 |
| 2004 | 1 |
| 2005 | 1 |
| 2006 | 2 |
| 2007 | 1 |
| 2008 | 1 |
| 2009 | 2 |
| 2010 | 1 |
| 2011 | 3 |
| 2012 | 4 |
| 2015 | 3 |
| 2016 | 4 |
| 2018 | 3 |
| 2019 | 1 |
| 2021 | 1 |
| 2022 | 1 |
| 2023 | 2 |
| 2024 | 1 |
| 2025 | 1 |
| 2026 | 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 year(c.\"eventDate\") = 1994
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('8190112'))
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 year(c."eventDate") = 1994
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('8190112'))
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 LAX95LA055Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Hemet, CAThe other aircraft pilot's inadequate bounced landing recovery and his failure to maintain directional control.NTSB CHI94LA285Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Hettinger, NDthe pilot's improper use of the wheel brakes.NTSB MIA94LA140Accident · Minor injuriesLimited investigationFinal reportLuscombe 8E · Deland, FLCorrosion and subsequent failure of the left main landing gear strut.NTSB SEA94LA099Accident · No injuriesLimited investigationFinal reportLuscombe 8E · Coalville, UTThe failure of the connecting rod. Factors include the rough uneven terrain encountered during the forced landing.NTSB LAX94LA161Accident · No injuriesLimited investigationFinal reportLuscombe 8EZ · Prescott, AZthe flying pilot's inadequate compensation for the existing crosswind condition, his failure to maintain directional control, and the inadvertent entry into a ground loop. A factor in the accident was the flying pilot's lack of experience in conventional…