NTSB investigations: Cessna 152, 2000

8 cases on aircraft the registry lists as Cessna 152, where the first occurrence was “Hard landing”. 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

19822026
NTSB investigations: Cessna 152, 2000 per year, 1982–2026: 264 cases
198218
198325
198426
198516
19864
198721
198817
198912
19907
199110
19927
19939
19949
19955
199612
19976
19986
19997
20008
20017
20026
20038
20042
20059
20065
20072

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 ('2071835')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 200))
  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 LAX01LA028Accident · No injuriesLimited investigationFinal reportCessna 152 · Ramona, CAThe dual student's habit interference, from his previous training in a different type of airplane, that precipitated his improper use of the elevator control during a go-around.Oct 25, 2000 · N5447L · 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 CHI00LA313Accident · No injuriesLimited investigationFinal reportCessna 152 · Cumberland, WIthe go-around not performed and the inadequate flare by the pilot.Aug 18, 2000 · N5354M · Substantial damageNTSB CHI00LA232Accident · No injuriesLimited investigationFinal reportCessna 152 · Indianapolis, INthe non-pilot rated passenger's improper flare and not relinquishing the controls, and the pilot's inadequate remedial action and the pilot's poor decision to practice instruction with an unqualified pilot prior to becoming a Certified Flight Instructor.Jul 29, 2000 · N93289 · Substantial damageNTSB NYC00LA181Accident · No injuriesLimited investigationFinal reportCessna 152 · Beverly, MAThe pilot's improper flare, which resulted in a loss of control.Jul 3, 2000 · N48858 · Substantial damageNTSB CHI00LA197Accident · No injuriesLimited investigationFinal reportCessna 152 · Lincoln, NEthe misjudged flare and the inadequate recovery from the bounced landing performed by the student pilot.Jul 2, 2000 · N6432M · Substantial damageNTSB CHI00LA166Accident · No injuriesLimited investigationFinal reportCessna 152 · Mankato, MNthe pilot performed inadequate remedial action to recover when the airplane ballooned during the landing flare. Factors associated with the accident were excessive airspeed during the landing and an improper landing flare.Jun 17, 2000 · N6445P · Substantial damageNTSB MIA00LA085Accident · No injuriesLimited investigationFinal reportCessna 152 · Louisburg, NCThe improper recovery from the bounced landing by the pilot-in-command for his failure to apply power and inadvertent stall by the pilot-in-command resulting in a hard landing. A contributing factor was the total lack of experience of the pilot-in-command.Feb 7, 2000 · N69174 · Substantial damage