NTSB investigations: Cessna 172L, IA
4 cases on aircraft the registry lists as Cessna 172L. 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 |
|---|---|
| 1982 | 1 |
| 1999 | 1 |
| 2008 | 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\" = 'IA' 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 ('2072432'))
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" = 'IA' 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 ('2072432'))
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 CHI08LA108Accident · Serious injuriesLimited investigationFinal reportCessna 172L · Fairfax, IAFuel exhaustion as a result of the pilot's inadequate preflight inspection and inaccurate fuel calculations.NTSB CHI99LA237Accident · No injuriesLimited investigationFinal reportCessna 172L · Montezuma, IAthe pilot inadvertently landed on the wrong runway and exceeded the proper touchdown point on the runway. Factors associated with the accident were the gusty tailwind, the fence, and the ditch.NTSB MKC82DA051Accident · No injuriesFinal reportCessna 172L · Des Moines, IAThe pilot landed on runway 23 with the wind from 230 degrees at 34 gusting 40 knots. After turning off to the right side of the runway, a gust of wind tipped the aircraft, turned it further to the right, and then blew it over on its back.NTSB MKC74DCD18Accident · No injuriesClosedCessna 172 · Davenport, IA