NTSB investigations: Cessna 172M, MS
16 cases on aircraft the registry lists as Cessna 172M. 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
| 1974 | 1 |
|---|---|
| 1976 | 1 |
| 1977 | 2 |
| 1980 | 1 |
| 1987 | 1 |
| 1989 | 2 |
| 1992 | 2 |
| 1995 | 1 |
| 2003 | 1 |
| 2005 | 1 |
| 2012 | 1 |
| 2021 | 1 |
| 2024 | 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\" = 'MS' 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 ('2072418'))
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" = 'MS' 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 ('2072418'))
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 CEN24LA366Accident · No injuriesClass 3 · LimitedFinal reportCessna 172M · Ackerman, MSThe excessive airplane speed during a no-flap landing, and the pilot’s failure to attain a proper touchdown point, which resulted in a runway overrun. Contributing to the accident was the interference of the instrument panel wiring with the flight control…NTSB CEN21LA392Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · Olive Branch, MSThe pilot’s failure to maintain directional control of the airplane during landing with a direct crosswind that resulted in an impact with terrain.NTSB ERA12CA568Accident · Serious injuriesData collectionFinal reportCessna 172M · Quitman, MSThe pilot’s improper preflight inspection, which resulted in a total loss of engine power due to fuel exhaustion.NTSB MIA05LA155Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Ocean Springs, MSThe pilot's mismanagement of available fuel and continued operation with the fuel selector set to the left tank position, which resulted in fuel starvation and subsequent loss of engine power.NTSB MIA03LA056Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Leesburg, MSThe pilot's improper use of flaps, resulting in the degradation of climb performance and collision with the ground.NTSB MIA96LA034Accident · No injuriesLimited investigationFinal reportCessna 172M · Madison, MSThe pilot's premature raising of flaps during a go-around.NTSB MIA92LA185Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Picayune, MSThe pilot in command's failure to maintain airspeed (vso) while conducting slow flight at a low altitude. This resulted in an in flight loss of control (stall) and subsequent in flight collision with trees.NTSB MIA92LA171Accident · No injuriesLimited investigationFinal reportCessna 172M · Hernando, MSThe failure of the pilot in command to compensate for the crosswind condition, resulting in a ground loop. Contributing to the accident was the pilot's lack of experience in the type of aircraft.NTSB MIA89LA120Accident · No injuriesLimited investigationFinal reportCessna 172M · Columbia, MSThe pilot's inadequate compensation for wind conditions, which resulted in a loss of directional control. A factor related to the accident was: the gusty/crosswind condition.NTSB MIA89FA109Accident · 2 fatalField investigationFinal reportCessna 172M · Pascagoula, MSContinued flight by the pilot into instrument meteorological conditions (IMC). Contributing factors were: inadequate preflight planning, weather conditions, pilot's lack of instrument flight time, lack of visual cues at night, and trees at the crash site.NTSB MIA87LA132Accident · No injuriesLimited investigationFinal reportCessna 172M · Clarksdale, MSThe pilot stated that while flying at a low altitude over a dried up lake bed the aircraft collided with an unmarked telephone wire. A landing was made in a field where damaged was inspected. The pilot then elected to takeoff and return to the departure…NTSB ATL81FA030Accident · 6 fatalClosedCessna 172M · Aberdeen, MSNTSB MIA78FKQ04Accident · Minor injuriesClosedCessna 172 · Natchez, MSNTSB MIA77FA023Accident · 1 fatalClosedCessna 172 · Wiggins, MSNTSB MIA76FKQ43Accident · No injuriesClosedCessna 172M · Holly Bluff, MSNTSB MIA75KKQ23Accident · No injuriesClosedCessna 172 · Greenville, MS