NTSB investigations: Cessna 182J

6 cases on aircraft the registry lists as Cessna 182J, where the first occurrence was “Overrun”. 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 182J per year, 1982–2026: 6 cases
19821
19831
19871
19911
19951
19991

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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072722')
      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\" = 340))
  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 FTW99LA259Accident · Minor injuriesLimited investigationFinal reportCessna 182J · Jeanerette, LAThe pilot's failure to attain the proper touchdown point resulting in the aircraft overrunning the runway on landing roll. A factor was the gusty crosswind condition.Sep 12, 1999 · N2751F · Substantial damageNTSB CHI95LA209Accident · No injuriesLimited investigationFinal reportCessna 182S · New Haven, MIThe pilot's improper raising of the flaps during the aborted landing. Factors associated with this accident were the pilot selecting the wrong runway, not attaining the appropriate touchdown point on the runway, and delay in aborting the landing.Jul 3, 1995 · N2423Q · Substantial damageNTSB SEA91FA057Accident · 3 fatalField investigationFinal reportCessna 182J · Glendale, ORThe pilot's failure to use all available runway for this landing, aggravated by his failure to initiate a go-around after misjudging the proper touchdown point and landing with a tailwind.Feb 22, 1991 · N3154F · DestroyedNTSB CHI87LA181Accident · No injuriesLimited investigationFinal reportCessna 182J · Lansing, ILWhile landing on runway 27, the pilot overshot the runway and rolled into a shallow ditch.Jul 31, 1987 · N3164F · Substantial damageNTSB LAX83LA118Accident · No injuriesLimited investigationFinal reportCessna 182J · Peoria, AZThe acft collided with a sign and a wall during an attempted go-around after an overrun. The pilot was practicing and had made 2 short field landings on the 3rd approach he forgot to lower flaps. His approach was fast and long and he landed too FAR down the…Feb 24, 1983 · N2912F · Substantial damageNTSB ATL82DA133Accident · No injuriesFinal reportCessna 182 · Summersville, WVAccording to the pilot, he made his landing approach high and hot. He touched down long and was unable to stop on the remaining runway. While applying brakes, the aircraft veered off the side of the runway. Subsequently, the nose and right main gear failed.May 15, 1982 · N3440F · Substantial damage