NTSB investigations: Luscombe 8A, 2000

8 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

19642026
NTSB investigations: Luscombe 8A, 2000 per year, 1964–2026: 852 cases
196465
196562
196657
196746
196840
196945
197044
197136
197239
197325
197427
197523
197626
197726
197818
197913
19807
198116
198213
19834
19844
198511
19869
19877
19885
19898
19908
19916
19926
19934
19944
19956
19964
19978
19982
19996
20008
20014
20023
20034
20042
20054
20064
200711
20084
20093
20107
20116
20124
20135
20142
20154
20165
20176
20185
20196
20202
20215
20225
20233
20242
20255
20263

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\") = 2000
    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.

NTSB FTW01LA027Accident · Minor injuriesLimited investigationFinal reportLuscombe 8A · Antlers, OKthe loss of engine power resulting from carburetor icing conditions.Nov 25, 2000 · N45537 · Substantial damageNTSB CHI01FA026Accident · 1 fatalField investigationFinal reportLuscombe 8A · Des Moines, IAThe pilot not maintaining aircraft control during the final turn, and the pilot's improper decision to fly the tight pattern to the closer runway. Factors relating to the accident were the pilot's inadequate distance/altitude in the traffic pattern and the…Nov 3, 2000 · N71134 · DestroyedNTSB ATL00LA094Accident · Minor injuriesLimited investigationFinal reportLuscombe 8A · Homosassa, FLThe pilot's inadvertent flight into instrument meteorological conditions and subsequently exhausting his fuel supply. Factors were his failure to obtain a weather briefing, the weather conditions which included clouds and obscuration, the residence and the…Sep 30, 2000 · N2234K · Substantial damageNTSB SEA00LA178Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Tacoma, WAThe pilot's inadequate compensation for winds and his failure to maintain directional control. Factors include a gusting crosswind.Sep 15, 2000 · N77948 · Substantial damageNTSB FTW00LA221Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Kingfisher, OKThe pilot's failure to maintain aircraft control. A factor was the downdraft weather condition.Jul 27, 2000 · N71620 · DestroyedNTSB NYC00LA192Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Westminster, MDthe delayed corrective action by the flight instructor. Factors were the failure of the private pilot to maintain directional control, his failure to use the brakes, and the lack of brakes on the right side for the flight instructor.Jul 8, 2000 · N1155B · Substantial damageNTSB FTW00LA174Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Greenville, TXThe pilot's failure to maintain directional control during the landing roll, which resulted in an inadvertent ground loop.Jun 6, 2000 · N45880 · Substantial damageNTSB LAX00LA113Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Selma, CAThe failure and separation of the right landing gear axle during taxi from landing for undetermined reasons.Feb 26, 2000 · N1544K · Substantial damage