NTSB investigations: Cessna 172F, UT
7 cases on aircraft the registry lists as Cessna 172F. 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
| 1975 | 1 |
|---|---|
| 1977 | 2 |
| 1983 | 1 |
| 1986 | 1 |
| 1989 | 1 |
| 2002 | 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\" = 'UT' 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 ('2072414'))
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" = 'UT' 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 ('2072414'))
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 DEN02LA053Accident · No injuriesLimited investigationFinal reportCessna 172F · Salt Lake City, UTthe pilot's improper in-flight planning and decisions, which resulted in fuel exhaustion. A factor contributing to the accident was the lack of suitable terrain for the forced landing.NTSB DEN89LA105Accident · No injuriesLimited investigationFinal reportCessna 172F · Morgan, UTInadequate servicing of the aircraft by the pilot, partial blockage of the fuel line and fuel filter, and fuel starvation. Contributing factors were: the downward sloping runway and a fence.NTSB DEN86LA089Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Ephraim, UTAccording to the plt, upon his arrival at the dest arpt, he could not activate the rwy lghts by radio, so he proceeded to the nearest arpt. He stated he could not find his alternate arpt beacon light, so he reversed direction and headed once more to his…NTSB DEN83LA110Accident · No injuriesLimited investigationFinal reportCessna 172F · Escalante, UTThe acft collided with the terrain and nosed over off the departure end of the runway during takeoff. The runway in use was 12 and the wind was from 180 degrees at 5 KTS gusting to 15 KTS. The runway is 5000 feet long and 60 feet wide. The field elevation is…NTSB DEN78FTM06Accident · Minor injuriesClosedCessna 172F · Salina, UTNTSB DEN77FA054Accident · 3 fatalClosedCessna 172 · Nsalina, UTNTSB DEN76FTM10Accident · Serious injuriesClosedCessna 172F · Tremonton, UT