NTSB investigations: Cessna 172P
49 cases on aircraft the registry lists as Cessna 172P, 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 | 7 |
|---|---|
| 1983 | 2 |
| 1984 | 3 |
| 1985 | 1 |
| 1986 | 4 |
| 1987 | 1 |
| 1988 | 5 |
| 1989 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 1992 | 5 |
| 1993 | 3 |
| 1994 | 3 |
| 1995 | 2 |
| 1996 | 1 |
| 1997 | 2 |
| 1999 | 2 |
| 2003 | 2 |
| 2004 | 1 |
| 2006 | 2 |
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 ('2072436')
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 ('2072436')
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 LAX06CA281Accident · No injuriesData collectionFinal reportCessna 172P · Spanish Springs, NVthe pilot's failure to initiate a timely go-around and to attain an adequate climb rate. Factors in the accident were the high density altitude and the likely quartering tail wind that may have affected the aircraft's climb gradient.NTSB ATL06CA043Accident · No injuriesData collectionFinal reportCessna 172P · Birmingham, ALAn in-flight collision with a deer during a go around, which resulted in damage to the left main landing gear and subsequent collapse of the left main landing gear.NTSB DEN04LA123Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Spanish Fork, UTthe pilot's improper inflight planning and decision making, and his failure to maintain terrain clearance. Contributing factors were his intentional low altitude flight and maneuvering, the aircraft's climb performance being exceeded, and the trees.NTSB CHI03LA212Accident · No injuriesLimited investigationFinal reportCessna 172P · Pinckneyville, ILThe planned approach not maintained by the pilot and the delayed remedial action by the certified flight instructor. A contributing factor to the accident was the approach light.NTSB MIA03FA066Accident · 1 fatalField investigationFinal reportCessna 172P · Osteen, FLThe intentional suicidal act by the pilot-in-command resulting in the in-flight collision with trees then the ground.NTSB CHI00LA017Accident · No injuriesLimited investigationFinal reportCessna 172 · Waukon, IAthe pilot failed to maintain directional control of the airplane during the aborted landing. Factors relating to the accident included the crosswinds, the fence, and the trees.NTSB MIA99LA182Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Seymour, TNThe failure of the pilot to perform a go-around earlier resulting in a long landing, insufficient runway remaining to stop, and subsequent in flight collision with a marked power line during an aborted landing.NTSB NYC98LA012Accident · No injuriesLimited investigationFinal reportCessna 172P · Pittsfield, MAThe pilot's poor in-flight decision to continue VFR flight in IFR conditions. Factor's in this accident were the pilot's inadequate pre-flight planning, and fog.NTSB IAD97LA046Accident · No injuriesLimited investigationFinal reportCessna 172P · Chesapeake, OHthe pilot's failure to maintain proper altitude during the approach at night. Related factors were: darkness, and the pilot's lack of night flying experience.NTSB FTW96LA128Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Iowa, LAthe pilot's selection of the wrong runway for landing, his delay in initiating a go-around (aborted landing), and his failure to maintain clearance from the transmission lines. Factors relating to the accident were: the pilot's improper weather evaluation,…NTSB FTW96FA058Accident · 3 fatalField investigationFinal reportCessna 172P · Hallett, OKThe flight instructor's intentional low altitude flight maneuver. Factors were the static wire and the bright night condition.NTSB ANC95LA149Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Soldotna, AKThe pilot's improper in-flight planning/decision, and his failure to maintain sufficient altitude to assure clearance from obstructions. The downdraft was a related factor.NTSB FTW95LA052Accident · No injuriesLimited investigationFinal reportCessna 172P · Blanco, TXThe pilot's use of unsuitable terrain for takeoff. Factors were the uphill terrain, the long vegetation, and short takeoff area available.NTSB CHI94LA289Accident · No injuriesLimited investigationFinal reportCessna 172 · Plato Center, ILThe pilot's attempt to take off on a short runway with a gross weight which exceeded the maximum allowable weight and an improper flap setting. A factor was the location of obstructions (trees) at the departure end of the runway.NTSB SEA94LA178Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Easton, WAImproper planning/decision by the pilot-in-command, and inadequate supervision by the check pilot, which resulted in their failure to remain clear of trees during takeoff. Factors related to the accident were: a downdraft and the proximity of trees to the…NTSB LAX94LA061Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Panoche, CAthe pilot's improper approach speed and glide path, and his delayed initiation of a go-around. A factor in the accident was the wind shear condition created by the hills immediately off the departure end of the dirt airstrip.NTSB BFO93LA156Accident · 1 fatalLimited investigationFinal reportCessna 172P · Pembroke, VAThe pilot's failure to maintain proper altitude while manuevering in mountainous terrain.NTSB FTW93LA217Accident · No injuriesLimited investigationFinal reportCessna 172P · Cookson, OKThe pilot's improper flare and his failure to maintain directional control during the aborted landing.NTSB DEN93FA008Accident · 1 fatalField investigationFinal reportCessna 172P · Woody Creek, COAircraft climb performance exceeded. Factors were: the pilot's lack of experience in mountain flying, and the high density altitude conditions.NTSB SEA92LA206Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Leavenworth, WAThe premature lift off by the pilot. Factors relating to the accident were the soft, rough turf airstrip and the high obstructions at the end of the runway.NTSB LAX92LA306Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Kernville, CAThe pilot's selection of the wrong runway; poorly planned approach; failure to attain the proper touch down point; and delay in executing the go-around. Contributing to this accident was the existing tailwind and crosswind.NTSB CHI92LA173Accident · Serious injuriesLimited investigationFinal reportCessna 172P · Ladysmith, WIFailure of the pilot to attain a proper touchdown point and the attempted abort of the precautionary landing attempt.NTSB BFO92FA069Accident · 2 fatalField investigationFinal reportCessna 172P · Princeton, NJThe pilot's failure to maintain clearance over an obstacle. Contributing factors were a tailwind, dark night, and premature raising of the flaps.NTSB ATL91LA139Accident · No injuriesLimited investigationFinal reportCessna 172P · Sylva, NCThe pilot's improper in-flight planning, and his failure to maintain a proper altitude while maneuvering in the canyon. Factor(s) in this accident were: the mountainous, box canyon conditions, the high density altitude, and the downdraft conditions at the…NTSB BFO91LA016Accident · 1 fatalLimited investigationFinal reportCessna 172P · Axton, VAThe pilot's failure to maintain adequate clearance with an obstacle. Contributing was an unmarked powerline and the pilot's lack of familiarity with the geographical area.NTSB ATL89LA183Accident · No injuriesLimited investigationFinal reportCessna 172P · Cincinnati, OHThe pilot's improper go-around procedure of fully retracting the flaps which resulted in the airplane mushing into trees. Contributing factor(s) was: a misjudgement of flare height above the runway and failure to remove the carburetor heat which may have…NTSB MKC89LA015Accident · No injuriesLimited investigationFinal reportCessna 172 · Blue Springs, MOThe plt said, while cruising over a water reservoir at about 500 feet AGL, he collided with two waterfowl, believed to be geese. One struck the wing tip, the other near the wing root. Acft control remained constant with no control problems encountered, and…NTSB FTW88FA162Accident · 1 fatalField investigationFinal reportCessna 172P · Marietta, OKThe plt elected to land on rwy 17 with wind from 300 degrees at 6 knots. During the second go-around the airplane's left wing struck a tree at a point 30 feet above the ground and the aircraft ended up inverted in a parking lot. Plt stated he had landed at…NTSB NYC88FA202Accident · 2 fatalField investigationFinal reportCessna 172P · Post Mills, VTThe plt flew the acft to an arpt with two turf rwys. Rwy 5/23 was 2300' long & rwy 4/22 was 2600' long. After attending a meeting which ended at 1600 EDT, the plt elected to wait until later in the day to takeoff after the air had cooled. Subsequently, he…NTSB LAX88FA240Accident · 1 fatalField investigationFinal reportCessna 172P · Descanso, CAPilot's poor judgment and intentional decision to low fly the aircraft below the minimum safe altitude.NTSB NYC88LA079Accident · 1 fatalLimited investigationFinal reportCessna 172P · East Hampton, NYThe flight departed East Hampton airport for a pleasure flt. Shortly thereafter, the pilot called on frequency 122.7 stating that he had struck some birds and could not maintain control of the aircraft. There as no further transmission as to his location, and…NTSB BFO87FA050Accident · Minor injuriesField investigationFinal reportCessna 172P · Whitemarsh, MDThe pilot stated that he touched down near the end of the 22OO foot runway. However, witnesses said he landed so FAR down the runway that they did not believe he could stop on the runway. The pilot delayed his go around attempt to the point where it was not…NTSB ATL87LA002Accident · Minor injuriesLimited investigationFinal reportCessna 172P · East Liverpool, OHRwy repair was in progress. The rwy was closed & battery powered lights were left to mark a 5 inch deep ditch that crossed the runway. Arpt & rwy lights were left off. The FBO continued to rent acft for operations from the arpt. The plt departed on a 28 mi…NTSB ATL86FA212Accident · 2 fatalField investigationFinal reportCessna 172 · Bridgeport, WVThe aircraft collided with a tree while on final approach to runway 21. The flight had been cleared for the approach after the pilot reported having the airport in sight. There was no current weather observation available at that time, but a local air taxi…NTSB LAX86LA117Accident · No injuriesLimited investigationFinal reportCessna 172P · Ontario, CAThe owner/plt (PIC) was on a flt for night & instrument currency requirements. He was flying the acft from the left front seat while a commercial plt (cp) was occupying the rgt front seat. Drg an ILS rwy 26L final apch at Ontario, CA, the PIC & cp discussed a…NTSB ATL86LA068Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Alexander City, ALThe acft was observed to make one takeoff and landing from an umimproved pasture. The second takeoff attempted was unsuccessful and the acft collided with a tree and crashed to the ground. The plt did not report any mechanical problems with the acft. There…NTSB CHI85LA164Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Phillipsburg, OHDuring a night VFR approach to a strange airport the acft struck power lines located one-half mile from the end of the rwy. The plt stated that she was unaware of the wires & was not aware that her acft had collided with them until her forward progress was…NTSB FTW84FA408Accident · 2 fatalField investigationFinal reportCessna 172P · Webbers Falls, OKAcft struck electrical transmission line 80' above water while flying under the line during a wildlife survey. The acft's mission was to conduct a duck count along a river in a nat'l wildlife refuge which required low, slow maneuvering. The ex-ag pilot was…NTSB ATL84LA271Accident · Minor injuriesLimited investigationFinal reportCessna 172P · Biloxi, MSPrior to departure the pilot determined that his destination, a grass runway, was dry. His first approach to this field resulted in a go-around because he would have landed long. The second approach resulted in a landing, but because his wheels began to slide…NTSB LAX84LA148Accident · No injuriesLimited investigationFinal reportCessna 172 · Oakland, CAThe acft collided with wires during a descent through the clouds. The student plt had found himself on top of an overcast and managed to descend through it but in doing so a power line was hit. The plt climbed back on top and continued to destination without…NTSB MIA83LA161Accident · No injuriesLimited investigationFinal reportCessna 172P · Pensacola, FLThe plt reported that he descended to aprx 50 ft AGL to demonstrate flt at low altitude to his passengers. While flying over a pasture at this altitude, the acft struck a pine tree, damaging the right wing. The plt experienced no control problems & returned…NTSB FTW83LA352Accident · Minor injuriesLimited investigationFinal reportCessna 172N · Morrilton, ARThe acft collided with trees on the final approach to land at night. The plt had canceled his IFR clearance. During the approach the plt had the rwy in sight and asked memphis center how FAR he was from the arpt. When he was informed he WAS3 miles south he…NTSB LAX83LA054Accident · No injuriesLimited investigationFinal reportCessna 172P · Dateland, AZDuring takeoff, the pilot was using the right side of a private strip to avoid an area of mud. At lift-off speed, the right wing tip struck a power pole near the right side of the runway and veered toward an irrigation ditch. The pilot was able to clear over…NTSB ATL83FKM01Accident · 1 fatalFinal reportCessna 172P · Near Maider, NCThe pilot crashed into trees 6 miles east of maiden, NC in deteriorating weather. Witnesses described the weather as rainy and foggy in the area of crash. Some heard the aircraft flying low before colliding with trees. The pilot was off course for statesville…NTSB NYC83LA008Accident · No injuriesLimited investigationFinal reportCessna 172P · Grahamsville, NYThe pilot and two passengers departed on a local sightseeing flight with full fuel tanks. About one hour after takeoff, the pilot flew over the passengers' house to take pictures. While a passenger was photographing the house, the pilot's attention was…NTSB ANC82DAG46Accident · No injuriesFinal reportCessna 172 · Quinhagak, AKThe pilot reported that he landed on a gravel bar about 900 ft long with a passenger to go fishing. Later, he took off to the west with a slight head wind. Near the end of the gravel bar was a tree with branches sticking out of the water. As the pilot took…NTSB CHI82DA251Accident · Serious injuriesFinal reportCessna 172P · Washington Island, WIDuring arrival, the pilot made an approach to runway 14 for a night landing. After flaring to land, the aircraft was observed to float. The pilot stated that he had come in high, and during a go-around, the aircraft did not seem to climb properly, then…NTSB DEN82FTC04Accident · 1 fatalFinal reportCessna 172P · Osage, WYThe aircraft departed gillette, Wyoming on a pipeline patrol mission. This was the pilot's first pipeline patrol over the line that he was patrolling. During the flight, the aircraft struck three powerlines and crashed. The passenger stated that he saw the…NTSB ATL82DA143Accident · No injuriesFinal reportCessna 172P · Jonesboro, GAThe pilot stated that after applying brakes on landing roll the aircraft began to hydroplane on water that was on the runway. He elected to raise the flaps and apply full power in a attempt to go-around but was unable to clear trees off the end of the runway.