NTSB investigations: Cessna 172P, 2005

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

19692026
NTSB investigations: Cessna 172P, 2005 per year, 1969–2026: 843 cases
19691
19731
19802
19819
198230
198334
198436
198532
198624
198742
198839
198927
199028
199139
199236
199326
199422
199519
199624
199725
199819
199924
200021
200116
200216
200325
200418
200517
20069
200710
200813
20099
201016
201114
201212
20136
20146
201512
20169
20177
201810
20194
20205
20217
202210
20237
20249
20257
20269

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\") = 2005
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072436'))
  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 ATL06CA047Accident · No injuriesData collectionFinal reportCessna 172 P · Wilmington, NCThe student pilot's improper landing flare which resulted in a hard landing.Dec 27, 2005 · N54360 · Substantial damageNTSB MIA06CA032Accident · No injuriesData collectionFinal reportCessna 172P · Hialeah, FLThe failure of the CFI to perform a go-around following a long landing resulting in overrun, on ground encounter with soft terrain, and subsequent nose over.Dec 16, 2005 · N51434 · Substantial damageNTSB DFW06CA008Accident · Minor injuriesData collectionFinal reportCessna 172P · Hitchcock, TXA loss of engine power due to a cracked cylinder.Oct 17, 2005 · N53795 · Substantial damageNTSB MIA06FA007Accident · 1 fatalField investigationFinal reportCessna 172P · La Belle, FLThe student pilot's failure to maintain airspeed during the initial takeoff climb, resulting in an inadvertent stall/spin and uncontrolled descent to ground impact. A contributing factor was the failure of the wing flap control, which resulted in the flaps…Oct 16, 2005 · N99173 · Substantial damageNTSB NYC05CA146Accident · No injuriesData collectionFinal reportCessna 172P · Mitchellville, MDThe pilot's failure to maintain directional control during landing.Sep 23, 2005 · N99137 · Substantial damageNTSB NYC05CA143Accident · No injuriesData collectionFinal reportCessna 172P · Caldwell, NJThe student pilot's failure to maintain directional control while landing. A factor in this accident was the crosswind condition.Sep 19, 2005 · N64763 · Substantial damageNTSB NYC05LA125Accident · No injuriesLimited investigationFinal reportCessna 172P · Caldwell, NJThe pilot's improper flare, which resulted in a hard landing. A factor was a partial loss of engine power, as reported by the pilot, for undetermined reasons.Jul 28, 2005 · N98730 · Substantial damageNTSB CHI05FA194Accident · 1 fatalField investigationFinal reportCessna 172P · Jackson, WIThe pilot not maintaining aircraft control for undetermined reasons while maneuvering.Jul 20, 2005 · N65875 · DestroyedNTSB ATL05CA132Accident · No injuriesData collectionFinal reportCessna 172P · Savannah, GAThe pilot's failure to maintain directional control on landing roll out resulting in a ground loop, and on ground collision of the right wing with the ground.Jul 18, 2005 · N5299K · Substantial damageNTSB ATL05CA125Accident · No injuriesData collectionFinal reportCessna 172P · Monroeville, ALThe student pilot's failure to maintain directional control and the subsequent collision with the ground during landing.Jul 7, 2005 · N98530 · Substantial damageNTSB CHI05CA150Accident · No injuriesData collectionFinal reportCessna 172P · St. Francis, KSThe pilot's failure to compensate for the crosswind conditions during landing and the unsuccessful go-around. A factor was the crosswind.Jun 19, 2005 · N53462 · Substantial damageNTSB NYC05LA123Accident · No injuriesLimited investigationFinal reportCessna 172P · Islip, NYThe pilot's failure to maintain clearance from a parked vehicle while taxiing.May 17, 2005 · N9344L · Substantial damageNTSB NYC05CA082Accident · No injuriesData collectionFinal reportCessna 172P · Caldwell, NJThe student pilot's improper flare and recovery from a bounced landing.May 11, 2005 · N64815 · Substantial damageNTSB CHI05CA095Accident · No injuriesData collectionFinal reportCessna 172P · Ann Arbor, MIThe failure of the carburetor nozzle resulting in loss of engine power and the unsuitable terrain encountered during the forced landing. A factor was the low altitude.Apr 8, 2005 · N777UM · Substantial damageNTSB ATL05CA062Accident · Minor injuriesData collectionFinal reportCessna 172P · Redstone Arsnl, ALThe pilot's failure to maintain adequate airspeed during approach, which resulted in an inadvertent stall and subsequent collision with the runway. Factors were the turbulence and crosswind conditions.Mar 12, 2005 · N5456K · DestroyedNTSB MIA05CA061Accident · No injuriesData collectionFinal reportCessna 172 · Brooksville, FLThe pilot's improper landing flare which resulted in substantial damage during the subsequent hard landing.Feb 21, 2005 · N98636 · Substantial damageNTSB IAD05CA037Accident · No injuriesData collectionFinal reportCessna 172P · Cross Keys, NJThe pilots failure to maintain directional control. Factors contributing to the accident were the pilots lack of experience, and the snow bank.Feb 7, 2005 · N54812 · Substantial damage