Cessna 172M
NTSB investigations · 1,699
Matched to the registry by N-number and event date, newest first.
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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.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_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.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 DEN90LA075Accident · No injuriesLimited investigationFinal reportCessna 172 · Elkhorn, MTThe pilot's decision to attempt flight in terrain and conditions which exceeded the performance capabilities of the airplane.NTSB LAX90LA118Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Redding, CAThe pilot's decision not to use full flaps which resulted in a long landing on a wet runway.NTSB FTW90FA063Accident · 1 fatalField investigationFinal reportCessna 172M · Tomball, TXFailure of the pilot in Cessna 150, N714RS, to comply with the air traffic control clearance, and failure of both pilots to maintain adequate visual lookout to see-and-avoid each other. Factors related to the accident were: physical impairment of the pilot in…NTSB LAX90LA078Accident · No injuriesLimited investigationFinal reportCessna 172 · Inyokern, CAImproper in-flight planning/decision by the pilot-in-command (PIC), and his failure to maintain adequate airspeed while maneuvering, which resulted in an inadvertent stall/mush.NTSB FTW90LA057Accident · No injuriesLimited investigationFinal reportCessna 172M · Goliad, TXThe pilot in command's failure to identify and correct for carburetor icing conditions which existed at the time of the accident and precipitated the precautionary landing.NTSB NYC90LA056Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Danbury, CTImproper maintenance, inadequate surveillance by the company/operator, and inadequate preflight by the pilot, which resulted in a fire during an attempted engine start. A factor related to the accident was: the unsecured fuel line.NTSB LAX90LA063Accident · No injuriesLimited investigationFinal reportCessna 172M · Apple Valley, CAThe failure of the pilot of the Mooney to stop his aircraft in a timely manner to avoid a collision.NTSB SEA90LA031Accident · No injuriesLimited investigationFinal reportCessna 172M · Salem, ORThe pilots inadequate visual lookout while taxiing. Factors related to the accident are: the pilot's diverted attention and the pole.NTSB CHI90FA040Accident · 4 fatalField investigationFinal reportCessna 172M · Linden, MIThe failure of the pilot to maintain sufficient speed for flight. A factor associated with the accident was the pilot's operation of the airplane above the maximum allowable gross weight.NTSB FTW90LA029Accident · No injuriesLimited investigationFinal reportCessna 172 · Port Allen, LAFuel system contamination due to inadequate maintenance/service of the airplane.NTSB MKC90LA031Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Osage City, KSThe pilot misjudged distance and altitude to the runway while on final approach to land. Factors related to the accident were: dark night and static wires.NTSB SEA90FA133Accident · 1 fatalField investigationFinal reportCessna 172M · Snoqualmie, WAIntentional flight into known adverse weather conditions and poor weather evaluation by the pilot.NTSB CHI90LA022Accident · No injuriesLimited investigationFinal reportCessna 172 · Lansing, ILThe pilot's inadvertent selection of unsuitable terrain (taxiway/construction area). The steel marker poles contributed to the aircraft damage.NTSB MKC90LA010Accident · No injuriesLimited investigationFinal reportCessna 172 · Omaha, NEFailure of the throttle cable assembly which resulted in a forced landing and subsequent collision with a fence.NTSB CHI90LA010Accident · No injuriesLimited investigationFinal reportCessna 172M · Cedarburg, WIDelay of the flight instructor (CFI) in making a go-around and his failure to attain sufficient airspeed to climb after taking off again. The transmission wire (power line) and high vegetation were contributing factors.NTSB FTW89LA158Accident · No injuriesLimited investigationFinal reportCessna 172M · Bellville, TXImproper flare by the pilot and his improper recovery from a bounced landing, which resulted in an inadvertent porpoise and subsequent nose gear failure.NTSB MKC89LA186Accident · No injuriesLimited investigationFinal reportCessna 172 · Clear Lake, MNThe pilot's improper decision in attempting to land with inadequate visual cues which precluded identification of a correct runway alignment. A suitable alternative airport was readily available.NTSB MIA89WA222Accident · No injuriesForeign investigationCessna 172M · Grand Turk Isl., Turks & Caicos IslandsNTSB DEN89FA184Accident · 1 fatalField investigationFinal reportCessna 172M · Albuquerque, NMThe pilot deliberately flew his aircraft into the face of a mountain. A contributing factor was: the psychological condition of the pilot.NTSB DEN89LA187Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Ruidoso, NMThe pilot's improper use of the mixture control and carburetor heat during a takeoff in high density altitude conditions. Contributing to the accident was the high density altitude.NTSB MIA89LA211Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Apalachicola, FLFailure of the pilot to maintain proper altitude. A factor related to the accident was: the pilot's lack of visual perception concerning altitude above the water.NTSB SEA89LA152Accident · No injuriesLimited investigationFinal reportCessna 172M · Carson City, NVThe student pilot's improper compensation for wind conditions, and improper recovery from a bounced landing. Factors related to the accident were: the adverse wind condition and the student's lack of total flying experience.NTSB LAX89LA256Accident · No injuriesLimited investigationFinal reportCessna 172M · Marana, AZInadequate preflight by the student pilot, inadequate supervision by the flight instructor (CFI), and fuel exhaustion due to lack of fuel. Related factors were: inoperative left fuel quantity gage, the cfi's decision to make the flight with a known deficiency…NTSB CHI89LA149Accident · No injuriesLimited investigationFinal reportCessna 172M · Wixom, MICarburetor ice due to the pilot's improper use of carburetor heat. Factors related to the accident were: weather conditions conducive to carburetor ice, dark night, and tree(s) in the emergency landing area.NTSB MIA89LA190Accident · No injuriesLimited investigationFinal reportCessna 172M · Perry, FLFailure of the number three exhaust valve which necessitated a forced landing. The trees were considered to be a contributing factor.NTSB MKC89LA157Accident · No injuriesLimited investigationFinal reportCessna 172 · Crystal, MNAircraft control was not maintained by the pilot in command, due to an improper landing flare which resulted in several bounces. The landing gear failed in overload during the bounced landing.NTSB DEN89LA157Accident · No injuriesLimited investigationFinal reportCessna 172M · Bicknell, UTFailure of the pilot to maintain adequate airspeed, which resulted in a stall. Factors related to the accident were: the pilot's selection of an unsuitable area (terrain) to land, unfavorable wind, & objects (fence & irrigation sprinkler).NTSB CHI89LA121Accident · No injuriesLimited investigationFinal reportCessna C172M · Wadsworth, OHPilot's poor planning/decision making during the approach and landing phase of flight, which resulted in a long landing and runway overrun.NTSB CHI89LA118Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Indianapolis, INFuel contamination from a deteriorating part in the carburetor. The trees and improper maintenance/servicing of the aircraft were probable contributing factors.NTSB DEN89LA143Accident · No injuriesLimited investigationFinal reportCessna 172M · Boulder, COInadequate compensation for wind conditions by the (private rated) dual student and his failure to maintain directional control, which resulted in an inadvertent ground swerve, and inadequate supervision by the instructor pilot (CFI). A factor related to the…NTSB MKC89FA117Accident · Serious injuriesField investigationFinal reportCessna 172M · Oakland, ARPilot electing to buzz persons on the lake at low altitude and colliding with power lines.NTSB MIA89LA152Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Okeechobee, FLThe pilot's poor preflight preparation when he failed to recheck weather conditions after he delayed takeoff because of thunderstroms. Also, the pilot's poor inflight decision to land off-airport rather than return to the departure airport.NTSB NYC89FA135Accident · 2 fatalField investigationFinal reportCessna 172M · Bradford, VTFailure of the rated pilots in both aircraft to see and avoid a midair collison.NTSB NYC89LA117Accident · No injuriesLimited investigationFinal reportCessna 172M · Palmyra, PAThe pilot misjudged the airspeed and distance during the landing.NTSB MIA89LA128Accident · No injuriesLimited investigationFinal reportCessna 172M · West Palm Beach, FLFailure of the pilot to insure adequate wingtip clearance while taxiing.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 LAX89LA139Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Santa Barbara, CAThe improper inflight planning/decisions by the plt when he decided to intentionally fly low over rough water in the pacific ocean and the partial loss of power for undetermined reasons.NTSB CHI89DEP02Accident · No injuriesFinal reportCessna 172M · West Bend, WIPartial failure of the throttle cable. Unsuitable (soft) terrain and transmission wires in the landing area were considered to be factors.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 FTW89LA068Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Galveston, TXFailure of the pilot to maintain sufficient airspeed, which resulted in a stall and loss of control. Contributing factors were: the weather conditions, which were below minimums, and failure of the pilot to perform a missed approach.NTSB ATL89LA103Accident · No injuriesLimited investigationFinal reportCessna 172M · Sanford, NCCarburetor ice due to the failure of the pilot to properly use the carburetor heat control during descent and flight in the traffic patterns at reduced power. Underlying this is inadequate training in the proper understanding of carburetor icing and the…NTSB LAX89LA109Accident · No injuriesLimited investigationFinal reportCessna 172M · Sacramento, CAThe pilot's selection of the wrong runway for landing and his delay in initiating a go-around after landing long. Contributing factors were: light conditions as dusk and a tailwind.NTSB MIA89LA084Accident · No injuriesLimited investigationFinal reportCessna 172M · San Juan, PRThe failure of the pilot to properly use carburetor heat in conditions conducive to the formation of carburetor ice.NTSB NYC89LA076Accident · No injuriesLimited investigationFinal reportCessna 172 · Seneca Falls, NYFailure of the pilot of the C-150, N17109, to maintain proper separation from other aircraft during landing at an uncontrolled airport.NTSB LAX89FA091Accident · 1 fatalField investigationFinal reportCessna 172M · Oxnard, CAContinued VFR flight by the pilot into instrument meteorlogical conditions which resulted in an in-flight collsion with terrain. Related factors were: failure of the pilot to use a preflight briefing service, his decision to initiate flight into known adverse…NTSB DEN89LA054Accident · No injuriesLimited investigationFinal reportCessna 172M · Erie, COThe pilot said that he made a normal preflight and engine runup prior to takeoff on runway 33 at the tri-county airport, Erie, Colorado. A normal takeoff was made but he said that as the aircraft reached 200 feet, the engine lost about 400 RPM. When he…NTSB NYC89LA037Accident · No injuriesLimited investigationFinal reportCessna 172 · Block Island, RIThe pilot of the Cessna 182 was on downwind when he stated that he pulled the carburetor heat on and then pulled the power back to 1500 RPM. Within a few seconds the engine quit and the pilot informed the tower. The aircraft landed about 500 feet short of the…NTSB ATL89LA049Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Griffin, GAAfter a preflight and runup the pilot made a takeoff and remained in closed traffic for landing practice. On downwind, opposite the desired point of touchdown, he retarded power, applied carb heat and slowed the airplane. Turning base, the acft lost power.…NTSB ATL89LA021Accident · No injuriesLimited investigationFinal reportCessna 172M · Hilton Head Is., SCThe plt reported that the airplane lost power shortly after takeoff. A forced ldg was subsequently made in a swamp near the arpt. The airplane nosed over during rollout. Post-crash exam of the airplane revealed that the throttle cable outer casing had become…NTSB DEN89LA022Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Peyton, COA practice touch and go landing was being made on rwy 15, with winds reported as gusting to 20 knots. During the takeoff, the wing flaps would not retract and the aircraft climbed to 15 ft AGL. The pilot said he attempted to land after flying 500 yards and…
Back to Cessna 172M