OpenAirDocs.org

NTSB investigations: Cessna 172S, 2003

29 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

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\") = 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 ('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 LAX04LA060Accident · No injuriesLimited investigationFinal reportCessna 172S · Watsonville, CAloss of engine power for undetermined reasons.Dec 7, 2003 · N396TA · Substantial damageNTSB LAX04LA054Accident · No injuriesLimited investigationFinal reportCessna 172S · Wikieup, AZThe pilot's selection of an en route altitude that did not provide adequate terrain clearance, and resulted in the in-flight collision with terrain. The rising terrain and the blind/box canyon were contributing factors.Nov 29, 2003 · N518ER · Substantial damageNTSB MIA04CA028Accident · No injuriesData collectionFinal reportCessna 172S · Orlando, FLThe student pilots improper landing flare and his improper recovery from a bounced landing resulting in a hard landing and damage to the airplane.Nov 21, 2003 · N378FA · Substantial damageNTSB CHI04LA024Accident · No injuriesLimited investigationFinal reportCessna 172S · Lakota, NDThe student pilot not maintaining directional control during takeoff roll on a solo instructional flight. The factor to the accident was the wind gusts.Nov 2, 2003 · N730SP · Substantial damageNTSB SEA04LA002Accident · No injuriesLimited investigationFinal reportCessna 172S · Seattle, WAImproper flare during the landing. Excessive airspeed and improper remedial action were factors.Oct 2, 2003 · N350ME · Substantial damageNTSB SEA03LA201Accident · No injuriesLimited investigationFinal reportCessna 172S · Anacortes, WAThe pilot attempting to taxi the airplane with a known system deficiency. Factors include worn wheel brakes and a drainage ditch.Sep 18, 2003 · N3555L · Substantial damageNTSB CHI03FA284Accident · 3 fatalField investigationFinal reportCessna 172S · Lake Elmo, MNBoth pilots failed to maintain adequate visual lookout and did not maintain clearance from the other aircraft.Aug 22, 2003 · N53033 · 2 aircraft · DestroyedNTSB IAD03CA071Accident · No injuriesData collectionFinal reportCessna 172 · Cleveland, OHThe pilot's improper flare, which resulted in a hard landing.Aug 19, 2003 · N229ME · Substantial damageNTSB MIA03CA158Accident · No injuriesData collectionFinal reportCessna 172S · Orlando, FLThe failure of the student pilot to maintain directional control of the airplane during takeoff roll resulting in the aircraft departing the runway and incurring substantial damage.Aug 7, 2003 · N775SP · Substantial damageNTSB MIA03CA148Accident · No injuriesData collectionFinal reportCessna 172S · Olive Branch, MSThe student pilot's improper landing flare/touchdown and inadequate recovery from a bounced landing which resulted in a hard landing and damage to the airplane.Jul 25, 2003 · N970SP · Substantial damageNTSB LAX03LA231Accident · No injuriesLimited investigationFinal reportCessna 172S · Chandler, AZThe pilot's misjudged landing flare, improper recovery from a bounced landing and failure to maintain directional control, resulting in a runway sign collision.Jul 12, 2003 · N5327G · Substantial damageNTSB LAX03CA248Accident · No injuriesData collectionFinal reportCessna 172S · Phoenix, AZThe student's misjudged landing flare and inadvertent entry into a porpoise pilot-induced oscillation.Jul 10, 2003 · N787WW · Substantial damageNTSB FTW03FA182Accident · 2 fatalField investigationFinal reportCessna 172S · McKinney, TXThe CFI's failure to maintain airspeed sufficient for flight resulting in an inadvertent stall/spin during the forced landing. A contributing factor was the impact with a bird, which affected the performance of the airplane.Jul 8, 2003 · N166ME · DestroyedNTSB MIA03CA125Accident · No injuriesData collectionFinal reportCessna 172S · Melbourne, FLThe pilot's improper flare and inadequate recovery from a bounced landing. Contributing factors were the pilot's failure to maintain directional control and his failure to execute a go-around.Jun 18, 2003 · N53352 · Substantial damageNTSB LAX03LA186Accident · No injuriesLimited investigationFinal reportCessna 172S · Prescott, AZThe student pilot's inadequate compensation for the wind conditions and failure to maintain directional control. Also causal was the flight instructor's inadequate supervision of the flight in allowing the student to perform a solo flight with a strong,…Jun 8, 2003 · N519ER · Substantial damageNTSB CHI03FA149Accident · 1 fatalField investigationFinal reportCessna 172S · Sidnaw, MIThe improper short/soft field landing procedure by the pilot and his lack of recent experience in type of operation. Contributing factors were the short/soft field runway, the trees and his delay in aborting the takeoff.Jun 6, 2003 · N975SP · DestroyedNTSB LAX03LA170Accident · No injuriesLimited investigationFinal reportCessna 172S · Kapolei, HIThe pilot's misjudged landing flare, and improper recovery from a bounced landing, which resulted in the collapse of the nose landing gear and structural damage to the airplane.May 29, 2003 · N5329L · Substantial damageNTSB LAX03LA151Accident · No injuriesLimited investigationFinal reportCessna 172S · Camarillo, CAthe student pilot's failure to maintain directional control, resulting in a collision with terrain. The flight instructor's inadequate supervision of the flight and delayed remedial action were also causal.May 15, 2003 · N585TM · Substantial damageNTSB MIA03LA096Accident · No injuriesLimited investigationFinal reportCessna 172S · Melbourne, FLThe student pilot's improper throttle setting during the braking test, resulting in a collision with a parked airplane.Apr 12, 2003 · N52903 · Substantial damageNTSB CHI03LA102Accident · No injuriesLimited investigationFinal reportCessna 172S · Grayslake, ILThe flight instuctor's improper in-flight decision to land with a tailwind and failure to maintain directional control of the airplane during landing. Factors contributing to the accident were the tailwind, the student pilot's inadequate flare, and the muddy…Apr 11, 2003 · N389SP · Substantial damageNTSB IAD03CA044Accident · No injuriesData collectionFinal reportCessna 172S · Cleveland, OHThe student pilot's improper flare, which resulted in a hard landing.Mar 27, 2003 · N613SP · Substantial damageNTSB ATL03FA064Accident · 2 fatalField investigationFinal reportCessna 172S · Monroe, GAThe pilot’s exceedence of the design limits of the airplane, which resulted in the overload failure of the horizontal stabilizers, followed by the overload separation of the right wing and subsequent loss of control.Mar 21, 2003 · N219ME · DestroyedNTSB LAX03LA091Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Scottsdale, AZthe student pilot's inadequate compensation for the existing crosswind conditions and failure to maintain directional control during the touch-and-go takeoff. A factor was his improper use of (failure to reduce) the throttle and normal brakes during the…Feb 21, 2003 · N3550X · Substantial damageNTSB NYC03LA048Accident · No injuriesLimited investigationFinal reportCessna 172SP · Flemington, NJThe manufacturer's improper assembly of the accessory drive section of the engine.Feb 19, 2003 · N197ME · Substantial damageNTSB CHI03LA073Accident · No injuriesLimited investigationFinal reportCessna 172 · Clare, MIThe student pilot failed to maintain directional control of the airplane during takeoff roll. A factor was the snow bank.Feb 14, 2003 · N693SA · Substantial damageNTSB SEA03LA037Accident · No injuriesLimited investigationFinal reportCessna 172S · Everett, WAThe pilot's failure to maintain adequate airspeed and the instructor's inadequate supervision of the flight. Contributing factors were the rime icing conditions, and the soft terrain encountered on the off runway rollout.Feb 9, 2003 · N912LB · Substantial damageNTSB CHI03LA061Accident · No injuriesLimited investigationFinal reportCessna 172 · Lakeville, MNThe pilot's inadequate removal of ice and snow during the airplane preflight, and the subsequent loss of control due to the airplane being covered with ice.Jan 31, 2003 · N670CS · Substantial damageNTSB ATL03LA034Accident · No injuriesLimited investigationFinal reportCessna 172S · Mt. Pleasant, SCThe student pilot's failure to maintain directional control during the takeoff roll, which resulted in a loss of control and collision with terrain.Jan 11, 2003 · N5199H · Substantial damageNTSB FTW03LA079Accident · No injuriesLimited investigationFinal reportCessna 172S · Springdale, ARThe pilot's failure to maintain directional control while landing. A contributing factor was the prevailing crosswind.Jan 8, 2003 · N142ME · Substantial damage