FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC98LA021 · Mooney M20K

26 Oct 1997 · Ocean City, NJ, United States

Mooney M20K · Accident: undershoot on approach

From Igor I Sikorsky Memorial Airport (BDR) to Ocean City Municipal Airport (26N)

Report a problem

Event

NTSB case
NYC98LA021
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
0
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 M20K

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
N252MY
Operator
Unknown
Onboard fatalities
Unknown
Route
From Igor I Sikorsky Memorial Airport (BDR), Bridgeport, CTTo Ocean City Municipal Airport (26N)
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 · IFR final approach
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
Undershoot
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

  • Pilot in command › Altitude, not maintained

Approximate · Estimated position: the centre of Ocean City, NJ, the place the record names. Not the accident site.

NTSB narrative

During final approach, about 200 feet above ground level, the pilot experienced a loss of altitude. He added full power, but the aircraft struck a tree about 250 feet from the approach end of the runway. The pilot reported wind shear in the area. There was no evidence of pre-impact malfunction to the airplane. Winds reported at an airport 12 miles northeast were from 080 degrees at 7 knots. The airport manager reported that there was heavy rain and fog at the time of the accident.

Probable cause

The pilot's failure to maintain sufficient altitude. Factors in the accident were the rain and fog.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC98LA021
Event ID
20001208X09111
Case number
NYC98LA021
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: investigation status. 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: 94376d8279fe1d2dc7322f66b7f08de84b5b12c94b1859799e084894bb7995cb; retrieved 2026-09-21T21:06:04.098Z.