NTSB investigations: Cessna 172M, VA
31 cases on aircraft the registry lists as Cessna 172M. 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
| 1973 | 1 |
|---|---|
| 1974 | 2 |
| 1975 | 1 |
| 1976 | 2 |
| 1977 | 1 |
| 1978 | 4 |
| 1981 | 1 |
| 1984 | 1 |
| 1986 | 1 |
| 1992 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2002 | 1 |
| 2006 | 1 |
| 2013 | 2 |
| 2017 | 1 |
| 2018 | 1 |
| 2019 | 2 |
| 2020 | 1 |
| 2021 | 1 |
| 2022 | 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.\"eventStateOrRegion\" = 'VA' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072418'))
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."eventStateOrRegion" = 'VA' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072418'))
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 ERA22LA113Accident · No injuriesClass 4 · LimitedFinal reportCessna 172 · Waynesboro, VAThe student pilot’s loss of directional control while landing.NTSB ERA21LA198Accident · No injuriesClass 4 · LimitedFinal reportCessna 172M · Fredericksburg, VAThe student pilot reported that, during the landing roll, he applied brakes and the airplane veered right. He was unable to correct back to the centerline or brake effectively; the airplane exited the runway and struck an embankment before coming to rest. The…NTSB ERA20CA235Accident · No injuriesClass 4 · Data collectionFinal reportCessna 172 · Chesapeake, VAThe student pilot's improper landing flare and failure to recover from the ensuing bounced landing, which resulted in a runway excursion.NTSB GAA19CA311Accident · No injuriesData collectionFinal reportCessna 172 · Culpeper, VAThe student pilot's improper landing flare, which resulted in a porpoised landing.NTSB ERA19TA192Accident · No injuriesClass 3Final reportCessna 172 · Stafford, VAThe pilot’s failure to maintain directional control while landing in gusting crosswind conditions, which resulted in a runway excursion.NTSB ERA18LA233Accident · Serious injuriesClass 3 · LimitedFinal reportCessna 172 · New Kent, VAThe student pilot’s loss of airplane control during a go-around.NTSB GAA17CA448Accident · No injuriesData collectionFinal reportCessna 172 · Manassas, VAThe student pilot’s improper landing flare, which resulted in a porpoised landing.NTSB ERA13FA330Accident · 1 fatalField investigationFinal reportCessna 172M · Fredericksburg, VAThe pilot's intentional descent into the ground to commit suicide.NTSB ERA13LA194Accident · No injuriesLimited investigationFinal reportCessna 172M · New Castle, VAThe pilot's failure to abort the takeoff after recognizing that the airplane was not accelerating properly, which led to an aerodynamic stall. The reason for the lack of acceleration could not be determined because postaccident examinations did not reveal any…NTSB NYC07CA019Accident · No injuriesData collectionFinal reportCessna 172M · Wakefield, VAThe student pilot's failure to maintain control during the landing. A factor to the accident was the wind gusts.NTSB IAD02LA095Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Edinburg, VAA loss of engine power for undetermined reasons.NTSB IAD02LA003Accident · Minor injuriesLimited investigationFinal reportCessna 172M · White Stone, VAloss of engine power for undetermined reasons.NTSB NYC01LA063Accident · No injuriesLimited investigationFinal reportCessna 172M · Farmville, VAthe failure of the pilot to maintain directional control.NTSB NYC98LA081Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Weyers Cave, VAthe pilot's inadequate compensation for crosswind conditions and failure to maintain directional control of the airplane during the landing roll, which resulted in an encounter with a fence on uneven terrain and a nose over.NTSB IAD98LA007Accident · No injuriesLimited investigationFinal reportCessna 172M · Oceana, VAImproper flare by the pilot, which resulted in a hard landing. A related factor was the diverted attention.NTSB IAD96LA053Accident · No injuriesLimited investigationFinal reportCessna 172 · Roanoke, VAloss of engine power for undetermined reason(s). Darkness and the pilot's improper emergency procedures were related factors.NTSB BFO92LA053Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Amelia, VAThe pilot's misjudgement of distance and altitude that resulted in an landing overrun and collision with an embankment. Contributing was failure to initiate a go around and inadequate supervision.NTSB BFO86FID07Accident · No injuriesFinal reportCessna 172M · Lynchburg, VAThe accident occurred as the plt was attempting to land at an unfamiliar arpt during a x-country flt because a passenger was feeling ill. The rwy was 2900 ft long with a 5% upslope at mid-field. The plt stated he misjudged his alt and airspeed during the…NTSB ATL85FID01Accident · Serious injuriesFinal reportCessna 172M · Norfolk, VAThe plt was making his landing apch behind a Boeing 727 and in front of a Boeing 737. Plt was requested by ATC to make a short apch but was also cautioned about wake turbulence. On final apch at aprx 50 ft AGL, N70554 rolled sharply into a 90 deg bank,…NTSB ATL81FA081Accident · No injuriesClosedPiper PA-23 · Manassas, VANTSB IAD79FID04Accident · Minor injuriesClosedCessna 172 · Newport News, VANTSB IAD78DID15Accident · No injuriesClosedCessna 172 · Chesapeake, VANTSB IAD78FID13Accident · No injuriesClosedCessna 172M · Gloucester, VANTSB IAD78FID05Accident · Minor injuriesClosedCessna 172M · Fredericksburg, VANTSB IAD77FIJ05Accident · No injuriesClosedCessna 172M · Richlands, VANTSB IAD77DIA07Accident · No injuriesClosedCessna 172 · Chantilly, VANTSB IAD76DID42Accident · No injuriesClosedCessna 172M · Lowmoor, VANTSB IAD76FID08Accident · No injuriesClosedCessna 172M · Crozet, VANTSB NYC07LA005Accident · 3 fatalLimited investigationClosedCessna 172M · Saltville, VAThe pilot's continued VFR flight into known night instrument meteorological conditions. Factors in the accident included mountainous terrain obscured by clouds, and dark night conditions.NTSB NYC74AN083Accident · 1 fatalClosedCessna 172M · Martinsville, VANTSB IAD73DID25Accident · No injuriesClosedCessna 172 · Ashland, VA