FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA11LA390 · Aero Vodochody L39C

9 Jul 2011 · West Milford, NJ, United States

Air Vatche Aero Vodochody L39C · Accident: runway excursion during landing

From Orange County Airport (MGJ) to Greenwood Lake Airport (4N1)

Report a problem

Event

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

Aero Vodochody L39C

Aircraft type
Aero Vodochody L39
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
N111XN
Operator
Air Vatche
Onboard fatalities
Unknown
Route
From Orange County Airport (MGJ), Montgomery, NYTo Greenwood Lake Airport (4N1), West Milford, 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 · landing roll
Defining eventThe 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
Runway excursion
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

While landing on runway 24 at an airport that had obstructions on both ends of the runway, had only 3,471 feet of usable runway available, and which required a 3.50 degree glideslope for landing, the pilot of the ex-military jet trainer landed the airplane and overran the runway. According to the pilot's written statement, during the landing he touched down 5 to 6 feet prior to the painted "24" on the runway. He then lowered the nose of the airplane and "retracted" the wing flaps. He then pushed the control stick forward and applied the brakes by squeezing the control-stick-mounted brake handle, but braking did not occur. He then applied the brakes a second time, extended the speed brakes, wiggled the control stick, and pushed the control stick forward and applied the brakes a third time without result before applying them a fourth time. He then felt the anti-skid engage. The airplane then struck a chain link fence and went over an embankment before impacting the ground, nosing over, and coming to rest inverted. The pilot was seriously injured during the impact sequence and the airplane incurred substantial damage to the forward fuselage.

Review of the pilot's statement also revealed that he had not touched down at 96 knots indicated airspeed, as specified by the landing speeds chart, but had touched down at 106 knots, which would have extended his landing distance by about 20 percent. Further, witnesses observed the airplane actually touch down about 300 to 400 feet past the painted "24" on the runway, not the 5 to 6 feet prior to the painted "24" as stated by the pilot. Skid marks that matched the width of the airplane's main landing gear geometry were also present on the runway surface. The marks started about 1,270 feet past the painted "24" on the runway and continued until they left the pavement.

Review of performance planning charts also revealed that the safety margin for operating at the airport was insufficient: even if the airplane had touched down just prior to the painted "24" on the runway, the pilot would already have 205 feet of the usable runway behind him, and with moderate braking the landing roll would have been about 2,500 feet, and the landing distance, when landing over a 50 foot obstacle, would have been about 3,370 feet. With intensive braking, the landing roll would have been about 2,000 feet, and the landing distance, when landing over a 50 foot obstacle, would have been about 2,900 feet. The pilot also would not have met the accelerate/stop criteria for takeoff or a balked landing, as the airplane required 3,600 feet to accelerate to takeoff speed and then stop after an aborted takeoff.

Examination of the airplane did not reveal any evidence of a preimpact mechanical failure or malfunction that would have resulted in failure of the normal braking system. The flaps were also in the 44 degree (landing) position and had not been retracted, as was required for a minimum run landing to reduce lift, increase weight on the wheels, and reduce tire skidding. Examination of the flight manual also revealed that, in the event of a brake failure, activation of the main wheel brake units still would have been possible if the pilot had operated the emergency brake lever. According to the flight manual, he should have used the emergency brake lever if he believed that he had lost normal braking.

Probable cause

The pilot's excessive airspeed and failure to attain the proper landing point, which resulted in the airplane touching down too fast and too far down the short runway. Contributing to the accident was the pilot's failure to retract the flaps after landing, which resulted in delayed brake activation, the pilot’s decision to land on a runway with an insufficient safety margin for the landing conditions, and the pilot’s failure to use the emergency brake lever.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA11LA390
Event ID
20110709X53314
Case number
ERA11LA390
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: e06c4d996fa111d865def2d546754254522e57dfe41e542b4db36f631a892214; retrieved 2026-09-15T16:25:55.698Z.