Cessna 172
NTSB investigations · 1,097
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 ('2072402')
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 ('2072402')
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 IAD99LA018Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Essex, MDA loss of engine power for undetermined reasons. Factors were the lack of suitable terrain for a forced landing and dark night conditions.NTSB FTW98FA384Accident · 2 fatalField investigationFinal reportCessna 172 · West Jordan, UTThe pilot's failure to maintain proper airport traffic pattern altitude. Factors were night lighting conditions and the unseen static line.NTSB ATL98LA120Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Sewanee, TNThe inadequate visual lookout by the ground pedestrian. A factor was dark night conditions.NTSB ANC98LA131Accident · No injuriesLimited investigationFinal reportCessna 172 · Palmer, AKFatigue of the forward end of the engine crankshaft resulting in separation of the propeller assembly, and the operator's failure to comply with a required maintenance procedure. A factor was uneven terrain.NTSB ATL98LA104Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Ocean Isle Bch, NCThe pilot's inadequate inflight planning that resulted in excessive airspeed and altitude for a full stop landing.NTSB SEA98LA154Accident · 1 fatalLimited investigationFinal reportCessna 172 · Baker City, ORThe pilot's failure to maintain terrain clearance and inadequate in-flight planning/decision. Contributing to the accident was mountain obscuration.NTSB LAX98LA214Accident · No injuriesLimited investigationFinal reportCessna 172 · Flagstaff, AZOil system contamination with an unidentified metal substance that traveled through the oil system and blocked the number 4 main bearing and number 6 connecting rod bearing oil ports, resulting in oil starvation and failure of the engine. The source of the…NTSB ANC98LA071Accident · No injuriesLimited investigationFinal reportCessna 172 · Angoon, AKThe pilot's failure to maintain directional control during the aborted takeoff. A factor associated with the accident was rough and uneven terrain.NTSB ANC98LA065Accident · No injuriesLimited investigationFinal reportCessna 172 · Naknek, AKThe pilot's inadequate compensation for wind conditions. A factor associated with this accident was a crosswind.NTSB CHI98FA165Accident · 2 fatalField investigationFinal reportCessna 172 · S. Sioux City, NEThe pilot's failure to maintain adequate flying airspeed during the climbing left turn resulting in a stall condition. Contributing factors were the gusty, crosswind conditions, and the pilot's excessively tight turn maneuver during the initial climb.NTSB CHI98LA122Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Barrington Hill, ILThe pilot's failure to maintain adequate airspeed which resulted in a stall/mush and subsequent in-flight collision with trees.NTSB MIA98LA065Accident · No injuriesLimited investigationFinal reportCessna 172 · Valkaria, FLthe pilot's inadequate preflight, and subsequent loss of engine power, due to fuel exhaustion, which resulted in a forced landing and impact with trees.NTSB FTW98LA116Accident · No injuriesLimited investigationFinal reportCessna 172 · Laramie, WYThe pilot's improper flare and subsequent improper go-around in that he failed to use compensating elevator control, and his loss of directional control.NTSB MIA98LA022Accident · No injuriesLimited investigationFinal reportCessna 172 · Crystal River, FLThe certified flight instructors improper supervision of the rated pilot during a crosswind landing resulting in an in-flight collision with the left wing of the airplane and the runway, subsequent loss of directional control on landing rollout, and collision…NTSB LAX97LA239Accident · No injuriesLimited investigationFinal reportCessna 172 · Aguiguan Island, MauritiusThe pilot's failure to maintain runway alignment while landing on an undeveloped private dirt strip.NTSB SEA97LA139Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Wendover, UTThe pilot's failure to maintain directional control. Factors include the pilot's improper decision to continue his flight into an area where he had observed thunderstorms, and a thunderstorm outflow which created strong wind gusts that the aircraft…NTSB FTW97LA123Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Manchaca, TXThe pilot's continued VFR flight into instrument meteorological conditions and his failure to maintain obstacle clearance. A factor was the weather condition.NTSB LAX97LA064Accident · No injuriesLimited investigationFinal reportCessna 172 · Big Bear City, CAthe pilot's inadequate compensation for the wind condition, and his failure to maintain alignment with the runway. The gusty crosswind was a related factor.NTSB IAD96LA149Accident · No injuriesLimited investigationFinal reportCessna 172P · Richwood, WVimproper in-flight planning/decision by the flight crew, and inadequate supervision by the check pilot, which resulted in the flight crew's failure to maintain altitude/clearance from trees on rising terrain. A factor relating to the accident was:…NTSB CHI96LA329Accident · No injuriesLimited investigationFinal reportCessna 172 · Wellston, MIThe pilot failed to maintain control of the aircraft. Factors were the rough road, the tree, and the tire.NTSB ANC96FA141Accident · 3 fatalField investigationFinal reportCessna 172 · Eagle River, AKThe first pilot's failure to maintain sufficient distance/altitude from terrain. A box canyon and mountainous terrain are factors in the accident.NTSB CHI96LA249Accident · No injuriesLimited investigationFinal reportCessna 172 · Emily, MNthe pilot misjudged his altitude and distance to the runway on final approach, and he failed to maintain obstacle clearance during landing. A factor relating to the accident was: the parked car.NTSB MIA96LA192Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Okeechobee, FLfailure of the pilot to maintain control of the airplane during a high speed taxi check, which resulted in a lift-off and subsequent collision with the terrain.NTSB LAX96LA278Accident · 1 fatalLimited investigationFinal reportCessna 172 · Midas, NVthe decision of the pilot to perform a low-level steep turn which resulted in an inadvertent loss of control and subsequent stall/spin. Factors were high density altitude and inadequate altitude for recovery.NTSB LAX96LA209Accident · No injuriesLimited investigationFinal reportCessna 172 · Marana, AZthe pilot's improper flare and improper recovery from a bounced landing.NTSB IAD96FA057Accident · 3 fatalField investigationFinal reportCessna 172 · Barkhamsted, CTthe CFI pilot/passenger's poor judgment which led to spatial disorientation and subsequent loss of control of the airplane. Factors involved in this accident were the night marginal visual flight conditions and continuing flight with a known nonfunctioning…NTSB LAX96LA143Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Upland, CAfuel system contamination and the pilot's intentional operation of a known unairworthy aircraft.NTSB CHI96LA100Accident · No injuriesLimited investigationFinal reportCessna 172 · Ankeny, IAthe pilot's poor judgment in attempting flight operations in the existing wind condition, and the high gusting wind.NTSB ATL96LA050Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Jackson, MSloss of engine power during takeoff for undetermined reason(s). A factor relating to the accident was: the lack of suitable terrain for a forced landing.NTSB ANC96LA015Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Kasilof, AKThe pilot's inadvertent liftoff, and an inoperative elevator that became jammed due to frozen slush/snow.NTSB FTW96LA033Accident · No injuriesLimited investigationFinal reportCessna 172 · Oklahoma City, OKThe student pilot's failure to use carburetor heat resulting in loss of engine power due to carburetor icing. A factor was the lack of suitable terrain for a forced landing.NTSB NYC95LA217Accident · No injuriesLimited investigationFinal reportCessna 172 · Quakertown, PAthe pilot's failure to maintain directional control, and the pilot's improper use of the wing flaps, which resulted in an inadvertent stall, and contact with trees. A factor was the crosswind.NTSB CHI95LA281Accident · No injuriesLimited investigationFinal reportCessna 172 · Wheeling, ILinadequate preflight planning and preparation by the pilot and an inadverent stall encountered by the pilot.NTSB CHI95LA248Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Niles, MIThe pilot's failure to ensure an adequate supply of fuel was aboard the aircraft during preflight planning and his failure to lean the engine mixture during cruise flight.NTSB SEA95LA160Accident · No injuriesLimited investigationFinal reportCessna 172 · Mazama, WAThe pilot's failure to maintain adequate airspeed for the wind conditions during climbout. The gusty wind condition was a factor.NTSB CHI95LA220Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Cedar Rapids, IAthe pilot's lack of experience in flying from the right seat. A factor was the steep final approach.NTSB BFO95LA074Accident · No injuriesLimited investigationFinal reportCessna 172 · Wauseon, OHThe pilot's failure to obtain/maintain adequate altitude/clearance from obstacles during an attempted go-round. Related factors are the pilot's failure to attain the planned approach and the improper go-around procedures.NTSB BFO95LA041Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Allentown, PAthe pilot's inadequate compensation for wind conditions. Related factors were the gusty wind conditions and the pilot's poor weather evaluation.NTSB ANC95LA024Accident · No injuriesLimited investigationFinal reportCessna 172 · Unalakleet, AKThe pilot's inadequate compensation for a crosswind condition. A crosswind was a factor in the accident.NTSB FTW95LA057Accident · 1 fatalLimited investigationFinal reportCessna 172 · Lawton, OKThe pilot's failure to attain sufficient airspeed during takeoff resulting in a stall. Factors were the pilot's selection of the downwind runway and his failure to use all availabble runway.NTSB CHI94LA338Accident · No injuriesLimited investigationFinal reportCessna 172 · Mora, MNwas an improper touchdown by the pilot-in-command. Factor's associated with this accident were the pilot's diverted attention due to his perception of a crosswind condition and the pilot not performing a recovery from a bounced landing.NTSB ATL94LA160Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Pine Mountain, GAThe pilot's inadequate compensation for existing wind conditions, and his failure to maintain both airspeed and clearance from a fence. Factors were the tailwind and the gusts which existed at the time of the accident.NTSB ANC94FA109Accident · 2 fatalField investigationFinal reportCessna 172 · Big Lake, AKThe pilot's failure to maintain airspeed. Factors in the accident were the fog, and the pilot becoming lost/disoriented.NTSB BFO94LA136Accident · No injuriesLimited investigationFinal reportCessna 172 · Fisherville, KYThe pilot's failure to maintain airspeed, which resulted in a stall and inflight loss of control.NTSB NYC94LA139Accident · No injuriesLimited investigationFinal reportCessna 172A · Block Island, RIThe pilot's improper decision to initiate VFR flight into instrument meteorological conditions. The dark night light conditions and the fog were contributing factors.NTSB SEA94FA154Accident · 1 fatalField investigationFinal reportCessna 172 · Port Angeles, WALack of oil and connecting rod failure. A factor to the accident was rough/uneven terrain.NTSB LAX94LA250Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Suisun City, CAundetermined.NTSB LAX94LA218Accident · No injuriesLimited investigationFinal reportCessna 172 · Santa Ana, CAthe pilot's failure to maintain directional control of the aircraft. A factor in the accident was the pilot's limited experience in conventional gear aircraft.NTSB ATL93LA122Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Seneca, SCThe pilot's improper preflight planning which resulted in fuel exhaustion.NTSB ATL93LA112Accident · Serious injuriesLimited investigationFinal reportCessna 172 · St. Elmo, ALThe pilot's failure to maintain adequate clearance from the trees located near the departure end of the runway. Factors were the pilot's failure to use the entire runway for the takeoff, and the trees located near the departure end of the runway.
Back to Cessna 172