Cessna 172N
NTSB investigations · 1,815
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 ('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_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 ('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 CHI94LA322Accident · No injuriesLimited investigationFinal reportCessna 172N · Boone, IAthe failure of both pilots to adequately monitor radio communications during an exceptionally busy period. Factors related to the accident were the high vegetation and the failure of airport personnel to recognize and correct a hazardous situation.NTSB MIA94LA205Accident · No injuriesLimited investigationFinal reportCessna 172N · Orlando, FLThe pilot-in-command's improper landing flare/touchdown, resulting in a hard landing, and subsequent separation of the nose gear.NTSB LAX94LA339Accident · No injuriesLimited investigationFinal reportCessna 172 · Lakeport, CAThe pilot's inadequate compensation for the existing cross wind conditions, and failure to maintain directional control of the airplane during landing rollout.NTSB CHI94LA296Accident · No injuriesLimited investigationFinal reportCessna 172 · Anoka, MNthe pilots decision to attempt a landing ahead of the approaching thunderstorm, and his failure to maintain directional control. A factor was the gusting crosswind ahead of the storm.NTSB LAX94LA334Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Mesa, AZThe student pilot's failure to maintain directional control by his improper use of the flight controls. Factors related to this accident were the pilot's lack of total experience and the crosswind.NTSB LAX94LA335Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Simi Valley, CAFuel exhaustion after the student pilot became lost/disoriented. Factors related to the accident were: failure of the supervising flight instructor (CFI) to follow the FAA approved syllabus, inadequate supervision by the company/operator management, darkness,…NTSB LAX94LA305Accident · No injuriesLimited investigationFinal reportCessna 172N · Cameron Park, CAthe pilot's improper use of the elevator control during the landing flare.NTSB FTW94LA251Accident · No injuriesLimited investigationFinal reportCessna 172N · Englewood, COAn inadvertent stall. A factor was the pilot's excessive flare.NTSB NYC94LA132Accident · No injuriesLimited investigationFinal reportCessna 172N · Chatham, MAThe pilot's failure to see and avoid the birds. The presence of the birds at the airport was a contributing factor.NTSB NYC94FA126Accident · 2 fatalField investigationFinal reportCessna 172N · Trout Run, PAthe delayed decision of the pilot to deviate from known weather which resulted in an inflight loss of control and impact with terrain.NTSB NYC94LA108Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Bristol, NHthe failure of maintenance personnel to remove an object from the carburetor heat duct during annual inspection which blocked induction air and resulted in the loss of engine power, and the subsequent collision with the terrain during a forced landing.NTSB LAX94LA269Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Schurz, NVthe pilot's inability to maintain an adequate airspeed in the takeoff initial climb due to an encounter with a windshear.NTSB CHI94LA211Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Lambertville, MIthe pilot-in-command's not maintaining airspeed. A factor was the pilot-in-command's misjudging the flare.NTSB CHI94LA205Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Lambertville, MIThe inadequate maintenance of the airplane resulting in a foreign object in the induction system.NTSB LAX94LA238Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Valencia, CAthe pilot's selection of an unsuitable field for an off-airport landing and attempted takeoff.NTSB LAX94LA231Accident · 1 fatalLimited investigationFinal reportCessna 172N · Roosevelt, AZthe pilot's selection of an inadequate terrain clearance altitude while maneuvering over a lake. A factor in the accident was the calm glassy water conditions which may have affected the pilot's perception of his actual height above the water.NTSB CHI94LA178Accident · 1 fatalLimited investigationFinal reportCessna 172N · Richmond, INInadequate visual lookout by the pilots of both airplanes.NTSB ATL94LA107Accident · No injuriesLimited investigationFinal reportCessna 172N · Hartford, ALThe student pilot's inadequate compensation for gusting wind conditions during the approach to land. Factors were the instructor pilot's inadequate supervision of his student, the gusting wind conditions, and the trees located in close proximity to the runway.NTSB NYC94LA092Accident · No injuriesLimited investigationFinal reportCessna 172N · Fredericksburg, VAThe pilot's premature lift-off, resulting in an inadvertent stall/mush back onto the runway, and the pilot's failure to maintain directional control during the aborted takeoff, which resulted in the airplane veering off the runway and colliding with a dirt…NTSB CHI94LA171Accident · No injuriesLimited investigationFinal reportCessna 172N · Mackinac Island, MIExcessive airspeed and a failure to attain the proper touchdown point on the runway. Factors related to the accident were the wet runway and the fence which was contacted.NTSB FTW94LA173Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Page, AZThe total loss of engine power for undetermined reason. A factor was the lack of suitable terrain at the pilot's disposal.NTSB LAX94LA219Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Arvin, CAa fatigue failure of the crankshaft gear teeth.NTSB SEA94LA113Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Monarch, MTPoor in flight planning/decision. A factor to the accident was downdrafts.NTSB LAX94LA215Accident · No injuriesLimited investigationFinal reportCessna 172N · Sedona, AZThe cfi's improper level off during landing. The tailwind was a factor.NTSB LAX94FA185Accident · 1 fatalField investigationFinal reportCessna 172N · Julian, CAImproper planning/decision by the pilot(s). Factors related to the accident were: the high/mountainous terrain and adverse weather conditions.NTSB BFO94LA061Accident · No injuriesLimited investigationFinal reportCessna 172N · Clarksburg, WVthe pilot's selection of a downwind runway, and his inadequate compensation for the wind conditions. A factor was the gusting tailwind.NTSB LAX94LA176Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Gasquet, CAThe failure of the pilot to adequately compensate for the cross- wind conditions, and to maintain proper alignment with the runway.NTSB MIA94LA104Accident · No injuriesLimited investigationFinal reportCessna 172N · Stuart, FLPoor in-flight planning/decision by the pilot-in-command. Contributing to the accident was wind information disregarded by the pilot-in-command.NTSB LAX94LA154Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Prescott, AZThe student pilot's delayed flare and failure to maintain directional control of the aircraft, and the flight instructor's inadequate supervision of the flight.NTSB SEA94LA070Accident · No injuriesLimited investigationFinal reportCessna 172 · Casper, WYThe pilot's failure to maintain proper alignment with the runway. The crosswind was of factor.NTSB FTW94LA083Accident · No injuriesLimited investigationFinal reportCessna 172N · Georgetown, ARA carburetor icing induced power loss due to the pilot's improper use of carburetor heat in conditions conducive to carburetor icing. A factor was the lack of suitable terrain onto which a forced landing could be executed.NTSB MIA94GA099Incident · No injuriesFinal reportCessna 172N · Opa-Locka, FLInadequate maintenance inspection and lubrication of the flap rollers which resulted in the left flap inboard roller becoming jammed in the track during flap retraction.NTSB LAX94LA103Accident · No injuriesLimited investigationFinal reportCessna 172N · Livermore, CAThe student pilot's failure to maintain directional and his improper use of the rudder. The student pilot's failure to raise the flaps, the prevailing 90-degree crosswind, and his lack of total experience are factors in this accident.NTSB FTW94FA060Accident · 5 fatalField investigationFinal reportCessna 172N · Pearland, TXInadequate visual lookout by the pilot of the hawk BM-4, which resulted in his failure to see-and-avoid the Cessna 172. The BM-4 pilot's non-standard procedure for entering the traffic pattern was a related factor.NTSB LAX94LA086Accident · No injuriesLimited investigationFinal reportCessna 172N · El Monte, CAThe pilot's delayed decision to abort the takeoff and improper use of the airplane's throttle.NTSB CHI94LA053Accident · No injuriesLimited investigationFinal reportCessna 172 · Kimball, NEthe pilot's failure to maintain directional control during the landing roll. A factor related to the accident was the pilot's lack of total flight experience.NTSB NYC94LA041Accident · No injuriesLimited investigationFinal reportCessna 172N · Bar Harbor, MEA disconnected fuel line with the carburetor not installed, and improper dispatch of the aircraft.NTSB FTW94LA037Accident · No injuriesLimited investigationFinal reportCessna 172N · Albuquerque, NMThe pilot's improper flare.NTSB SEA94LA033Accident · No injuriesLimited investigationFinal reportCessna C-172N · Idaho Falls, IDThe pilot's failure to attain the proper touchdown point. Factors include tailwind conditions and an airport perimeter fence.NTSB FTW94FA034Accident · Serious injuriesField investigationFinal reportCessna 172N · Fort Collins, COPower loss due to throttle linkage disconnect. Factors were missing cotter key, improper maintenance, and the lack of suitable terrain for the forced landing.NTSB LAX94LA032Accident · No injuriesLimited investigationFinal reportCessna 172N · Joshua Tree, CAthe pilot's failure to maintain a proper descent rate on final approach. A factor in the accident was the student's limited total experience.NTSB FTW94LA017Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Woodville, TXFailure of the pilot in command to maintain control of the aircraft during an aborted landing.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 SEA94LA013Accident · No injuriesLimited investigationFinal reportCessna 172N · Renton, WAThe student pilot's failure to maintain directional control during landing. The crosswind was a factor.NTSB LAX94FA007Accident · 1 fatalField investigationFinal reportCessna 172N · Sedona, AZthe pilot's decision to continue VFR at an improper altitude into mountainous terrain at night and the inadvertent encounter with clouds along the route. Self-induced pressure due to a low fuel state contributed to the accident.NTSB SEA93FA214Accident · 3 fatalField investigationFinal reportCessna 172N · Ellensburg, WAThe pilot's failure to maintain an airspeed above stalling speed (vs), and his inadequate remedial action. Factors include the pilot's diverted attention, and an inadvertent stall/spin.NTSB BFO93LA170Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Tangier Island, VAFailure of the pilot to maintain control of the aircraft during a go-around. A factor related to the accident was: the crosswind condition.NTSB ATL93LA152Accident · No injuriesLimited investigationFinal reportCessna 172 · N. Myrtle Beach, SCThe failure of the engine exhaust valve which resulted in the loss of engine power. The soft terrain in the landing area was a factor.NTSB SEA93LA193Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Price, UTThe failure of the pilot to maintain airspeed above stall.NTSB SEA93FA179Accident · 1 fatalField investigationFinal reportCessna 172N · Lake Fork, IDPoor judgment of the pilot by flying while under the influence of alcohol and a drug, his continued flight into an area of adverse weather, and his failure to maintain adequate clearance (or altitude) from mountainous terrain. Factors related to the accident…
Back to Cessna 172N