FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10CA233 · Piper PA-28-235

8 May 2010 · Lake Havasu City, AZ, United States

Piper PA-28-235 · Accident: loss of control in flight on approach

From Lake Havasu City Airport (HII) to Lake Havasu City Airport (HII)

Report a problem

Event

NTSB case
WPR10CA233
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 PA-28-235

Aircraft type
Piper PA-28
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
N918JR
Onboard fatalities
Unknown
Route
From Lake Havasu City Airport (HII), Lake Havasu, AZTo Lake Havasu City Airport (HII), Lake Havasu, AZ
Aircraft age
Not recorded
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 › 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 was on a local training flight. After flying about 1 hour in the practice area, she returned to the airport to perform touch-and-go takeoffs and landings. The reported winds at the time of the accident were 200 at 4 knots. During the approach to runway 32, she felt that a crosswind blew the airplane to the left. Landing in this position would have resulted in excessive stress to the left main landing gear. The student pilot initiated a go-around, applying full power and turning off carburetor heat. She indicated that at this point, an updraft pushed the airplane nose up and the airplane stalled. The student pilot attempted to recover from the stall; however, the "controls were sloppy and the airplane was not responding." The airplane came to rest inverted.

Probable cause

The student pilot's failure to maintain aircraft control during a go-around, resulting in a stall/mush.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10CA233
Event ID
20100508X64527
Case number
WPR10CA233
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: 62c61740247ccc6b088617e34687fcb5b8ea0942f3e6d7abdf47b95e7e33dd2b; retrieved 2026-09-15T14:02:03.013Z.