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 NYC93LA058Accident · No injuriesLimited investigationFinal reportCessna 172M · Bedford, PAThe pilot attempted to land in a cross wind, lost control of the airplane, landed off the runway, swerved towards a hanger after going threw a snow bank resulting in the left wing striking the hanger.NTSB FTW93LA074Accident · No injuriesLimited investigationFinal reportCessna 172M · Baytown, TXThe loss of power due to a stuck exhaust valve in the number 3 cylinderNTSB LAX93LA091Accident · Serious injuriesLimited investigationFinal reportCessna 172 · San Jacinto, CAThe flight's encounter with unforecast clear air turbulence.NTSB LAX93FA068Accident · 3 fatalField investigationFinal reportCessna 172M · Laie, HIThe pilot's inadvertent flight into a mountainous area where he lost visual reference to illuminated ground features which resulted in his becoming disoriented. Factors which contributed to the accident were: 1) the dark sky and low cloud conditions; 2) the…NTSB FTW93FA039Accident · 1 fatalField investigationFinal reportCessna 172M · Snook, TXThe pilot's intentional flight into instrument meteorological conditions as a result of his alcoholic and drug impairment of efficiency and judgement. Factors contributing to the accident were: the pilot's failure to obtain weather information, the dark night…NTSB SEA93LA024Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Vancouver, WAThe pilot's inability to see birds due to darkness.NTSB SEA93LA021Accident · No injuriesLimited investigationFinal reportCessna 172M · Olympia, WAThe pilot's poor inflight decision, and excessive airspeed on final. Factors include a wet turf runway, and trees adjacent to the runway.NTSB NYC93LA035Accident · No injuriesLimited investigationFinal reportCessna 172M · Mallory, WVThe pilot failed to maintain control of the airplane, which resulted in the airplane departing the runway and striking a tree.NTSB MIA93WA008Accident · No injuriesForeign investigationCessna 172M · Mayaguana Isl, BahamasNTSB DEN93LA019Accident · No injuriesLimited investigationFinal reportCessna 172 · Colorado Spring, COProper descent rate was not maintained by the pilot in command which resulted in a hard landing.NTSB LAX93FA007Accident · 1 fatalField investigationFinal reportCessna 172M · Fairfield, CAThe pilot's delay in initiating a go-around during a night landing. Factors related to the accident were: the pilot misjudging distance and speed resulting a overshooting the touchdown, the night light condition, his lack of night flying experience in a…NTSB DEN93LA004Accident · No injuriesLimited investigationFinal reportCessna 172M · Addison, TXThe attempt by both pilots to pass each other without adequate clearance between their airplanes.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 DEN92FA093Accident · 1 fatalField investigationFinal reportCessna 172M · Evanston, WYLoss of control for undetermined reasons.NTSB ATL92LA178Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Boone, NCThe pilot's failure to abort the take off, and his abrupt pull up with insufficient airspeed to continue flight. Factors were the inadequate airspeed and the inadvertent stall.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 BFO92LA120Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Mount Vernon, OHThe pilot's failure to maintain airspeed which resulted in a stall.NTSB BFO92LA111Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Charleston, WVThe pilot's failure to attain adequate airspeed to outclimb obstacles.NTSB ANC92LA110Accident · No injuriesLimited investigationFinal reportCessna 172 · Twin Hills, AKThe pilot in command not following the procedures outlined in the pilot's operating handbook.NTSB BFO92LA097Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Bedford, PAThe pilot failed to maintain adequate airspeed which resulted in a stall.NTSB CHI92FA201Accident · 4 fatalField investigationFinal reportCessna 172M · St Paul, MNInadequate visual lookout by the pilots of both airplanes, which resulted in their failure to see-and-avoid conflicting traffic, and failure of the relieving controllers to use the radar display to identify and sequence an airplane entering the pattern.…NTSB CHI92LA168Accident · No injuriesLimited investigationFinal reportCessna 172M · Hastings, MIThe pilot-in-command's misjudgement of the touchdown point which resulted in an undershoot and damage to the elevator. In addition, the pilot-in-command failed to properly inspect the airplane for damage prior to further flight.NTSB ANC92LA089Accident · No injuriesLimited investigationFinal reportCessna 172 · Anchorage, AKInadequate visual look out by the pilot of both aircraft. Contributing to the accident were the pilot's diverted attention, the other moving aircraft/object (c 172), and the excessive taxi speed of the c 172.NTSB NYC92LA105Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Buffalo, NYThe pilot's failure to maintain airspeed during a go around, which resulted in an inadvertent stall and in flight collision with terrain. Contributing to the accident was the pilot delayed the go around and lack of recent flight expereince.NTSB NYC92LA104Accident · No injuriesLimited investigationFinal reportCessna 172N · Dexter, MEA failure of the top torque link bolt on the nose landing gear which resulted in a landing with a flat strut and misaligned wheel.NTSB CHI92LA151Accident · No injuriesLimited investigationFinal reportCessna 172M · Climax Springs, MODelay in aborting the landing by the pilot in command.NTSB FTW92LA124Accident · No injuriesLimited investigationFinal reportCessna 172M · Canton, TXThe pilot's failure to maintain adequate airspeed and directional control during the attempted go around following an encounter with adverse wind conditions on approach.NTSB BFO92LA053Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Amelia, VAThe pilot's misjudgement of distance and altitude that resulted in an landing overrun and collision with an embankment. Contributing was failure to initiate a go around and inadequate supervision.NTSB SEA92FA083Accident · 1 fatalField investigationFinal reportCessna 172M · Shaw Island, WAA delayed go-around, and procedures not being followed. Factors include a lack of total experience in this type of operation, trees near the runway, and an uphill runway slope.NTSB FTW92LA114Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Stuttgart, ARThe pilot's failure to compensate for wind conditions. Factors were the crosswind and the downdraft.NTSB CHI92LA121Accident · No injuriesLimited investigationFinal reportCessna 172M · Osage Beach, MOThe pilot-in-command's failure to use all th eavailable runway and his misjudgment of the proper touchdown point during landing.NTSB FTW92FA098Accident · 1 fatalField investigationFinal reportCessna 172M · Oklahoma City, OKInadvertent stall during aborted landing. Factors were the tailwind, the pilot's selection of the wrong runway for existing wind conditions and his long landing.NTSB CHI92LA099Accident · No injuriesLimited investigationFinal reportCessna 172 · Manhattan, KSThe pilot's failure to refuel the airplane. A factor related to the accident was the rough terrain on which the landing was made.NTSB NYC92LA069Accident · No injuriesLimited investigationFinal reportCessna 172M · Sanford, METhe failure of the pilot of N64147 to maintain adequate spacing and visual lookout from N6544G while taxiing, resulting in a ground collision.NTSB CHI92FA062Accident · 2 fatalField investigationFinal reportCessna 172M · Sanford, MIThe pilot-in-command's failure to maintain a visual lookout to avoid a wire strike. Factors were the pilot-in-command's intentional low level flight, his failure to maintain proper altitude, and the transmission wires.NTSB NYC92LA046Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Lockport, NYAn inadvertent stall during an attempted go-around by the second pilot. Factors related to the accident were improper use of the flight controls by both pilots and the second pilot's attempted control of the airplane.NTSB SEA92FA022Accident · Serious injuriesField investigationFinal reportCessna 172M · Vancouver, WAInadequate visual lookout on the part of the pilot as well as both the flight instructor and student of the other aircraft. A factor contributing to the accident was the other pilot's lack of landing light usage.NTSB DEN92LA009Accident · No injuriesLimited investigationFinal reportCessna 172N · Boulder, COFailure of the pilot to maintain clearance from the sign.NTSB CHI92LA029Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Howell, MIProper glidepath was not maintained resulting in an undershoot. A factor related to the accident was dark night flying conditions.NTSB LAX92FA043Accident · 3 fatalField investigationFinal reportCessna 172M · Carmel Valley, CAThe pilot's failure to maintain a safe altitude above the ground during an intentional low altitude flight in mountainous terrain. Contributing factors related to the pilot becoming distracted while flying over the ground and to his failure to initiate a…NTSB FTW92LA017Accident · No injuriesLimited investigationFinal reportCessna 172M · Springer, NMThe pilot's poor judgement in attempting flight into forcasted adverse weather, his disregard for the hazardous weather advisory received which resulted in partial loss of engine power as a result of a blocked induction system due to ice and snow, and the…NTSB SEA92LA010Accident · No injuriesLimited investigationFinal reportCessna 172C · Colville, WAThe pilot's delayed go-around. Factors contributing to the accident was the pilot's misjudgement of distance and speed during the approach.NTSB DEN92LA002Accident · No injuriesLimited investigationFinal reportCessna 172M · Erie, COThe pilot's failure to maintain directional control land his inadequate compensation for wind conditions. Factors were: crosswind conditions and the pilot's total lack of experience.NTSB ANC92FA002Accident · No injuriesField investigationFinal reportCessna 172M · Bethel, AKA power loss over unsuitable terrain which resulted in a nose over.NTSB BFO91LA086Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Grayson, KYThe pilot's failure to maintain control of the aircraft during the attempted go-around.NTSB NYC91LA236Accident · No injuriesLimited investigationFinal reportCessna 172M · Norwood, MAPremature retraction of the wing flaps during a go-around which resulted in an inadvertent stall with insufficient altitude for recovery. Factors related to the accident were: the pilot's lack of total experience in make and model, and lack of recent…NTSB CHI91FA254Accident · 2 fatalField investigationFinal reportCessna 172M · Ottumwa, IAImproper IFR procedure by the pilot by not maintaining the proper minimum descent altitude (mda) until established on the ILS localizer and glidepath.NTSB ATL91LA146Accident · No injuriesLimited investigationFinal reportCessna C172M · Mc Minnville, TNThe failure of the pilot to maintain cleearance from obstacles during the final approach to landing.NTSB NYC91FA188Accident · Serious injuriesField investigationFinal reportCessna 172M · Phillips, MEAn inadvertent stall and loss of control due to the pilot's improper use of the wing flaps for takeoff. Factors related to the accident were: the pilot's misunderstanding of airplane performance, and the pilot's decision to takeoff uphill.NTSB SEA91LA192Accident · No injuriesLimited investigationFinal reportCessna 172M · Little Rock, WAA delayed go-around, and airspeed not being maintained. Factors include the pilot's overconfidence in the aircraft's ability, the pilot's lack of total experience in this type of operation, misjudged clearance, and the use of improper procedure.
Back to Cessna 172M