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 CHI89LA166Accident · No injuriesLimited investigationFinal reportCessna 172P · Ravenna, OHFailure of pilot in command to maintain directional control of the airplane while executing a touch-and-go.NTSB LAX89LA273Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Seligman, AZA loss of engine power due to a failure of the number 3 cylinder exhaust valve rocker arm pivot stud, which was in turn caused by a stuck exhaust valve.NTSB MIA89LA207Accident · No injuriesLimited investigationFinal reportCessna 172N · Gainesville, FLThe student's improper flare for landing. The crosswind (quartering headwind) and the student's lack of experience in this aircraft were considered to be contributing factors.NTSB MIA89LA201Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Leesburg, FLFailure of the pilot to maintain adequate airspeed, which resulted in an inadvertent stall as he initiated a go-around.NTSB DEN89LA166Accident · No injuriesLimited investigationFinal reportCessna 172 · Glenwood Spgs, COInadequate compensation for wind conditions by the dual student, resulting in a loss of control and a forced landing. The pilot-in-command, CFI, failed to adequately supervise the operation.NTSB NYC89LA150Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Niagara Falls, NYEngine failure due to oil starvation and collision with terrain during the forced landing. The oil starvation was caused by the oil leaking out of the drain because maintenance personnel failed to install the drain plug.NTSB SEA89LA110Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Chemult, ORImproper inflight planning/decision by the pilot, which resulted in a sudden altitude deviation, and his delay in initiating remedial action to maintain clearance from the trees. Contributing factors were the downdrafts, high density altitude, the pilot…NTSB MIA89LA170Accident · No injuriesLimited investigationFinal reportCessna 172 · Cedar Key, FLThe pilot's failure to maintain directional control during landing.NTSB LAX89LA208Accident · No injuriesLimited investigationFinal reportCessna 172N · Sacramento, CAThe pilot of the other aircraft displayed poor judgement when he elected to continue taxiing in the runup area when visual lookout could not be maintained.NTSB FTW89LA105Accident · No injuriesLimited investigationFinal reportCessna 172 · Addison, TXFailure of the pilot to maintain clearance from the telephone pole. Factors related to the accident were: darkness, the pilot's disorientation, lack of visual perception at night, the telephone (utility) pole, and the ditch.NTSB ATL89LA147Accident · No injuriesLimited investigationFinal reportCessna 172N · Fuquay, NCFailure of the student pilot to maintain directional control of the aircraft during the landing, which resulted in an inadvertent ground swerve. Contributing factors were: improper flare by the student during the landing, which resulted in a hard landing, and…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 LAX89LA158Accident · No injuriesLimited investigationFinal reportCessna 172N · Eureka, CAThe improper in-flight planning by the instructor pilot when he allowed the private pilot student to land long. Additionally, the instructor delayed remedial action until the runway overrun was inevitable.NTSB ATL89LA127Accident · No injuriesLimited investigationFinal reportCessna 172 · Xenia, OHThe pilot's improper in-flight planning/decision and improper use of the flaps. Contributing was the downdraft.NTSB LAX89LA150Accident · No injuriesLimited investigationFinal reportCessna 172N · Prescott, AZImproper use of the elevator flight control by the pilot and his failure to maintain a proper rate of climb after lift-off. Contributing factors were: improper use of elevator trim by the pilot, his lack of total experience, and an inadvertent porpoise.NTSB MKC89LA074Accident · No injuriesLimited investigationFinal reportCessna 172 · Cresco, IAFailure of the pilot to maintain control of the airplane during the landing on a closed runway.NTSB CHI89LA055Accident · No injuriesLimited investigationFinal reportCessna 172N · Superior, WIFailure of the pilot to maintain directional control during the landing, which resulted in an inadvertent ground swerve. Factors related to the accident were the icy and snow covered runway conditions and the snowbank.NTSB MKC89LA067Accident · No injuriesLimited investigationFinal reportCessna 172 · Grand Rapids, MNThe pilot's failure to adequately compensate for the crosswind conditions. Contributing to the accident were the gusty crosswind conditions.NTSB FTW89LA058Accident · No injuriesLimited investigationFinal reportCessna 172 · Marietta, OKFailure of the pilot to select the proper runway, which resulted in a downwind landing and an overrun of the runway. The gusty tailwind, ditch, and railing (fence) were factors.NTSB MIA89IA095Incident · No injuriesIncident investigationFinal reportCessna 172N · Homestead, FLFuel starvation caused by a sticking needle valve which was softened by contact with automotive fuel previously used to operate the engine.NTSB LAX89LA107Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Deer Valley, AZThe pilot's failure to raise the wing flaps during the aborted landing, and his failure to maintain airspeed during the climbing right turn.NTSB MKC89LA056Accident · No injuriesLimited investigationFinal reportCessna 172 · Ainsworth, NEThe loss of power from undetermined reasons during an attempted go-around. Contributing to the accident was the pilot's failure to maintain directional control of the airplane and the crosswind conditions.NTSB BFO89LA014Accident · No injuriesLimited investigationFinal reportCessna 172N · Ashland, VAThe pilot's failure to maintain directional control of the airplane during landing and the failure to achieve sufficient airspeed during the go-around to initiate a climb.NTSB MIA89LA055Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Clearwater, FLThe plt stated that he had been given a short approach for runway 4, when the tower told him to go around. He added power, retracted the flaps, and made a sharp right turn. The acft stalled and crashed into an office building aprx 1 mile from the airport.NTSB DEN89LA040Accident · No injuriesLimited investigationFinal reportCessna 172 · Englewood, COThe CFI and her student were practicing landings on rwy 10 with winds reported as 090 deg at 5 KTS. The student was on the controls, flared too high, and the acft bounced at touchdown. The CFI told him to add power to recover from the bounced landing. The…NTSB ATL89LA050Accident · No injuriesLimited investigationFinal reportCessna 172 · Lawrenceville, GAAfter 3 full stop landings, the pilot reported that the airplane would not accelerate to liftoff airspeed on 4th takeoff after rolling about 2000 feet. The pilot elected to abort the takeoff. The airplane rolled off the departure end of runway 07 and nosed…NTSB SEA89LA022Accident · No injuriesLimited investigationFinal reportCessna 172 · Oregon City, ORThe pilot was landing his aircraft on a very wet 1,170 foot grass runway. The pilot was not able to stop the aircraft before it collided with a fence at the end of the runway. According to the manufacturers performance figures, under the given temperature and…NTSB LAX89FA042Accident · 1 fatalField investigationFinal reportCessna 172N · Fremont, CAThe newly certificated private plt reportedly was emotionally disturbed about his employment & personal life situation. He loved flying & flew to release anxiety. Near midnight the plt departed for a short x-c flight during which he became disoriented. The…NTSB ATL89LA029Accident · No injuriesLimited investigationFinal reportCessna 172N · Rogersville, TNThe plt reported that he was ferrying the airplane to obtain scheduled maintenance. Upon arrival over the arpt, he found that the only rwy was closed for maintenance. He then elected to land on a taxiway. He made a short-field ldg and applied the brakes…NTSB MIA89LA017Accident · No injuriesLimited investigationFinal reportCessna 172N · Houston, MSDuring normal cruise flt a portion of one propeller blade separated. The plt landed the acft in a field & during the landing roll, the acft collided with a haystack. Examination of the propeller blade revealed it separated at blade station 28.5. Metallurgical…NTSB LAX89FA022Accident · 2 fatalField investigationFinal reportCessna 172N · Petaluma, CAPilot used poor judgement when he attempted v.f.r. flight during instrument meteorological conditions and that he encountered spatial disorientation when he entered into the clouds.NTSB MKC89LA003Accident · No injuriesLimited investigationFinal reportCessna 172 · West Memphis, ARThe pilot said he was unable to activate the runway lights on the designated frequencies during a night personal flight. He attempted to land without the aid of the runway lights, and touched down on the FAR end of the runway subsequently running off the end…NTSB BFO89LA001Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Sandston, VAThe plt said he was on final apch about 600 to 800 ft AGL when power loss occurred. He forced landed on an open field about 1/2 mi short of the rwy. The eng exam revealed that two teeth of the idler gear had separated. This resulted in a loss of continuity…NTSB NYC88FA236Accident · 2 fatalField investigationFinal reportCessna 172N · Adams, MAPilot's inadequate preflight planning and improper inflight decisions, he continued VFR into IFR conditions. The air route traffic control center service was improper.NTSB LAX88LA320Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Truckee, CADuring takeoff roll the pilot heard a banging noise on the left wing. The pilot continued the takeoff. At 100 ft a.g.l. he executed a 180 degree turn to the right to return to land. The pilot added 30 degrees of flaps to the 10 that had been set for takeoff.…NTSB LAX88LA329Accident · No injuriesLimited investigationFinal reportCessna 172N · Camarillo, CAWhile taxiing for takeoff, the pilot maneuvered off the taxiway centerline to allow an oncoming Cessna 182 to pass. The Cessna 172 then collided with an airport t-hangar located near the taxiway.NTSB SEA88LA157Accident · No injuriesLimited investigationFinal reportCessna 172N · Tyge Valley, ORThe pilot reported that late in the apch, the acft developed a high sink rate. However, he used elevator only to correct the sink rate. The aircraft impacted the runway and bounced. On the third bounce, the nose gear failed and the aircraft nosed over. The…NTSB LAX88LA285Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Lake Arrowhead, CADuring a local parachute jump flight, the airplane was unable to gain enough altitude to clear rising terrain. The airplane collided with a tree and eventually the terrain. There were no reported mechanical failures or malfunctions. The acft handbook lists…NTSB CHI88LA210Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Montgomery, OHWhile on a local pleasure night flight, in normal cruise configuration, the pilot experienced a loss of engine power due to fuel contamination and executed a forced landing on a highway exit ramp. The pilot stated that he attempted to make the forced landing…NTSB CHI88LA185Accident · No injuriesLimited investigationFinal reportCessna 172N · Xenia, OHNTSB DEN88LA174Accident · No injuriesLimited investigationFinal reportCessna 172M · Gillette, WYThe student plt was completing his first solo x-country flt. During touchdown, the airplane bounced and began to porpoise. On the third bounce, the nose wheel fork failed. Subsequently, the acft turned 180 deg to the left & came to rest on the left side of…NTSB LAX88LA269Accident · No injuriesLimited investigationFinal reportCessna 172N · Redlands, CADuring the takeoff ground run on a solo instructional flight, the student pilot lost control of the airplane. The airplane veered to the left. The pilot applied right rudder, however, the airplane continued to the left, exited the runway and collided with the…NTSB CHI88FA160Accident · 1 fatalField investigationFinal reportCessna 172N · Middletown, INAttempted operation of the accident airplane by the PIC when he was under the influence of alcohol.NTSB ANC88LA082Accident · No injuriesLimited investigationFinal reportCessna 172 · Healy, AKThe commercial pilot/flight instructor was attempting to land at a private turf airstrip when she reportedly encountered the outflow from a thunderstorm located about one mile away. She elected to continue with the landing and touched down with a greater than…NTSB LAX88LA234Accident · No injuriesLimited investigationFinal reportCessna 172N · La Grange, CANTSB DEN88LA129Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Rifle, COThe student plt was flying a x-country training flt. The flt was not on the planned route. The plt flew into a box canyon too narrow to complete a turn and could not climb fast enough to clear the terrain at the end of the canyon. The pilot attempted a turn…NTSB MKC88LA106Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Lakeview, ARWhile attempting to land crosswind on a 'one way' runway, the plt said a gust of wind blew him towards some bordering trees, so he made a decision to 'go around'. The plt said he applied full throttle and raised the flaps from the full flap setting, and…NTSB MIA88FA187Accident · Serious injuriesField investigationFinal reportCessna 172N · Jacksonville, FLThe private pilot had been hired to ferry a recently purchased aircraft. He stated that the aircraft had not been flown for about 2 weeks. He had it refueled and checked the fuel tanks for water. After takeoff the engine failed at about 200 ft. he crashed…NTSB ANC88FA065Accident · 3 fatalField investigationFinal reportCessna 172N · Hatcher Pass, AKThe aircraft crashed at the 3100 foot level of a mountain Pass. The aircraft was destroyed by ground impact and fire, and the pilot and the two passengers were fatally injured. Witnesses near the crash site stated the aircraft was maneuvering very low above…NTSB ATL88FA185Accident · 2 fatalField investigationFinal reportCessna 172 · Raleigh, NCA Piper PA-28R (lead acft, N44018) & a Cessna 172 (#2 acft, N737GU) were departing Raleigh-durham arpt on a formation flt to petersburg, VA. The Cessna plt (wingman) rprtd that drg takeoff & initial climb, the lead acft bgn to accelerate ahead of him. The…
Back to Cessna 172N