NTSB investigations: Cessna 172S
25 cases on aircraft the registry lists as Cessna 172S, where NTSB found Not determined, general. 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
| 2009 | 1 |
|---|---|
| 2010 | 2 |
| 2011 | 1 |
| 2012 | 1 |
| 2013 | 2 |
| 2014 | 2 |
| 2015 | 5 |
| 2018 | 3 |
| 2019 | 3 |
| 2021 | 5 |
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 ('2072439', '2072442')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f.\"findingCode\", '05000000')))
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 ('2072439', '2072442')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f."findingCode", '05000000')))
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 ERA22LA029Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Westhampton Beach, NYA total loss of engine power during cruise flight for reasons that could not be determined based on the available evidence.NTSB CEN21LA414Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172S · LaSalle, COA loss of engine power for undetermined reasons.NTSB WPR21LA303Accident · No injuriesClass 3 · LimitedFinal reportCessna 172S · Yelm, WAA total loss of engine power for reasons that could not be determined based on the available evidence.NTSB ERA21LA187Accident · No injuriesClass 3 · LimitedFinal reportCessna 172S · Venice, FLA total loss of engine power for reasons that could not be determined based on the available information.NTSB WPR21LA140Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172S · Everett, WAA total loss of engine power during climb, for reasons that could not be determined based on available evidence.NTSB CEN19FA221Accident · 1 fatalClass 3 · FieldFinal reportCessna 172 · Katy, TXThe pilot’s loss of airplane control and subsequent impact with terrain for reasons that could not be determined based on the available information.NTSB WPR19FAMS1Accident · 1 fatalMissing aircraftFinal reportCessna 172 · Pescadero, CAImpact with the ocean for reasons that could not be determined because the airplane was not located.NTSB GAA19CA282Accident · No injuriesData collectionFinal reportCessna 172 · Edwards Air Force Base, CAAn undetermined event, which resulted in substantial damage to the airplane for reasons that could not be determined based on the available evidence.NTSB WPR18LA207Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Mount Vernon, OHAn in-flight fuel-fed fire from an unknown source for reasons that could not be determined due to the extensive fire damage to the airplane.NTSB ERA18LA094Accident · 2 fatalLimited investigationFinal reportCessna 172 · Ocean City, MDThe pilot's flight in dark night visual meteorological conditions, which resulted in an impact with water for reasons that could not be determined based on the available information.NTSB ERA18LA074Accident · No injuriesLimited investigationFinal reportCessna 172 · Babylon, NYThe partial loss of engine power after a simulated engine failure for reasons that could not be determined because a postaccident examination and an engine test run did not reveal any anomalies that would have precluded normal operation.NTSB ANC16LA011Accident · 1 fatalLimited investigationFinal reportCessna 172 · Anchorage, AKThe pilot's intentional flight into a building.NTSB GAA15CA161Accident · No injuriesData collectionFinal reportCessna 172S · Galesburg, ILFirewall damage reported by maintenance personnel that occurred during an unknown phase of flight, because the accident flight and pilot could not be determined.NTSB WPR15FAMS1Accident · 1 fatalMissing aircraftFinal reportCessna 172S · Davenport, CAUndetermined because the airplane was not located.NTSB GAA15CA018Accident · No injuriesData collectionFinal reportCessna 172S · Camarillo, CAThe pilot involved and the phase of flight when the damage occurred were not determined.NTSB ERA15LA094Accident · No injuriesLimited investigationFinal reportCessna 172 · Norfolk, VAThe engine’s failure to regain full power after a simulated engine failure for reasons that could not be determined during postaccident examinations and testing.NTSB WPR15LA014Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Big Bear, CAA partial loss of engine power for reasons that could not be determined because postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation.NTSB ERA14FA283Accident · 2 fatalField investigationFinal reportCessna 172S · Daytona Beach, FLA partial loss of engine power during the initial climb after takeoff for reasons that could not be determined due to the postaccident condition of the wreckage. Contributing to the accident was the pilots' decision to turn back to the airport, which led to…NTSB WPR13CA348Accident · No injuriesData collectionFinal reportCessna 172S · Phoenix, AZA substantially damaged firewall that occurred during an unknown phase of flight for reasons that could not be determined.NTSB ERA13LA291Accident · No injuriesLimited investigationFinal reportCessna 172S · Clearwater, FLA total loss of engine power for reasons that could not be determined because neither postaccident visual examinations nor test runs of the engine revealed any anomalies that would have precluded normal operation.NTSB ERA12LA274Accident · No injuriesLimited investigationFinal reportCessna 172S · Daytona Beach, FLA total loss of engine power due to a catastrophic engine failure, the origin of which could not be determined during postaccident examination.NTSB WPR11LA284Accident · No injuriesLimited investigationFinal reportCessna 172S · Palo Alto, CAA total loss of engine power for undetermined reasons during the landing approach over unsuitable terrain.NTSB ERA11LA015Accident · No injuriesLimited investigationFinal reportCessna 172SP · Boynton Beach, FLThe loss of engine power for undetermined reasons.NTSB CEN10CA325Accident · No injuriesData collectionFinal reportCessna 172 · Traverse City, MIDamage to the firewall for undetermined reasons.NTSB WPR09LA098Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Oceanside, CAA defective alternator wire splice that resulted in an intermittent electrical system malfunction and erroneous fuel gauge readings, and, a loss of engine power for an undetermined reason.