NTSB investigations: Luscombe 8A, 1986
9 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
Latest 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\") = 1986
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") = 1986
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 LAX87LA031Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Half Moon Bay, CAThe acft collided with the terrain during a forced landing following a loss of engine power. The plt indicated that he retarded the throttle and applied the carburetor heat to descend from 3,000 to 2,000 ft when the engine quit. He was unable to restart the…NTSB SEA86FA213Accident · 2 fatalField investigationFinal reportLuscombe 8A · Pelican, AKAt about 1500 adt on 8/19/86, the plt departed on a flt to hoonak, AK. When he did not return, a search was initiated. The acft was located at 1400 adt on the following day where it had crashed on rising mountainous terrain at an elev of about 1740 ft. an…NTSB NYC86LA210Accident · Serious injuriesLimited investigationFinal reportLuscombe 8A · Nantucket, MAThe pilot made a precautionary landing on a beach shortly after takeoff when the engine stopped running. However during engine examination, nothing was found to determine malfunction or failure.NTSB SEA86LA189Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Rosalia, WADuring climb out the acft entered a departure stall. The acfts left wing dropped and the acft came to rest 90 degrees from its departure heading. This acft has no stall warning system.NTSB ATL86LA213Accident · Minor injuriesLimited investigationFinal reportLuscombe 8A · Ringgold, GAThe pilot reported he attempted to make a 180 degree turn because he realized he was getting too close to an airport while on a cross country flight. A highway patrolman said the pilot told him he became disoriented during the turn, cut the power to land, and…NTSB DEN86LA186Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Salida, COAccording to the plt, upon entering the mountain pass, the acft he was piloting encountered downdrafts from which he was unable to recover. The plt stated he bled off airspeed until contact with the trees. A local flt instructor who witnessed the accident…NTSB NYC86LA171Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Barkhanstead, CTThe flight took off with about seven gallons of fuel with a slight tailwind. But after about 30 minutes of flight the flight encountered a headwind. The aircraft suffered fuel exhaustion and the pilot executed a precautionary landing in a field. During ground…NTSB ATL86LA091Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Hampton, GADuring landing roll the pilot was unable to keep the tailwheel on the ground and the aircraft nosed over. Post crash examination of the wreckage disclosed that the brake pads were worn down to the rivets.NTSB SEA86LA043Accident · 2 fatalLimited investigationFinal reportLuscombe 8A · Sloan, NVAcft was observed performing low-level aerobatics, failed to complete pull-out from second consecutive overhead maneuver, striking ground in 20-30 degree nose-low attitude. No evidence of pre-impact mechanical failure or malfunction found in acft structure,…