FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC02LA039 · Piper PA-28

17 Dec 2001 · Cross Keys, NJ, United States

Piper PA-28 · Accident: in flight collision with object during landing

From Monmouth Executive Airport (BLM) to Cross Keys Airport (17N)

Report a problem

Event

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

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
N7658F
Operator
Unknown
Onboard fatalities
Unknown
Route
From Monmouth Executive Airport (BLM), Belmar, NJTo Cross Keys Airport (17N), Cross Keys, 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
Landing · aborted
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
In flight collision with object
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 › Aborted landing, delayed

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

NTSB narrative

The airplane departed on a VFR flight. The departure, en route, and descent portions of the flight were uneventful. The airplane turned final "high" and approximately 1/2 mile from the displaced threshold. On final, the pilot selected 40 degrees of flaps. The airplane crossed the displaced threshold approximately 100 feet agl, and 15 to 20 knots fast. The airplane touched down with approximately 1,750 feet of runway remaining. When the nosewheel touched down, the pilot realized he would not be able to stop before reaching the end. With approximately 500 feet of runway remaining, he decided to abort the landing. The airplane lifted off at the end of the runway. The right main landing gear struck a wooden fence at the end of the runway, and then an automobile traveling on a road. The airplane spun approximately 180 degrees to the right, impacted the ground, came to a stop, and the pilot exited. After the accident, the pilot did not report any preimpact failures or malfunctions with the airplane.

Probable cause

The pilot's delayed decision to abort the landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC02LA039
Event ID
20020213X00215
Case number
NYC02LA039
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: 5e65511dfb20d2a1175a82ce6b60ee9bfb97cbac4adb62d962a4cb66e2e0f7c6; retrieved 2026-09-22T11:15:15.227Z.