WPR15CA004 · Cessna 172S
Northern Arizona Investment Group Cessna 172S · Accident: loss of control on ground during landing
From Prescott Regional Airport - Ernest A. Love Field (PRC) to Sedona Airport (SEZ)
Event
- NTSB case
- WPR15CA004
- 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 172S
- 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
- N2179L
- Onboard fatalities
- Unknown
- Route
- From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo Sedona Airport (SEZ), Sedona, AZ
- Aircraft age
- About 10 years (built 2004)
- 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
- Landing · landing roll
- 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 on ground
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was on an extended final for landing. As he got closer to the runway, he noted that he was right of centerline, and made corrections to return to the runway centerline for landing. The pilot indicated that he was still making corrections as he initiated the flare to land. The flare was too high, and as a result, the airplane developed a greater than desired sink rate, which he corrected by adding power. The pilot stated that the landing was firmer than normal, and the airplane bounced before it settled back to the runway. The pilot looked inside the cockpit to retract the flaps and reduce the power to idle. When he looked back outside, the airplane was pointed off the runway. The pilot added right rudder to correct back to the runway. He did not want to add too much rudder and lose airplane control, and when he went to apply the brakes, he noted that his feet were too far down the rudder pedals, so there was no braking action. The airplane departed the runway surface, and traveled onto the grass, toward a ditch. As the airplane traversed through the ditch, the nose landing gear collapsed, the propeller struck the ground, and then the airplane came to rest inverted. The airplane sustained substantial damage to right wing, rudder, and vertical stabilizer.
The pilot reported that there were no mechanical malfunctions with the airplane that would have precluded normal operation. In the Recommendation (how could this accident/incident have been prevented) section of the accident report, the pilot reported that the flight school has changed their policy, and no longer allows solo students to fly to the accident airport. He further reported that if he had ensured positive aircraft control prior to retracting the flaps, or taking his attention away from the landing, the airplane would not have yawed to the side of the runway.
Probable cause
The pilot's failure to maintain airplane control during the landing roll out.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR15CA004
- Event ID
- 20141007X12423
- Case number
- WPR15CA004
- 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. 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: ae72c7911220bc1b2d0d8c5adb29d2ce63dc892d199da6471c595d2a22056716; retrieved 2026-09-16T01:50:04.457Z.