NTSB investigations: Cessna 152, 2000, TX

8 cases on aircraft the registry lists as Cessna 152. 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

19772026
NTSB investigations: Cessna 152, 2000, TX per year, 1977–2026: 244 cases
19772
19784
197915
198014
198122
198214
198319
198410
19858
19865
19879
19884
19899
19905
19913
19924
19939
19942
19957
19964
19978
19989
19993
20008
20015
20022
20032
20053
20062
20074
20083
20101
20121
20134
20143
20151
20162
20171
20182
20195
20201
20212
20231
20241
20251

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.\"eventStateOrRegion\" = 'TX' AND c.\"eventCountry\" = 'USA'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2071835'))
  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 FTW00FA268Accident · 2 fatalField investigationFinal reportCessna 152 · Navasota, TXthe pilot's failure to maintain control of the airplane due to spatial disorientation. Contributory factors were the clouds, dark night light conditions, the pilot's lack of total instrument flight time, and the pilot's self-induced pressure to complete the…Sep 25, 2000 · N5357M · DestroyedNTSB FTW00LA256Accident · Minor injuriesLimited investigationFinal reportCessna 152 · Saspamco, TXthe failure of the #3 and #4 connecting rods. A contributing factor was the lack of suitable terrain condition for the forced landing.Sep 12, 2000 · N64921 · Substantial damageNTSB FTW00LA238Accident · No injuriesLimited investigationFinal reportCessna 152 · Wichita Falls, TXThe student pilot's delayed landing flare and failure to recover from the ensuing bounced landing.Aug 21, 2000 · N4711L · Substantial damageNTSB FTW00LA234Accident · Minor injuriesLimited investigationFinal reportCessna 152 · San Antonio, TXThe pilot's failure to maintain aircraft control. A factor was the crosswind.Aug 16, 2000 · N68168 · Substantial damageNTSB FTW00LA182Accident · No injuriesLimited investigationFinal reportCessna 152 · Mcallen, TXLoss of engine power for reasons undetermined. A factor was the lack of suitable terrain for the forced landing.Jun 19, 2000 · N94290 · Substantial damageNTSB FTW00LA109Accident · Minor injuriesLimited investigationFinal reportCessna 152 · Decatur, TXThe instructor pilot's failure to maintain the minimum controllable airspeed during a simulated emergency approach, which resulted in a stall.Mar 28, 2000 · N94912 · Substantial damageNTSB FTW00LA089Accident · No injuriesLimited investigationFinal reportCessna 152 · Fort Worth, TXThe pilot's failure to maintain aircraft control during landing. A factor was the crosswind condition.Mar 1, 2000 · N48821 · Substantial damageNTSB FTW00LA071Accident · No injuriesLimited investigationFinal reportCessna 152 · Slidell, TXThe pilot's improper approach planning, which resulted in a downwind landing. A factor was the loss of engine power for undetermined reasons.Jan 21, 2000 · N6179Q · Substantial damage