FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC94LA063 · Cessna 172RG

17 Mar 1994 · Fairfield, NJ, United States

Mac Dan Aviation Cessna 172RG · Accident: overrun during landing

From Monmouth Executive Airport (BLM) to an unrecorded destination

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

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

Cessna 172RG

Aircraft type
Cessna 172
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
N9585B
Onboard fatalities
Unknown
Route
From Monmouth Executive Airport (BLM), Farmingdale, NJTo not recorded
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 › Airspeed, improper
  • Pilot in command › Planned approach, improper
  • Pilot in command › Proper touchdown point, not attained

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

NTSB narrative

WITH WINDS FROM 320 TO 330 DEGREES, AT 8 TO 10 KNOTS, THE PILOT WAS CLEARED FOR A LEFT CROSSWIND ENTRY TO RWY 4. INSTEAD HE LINED UP WITH RWY 9. THE LOCAL CONTROLLER SAW THIS AND THEN CLEARED HIM TO LAND ON RWY 9 WHICH WAS 3721 FEET LONG. THE AIRPLANE RAN OFF THE DEPARTURE END OF THE RWY, CROSSED 325 FEET OF OPEN FIELD, WENT THROUGH A FENCE, UP AN EMBANKMENT AND CAME TO REST ON A 4 LANE ROAD. THERE WERE 500 FEET OF SKID MARKS ON THE RWY, AND THE AIRPLANE TRAVELED 375 FEET BEYOND THE DEPARTURE END OF THE RWY. THE PILOT SAID HE LANDED LONG, WITHOUT FLAPS, CARRIED EXTRA POWER, AND FLOATED. HE SAID HIS TOUCHDOWN SPEED WAS 85 KNOTS. RUNWAY 9 WAS 830 FEET SHORTER THAN RUNWAY 4.

Probable cause

THE FAILURE OF THE PILOT TO ATTAIN A PROPER TOUCHDOWN, AT THE PROPER SPEED WHICH RESULTED IN AN OVERRUN AND CONTACT WITH A FENCE. A FACTOR WAS THE FAILURE OF THE PILOT TO FOLLOW HIS INITIAL AIR TRAFFIC INSTRUCTIONS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC94LA063
Event ID
20001206X00987
Case number
NYC94LA063
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1994-03-18.
  • API snapshot SHA-256: 2c12a6c13412beeed3de3ed93eb557be58a5aab2989e4703d4ad315abac85036; retrieved 2026-09-21T22:41:11.500Z.