NTSB investigations: Cessna 172K, 2004

7 cases on aircraft the registry lists as Cessna 172K. 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

19672026
NTSB investigations: Cessna 172K, 2004 per year, 1967–2026: 691 cases
19671
19683
196929
197048
197166
197252
197343
197440
197521
197630
197729
197825
197915
198012
198113
198211
19836
19845
19857
19866
198712
19889
19895
19907
199111
19924
19937
199412
19956
199612
19975
19986
19996
200010
20015
20028
200310
20047
20054
20062
20078
20083
20091
20104
20116
20126
20135
20147
20152
20166
20171
20182
20198
20201
20213
20224
20234
20244
20254
20262

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\") = 2004
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072430'))
  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 ATL05LA031Accident · No injuriesLimited investigationFinal reportCessna 172K · Smyrna, TNThe pilot's inadequate preflight planning of fuel required for the flight, and his inadequate in-flight planning/decision which resulted in fuel exhaustion and the loss of engine power.Nov 29, 2004 · N78402 · Substantial damageNTSB ATL05CA002Accident · Serious injuriesData collectionFinal reportCessna 172K · Knoxville, TNThe pilot's failure to maintain airspeed on initial take off climb resulted in an inadvertent stall and an uncontrolled descent into the ground.Oct 9, 2004 · N78211 · No damageNTSB ANC04LA074Accident · No injuriesLimited investigationFinal reportCessna 172 · Yakutat, AKThe pilot's selection of an unsuitable landing area, which resulted in the collapse of the landing gear, and subsequent nose over during the landing roll. A factor associated with the accident was soft terrain.Jul 8, 2004 · N172JL · Substantial damageNTSB CHI04CA113Accident · Minor injuriesData collectionFinal reportCessna 172K · Harrisonville, MOThe dual student's failure to maintain directional control of the aircraft during the landing flare. Contributing factors were the dual student's failure to relinquish the controls to the flight instructor, the resulting inability of the flight instructor to…May 1, 2004 · N7448G · Substantial damageNTSB FTW04CA106Accident · No injuriesData collectionFinal reportCessna 172K · Bogalusa, LAThe loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.Apr 10, 2004 · N84623 · Substantial damageNTSB FTW04LA085Accident · No injuriesLimited investigationFinal reportCessna 172K · Angleton, TXThe unqualified person's failure to maintain clearance with the power lines. A contributing factor was the night light conditions.Feb 29, 2004 · N79502 · DestroyedNTSB LAX04FA096Accident · 2 fatalField investigationFinal reportCessna 172K · Grass Valley, CAthe pilot's continued visual flight into instrument meteorological conditions and failure to maintain an adequate terrain/object clearance altitude. Also causal was the pilot's improper in-flight decision to return to the origin airport in the face of…Jan 20, 2004 · N99LR · Destroyed