Luscombe 11A
NTSB investigations · 23
Matched to the registry by N-number and event date, newest first.
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.aircraft_model_code IN ('8890402')
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.aircraft_model_code IN ('8890402')
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 WPR10LA306Accident · No injuriesLimited investigationFinal reportLuscombe 11A · Merced, CAThe pilot’s inability to maintain airplane control during cruise flight due to the failure of the elevator trim tab as a result of missing hardware for the elevator control cable bellcrank to elevator torque tube attachment bracket.NTSB SEA05LA015Accident · No injuriesLimited investigationFinal reportLuscombe 11A · Redmond, ORThe student pilot's failure to maintain directional control during the landing roll. Also causal were the instructor's inadequate supervision and remedial action. Factors include soft terrain just off the side of the runway.NTSB LAX01LA184Accident · Minor injuriesLimited investigationFinal reportLuscombe 11A · Apple Valley, CAThe pilot's fuel mismanagement, which led to fuel exhaustion, a loss of engine power, and subsequent landing on unsuitable terrain.NTSB FTW96LA213Accident · No injuriesLimited investigationFinal reportLuscombe 11A · Calhan, COthe pilot's failure to maintain directional control during landing. A factor was a gusting cross-wind.NTSB FTW90LA113Accident · No injuriesLimited investigationFinal reportLuscombe 11 · Fort Worth, TXLoss of control on the ground, due to a locked left brake, undetermined reasons.NTSB FTW89LA019Accident · Minor injuriesLimited investigationFinal reportLuscombe 11A · Houston, TXNTSB ANC81DAA09Accident · No injuriesClosedLuscombe 11A · Moses Point, AKNTSB MKC75FER02Accident · No injuriesClosedLuscombe 11A · Anoka, MNNTSB CHI74FEE13Accident · No injuriesClosedLuscombe 11A · Wheeling, ILNTSB DEN73DQA22Accident · Minor injuriesClosedLuscombe 11A · Santa Fe, NMNTSB MKC73FCJ11Accident · No injuriesClosedLuscombe 11A · Papillion, NENTSB DEN72DTM14Accident · No injuriesClosedTemco 11A · Modena, UTNTSB NYC72FHJ07Accident · Serious injuriesClosedLuscombe 11A · East Moriches, NYNTSB NYC71DFM25Accident · Minor injuriesClosedLuscombe 11A · G.Barrington, MANTSB SEA70FVQ01Accident · No injuriesClosedLuscombe 11A · Bend, ORNTSB LAX70F0115Accident · No injuriesClosedLuscombe 11A · Bakersfield, CANTSB OAK69D0299Accident · Minor injuriesClosedLuscombe 11A · Lathrop Wells, NVNTSB DEN69D0187Accident · No injuriesClosedLuscombe 11A · Farmington, NMNTSB DEN69D0053Accident · No injuriesClosedTemco 11A · Farmington, NMNTSB SEA67F0125Accident · No injuriesClosedLuscombe 11A · Bellevue, WANTSB LAX67D0044Accident · No injuriesClosedLuscombe 11A · Scottsdale, AZNTSB MIA66F0501Accident · Minor injuriesClosedLuscombe 11A · Thomasville, NCNTSB UNK65X1146Accident · Serious injuriesClosedLuscombe 11A · Hinsdale, IL
Back to Luscombe 11A