NTSB investigations: Cessna 152, MN

7 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, MN per year, 1982–2026: 7 cases
19822
19871
19961
19971
20001
20021

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 c.\"eventStateOrRegion\" = 'MN' 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')
      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 CHI02LA107Accident · No injuriesLimited investigationFinal reportCessna 152 · Maple Lake, MNThe student pilot's inadequate flare and compensation for the crosswind condition during landing. A factor to the accident was the crosswind condition.Apr 16, 2002 · N752AA · 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 CHI97LA147Accident · No injuriesLimited investigationFinal reportCessna 152 · Crystal, MNthe student pilot's misjudged flare and improper recovery from a bounced landing. A factor was the lack of recent flight time.May 24, 1997 · N5499B · Substantial damageNTSB CHI96LA341Accident · No injuriesLimited investigationFinal reportCessna 152 · Lakeville, MNthe student pilot misjudged the landing flare which resulted in the hard landing.Sep 17, 1996 · N757PC · Substantial damageNTSB CHI87LA128Accident · No injuriesLimited investigationFinal reportCessna 152 · Minneapolis, MNThe plt stated that while practicing touch-and-go landings, he extended full flaps on final apch and maintained rwy alignment. According to the plt, the acft touched down hard and began to porpoise. A police officer witnessed the acft bounce three times after…May 15, 1987 · N92140 · Substantial damageNTSB CHI83LA012Accident · No injuriesLimited investigationFinal reportCessna 152 · St. Cloud, MNWhile performing a touch-and-go landing, the pilot used a higher than normal speed. After touching down, the aircraft became airborne again, then began to porpoise. After about the 3rd or 4th bounce, the nose gear failed.Oct 10, 1982 · N6332P · Substantial damageNTSB CHI82DA313Accident · No injuriesFinal reportCessna 152 · Chatfield, MNThe pilot reported that he was landing on runway 36 at a private airport with a crosswind from 300 deg at 17, gusting 26 KTS. The wind was blowing over tall trees along the left side of the runway, near the approach end. The pilot stated that this resulted in…Jul 29, 1982 · N6489B · Substantial damage