FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD05LA053 · Mooney M20J

6 Apr 2005 · Rocky Hill, NJ, United States

Mooney M20J · Accident: loss of control in flight on approach

From Cape May County Airport (WWD) to Princeton Airport (39N)

Report a problem

Event

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

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
N4398H
Operator
Unknown
Onboard fatalities
Unknown
Route
From Cape May County Airport (WWD), Wildwood, NJTo Princeton Airport (39N), Rocky Hill, NJ
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
First occurrenceThe 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
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
Stall
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

  • Pilot in command › Airspeed, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On the short final leg of the approach to the destination airport, the pilot observed an airplane at the opposite end of the runway and initiated a go-around. He turned the airplane right, applied full power, and retracted the landing gear, flaps and speed brakes. As he was attempting to adjust the elevator trim in a nose down direction, and was holding forward pressure on the control yoke, the airplane "stalled," and the airplane impacted the ground. When asked how the accident could have been prevented, the pilot stated, "I should have done a go-around straight down the runway, not a 45-degree turn off airport."

Probable cause

The pilot's failure to maintain airspeed during a go-around, which resulted in an inadvertent stall, and subsequent impact with terrain. Factors included the night lighting conditions, and the airplane approaching the opposite runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD05LA053
Event ID
20050503X00537
Case number
IAD05LA053
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-04-07.
  • API snapshot SHA-256: 0e05a0e40c6e6669bec79eb892fc3db83c06e539f0cae7227331ba7a99cf1006; retrieved 2026-09-21T19:03:07.357Z.