FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA403 · Cessna 172 E

28 Jul 2016 · Rexburg, ID, United States

Cessna 172 E · Accident: collision during takeoff/landing

From Rexburg Madison County Airport (RXE) to Rexburg Madison County Airport (RXE)

Report a problem

Event

NTSB case
GAA16CA403
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 172 E

Aircraft type
Cessna 172
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N3677S
Operator
Unknown
Onboard fatalities
Unknown
Route
From Rexburg Madison County Airport (RXE), Rexburg, IDTo Rexburg Madison County Airport (RXE), Rexburg, ID
Aircraft age
About 52 years (built 1964)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Takeoff
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Collision during takeoff/landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The student pilot reported that while practicing short-field landings on runway 17, a 4,200 foot asphalt runway, he overshot his intended landing area. He reported that about 65 knots indicated air speed and 25 feet above ground level (AGL), he executed a go-around by applying mixture rich, full throttle, carburetor heat cold, but the electric flaps were left fully extended. He reported that he pulled back on the yoke, but he could not get the airplane to climb, and the airplane descended to the right side of the runway, and touched down in the safety area to the right of the runway and nosed over. The airplane sustained substantial damage to both wings, vertical stabilizer and the rudder.

The pilot reported that there were no mechanical malfunctions or anomalies with any portion of the airplane during the flight that would have prevented normal flight operations.

Photographs of the accident airplane provided by the Federal Aviation Administration (FAA) showed the airplane inverted with the flaps extended.

The airplane manufacturer pilot operating handbook prescribed Balked Landing procedure states:

1. Throttle – Full Open

2. Carburetor Heat – Cold

3. Wing Flaps - 20 Degrees (Immediately)

4. Climb Speed – 55 Knots

5. Wing Flaps 10 Degrees (Until obstacles are cleared) Retract (after reaching a safe altitude and 60 KIAS)

The meteorological aerodrome report at accident airport about the time of the accident indicated: The temperature was 90 degrees Fahrenheit, dew point was 37 degrees Fahrenheit, the wind was out of 170 degrees true at 7 knots and varying between 140 degrees and 200 degrees true. The altimeter setting was 30.10. The field elevation at the airport was 4,858 feet and the density altitude was 7,850 feet.

According to the FAA Pamphlet 8740-2 pertaining to Density Altitude:

Whether due to high altitude, high temperature, or both, reduced air density (reported in terms of density altitude) adversely affects aerodynamic performance and decreases the engine's horsepower output. Takeoff distance, power available (in normally aspirated engines), and climb rate are all adversely affected. Landing distance is affected as well; although the indicated airspeed (IAS) remains the same, the true airspeed (TAS) increases. From the pilot's point of view, therefore, an increase in density altitude results in the following:

• Increased takeoff distance.

• Reduced rate of climb.

• Increased TAS (but same IAS) on approach and landing.

According to the aforementioned FAA Pamphlet, the Koch Chart (chart in docket) depicting the relationship between airport temperature (90 degrees) and airport pressure altitude (4,693 feet), the climb rate decreases by 64 percent. The pilot initiated the balked landing procedure at 25 feet AGL.

Probable cause

The student pilot's failure to retract the flaps during a go-around in high density altitude conditions, resulting in the airplane's inability to climb and a subsequent collision with terrain and nose over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA403
Event ID
20160801X33224
Case number
GAA16CA403
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: b6e2bf96e5171db58f385d23464c72ae17d9a5c8ae2bd6087a5e3368b1966d0d; retrieved 2026-09-16T03:43:29.002Z.