NTSB investigations: Cessna 172M, 2007

16 cases on aircraft the registry lists as Cessna 172M. 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 172M, 2007 per year, 1972–2026: 1,698 cases
19723
197324
197459
197582
1976104
197799
197892
197980
198059
198150
198253
198334
198435
198534
198638
198729
198828
198938
199037
199136
199231
199337
199424
199529
199623
199735
199830
199922
200022
200130
200226
200324
200418
200516
200618
200716
200824
200914
201015
201113
201218
201320
201420
20159
201610
201719
201814
201913
202016
20218
202224
202312
202414
202512
20268

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\") = 2007
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072418'))
  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 DFW08CA051Accident · No injuriesData collectionFinal reportCessna 172 · Houston, TXThe pilot's failure to maintain aircraft control. A contributing factor was prevailing crosswind.Dec 28, 2007 · N1458U · Substantial damageNTSB CHI08CA030Accident · No injuriesData collectionFinal reportCessna 172M · Duluth, MNThe pilot's inadequate compensation for wind conditions during the landing approach. Contributing to the accident was the crosswind weather condition.Oct 28, 2007 · N4366R · Substantial damageNTSB ANC08LA007Accident · No injuriesLimited investigationFinal reportCessna 172M · Rangeley, METhe pilot's failure to maintain aircraft control during the landing flare/touchdown. A factor contributing to the accident was the pilot's diverted attention.Oct 18, 2007 · N92737 · Substantial damageNTSB CHI07CA296Accident · Minor injuriesData collectionFinal reportCessna 172 Skyhawk · Stockton, MOThe pilot's improper recovery from a bounced landing, her subsequent loss of control of the airplane, and the inadvertent stall.Sep 11, 2007 · N12189 · Substantial damageNTSB ATL07FA125Accident · 2 fatalField investigationFinal reportCessna 172M · Mansfield, MAThe pilot's improper use of wing flaps during takeoff, which resulted in reduced climb performance and a subsequent stall. Contributing to the accident was the exceedance of the airplane's maximum gross weight.Sep 8, 2007 · N19952 · Substantial damageNTSB SEA07LA251Accident · No injuriesLimited investigationFinal reportCessna 172M · Thompson, UTThe pilot's failure to maintain terrain clearance while maneuvering in a box canyon.Sep 5, 2007 · N8945V · Substantial damageNTSB CHI07CA294Accident · No injuriesData collectionFinal reportCessna 172M · Pontiac, MIThe pilot's misjudgment of the landing flare and her improper recovery from the bounced landing.Sep 5, 2007 · N73455 · Substantial damageNTSB CHI07LA288Accident · 1 fatalLimited investigationFinal reportCessna 172M · Union Star, MOThe student pilot's failure to maintain adequate airspeed and the subsequent inadvertent stall while buzzing residences. Contributing to the accident was the pilot performing buzzing maneuvers.Sep 2, 2007 · N1502V · DestroyedNTSB CHI07LA266Accident · No injuriesLimited investigationFinal reportCessna 172M · Marine City, MIA loss of engine power for undetermined reasons. Factors contributing to the accident were the insufficient runway remaining and the soft terrain.Aug 11, 2007 · N13586 · Substantial damageNTSB DFW07CA163Accident · No injuriesData collectionFinal reportCessna 172M · Throckmorton, TXThe pilot's failure to maintain clearance from power transmission lines. A contributing factor was the prevailing dusk illumination.Jul 16, 2007 · N13441 · Substantial damageNTSB CHI07LA177Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Rio Creek, WIThe pilot's improper aircraft weight and balance, and his failure to maintain sufficient airspeed to avoid a stall during takeoff-initial climb.Jun 24, 2007 · N4422R · Substantial damageNTSB LAX07CA169Accident · No injuriesData collectionFinal reportCessna 172M · St. George, UTthe pilot's inadequate compensation for a gusting crosswind and his failure to maintain directional control.May 12, 2007 · N5285H · Substantial damageNTSB MIA07CA095Accident · Minor injuriesData collectionFinal reportCessna 172-M · Oxford, METhe student pilot's failure to maintain a climb during a go-around resulting in collision with an embankment.May 8, 2007 · N80132 · Substantial damageNTSB NYC07CA111Accident · Minor injuriesData collectionFinal reportCessna 172S · Montgomery, NYThe pilot's improper flare while landing, which resulted in a loss of directional control and collision with terrain.May 5, 2007 · N12152 · Substantial damageNTSB SEA07CA116Accident · No injuriesData collectionFinal reportCessna 172M · Astoria, ORThe student pilot's failure to adequately correct for changing wind conditions, leading to a loss of directional control during the takeoff ground roll. Factors include wet, soft terrain along the side of the runway.Apr 29, 2007 · N1911V · Substantial damageNTSB LAX07CA125Accident · Minor injuriesData collectionFinal reportCessna 172M · Stockton, CAThe loss of engine power due to fuel exhaustion resulting from the pilot's inaccurate fuel consumption calculations and failure to refuel while en route.Apr 12, 2007 · N9685Q · Substantial damage