FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA18CA193 · Piper PA28 181

1 Apr 2018 · Phoenix, AZ, United States

AeroGuard Flight Training Center Piper PA28 181 · Accident: loss of control in flight on approach

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

Report a problem

Event

NTSB case
GAA18CA193
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
N297PA
Onboard fatalities
Unknown
Route
From Wickenburg Municipal Airport (E25), Wickenburg, AZTo Phoenix Deer Valley Airport (DVT), Phoenix, AZ
Aircraft age
About 16 years (built 2002)
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 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
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 flight instructor reported that he was conducting a lesson in takeoffs and landings and go-around procedures with the student pilot at the controls. During one particular go-around, the student retracted the flaps too far and the instructor stressed the importance of using the proper flap settings. On the subsequent downwind, the tower advised a crosswind from the south gusting to 18 knots. During the approach, the airplane drifted left of the runway centerline, so he called for the student to execute a go-around. The student pilot applied full power and reduced flaps from 40° to 10° (25º is prescribed in the go-around procedure). When the flight instructor noticed that the airplane was not climbing and the student was not correcting the course, the flight instructor took the flight controls. The flight instructor attempted to recover, but the airplane was in a nose-high attitude and struck the ground. The airplane then lifted off the ground and flew slowly toward a sign; the instructor "pulled up to avoid the sign," but the airplane struck the sign, aerodynamically stalled, and impacted the ground to the right of the runway.

The airplane sustained substantial damage to the left wing.

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

The automated weather observation station located on the accident airport reported that, at the time of the accident, the wind was from 110° at 8 knots. The airplane was landing on runway 7L.

The Federal Aviation Administration's Airplane Flying Handbook, FAA-H-8083-3B, contains a section titled "Go-Arounds (Rejected Landings)" which states:

After establishing the proper climb attitude and power settings, be concerned first with flaps and secondly with the landing gear (if retractable). When the decision is made to perform a go-around, takeoff power is applied immediately and the pitch attitude changed so as to slow or stop the descent. After the descent has been stopped, the landing flaps are partially retracted or placed in the takeoff position as recommended by the manufacturer. Caution must be used in retracting the flaps. Depending on the airplane's altitude and airspeed, it is wise to retract the flaps intermittently in small increments to allow time for the airplane to accelerate progressively as they are being raised. A sudden and complete retraction of the flaps could cause a loss of lift resulting in the airplane settling into the ground.

Probable cause

The student pilot’s improper selection of the flap setting during a go-around, and the flight instructor’s delayed remedial action, which resulted in an aerodynamic stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA18CA193
Event ID
20180401X75919
Case number
GAA18CA193
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: 5e3165c221e7d48e032becce9853e3963b98017040f2a5494dce009067f80c5b; retrieved 2026-09-16T06:46:23.682Z.