NTSB investigations: Cessna 172M
107 cases on aircraft the registry lists as Cessna 172M, where the first occurrence was “Loss of control - on ground/water”. 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
| 1982 | 5 |
|---|---|
| 1983 | 6 |
| 1984 | 6 |
| 1985 | 2 |
| 1986 | 6 |
| 1987 | 4 |
| 1988 | 1 |
| 1989 | 2 |
| 1990 | 4 |
| 1991 | 5 |
| 1992 | 5 |
| 1993 | 4 |
| 1994 | 2 |
| 1995 | 6 |
| 1996 | 3 |
| 1997 | 3 |
| 1998 | 6 |
| 1999 | 1 |
| 2000 | 4 |
| 2001 | 9 |
| 2002 | 7 |
| 2003 | 4 |
| 2004 | 2 |
| 2005 | 2 |
| 2006 | 6 |
| 2007 | 2 |
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 ('2072418')
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\" = 260))
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 ('2072418')
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" = 260))
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 CHI07CA296Accident · Minor injuriesData collectionFinal reportCessna 172 Skyhawk · Stockton, MOThe pilot's improper recovery from a bounced landing, her subsequent loss of control of the airplane, and the inadvertent stall.NTSB LAX07CA169Accident · No injuriesData collectionFinal reportCessna 172M · St. George, UTthe pilot's inadequate compensation for a gusting crosswind and his failure to maintain directional control.NTSB DFW07CA046Accident · No injuriesData collectionFinal reportCessna 172M · Houston, TXThe pilot's failure to compensate for the existing wind conditions during the landing roll resulting in a loss of control. A contributing factor was the crosswind.NTSB SEA06CA103Accident · No injuriesData collectionFinal reportCessna 172M · Hamilton, MTThe pilot's inadequate compensation for the wind conditions during the landing roll which resulted in his failure to maintain directional control. Factors included variable winds and gusty crosswinds.NTSB MIA06CA083Accident · No injuriesData collectionFinal reportCessna 172M · Vero Beach, FLThe pilot's failure to maintain directional control while executing a go-around in gusty conditions which resulted in the airplane veering off the runway, colliding with a ditch and nosing over.NTSB ATL06CA057Accident · No injuriesData collectionFinal reportCessna 172M · Newnan, GAThe student pilot's failure to maintain directional control on the landing roll out, resulting in the airplane veering off the right side of the runway and colliding with an airport runway sign.NTSB LAX06CA117Accident · No injuriesData collectionFinal reportCessna 172M · Prescott, AZthe pilot's inadequate compensation for the crosswind conditions and his failure to maintain directional control.NTSB DEN06CA033Accident · No injuriesData collectionFinal reportCessna 172M · Denver, COthe pilot's failure to align the airplane's nose into the direction of the wind while performing the pre-takeoff checklist. A contributing factor was the gusty wind conditions.NTSB IAD05LA087Accident · No injuriesLimited investigationFinal reportCessna 172M · Marysville, OHThe pilot's failure to maintain directional control during landing.NTSB CHI05CA123Accident · No injuriesData collectionFinal reportCessna C-172M · Madison, WIThe pilot's inadequate compensation for the wind conditions and his failure to maintain directional control. Factors were the gusty winds and the soft ground.NTSB FTW04LA145Accident · No injuriesLimited investigationFinal reportCessna 172 · Levelland, TXThe student pilot's failure to maintain directional control and his inadequate compensation for the winds.NTSB NYC04CA064Accident · No injuriesData collectionFinal reportCessna 172M · Cumberland, MDThe pilot's inadequate compensation for the crosswind while landing. A factor was the crosswind.NTSB ATL04LA040Accident · No injuriesLimited investigationFinal reportCessna 172 · Hickory, NCThe CFI inadequate supervision, and failure to maintain directional control during the attempted touch-and-go landing.NTSB LAX04CA023Accident · No injuriesData collectionFinal reportCessna 172M · Montague, CAthe pilot's inadequate compensation for the crosswind condition and failure to maintain directional control.NTSB ATL04LA018Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Sanford, NCThe student pilot's failure to maintain directional control on landing roll resulting in a collision with a ditch, and subsequent nose over.NTSB ATL03LA058Accident · No injuriesLimited investigationFinal reportCessna 172 M · Collegedale, TNThe student pilot's failure to maintain directional control, which resulted in a loss of control, impact with terrain and subsequent nose over.NTSB LAX03LA023Accident · No injuriesLimited investigationFinal reportCessna 172M · Mesquite, NVThe pilot's failure to maintain directional control during takeoff. A contributing factor was the ditch.NTSB ATL03LA005Accident · No injuriesLimited investigationFinal reportCessna 172 · Opa Locka, FLThe pilot' inadequate evaluation of weather information, and the selection of the wrong runway that resulted in an attempted takeoff with a tailwind and the subsequent loss of control during takeoff.NTSB ATL02LA151Accident · No injuriesLimited investigationFinal reportCessna 172M · Dahlonega, GAThe pilot's improper recovery from a bounced landing and failure to maintain directional control resulting in the airplane going off the left side of the runway and colliding with a ditch.NTSB LAX02LA199Accident · No injuriesLimited investigationFinal reportCessna 172M · Saint Johns, AZthe pilot's inadequate compensation for wind conditions resulting in a loss of directional control and collision with terrain. Related factors were the wind gusts, crosswind and soft terrain.NTSB LAX02LA070Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Payson, AZFailure of the pilot to maintain directional control of the airplane. A contributing factor was the premature raising of the flaps.NTSB FTW02LA067Accident · No injuriesLimited investigationFinal reportCessna 172 · Iraan, TXThe pilot's failure to maintain directional control during landing roll. Contributing factors were the pilot's selection of a downwind runway for landing, the tail wind condition, and his lack of total experience in the type of aircraft.NTSB ATL02LA039Accident · No injuriesLimited investigationFinal reportCessna 172M · Sanford, NCThe pilots failure to maintain directional control during landing roll that resulted in a collision with an airport sign. Factors were wet runway surface and wind gust.NTSB FTW02LA058Accident · No injuriesLimited investigationFinal reportCessna 172 · New Braunfels, TXThe student pilot's failure to maintain directional control of the airplane during the landing roll. A contributing factor was the soft terrain.NTSB NYC02LA035Accident · No injuriesLimited investigationFinal reportCessna 172M · Ravenna, OHThe student pilot's failure to maintain directional control.NTSB LAX02LA026Accident · No injuriesLimited investigationFinal reportCessna 172M · Chandler, AZFailure of the student pilot to maintain directional control during landing.NTSB LAX02LA017Accident · No injuriesLimited investigationFinal reportCessna 172M · Prescott, AZThe CFI's improper remedial action and failure to maintain directional control during landing in a strong crosswind condition.NTSB ATL02LA001Accident · No injuriesLimited investigationFinal reportCessna 172 · Goldsboro, NCThe student pilot's failure to maintain directional control during a touch-and-go landing.NTSB NYC01LA219Accident · No injuriesLimited investigationFinal reportCessna 172M · Danbury, CTAn inoperative airspeed indicator and the pilot's improper recovery from the bounced landing.NTSB FTW01LA161Accident · No injuriesLimited investigationFinal reportCessna 172 · Kingston, OKthe pilot's failure to maintain directional control during the takeoff roll, which required his evasive maneuver and resulted in a stall.NTSB MIA01LA161Accident · No injuriesLimited investigationFinal reportCessna 172M · Bennettsville, SCThe pilot's improper correction for wind conditions and his failure to maintain control of the airplane resulting in the airplane sliding off an embankment during taxi from landing.NTSB LAX01LA135Accident · No injuriesLimited investigationFinal reportCessna 172M · N. Las Vegas, NVThe pilot's inadequate compensation for the existing crosswind condition, and his failure to maintain runway alignment.NTSB NYC01LA063Accident · No injuriesLimited investigationFinal reportCessna 172M · Farmville, VAthe failure of the pilot to maintain directional control.NTSB CHI01LA051Accident · No injuriesLimited investigationFinal reportCessna 172M · Sturgis, SDThe pilot failed to maintain control of the airplane during takeoff and he discontinued an aborted takeoff once initiated. Factors associated with the accident were the inaccurate elevator trim indicator, the pilot's failure to verify the trim setting,…NTSB LAX00LA256Accident · No injuriesLimited investigationFinal reportCessna 172 · Chandler, AZfailure of the pilot-in-command to adequately compensate for a crosswind condition and maintain directional control during the landing roll, resulting in the airplane departing the runway and colliding with a sign.NTSB LAX00LA133Accident · No injuriesLimited investigationFinal reportCessna 172M · Sacramento, CAThe failure of the pilot to maintain directional control of the aircraft during the takeoff roll. A rough, uneven runway surface was a factor in the accident.NTSB ATL99LA090Accident · No injuriesLimited investigationFinal reportCessna 172M · Double Springs, ALThe pilot's failure to maintain directional control of the aircraft during landing. A factor was the pilot's lack of experience.NTSB FTW98LA387Accident · No injuriesLimited investigationFinal reportCessna 172M · Englewood, COThe pilot's failure to maintain directional control during landing. Factors were the runway light and the terrain conditions.NTSB IAD98LA076Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Somerset, KYthe pilot's failure to follow procedures to hand-prop the airplane.NTSB CHI98LA237Accident · No injuriesLimited investigationFinal reportCessna 172M · Chesterfield, MOthe pilot's not obtaining and maintaining directional control. A factor was wet terrain (grass).NTSB FTW98LA219Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Albuquerque, NMThe flight instructor's failure to maintain directional control of the aircraft. Factors were crosswind, high wind conditions, insufficient demonstrated crosswind component information provided by the manufacturer, and insufficient aircraft…NTSB LAX98LA143Accident · No injuriesLimited investigationFinal reportCessna 172M · Henderson, NVThe pilot's decision to attempt a landing in crosswind conditions at or above the demonstrated capability of the aircraft, and his subsequent failure to maintain proper runway alignment.NTSB NYC98LA081Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Weyers Cave, VAthe pilot's inadequate compensation for crosswind conditions and failure to maintain directional control of the airplane during the landing roll, which resulted in an encounter with a fence on uneven terrain and a nose over.NTSB FTW98LA057Accident · No injuriesLimited investigationFinal reportCessna 172M · Mesquite, TXthe pilot's inadequate compensation for wind conditions and failure to maintain directional control of the airplane, while landing. The gusty crosswind was a related factor.NTSB MIA97LA165Accident · No injuriesLimited investigationFinal reportCessna 172 · Vero Beach, FLfailure of the pilot to ensure all articles in the aircraft were secured before flight, and subsequently, an oil can becoming lodged under the rudder pedals and preventing her from controlling the aircraft during landing.NTSB LAX97LA113Accident · No injuriesLimited investigationFinal reportCessna 172M · Petaluma, CAThe pilot's inadequate compensation for the crosswind condition and his failure to maintain directional control.NTSB FTW97LA008Accident · No injuriesLimited investigationFinal reportCessna 172M · Tuttle, OKfailure of the pilot to maintain directional control during takeoff roll, which resulted in a ground swerve. Factors relating to the accident were: tall grass along the edges of the runway, and the proximity of the fence, fence posts, and trees.NTSB LAX96LA314Accident · No injuriesLimited investigationFinal reportCessna 172M · Truckee, CAthe student pilot's inadequate compensation for the existing crosswind condition and failure to maintain directional control. The encounter with a ditch was a related factor.NTSB NYC96LA075Accident · No injuriesLimited investigationFinal reportCessna 172M · Warehouse Point, CTthe pilot's inadequate compensation for the crosswind and gusts. The wind conditions were factors.NTSB CHI96LA062Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Excelsior Sprg, MOthe pilot's selection of the wrong runway for landing and the delayed aborted landing. Factors associated with the accident were the tailwind condition and the pilot's inadequate level-off.