NTSB investigations: Cessna 172N, MO
27 cases on aircraft the registry lists as Cessna 172N. 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
| 1978 | 4 |
|---|---|
| 1979 | 2 |
| 1981 | 3 |
| 1982 | 2 |
| 1983 | 1 |
| 1984 | 2 |
| 1986 | 1 |
| 1989 | 1 |
| 1992 | 2 |
| 1993 | 2 |
| 1995 | 1 |
| 1998 | 1 |
| 2000 | 2 |
| 2003 | 1 |
| 2006 | 1 |
| 2010 | 1 |
Where
Latest 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\" = 'MO' 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 ('2072434'))
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" = 'MO' 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 ('2072434'))
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 CEN10CA336Accident · No injuriesData collectionFinal reportCessna 172N · Maryland Heights, MOThe pilot's improper flare, which resulted in a hard landing.NTSB CHI07CA004Accident · No injuriesData collectionFinal reportCessna 172N · St Charles, MOThe pilot's failure to properly judge the landing flare and his inadequate recovery from the resulting bounced landing. A contributing factor was the inadvertent pilot induced oscillation (porpoise) after initial runway contact.NTSB CHI03LA250Accident · No injuriesLimited investigationFinal reportCessna 172M · La Monte, MOThe pilot's misjudgment of speed and distance resulting in an overrun of the runway.NTSB CHI00LA117Accident · No injuriesLimited investigationFinal reportCessna 172N · Chesterfield, MOthe pilot misjudged the landing flare which resulted in the airplane porpoising on the runway during the landing.NTSB CHI00LA065Accident · No injuriesLimited investigationFinal reportCessna 172 · Chesterfield, MOThe pilot failed to maintain directional control during the takeoff portion of a touch and go landing.NTSB CHI98LA147Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Hannibal, MOa loss of engine power due to undetermined reasons. A factor was the rough field in which the forced landing was made.NTSB CHI95LA067Accident · No injuriesLimited investigationFinal reportCessna 172N · Kansas City, MOAn improper recovery from a bounced landing. Factors associated with the accident were an improper airspeed and not attaining a proper descent rate by the pilot.NTSB CHI94LA011Accident · No injuriesLimited investigationFinal reportCessna 172 · Independence, MOThe pilot's misjudgment of distance, altitude, and speed on final approach to land, and failure to maintain obstacle clearance from the vehicle. The proximity of the vehicle to the approach path was a related factor.NTSB CHI93LA229Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Point Lookout, MOThe pilot in command's failure to maintain proper glide path, and her failure to attain the proper touch down Point.NTSB CHI92LA207Accident · No injuriesLimited investigationFinal reportCessna 172N · Bates City, MOTotal failure of the airplane windshield.NTSB CHI92LA199Accident · No injuriesLimited investigationFinal reportCessna 172N · Chesterfield, MOThe improper use of the aircraft brake system by the pilot in command.NTSB MKC89LA100Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Wentzville, MOThe pilot's delay in aborting the landing, and his failure to maintain clearance from the power lines. Factors related to the accident were: the pilot's selection of the wrong runway, the adverse weather conditions, the pilot's failure to attain the proper…NTSB MKC86LA043Accident · No injuriesLimited investigationFinal reportCessna 172N · Kansas City, MOThe pilot had been at this airport 31 times since 1979. During his taxi to takeoff for a night flight, he mistook a service road for a taxiway. He taxied past one sign without seeing it but struck the second one. This is the third documented accident at this…NTSB MKC84LA187Accident · No injuriesLimited investigationFinal reportCessna 172N · Gainsville, MOThe pilot was taxiing the aircraft back to his hangar. Upon reaching the hangar he made a 180 degree turn to position the aircraft so he could push it backwards into the hangar. During the turn the left wing impacted a pole.NTSB MKC84LA065Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Kennett, MOThe acft crashed in IMC weather after the engine lost power due to fuel exhaustion. The plt had received a briefing on the weather prior to departure. Post accident investigation revealed less than 2 gallons of fuel remained aboard the acft.NTSB MKC83FA130Accident · 1 fatalField investigationFinal reportCessna 172N · South Fork, MOTakeoff was from a farm strip 1,600 ft long with grass 8 to 10 inches high. There are trees about 800 ft south of the south end of the strip. The acft took off to the south & made a left turn. After turning about 135 deg the bank abruptlysteepened, the nose…NTSB MKC82FCG19Accident · 2 fatalFinal reportCessna 172N · Lake Of The Oza, MOWitnesses reported that the pilot made a low pass at a cove, then flew out over the water, turned and flew back at low altitude. During a second low pass, it struck electrical cables that crossed the cove. After hitting the cables, the aircraft crashed in a…NTSB MKC82DA045Accident · No injuriesFinal reportCessna 172N · Thayer, MODuring takeoff, the pilot's seat slid full aft just as the aircraft became airborne. The pilot was unable to reach the rudders or powerplant controls and could not control the aircraft. The plane crashed into trees on the left side of the runway. No…NTSB MKC81FCA21Accident · No injuriesClosedCessna 172 · Fenton, MONTSB MKC81DCA16Accident · No injuriesClosedCessna 172 · Knox City, MONTSB MKC81FA032Accident · Minor injuriesClosedCessna 172 · Maryville, MONTSB MKC79FCA22Accident · No injuriesClosedCessna 172 · St Peters, MONTSB MKC79FCG28Accident · Serious injuriesClosedCessna 172N · Independence, MONTSB MKC78FCG70Accident · Minor injuriesClosedCessna 172 · Higginsville, MONTSB MKC78FCA44Accident · Minor injuriesClosedCessna 172 · De Soto, MONTSB MKC78FCA47Accident · Minor injuriesClosedCessna 172N · Pevely, MONTSB MKC78DCG19Accident · No injuriesClosedCessna 172 · Ozark, MO