NTSB investigations: Cessna 172I
9 cases on aircraft the registry lists as Cessna 172I, where the first occurrence was “Loss of engine power(total) - nonmechanical”. 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 |
|---|---|
| 1987 | 1 |
| 1990 | 1 |
| 1993 | 1 |
| 1997 | 2 |
| 1998 | 1 |
| 2001 | 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 ('2072426')
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\" = 353))
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 ('2072426')
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" = 353))
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 NYC01LA080Accident · No injuriesLimited investigationFinal reportCessna 172I · Suffolk, VAThe pilot's improper in-flight planning/decision and his failure to refuel, which resulted in fuel exhaustion.NTSB MIA98LA104Accident · No injuriesLimited investigationFinal reportCessna 172I · Kinston, NCthe pilot's inadequate preflight and improper fuel management, which resulted in fuel exhaustion, loss of engine power, and a forced landing. Soft terrain in the emergency landing area was a related factor.NTSB SEA97LA166Accident · Minor injuriesLimited investigationFinal reportCessna 172I · Naches, WAinadequate preflight by the pilot, and subsequent fuel exhaustion, which led to a forced landing and subsequent nose over of the aircraft. Related factors were: the FBO did not refuel the aircraft as requested, and soft terrain was encountered during the…NTSB ATL97LA081Accident · No injuriesLimited investigationFinal reportCessna 172I · N. Myrtle Beach, SCThe pilot's inadequate pre-flight inspection which resulted in fuel exhaustion and total loss of engine power. A factor was the soft terrain at the emergency landing site.NTSB NYC93LA171Accident · No injuriesLimited investigationFinal reportCessna 172 · Phillips, METhe pilot's inadequate preflight and inflight decision which resulted in fuel exhaustion and the loss of engine power.NTSB FTW91LA003Accident · No injuriesLimited investigationFinal reportCessna 172 · Claremore, OKFailure of pilot in command to insure the aircraft contained enough fuel for the flight resulting in engine failure due to fuel exhaustion.NTSB MKC88LA013Accident · No injuriesLimited investigationFinal reportCessna 172 · Sweet Springs, MODuring a night cross country flight an emergency ldg was made due to complete power failure. PIC said he failed to visually check fuel supply before departure, and also failed to check winds aloft, which were quartering headwinds, of twenty five knots. Post…NTSB FTW83LA281Accident · Minor injuriesLimited investigationFinal reportCessna 172I · Forrest City, ARThe acft experienced power failure from about 20 feet AGL during takeoff from a private grass strip. A witness heard theengine spit and pop during the takeoff roll. He said it sounded just like his old pickup when it runs out of gas. After the accident the…NTSB MKC83FA087Accident · No injuriesField investigationFinal reportCessna 172 I · Paola, KSThe acrt crashed in a pasture after fuel exhaustion during an approach to johnson county industrial arpt. The acft had made a missed approach at his destination of Nevada MO. Enroute to a suggested alterate of butler arpt. The weather became worse and johnson…