NTSB investigations: Cessna 172M
69 cases on aircraft the registry lists as Cessna 172M, where the first occurrence was “In flight collision with object”. 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
| 1982 | 6 |
|---|---|
| 1983 | 3 |
| 1984 | 1 |
| 1985 | 2 |
| 1986 | 4 |
| 1987 | 3 |
| 1988 | 4 |
| 1989 | 4 |
| 1990 | 3 |
| 1991 | 5 |
| 1992 | 3 |
| 1993 | 2 |
| 1994 | 2 |
| 1995 | 3 |
| 1996 | 4 |
| 1997 | 2 |
| 1998 | 5 |
| 1999 | 3 |
| 2000 | 2 |
| 2001 | 2 |
| 2002 | 1 |
| 2003 | 4 |
| 2007 | 1 |
Where
Open the mapLatest 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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072418')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
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_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 c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2072418')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 220))
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 DFW07CA163Accident · No injuriesData collectionFinal reportCessna 172M · Throckmorton, TXThe pilot's failure to maintain clearance from power transmission lines. A contributing factor was the prevailing dusk illumination.NTSB SEA04LA030Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Elk City, IDThe pilot's failure to maintain clearance from trees during a go-around. Factors include dark night conditions and trees.NTSB SEA04LA013Accident · No injuriesLimited investigationFinal reportCessna 172M · Bandon, ORThe pilot's failure to maintain clearance from objects while on final approach. Dark night conditions, trees and a low glidepath were factors.NTSB ATL03LA044Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Hendersonville, NCThe pilot's failure to maintain directional control and clearence from power lines during a go-around, resulting in an in-flight collision with a powerline.NTSB DEN03LA039Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Logan, NMthe pilot's improper in-flight planning/decision, his failure to accomplish appropriate checklist items during the go-around, and his failure to maintain clearance from the trees and the lamp post. Factors contributing to the accident were the low altitude,…NTSB CHI03LA040Accident · No injuriesLimited investigationFinal reportCessna 172M · Moline, ILThe pilot's failure to maintain altitude clearance during a base to final turn on approach. Contributing factors to the accident were the night conditions and the trees.NTSB LAX01LA251Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Carson City, NVThe pilot's failure to follow the approved procedures for the aircraft when he attempted to takeoff at high density altitude with the wing flaps fully extended.NTSB FTW01LA138Accident · No injuriesLimited investigationFinal reportCessna 172M · Hot Springs, ARthe student pilot's delayed go-around, which resulted in the airplane impacting trees during the aborted landing.NTSB SEA00LA113Accident · No injuriesLimited investigationFinal reportCessna 172M · Wallace, IDThe pilot's failure to maintain airspeed and his failure to maintain clearance from the trees. Related factors were trees and mountainous terrain.NTSB FTW00LA090Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Manilla, ARThe pilot's performance of low altitude flight and his failure to maintain clearance with the power lines.NTSB CHI99LA135Accident · No injuriesLimited investigationFinal reportCessna 172M · Mayview, MOthe pilot's selection of unsuitable terrain for the attempted precautionary landing. Factors to the accident were the overcast weather condition, inadequate preflight planning by the pilot, the inadvertent flight into instrument meteorological conditions, and…NTSB FTW99LA108Accident · No injuriesLimited investigationFinal reportCessna 172M · Midlothian, TXThe pilot's failure to maintain clearance with the powerlines. Factors were the low ceilings and the dusk light illumination.NTSB LAX99LA123Accident · No injuriesLimited investigationFinal reportCessna 172M · Reno, NVThe pilot's inadequate compensation for the crosswind condition and his failure to maintain runway alignment during the crosswind landing.NTSB CHI98FA274Accident · 1 fatalField investigationFinal reportCessna 172M · Brooklyn, MIThe proper touchdown point was not attained and the visual lookout not being maintained by the pilot-in-command. Contributing factors to the accident were the unmarked static and transmission wires.NTSB CHI98LA225Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Flushing, MIwas a delayed go-around maneuver by the pilot. Factors associated with this accident were the pilot misjudging his final approach altitude and glide path, having inadequate altitude to clear the trees at the end of the runway, and inadequate training on how…NTSB MIA98LA113Accident · No injuriesLimited investigationFinal reportCessna 172M · Kingsport, TNThe dual student's failure to maintain adequate airspeed which resulted in a stall mush. Contributing to the accident were the flight instructor's inadequate supervision and the night conditions.NTSB FTW98LA122Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Port Lavaca, TXThe pilot's failure to maintain clearance from the power line. Factors were the gusty winds, the pilots lack of experience in the type of operation, inadequate training and insufficient standards/requirements by the company/operator management, and the power…NTSB LAX98FA066Accident · 2 fatalField investigationFinal reportCessna 172M · Chandler, AZThe pilot's intentional flying at a low altitude and failure to see and avoid the power lines during dusk conditions.NTSB FTW98LA075Accident · 1 fatalLimited investigationFinal reportCessna 172M · Monticello, UTThe pilot's failure to maintain adequate altitude and clearance from obstacles. Also causal was the pilot becoming lost and disoriented. Contributing factors were his lack of familiarity with the geographical area, lack of experience, night conditions, and…NTSB SEA97LA170Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Donnelly, IDThe pilot's failure to perform proper preflight planning for the flight, and his failure to obtain/maintain clearance from trees during takeoff. Factors contributing to the accident include the pilot's delayed remedial action, his improper use of flaps, and…NTSB SEA96LA211Accident · No injuriesLimited investigationFinal reportCessna 172M · Pacific City, ORthe pilot's failure to see-and-avoid the transmission line. Factors relating to the accident were: the pilot's low altitude flight, and the transmission line.NTSB SEA96LA169Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Nez Perce, IDthe pilot's improper in-flight decision to turn up a canyon, which the aircraft was unable to out-climb. Factors relating to the accident were: high ambient temperature, high density altitude, blind/box canyon, and trees in the area where the aircraft's climb…NTSB LAX96LA255Accident · No injuriesLimited investigationFinal reportCessna 172 · Frazier Park, CAthe failure of the pilot to maintain terrain clearance after a misjudged approach and landing that necessitated a go-around and subsequent collision with some wires. Factors were high density altitude and an inadequate evaluation by the pilot-in-command of…NTSB SEA96LA047Accident · No injuriesLimited investigationFinal reportCessna 172M · Mcleary, WAfailure of the pilot to maintain sufficient altitude/clearance from mountainous/wooded terrain. Factors relating to the accident were: the terrain and downdraft conditions.NTSB ATL96LA001Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Savannah, GAThe pilot's selection of unsuitable terrain for a precautionary landing, and his failure to maintain clearance from an obstacle (road sign) during the landing.NTSB FTW95FA393Accident · 3 fatalField investigationFinal reportCessna 172M · Witter, ARfailure of the pilot to maintain sufficient altitude/clearance from high/wooded terrain. Factors relating to the accident were: darkness, high terrain, and foggy weather conditions. Also, the pilot's use of Methamphetamine (not approved by the FAA) was a…NTSB NYC95LA207Accident · 1 fatalLimited investigationFinal reportCessna 172M · Kingswood Twsp, NJFailure of the pilot to maintain control of the airplane, which resulted in an in-flight collision with trees.NTSB LAX94LA350Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Rescue, CAThe pilot's delayed go-around. His inadequate compensation for the wind was a factor.NTSB SEA94LA189Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Seattle, WAThe proper touchdown point was misjudged by the pilot. During the go-around attempt, he failed to maintain clearance from obstacles.NTSB FTW94FA050Accident · 1 fatalField investigationFinal reportCessna 172M · Lancaster, TXwas THE FAILURE OF THE PILOT TO MAINTAIN AIRCRAFT CONTROL DUE TO PHYSICAL IMPAIRMENT (ALCOHOL).NTSB LAX93FA154Accident · 2 fatalField investigationFinal reportCessna 172M · White Water, CAThe pilot's failure to see and avoid the tower due to drug impairment. Factors which contributed to the accident were: the low altitude and the dawn light condition.NTSB SEA93LA024Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Vancouver, WAThe pilot's inability to see birds due to darkness.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 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 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 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 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 FTW91FA060Accident · 2 fatalField investigationFinal reportCessna 172M · Flippin, ARThe pilot's attempted VFR flight in instrument meteorological conditions and his failure to maintain altitude.NTSB LAX91FA012Accident · 1 fatalField investigationFinal reportCessna 172M · Goleta, CAThe pilot's failure to maintain proper glidepath while on final approach. A contributing factor was sunglare.NTSB MKC90LA123Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Winfield, IAThe pilot's decision to go-around was delayed and clearance of the power lines was not attained.NTSB SEA90FA065Accident · Serious injuriesField investigationFinal reportCessna 172M · Incline Village, NVImproper in-flight planning/decision by the instructor pilot (CFI), and his failure to maintain adequate altitude and clearance from obstructions. Factors related to the accident were: mountainous terrain, high density altitude, and the trees (obstructions).NTSB CHI90LA022Accident · No injuriesLimited investigationFinal reportCessna 172 · Lansing, ILThe pilot's inadvertent selection of unsuitable terrain (taxiway/construction area). The steel marker poles contributed to the aircraft damage.NTSB CHI90LA010Accident · No injuriesLimited investigationFinal reportCessna 172M · Cedarburg, WIDelay of the flight instructor (CFI) in making a go-around and his failure to attain sufficient airspeed to climb after taking off again. The transmission wire (power line) and high vegetation were contributing factors.NTSB MKC89FA117Accident · Serious injuriesField investigationFinal reportCessna 172M · Oakland, ARPilot electing to buzz persons on the lake at low altitude and colliding with power lines.NTSB LAX89LA109Accident · No injuriesLimited investigationFinal reportCessna 172M · Sacramento, CAThe pilot's selection of the wrong runway for landing and his delay in initiating a go-around after landing long. Contributing factors were: light conditions as dusk and a tailwind.NTSB LAX89LA004Accident · Serious injuriesLimited investigationFinal reportCessna 172M · Auberry, CAThe pilot was unfamiliar with the area that he was attempting to land in and circled to familiarize himself with the terrain. He then made a low pass over the dirt runway and circled to land. The first attempt was discontinued because the pilot felt that he…NTSB SEA88LA101Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Lester State, WAThe pilot inadvertently flew into a narrow valley with trees on both sides and steep rising terrain during climb to cruise. The aircraft was not able to outclimb the rising terrain, so the pilot slowed the aircraft to 40 m.p.h. and attempted a shallow…NTSB FTW88DPJ03Accident · Serious injuriesFinal reportCessna 172M · Norman, OKPilot retracted flaps during go around and aircraft settled into trees and was destroyed. Front seat occupants were not wearing the available shoulder harnesses. The acft was landing with a quartering tailwind. Due to serious head injuries the plt never…NTSB MKC88LA052Accident · No injuriesLimited investigationFinal reportCessna 172 · Kimball, NEThe pilot said that he was using outdated charts for his destination apt. He failed to notice a new runway. He also failed to notice the yellow x's, signifying closure of the old runway. It was almost parallel to the runway, within ten degrees of heading. Ldg…