FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC02LA119 · Mooney M20

20 Jun 2002 · Hagerstown, MD, United States

Mooney M20 · Accident: overrun during landing

From Jackson County Airport/Reynolds Field (JXN) to Hagerstown Regional Richard A Henson Field (HGR)

Report a problem

Event

NTSB case
NYC02LA119
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 M20

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
N3282F
Operator
Unknown
Onboard fatalities
Unknown
Route
From Jackson County Airport/Reynolds Field (JXN), Jackson, MITo Hagerstown Regional Richard A Henson Field (HGR), Hagerstown, MD
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
Landing · landing roll
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
Overrun
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 › Go-around, not performed
  • Pilot in command › Proper touchdown point, not attained

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 performing his second approach to runway 27, a 5,460-foot long, 150-foot wide, dry, asphalt runway. During the first approach, the airplane came in high and the pilot elected to perform a go-around. On the second approach, the pilot said he encountered a gust of wind, and landed with about 1,500 feet of runway remaining. The pilot added that when he initially applied the brakes, they responded to gentle pressure; however, "faded quickly." The airplane departed the end of the runway, struck an airport boundary fence and came to rest about 800 feet beyond the departure end of the runway. Witnesses reported they observed the airplane touch down about 4,000 feet beyond the approach end of the runway. The airplane bounced three times, and smoke was observed emanating from the airplane's tires before the airplane "launched" off the departure end of the runway. Examination of the airplane, which included the brake system, did not reveal any pre-impact malfunctions. Winds reported at the airport about the time of the accident, were from 170 degrees at 8 knots.

Probable cause

The pilot's failure to perform a go-around and obtain the proper touchdown point, which resulted in an overrun. A factor in the accident was the crosswind condition.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC02LA119
Event ID
20020627X00979
Case number
NYC02LA119
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, 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: 38f0b4186e8412f17f4b9b996866748b47e488e23742fa944d87bd5ce90a7090; retrieved 2026-09-21T09:38:10.255Z.