NTSB investigations: Cessna 172R
29 cases on aircraft the registry lists as Cessna 172R, 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 | 4 |
|---|---|
| 2000 | 5 |
| 2001 | 2 |
| 2002 | 2 |
| 2003 | 1 |
| 2004 | 3 |
| 2005 | 3 |
| 2006 | 2 |
| 2007 | 7 |
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 ('2072401')
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 ('2072401')
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 CHI08CA047Accident · No injuriesData collectionFinal reportCessna Skyhawk 172 · Wausau, WIThe pilot failed to maintain directional control during the landing roll. Factors that contributed to the accident included the snow on the runway and the snowbank.NTSB CHI08CA029Accident · No injuriesData collectionFinal reportCessna 172R · Brookings, SDThe student pilot's failure to maintain directional control during takeoff roll. Contributing to the accident was the student pilot's lack of solo flight experience and the runway sign.NTSB ATL07CA124Accident · No injuriesData collectionFinal reportCessna C172R · Pawtucket, RIThe student pilot's failure to maintain control of the aircraft during the takeoff roll.NTSB MIA07CA090Accident · No injuriesData collectionFinal reportCessna 172R · Lantana, FLThe student pilot's failure to maintain directional control of the airplane during landing roll.NTSB CHI07CA089Accident · No injuriesData collectionFinal reportCessna 172R · Columbus, OHThe pilot's failure to maintain directional control while landing. Contributing factors to the accident were the wind conditions and the runway sign.NTSB NYC07CA078Accident · No injuriesData collectionFinal reportCessna 172R · Norfolk, VAThe pilot's failure to maintain directional control while landing, which resulted in a collision with a runway sign. A factor was the crosswind.NTSB ATL07CA047Accident · No injuriesData collectionFinal reportCessna 172R · Cartersville, GAThe pilot's failure to maintain directional control during the landing roll, which resulted in a loss of control and an on-ground collision with a sign.NTSB CHI07LA034Accident · No injuriesLimited investigationFinal reportCessna 172R · Lake in the Hil, ILThe directional control not maintained/obtained by the pilot, and the lack of recent experience by the pilot. The snow bank was a contributing factor.NTSB CHI06CA189Accident · No injuriesData collectionFinal reportCessna 172R · Waterford, MIThe directional control not obtained/maintained, the inadequate compensation for wind conditions, and the go-around not performed during landing by the pilot. An additional cause was the lack of experience by the pilot. A contributing factor was the crosswind.NTSB LAX06LA032Accident · No injuriesLimited investigationFinal reportCessna 172R · Ramona, CAthe student pilot's failure to maintain directional control during the landing.NTSB DFW06CA004Accident · No injuriesData collectionFinal reportCessna 172 · Spring, TXThe pilot's failure to maintain directional control while landing.NTSB CHI05CA090Accident · No injuriesData collectionFinal reportCessna 172R · Kalamazoo, MIThe pilot's failure to maintain directional control and the excessive taxispeed.NTSB NYC05LA034Accident · Minor injuriesLimited investigationFinal reportCessna 172R · Smoketown, PAThe pilot's failure to maintain directional control during takeoff, which resulted in a collision with a parked airplane.NTSB CHI04LA097Accident · No injuriesLimited investigationFinal reportCessna 172R · Kalamazoo, MIThe air traffic control procedures/directives not followed by tower air traffic controller, the inadequate compensation for wind conditions by the student pilot during landing, the lack of total experience by the student pilot, and the recommended crosswind…NTSB IAD04CA009Accident · No injuriesData collectionFinal reportCessna 172R · Fredrick, MDThe student pilot's failure to maintain directional control during the landing. A factor was the snow bank.NTSB LAX03LA112Accident · No injuriesLimited investigationFinal reportCessna 172R · Thermal, CAthe student pilot's failure to use aileron controls to compensate for the known crosswind and failure to maintain directional control during the landing rollout.NTSB FTW02LA122Accident · No injuriesLimited investigationFinal reportCessna 172R · McKinney, TXthe pilot's failure to maintain directional control of the airplane while taxiing from landing.NTSB LAX02LA115Accident · No injuriesLimited investigationFinal reportCessna 172R · Camarillo, CAThe pilot's failure to maintain directional control.NTSB MIA01LA095Accident · No injuriesLimited investigationFinal reportCessna 172R · Cartersville, GAthe pilot's failure to maintain control of the airplane which resulted in the airplane veering off course and subsequent impact with trees.NTSB CHI01LA092Accident · No injuriesLimited investigationFinal reportCessna 172R · Battle Creek, MIAircraft control not maintained by the student pilot during the takeoff roll. Factors to the accident were the student pilot's lack of experience and the snowbank.NTSB CHI00LA287Accident · No injuriesLimited investigationFinal reportCessna 172R · New Lenox, ILThe pilot's failure to maintain directional control during landing. Factors to the accident were the pipe that was struck, the crosswind, and the pilot's runway selection.NTSB CHI00LA182Accident · No injuriesLimited investigationFinal reportCessna 172R · Athens, MIthe failure of the student pilot to maintain control of the aircraft, the inadequate supervision by the flight instructor, and the delayed remedial action performed by the flight instructor. A factor to the accident was the runway edge light that was struck…NTSB CHI00LA115Accident · No injuriesLimited investigationFinal reportCessna 172R · Battle Creek, MIthe student pilot's failure to maintain directional control of the airplane during the landing. Factors associated with the accident were the misjudged landing flare, the student's lack of total experience, the runway lights, and the runway signs.NTSB CHI00LA081Accident · No injuriesLimited investigationFinal reportCessna 172R · Waterford, MIthe directional control not obtained/maintained by the dual student and the remedial action not performed by the certified flight instructor. Contributing factors were the crosswind and the snow bank.NTSB MIA00LA086Accident · No injuriesLimited investigationFinal reportCessna 172R · Olive Branch, MSThe student pilot's failure to maintain directional control during landing and the subsequent collision with a taxiway sign and collapsed right main landing gear.NTSB MIA99LA216Accident · No injuriesLimited investigationFinal reportCessna 172R · Savannah, GAThe student pilot's failure to maintain directional control of the airplane during a touch-and-go landing, resulting in the airplane running off the runway and colliding with a runway sign.NTSB CHI99LA203Accident · No injuriesLimited investigationFinal reportCessna 172R · Kokomo, INthe student pilot's failure to maintain directional control during landing. Factors to the accident were the pilot's lack of experience and the VOR station.NTSB CHI99LA091Accident · No injuriesLimited investigationFinal reportCessna 172R · Battle Creek, MIthe loss of directional control by the pilot. Factors to the accident were the lack of total experience of the pilot, the snow covered runway condition, the snowbank, and the flight instructor not verifying the runway snow removal with the Duty Instructor…NTSB CHI99LA071Accident · No injuriesLimited investigationFinal reportCessna 172R · Chesterfield, MOthe instructor pilot's failure to maintain aircraft control. Factors contributing to this accident were the snow covered grassy field area along the side of the runway and the pile of snow.