NTSB investigations: Cessna 182P, MD

10 cases on aircraft the registry lists as Cessna 182P. 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

19732026
NTSB investigations: Cessna 182P, MD per year, 1973–2026: 10 cases
19731
19761
19851
19951
19962
20001
20102
20151

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\" = 'MD' 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 ('2075816'))
  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 GAA15CA142Accident · No injuriesData collectionFinal reportCessna 182P · Westminster, MDThe flight instructor's delayed remedial action during the landing flare, which resulted in a hard landing and porpoise.Jun 13, 2015 · N1248S · Substantial damageNTSB ERA10LA375Accident · No injuriesLimited investigationFinal reportCessna 182 · Crisfield, MDThe pilot's delayed decision to abort the takeoff, which resulted in a runway excursion.Jul 17, 2010 · N777RM · Substantial damageNTSB ERA10TA197Accident · Minor injuriesFinal reportCessna 182P · Frederick, MDA loss of engine power for undetermined reasons following a reported severe turbulence encounter.Mar 30, 2010 · N52790 · Substantial damageNTSB NYC01LA060Accident · Minor injuriesLimited investigationFinal reportCessna 182P · Mitchellville, MDA loss of engine power for undetermined reasons.Dec 24, 2000 · N58833 · Substantial damageNTSB IAD97FA024Accident · Serious injuriesField investigationFinal reportCessna 182P · Fort Washington, MDLoss of engine power for undetermined reason(s).Nov 29, 1996 · N52773 · DestroyedNTSB IAD96LA101Accident · No injuriesLimited investigationFinal reportCessna 182P · White Marsh, MDThe pilot's improper flare which resulted in a hard landing. A related factor was the pilot's improperly planned approach.Jun 26, 1996 · N40007 · Substantial damageNTSB BFO95FA071Accident · 1 fatalField investigationFinal reportCessna 182P · Frederick, MDthe pilot's continued flight into known adverse weather during descent, which resulted in in-flight collision with terrain. Related factors were the pilot's disregard of a hazardous weather advisory, and the low ceilings, fog and drizzle.Jun 24, 1995 · N1284S · DestroyedNTSB BFO85FA026Accident · No injuriesField investigationFinal reportCessna 182P · Laurel, MDWhile on a return flight from morrisville,VT the acft lost pwr and the PIC elected to land in a cul-de-sac im a residential neighborhood. Investigation revealed that the acft contained less than 1 gallon of fuel. Both plts had dptd pxt 4 days prior and…Mar 11, 1985 · N52581 · Substantial damageNTSB IAD77FIA06Accident · Minor injuriesClosedCessna 182 · Friendly, MDDec 11, 1976 · N52581 · Substantial damageNTSB IAD73FIG22Accident · No injuriesClosedCessna 182P · Laurel, MDApr 11, 1973 · N79459 · Substantial damage