NTSB investigations: Cessna 172K, ME
5 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
| 1980 | 1 |
|---|---|
| 1982 | 1 |
| 1988 | 1 |
| 2011 | 1 |
| 2012 | 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\" = 'ME' 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" = 'ME' 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 ERA12LA241Accident · No injuriesLimited investigationFinal reportCessna 172K · Belfast, METhe flight instructor’s failure to ensure the radio was set correctly to activate the pilot-controlled lighting, which resulted in poor positioning for a proper landing and a subsequent off-runway forced landing during an attempted go-around. Contributing to…NTSB ERA11CA333Accident · No injuriesData collectionFinal reportCessna 172K · Bar Harbor, METhe pilot's inadequate landing flare while landing with a gusting wind, which resulted in a hard landing.NTSB NYC88FA218Accident · 1 fatalField investigationFinal reportCessna 172K · Island Falls, MEPilot's poor in-inflight decisions and planning and failed to follow ATC directives to maintain VFR. The pilot continued VFR into IFR conditions and collided with hilly terrain.NTSB NYC82DA225Accident · No injuriesFinal reportCessna 172K · Vinalhaven, METhe engine lost power at 100 feet of altitude after takeoff. The pilot found by pumping the throttle, he could regain some power. The aircraft collided with trees and came to rest on the ground. The mixture control cable had separated about one inch from it…NTSB NYC80FA060Accident · 2 fatalClosedCessna 172 · Rockland, ME