NTSB investigations: Cessna 182G

8 cases on aircraft the registry lists as Cessna 182G, where the first occurrence was “Loss of control - in flight”. 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

19852026
NTSB investigations: Cessna 182G per year, 1985–2026: 8 cases
19851
19872
19911
19931
20031
20041
20071

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 ('2072716')
      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\" = 250))
  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 SEA07LA137Accident · Serious injuriesLimited investigationFinal reportCessna 182 · Moab, UTThe pilot's failure to maintain control of the airplane while maneuvering after takeoff.May 28, 2007 · N2164R · Substantial damageNTSB SEA04FA032Accident · 4 fatalField investigationFinal reportCessna 182G · Glasgow, MTLoss of aircraft control resulting in an in-flight collision with terrain. Factors include marginal weather and dark night conditions.Jan 2, 2004 · N3171S · DestroyedNTSB CHI03FA251Accident · 1 fatalField investigationFinal reportCessna 182G · Topeka, KSThe pilot's failure to maintain adequate airspeed resulting in a stall during takeoff. Contributing factors were the low altitude he was at during the takeoff, and the trees.Aug 8, 2003 · N2064R · DestroyedNTSB LAX93LA376Accident · No injuriesLimited investigationFinal reportCessna 182G · Carson City, NV1) the pilot's failure to maintain an appropriate airspeed during an attempted go around, 2) his failure to retract the landing flaps, and 3) the resulting inadvertent entry into a stall/mush condition.Aug 30, 1993 · N2082R · Substantial damageNTSB SEA91LA133Accident · Minor injuriesLimited investigationFinal reportCessna 182G · Pleasant Grove, UTThe pilot's failure to maintian proper airspeed while on final approach.Jun 16, 1991 · N3705U · Substantial damageNTSB ANC87LA087Accident · Serious injuriesLimited investigationFinal reportCessna 182G · Chistochina, AKDuring a telephone interview the pilot stated the aircraft did not produce full power and believed the reason was the propeller setting was not set to high RPM before landing. The aircraft stalled on final approach to the airport and the aircraft impacted the…Jul 2, 1987 · N3403S · Substantial damageNTSB CHI87FA114Accident · 1 fatalField investigationFinal reportCessna 182G · West Point, INDrg an IFR arrival, the plt was clrd for an ILS rwy 10 apch. No radar facilities were available, but at 1026 EST, he rprtd he was established on the localizer. Aprx 4 min later, he declared a missed apch & was cleared back to the outer marker (om), then was…Apr 16, 1987 · N2382R · DestroyedNTSB LAX85LA234Accident · No injuriesLimited investigationFinal reportCessna 182 · Parker, AZThe pilot stated that he encountered shifting winds on landing at his destination airport and that turbulence was severe. There is no record of a weather briefing prior to departure.Apr 30, 1985 · N2444R · Substantial damage