NTSB investigations: Cessna 172S
10 cases on aircraft the registry lists as Cessna 172S, where the first occurrence was “In flight collision with object”. 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
| 2001 | 3 |
|---|---|
| 2002 | 1 |
| 2003 | 2 |
| 2004 | 2 |
| 2005 | 1 |
| 2007 | 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.\"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_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
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_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 220))
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 MIA07CA045Accident · No injuriesData collectionFinal reportCessna 172S · Sanford, FLThe inadvertent inflight collision with a bird resulting in damage to the airplane and the pilot having limited control capability.NTSB DFW05CA253Accident · No injuriesData collectionFinal reportCessna 172S · Batesville, TXThe pilot's failure to maintain clearance from the tree. A contributing factor was the gusty winds.NTSB LAX04CA309Accident · Minor injuriesData collectionFinal reportCessna 172S · Willits, CAthe pilot's inadvertent descent and controlled flight into obstacles while maneuvering to land. Contributing factors were the dark, nighttime condition, which impaired the pilot's visual perceptions, and the pilot's failure to obtain a pertinent Notice to…NTSB ATL04LA140Accident · Serious injuriesLimited investigationFinal reportCessna 172S · Asheville, NCThe CFII's inadequate visual lookout and failure to maintain clear of objects during flight. Factors were clouds and dark night.NTSB FTW03FA182Accident · 2 fatalField investigationFinal reportCessna 172S · McKinney, TXThe CFI's failure to maintain airspeed sufficient for flight resulting in an inadvertent stall/spin during the forced landing. A contributing factor was the impact with a bird, which affected the performance of the airplane.NTSB CHI03FA149Accident · 1 fatalField investigationFinal reportCessna 172S · Sidnaw, MIThe improper short/soft field landing procedure by the pilot and his lack of recent experience in type of operation. Contributing factors were the short/soft field runway, the trees and his delay in aborting the takeoff.NTSB MIA02FA104Accident · 1 fatalField investigationFinal reportCessna 172S · Lutz, FLThe suicidal act by the pilot resulting in the in-flight collision with trees then the ground. A contributing factor in the accident was the pilot's depression. Findings in the investigation were the pilot's overdose of zolpidem and citalopram before the…NTSB NYC01FA217Accident · 2 fatalField investigationFinal reportCessna 172SP · Matawan, NJThe pilot's failure to maintain runway alignment during the initial climb. Factors were the pilot's failure to perform a go-around, the pilot's lack of flight experience in nighttime conditions, the nighttime conditions, and a tailwind.NTSB SEA01LA077Accident · No injuriesLimited investigationFinal reportCessna 172S · Renton, WAA Canadian goose which crossed the aircraft's flight path and impacted the left wing during the aircraft's final approach.NTSB ATL01LA023Accident · Serious injuriesLimited investigationFinal reportCessna 172SP · Austell, GAThe pilots failure to follow instrument flight procedures and descended below the published the minimum descent altitude and subsequently collided with trees short of the runway.