OpenAirDocs.org

NTSB investigations: Cessna 172N, 2004

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

19652026

Where

Open the map

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 ('2072434'))
  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 NYC05LA033Accident · 3 fatalLimited investigationFinal reportCessna 172N · Mount Gilead, OHThe pilot's failure to maintain control of the airplane following an inadvertent encounter with instrument meteorological conditions. A factor in the accident was the rapidly deteriorating weather.Dec 30, 2004 · N737AZ · Substantial damageNTSB CHI05CA034Accident · No injuriesData collectionFinal reportCessna 172N · Lakeville, MNThe pilot misjudged his distance and speed which resulted in an overrun.. Factors were the wet runway, the grass and the berm.Nov 20, 2004 · N737CR · Substantial damageNTSB ATL05CA024Accident · No injuriesData collectionFinal reportCessna 172N · Wilmington, NCThe student pilot's failure to recognize the proper emergency procedure, which resulted in a precautionary landing in a field and subsequent collision with a ditch. Factors were the undetermined electrical malfunction, smoke in the cockpit, and the student…Nov 14, 2004 · N75776 · Substantial damageNTSB MIA05LA037Accident · No injuriesLimited investigationFinal reportCessna 172N · Sanford, FLThe improper flare by the pilot in command resulting in a hard landing, Restricted movement of the throttle was a contributing factor.Nov 9, 2004 · N8077E · Substantial damageNTSB ATL05CA019Accident · Serious injuriesData collectionFinal reportCessna 172N · Columbia, SCThe pilot's inadequate preflight planning of fuel required for the flight, which resulted in fuel exhaustion and subsequent loss of engine power.Nov 3, 2004 · N4874G · Substantial damageNTSB NYC05FA001Accident · 2 fatalField investigationFinal reportCessna 172N · Germantown, NYThe pilot's inadequate in-flight planning/decision which led to VFR flight into IMC and his loss of aircraft control. Factors were night and cloud conditions.Oct 10, 2004 · N2771J · Substantial damageNTSB DEN05LA005Accident · No injuriesLimited investigationFinal reportCessna 172N · Casper, WYthe student pilot's improper flare resulting in a hard landing. A factor contributing to the accident was the student pilot's improper recovery from the bounced landing.Oct 7, 2004 · N73764 · Substantial damageNTSB CHI04LA248Accident · No injuriesLimited investigationFinal reportCessna 172 · Gary, INThe failure of the nose wheel for undetermined reasons. A factor associated with the accident was the student pilot's failure to properly flare the airplane.Sep 4, 2004 · N2355E · Substantial damageNTSB FTW04LA215Accident · No injuriesLimited investigationFinal reportCessna 172N · New Braunfels, TXThe student pilot's failure to maintain directional control of the airplane. A contributing factor was the high wind condition.Aug 18, 2004 · N739AM · Substantial damageNTSB NYC04CA189Accident · No injuriesData collectionFinal reportCessna 172P · Wilkes-Barre, PAThe student pilot's improper flare and improper recover from a bounced landing. Factors in this accident were the crosswind condition and the partial failure of the airplane's transceiver, as reported by the pilot.Aug 8, 2004 · N4599D · Substantial damageNTSB FTW04CA205Accident · No injuriesData collectionFinal reportCessna 172N · Cleveland, TXThe student pilot's improper judgment of the airplanes altitude during landing. A contributing factor was the pilot's level of anxiety/apprehension after becoming lost/disoriented.Aug 4, 2004 · N4865G · Substantial damageNTSB DEN04LA114Accident · No injuriesLimited investigationFinal reportCessna 172N · Hurricane, UTthe student pilot's failure to maintain aircraft control during the landing. Contributing factors include the crosswind, the wind gusts, and the exceeded maximum demonstrated crosswind component.Jul 31, 2004 · N5426J · Substantial damageNTSB NYC04LA169Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Erwinna, PAThe student pilot's failure to maintain airspeed and his failure to follow the go-around procedure which resulted in a stall.Jul 17, 2004 · N262MC · Substantial damageNTSB ATL04CA162Accident · No injuriesData collectionFinal reportCessna 172 · Chamblee, GAThe pilot's improper landing flare that resulted in a hard landing. A factor was a tailwind condition.Jul 11, 2004 · N6555D · Substantial damageNTSB LAX04CA255Accident · Minor injuriesData collectionFinal reportCessna 172N · Chemehuevi, CAthe pilot's improper recovery from a bounced landing, inadequate compensation for the wind conditions, and his failure to maintain directional control of the airplane.Jul 7, 2004 · N734PW · Substantial damageNTSB DEN04CA099Accident · No injuriesData collectionFinal reportCessna 172N · Laramie, WYfuel exhaustion due to the pilot's improper inflight decision not to stop and refuel. A contributing factor was the unsuitable terrain on which to make a forced landing.Jul 5, 2004 · N737YJ · Substantial damageNTSB IAD04LA034Accident · No injuriesLimited investigationFinal reportCessna 172N · Wellsboro, PAThe pilot's inadequate compensation for wind conditions and his failure to maintain directional control. A factor was the crosswind.Jul 4, 2004 · N10DJ · Substantial damageNTSB ATL04CA129Accident · No injuriesData collectionFinal reportCessna 172N · Dover, TNThe certified flight instructor initiated flight into thunderstorm activity that resulted in a loss of control and the subsequent collision with trees.Jun 12, 2004 · N5153E · Substantial damageNTSB CHI04CA152Accident · No injuriesData collectionFinal reportCessna 172N · Hillsboro, NDDirectional control not obtained/maintained by the pilot during landing roll.Jun 10, 2004 · N737SV · Substantial damageNTSB NYC04CA134Accident · Serious injuriesData collectionFinal reportCessna 172M · Worcester, MAThe pilot's improper recovery from a bounced landing, and his inadequate compensation for wind conditions. A factor in the accident was the gusting wind.May 29, 2004 · N73704 · Substantial damageNTSB FTW04LA138Accident · No injuriesLimited investigationFinal reportCessna 172 · Decatur, TXThe student pilot's failure to follow the flight instructor's instructions and relinquish the controls, and the flight instructor's delay in initiating a go-around.May 24, 2004 · N5302E · Substantial damageNTSB MIA04CA085Accident · No injuriesData collectionFinal reportCessna 172N · Pembroke Pines, FLThe pilot's failure to establish a climb and his failure to maintain directional control of the airplane during an aborted landing leading to the airplane departing the runway and incurring substantial damage.May 17, 2004 · N737FE · Substantial damageNTSB ATL04CA113Accident · No injuriesData collectionFinal reportCessna 172N · Odessa, FLThe pilot's improper landing flare that resulted in a hard landing.May 4, 2004 · N737HW · Substantial damageNTSB LAX04CA196Accident · No injuriesData collectionFinal reportCessna 172N · Lincoln, CAthe pilot's failure to maintain obstacle clearance.Apr 25, 2004 · N734RE · Substantial damageNTSB DEN04CA067Accident · No injuriesData collectionFinal reportCessna 172N · Lyons, COa loss of engine power due to carburetor icing. Contributing factors were weather conditions conducive to carburetor icing and unsuitable terrain available on which to make a forced landing and the road sign.Apr 24, 2004 · N5048E · Substantial damageNTSB ATL04FA099Accident · 3 fatalField investigationFinal reportCessna 172N · Moselle, MSThe pilot's failure to maintain clearance and his inadequate visual look-out while maneuvering resulting in an in-flight collision with a radio tower.Apr 24, 2004 · N75812 · Substantial damageNTSB NYC04CA104Accident · No injuriesData collectionFinal reportCessna 172N · Bridgeport, CTThe pilot's inadequate compensation for wind conditions and his failure to maintain aircraft control which resulted in a hard landing. A factor was the gusty winds.Apr 10, 2004 · N6583D · Substantial damageNTSB ATL04CA089Accident · No injuriesData collectionFinal reportCessna 172N · Statesboro, GAThe pilot's failure to establish a positive climb and his failure to maintain clearance during a go-around, which resulted in an in-flight collision with trees. A factor was the gusting winds.Apr 3, 2004 · N4874G · Substantial damageNTSB ATL04LA088Accident · No injuriesLimited investigationFinal reportCessna 172N · Columbia, SCThe pilot's inadequate in-flight planning/decision, which resulted in fuel exhaustion. The pilot's preflight planning and uneven terrain were contributing factors.Apr 2, 2004 · N271EP · Substantial damageNTSB SEA04LA052Accident · No injuriesLimited investigationFinal reportCessna 172N · Creswell, ORThe pilot's attempting takeoff with the fuel selector in the OFF position resulting in fuel starvation. Contributing factors were the change in habit pattern and expectancy of the fuel selector position as well as the fence and tree.Mar 21, 2004 · N739HQ · Substantial damageNTSB ATL04LA082Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Knoxville, TNThe CFI's inadequate in-flight planning/decision and his inadequate supervision which resulted in fuel exhaustion. A factor was the inadequate preflight planning/preparation to ensure an adequate fuel supply, and the berm.Mar 10, 2004 · N6257F · Substantial damageNTSB SEA04LA048Accident · No injuriesLimited investigationFinal reportCessna 172N · Gig Harbor, WAThe pilot's failure to follow the published IFR procedure resulting in failure to maintain clearance from objects during an instrument approach. Trees and an inoperative glide slope receiver were factors.Mar 3, 2004 · N75844 · Substantial damageNTSB NYC04CA076Accident · No injuriesData collectionFinal reportCessna 172N · Youngstown, OHAn inadvertent collision with a deer while landing.Feb 23, 2004 · N738EK · Substantial damageNTSB LAX04LA124Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Upland, CAA partial loss of engine power for undetermined reasons during takeoff.Feb 13, 2004 · N5107K · Substantial damageNTSB DEN04LA045Accident · No injuriesLimited investigationFinal reportCessna 172N · Parowan, UTthe pilot's in-flight decision/planning which resulted in fuel exhaustion. The fence and night conditions were contributing factors.Feb 13, 2004 · N9892J · Substantial damageNTSB NYC04CA073Accident · No injuriesData collectionFinal reportCessna 172N · Easton, MDThe student pilot's improper flare, which resulted in a hard landing.Feb 12, 2004 · N734AT · Substantial damageNTSB CHI04CA067Accident · No injuriesData collectionFinal reportCessna 172N · Cahokia, ILThe inadequate supervision by the certified flight instructor which lead to the student pilot's failure to maintain clearance from the snowbank during the landing. The snowbank was a factor.Feb 7, 2004 · N738EJ · Substantial damageNTSB SEA04LA038Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Rigby, IDThe flight instructor's failure to follow procedures, i.e., operating the non-icing certified aircraft in known icing conditions contrary to the pilot operators handbook which resulted in ice accretion and ultimately a stall and loss of control in flight.…Jan 28, 2004 · N734CB · Substantial damage