NTSB investigations: Luscombe 8A, 1997

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, 1997 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\") = 1997
    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 LAX98LA051Accident · No injuriesLimited investigationFinal reportLuscombe 8 · Grass Valley, CAthe pilot's inadvertent activation of the aircraft brakes during the landing rollout.Dec 2, 1997 · N2591K · Substantial damageNTSB CHI98LA046Accident · Minor injuriesLimited investigationFinal reportLuscombe 8A · Lincoln, NEthe throttle linkage coming apart in flight, and the inadvertent stall.Nov 24, 1997 · N71329 · Substantial damageNTSB CHI97LA304Accident · 1 fatalLimited investigationFinal reportLuscombe 8A · Brooklyn, MIfailure of the pilot to see-and-avoid the transmission wires (inadequate visual lookout, and failing to maintain sufficient altitude and clearance from the obstruction).Sep 27, 1997 · N1269K · DestroyedNTSB FTW97LA259Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Seminole, TXThe pilot's inadequate compensation for the existing wind conditions. A factor was the prevailing quartering tailwind.Jul 3, 1997 · N71381 · Substantial damageNTSB IAD97LA086Accident · Minor injuriesLimited investigationFinal reportLuscombe LL-8-A · Annapolis, MDthe pilot's failure to use carburetor heat, which resulted in accumulation of carburetor ice and subsequent loss of engine power. Related factors were: carburetor icing conditions, and trees in the emergency landing area.Jun 11, 1997 · N37095 · DestroyedNTSB ANC97LA038Accident · Minor injuriesLimited investigationFinal reportLuscombe 8A · Kake, AKThe pilot's failure to refuel the airplane prior to fuel exhaustion. Factors associated with the accident were the pilot's lack of familiarity with the geographic area, the pilot's becoming lost/disoriented, and rocks and boulders in the emergency landing…Mar 27, 1997 · N1295K · Substantial damageNTSB SEA97LA073Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Arlington, WALanding long (improper touchdown point) and collapse of the main landing gear during an intentional swerve or groundloop. Factors include excessive airspeed on approach.Mar 22, 1997 · N1184K · Substantial damageNTSB SEA97LA061Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Morgan, UTDisconnection of the mixture control wire wound cable sheath. A factor was the abrupt, elevated edge of the highway pavement.Feb 22, 1997 · N77947 · Substantial damage