NTSB investigations: Cessna 172L
10 cases on aircraft the registry lists as Cessna 172L, where the first occurrence was “Overrun”. 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
| 1984 | 1 |
|---|---|
| 1985 | 1 |
| 1990 | 1 |
| 1994 | 1 |
| 1999 | 2 |
| 2003 | 1 |
| 2006 | 3 |
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 ('2072432')
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\" = 340))
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 ('2072432')
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" = 340))
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 CHI06CA182Accident · No injuriesData collectionFinal reportCessna 172L · Waterford, OHThe pilot's selection of unsuitable terrain for landing. The runway's downhill slope, the wet grass, the fence, and the embankment were factors.NTSB ATL06CA084Accident · No injuriesData collectionFinal reportCessna 172L · Lexington, TNThe pilot's failure to attain the proper touchdown point during landing.NTSB ATL06CA046Accident · No injuriesData collectionFinal reportCessna 172L · Long Island, NCThe student pilot's failure to achieve the proper touch down point on landing resulting in an overrun, on-ground collision with a ditch, and subsequent nose over. A factor in the accident was the inadequate supervision of the student pilot by the flight…NTSB FTW03LA175Accident · Serious injuriesLimited investigationFinal reportCessna 172L · San Antonio, TXThe pilot misjudged his altitude and airspeed, and his failure to perform a go-around.NTSB CHI99LA237Accident · No injuriesLimited investigationFinal reportCessna 172L · Montezuma, IAthe pilot inadvertently landed on the wrong runway and exceeded the proper touchdown point on the runway. Factors associated with the accident were the gusty tailwind, the fence, and the ditch.NTSB LAX99LA082Accident · No injuriesLimited investigationFinal reportCessna 172L · Santa Paula, CAThe instructor pilot's misjudged altitude and speed, which resulted in a failure to attain the proper touchdown point causing an overrun and collision with a block wall. A factor was the wet runway, which may have hindered brake effectiveness.NTSB SEA94LA102Accident · No injuriesLimited investigationFinal reportCessna 172L · Colville, WAThe pilot's failure to attain a proper touchdown point, and his excessive airspeed at the point of touchdown. Factors include the student pilot's lack of recent experience, and a ravine off the end of the runway.NTSB CHI90FA196Accident · No injuriesField investigationFinal reportCessna 172 · Canton, MIThe pilot's inadequate takeoff procedure, premature liftoff and delayed reaction to abort the takeoff.NTSB SEA86LA006Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Emmett, IDWhile landing in calm wind conditions on a 2400 ft rwy, the left brake failed & the acft contd off the departure end, then hit a fence. An exam revealed the left brake pads were worn & the left actuator cylinder was losing fluid. The brake backing plate & the…NTSB NYC84LA140Accident · Minor injuriesLimited investigationFinal reportCessna 172L · Mayville, NYOn an apch to land, after a go-around, the acft crossed over wires & touched down on the 1st half of the rwy. The plt applied brakes on the wet grass rwy, but noted a lack of braking action. He applied power to go around, but decided the acft would not clear…