NTSB investigations: Cessna 172M
44 cases on aircraft the registry lists as Cessna 172M, where the first occurrence was “On ground/water 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 | 3 |
|---|---|
| 1983 | 3 |
| 1984 | 2 |
| 1986 | 2 |
| 1987 | 2 |
| 1988 | 2 |
| 1989 | 3 |
| 1990 | 3 |
| 1991 | 1 |
| 1992 | 4 |
| 1993 | 1 |
| 1994 | 2 |
| 1995 | 1 |
| 1997 | 1 |
| 1998 | 4 |
| 1999 | 2 |
| 2000 | 1 |
| 2001 | 2 |
| 2002 | 1 |
| 2003 | 1 |
| 2004 | 2 |
| 2005 | 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\" = 310))
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" = 310))
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 SEA05CA159Accident · No injuriesData collectionFinal reportCessna 172M · Hoquiam, WAThe pilot's failure to maintain clearance from a fence. The fence was a factor.NTSB ATL04LA167Accident · No injuriesLimited investigationFinal reportCessna 172M · Winston Salem, NCThe pilot's failure to maintain clearance from the fence post, while taxing which resulted in a collision.NTSB CHI04LA062Accident · No injuriesLimited investigationFinal reportCessna 172M · Jeffersonville, INThe pilot selecting a closed runway for landing and the collapse of the nose landing gear. Factors were the pilot's failure to obtain NOTAM information and the snowbank across the closed runway.NTSB SEA03LA047Accident · No injuriesLimited investigationFinal reportCessna 172M · Idaho Falls, IDThe student pilot's failure to maintain proper runway alignment (centerline tracking) during a go around maneuver resulting in the aircraft impacting a runway light. Contributing factors were the gusty/crosswind conditions and the light fixture.NTSB MIA02LA180Accident · No injuriesLimited investigationFinal reportCessna 172M · Kissimmee, FLThe pilot's failure to maintain the proper clearance while taxing the airplane which resulted in the left wing tip colliding with an object and damage to the airplane. A related factor was night conditions.NTSB MIA02LA024Accident · No injuriesLimited investigationFinal reportCessna 172M · Crystal River, FLthe pilot's failure to keep a proper visual lookout and ensure proper clearance during taxi operations, which resulted in a collision with vehicles.NTSB SEA01LA171Accident · No injuriesLimited investigationFinal reportCessna 172M · Seattle, WAPilot's failure to maintain an adequate visual lookout during taxi. A fence was a factor.NTSB CHI00LA168Accident · No injuriesLimited investigationFinal reportCessna 172M · Decatur, ILthe pilot's failure to maintain clearance with the T-hangar while taxiing. A Factor associated with the accident was the pilot's attention was diverted to an other airplane which was taxiing on the same taxi line in the opposite direction.NTSB SEA99LA160Accident · No injuriesLimited investigationFinal reportCessna 172M · Tahola, WAThe pilot's inadequate directional control and his failure to maintain clearance from trees along the side of the landing area. Factors include a landing area surrounded by tall trees.NTSB CHI99LA312Accident · No injuriesLimited investigationFinal reportCessna 172M · Bloomington, ILthe pilot's inadequate visual lookout and not performing a maneuver to avoid obstructions. A factor was the road signs.NTSB NYC98LA189Accident · No injuriesLimited investigationFinal reportCessna 172M · Teterboro, NJThe pilot's failure to maintain control of the airplane. Factors in this accident were the night light conditions, and pilot's lack of recent night flight experience.NTSB CHI98LA149Accident · No injuriesLimited investigationFinal reportCessna 172M · Elkhart, INthe pilot's disorientation that led him to believe he was on the active runway. A factor was the pilot's inattentiveness.NTSB SEA98LA071Accident · No injuriesLimited investigationFinal reportCessna 172M · Ocean Shores, WAThe pilot's failure to maintain clearance from a light standard (utility pole) just off the edge of the parking ramp. Factors include a light standard placed near the edge of the parking ramp.NTSB CHI98LA141Accident · No injuriesLimited investigationFinal reportCessna 172M · Superior, NEthe pilot's failure to maintain clearance with the sign. Factors associated with the accident were the sign which the airplane contacted and inadequate preflight planning/preparation.NTSB CHI97TA070Accident · No injuriesFinal reportCessna 172 · Oconto, WIthe failure of the pilot to maintain proper runway alignment and thus clearance with the snow drifts during takeoff. A factor was the distance the snow drifts extended past the runway edge.NTSB LAX96LA073Accident · No injuriesLimited investigationFinal reportCessna 172 · Mohave Valley, AZthe failure of the pilot to assure that clearance was maintained while taxiing in proximity of buildings at an excessive taxi speed.NTSB MIA95LA035Accident · No injuriesLimited investigationFinal reportCessna 172M · Crystal River, FLThe pilot in command's failure to maintain visual outlook during taxiing.NTSB NYC94LA093Accident · No injuriesLimited investigationFinal reportCessna 172M · Groton, CTthe pilot's inadequate visual lookout during taxi, which resulted in the airplane's wing tip striking ground support equipment.NTSB MIA94LA023Accident · No injuriesLimited investigationFinal reportPiper PA-60 · Orlando, FLThe failure of the pilot-in-command of the other aircraft to maintain a visual lookout and clearance between aircraft.NTSB DEN93LA004Accident · No injuriesLimited investigationFinal reportCessna 172N · Addison, TXThe attempt by both pilots to pass each other without adequate clearance between their airplanes.NTSB ANC92LA089Accident · No injuriesLimited investigationFinal reportCessna 172 · Anchorage, AKInadequate visual look out by the pilot of both aircraft. Contributing to the accident were the pilot's diverted attention, the other moving aircraft/object (c 172), and the excessive taxi speed of the c 172.NTSB CHI92LA151Accident · No injuriesLimited investigationFinal reportCessna 172M · Climax Springs, MODelay in aborting the landing by the pilot in command.NTSB NYC92LA069Accident · No injuriesLimited investigationFinal reportCessna 150 · Sanford, METhe failure of the pilot of N64147 to maintain adequate spacing and visual lookout from N6544G while taxiing, resulting in a ground collision.NTSB DEN92LA009Accident · No injuriesLimited investigationFinal reportCessna 172N · Boulder, COFailure of the pilot to maintain clearance from the sign.NTSB LAX91LA010Accident · No injuriesLimited investigationFinal reportCessna 172 · San Carlos, CAThe pilot's visual lookout was inadequate.NTSB FTW90LA158Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Broken Arrow, OKThe pilot in command's failure to maintain directional control during the takeoff.NTSB LAX90LA063Accident · No injuriesLimited investigationFinal reportMooney Mark 22 · Apple Valley, CAThe failure of the pilot of the Mooney to stop his aircraft in a timely manner to avoid a collision.NTSB SEA90LA031Accident · No injuriesLimited investigationFinal reportCessna 172M · Salem, ORThe pilots inadequate visual lookout while taxiing. Factors related to the accident are: the pilot's diverted attention and the pole.NTSB MIA89LA211Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Apalachicola, FLFailure of the pilot to maintain proper altitude. A factor related to the accident was: the pilot's lack of visual perception concerning altitude above the water.NTSB MIA89LA128Accident · No injuriesLimited investigationFinal reportCessna 172M · West Palm Beach, FLFailure of the pilot to insure adequate wingtip clearance while taxiing.NTSB MKC88LA138Accident · No injuriesLimited investigationFinal reportCessna 172 · Lamar, MOThe plt of the aerial applicator acft said he was pulling out for an intersection departure on rwy 21, when the Cessna on a landing roll, struck him from the rear. The pilot said that possibly the background, haze, and airframe components made the incoming…NTSB MKC88LA125Accident · No injuriesLimited investigationFinal reportCessna 172 · Topeka, KSWhile taxiing in from a personal solo training flight, the student pilot taxied into a chain link fence while attempting to park the acft. The right wing spar sustained substantial damage.NTSB SEA88LA027Accident · No injuriesLimited investigationFinal reportCessna 172M · Tacoma, WAThe Cessna was at the runup area for runway 35 preparing to do his runup. Three pitts aircraft were taxiing abreast of each other, when one of the pitts's propeller struck the right wingtip of the Cessna causing substantial damage to the Cessna and minor…NTSB MKC87LA142Accident · No injuriesLimited investigationFinal reportCessna 172 · Kansas City, MOAfter lndg, the PIC was clrd to taxi to the g/a ramp. He was not aware of the new g/a ramp & proceeded toward the old ramp. He saw a large acft coming from the opposite drctn on the same twy, so he modified his route by selecting another way. Mistakenly, he…NTSB FTW87LA039Accident · No injuriesLimited investigationFinal reportCessna 172M · Lindale, TXA private pilot substantially damaged his aircraft while attempting a landing on a grass strip in Lindale, TX. The pilot overshot the airstrip, and crashed in a field off the end of the runway.NTSB FTW86LA080Accident · No injuriesLimited investigationFinal reportCessna 172M · Dallas, TXThe pilot collided with a fence while taxiing on an airport access road, which he had mistaken for the taxiway. Although the pilot should have exercised better judgement, it has been determined that this same type of mishap has occurred before. After a…NTSB FTW84LA373Accident · No injuriesLimited investigationFinal reportCessna 172M · Bethany, OKAccording to the plt of N9646H, while he was taxiing under the direction of ground control the acft was struck from behind by N1PN. The plt of N1PN stated that he was cleared to taxi and did not see any other acft as he entered the taxiway. Seated in the rear…NTSB MIA84LA100Accident · No injuriesLimited investigationFinal reportCessna 172 M · Ormond Beach, FLThe plt stated that the alternator was inop, so the acft had no electrical power. He decided to hand prop the eng to start it for a banner towing operation. He set the parking brake & started pulling the propeller thru by hand while the cockpit was…NTSB MKC83LA223Accident · No injuriesLimited investigationFinal reportCessna 172 · Kansas City, MOWhile taxiing off temporary rwy 22 the plt prematurely taxied into the taxiway leading to the air cargo ramp. In an effort to reach the general aviation ramp he turned onto a vehicle access road & the left wing struck a vehicular traffic warning sign.NTSB SEA83LA112Accident · No injuriesLimited investigationFinal reportCessna 180H · Blakely Island, WAA Cessna 180H, N2429F, was being landed on rwy 19 after a Cessna 172M, N80202, had just landed. The Cessna 180 plt stated that during arrival, the wind socks at the ends of the rwy were swinging in all directions & there was light to moderate turbulence.…NTSB CHI83LA216Accident · No injuriesLimited investigationFinal reportCessna 150 · Janesville, WIN13364 had stopped short of the runway for a run-up check prior to takeoff. The pilot of N8576J continued his taxi while he was checking the field elevation and setting his altimeter he taxied into the empennage of N13364.NTSB CHI82DA291Accident · No injuriesFinal reportCessna 172M · Strongsville, OHThe aircraft was on a local flight from an uncontrolled airport. The wind was from 320 deg at 11 KTS. During arrival, the pilot elected to make a straight-in landing on runway 36. At about the same time, a Cessna 172, N20374, was landing from a normal pattern…NTSB DEN82DA157Accident · No injuriesFinal reportCessna 172 · Grafton, NDThe pilot stated that when he began to taxi he noticed a Cessna 172 with its engine running in front of a hangar, about 500 feet ahead and to his left. Continuing his taxi, the pilot's attention was diverted by an aircraft on the right. When he looked forward…NTSB LAX82DA118Accident · No injuriesFinal reportCessna 172 · Dilkon, AZThe pilot elected to land on a paved road and during the landing roll collided with a road sign.