NTSB investigations: Luscombe 8A, 2007
11 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\") = 2007
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") = 2007
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 NYC08LA021Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Pensacola, FLThe fatigue fracture of the tail wheel spring during takeoff.NTSB LAX07CA289Accident · No injuriesData collectionFinal reportLuscombe 8A · Reedley, CAThe pilot's failure to maintain directional control on landing.NTSB DFW07LA206Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Mason County, TXThe loss of control as result of the collapsed right main landing gear during the landing roll. A contributing factor was the failure of the right main gear as result of corrosion.NTSB CHI07CA175Accident · Minor injuriesData collectionFinal reportLuscombe 8A · London, OHThe pilot's failure to maintain directional control of the airplane and the pilot's inadequate compensation for the crosswind which resulted in a ground loop and subsequent collision with a taxiway sign. Factors contributing to the accident include the…NTSB CHI07CA171Accident · No injuriesData collectionFinal reportLuscombe 8A · Columbia, ILThe pilot's failure to maintain directional control of the airplane, causing a ground loop, subsequent runway excursion, and left main gear collapse. Factors in the accident include the ground loop encountered and the depression.NTSB CHI07CA156Accident · Minor injuriesData collectionFinal reportLuscombe 8A · Elwood, INThe commercial pilot's failure to maintain adequate altitude and airspeed which resulted in the airplane mushing into the terrain during the simulated forced landing along with the CFI's failure to adequately supervise the commercial pilot's actions.NTSB NYC07CA110Accident · No injuriesData collectionFinal reportLuscombe 8A · Whitefield, NHThe pilot's failure to maintain directional control while landing. A factor in this accident was the crosswind condition.NTSB CHI07LA126Accident · Serious injuriesLimited investigationFinal reportLuscombe 8A · Fruitport, MIThe flight instructor failed to use carburetor heat during takeoff in icing conditions. A factor was the power line pole.NTSB CHI07CA101Accident · No injuriesData collectionFinal reportLuscombe 8A · Chippewa Falls, WIThe pilot intentionally leaving the airplane unoccupied during the engine start, which resulted in the unoccupied airplane traversing into a cornfield. A factor was the rough/uneven cornfield.NTSB LAX07CA088Accident · Minor injuriesData collectionFinal reportLuscombe 8A · Compton, CAThe pilot's failure to maintain directional control during landing rollout. A contributing factor was the passenger's interference with the pilot's manipulation of the controls.NTSB DFW07CA057Accident · No injuriesData collectionFinal reportLuscombe 8A · El Paso, TXThe pilot's foot becoming lodged behind the right rudder pedal which resulted in a loss of directional control during landing.