NTSB investigations: Cessna 152, 2000

7 cases on aircraft the registry lists as Cessna 152, where the first occurrence was “Loss of control - on ground/water”. 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: 376 cases
198231
198325
198426
198527
198623
198727
198821
198917
199020
199115
199211
199316
199422
199513
199614
19977
19989
199912
20007
200110
20026
20034
20044
20054
20063
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\" = 260))
  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 CHI00LA202Accident · No injuriesLimited investigationFinal reportCessna 152 · Park River, NDdirectional control not being maintained by the pilot during landing.Jul 13, 2000 · N69066 · Substantial damageNTSB LAX00LA252Accident · No injuriesLimited investigationFinal reportCessna 152 · Oakland, CAfailure of the instructor to adequately supervise the student, resulting in a loss of directional control.Jul 6, 2000 · N6439M · Substantial damageNTSB NYC00LA177Accident · No injuriesLimited investigationFinal reportCessna 152 · West Point, VAThe student pilot's failure to maintain directional control during the landing roll.Jul 1, 2000 · N68910 · Substantial damageNTSB CHI00LA140Accident · No injuriesLimited investigationFinal reportCessna 152 · Goshen, INthe failure of the student pilot to maintain directional control on the takeoff roll. Factors to the accident were the lack of experience of the student pilot and the improper use of the throttle.May 22, 2000 · N68182 · Substantial damageNTSB LAX00LA161Accident · No injuriesLimited investigationFinal reportCessna 152 · Eureka, CAThe pilot's failure to compensate for a crosswind and to maintain directional control during landing.Apr 19, 2000 · N6251Q · Substantial damageNTSB NYC00LA101Accident · No injuriesLimited investigationFinal reportCessna 152 · Hazelton, PAThe pilot's failure to maintain directional control while landing with a crosswind.Mar 1, 2000 · N67639 · Substantial damageNTSB SEA00LA044Accident · No injuriesLimited investigationFinal reportCessna 152 · Billings, MTDirectional control was not maintained. Inadequate remedial action was a factor.Feb 16, 2000 · N757XG · Substantial damage