NTSB investigations: Cessna 172S
47 cases on aircraft the registry lists as Cessna 172S, where the first occurrence was “Loss of control - on ground/water”. 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
| 1999 | 1 |
|---|---|
| 2001 | 3 |
| 2002 | 4 |
| 2003 | 10 |
| 2004 | 5 |
| 2005 | 4 |
| 2006 | 9 |
| 2007 | 11 |
Where
Open the mapLatest 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 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')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 260))
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_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 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')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 260))
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 SEA08CA047Accident · No injuriesData collectionFinal reportCessna 172S · El Cajon, CAThe excessive speed while turning off of the runway which resulted in a loss of aircraft control. The ditch was a factor.NTSB CHI07CA308Accident · No injuriesData collectionFinal reportCessna 172 SP · Heath, OHThe improper flare and inadequate recovery from a bounced landing by the student pilot. A factor was the student pilot's lack of experience.NTSB DFW07CA210Accident · No injuriesData collectionFinal reportCessna 172 · McKinney, TXThe student pilot's failure to compensate for existing conditions while landing. A contributing factor was the prevailing crosswind.NTSB SEA07CA243Accident · No injuriesData collectionFinal reportCessna 172S · Bakersfield, CAThe student pilot's failure to maintain directional control of the airplane during the landing roll, which resulted in a collision with a taxiway sign.NTSB LAX07CA199Accident · No injuriesData collectionFinal reportCessna 172S · Santa Barbara, CAthe pilot's failure to maintain directional control.NTSB LAX07CA193Accident · No injuriesData collectionFinal reportCessna 172S · Jacksonville, FLthe student pilot's failure to maintain directional control.NTSB LAX07CA185Accident · Minor injuriesData collectionFinal reportCessna 172S · Wendover, UTThe pilot's failure to maintain directional control during the landing roll.NTSB LAX07CA170Accident · No injuriesData collectionFinal reportCessna 172S · Carson City, NVThe loss of directional control for undetermined reasons.NTSB CHI07CA103Accident · No injuriesData collectionFinal reportCessna 172S · Naples, FLThe pilot's failure to maintain directional control of the airplane during landing. A contributing factor to the accident was the runway marker sign.NTSB LAX07CA101Accident · No injuriesData collectionFinal reportCessna 172S · Prescott, AZthe student pilot's failure to maintain directional during the landing rollout and the certified flight instructor's inadequate supervision.NTSB CHI07CA074Accident · No injuriesData collectionFinal reportCessna 172S · St. Louis, MOThe pilot's inadequate compensation for the wind conditions and failure to maintain directional control. Factors were the gusting crosswind conditions and the snow covered ground.NTSB DFW07CA048Accident · No injuriesData collectionFinal reportCessna 172S · Spicewood, TXThe pilot's failure to compensate for the existing wind conditions resulting in a loss of directional control. Factors were the gusty crosswind and the muddy terrain.NTSB SEA07LA013Accident · No injuriesLimited investigationFinal reportCessna 172S · Richfield, UTThe student pilot's inability to compensate for the gusty crosswinds during the initial part of the landing roll, which resulted in a loss of control and a noseover. Factors associated with the accident are gusty crosswinds, and a mound/berm of dirt alongside…NTSB NYC06CA232Accident · No injuriesData collectionFinal reportCessna 172S · Cambridge, MDThe pilot's failure to maintain directional control while landing.NTSB SEA06CA187Accident · No injuriesData collectionFinal reportCessna 172S · Naples, FLThe student pilot's failure to adequately compensate for wind conditions during the landing roll. A drainage ditch and wind were contributing factors.NTSB ATL06CA117Accident · No injuriesData collectionFinal reportCessna 172S · Thomson, GAThe student pilot's failure to maintain directional control during the landing roll resulting in an on-ground collision with an embankment.NTSB LAX06CA174Accident · No injuriesData collectionFinal reportCessna 172S · Madera, CAthe pilot's failure to maintain directional control during the landing rollout.NTSB NYC06CA116Accident · No injuriesData collectionFinal reportCessna 172S · Louisville, KYThe student pilot's failure to maintain directional control during the takeoff roll.NTSB ATL06CA075Accident · No injuriesData collectionFinal reportCessna C172S · Muscle Shoals, ALThe student pilot's failure to maintain directional control of the airplane during takeoff roll.NTSB DFW06CA098Accident · No injuriesData collectionFinal reportCessna 172S · Denton, TXThe student pilot's failure to maintain directional control during the takeoff roll.NTSB DEN06CA022Accident · No injuriesData collectionFinal reportCessna 172S · Lawrence, KSthe student pilot's improper decision to continue taxiing through the field. Contributing factor's include student pilot's failure to maintain control during the takeoff roll and the drainage ditch masked by snow.NTSB ATL05CA153Accident · No injuriesData collectionFinal reportCessna 172S · Savannah, GAThe instructor's inadequate supervision and failure to maintain directional control, resulting in an on ground collision with terrain.NTSB LAX05LA118Accident · No injuriesLimited investigationFinal reportCessna 172S · Thermal, CAthe student pilot's inadequate compensation for the crosswind conditions and failure to maintain directional control.NTSB MIA05CA048Accident · No injuriesData collectionFinal reportCessna 172SP · Clewiston, FLThe pilot's failure to maintain directional control during landing rollout which resulted in the airplane veering off the runway and colliding into an airport sign.NTSB MIA05LA043Accident · No injuriesLimited investigationFinal reportCessna 172S · Lakeland, FLThe faulure of the pilot to maintain directional control of the aircraft during the landing roll resulting in the on-ground collision with a taxiway sign and subsequent collapse of the nose landing gear.NTSB MIA04CA109Accident · No injuriesData collectionFinal reportCessna 172SP · Miami, FLThe pilot's failure to maintain control while landing with a crosswind and gusting wind conditions, which resulted in the airplane veering off the runway and incurring damage.NTSB LAX04CA250Accident · No injuriesData collectionFinal reportCessna 172S · Glendale, AZthe pilot's failure to maintain directional control of the airplane, which resulted in a veer off the runway and collision with terrain.NTSB FTW04LA178Accident · No injuriesLimited investigationFinal reportCessna 172S · San Antonio, TXThe student pilot's failure to maintain control of the airplane during landing.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 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 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 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 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 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 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 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 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 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 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.NTSB LAX02LA130Accident · No injuriesLimited investigationFinal reportCessna 172S · Palm Springs, CAThe pilot lost directional control and collided with a runway edge light and taxiway sign.NTSB LAX02LA084Accident · No injuriesLimited investigationFinal reportCessna 172S · Glendale, AZThe pilot of the landing airplane failed to maintain directional control resulting in the on-ground collission.NTSB LAX01LA191Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Cottonwood, AZthe student's inadequate compensation for the gusty crosswind conditions and the subsequent loss of aircraft control during landing roll. The flight instructor’s inadequate supervision and his inadequate remedial action is also causal. Contributing factors…NTSB NYC01LA083Accident · No injuriesLimited investigationFinal reportCessna 172S · Keene, NHThe pilot's failure to maintain directional control during the landing roll. A factor included the patchy snow on the runway.NTSB CHI01LA060Accident · No injuriesLimited investigationFinal reportCessna 172S · Sioux Falls, SDAircraft directional control not being maintained by the student pilot during the takeoff roll. Factors to the accident were the snow bank and the student pilot's lack of total experience.NTSB FTW00LA050Accident · No injuriesLimited investigationFinal reportCessna 172S · Sugar Land, TXThe student pilot's failure to maintain control of the airplane during the landing roll.