NTSB investigations: Cessna 172N, 1993

51 cases on aircraft the registry lists as Cessna 172N. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.

Cases per year

19652026
NTSB investigations: Cessna 172N, 1993 per year, 1965–2026: 1,815 cases
19651
19662
19672
19751
19762
197726
197862
197981
1980107
198186
198291
198353
198455
198540
198644
198742
198847
198945
199046
199157
199240
199351
199443
199548
199637
199740
199837
199946
200035
200132
200243
200332
200438
200526
200623
200721
200821
200920
201023
201122
201214
201320
201415
201510
201624
201719
201814
201916
202025
202115
202216
202320
202413
202515
202611

Latest cases

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_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
  WHERE year(c.\"eventDate\") = 1993
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.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.

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.Dec 30, 1993 · N7553E · Substantial damageNTSB 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.Dec 18, 1993 · N4930G · Substantial damageNTSB NYC94LA041Accident · No injuriesLimited investigationFinal reportCessna 172N · Bar Harbor, MEA disconnected fuel line with the carburetor not installed, and improper dispatch of the aircraft.Dec 17, 1993 · N5753E · Substantial damageNTSB FTW94LA037Accident · No injuriesLimited investigationFinal reportCessna 172N · Albuquerque, NMThe pilot's improper flare.Nov 27, 1993 · N4759G · Substantial damageNTSB 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.Nov 17, 1993 · N4713D · Substantial damageNTSB 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.Nov 15, 1993 · N4829E · DestroyedNTSB 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.Oct 30, 1993 · N8279E · Substantial damageNTSB FTW94LA017Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Woodville, TXFailure of the pilot in command to maintain control of the aircraft during an aborted landing.Oct 24, 1993 · N317BB · Substantial damageNTSB 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.Oct 10, 1993 · N738LX · Substantial damageNTSB SEA94LA013Accident · No injuriesLimited investigationFinal reportCessna 172N · Renton, WAThe student pilot's failure to maintain directional control during landing. The crosswind was a factor.Oct 9, 1993 · N7367E · Substantial damageNTSB 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.Oct 8, 1993 · N5365D · DestroyedNTSB 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.Oct 1, 1993 · N172LS · DestroyedNTSB 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.Sep 11, 1993 · N5347J · Substantial damageNTSB 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.Sep 9, 1993 · N2437E · Substantial damageNTSB SEA93LA193Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Price, UTThe failure of the pilot to maintain airspeed above stall.Sep 6, 1993 · N8067E · Substantial damageNTSB 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…Aug 21, 1993 · N75644 · DestroyedNTSB NYC93LA163Accident · No injuriesLimited investigationFinal reportCessna 172 · Hope Valley, RIThe engine failure as the result of ingestion of pieces of carburetor into the cylinders, and the subsequent forced landing and nose over during the landing roll after encountering soft terrain.Aug 19, 1993 · N9845J · Substantial damageNTSB NYC93FA158Accident · 1 fatalField investigationFinal reportCessna 172N · Lincoln Park, NJThe failure of both pilots to maintain adequate visual lookout while in the airport traffic pattern, which resulted in an in-flight collision.Aug 15, 1993 · N5226E · 2 aircraft · DestroyedNTSB NYC93LA146Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Leeds, METhe loss of engine power for undetermined reasons.Aug 7, 1993 · N739EP · Substantial damageNTSB SEA93LA167Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Monroe, WAThe improper inflight decision by the PIC and his failure to attain proper runway alignment. Factors relating to the accident were the dark night light conditions, unavailability of runway lights, and lack of recent night flight time by the PIC.Jul 29, 1993 · N734DL · Substantial damageNTSB FTW93LA216Accident · No injuriesLimited investigationFinal reportCessna 172N · Purcell, OKThe lack of suitable terrain onto which to execute the forced landing which was neccesitated by the partial power loss. The power loss was a result of the fatigue failure of the exhaust valve rocker arm attachment stud. A factor was the night conditions.Jul 25, 1993 · N4884G · Substantial damageNTSB CHI93FA272Accident · Serious injuriesField investigationFinal reportCessna 172N · Long Grove, ILThe pilot-in-command's failure to refuel the airplane prior to fuel exhaustion. Related factors to the accident were: inadequate certification/approval of the STC by the FAA, inadequate performance data, and unavailable fuel consumption information.Jul 23, 1993 · N733XS · Substantial damageNTSB MIA93LA158Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Atlantic Ocean (Atlantic Ocean)Total loss of engine power due to fuel exhaustion. Contributing to the accident was inaccurate fuel comsumption calculations by the pilot-in-command.Jul 19, 1993 · N99BW · DestroyedNTSB LAX93LA284Accident · No injuriesLimited investigationFinal reportCessna 172N · Alturus, CAThe pilot's delay in aborting the takeoff. The pilot's premature rotation and his failure to follow the procedures in the airplane flight manual regarding use of the mixture control, the high density altitude condition and the pilot's lack of total flight…Jul 9, 1993 · N75901 · Substantial damageNTSB LAX93LA280Accident · No injuriesLimited investigationFinal reportCessna 172N · Truckee, CAThe partial loss of engine power during the takeoff initial climb for undetermined reasons. A factor in the accident was the unsuitable nature of the terrain for a forced landing.Jul 6, 1993 · N3090E · Substantial damageNTSB NYC93LA136Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Voluntown, CTThe pilot's failure to achieve the proper touchdown point which resulted in an overrun of the runway and collision with trees. A factor is the pilot's improper compensation for the wind condition.Jun 27, 1993 · N6553E · Substantial damageNTSB CHI93LA229Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Point Lookout, MOThe pilot in command's failure to maintain proper glide path, and her failure to attain the proper touch down Point.Jun 26, 1993 · N76107 · Substantial damageNTSB CHI93LA221Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Rapid City, SDThe pilot in command's inadequate compensation for wind conditions.Jun 23, 1993 · N5435E · Substantial damageNTSB DEN93LA068Accident · No injuriesLimited investigationFinal reportCessna 172N · Livermore, COA partial power loss when the rocker box for one cylinder disengaged. A factor was: unsuitable terrain for a forced landing.Jun 11, 1993 · N4829E · Substantial damageNTSB CHI93LA196Accident · No injuriesLimited investigationFinal reportCessna 172N · St. James, MIThe pilot landed too long on a wet runway.Jun 8, 1993 · N73630 · Substantial damageNTSB LAX93FA223Accident · 2 fatalField investigationFinal reportCessna 172N · Lompoc, CAVFR flight by the pilot into instrument meteorological conditions (IMC), and his failure to maintain proper altitude (or clearance) from mountainous terrain. Factors relating to the accident were: the low ceiling, fog, drizzle, obscuration, and mountainous…May 25, 1993 · N4783J · DestroyedNTSB LAX93LA225Accident · 1 fatalLimited investigationFinal reportCessna 172N · Page, AZthe pilot's selection of an inadequate cruise altitude. A factor in the accident was the high winds and turbulence in the vicinity of the cliffs.May 24, 1993 · N734DB · DestroyedNTSB DEN93LA061Accident · No injuriesLimited investigationFinal reportCessna 172N · Buena Vista, COA downdraft and the pilot's failure to maintain directional control of the airplane. Factors were: a crosswind and the inadvertent selection of additional flaps.May 23, 1993 · N4881G · DestroyedNTSB MIA93FA127Accident · 4 fatalField investigationFinal reportCessna 172N · Deerfield Beach, FLFailure of the pilot-in-command to maintain airspeed (vso). The low altitude at the time of the aerodynamic stall was a factor.May 21, 1993 · N4931D · DestroyedNTSB BFO93LA091Accident · No injuriesLimited investigationFinal reportCessna 172N · Petersburg, OHThe pilot's failure to attain the proper touchdown point while attempting to land on a wet grass strip, and his failure to perform a go around. The wet grass runway was a factor.May 18, 1993 · N7355E · Substantial damageNTSB ATL93LA091Accident · No injuriesLimited investigationFinal reportCessna 172 · Wilmington, NCThe ground personnel's failure to ensure that the airplane was clear of obstructions which resulted in the right wing colliding with a utility pole. A factor was the pilot's inadequate visual lookoutMay 10, 1993 · N4856D · Substantial damageNTSB BFO93LA075Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Falmouth, KYThe pilot's failure to maintain directional control of the airplane during the landing roll, which resulted in an inadvertent swerve, and his delayed remedial action.May 8, 1993 · N1329E · Substantial damageNTSB ANC93LA059Accident · No injuriesLimited investigationFinal reportCessna 172 · Kasigluk, AKThe pilot's poor judgement in attempting a takeoff from a narrow, wet, soft gravel runway with a crosswind. The runway conditions and the crosswind were factors in the accident.May 1, 1993 · N6332D · Substantial damageNTSB LAX93LA193Accident · No injuriesLimited investigationFinal reportCessna 172N · Santa Monica, CAThat the pilot misjudged the flare and failed to properly recover from the ensuing bounced landing. The pilot's failure to attain the proper touchdown point was a factor.Apr 29, 1993 · N401KA · Substantial damageNTSB NYC93LA090Accident · No injuriesLimited investigationFinal reportCessna 172 · Columbus, OHThe improper flare by the pilot allowing the airplane to balloon and land hard. A factor in this accident was pilot's lack of recent flying experience.Apr 23, 1993 · N734QF · Substantial damageNTSB LAX93LA183Accident · No injuriesLimited investigationFinal reportCessna 172N · Needles, CAthe total loss of engine power due to the failure of the magneto in the ignition system. The magneto failure resulted from the operator's lack of voluntary compliance with the manufacturers suggested overhaul cycle.Apr 23, 1993 · N6292D · Substantial damageNTSB LAX93LA176Accident · No injuriesLimited investigationFinal reportCessna 172N · Flagstaff, AZThe pilot's poor aircraft handling techniques, his failure to correctly configure the carburetor heat control during the go around, and, his failure to maintain an adequate airspeed which resulted in an inadvertent stall mush condition. Factors in the…Apr 15, 1993 · N3443E · Substantial damageNTSB MIA93LA132Accident · No injuriesLimited investigationFinal reportCessna 172N · Immokalee, FLThe decision of the pilot to buzz and his failure to maintain adequate visual lookout.Apr 12, 1993 · N6542J · Substantial damageNTSB NYC93LA078Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Durham, NHImproper planning/decision by the pilot, which resulted in fuel exhaustion and loss of engine power. Factors related to the accident were flight into adverse weather conditions, failure to obtain inflight weather information, and pilot fatigue.Apr 10, 1993 · N8228G · Substantial damageNTSB FTW93FA096Accident · 1 fatalField investigationFinal reportCessna 172N · Katy, TXThe pilot's failure to maintain control of the airplane for undetermined reasonsMar 6, 1993 · N222UF · DestroyedNTSB FTW93LA094Accident · No injuriesLimited investigationFinal reportCessna 172N · Houston, TXFuel starvation power loss due to carburetor restriction from a foreign object, the inadequate inspection and improper overhaul of the carburetor by other maintenance personnelMar 3, 1993 · N8071E · Substantial damageNTSB DEN93LA029Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Broomfield, CORudder control interference.Mar 1, 1993 · N4908G · DestroyedNTSB MIA93LA079Accident · No injuriesLimited investigationFinal reportAeronca KCA · Bunnell, FLImproper procedures by the other pilot for his failure to perform 's' turns while taxiing.Feb 28, 1993 · N1938K · 2 aircraft · Substantial damageNTSB LAX93LA102Accident · No injuriesLimited investigationFinal reportCessna 172N · Sedona, AZThe pilots inadequate compensation for the existing wind conditions and his delay in executing a go around. A factor in the accident was the pilot's lack of total experience.Jan 24, 1993 · N737EA · Substantial damageNTSB FTW93LA065Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Santa Fe, NMThe pilot's failure to maintain directional control. A factor was the snow conditionsJan 12, 1993 · N734GD · Substantial damage