NTSB investigations: Cessna 172D, PA
8 cases on aircraft the registry lists as Cessna 172D. 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
| 1965 | 1 |
|---|---|
| 1967 | 1 |
| 1969 | 1 |
| 1974 | 1 |
| 1976 | 1 |
| 1987 | 1 |
| 1988 | 1 |
| 1993 | 1 |
Where
Latest 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\" = 'PA' 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 ('2072410'))
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" = 'PA' 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 ('2072410'))
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 BFO93LA126Accident · Serious injuriesLimited investigationFinal reportCessna 172D · New Milford, PALoss of engine engine power due to water contamination of the fuel. Factors related to the accident were the mice, which partially blocked fuel and air flow to the carburetor, and the lack of suitable terrain in the emergency landing area.NTSB NYC88LA122Accident · No injuriesLimited investigationFinal reportCessna 172 · Myerstown, PAThe pilot stated that during takeoff the aircraft veered to the left and the left wheel dug into the sod. At the same time the right wing lifted up and the aircraft rolled over. The wind was variable at 10 to 15 knots, gusting to 30.NTSB NYC87LA253Accident · No injuriesLimited investigationFinal reportCessna 172D · Scottdale, PADuring a local pleasure flight, the pilot noticed the airspeed indicator was inoperative. On lndg the acft was obsvd to touchdown abt half-way down the rwy and faster than normal. The aircraft continued off the runway and crossed the airport road coming to…NTSB NYC76AN097Accident · 1 fatalClosedCessna 172 · Marklesburg, PANTSB NYC75FHA11Accident · No injuriesClosedCessna 172 · E Stroudsburg, PANTSB NYC69F0411Accident · Serious injuriesClosedCessna 172D · Darragh, PANTSB NYC68F0023Accident · Minor injuriesClosedCessna 172 · Central City, PANTSB NYC66D0424Accident · Minor injuriesClosedCessna 172 · Pittsburg, PA