NTSB investigations: Luscombe 8A, 2008
4 cases on aircraft the registry lists as Luscombe 8A. 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 | 65 |
|---|---|
| 1965 | 62 |
| 1966 | 57 |
| 1967 | 46 |
| 1968 | 40 |
| 1969 | 45 |
| 1970 | 44 |
| 1971 | 36 |
| 1972 | 39 |
| 1973 | 25 |
| 1974 | 27 |
| 1975 | 23 |
| 1976 | 26 |
| 1977 | 26 |
| 1978 | 18 |
| 1979 | 13 |
| 1980 | 7 |
| 1981 | 16 |
| 1982 | 13 |
| 1983 | 4 |
| 1984 | 4 |
| 1985 | 11 |
| 1986 | 9 |
| 1987 | 7 |
| 1988 | 5 |
| 1989 | 8 |
| 1990 | 8 |
| 1991 | 6 |
| 1992 | 6 |
| 1993 | 4 |
| 1994 | 4 |
| 1995 | 6 |
| 1996 | 4 |
| 1997 | 8 |
| 1998 | 2 |
| 1999 | 6 |
| 2000 | 8 |
| 2001 | 4 |
| 2002 | 3 |
| 2003 | 4 |
| 2004 | 2 |
| 2005 | 4 |
| 2006 | 4 |
| 2007 | 11 |
| 2008 | 4 |
| 2009 | 3 |
| 2010 | 7 |
| 2011 | 6 |
| 2012 | 4 |
| 2013 | 5 |
| 2014 | 2 |
| 2015 | 4 |
| 2016 | 5 |
| 2017 | 6 |
| 2018 | 5 |
| 2019 | 6 |
| 2020 | 2 |
| 2021 | 5 |
| 2022 | 5 |
| 2023 | 3 |
| 2024 | 2 |
| 2025 | 5 |
| 2026 | 3 |
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\") = 2008
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('8190104', '8190111'))
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") = 2008
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('8190104', '8190111'))
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 CEN09CA001Accident · No injuriesData collectionFinal reportLuscombe 8A · Greeley, COThe pilot's failure to maintain directional control during the landing roll resulting in a ground loop. Contributing to the accident was the lack of remedial action from the flight instructor.NTSB NYC08CA205Accident · No injuriesData collectionFinal reportLuscombe 8A · Indiantown, FLAn inadequate annual inspection that failed to detect a damaged rudder cable which resulted in the cable's subsequent failure during takeoff.NTSB CHI08CA118Accident · No injuriesData collectionFinal reportLuscombe 8A · Remus, MIThe loss of engine power during approach due to fuel contamination. Contributing to the accident were the unsuitable terrain and a tree.NTSB NYC08CA153Accident · Minor injuriesData collectionFinal reportLuscombe 8A · Lincoln, METhe pilot-rated-passenger's failure to maintain directional control during takeoff.