NTSB investigations: Luscombe 8A, 1990

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, 1990 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\") = 1990
    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 CHI91LA046Accident · Minor injuriesLimited investigationFinal reportLuscombe 8E · Mundelein, ILLanding gear tire failure and directional control not maintained by the pic/cfi.Dec 13, 1990 · N71207 · Substantial damageNTSB CHI91LA005Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Ashland, KSThe pilot-in-command's exceeding the proper climb rate of the aircraft, and his not maintaining control of the aircraft to prevent a stall.Oct 6, 1990 · N45606 · Substantial damageNTSB CHI90LA259Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Lebanon, ILthe loss of engine power for undetermined reasons while executing a go-around with insufficient runway remaining for a forced landing. A factor in the accident was the structures at the end of the runway that the pilot was attempting to avoid. This report was…Sep 6, 1990 · N2229B · Substantial damageNTSB LAX90LA295Accident · Minor injuriesLimited investigationFinal reportLuscombe 8A · Tucson, AZThe pilot to maintain proper pitch attitude and airspeed to avoid an aerodynamic stall.Aug 19, 1990 · N71330 · Substantial damageNTSB DEN90LA162Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Logan, UTThe pilot's failure to maintain directional control and his improper use of the wheel brakes. A factor related to the accident was: the pilot's lack of experience in the make and model of aircraft.Jul 12, 1990 · N45537 · Substantial damageNTSB LAX90FA181Accident · 2 fatalField investigationFinal reportLuscombe 8A · Strawberry, CAThe pilot's decision to continue VFR flight in a confined mountain pass area which was in instrument meteorological conditions; and the pilot's inflight loss of control while attempting a course reversal in the narrow confined canyon.May 20, 1990 · N71653 · DestroyedNTSB BFO90LA035Accident · No injuriesLimited investigationFinal reportLuscombe 8A · Frederick, MDThe pilot failed to maintain directional control, and used excessive braking trying to regain control.Apr 18, 1990 · N71231 · Substantial damageNTSB FTW90FA091Accident · 1 fatalField investigationFinal reportLuscombe 8-A · Baytown, TXThe pilot's inadvertent stall of the airplane while maneuvering after a partial power loss during initial climb and a partially blocked exhaust system which had been inadequately maintained.Apr 7, 1990 · N1410K · Destroyed