NTSB investigations: Cessna 172S, 2009

22 cases on aircraft the registry lists as Cessna 172S. 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 172S, 2009 per year, 1967–2026: 586 cases
19672
19701
19721
19793
19871
19992
20004
200120
200222
200329
200427
200528
200625
200726
200831
200922
201027
201120
201229
201324
201418
201518
201629
201724
201822
201923
202018
202122
20229
202313
202414
202518
202614

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\") = 2009
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072439', '2072442'))
  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 ERA10FA091Accident · 4 fatalField investigationFinal reportCessna 172S · Kissimmee, FLThe pilot's decision to depart under special VFR flight at night when instrument meteorological conditions prevailed at the departure airport and along the route of flight and his continued VFR flight into instrument meteorological conditions, which resulted…Dec 8, 2009 · N5269X · DestroyedNTSB CEN10CA062Accident · No injuriesData collectionFinal reportCessna 172S · Mt. Comfort, INThe pilot's failure to maintain directional control of the airplane while touching down during the landing.Dec 2, 2009 · N6036Y · Substantial damageNTSB ERA10CA057Accident · No injuriesData collectionFinal reportCessna 172S · Summit, DEThe student pilot’s failure to maintain directional control during takeoff.Nov 7, 2009 · N134B · Substantial damageNTSB ERA10FA048Accident · 2 fatalField investigationFinal reportCessna 172S · Tallahassee, FLThe pilots' spatial disorientation during flight in dark conditions, which resulted in an uncontrolled descent into terrain.Nov 5, 2009 · N5194X · DestroyedNTSB CEN10CA025Accident · No injuriesData collectionFinal reportCessna 172S · Grand Forks, NDThe student pilot's improper landing flare and recovery from a bounced landing.Oct 20, 2009 · N519ND · Substantial damageNTSB WPR10CA019Accident · Minor injuriesData collectionFinal reportCessna 172S · Honolulu, HIThe student pilot's distraction and subsequent loss of airplane control after the cabin window opened during the takeoff roll.Oct 17, 2009 · N5329L · Substantial damageNTSB ERA10CA008Accident · No injuriesData collectionFinal reportCessna 172S · Easton, PAThe pilot’s failure to maintain adequate clearance from terrain while on short final.Oct 6, 2009 · N66087 · Substantial damageNTSB WPR09CA461Accident · No injuriesData collectionFinal reportCessna 172S · San Carlos, CAThe student pilot's failure to maintain clearance with a fence post during taxi.Sep 21, 2009 · N21591 · Substantial damageNTSB CEN09LA579Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Park Rapids, MNThe pilot's failure to maintain a proper climb rate during a night takeoff.Sep 13, 2009 · N523ND · Substantial damageNTSB CEN09LA586Accident · No injuriesLimited investigationFinal reportCessna 172S · Duluth, MNThe pilot's failure to maintain aircraft control during landing, resulting in a hard landing and a propeller strike with the ground.Sep 7, 2009 · N568ND · Substantial damageNTSB CEN09CA530Accident · No injuriesData collectionFinal reportCessna 172 · Centennial, COThe pilot's failure to maintain directional control of the airplane during the landing flare in crosswind conditions.Aug 16, 2009 · N22265 · Substantial damageNTSB CEN09CA509Accident · No injuriesData collectionFinal reportCessna 172S · Bluffton, OHThe student pilot's failure to compensate for wind conditions and maintain aircraft control during the landing.Aug 6, 2009 · N6186T · Substantial damageNTSB CEN09CA495Accident · No injuriesData collectionFinal reportCessna 172S · New Braunfels, TXThe student pilot's improper flare resulting in a bounced landing.Aug 4, 2009 · N401LP · Substantial damageNTSB CEN09LA442Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Boyd, TXA total loss of engine power due to the pilot's improper leaning procedures, resulting in a forced landing and collision with a fence.Jul 14, 2009 · N2446F · Substantial damageNTSB CEN09CA404Accident · No injuriesData collectionFinal reportCessna 172S · Grand Forks, NDThe student pilot's improper landing flare that resulted in a hard landing.Jul 2, 2009 · N538ND · Substantial damageNTSB CEN09CA402Accident · No injuriesData collectionFinal reportCessna 172S · Grand Forks, NDThe student pilot's improper landing flare and recovery from a bounced landing.Jul 2, 2009 · N525ND · Substantial damageNTSB WPR09CA275Accident · No injuriesData collectionFinal reportCessna 172S · Tooele, UTThe pilot's failure to maintain directional control during landing.Jun 2, 2009 · N5262Y · Substantial damageNTSB ERA09CA404Accident · No injuriesData collectionFinal reportCessna 172 · York, PAThe student pilot's improper recovery from a bounced landing.Apr 13, 2009 · N144ME · Substantial damageNTSB CEN09LA182Accident · No injuriesLimited investigationFinal reportCessna 172N · Johnson County Exec Airport, KSFailure of the pilot of the Cessna 172S to ensure the taxiway was clear prior to initiating the turn. Contributing to the accident was the failure of the pilot of the Cessna 172N to obtain taxi clearance prior to entering the movement area.Feb 25, 2009 · N734WD · 2 aircraft · Substantial damageNTSB CEN09CA148Accident · No injuriesData collectionFinal reportCessna 172 · Union Mills, INThe certificated flight instructor's failure to follow correct engine clearing procedures. A factor was the unsuitable landing area.Feb 1, 2009 · N53576 · Substantial damageNTSB WPR09LA098Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Oceanside, CAA defective alternator wire splice that resulted in an intermittent electrical system malfunction and erroneous fuel gauge readings, and, a loss of engine power for an undetermined reason.Jan 24, 2009 · N562AD · Substantial damageNTSB ERA09CA119Accident · No injuriesData collectionFinal reportCessna 172SP · Lancaster, NYThe student pilot's failure to maintain directional control during takeoff. Contributing to the accident was the student pilot's lack of solo flight experience and the snow bank located off the left side of the runway.Jan 1, 2009 · N2228L · Substantial damage