NTSB investigations: Cessna 172K, VA
12 cases on aircraft the registry lists as Cessna 172K. 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
| 1970 | 1 |
|---|---|
| 1971 | 1 |
| 1973 | 3 |
| 1976 | 1 |
| 1977 | 1 |
| 1978 | 1 |
| 1987 | 1 |
| 1995 | 1 |
| 2007 | 1 |
| 2024 | 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 ('2072430'))
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 ('2072430'))
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 ERA24LA390Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172K · Fredericksburg, VAThe pilot’s inadequate fuel planning, which resulted in fuel exhaustion and a subsequent total loss of engine power.NTSB MIA07CA099Accident · No injuriesData collectionFinal reportCessna 172K · Emporia, VAThe failure of the student pilot to maintain directional control of the airplane during the takeoff roll resulting in the on-ground collision with a ditch.NTSB BFO96LA030Accident · No injuriesLimited investigationFinal reportCessna 172K · Lovingston, VAthe pilot's improper planning/decision during the approach/landing phase of flight. Related factors were: the pilot's selection of the wrong runway, and the gusty tailwind conditions.NTSB BFO87LA061Accident · No injuriesLimited investigationFinal reportCessna 172 · Tappahannock, VAThe acft was at 1500 MSL when a 300 RPM loss of power occurred. The plt sighted a private landing strip and he decided to make a precautionary landing on it. During the landing roll on the 62 ft wide grass strip the l wing struck corn stalks in an adjacent…NTSB IAD78FA096Accident · No injuriesClosedCessna 180 · Roanoke, VANTSB IAD77DIA25Accident · Minor injuriesClosedCessna 172 · Warrenton, VANTSB IAD76FIA12Accident · No injuriesClosedCessna 172K · Springfield, VANTSB IAD74FIA01Accident · No injuriesClosedCessna 172K · Leesburg, VANTSB IAD74FID04Accident · Minor injuriesClosedCessna 172K · Charles City, VANTSB IAD73FIA14Accident · No injuriesClosedCessna 172K · Luray, VANTSB NYC72DID18Accident · No injuriesClosedCessna 172K · Reedville, VANTSB IAD71DID16Accident · Minor injuriesClosedCessna 172K · Waynesboro, VA