Cessna 172S
NTSB investigations · 589
Matched to the registry by N-number and event date, newest first.
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.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.
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.aircraft_model_code IN ('2072439', '2072442')
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB LAX04CA186Accident · No injuriesData collectionFinal reportCessna 172S · Long Beach, CAthe student pilot's inadequate flare, which resulted in a hard landing and porpoise.NTSB DEN04LA053Accident · No injuriesLimited investigationFinal reportCessna C172 · Broomfield, COthe pilot of the Maule's failure to maintain a visual lookout.NTSB LAX04CA130Accident · No injuriesData collectionFinal reportCessna 172S · Riverside, CAthe pilot's inadequate visual lookout, which resulted in his failure to maintain proper alignment with the taxiway. Factors in the accident were the dusk lighting conditions and pilot not understanding the ground control taxi clearance.NTSB FTW04LA072Accident · No injuriesLimited investigationFinal reportCessna 172-SP · McKinney, TXThe student pilot's failure to maintain directional control of the aircraft during the take-off roll.NTSB LAX04LA060Accident · No injuriesLimited investigationFinal reportCessna 172S · Watsonville, CAloss of engine power for undetermined reasons.NTSB 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.NTSB 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.NTSB 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.NTSB SEA04LA002Accident · No injuriesLimited investigationFinal reportCessna 172S · Seattle, WAImproper flare during the landing. Excessive airspeed and improper remedial action were factors.NTSB 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.NTSB 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.NTSB IAD03CA071Accident · No injuriesData collectionFinal reportCessna 172 · Cleveland, OHThe pilot's improper flare, which resulted in a hard landing.NTSB 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.NTSB 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.NTSB 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.NTSB LAX03CA248Accident · No injuriesData collectionFinal reportCessna 172S · Phoenix, AZThe student's misjudged landing flare and inadvertent entry into a porpoise pilot-induced oscillation.NTSB 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.NTSB 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.NTSB 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,…NTSB 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.NTSB 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.NTSB 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.NTSB 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.NTSB 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…NTSB IAD03CA044Accident · No injuriesData collectionFinal reportCessna 172S · Cleveland, OHThe student pilot's improper flare, which resulted in a hard landing.NTSB 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.NTSB 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…NTSB NYC03LA048Accident · No injuriesLimited investigationFinal reportCessna 172SP · Flemington, NJThe manufacturer's improper assembly of the accessory drive section of the engine.NTSB 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.NTSB 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.NTSB 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.NTSB 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.NTSB FTW03LA079Accident · No injuriesLimited investigationFinal reportCessna 172S · Springdale, ARThe pilot's failure to maintain directional control while landing. A contributing factor was the prevailing crosswind.NTSB NYC03LA032Accident · No injuriesLimited investigationFinal reportCessna 172S · Akron, OHThe pilot's improper flare which resulted in a hard landing.NTSB CHI03LA075Accident · No injuriesLimited investigationFinal reportCessna 172S · Tea, SDThe student pilot's improper flare. The pilot's lack of experience and diverted attention were factors.NTSB CHI03LA015Accident · No injuriesLimited investigationFinal reportCessna 172 · St. Paul, MNThe student pilot failed to maintain directional control. A factor was the runway sign.NTSB SEA02FA185Accident · 2 fatalField investigationFinal reportCessna 172S · Medford, ORTerrain clearance was not maintained during cruise flight. Dark night and mountainous terrain were factors.NTSB CHI02LA291Accident · No injuriesLimited investigationFinal reportCessna 172S · Boyne Falls, MIThe pilot's improper flare during landing.NTSB ATL02LA166Accident · No injuriesLimited investigationFinal reportCessna 172S · Immokalee, FLThe student pilot's improper flare at touchdown resulted in a hard landing while performing an off-airport precautionary landing after the inadvertent activation of the autopilot.NTSB IAD02FA086Accident · 2 fatalField investigationFinal reportCessna 172S · Plainville, CTAn in-flight engine compartment fire of unknown origin, and a loss of engine power for undetermined reasons. Also causal, was the pilot's failure to maintain airspeed during a turn back to the airfield, which resulted in an inadvertent stall and subsequent…NTSB FTW02LA224Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Marietta, OKThe pilot's failure to maintain adequate airspeed which resulted in a stall.NTSB DEN02LA088Accident · No injuriesLimited investigationFinal reportCessna 172S · Englewood, COthe instructor's inadequate supervision of the flight and his premature raising of the flaps, resulting in a hard landing.NTSB MIA02GA137Accident · 3 fatalFinal reportCessna 172S · Tyner, NCThe loss of power for undetermined reasons, and the pilot's failure to maintain airspeed.NTSB MIA02LA112Accident · No injuriesLimited investigationFinal reportCessna 172S · Kill Devil Hill, NCthe pilot's failure to maintain control of the airplane after an attempted aborted landing, and while braking during the landing roll, which resulted in the airplane departing the end of the runway and impacting with a ditch.NTSB LAX02LA192Accident · Minor injuriesLimited investigationFinal reportCessna 172S · Goldfield, NVThe pilot's failure to maintain control of the airplane during a high density altitude takeoff. Contributing factors were the pilot's lack of experience in the type of operation and a wind gust.NTSB LAX02LA184Accident · No injuriesLimited investigationFinal reportCessna 172S · Monterey, CAThe pilot was unfamiliar with the airplane's systems and failed to set the elevator trim in accordance with the published checklist.NTSB MIA02FA104Accident · 1 fatalField investigationFinal reportCessna 172S · Lutz, FLThe suicidal act by the pilot resulting in the in-flight collision with trees then the ground. A contributing factor in the accident was the pilot's depression. Findings in the investigation were the pilot's overdose of zolpidem and citalopram before the…NTSB LAX02LA167Accident · No injuriesLimited investigationFinal reportCessna 172S · Scottsdale, AZthe student pilot's improper recovery from a bounced landing and failure to maintain directional control on the landing roll, which resulted in a collision with a runway sign.NTSB MIA02LA091Accident · No injuriesLimited investigationFinal reportCessna 172S · Daytona Beach, FLthe pilot misjudged the landing flare, resulting in a hard landing, and damage to the airplane.NTSB FTW02LA115Accident · No injuriesLimited investigationFinal reportCessna 172S · Angel Fire, NMThe pilots failure to maintain directional control during the crosswind landing. A contributing factor was the gusting wind condition.
Back to Cessna 172S