NTSB investigations: Cessna 172E
13 cases on aircraft the registry lists as Cessna 172E, 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
| 1983 | 2 |
|---|---|
| 1986 | 2 |
| 1987 | 1 |
| 1999 | 2 |
| 2002 | 1 |
| 2004 | 2 |
| 2006 | 2 |
| 2007 | 1 |
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 ('2072412')
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 ('2072412')
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 CHI07CA090Accident · No injuriesData collectionFinal reportCessna 172E · Big Rapids, MIThe student pilot's failure to maintain directional control of the airplane during takeoff which led to the impact with the snow banks adjacent to the runway. The snow banks were contributing factors in the accident.NTSB CHI06CA123Accident · No injuriesData collectionFinal reportCessna 172E · Richmond, INThe pilot's inadequate compensation for wind conditions during the landing. Factors were the crosswind and gusts.NTSB CHI06CA120Accident · No injuriesData collectionFinal reportCessna 172E · Wadena, MNThe pilot's inadequate compensation for the wind conditions during the landing. Factors were the crosswinds, the gusts, and the ditch.NTSB SEA04LA053Accident · No injuriesLimited investigationFinal reportCessna 172E · Raymond, WAThe pilot's failure to maintain directional control during the landing roll resulting in the aircraft nosing over. Incorrect remedial action and soft terrain were factors.NTSB NYC04CA068Accident · No injuriesData collectionFinal reportCessna 172E · Batavia, NYThe pilot's failure to maintain directional control while landing. Factors were a tailwind and icy runway.NTSB FTW02LA170Accident · No injuriesLimited investigationFinal reportCessna 172E · Navajo Dam, NMthe pilot's failure maintain directional control of the airplane during a touch and go landing which resulted in a collision with trees. A contributing factor was the gusting wind conditions.NTSB DEN99LA125Accident · Minor injuriesLimited investigationFinal reportCessna 172E · Peyton, COThe pilot's failure to maintain directional control of the aircraft during landing touchdown. Factors were the crosswind and the ditch.NTSB FTW99LA071Accident · No injuriesLimited investigationFinal reportCessna 172E · Guymon, OKThe pilot's failure to maintain aircraft control. A factor was the gusty crosswind.NTSB CHI87LA096Accident · No injuriesLimited investigationFinal reportCessna 172E · Muncie, INAccording to the plt, he contacted the mie tower about 20 miles north of Muncie, Indiana and received a weather briefing with a choice of rwy 14 or 02. The plt stated that the winds were reported as 12 knots from 080, and he chose to land on rwy 14. According…NTSB SEA86LA103Accident · No injuriesLimited investigationFinal reportCessna 172 · Reno, NVThe student plt lost control of the acft during high gusty wind conditions. The acft then veered to the right of the rwy. The wind at the time of the accident was from 280 degrees at 28 knots gusting to 31 knots.NTSB NYC86LA062Accident · No injuriesLimited investigationFinal reportCessna 172 · Durhamville, NYThe flight was returning from a 4-LEG 300-mile cross country trip. On flare touchdown, the pilot reported severe vibration. As brakes were applied the vibration increased, and the aircraft became uncontrollable. The aircraft pulled to the right and collided…NTSB MKC84LA030Accident · No injuriesLimited investigationFinal reportCessna 172 · Hampton, IAOn his fourth touch and go landing the pilot added power for the go-around and the aircraft drifted off the left side of the runway. The left main gear hit a snowbank and the aircraft flipped over landing upside down in the snow. The winds at macon city, IA…NTSB CHI83LA177Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Youngstown, OHThe pilot stated that during a landing, the left wing was caught by the wind and the aircraft drifted to the right. A go-around was initiated but the aircraft struck a runway light and a runway distance marker and nosed over.