NTSB investigations: Cessna 182P, 2002

7 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

19722026
NTSB investigations: Cessna 182P, 2002 per year, 1972–2026: 700 cases
197213
197323
197424
197529
197640
197736
197842
197931
198020
198119
198225
198322
198413
198517
198614
19877
19888
198910
199013
19918
19928
199311
199420
19958
199615
199713
199810
19997
20009
200113
20027
20038
200413
20057
20065
200713
20083
20099
201010
20119
20128
20136
20143
20154
20167
20177
20188
20196
20207
20214
20226
20232
20246
20259
20265

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\") = 2002
    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 IAD03LA014Accident · No injuriesLimited investigationFinal reportCessna 182P · Lincoln Park, NJThe student pilot's improper power management during the short-field landing procedure, and the flight instructor's delayed remedial action.Nov 12, 2002 · N1835M · Substantial damageNTSB FTW02LA255Accident · No injuriesLimited investigationFinal reportCessna 182P · Kirbyville, TXThe pilot's physical impairment due to a previous head injury which resulted in his becoming disoriented. A contributing factor was the lack of suitable terrain for the precautionary landing.Sep 5, 2002 · N41CW · Substantial damageNTSB SEA02LA144Accident · No injuriesLimited investigationFinal reportCessna 182P · Cascade, IDThe pilot's inadequate decision and his improper setting of the propeller controls. Contributing factors were a tailwind, high density altitude, and swampy terrain.Aug 4, 2002 · N58818 · Substantial damageNTSB LAX02LA244Accident · No injuriesLimited investigationFinal reportCessna 182P · Mokelumne Hill, CAThe pilot's failure to maintain the proper glidepath and failure to follow the manufacturer's recommended flap setting of 40 degrees, which resulted in an undershoot short of the runway. Factors include the runway's upslope and short length, which likely…Aug 2, 2002 · N8290G · Substantial damageNTSB LAX02LA181Accident · No injuriesLimited investigationFinal reportCessna 182P · Roosevelt, AZFailure of the pilot to maintain aircraft control during the landing rollout after making a precautionary landing precipitated by an electrical system failure.May 30, 2002 · N79107 · Substantial damageNTSB LAX02FA179Accident · 1 fatalField investigationFinal reportCessna 182P · Pleasanton, CAThe pilot's inadvertent flight into adverse weather and his failure to maintain clearance. Contributing factors included the pilot's inadequate preflight planning, the low ceilings, and the dark night conditions.May 28, 2002 · N52404 · DestroyedNTSB LAX02LA152Accident · No injuriesLimited investigationFinal reportCessna 182P · Boulder City, NVthe pilot's failure to lean the mixture properly resulting in a partial loss of power.May 7, 2002 · N425Q · Substantial damage