FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA18CA234 · Piper PA28 181

24 Apr 2018 · Wickenburg, AZ, United States

AeroGuard Flight Training Center Piper PA28 181 · Accident on approach

From Phoenix Deer Valley Airport (DVT) to Wickenburg Municipal Airport (E25)

Report a problem

Event

NTSB case
GAA18CA234
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

Piper PA28 181

Aircraft type
Piper PA28
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
N922PA
Onboard fatalities
Unknown
Route
From Phoenix Deer Valley Airport (DVT), Phoenix, AZTo Wickenburg Municipal Airport (E25), Wickenburg, AZ
Aircraft age
About 19 years (built 1999)
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
Approach · VFR pattern final
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
Miscellaneous/other
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 systems
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight instructor reported that, while abeam the intended touchdown point, he reduced power to idle for the student pilot to perform a simulated engine failure approach. The student pilot maneuvered for the runway and added full flaps (40°), decreasing airspeed to about 62 to 68 knots. The instructor asked the student if he believed he would be able to make the runway given his airspeed, and the student pilot retracted the flaps to 0° and then back to 25°. The airplane began to sink, the flight instructor added full flaps to "regain some lift," and he instructed the student pilot to recover. The student pilot put both hands on the yoke and pitched up. The flight instructor said "my controls," applied full power, and attempted to lower the nose, but the student pilot froze and continued to pitch up. The flight instructor repeated the exchange of flight controls command, the student pilot released control of the yoke and retracted the flaps to 0°. The flight instructor put the flaps back to 25° and pitched the nose down in an attempt to recover. The airplane struck the top of a tree, the flight instructor reduced power and landed short of the runway; the nose landing gear collapsed.

The airplane sustained substantial damage to both wings and empennage.

The flight instructor reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

The Federal Aviation Administration inspector reported that, after conducting interviews, it was revealed that the flight instructor took control of the airplane "well below 500 feet from the ground." He also added that there may have been a communication barrier between the flight instructor and the student pilot. He reported that the student pilot paused for 20 to 30 seconds to comprehend each question before answering.

Probable cause

The student pilot’s failure to relinquish flight controls and premature flap reduction during approach to land.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA18CA234
Event ID
20180424X24445
Case number
GAA18CA234
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2018-04-25.
  • API snapshot SHA-256: 4cee26200777600c24dece95ce8a560b88fa1c21c6ff947c32be7544ebadffc6; retrieved 2026-09-16T06:55:26.012Z.