Cessna (Textron Aviation) · Single-engine piston plane
Cessna 172 Skyhawk (incl. 172RG Cutlass)
Is the Cessna 172 Skyhawk (incl. 172RG Cutlass) safe? It ranks #1 of 23 small planes we rate, with 193 fatal accidents counted in about 76 million US flights since 2008.
Medium confidenceIn serviceUpdated 5 November 2026
Spot a mistake?
Cessna 172 Skyhawk (incl. 172RG Cutlass) safety score: 58 out of 100, grade C (Fair)
Likely range 53 to 63
1 in 430,000chance of dying on a flight2.33 deaths per million boardings
How the score is built
- Fatal accidents
- 193 in 75.6 million flights
2.6 fatal accidents per million flights. Counted: all civil flights in the United States since 2008 (private, training, charter and other), accidents and unexplained losses; not counted: accidents outside the United States or before 2008, military, test and illegal flights, sabotage, hijackings, shoot-downs and deliberate crew acts.
- Full-loss equivalents
- 175
Each counted accident adds the share of people on board who died (1 = no survivors). This is what the score is based on.
- Flights flown
- 75.6 million
Estimated flights of all kinds in the United States since 2008. Flights of all kinds in the United States (private, training, charter and other civil use) 2008 to 3 November 2026, each counted from take-off to final landing: the hours of all US piston singles in each year (active aircraft and hours from the FAA General Aviation and Part 135 Activity Survey), split between types by US-registered aircraft (FAA register, 20,463 of this type in 2024) times how much each type flies against its class (2.27, mostly from airframe hours in NTSB accident records, partly from hours per aircraft seen by ADS-B receivers in 2019-2022), at 0.82 hours per flight from ADS-B tracks: about 231 flights per registered aircraft per year in 2024. Flights and accidents outside the United States, or before 2008, are not used. Against the FAA's hours per helicopter model, this method is off by about 22% on a typical type. Uncertainty roughly ±25%.
- Technology generation
- Single-engine piston plane
Small fleets are pulled toward the record of the other types of their generation: 7.4 full-loss equivalents per million flights over 143 million flights. Weight of this family's own record: 100%.
- Likely range
- 53 to 63
The score is 90% likely to lie in this range, given how few accidents a type has and the error in the estimate of its flights.
- Last fatal accident
- 23 September 2026
Private, Royal City, WA, United States of America: 1 of 1 people on board died.
- Aircraft destroyed
- 101
Aircraft the NTSB coded as destroyed in an accident in the United States since 2008, fatal or not, from all causes. The NTSB codes many wrecks as only substantially damaged, so the real number is higher (context only, not in the score).
Compared with everyday risks
One flight on the Cessna 172 Skyhawk (incl. 172RG Cutlass) carries about the same risk of death as the activities near it below.
- An hour's walk1 in 14 million
- Driving 100 miles (160 km)1 in 5.9 million
- An ordinary day: accidents and violence1 in 1 million
- A day of skiing1 in 830,000
- A scuba dive1 in 500,000
- Cycling 100 miles (160 km)1 in 430,000
- One flight on the Cessna 172 Skyhawk (incl. 172RG Cutlass)This aircraft1 in 430,000
- Running a marathon1 in 290,000
- A skydive1 in 250,000
- A general anaesthetic1 in 100,000
- Riding a motorbike 100 miles (160 km)1 in 83,000
Accident history
193 fatal accidents in the United States since 2008 count toward the score, with 320 people on board killed.
| Date | Flight | Killed | What happened |
|---|---|---|---|
| Private172B · Royal City, WA, United States of America | 1 killed / 1 on board | Taking off from B & G Farms near Royal City, Washington, after 20 minutes with the engine running at the runway end, the 172 pitched up steeply, yawed and rolled left, and its nose dropped into a field. The pilot died. The investigation has not published a cause.Cause not yet established; counted.Type: Loss of control in flightNTSB docket | |
| Unknown operator172N · San Diego, CA, United States of America | 2 killed / 2 on board | After nine circuits at Montgomery-Gibbs, San Diego, with erratic go-arounds, the training 172 pitched up about 45 degrees near the threshold, rolled into a steep left turn and hit the runway and burned. The instructor and student died. The investigation has not published a cause.Cause not yet established; counted.Type: Loss of control in flightNTSB docket | |
| Atp Aircraft172S · Provo, UT, United States of America | 1 killed / 2 on board | Departing Provo, Utah, on a training flight while other aircraft reported moderate to severe turbulence, the 172 came down in shallow water by Provo Bay. The pilot under instruction died and the instructor was badly hurt. The investigation has not published a cause.Cause not yet established; counted.Type: Windshear or stormNTSB docket | |
| Idaho Skyriders Flying Club172 · Blackfoot, ID, United States of America | 1 killed / 3 on board | Just after night take-offs and landings for currency at Blackfoot, Idaho, the 172 hit the ground inside the airport fence and slid through it onto a road. The pilot died and two passengers were badly hurt. The investigation has not published a cause.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Cornerstone Aviation172 · Willard, UT, United States of America | 1 killed / 1 on board | On a solo night cross-country for commercial pilot training from Salt Lake City, the pilot flew north over dark mountain foothills instead of the planned route, and the 172 crashed near Willard, Utah; he died. The investigation has not published a cause.Cause not yet established; counted.Type: Flight into terrainNTSB docket | |
| Brockton Flying Club Inc172 · Provincetown, MA, United States of America | 1 killed / 1 on board | After waiting for snow clearing at Provincetown, Massachusetts, the pilot came back to land; the 172 crossed the threshold low, climbed slightly, then dropped onto the runway, bounced and slid to a stop in a crosswind. He died. The investigation has not published a cause.Cause not yet established; counted.Type: Hard landing or abnormal runway contactNTSB docket | |
| Apollo Flight School172N · New Orleans, LA, United States of America | 2 killed / 2 on board | On an instrument training flight from Gulfport to New Orleans Lakefront at night under an 800 ft ceiling, the 172 entered a tight descending left turn on the ILS and hit Lake Pontchartrain; the instructor and pilot died. The investigation has not published a cause.Cause not yet established; counted.Type: Loss of control in flightNTSB docket | |
| 702 Aviation172M · Poleta, CA, United States of America | 2 killed / 3 on board | Climbing from Bishop, California, toward mountains up to 9,000 ft, the rented 172 crashed in a canyon at about 7,000 ft. The pilot was badly hurt and his two passengers died; the wreck was found next morning. The investigation has not published a cause.Cause not yet established; counted.Type: Flight into terrainNTSB docket | |
| Private172F · Battle Ground, WA, United States of America | 1 killed / 1 on board | After a touch-and-go at Goheen Airport, Battle Ground, Washington, the pilot flew another circuit and turned final low; the 172 crashed near the runway end and burned, and he died. The investigation has not published a cause.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Trade Winds Aviation172S · Los Banos, CA, United States of America | 1 killed / 1 on board | Out of San Jose's Reid-Hillview, the pilot declared an emergency, saying he needed strong back pressure to stop the 172 pitching down. Other pilots tried to guide him to Los Banos, but it crashed near there and he died. The investigation has not published a cause.Cause not yet established; counted.Type: System failureNTSB docket | |
| Pilot172L · Walters, OK, United States of America | 1 killed / 1 on board | On a proficiency flight from Lawton, Oklahoma, the pilot, a flight instructor, flew turns east of the airport, then the 172 turned right, descended and hit the ground at high speed near Walters; he died. The investigation has not published a cause.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| LA Partnership172 · Billings, MT, United States of America | 1 killed / 1 on board | Five minutes after take-off from a private strip near Billings, Montana, the 172 flew over a ranch and came down under damaged power lines in a coulee; the pilot died. No fault was found in an initial check. The investigation has not published a cause.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Private172F · Brazoria, TX, United States of America | 1 killed / 1 on board | Moving his 172 from a wet grass strip at Brazoria, Texas, the pilot heard the engine backfire, stopped, then took off again. The aircraft pitched up too slow, stalled and crashed, and he died. The NTSB also cited his failure to abort when he could not keep it straight.Type: Loss of control in flightNTSB docket | |
| Quarter TO Two Flying Club Inc172N · Lock Haven, PA, United States of America | 1 killed / 1 on board | On her second solo flight, a student pilot doing landings at Lock Haven, Pennsylvania, began a climbing left turn halfway down the runway at a very low groundspeed; the 172 crashed and she died. NTSB: she turned too early, low and slow, and hit trees.Type: Loss of control in flightNTSB docket | |
| Wings Over Texas Holdings LLC172 · Gainesville, TX, United States of America | 1 killed / 2 on board | On the third take-off during practice landings at Gainesville, Texas, the 172 stopped climbing and the engine quit; the instructor glided into a field and it landed hard. The instructor died and the student was hurt. The fuel pump maker had not tightened its screws properly.Type: Engine failureNTSB docket | |
| Private172M · Brookwood, AL, United States of America | 1 killed / 1 on board | Flying low over a river near Brookwood, Alabama, the 172 hit power lines about 60-80 ft up and fell into the river; the pilot died. No fault was found. The NTSB found he did not see and avoid the lines while flying low.Type: Flight into terrainNTSB docket | |
| Ata Flight School172 · Weston, FL, United States of America | 2 killed / 2 on board | On a night flight from North Perry, Florida, two commercial pilots flew out over unlit Everglades wetland; the 172 began an ever steeper descent and hit a swamp near Weston, killing both. The NTSB found they became spatially disoriented in the dark.Type: Loss of control in flightNTSB docket | |
| Private172G · Independence, OR, United States of America | 3 killed / 3 on board | Told by an instructor not to return because of thick fog, the pilot flew back to Independence, Oregon, anyway and tried to land; the 172 hit an obstacle and all three pilots on board died. The NTSB cited continued visual flight into fog.Type: Flight into terrainNTSB docket | |
| Private172G · Provo, UT, United States of America | 2 killed / 3 on board | Flying from Spanish Fork toward Driggs to build hours, the pilot flew into a canyon with rising ground near Provo, Utah, and tried a climbing turn; the 172 stalled into trees. The pilot and a front passenger died. The NTSB cited the stall and poor performance planning.Type: Loss of control in flightNTSB docket | |
| Aeroflyin Corp172 · Pembroke Pines, FL, United States of America | 2 killed / 3 on board | Taking off from North Perry, Florida, with an instructor and two passengers, the 172 pitched up sharply to about 125 ft, rolled left and dived into the airport grounds. The instructor and the front passenger died. The NTSB found the instructor let it stall in the climb.Type: Loss of control in flightNTSB docket | |
| Private172N · San Rafael, CA, United States of America | 1 killed / 2 on board | Descending at night toward San Rafael, California, the pilot found the engine would not respond to the throttle. Carburettor heat did not help, and the 172 hit a power line and fell into a canal short of the runway; the passenger died. The NTSB cited carburettor ice.Type: Engine failureNTSB docket | |
| California Professional Flyers Inc172N · Murrieta, CA, United States of America | 1 killed / 4 on board | Two weeks after qualifying, the pilot was giving his family rides at French Valley, California. On the landing roll he heard a bang, panicked and took off again, then raised the flaps suddenly; the 172 stalled and crashed. He died and the three passengers were badly hurt.Type: Loss of control in flightNTSB docket | |
| Airmax Charters, LLC172 · Lake Worth, FL, United States of America | 2 killed / 2 on board | Just after take-off from Palm Beach County Park, Florida, the 172 rolled right to about 90 degrees of bank and descended into the ground at full power; the instructor and student died. A corroded aileron cable had broken, which maintenance staff had missed in recent inspections.Type: System failureNTSB docket | |
| Private172 · Chambers, NE, United States of America | 1 killed / 1 on board | With cloud forecast over the whole route, the pilot flew a night cross-country from Kansas toward North Dakota with no briefing or flight plan. Flying low under cloud near Chambers, Nebraska, the 172 hit the ground and he died. The NTSB cited continued visual flight into cloud.Type: Flight into terrainNTSB docket | |
| Private172S · Los Angeles, CA, United States of America | 1 killed / 1 on board | Returning in a rented 172 from Palm Springs toward Camarillo, the pilot, who had no instrument rating, descended into a forecast marine layer of low cloud and hit hilly terrain in Los Angeles; he died. The NTSB found he lost awareness of his position in the worsening weather.Type: Flight into terrainNTSB docket | |
| Unknown operator172 · London, OH, United States of America | 2 killed / 2 on board | On what was likely a student's first lesson at London, Ohio, the 172 slowed on final in gusty wind, then stalled and hit the ground beside the runway nearly vertically. The instructor and student died. The NTSB found the instructor let the airspeed fall into a stall.Type: Loss of control in flightNTSB docket | |
| Private172 · Hooker, OK, United States of America | 1 killed / 1 on board | The pilot, who had no instrument rating, flew home after dark as the weather fell to an 800 ft ceiling and mist. Near Hooker, Oklahoma, the 172 entered a descending 720-degree left turn and crashed; he died. The NTSB cited the flight into night cloud and disorientation.Type: Loss of control in flightNTSB docket | |
| Unknown operator172 · Newport News, VA, United States of America | 1 killed / 3 on board | On a student's first lesson at Newport News, Virginia, the instructor let him pull back on take-off; the 172 pitched up too far, stalled low and hit the ground. The instructor died and the other two were badly hurt. The NTSB cited her late action to stop the student.Type: Loss of control in flightNTSB docket | |
| Svetfur Aviation LLC172S · Hermantown, MN, United States of America | 3 killed / 3 on board | Taking off at night from Duluth, Minnesota, into very low cloud and mist, the pilot lost control just after departure and the 172 descended into a house in Hermantown. All three on board died. The NTSB cited spatial disorientation, with fatigue from a long day.Type: Loss of control in flightNTSB docket | |
| Unknown operator172S · Longmont, CO, United States of America | 2 killed / 2 on board | Practising manoeuvres at 7,000-7,500 ft near Longmont, Colorado, a training 172 collided with a Sonex Xenos; both aircraft were destroyed. The instructor and student and the Sonex pilot died. The NTSB found the pilots could not see and avoid each other.Type: Mid-air collisionNTSB docket | |
| Private172M · Pacific Ocean | 1 killed / 1 on board | The pilot took off at night from Watts-Woodland, California, for an unknown destination; his car was found by the empty tie-down next day. The 172 is presumed lost in the Pacific. The aircraft and pilot were never found, so no cause could be determined.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Unknown operator172N · North Las Vegas, NV, United States of America | 2 killed / 2 on board | On final at North Las Vegas, a Piper PA-46 lined up for the wrong runway descended onto this training 172. All four in the two aircraft died. The NTSB blamed the Piper pilot, the controller's late traffic warnings and the FAA's short staffing of the tower.Type: Mid-air collisionNTSB docket | |
| Private172F · Show Low, AZ, United States of America | 2 killed / 2 on board | At Show Low, Arizona, the pilot aborted a take-off with the engine sputtering, did a run-up and tried again. The 172 stayed low, turned left and sank; both on board died. A stuck exhaust valve from poor leaning cut power; the NTSB also cited the second attempt.Type: Engine failureNTSB docket | |
| Private172H · Miami, FL, United States of America | 1 killed / 3 on board | Flying along the Miami shoreline toward Key West, the pilot reported engine failure and tried to land on a bridge; the 172 came down on the causeway and the pilot died, with two passengers and five people on the ground hurt. The NTSB found carburettor ice stopped the engine.Type: Engine failureNTSB docket | |
| Private172 · Broomfield, CO, United States of America | 1 killed / 1 on board | On final at Broomfield, Colorado, after ATC moved him to the parallel runway, the 172 suddenly turned north and descended into a road intersection, then burned; the pilot died. Witnesses said it was not stalled. The NTSB could not determine why he lost control.Cause not yet established; counted.Type: Loss of control in flightNTSB docket | |
| Private172 · Altha, FL, United States of America | 2 killed / 4 on board | Taking off from Altha, Florida, with three passengers and nearly 10% over maximum weight, the 172 stayed nose high and slow, turned left and stalled into the ground east of the runway, then burned. Two of the four died. The NTSB cited the overweight take-off.Type: Loss of control in flightNTSB docket | |
| Civil Air Patrol Inc172P · Kekaha, HI, United States of America | 2 killed / 2 on board | On a routine Civil Air Patrol hurricane and tsunami warning flight over Kauai, the 172 missed its turn to the coast and flew up a ridge in poor visibility into a mountainside near Kekaha; both on board died. The NTSB cited continued visual flight into low visibility.Type: Flight into terrainNTSB docket | |
| Blue Ridge Mountain Flyers Inc172 · Dahlonega, GA, United States of America | 1 killed / 1 on board | Landing fast with flaps up at a valley airport near Dahlonega, Georgia, the low-time pilot bounced twice on the nose wheel, then decided late to go around; turning left while climbing to avoid trees, the 172 stalled and hit the ground, and he died.Type: Loss of control in flightNTSB docket | |
| Private172 · Hardy, AR, United States of America | 2 killed / 2 on board | The pilot, who had no instrument rating, flew a visual cross-country over the Ozarks in a 172 not equipped for cloud, with no weather briefing. In cloud near Hardy, Arkansas, he lost control and the aircraft crashed; both died. The NTSB also found the fuel had run out.Type: Loss of control in flightNTSB docket | |
| Unknown operator172 · Branchville, NJ, United States of America | 2 killed / 2 on board | On an instruction flight from Caldwell, New Jersey, the 172 slowed and pitched up after a power reduction at 6,400 ft, then entered a steep spiral that the instructor did not recover from; it hit woods near Branchville and both pilots died.Type: Loss of control in flightNTSB docket | |
| Mike Smith Aviation172 · Ukiah, CA, United States of America | 1 killed / 1 on board | On a solo cross-country into Ukiah, California, water in the fuel interrupted engine power during a go-around; the student aborted, the 172 hit the runway nose first and flipped. He had not refastened his seat belt and died. A tank leak had let rain into the fuel.Type: Engine failureNTSB docket | |
| Angel Aviation Inc172P · Eagle River, AK, United States of America | 2 killed / 2 on board | On a two-hour discovery flight from Merrill Field, Anchorage, the 172 hit rocky mountain terrain near Eagle River and was found nine hours late because its locator beacon failed. The instructor and pilot died. The NTSB could not establish how it came to hit the terrain.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Private172R · Missoula, MT, United States of America | 2 killed / 2 on board | Over its maximum weight, the 172 flew west from Missoula, Montana, over rising ground into a box canyon at low height and speed, then stalled too low to recover; both on board died. The NTSB found the pilot let the airspeed fall into a stall.Type: Loss of control in flightNTSB docket | |
| Flight Operations Aircraft LLC172S · Eden, UT, United States of America | 2 killed / 2 on board | On an introductory flight from Ogden, Utah, the instructor flew into a canyon near Eden to cross a mountain; about 2 miles in, a low downdraft took the 172 into rising terrain. The instructor and prospective student died. The NTSB cited the instructor's poor decision-making.Type: Flight into terrainNTSB docket | |
| Private172 · Arch Cape, OR, United States of America | 1 killed / 1 on board | Flying north along the Oregon coast from Tillamook, the 172 descended steadily in what looked like controlled flight and hit the sea by Falcon Rock off Arch Cape; a wave covered it. The pilot and wreckage were never found, and the NTSB could not determine why it descended.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Private172 · Billings, MT, United States of America | 1 killed / 1 on board | Diverting at night to Billings, Montana, after reporting windshear, strong headwinds and trouble climbing over the mountains, the pilot could not pick out the runway among other lights; the 172 came down short and he died. The NTSB could not find why he left the glide path.Cause not yet established; counted.Type: Landed short or longNTSB docket | |
| Private172 · Dunnellon, FL, United States of America | 1 killed / 1 on board | On a short local flight from Belleview, Florida, the 172 slowed from 94 to 47 kt near Marion County Airport, then turned left and descended nose low into a field; the pilot, alone, died. NTSB: fuel exhaustion, then a stall and spin.Type: FuelNTSB docket | |
| Harrier Aviation172 · Cottage Grove, MN, United States of America | 3 killed / 3 on board | On a discovery flight from South St Paul, Minnesota, with an instructor and two passengers, the 172 began a steep descent four minutes after take-off and hit water near Cottage Grove; all three died. No fault, bird strike or medical cause was found, and the cause is unknown.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Private172 · Seeley Lake, MT, United States of America | 2 killed / 3 on board | On a night flight into Seeley Lake, Montana, the pilot, who had no instrument rating, flew past the airport in wildfire smoke; the 172 hit 75 ft trees north of the field. Two of the three on board died. The NTSB found smoke put him into instrument conditions.Type: Flight into terrainNTSB docket | |
| Private172 · Lake Tahoe, CA, United States of America | 2 killed / 2 on board | Shortly after take-off from Lake Tahoe, California, the 172 flew low with the engine surging, clipped a tree and hit the ground 2.5 miles away; both on board died. The NTSB found carbon buildup in one cylinder, caused by poor mixture leaning, cut engine power.Type: Engine failureNTSB docket | |
| Private172 · Alpine, UT, United States of America | 4 killed / 4 on board | With three passengers on a summer flight from South Valley, Utah, the pilot flew into a canyon near Alpine too low to climb out and made a tight turn; the 172 rocked its wings and dropped. All four died. The NTSB found he stalled it while manoeuvring in the canyon.Type: Loss of control in flightNTSB docket | |
| Cardinal Wings Aviation LLC172 · New Washington, IN, United States of America | 1 killed / 1 on board | A student pilot on a solo practice flight before his check ride did steep turns at 3,000 ft near New Washington, Indiana, then the 172 dived at more than 10,000 ft a minute into a field; he died. No fault or medical cause was found, and the NTSB could not determine why.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Synergy Flight Center, LLC172 · Lincoln, IL, United States of America | 3 killed / 3 on board | On an aerial survey with two ecologists near Lincoln, Illinois, the pilot circled a wooded area slowly; the left wing dropped and the 172 spun about 2.5 turns onto a highway and burned. All three died. The NTSB found he stalled it too low to recover.Type: Loss of control in flightNTSB docket | |
| Private172 · Newborn, GA, United States of America | 1 killed / 1 on board | On a flight from Toccoa toward Cairo, Georgia, the 172 flew a wandering track with many 360-degree turns, then circled low and went into trees near Newbern; the pilot died. The NTSB found carbon monoxide from a worn muffler had poisoned him.Type: OtherNTSB docket | |
| Private172 · Aberdeen, SD, United States of America | 1 killed / 1 on board | A student pilot took his 172, tagged unairworthy after an inspection, from Aberdeen, South Dakota, at night in cloud with no weather briefing. It hit the ground fast 7 miles from the airport and he died. The NTSB cited the decision to fly in those conditions.Type: Flight into terrainNTSB docket | |
| Private172 · Mckenzie Bridge, OR, United States of America | 2 killed / 2 on board | Landing on a short grass strip ringed by tall trees at McKenzie Bridge, Oregon, the pilot floated low along the runway, climbed late and hit trees past its end; both on board died. The NTSB cited the late climb and his lack of mountain airport experience.Type: Flight into terrainNTSB docket | |
| West Houston Airport Corporation172 · Katy, TX, United States of America | 1 killed / 1 on board | Three minutes after take-off from West Houston, the 172 sped up from 104 to 151 kt while descending, then hit a tree, a parking lot and a building in Katy, Texas; the pilot died. The NTSB could not determine why he lost control.Cause not yet established; counted.Type: Loss of control in flightNTSB docket | |
| Civil Air Patrol Inc172 · Oxford, MS, United States of America | 1 killed / 1 on board | On a solo cross-country, a student pilot who sounded panicked on the radio approached Oxford, Mississippi, with a tailwind, did not touch down and went around; the 172 lost control and hit the ground, and she died. The NTSB found she lost control in the go-around.Type: Loss of control in flightNTSB docket | |
| Gryphon Aire LLC172 · Pescadero, CA, United States of America | 1 killed / 1 on board | At dusk a pilot not then cleared to fly club aircraft solo took a 172 from Pescadero, California, and flew along the coast; campers saw an aircraft hit the sea off Santa Cruz. Neither the pilot nor the aircraft was ever found, so the cause could not be determined.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| PrivateR172 · Mertzon, TX, United States of America | 1 killed / 1 on board | A pilot who had turned back the night before because it was too dark set out again before dawn from Seminole, Texas, toward Sealy. The 172 crashed in remote, unlit country near Mertzon and he died. The NTSB found he lost control from spatial disorientation.Type: Loss of control in flightNTSB docket | |
| Private172 · Tyrone, PA, United States of America | 2 killed / 2 on board | Warned of cloud and mountain obscuration, the pilot nonetheless flew visually from State College toward Butler, Pennsylvania; the 172 hit trees and terrain near Tyrone and both on board died. The NTSB cited continued visual flight into cloud.Type: Flight into terrainNTSB docket | |
| Unknown operator172 · Lakeway, TX, United States of America | 1 killed / 2 on board | In the pattern at Lakeway, Texas, after an aborted landing, the 172's engine began to sputter. Turning back toward the runway, the instructor let it stall; it hit a tree and a road sign. One of the two died. The NTSB could not determine why the engine lost power.Cause not yet established; counted.Type: Engine failureNTSB docket | |
| Private172 · Skwentna, AK, United States of America | 1 killed / 1 on board | Flying home from a hunting camp through Alaska mountains in snow showers with icing forecast, the pilot climbed to 6,900 ft; the 172 picked up ice, stalled and spun into terrain near Skwentna, killing him. The NTSB cited the choice to depart into that weather.Type: IcingNTSB docket | |
| New Horizon Aviation Inc172 · Mansfield, MA, United States of America | 2 killed / 2 on board | After a long float and a late touchdown on a touch-and-go at Mansfield, Massachusetts, the 172 climbed in a steep right bank against the pattern, slowed and spiralled into a grass area by the terminal. The instructor and student died. The NTSB found the instructor let it stall.Type: Loss of control in flightNTSB docket | |
| Flying Academy Los Angeles172 · Desert Hot Springs, CA, United States of America | 2 killed / 2 on board | On a night flight from El Monte toward Las Vegas, the pilot chose an altitude too low to clear the mountains; in turbulent downdrafts the 172 hit terrain near Desert Hot Springs, California, killing him and his passenger. The NTSB cited poor flight preparation.Type: Flight into terrainNTSB docket | |
| PrivateR172K · Chesaning, MI, United States of America | 1 killed / 1 on board | Doing touch-and-go landings at Chesaning, Michigan, the 172 banked steeply and dived into the ground and a building at high power; the pilot died. No fault was found, and the NTSB could not determine whether a medical problem caused the loss of control.Cause not yet established; counted.Type: Loss of control in flightNTSB docket | |
| Private172 · Rhome, TX, United States of America | 1 killed / 4 on board | Giving family members rides at Rhome Meadows, Texas, the pilot took off a third time; at about 300 ft the engine quit and the 172 turned left into trees. One of the four on board died. The NTSB found organic debris starved the engine of fuel, and the pilot had been drinking.Type: FuelNTSB docket | |
| Dean International Inc172 · Miami, FL, United States of America | 2 killed / 2 on board | Returning to Miami Executive from a training cross-country, the 172 collided almost head-on at 1,500 ft over the Everglades with a Piper Seneca on a check flight. Both on the 172 died, as did the two on the Piper. The NTSB found that neither crew saw and avoided the other.Type: Mid-air collisionNTSB docket | |
| Moody Bible Institute OF Chicago172 · Deer Park, WA, United States of America | 3 killed / 3 on board | On a student's first lesson from Felts Field, Spokane, the 172 suddenly turned sharply right and dived after hitting a large bird; the instructor could not recover before it exceeded its strength and the wings broke off near Deer Park, Washington. All three on board died.Type: Bird strikeNTSB docket | |
| Private172 · Diamondhead, MS, United States of America | 1 killed / 1 on board | A student pilot doing solo pattern work at Diamondhead, Mississippi, made a touch-and-go without raising the flaps from 40 degrees. The 172 could not climb, crossed a highway at treetop height and sank into the trees; he died. The NTSB cited the full-flap take-off.Type: Loss of control in flightNTSB docket | |
| Aero Photo172N · Rotan, TX, United States of America | 2 killed / 2 on board | Heading home after an aerial photography job, the pilot flew fast and low over a canyon near Rotan, Texas; the 172 hit power lines and the ground, killing both on board. Camera and GPS records showed the low flight. The NTSB called it a reckless decision.Type: Flight into terrainNTSB docket | |
| Middle River Aviation LLC172 · Ocean City, MD, United States of America | 2 killed / 2 on board | On a night flight from Baltimore to Ocean City, Maryland, the pilot, who had no instrument rating, descended toward the airport and the rented 172 went into the sea 2 miles from the runway. Both died. The wreckage was not recovered and the cause could not be determined.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Kent Cook Aviation172F · Williamsport, IN, United States of America | 1 killed / 1 on board | Ferrying a newly bought 172 at night from Columbus, Ohio, to Danville, Illinois, the commercial pilot ran out of fuel and the aircraft hit trees near Williamsport, Indiana; he died. The NTSB cited his fuel management.Type: FuelNTSB docket | |
| Private172M · Ogden, UT, United States of America | 2 killed / 2 on board | On a local flight from Ogden, Utah, the pilot descended low over the glassy Great Salt Lake near Promontory Point and the 172 hit the water and sank; both on board died. The NTSB cited the failure to stay clear of the water and the pilot's use of three impairing medicines.Type: Flight into terrainNTSB docket | |
| Private172G · Pittsford, VT, United States of America | 1 killed / 1 on board | An 89-year-old pilot flew visually to see family before Thanksgiving despite a briefing that advised against it. Following a highway, the 172 descended into cloud and crashed near Pittsford, Vermont; he died. The NTSB cited visual flight into cloud and spatial disorientation.Type: Loss of control in flightNTSB docket | |
| Private172N · Hatch, NM, United States of America | 4 killed / 4 on board | Taking off from Hatch, New Mexico, with three passengers, in gusty wind and high density altitude toward the setting sun, the 172 stalled and spun into desert half a mile beyond the runway; all four died and were found next evening. The NTSB cited lost airspeed in the climb.Type: Loss of control in flightNTSB docket | |
| Private172M · Ramsey, MN, United States of America | 2 killed / 2 on board | Flying at treetop height along the Mississippi River at Anoka, Minnesota, the pilot turned with a bend and hit power lines spanning the river; the 172 fell in and both on board died. The NTSB cited the illegal low flight, with the sun and the bend hiding the lines.Type: Flight into terrainNTSB docket | |
| Private172L · Perkinsville, AZ, United States of America | 2 killed / 2 on board | Instead of the touch-and-goes he had planned, a pilot qualified seven months earlier flew from Prescott into a river canyon east of Paulden, Arizona, in turbulent wind; the 172 hit the canyon wall nearly vertically and both died. The NTSB cited loss of control in the canyon.Type: Loss of control in flightNTSB docket | |
| Private172N · Bolinas, CA, United States of America | 1 killed / 1 on board | Heading to Santa Rosa, the pilot, who had no instrument rating, descended under the marine layer to follow the coast; the 172 hit Inverness Ridge at Point Reyes, California, and he died. The NTSB cited the decision to fly into forecast cloud and mountain obscuration.Type: Flight into terrainNTSB docket | |
| Arrow Aviation LLC172 · New Milford, CT, United States of America | 1 killed / 3 on board | After a touch-and-go on a grass strip at New Milford, Connecticut, with full flaps, the 172 climbed about 150 ft, stalled and hit the ground. The instructor died; the student and a passenger were hurt. The NTSB found the instructor did not make sure the flaps were set right.Type: Loss of control in flightNTSB docket | |
| Arrow Aviation LLC172 · Danbury, CT, United States of America | 1 killed / 3 on board | Taking off from Danbury, Connecticut, 59 lb over its maximum weight, the 172 began to sink over the runway, pitched nose high and stalled in a left turn. One of the three on board died. The NTSB cited the stall, with overweight reducing performance.Type: Loss of control in flightNTSB docket | |
| Private172N · Big Bear, CA, United States of America | 2 killed / 2 on board | Taking off from Big Bear, California, at 6,752 ft elevation in thin air, the 172 slowed, hung nose high at the runway end, turned downwind and sank into trees; both on board died. The NTSB found the pilot stalled it in the high density altitude.Type: Loss of control in flightNTSB docket | |
| PrivateR172K · Nome, AK, United States of America | 1 killed / 1 on board | Arriving at night in cloud after a five-hour flight from Wasilla to Nome, Alaska, the pilot tried several visual approaches; the 172 ran out of fuel, stalled and crashed, killing him. His medical barred night flying. The NTSB cited the approaches and fuel exhaustion.Type: FuelNTSB docket | |
| Mcair Aviation, LLC172S · Berthoud, CO, United States of America | 2 killed / 2 on board | Practising spins on a training flight near Berthoud, Colorado, the 172 recovered from the first spin but not the second; it spun about five turns into Culver Reservoir and the instructor and pilot died. The NTSB found they did not apply prompt, correct recovery inputs.Type: Loss of control in flightNTSB docket | |
| Private172 · Panguitch, UT, United States of America | 3 killed / 3 on board | At night in cloud over mountains, the pilot, who had no instrument rating, flew a visual cross-country from Page, Arizona, toward Salt Lake City; the 172 hit snowy terrain at 7,350 ft near Panguitch, Utah, and all three died. The NTSB cited continued visual flight into cloud.Type: Flight into terrainNTSB docket | |
| Unknown operator172 · Ramona, CA, United States of America | 1 killed / 3 on board | After a simulated engine failure in a mountain valley near Ramona, California, the 172 climbed toward rising ground and could not out-climb it. One of the three on board died. The NTSB found the instructor did not keep the aircraft clear of the terrain.Type: Flight into terrainNTSB docket | |
| Private172 · Jay, OK, United States of America | 1 killed / 1 on board | Taking off from Jay, Oklahoma, the 172's engine stopped and it came down in a field by some trees; the pilot died. The fuel selector handle was missing its securing pin. The NTSB cited poor maintenance that led to fuel starvation.Type: FuelNTSB docket | |
| Private172M · Open Water, HI, United States of America | 3 killed / 3 on board | On a flight from Molokai to Honolulu, the pilot, who had no instrument rating, flew straight into low cloud and mountain obscuration he had been warned about. The 172 turned right and descended, and radar lost it over the sea. It and the three on board were never found.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Private172N · Moss Beach, CA, United States of America | 1 killed / 2 on board | On final to Half Moon Bay, California, in a gusty crosswind, the pilot raised the flaps to fly faster; turbulence and a downdraft then rolled the 172 right and it came down onto a road, cars and two houses. One of the two on board died. The NTSB cited windshear and the flaps.Type: Windshear or stormNTSB docket | |
| Private172 · Palmer, AK, United States of America | 1 killed / 1 on board | Flying over a river valley near Wasilla, Alaska, while friends rode quad bikes, a student pilot did a touch-and-go on a gravel bar, then climbed and turned steeply; the 172 stalled and dived into the ground. He died. The NTSB found he stalled it too low to recover.Type: Loss of control in flightNTSB docket | |
| Private172 · Laytonsville, MD, United States of America | 1 killed / 1 on board | After servicing the 172 at Laytonsville, Maryland, the pilot, also its mechanic, drained the engine oil and flew without refilling it. The engine failed after take-off; turning back, the 172 stalled into the ground and he died. The NTSB cited the missing oil and the stall.Type: Engine failureNTSB docket | |
| Private172 · Hollywood, FL, United States of America | 2 killed / 2 on board | Flying low along the shore from Pompano Beach toward Key Largo, the pilot ignored ATC advice to go around a thunderstorm and flew on into extreme rain; the 172 dived into the ocean off Dania Beach, Florida, and both died. The NTSB cited poor weather planning.Type: Windshear or stormNTSB docket | |
| New Orleans Aerial Air Tours172 · New Orleans, LA, United States of America | 2 killed / 3 on board | Returning after dark from a sightseeing flight over New Orleans, the pilot descended over Lake Pontchartrain in rain and poor visibility, ignoring approach lights that showed he was far too low. The 172 hit the lake and two of the three on board died.Type: Flight into terrainNTSB docket | |
| Private172N · Terre Haute, IN, United States of America | 1 killed / 2 on board | A pilot thinking of buying the 172 flew it in the pattern at Sky King, Terre Haute, Indiana, with the owner beside him. On the second approach, low and slow, it hit a 50 ft tree and then a house; one of the two died. The NTSB cited the low approach and little recent flying.Type: Landed short or longNTSB docket | |
| Private172 · Brookings, OR, United States of America | 3 killed / 3 on board | Departing Brookings, Oregon, on a moonless night toward the ocean, the pilot, who had no instrument rating, turned left after take-off and the 172 flew into the sea 2 miles west of the airport; all three died. The NTSB found he became spatially disoriented in the dark.Type: Loss of control in flightNTSB docket | |
| Encore Flight Academy172N · Avalon, CA, United States of America | 2 killed / 2 on board | An instructor and student left Catalina Island for Van Nuys under an 800 ft ceiling with a thick marine layer to the north. The radar track ended 3 minutes later over the sea 5 miles out; only an oil slick was found. The aircraft was never found and no cause could be determined.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| 70 North LLC172 · Chugiak, AK, United States of America | 4 killed / 4 on board | On a low aerial photography flight near Birchwood, Alaska, the 172 hit one or more bald eagles, which damaged the left tailplane; the pilot lost control and it crashed into woods and burned. All four on board died. The NTSB found the bird strike caused the loss of control.Type: Bird strikeNTSB docket | |
| Private172 · Westmoreland, NY, United States of America | 2 killed / 3 on board | Taking off from a short private grass strip at Westmoreland, New York, against the owner's advice, the pilot pulled back so hard the tail hit the ground; the 172 then stalled into trees and burned. Two of the three on board died. The NTSB cited the take-off decision.Type: Loss of control in flightNTSB docket | |
| Unknown operator172N · Charleston, WV, United States of America | 1 killed / 2 on board | On an instruction take-off at Charleston, West Virginia, the 172 lifted off, pitched up and rolled left until inverted, then hit the ground beside the runway; the instructor died and the student was hurt. Her seat had likely slid back; the NTSB cited the unsecured seat.Type: Loss of control in flightNTSB docket | |
| Pilot172N · Gilmer, TX, United States of America | 1 killed / 2 on board | Flying home at night to Gilmer, Texas, without refuelling at their stop, the 172's engine stopped on final and it hit trees; one of the two on board died. No usable fuel was found. The NTSB cited poor planning, fuel exhaustion and a pattern flown too far from the runway.Type: FuelNTSB docket | |
| Private172N · Wayne, NE, United States of America | 1 killed / 1 on board | On a flight toward Sioux City, Iowa, the 172 crashed about 9 miles from Wayne, Nebraska, and the pilot, alone on board, died. The record gives no account of the flight or of a cause.Type: Unknown causeNTSB docket | |
| Private172S · Seville, FL, United States of America | 1 killed / 3 on board | Flying low and slow, between 300 and 600 ft, near Seville, Florida, the pilot met a downdraft and could not recover before the 172 hit the ground. The rear-seat passenger died; the pilot and front passenger were badly hurt. The NTSB cited the downdraft and the low, slow flight.Type: Loss of control in flightNTSB docket | |
| Private172 · Riegelwood, NC, United States of America | 1 killed / 1 on board | A man with no pilot certificate took off from a private strip near Bolton, North Carolina; the 172 hit the ground fast, left wing low, 3 miles along the route, and he died. No fault was found. The NTSB could not determine why he did not stay clear of the terrain.Cause not yet established; counted.Type: Flight into terrainNTSB docket | |
| Private172 · Martinville, IL, United States of America | 1 killed / 1 on board | A man with no pilot certificate took off from Casey, Illinois, on a personal flight; the 172 hit a soybean field 11 miles away at a 30-degree nose-down angle and he died. No fault was found. The NTSB found he did not keep clear of the terrain.Type: Flight into terrainNTSB docket | |
| Private172P · Townsend, MT, United States of America | 2 killed / 2 on board | On a dark night flight from Helena, Montana, over a 7,200 ft mountain range, the pilot, who had no instrument rating and little night experience, flew into a rock face at 5,000 ft in a steep right turn. Both on board died. The NTSB cited the decision to fly the route at night.Type: Flight into terrainNTSB docket | |
| Private172M · San Diego, CA, United States of America | 1 killed / 1 on board | Doing touch-and-go landings at Brown Field, San Diego, the 172 collided with a Sabreliner jet that the tower had turned into its path; the pilot and the four on the jet died. The NTSB blamed the controller for not identifying the aircraft in the pattern.Type: Mid-air collisionNTSB docket | |
| Fox Flying Club Inc172P · Bartlett, IL, United States of America | 1 killed / 1 on board | Returning to DuPage, Illinois, the pilot told the tower he had a rudder problem and declined help; 90 seconds later the 172 vanished from radar and hit a field. He died. Nothing wrong was found with the controls, and the NTSB could not determine why he lost control.Cause not yet established; counted.Type: Loss of control in flightNTSB docket | |
| Bag Flying Club Inc172 · Shreveport, LA, United States of America | 1 killed / 1 on board | During touch-and-go landings at Shreveport Downtown, Louisiana, the 172 climbed nose high; the pilot said he was returning, then it rolled left, nosed over and cartwheeled. He died hitting the yoke, with no shoulder harness fitted. No cause for the loss of control was found.Cause not yet established; counted.Type: Loss of control in flightNTSB docket | |
| Private172 · Penn Yan, NY, United States of America | 1 killed / 1 on board | A student pilot made unsupervised cross-country flights, then landed long and fast at Penn Yan, New York, with a tailwind and took off again. The 172 lost control in the climb and crashed; he died. The NTSB also cited a wrong flap setting for the climb.Type: Loss of control in flightNTSB docket | |
| Private172 · Sutter Creek, CA, United States of America | 2 killed / 2 on board | Returning to Sutter Creek, California, in low cloud, the pilot, who had no instrument rating, circled to find the airport; witnesses heard the engine struggling. The 172 hit a hilltop and both on board died. The NTSB found he lost control from spatial disorientation in cloud.Type: Loss of control in flightNTSB docket | |
| American Patrols Inc172M · Odessa, TX, United States of America | 1 killed / 1 on board | On a pipeline patrol near Goldsmith, Texas, the pilot likely spotted a water leak and banked very steeply at 400-500 ft to look; the 172 stalled, dived into the ground and burned, killing him. The NTSB cited an accelerated stall at low height.Type: Loss of control in flightNTSB docket | |
| Unknown operator172K · Lake Pontchartrain, LA, United States of America | 2 killed / 2 on board | Soon after a night take-off from New Orleans Lakefront on an instruction flight, the pilot said he had to return but gave no reason. The 172 went into Lake Pontchartrain; the two pilots were found days later, but the aircraft never was. The cause could not be determined.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Fredrick Flight Center172 · Hinton, VA, United States of America | 1 killed / 2 on board | Just before a training cross-country, the instructor switched to a farther destination in the mountains and gave the student no time to plan. After dark the 172 flew at 3,000 ft into a ridge in George Washington National Forest; the instructor died. The NTSB faulted him.Type: Flight into terrainNTSB docket | |
| Western New York Flying Club Inc172M · Lancaster, NY, United States of America | 2 killed / 2 on board | During a volunteer event giving young people airplane rides at Lancaster, New York, the 172 overtook and descended onto a slower Searey and the two collided. Both on the 172 died; the Searey landed. The NTSB found the 172 pilot did not keep a good lookout for known traffic.Type: Mid-air collisionNTSB docket | |
| Private172R · Okmulgee, OK, United States of America | 1 killed / 1 on board | With cloud and rain forecast along the route from Fort Worth to Tulsa, the pilot flew on visually, turned about, and tried an approach to another airport near Okmulgee, Oklahoma. The 172 then hit trees and terrain and he died. The NTSB cited continued visual flight into cloud.Type: Flight into terrainNTSB docket | |
| Unknown operator172 · Selkirk, NY, United States of America | 2 killed / 2 on board | On an instruction flight at South Albany, New York, the 172 lifted off late on the short runway; at about 100 ft the engine lost and regained power, then ran rough. It banked right and hit a parked rail car; both on board died. The NTSB could not find why the engine lost power.Cause not yet established; counted.Type: Engine failureNTSB docket | |
| T & G Flying Club172R · Willoughby Hills, OH, United States of America | 4 killed / 4 on board | Taking off at night from Willoughby Hills, Ohio, with three passengers and over maximum weight, the 172 would not climb well. The pilot turned back, but it stalled in the turn and hit the ground steeply and burned; all four died. The NTSB cited lost control and poor planning.Type: Loss of control in flightNTSB docket | |
| Cane River Aviation Inc172N · Natchitoches, LA, United States of America | 1 killed / 2 on board | At about 300 ft after take-off from Natchitoches, Louisiana, the engine lost power and shook. The pilot turned for a soybean field but overflew it and hit trees; one of the two on board died. A loose rocker stud had jammed an exhaust valve; the engine was overdue for overhaul.Type: Engine failureNTSB docket | |
| Dean International Inc172N · Elliott Key, FL, United States of America | 1 killed / 1 on board | Told to stay in the pattern at Miami Executive, a student pilot left it on a solo flight. Two hours later, 20 miles out over the ocean near Elliott Key, the 172 pitched up, then dived straight down at full power into the water; he died. The NTSB could not determine why.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Private172K · Littlefield, AZ, United States of America | 2 killed / 2 on board | A newly qualified pilot and his brother flew a rented 172 low through a narrow canyon near Littlefield, Arizona, in strong gusty wind; it hit the terrain and burned, killing both. The NTSB found he lost control in the gusts while flying low in the canyon.Type: Loss of control in flightNTSB docket | |
| PrivateR172K · Landmark, ID, United States of America | 1 killed / 1 on board | Two pilots had arranged to meet at Cascade, Idaho. Flying faster, the 172 overtook an American Champion from behind and below and hit its propeller; the 172 fell and burned, killing its pilot. The other pilot landed in a meadow. The NTSB blamed the overtaking pilot.Type: Mid-air collisionNTSB docket | |
| Phoenix East Aviation172S · Daytona Beach, FL, United States of America | 2 killed / 2 on board | Climbing out after a night touch-and-go at Daytona Beach, Florida, the 172's engine backfired and lost power. The crew turned back, the aircraft stalled and dived into the ground and burned; the instructor and pilot died. The cause of the power loss could not be determined.Cause not yet established; counted.Type: Engine failureNTSB docket | |
| Private172M · Laytonville, CA, United States of America | 1 killed / 1 on board | Making low passes over a field by the Eel River near Laytonville, California, the pilot hit a tree with the right wing, which came off; the 172 crashed into woods and he died. The NTSB found he was impaired by alcohol.Type: Flight into terrainNTSB docket | |
| Private172K · Fresno, CA, United States of America | 2 killed / 2 on board | On a dark, hazy night at Fresno Chandler, California, the pilot tried to land three times; on the third the left wing hit a 62 ft tree and the 172 dived into the ground. Both on board died. The NTSB also cited a medical condition that degraded his night vision.Type: Loss of control in flightNTSB docket | |
| Private172C · Fairbanks, AK, United States of America | 1 killed / 3 on board | Departing Fairbanks, Alaska, to take the 172 for maintenance, the pilot did not answer ATC; the aircraft turned left and hit the ground on the airport, with the engine not giving power. One of the three died. The NTSB found the tanks held too little fuel and it ran out.Type: FuelNTSB docket | |
| Unknown operator172 · Limington, ME, United States of America | 1 killed / 1 on board | On a solo take-off at Limington, Maine, a student pilot lost control; the 172 swerved off the runway to the left, hit the ground with a wing and he died. The engine ran normally. The NTSB found a medical event of unknown origin impaired him and caused the loss of control.Cause not yet established; counted.Type: Loss of control in flightNTSB docket | |
| Imsar Aviation LLC172 · Birdseye, UT, United States of America | 1 killed / 2 on board | On a radar test flight from Springville, Utah, a badly installed extra power supply short-circuited and started a fire. Landing on a road near Birdseye, the 172 hit power lines; the radar operator died and the pilot was badly hurt. The NTSB cited the installation work.Type: FireNTSB docket | |
| Flight 101, LLC172M · Waterford, MI, United States of America | 4 killed / 4 on board | Taking off from Pontiac, Michigan, with the flaps fully down and slightly overweight, the 172 would not climb past about 100 ft; the pilot said he would return, but it hit the ground and burned. All four died. The NTSB found he had not retracted the flaps, being new to the type.Type: Loss of control in flightNTSB docket | |
| Newton Flying Club Inc172K · Newton, MS, United States of America | 1 killed / 2 on board | Landing at Newton, Mississippi, the student did not add power when the instructor told him to, and the instructor took over late; the 172 hit a static wire short of the runway. One of the two died. The student had not used the hearing aid his medical required.Type: Flight into terrainNTSB docket | |
| Westwind School OF Aeronautics172S · Anthem, AZ, United States of America | 2 killed / 2 on board | Two training aircraft, this 172 and a Piper PA-28, turned at the same time in a busy practice area northwest of Deer Valley, Phoenix, and collided; both on the 172 died. The NTSB found that both crews did not keep an adequate lookout.Type: Mid-air collisionNTSB docket | |
| Private172M · Calabasas, CA, United States of America | 2 killed / 2 on board | Over the Santa Monica Mountains near Calabasas, California, this 172 collided with a Cessna 172RG on a training flight and fell into the hills; both people on board died. The NTSB found that the pilots of both aircraft did not keep an adequate lookout.Type: Mid-air collisionNTSB docket | |
| Private172M · Saratoga, WY, United States of America | 1 killed / 1 on board | Flying low under broken cloud toward mountains near Saratoga, Wyoming, the pilot circled several times to get around the weather, then the 172 crashed and he died. The NTSB cited the decision to fly into bad weather, mountain cloud and turbulence, and a lost control.Type: Loss of control in flightNTSB docket | |
| Flying Start Aero172S · Minden, NV, United States of America | 1 killed / 1 on board | Taking off late in the day from Minden, Nevada, the pilot climbed to 11,400 ft over the mountains, turned back west, then the 172 entered a rapid descent and crashed 14 miles from the airport; he died and was found the next day. The NTSB found he lost control over the mountains.Type: Loss of control in flightNTSB docket | |
| Private172S · Kahului, HI, United States of America | 1 killed / 1 on board | On a night flight from Maui to Molokai in rain, the pilot, who had no instrument rating, began a 360-degree turn and the 172 descended and was lost; some parts were found but not the pilot. The NTSB found he lost control from spatial disorientation over the dark sea.Type: Loss of control in flightNTSB docket | |
| Private172K · Savannah, GA, United States of America | 1 killed / 1 on board | On a night ILS approach to Savannah, Georgia, in cloud, the pilot flew through the localizer, turned, and said he was trying to recover; the 172 spiralled into a salt marsh and he died. The NTSB found he lost control from spatial disorientation.Type: Loss of control in flightNTSB docket | |
| Private172N · Owls Head, ME, United States of America | 3 killed / 3 on board | At lift-off on a dusk take-off from Rockland, Maine, the 172 hit a private car crossing the runway, which tore off the right elevator. The pilot kept flying, but the 172 stalled and spun in; all three died. The NTSB blamed the driver and the decision to continue with damage.Type: Ground collisionNTSB docket | |
| Flightline Leasing Inc172R · Simpson, LA, United States of America | 1 killed / 1 on board | On a night cross-country in a rented 172 from Pineville, Louisiana, toward Orange, Texas, the pilot flew between areas of rain; the aircraft hit a tree and the ground near Simpson and he died. The NTSB found he lost control while manoeuvring between the showers.Type: Loss of control in flightNTSB docket | |
| Private172S · Land O'lakes, FL, United States of America | 1 killed / 1 on board | Flying home at night in a 172 he had just bought, the pilot began a gentle descent toward Tampa and never answered ATC; the aircraft flew into trees and pasture near Land O' Lakes, Florida, and he died. The NTSB found he fell asleep after days of too little rest.Type: Flight into terrainNTSB docket | |
| Interstate Aviation Inc172P · Plainville, CT, United States of America | 1 killed / 1 on board | On a second approach to his home airport at Plainville, Connecticut, in good weather, the pilot flew low, the nose dropped and the 172 hit a berm just before the runway and burned; he died. No fault was found. The NTSB cited a failure to keep the proper glidepath.Type: Landed short or longNTSB docket | |
| Private172 · Veneta, OR, United States of America | 4 killed / 4 on board | Just after take-off from a grass strip at Veneta, Oregon, the 172 failed to climb clear of 100 ft trees and came down into them; all four on board died. The NTSB found the pilot did not keep enough airspeed and height to clear the trees.Type: Flight into terrainNTSB docket | |
| Diamond Flying LLC172S · St. George, UT, United States of America | 4 killed / 4 on board | After drinking at a party, the pilot took off at 1:20 am from St George, Utah, with three friends to go gambling, 160 lb over maximum weight. The 172 pitched up steeply, stalled and dived into the ground by the runway; all four died. The NTSB cited alcohol and overweight.Type: Loss of control in flightNTSB docket | |
| Mcair Aviation LLC172S · Longmont, CO, United States of America | 2 killed / 2 on board | A training 172 and a Cessna 180 on slowly converging paths collided at about 7,200 ft near Longmont, Colorado, in clear weather. The 172 descended into the ground and both on board died; the 180 landed. The NTSB found that neither pilot kept an adequate lookout.Type: Mid-air collisionNTSB docket | |
| Dean International Inc.172S · Key West, FL, United States of America | 2 killed / 2 on board | Returning a rented 172 from the Bahamas, two pilots waited at Key West, Florida, for a presidential flight restriction to end, then left on a dark night. The 172 flew erratically and hit the water; both died. The NTSB cited a pilot not qualified for night flight.Type: Loss of control in flightNTSB docket | |
| Private172S · North Bend, WA, United States of America | 3 killed / 3 on board | On a dark night flight from Renton, Washington, under low cloud, the 172 flew into the western face of Mount Si near North Bend; all three died. The NTSB found the pilot was impaired by alcohol, which affected his ability to clear the terrain.Type: Flight into terrainNTSB docket | |
| Pro Flite Aviation172N · Floresville, TX, United States of America | 1 killed / 1 on board | Returning to San Antonio from a local flight, the 172 vanished from radar and hit an open field almost vertically; the pilot died. No fault was found in the aircraft. The NTSB found he was likely incapacitated by a sudden heart arrhythmia or heart attack.Type: Loss of control in flightNTSB docket | |
| US Aviation Group LLC172R · Denton, TX, United States of America | 1 killed / 3 on board | Flying the ILS into Denton, Texas, under a 200 ft fog ceiling, the pilots found they were not lined up and tried to circle to the other runway below minimums instead of going around. The 172 hit terrain in a left turn; one of the three on board died.Type: Flight into terrainNTSB docket | |
| Bear Butte Flying Club172M · Sturgis, SD, United States of America | 1 killed / 1 on board | On a solo touch-and-go at Sturgis, South Dakota, the student pilot took off again with the flaps still down; the 172 pitched up steeply, spun half a turn and hit the ground vertically, killing him. The NTSB found he lost control taking off with flaps extended.Type: Loss of control in flightNTSB docket | |
| Private172M · Greenville, ME, United States of America | 1 killed / 1 on board | Circling low near Greenville, Maine, while waving to people on the ground, the pilot let the 172 pitch up and slow, then it stalled, spun and hit the ground; he died. The NTSB found he did not keep enough airspeed at low altitude.Type: Loss of control in flightNTSB docket | |
| Titusville Aeroclub Inc172M · Titusville, PA, United States of America | 2 killed / 2 on board | Returning at night to Titusville, Pennsylvania, on a training cross-country, the instructor and student tried to descend visually into thick ground fog; the 172 hit trees half a mile from the airport and both died. The NTSB cited the instructor's decision to descend into fog.Type: Flight into terrainNTSB docket | |
| Private172M · Poughkeepsie, NY, United States of America | 2 killed / 2 on board | On short final at Poughkeepsie, New York, in good weather, the 172 suddenly nosed down into a field a quarter mile before the runway; both on board died. The NTSB found the pilot was likely incapacitated by heart disease that he had not fully reported to the FAA.Type: Loss of control in flightNTSB docket | |
| C/o G&b Investment Management Inc172R · Wendover, UT, United States of America | 4 killed / 4 on board | Lost and low on fuel after two hours, the pilot asked ATC for help and diverted to Wendover, Utah, where he tried to land in a strong gusty crosswind with the 172 loaded beyond its aft limit. On a go-around it stalled in the downwind turn and spun in; all four died.Type: Loss of control in flightNTSB docket | |
| PrivateR172K · Cold Springs, NV, United States of America | 3 killed / 3 on board | Flying the owner's 172 to Reno, the pilot cancelled his IFR clearance and went on visually toward forecast snow and mountain cloud. The aircraft flew into terrain 22 miles northwest of Reno and all three died. The NTSB cited continued visual flight into cloud.Type: Flight into terrainNTSB docket | |
| Phoenix East Aviation172S · New Smyrna Beach, FL, United States of America | 2 killed / 2 on board | Near sunset at the end of an instrument training flight, the 172 circled tightly offshore near New Smyrna Beach, Florida, then dived into the sea; the instructor and pilot died. The NTSB cited spatial disorientation and the instructor's failure to correct it.Type: Loss of control in flightNTSB docket | |
| Flynfish LLC172S · North Myrtle Beach, SC, United States of America | 1 killed / 1 on board | Practising instrument approaches at North Myrtle Beach, South Carolina, the pilot told ATC during the missed approach that he was disoriented; the 172 then crashed and he died. The NTSB found he lost control from spatial disorientation.Type: Loss of control in flightNTSB docket | |
| Private172H · Walnut Grove, MO, United States of America | 1 killed / 1 on board | On the fourth leg of a long day of flying, at night near Walnut Grove, Missouri, the 172 left level cruise in a descending left spiral and hit a field; the pilot died. No fault was found. The NTSB could not determine why he lost control, and named fatigue as a factor.Cause not yet established; counted.Type: Loss of control in flightNTSB docket | |
| Private172H · Weyers Cave, VA, United States of America | 2 killed / 2 on board | Joining the pattern at Weyers Cave, Virginia, 500 ft below pattern height and against the traffic flow, the 172 collided with a descending medical helicopter; its right wing came off and both on board died. The helicopter landed. The NTSB cited the limits of see-and-avoid.Type: Mid-air collisionNTSB docket | |
| Eagle Sky Patrol, Inc.172M · Velma, OK, United States of America | 1 killed / 1 on board | On a pipeline patrol near Duncan, Oklahoma, the pilot circled a leak to guide a ground crew; on the fifth circle the 172 rolled hard left, dropped its nose, hit power lines and crashed, killing him. The NTSB found he stalled it while manoeuvring, with little patrol experience.Type: Loss of control in flightNTSB docket | |
| Private172 · Panguitch, UT, United States of America | 2 killed / 2 on board | On an elk-spotting flight in Utah's Dixie National Forest, the 172 hit trees and terrain in a remote canyon at 9,600 ft in strong wind and thin air; both on board died. The NTSB cited the choice to fly low into the canyon in those conditions.Type: Flight into terrainNTSB docket | |
| Flight Training Express LLC172 · Chatsworth, GA, United States of America | 2 killed / 3 on board | About two and a half hours into a flight to Chattanooga, the pilot cancelled his IFR plan, changed destination and then reported engine failure. The 172 hit a tree and the ground at Spring Place, Georgia; two of the three died. The NTSB found the tanks had run almost dry.Type: FuelNTSB docket | |
| Private172 · Orange, MA, United States of America | 2 killed / 2 on board | Climbing out from Orange, Massachusetts, on a dark night, the 172 turned on course, then entered a descending left turn and hit trees; both pilots died. No mechanical fault was found. The NTSB found they lost control from spatial disorientation.Type: Loss of control in flightNTSB docket | |
| Private172P · Chesapeake, VA, United States of America | 1 killed / 1 on board | After circling low near Chesapeake, Virginia, for half an hour, the pilot radioed mayday and reported a flight control problem; the 172 then dived into a corn field and he died. Tests found no fault in the aircraft. The NTSB could not determine why it hit the ground.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Private172N · Angels Camp, CA, United States of America | 1 killed / 1 on board | Witnesses saw the borrowed Cessna 172N circle low with sharp turns and dives near Angels Camp, California, before it hit hilly ground; the pilot, alone, died. The NTSB found he lost control while maneuvering.Type: Loss of control in flightNTSB docket | |
| Private172H · Archer, FL, United States of America | 1 killed / 1 on board | Arriving at a grass strip near Archer, Florida, the 172 stalled and hit a pasture beside the runway, nose low. The pilot was found an hour later and died in hospital. The NTSB found he let the airspeed get too low while manoeuvring but could not determine why.Cause not yet established; counted.Type: Loss of control in flightNTSB docket | |
| Private172E · West Milford, NJ, United States of America | 1 killed / 2 on board | Soon after take-off from Greenwood Lake, New Jersey, in a 172 bought four weeks earlier after years parked outdoors, the engine stopped and the aircraft hit terrain. The pilot died and the student pilot co-owner was badly hurt. The NTSB found the engine was starved of fuel.Type: FuelNTSB docket | |
| Private172D · Hillsboro, OH, United States of America | 1 killed / 1 on board | On a night flight at Hillsboro, Ohio, the 172 hit the runway steeply at high power about 100 ft past the threshold and broke up; the pilot died and was found next morning. No fault was found. The NTSB could not determine why it hit the runway.Cause not yet established; counted.Type: Unknown causeNTSB docket | |
| Tulip City Air Service172 · Holland, MI, United States of America | 2 killed / 2 on board | The pilot rented a 172 to give friends rides and took off from Holland, Michigan, into low cloud without recent instrument practice. He lost control and the aircraft spun into a snowy field; both on board died. The NTSB cited the take-off into cloud and a lack of rest.Type: Loss of control in flightNTSB docket | |
| American King Air Services, Inc.172S · Greenbush, ME, United States of America | 1 killed / 1 on board | On a ferry flight of a new 172 from Bangor, Maine, toward Goose Bay and the Atlantic, the overweight aircraft met turbulence and icing and fell into the Penobscot River; the pilot died. The NTSB cited the decision to try the ocean crossing in icing without de-icing gear.Type: IcingNTSB docket | |
| Ramz Enterprises172S · Kissimmee, FL, United States of America | 4 killed / 4 on board | With cloud at the airport, the pilot, who had no instrument rating, took off at night from Kissimmee, Florida, on a special VFR clearance. The 172 turned and fell 2,400 ft in 12 seconds into Lake Russell; all four died. The NTSB cited the departure into cloud and disorientation.Type: Loss of control in flightNTSB docket | |
| Eagle Air Corp172S · Tallahassee, FL, United States of America | 2 killed / 2 on board | Taking off at night from Tallahassee, Florida, the 172 turned toward a large unlit forest, then curved down to the left into the trees; both pilots died. The NTSB found they became spatially disoriented with no visible horizon.Type: Loss of control in flightNTSB docket | |
| Sky Training LLC172P · Bennington, VT, United States of America | 1 killed / 1 on board | Landing at night at Bennington, Vermont, the pilot flew a right-hand pattern over higher ground than the published left-hand one, after two go-arounds. The 172 hit trees on the base leg and he died. The NTSB cited the failure to clear terrain on the night approach.Type: Flight into terrainNTSB docket | |
| Private172 · Lowndesville, SC, United States of America | 2 killed / 2 on board | The pilot, with no instrument rating and no weather briefing, flew on into very low cloud near Lake Russell, South Carolina; witnesses saw the 172 dive out of the cloud into the lake. Both died. The NTSB cited poor planning and spatial disorientation after entering cloud.Type: Loss of control in flightNTSB docket | |
| Private172 · Latimer, IA, United States of America | 1 killed / 1 on board | Flying low near Latimer, Iowa, the 172 hit a 70 ft power line over a road and dived into the ground; the pilot died. No mechanical fault was found. The NTSB cited the failure to clear the power line at low altitude.Type: Flight into terrainNTSB docket | |
| Private172M · Rimrock, WA, United States of America | 2 killed / 3 on board | Landing for the first time on a mountain grass strip at Rimrock, Washington, with a gusty tailwind, the pilot came in high and fast, added power late and hit trees beyond the runway end; two of the three on board died. The NTSB cited a late go-around and little experience.Type: Flight into terrainNTSB docket | |
| Aero Aviation LLC172N · Long Beach, CA, United States of America | 2 killed / 2 on board | Practising manoeuvres in a common training area over the sea off Long Beach, California, the 172 collided with a fast Cessna 310 coming from the west. Both on the 172 died. The NTSB found that neither pilot saw and avoided the other.Type: Mid-air collisionNTSB docket | |
| Golden Wings Flying Club172N · Oceanside, CA, United States of America | 1 killed / 1 on board | On a local flight from San Diego the 172 stayed above 14,000 ft for over 40 minutes, then dived into the Pacific 30 miles east of San Clemente Island. The pilot and most of the wreckage were never recovered. The NTSB could not determine why control was lost.Cause not yet established; counted.Type: Loss of control in flightNTSB docket | |
| Private172 · Hardin, KY, United States of America | 1 killed / 1 on board | Before sunrise, the pilot flew out from Murray, Kentucky, turned back, and about 10 miles from the airport the 172 dived almost vertically into the ground; he died. No fault was found. The NTSB found he lost control while impaired by marijuana used shortly before.Type: Loss of control in flightNTSB docket | |
| Naples Air Center172S · Goodland, FL, United States of America | 1 killed / 1 on board | On a night practice flight over water with few visual references south of Naples, Florida, the 172 dived into a mud flat near Marco Island and the pilot died. He had no instrument rating. The NTSB found he lost control from spatial disorientation in the dark.Type: Loss of control in flightNTSB docket | |
| Private172 · Lompoc, CA, United States of America | 1 killed / 1 on board | On a very slow, low approach to Lompoc, California, with the engine at idle, the 172 flew into a power line a third of a mile short of the runway; the pilot died. His medical and flight review had expired. The NTSB cited the failure to clear the line.Type: Flight into terrainNTSB docket | |
| Unknown operator172R · Ft. Lauderdale, FL, United States of America | 2 killed / 2 on board | Two training aircraft collided at about 2,000 ft over a busy practice area 18 miles west of Fort Lauderdale: this 172 and a Piper Seminole. The two pilots in each aircraft died. The NTSB found that neither crew saw and avoided the other.Type: Mid-air collisionNTSB docket | |
| York Aviation, Inc.172L · York, NE, United States of America | 2 killed / 2 on board | Starting touch-and-go landings at York, Nebraska, the 172 climbed about 100 ft and then nosed down into the ground; the instructor and the student died. No fault was found. The NTSB found the student lost control and the instructor did not correct it, for undetermined reasons.Cause not yet established; counted.Type: Loss of control in flightNTSB docket | |
| Franklin AviationR172K · Rock Springs, WY, United States of America | 1 killed / 1 on board | A student pilot on a solo practice flight near Rock Springs, Wyoming, collided with a Cirrus SR22 that was descending toward the airport; both aircraft burned. The student and the two people in the Cirrus died. The NTSB found that neither pilot saw and avoided the other.Type: Mid-air collisionNTSB docket | |
| Advantage Aviation Inc.172S · Incline Village, NV, United States of America | 1 killed / 1 on board | A student pilot flew a night cross-country to a Reno casino without his instructor's approval or training for it. The 172 flew into mountains near Incline Village, Nevada, and he died. The NTSB cited a flight he was not approved or qualified for and the dark night.Type: Flight into terrainNTSB docket | |
| Private172K · Gearhart, OR, United States of America | 2 killed / 2 on board | Taking off from Seaside, Oregon, into a 300 ft overcast, the 172 climbed into a tightening left spiral, then dived into a vacation home about a mile away; the house burned and both on board died. The NTSB found the pilot lost control from spatial disorientation.Type: Loss of control in flightNTSB docket | |
| Private172N · Mcmurray, WA, United States of America | 3 killed / 3 on board | On a visual flight from Roche Harbor to Auburn, Washington, the pilot flew on into low cloud over hilly terrain near McMurray; the 172 hit trees and the ground, killing all three. The NTSB cited the decision to continue visual flight into cloud.Type: Flight into terrainNTSB docket | |
| San Diego Flight Training International, Inc.172S · Oceanside, CA, United States of America | 2 killed / 3 on board | Flying home to San Diego, the pilot told friends he would spin the 172. After one spin and recovery he entered a longer spin and did not recover; it hit the sea off Oceanside. Two of the three on board died. Spins are prohibited with the rear seat occupied.Type: Loss of control in flightNTSB docket | |
| Unknown operator172M · Pahala, HI, United States of America | 3 killed / 3 on board | On an air tour around the Big Island of Hawaii, the pilot left the planned shoreline route in fog and rain and flew into cloud. The 172 hit the side of Mauna Loa at 4,500 ft and was found five days later; all three died. The NTSB cited continued visual flight into cloud.Type: Flight into terrainNTSB docket | |
| Redtail Aviation Inc172R · Monticello, UT, United States of America | 2 killed / 2 on board | On a two-hour sightseeing tour from Moab, Utah, the pilot stopped answering the radio; a hiker saw the 172 flying below a canyon rim in steep banks before it hit the terrain, killing both on board. The NTSB could not determine why it hit the terrain.Cause not yet established; counted.Type: Flight into terrainNTSB docket | |
| Private172 · Mccall, ID, United States of America | 3 killed / 4 on board | Over the approach end of runway 34 at McCall, Idaho, two Cessna 172s collided as both tried to land and burned. Three of the four people in this aircraft died. The NTSB cited this pilot's poor lookout, and the other pilot's non-standard pattern entry.Type: Mid-air collisionNTSB docket | |
| Private172K · Roseglen, ND, United States of America | 2 killed / 2 on board | Flying at night near his farm northwest of Garrison, North Dakota, the pilot hit a 40 ft television antenna next to his home and crashed into a hayfield; both on board died. The NTSB cited the low flight in the dark and alcohol impairment.Type: Flight into terrainNTSB docket | |
| Kemper Aviation172 · Indiantown, FL, United States of America | 4 killed / 4 on board | On a low bird-survey flight over ranch land in Martin County, Florida, the 172 nosed down in a circling pass at about 300 ft and spun into the ground; all four died. The NTSB cited low airspeed, with the aircraft over its maximum weight and the stall warning out of order.Type: Loss of control in flightNTSB docket | |
| Private172M · Gun Barrel City, TX, United States of America | 1 killed / 2 on board | A pilot with no pilot certificate flew low to buzz a friend in a park near Gun Barrel City, Texas. The right wing hit a power line and the 172 crashed; one of the two on board died. The NTSB cited the failure to avoid the line and the decision to fly the low pass.Type: Flight into terrainNTSB docket | |
| Funoutside172N · Corona, CA, United States of America | 2 killed / 2 on board | Joining the traffic pattern at Corona, California, the 172 collided with a Cessna 150 entering the downwind leg. Both broke up over a built-up area; all four on board and one person on the ground died. The NTSB found neither pilot saw and avoided the other.Type: Mid-air collisionNTSB docket | |
| Private172L · Clearwater, FL, United States of America | 3 killed / 3 on board | Returning to Clearwater, Florida, the pilot lined up for the wrong runway, then turned sharply right; the 172 stalled into Tampa Bay short of the runway, killing all three. The NTSB cited lost airspeed while manoeuvring, with the aircraft slightly over its maximum weight.Type: Loss of control in flightNTSB docket |
Listed but not counted
These events happened on military, test or illegal flights, or were caused by a crime or a deliberate act, which says little about the aircraft design.
| Date | Flight | Killed | Why not counted |
|---|---|---|---|
| Westerly Air172N · Westerly, RI, United States of America | 1 killed / 1 on board | Test flight. On a test flight after maintenance at Westerly, Rhode Island, to check the alternator, the 172 flew very low and slow, then banked steeply right, rolled nearly inverted and hit a farm field; the pilot died. The investigation has not published a cause.Type: Loss of control in flightNTSB docket | |
| Private172S · Direct, TX, United States of America | 1 killed / 1 on board | Deliberate act by a crew member. A flight school student took a 172 from Addison, Texas, without permission, told the tower he would stop following instructions and flew east. Over 100 miles later it climbed to 11,000 ft, then dived into a field near Direct; he died. The NTSB found he crashed on purpose.Type: OtherNTSB docket | |
| JD Schools Llc.172 · Atlantic Ocean | 1 killed / 1 on board | Deliberate act by a crew member. Flying out from Pompano Beach, Florida, the 172 circled, then headed out to sea and went into the Atlantic 15 miles east; the pilot died. His wife had received a note, and the medical examiner ruled the death a suicide. The NTSB gave the pilot's suicide as the cause.Type: OtherNTSB docket | |
| Private172 · Anchorage, AK, United States of America | 1 killed / 1 on board | Deliberate act by a crew member. The pilot took a 172 from Merrill Field without permission and flew it very low into the corner of an office building in downtown Anchorage, Alaska; it burned and he died. The NTSB found the pilot flew into the building on purpose, and the FBI took over the investigation.Type: OtherNTSB docket | |
| Private172S · Davenport, CA, United States of America | 1 killed / 1 on board | Illegal flight (stolen aircraft, smuggling or no licence). A contract flight instructor took a 172 from Palo Alto, California, at night without permission; police later listed it as stolen. Radar tracked it south over the Pacific off the coast until it vanished. The aircraft and pilot were never found, so no cause could be determined.Type: Unknown causeNTSB docket | |
| Jls Aviation, LLC172M · Fredericksburg, VA, United States of America | 1 killed / 1 on board | Deliberate act by a crew member. After an argument with his fiancée at Fredericksburg, Virginia, the pilot took off; the 172 climbed to about 3,000 ft and then dived at full power into the ground. He died. The NTSB found he crashed on purpose to take his own life.Type: OtherNTSB docket | |
| Private172B · Atlantic Ocean | 1 killed / 1 on board | Deliberate act by a crew member. Before dawn the pilot took off from Herlong, Jacksonville, Florida, with no transponder signal, flew out over the Atlantic and went into the sea about 21 miles offshore; he was never found. A suicide note was in his car, and the NTSB gave the pilot's suicidal act as the cause.Type: OtherNTSB docket | |
| Private172N · Fresno, CA, United States of America | 1 killed / 1 on board | Illegal flight (stolen aircraft, smuggling or no licence). A man with no pilot certificate flew a stolen 172 at power-line height west of Fresno, California, with the engine sputtering; it banked right, hit the lines and fell, killing him. The NTSB cited the failure to clear the lines and impairment from methamphetamine.Type: Flight into terrainNTSB docket |
The NTSB lists 3 more fatal events of the Cessna 172 Skyhawk (incl. 172RG Cutlass) in Puerto Rico, the US Virgin Islands or another US territory, or on a route outside the US states. They are not used, because the flight count covers US flights since 2008 only.
Most American pilots learn on the Cessna 172, and its US record since 2008 puts it at the top of the small planes we rate. Up to 28 October 2026, 193 fatal US accidents count toward its score. Most were private flights, and the most common pattern is a loss of control, often at night, in cloud or with too much weight on board.
Who flies the Cessna 172?
Cessna has built about 45,000 since 1956, more than any other aircraft. It is a four-seat, high-wing single with fixed landing gear (the 172RG Cutlass has retractable gear). The US register held about 20,700 in 2026, down from 25,200 in 2008. Flight schools, clubs and rental fleets use it more than any other type; owners fly it on short trips, and a few air-tour firms use it.
How is a small plane scored?
The count covers only the United States since 2008: fatal accidents from the NTSB database, against about 76 million flights (take-off to final landing; touch-and-goes do not count) estimated from the FAA aircraft register and General Aviation survey. The survey gives hours for all single-engine pistons together, so we split them by how much each type flies, measured mostly from airframe hours in NTSB accident records since 2008 and partly from hours per aircraft seen by ADS-B receivers from 2019 to 2022. Both show that a school 172 flies far more each year than the average owner's aircraft. That is why the 172's flight count is so large next to its fleet. Only US-registered aircraft that the register keeps in the flight count are counted on the accident side too.
Small planes have their own ranking, and a flight in any of them carries far more risk than an airline flight. Among small planes, the 172 is at the top, just ahead of two other trainers, the Diamond DA40 and the Cessna 150 and 152; the gaps are small and their likely ranges overlap, so the difference is uncertain. It is also ahead of the Piper PA-44 Seminole and the Piper PA-28, though their ranges overlap too, and clearly ahead of the Cessna 182 and fast touring types such as the Cirrus SR22.
What goes wrong in a 172?
Of the 193, 142 were private and other flights, 45 training flights, three ferry flights and three air tours. Loss of control is the largest group (80), then flight into terrain (44) and mid-air collisions (15). About a third of the accident summaries mention night, cloud, fog or poor visibility, and 17 mention disorientation. At least five crashes followed a take-off over the maximum weight, among them two in which all four on board died: Waterford, Michigan, on 21 June 2013, and Willoughby Hills, Ohio, on 25 August 2014.
Nine of the 15 mid-air collisions involved a training flight, mostly over busy practice areas, as near Longmont, Colorado, on 17 September 2022, when a training 172 and a Sonex collided and all three people in them died.
One of the rare findings about the aircraft came at Lake Worth, Florida, on 26 May 2023. A corroded aileron cable that inspections had missed broke after take-off, and both on board died.
Is it safe to learn to fly in a 172?
In several of the 45 training accidents, the NTSB found that an instructor let the aircraft stall close to the ground, as at London, Ohio, on 18 April 2023. The latest, at Montgomery-Gibbs, San Diego, on 7 September 2026, killed an instructor and a student; no cause is published yet. Before you sign up:
- Look up the instructor in the FAA Airmen Inquiry and the school's aircraft by N-number in the NTSB CAROL database.
- Aircraft used for instruction need a 100-hour inspection; ask to see the last one.
- Ask whether the aircraft show other traffic on an ADS-B display, and how the school keeps students apart in the practice area.
Renting one or riding along
Do the weight and balance with real weights on every flight: four adults and full tanks usually exceed a 172's limit. Without an instrument rating and recent practice, stay away from cloud and from night flights over dark ground or water. For an air tour, such as the Island Hoppers flight that hit Mauna Loa, Hawaii, in fog on 17 June 2008, ask whether the operator flies under Part 135 or Part 91 with an FAA letter of authorisation, and when it cancels for weather.
How to tell if you are on one
Flight trackers show C172, or C72R for the 172RG. The bigger Cessna 182 looks similar; the small-planes ranking compares them all.
Questions people ask
Is the Cessna 172 a safe plane?
For a small plane, yes. Its US record per flight since 2008 puts it at the top of the small planes we rate, and few official findings point to the aircraft itself. A flight in any small plane still carries far more risk than an airline flight, so the pilot's experience and choices matter most.
How many Cessna 172 crashes are there each year?
In the United States, 193 fatal accidents count toward our score from 2008 up to 28 October 2026, about ten a year. The yearly number has been lower in recent years, partly because fewer 172s are registered than in 2008. Eight more are listed but not counted: five deliberate acts, one test flight and two illegal flights.
Is the Cessna 172 safe for student pilots?
It is the most common US trainer because it is stable and easy to fly. Of the 193 counted accidents, 45 were training flights. Choose a school with a clear maintenance record and experienced instructors, and check its history in the NTSB database.
Is the Cessna 172 safer than the Piper Cherokee?
The 172's US record per flight since 2008 is better than the PA-28's in our data, and the 172 ranks ahead, but their likely score ranges overlap. The Piper PA-28 family, which includes the Cherokee, Warrior and Archer, does the same jobs as the 172, so the difference says little about either design.
Is it safe to fly with a friend in a Cessna 172?
It depends mostly on the pilot. Ask how many hours they have flown in the last three months, whether they hold an instrument rating, and how they will handle weather and darkness. Do not go if the flight means four adults and full tanks without a weight check.
Sources
- 1.NTSB docket: Cessna 172S, Longmont, Colorado, 17 September 2022 (opens in a new tab) · National Transportation Safety Board
- 2.NTSB docket: Cessna 172M, Waterford, Michigan, 21 June 2013 (opens in a new tab) · National Transportation Safety Board
- 3.NTSB docket: Cessna 172R, Willoughby Hills, Ohio, 25 August 2014 (opens in a new tab) · National Transportation Safety Board
- 4.NTSB docket: Cessna 172, Lake Worth, Florida, 26 May 2023 (opens in a new tab) · National Transportation Safety Board
- 5.NTSB docket: Cessna 172, London, Ohio, 18 April 2023 (opens in a new tab) · National Transportation Safety Board
- 6.NTSB docket: Cessna 172M, Pahala, Hawaii, 17 June 2008 (opens in a new tab) · National Transportation Safety Board
- 7.NTSB docket: Cessna 172N, San Diego, California, 7 September 2026 (opens in a new tab) · National Transportation Safety Board
- 8.SafetyScorer exposure model: FAA aircraft register, FAA General Aviation and Part 135 Activity Survey, OpenSky ADS-B, NTSB airframe hours (opens in a new tab)Flights of all kinds in the United States (private, training, charter and other civil use) 2008 to 3 November 2026, each counted from take-off to final landing: the hours of all US piston singles in each year (active aircraft and hours from the FAA General Aviation and Part 135 Activity Survey), split between types by US-registered aircraft (FAA register, 20,463 of this type in 2024) times how much each type flies against its class (2.27, mostly from airframe hours in NTSB accident records, partly from hours per aircraft seen by ADS-B receivers in 2019-2022), at 0.82 hours per flight from ADS-B tracks: about 231 flights per registered aircraft per year in 2024. Flights and accidents outside the United States, or before 2008, are not used. Against the FAA's hours per helicopter model, this method is off by about 22% on a typical type. Uncertainty roughly ±25%.
Spot a mistake?