FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Aviation Cessna 172N N accident

7 Jun 2014 · Page, AZ, United States

Cessna 172N N · Accident: loss of control in flight on approach

From Page Municipal Airport (PGA) to Page Municipal Airport (PGA)

Report a problem

Event

NTSB case
WPR14LA235
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
Charter & commuter
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 172N N

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
N5589E
Onboard fatalities
Unknown
Route
From Page Municipal Airport (PGA), Page, AZTo Page Municipal Airport (PGA), Page, AZ
Aircraft age
About 36 years (built 1978)
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 135: Air Taxi & Commuter
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
Approach · VFR go-around
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
Loss of control in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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
  • Environmental issues › Conditions/weather/phenomena
  • 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 pilot reported that, while landing the airplane in gusting wind conditions, he approached the runway at 60 knots and that, when he flared the airplane, it started to drift to the side of the runway. When the main landing gear touched down, a gust of wind lifted the airplane off the runway. The airplane touched down again and then bounced too high to continue the landing. The pilot subsequently initiated a go-around; the airplane was at full power with an airspeed of less than 43 knots. He did not raise the flaps because he was afraid the airplane would descend. The airplane started a slow descent, and the stall warning horn sounded. The airplane subsequently struck a small tree and then the ground, which resulted in substantial damage to the fuselage and wings. The wind at the airport was from 190 degrees at 13 knots gusting to 23 knots at the time of the accident. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot’s improper landing flare in gusting wind conditions, his inadequate recovery from the subsequent bounced landing, and his decision to perform a go-around with insufficient airspeed to climb.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR14LA235
Event ID
20140608X10855
Case number
WPR14LA235
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2014-06-08.
  • API snapshot SHA-256: 1bab9369560545de784f6d05e642a1df881e7b7121ffea60c91bf7541c3f0066; retrieved 2026-09-15T23:45:56.616Z.