FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18FA251 · Mooney M20J

4 Sept 2018 · Palo Alto, CA, United States

Mooney M20J · Accident: aerodynamic stall/spin during initial climb

From Redding Municipal Airport (RDD) to Palo Alto Airport (PAO)

Report a problem

Event

NTSB case
WPR18FA251
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
1 · 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

Mooney M20J

Aircraft type
Mooney M20
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
N701JM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Redding Municipal Airport (RDD), Redding, CATo Palo Alto Airport (PAO), Palo Alto, CA
Aircraft age
About 26 years (built 1992)
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
Initial climb
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
Aerodynamic stall/spin
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

  • Personnel issues › Action/decision

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 was flying two passengers on an Angel Flight. When the airplane was about 10 miles north of the destination, the pilot contacted the air traffic control tower (ATCT). He was given instructions to fly to a charted VFR checkpoint, but then reported that he was not familiar with it and asked for directions from the controller. The pilot navigated to that checkpoint after several communications, and was then instructed to overfly a second checkpoint, about 2.5 miles north of the runway, as his left base leg for the arrival. The pilot was unable to locate the airport and requested ATCT assistance to advise him when to turn final, which the controller did. The pilot saw the airport and continued the approach.

Witnesses observed the airplane touch down about mid-field and began to porpoise, alternately bouncing between the main and nose landing gear. After 3 to 4 oscillations, the pilot initiated a go-around and reported to the controller of the go-around. In response, the controller instructed the pilot to make a left closed traffic and asked if he needed assistance, to which the pilot replied “negative, I just came in too fast." The airplane climbed a few hundred feet and was then observed to enter a very steep left bank. The nose pitched sharply down, and the airplane descended rapidly to the ground. Examinations of the airplane and engine did not reveal any evidence of any pre-impact mechanical deficiencies or failures. Physical examination of the engine and propeller, combined with review of recorded engine operating parameter data, indicated that the engine operated normally, and was producing power at impact.

The pilot’s logbook indicated that he had flown into that airport at least 32 times before, and therefore he should have been familiar with both the physical location of the airport and the names and locations of the local navigation fixes. Even if he had never been into that airport before, proper preflight planning dictates that he should have become familiar with those aspects.

Data downloaded from the onboard GPS device revealed the airplane was about 10 to 15 knots above the manufacturer's approach speed (75 knots for the calculated landing weight) during final approach. The data also indicated that for most of the final approach, the airplane remained below the runway's 4° PAPI approach slope path

The pitch trim was found slightly airplane nose down from the normal takeoff setting, but the flaps were found fully retracted. The manufacturer's go-around procedures called for full power, liftoff, and retraction of the flaps from the landing position (full down) to the takeoff position (approximately half) once the climb was established. Then, in sequence, this was to be followed by re-trimming in pitch, acceleration to 76 knots, landing gear retraction, flap retraction to the full-up position, and acceleration to 86 knots. Witnesses reported that the landing gear was retracted very soon after liftoff, making it likely that the pilot did not comply with the manufacturer's retraction sequence.

The flaps-retracted 0° bank stall speed for the calculated airplane weight was about 58 knots, and the stall speed for 30° bank was about 63 knots. Takeoff flaps reduce these speeds by about 2 knots. Both the short amount of time between liftoff and the stall, and the stall itself, indicate that the pilot had fully retracted the flaps prior to achieving the prescribed speed of 86 knots. Based on the available information, speed mismanagement by the pilot, and a reduced stall margin due to the pilot prematurely retracting the flaps, caused the airplane to stall during the early portion of its go-around climb out at an altitude too low for recovery.

Probable cause

The pilot’s failure to maintain aircraft control during a go-around due to his premature flap retraction, which resulted in an aerodynamic stall and subsequent loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18FA251
Event ID
20180904X52324
Case number
WPR18FA251
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: 000f6ac1961b3e20182fc608104b259affa567f8280a8991aeb7837fe4269510; retrieved 2026-09-15T06:47:35.421Z.