NTSB investigations: Cessna 172P, CT
13 cases on aircraft the registry lists as Cessna 172P. 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 |
|---|---|
| 1984 | 1 |
| 1985 | 1 |
| 1987 | 4 |
| 1991 | 1 |
| 1998 | 1 |
| 2003 | 1 |
| 2012 | 1 |
| 2017 | 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\" = 'CT' 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 ('2072436'))
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" = 'CT' 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 ('2072436'))
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 GAA17CA530Accident · Minor injuriesData collectionFinal reportCessna 172 · Plainville, CTThe pilot’s failure to properly execute the go-around, which resulted in the airplane failing to maintain a climb, which resulted in collision with a tree.NTSB ERA12FA483Accident · 1 fatalField investigationFinal reportCessna 172P · Plainville, CTThe pilot's failure to maintain the proper glidepath during final approach in visual meteorological conditions, resulting in collision with a berm.NTSB NYC03CA167Accident · No injuriesData collectionFinal reportCessna 172P · Plainfield, CTThe pilot's failure to maintain directional control, which resulted in a collision with a ditch. A factor in this accident was the crosswind condition.NTSB NYC98LA082Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainville, CTThe pilot's inadequate crosswind compensation.NTSB NYC91LA106Accident · No injuriesLimited investigationFinal reportCessna 172P · Burlington, CTThe failure of the pilot to maintain directional control during the landing. Factors related to the accident were: improper use of the flight controls by the pilot, his lack of recent experience and total time, and the crosswind.NTSB NYC88LA031Accident · No injuriesLimited investigationFinal reportCessna 172 · Stamford, CTThe instructor (CFI) reported that the aircraft had just reached the top of a climb at 2500 ft when the engine lost power. An off airport landing was made on a golf course. During the landing, the wings struck trees and the aircraft was damaged. The golf…NTSB NYC87LA213Accident · No injuriesLimited investigationFinal reportCessna 172P · Plainfield, CTWhile landing in crosswind conditions, the pilot failed to compensate for the conditions and lost directional control of the aircraft. The aircraft went down an embankment, collided with a fence and then flipped inverted.NTSB NYC87LA228Accident · No injuriesLimited investigationFinal reportCessna 172 · Groton, CTThe aircraft was taxiing to the ramp after landing. While the pilot was maneuvering the aircraft into a parking space, the aircraft was positioned in such a way that the sun had blinded him temporarily. As the pilot turned the aircraft the left wing contacted…NTSB NYC87LA154Accident · No injuriesLimited investigationFinal reportCessna 172 · New Haven, CTDrg a night flt from new bedford to bridgeport, the plt enctrd visibility problems & believed that fuel consumption was higher than normal. He obtained radar vectors to New Haven. After seeing the arpt, he flew over to establish the runway pattern. However,…NTSB NYC85LA178Accident · Minor injuriesLimited investigationFinal reportCessna C172 · Ellington, CTThe acft collided with the ground during takeoff from rwy 01 at Ellington, Connecticut, and was substantially damaged but there was no fire. The pilot received minor injuries. The aircraft crashed for undetermined reasons.NTSB NYC85LA034Accident · No injuriesLimited investigationFinal reportCessna 172P · Madison, CTPlt stated that as he lowered nose gear to runway following initial touchdown on mains, acft nose continued to drop. Control inputs were not effective. Investigation revealed the nose gear ass'y failed in overload. Based on fuel remaining on board and…NTSB NYC83LA161Accident · No injuriesLimited investigationFinal reportCessna 172P · Redding, CTThe flight originated at ramapo, NY. During a preflight check, the plt noted that the fuel gauges indicated full. When he visually checked the fuel tanks, he estimated that the fuel level in each tank was about 1 inch from being full. The fuel capacity of…NTSB NYC83LA058Accident · No injuriesLimited investigationFinal reportCessna 172P · Bridgeport, CTAfter practicing three takeoffs and landings, a fourth takeoff was aborted. The student completed a run-up, checked the controls and received clearance to takeoff. He stated that he began rolling straight down the centerline, then at about 45 KTS, the plane…