NTSB investigations: Cessna 172N, 2003

32 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
NTSB investigations: Cessna 172N, 2003 per year, 1965–2026: 1,815 cases
19651
19662
19672
19751
19762
197726
197862
197981
1980107
198186
198291
198353
198455
198540
198644
198742
198847
198945
199046
199157
199240
199351
199443
199548
199637
199740
199837
199946
200035
200132
200243
200332
200438
200526
200623
200721
200821
200920
201023
201122
201214
201320
201415
201510
201624
201719
201814
201916
202025
202115
202216
202320
202413
202515
202611

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\") = 2003
    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 LAX04CA082Accident · No injuriesData collectionFinal reportCessna 172N · Angels Camp, CAthe CFI's inadequate compensation for a crosswind condition, which resulted in the loss of directional control. The crosswind and wind gusts were factors.Dec 29, 2003 · N461BD · Substantial damageNTSB LAX04LA062Accident · No injuriesLimited investigationFinal reportCessna 172N · Snelling, CAThe total loss of engine power due to oil starvation caused by the failure of the engine driven oil pump.Dec 8, 2003 · N739SU · Substantial damageNTSB LAX04LA056Accident · No injuriesLimited investigationFinal reportCessna 172N · Nogales, AZThe student pilot's improper recovery from a bounced landing and his failure to maintain directional control.Dec 4, 2003 · N5216J · Substantial damageNTSB FTW04LA026Accident · Minor injuriesLimited investigationFinal reportCessna 172N · La Grange, TXThe pilot's failure to properly navigate during the day VFR cross-country flight, which resulted in the pilot becoming disoriented.Nov 21, 2003 · N739YK · Substantial damageNTSB WAS04WA003Accident · No injuriesForeign investigationCessna 172N · Mannheim, GermanyNov 10, 2003 · N6473D · Substantial damageNTSB NYC04CA032Accident · Minor injuriesData collectionFinal reportCessna 172N · Philippi, WVThe pilot's improper decision to depart from a runway of insufficient length. Factors in the accident were the turf runway and tailwind condition.Nov 9, 2003 · N738UL · Substantial damageNTSB LAX04CA059Accident · No injuriesData collectionFinal reportCessna 172N · Winslow, AZthe pilot's misjudged landing flare, which resulted in a pilot induced porpoise oscillation and hard landing.Nov 9, 2003 · N75816 · Substantial damageNTSB LAX04CA024Accident · No injuriesData collectionFinal reportCessna 172N · Fresno, CAthe pilot's inadequate fuel management, which resulted in fuel starvation and a loss of engine power. Also causal was the pilot's failure to follow engine out emergency procedures as defined by the pilot operating handbook.Oct 25, 2003 · N738YL · Substantial damageNTSB MIA04FA007Accident · 1 fatalField investigationFinal reportCessna 172N · Olive Branch, MSThe student pilot's failure to maintain airspeed (Vso), which resulted in an inadvertent stall/spin, an uncontrolled descent, and an impact with terrain. A factor in the accident was his failure to follow the airplane's operating checklist and retract the…Oct 21, 2003 · N75510 · Substantial damageNTSB MIA04CA009Accident · No injuriesData collectionFinal reportCessna 172N · Melbourne, FLInadvertent full retraction of the flaps, while recovering from a bounced landing, resulting in an inadvertent stall, uncontrolled descent, and subsequent impact with terrain.Oct 21, 2003 · N734JT · Substantial damageNTSB MIA04CA005Accident · Minor injuriesData collectionFinal reportCessna 172N · Everglades City, FLThe pilot's improper preflight planning/preparation which resulted in the airplane's gust lock being left installed, which resulted in the airplane not being able lift off during the takeoff roll, and damage to the airplane when it overran the runway and…Oct 19, 2003 · N933JH · Substantial damageNTSB LAX03LA294Accident · No injuriesLimited investigationFinal reportCessna 172N · Pahrump, NVthe pilot's failure to maintain altitude/clearance from the mountainous terrain while maneuvering, which resulted in an in-flight collision with terrain.Sep 21, 2003 · N6548D · Substantial damageNTSB CHI03LA250Accident · No injuriesLimited investigationFinal reportCessna 172M · La Monte, MOThe pilot's misjudgment of speed and distance resulting in an overrun of the runway.Aug 4, 2003 · N73660 · Substantial damageNTSB LAX03CA247Accident · No injuriesData collectionFinal reportCessna 172N · Livermore, CAThe pilot's misjudged landing flare, which resulted in a porpoise pilot induced oscillation and hard landing.Jul 20, 2003 · N73857 · Substantial damageNTSB NYC03LA146Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Linden, NJThe mechanic's improper installation of the carburetor, and his failure to secure the mixture control wire to the mixture control arm pivot bolt.Jul 2, 2003 · N314TM · Substantial damageNTSB CHI03LA290Accident · No injuriesLimited investigationFinal reportCessna 172N · Romeo, MIThe pilot not maintaining directional control during landing. A factor to the accident was the parked airplane.Jun 27, 2003 · N739NW · Substantial damageNTSB MIA03FA124Accident · 5 fatalField investigationFinal reportCessna 172N · Deerfield Beach, FL**This case was revised 6/10/2005 and 2/24/2016. Refer to the public docket for this accident for details.** The failure of the pilot of N4903F, the Cessna 172, and the pilot of N759XA, the Cessna 182, to see and avoid each other while operating in Class E…Jun 17, 2003 · N4903F · 2 aircraft · DestroyedNTSB CHI03LA163Accident · No injuriesLimited investigationFinal reportCessna 172N · Anoka, MNThe pilot's failure to attain the proper touchdown point, and his failure to maintain directional control. Contributing factors were the pilot's lack of experience, and the runway sign.Jun 14, 2003 · N2238E · Substantial damageNTSB MIA03LA116Accident · No injuriesLimited investigationFinal reportCessna 172N · Clearwater, FLthe pilot's failure to maintain directional control during the takeoff roll, which resulted in the airplane departing the runway, and impacting with trees.Jun 1, 2003 · N9758G · Substantial damageNTSB ATL03LA100Accident · No injuriesLimited investigationFinal reportCessna 172N · Orangeburg, SCThe pilot's continued operation of the airplane with known deficiencies in the equipment. Also causal was the other maintenance personnel's improper installation of the mixture control linkage bolt that resulted in binding of the mixture control linkage and…May 30, 2003 · N734AG · DestroyedNTSB ATL03LA098Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Hampton, GAThe certified flight instructor's failure to maintain clearance from the runway during a low pass. A factor was gusty wind conditions.May 29, 2003 · N140PF · Substantial damageNTSB SEA03LA084Accident · No injuriesLimited investigationFinal reportCessna 172 N · Center Island, WAThe pilot did not attain the proper touchdown point during landing. The pilot's diverted attention, deer near the runway, and trees were factors.May 19, 2003 · N5326J · Substantial damageNTSB LAX03LA152Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Payson, AZthe pilot's inadequate recovery from a bounced landing, failure to retract the flaps during an aborted landing attempt, failure to maintain an adequate airspeed, and failure to maintain directional control. A factor in the accident was the high density…May 17, 2003 · N739NS · Substantial damageNTSB CHI03LA103Accident · No injuriesLimited investigationFinal reportCessna 172N · Carbondale, ILThe pilot failed to properly recover from a bounced landing which resulted in the airplane porpoising.Apr 11, 2003 · N6317D · Substantial damageNTSB MIA03LA098Accident · No injuriesLimited investigationFinal reportCessna 172N · Foxworth, MSThe failure of the pilot to perform a go-around, his failure to attain the proper touchdown point, and his delay in applying the normal brakes resulting in his inability to stop the airplane and subsequent on-ground collision with a fence.Apr 10, 2003 · N738QM · Substantial damageNTSB LAX03LA128Accident · No injuriesLimited investigationFinal reportCessna 172N · Anaheim, CAFailure of company maintenance personnel to correctly install and safety wire the oil drain plug, which led to a loss of engine oil and a catastrophic internal failure of the engine.Apr 5, 2003 · N6272D · Substantial damageNTSB CHI03FA086Accident · 3 fatalField investigationFinal reportCessna 172N · Foley, MNThe pilot's continued visual flight into instrument meteorological conditions which led to spatial disorientation and subsequent impact with the ground. Contributing factors was the pilot's lack of instrument rating, the pilot's disregard of the preflight…Mar 16, 2003 · N5315D · DestroyedNTSB NYC03LA062Accident · No injuriesLimited investigationFinal reportCessna 172N · Cincinnati, OHThe student pilot's failure to maintain directional control.Feb 26, 2003 · N733XP · Substantial damageNTSB LAX03FA100Accident · 2 fatalField investigationFinal reportCessna 172N · Ely, NVthe pilot's failure to maintain adequate terrain clearance while flying in a box canyon.Feb 23, 2003 · N9885J · Substantial damageNTSB CHI03FA071Accident · 1 fatalField investigationFinal reportCessna 172N · Wellington, KSSpatial disorientation experienced by the pilot and his subsequent failure to maintain control of the aircraft. Contributing factors were the pilot's failure to obtain an updated preflight weather briefing prior to the return flight, his attempted flight into…Feb 15, 2003 · N5898E · DestroyedNTSB SEA03LA036Accident · No injuriesLimited investigationFinal reportCessna 172N · McMinnville, ORThe pilot's inadequate compensation for wind conditions and his failure to maintain directional control during the landing roll. Factors include gusty crosswinds and soft terrain in the area where the aircraft departed the side of the runway.Feb 8, 2003 · N734KU · Substantial damageNTSB LAX03FA077Accident · 1 fatalField investigationFinal reportCessna 172N · Kalaupapa, HIthe student pilot's inadvertent VFR flight into IMC, which resulted in his in-flight collision with mountainous terrain while maneuvering. A contributing factor was the low ceiling weather condition.Jan 25, 2003 · N911FC · Destroyed