FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA163 · Enstrom F280 F

26 Mar 2016 · Sodus, NY, United States

B.A.C. Services Enstrom F280 F · Accident: abnormal runway contact during landing

From Williamson Sodus Airport (SDC) to Williamson Sodus Airport (SDC)

Report a problem

Event

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

Enstrom F280 F

Aircraft type
Enstrom F280
Category
Helicopter
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
N5698Y
Onboard fatalities
Unknown
Route
From Williamson Sodus Airport (SDC), Sodus, NYTo Williamson Sodus Airport (SDC), Sodus, NY
Aircraft age
About 35 years (built 1981)
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 · flare/touchdown
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
Abnormal runway contact
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
  • Aircraft › Aircraft propeller/rotor
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight instructor reported that he asked the pilot receiving instruction to demonstrate a run-on landing on the sod between the runway and taxiway. He reported that as the helicopter touched down at about 25 miles per hour (21.72 knots), the pilot lowered the collective to the full down position while the helicopter was still moving forward with considerable momentum. The helicopter began to "lurch forward" and the nose of the helicopter started to lower. The flight instructor then came on the flight controls, but the helicopter had progressed to an "extreme nose low attitude," and he applied aft cyclic to prevent the main rotor blades from impacting terrain. The main rotor blades instead impacted and separated the tailboom. The fuselage continued moving forward and the nose impacted terrain and then settled back on the skids. The helicopter sustained substantial damage to the fuselage, main rotor system, tailboom, and tail rotor system.

The flight instructor verified that there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

The flight instructor reported that he recommended landing on sod due to potential wear on the bottom of the skids from friction with the paved runway. He also reported that the pilot had successfully performed run-on landings in the past on the sod area.

As a safety recommendation, the flight instructor reported that landing the helicopter on the runway instead of the sod may have lessened the effects of improper application of the collective at touchdown. He reported that he should have verbally reviewed the importance of using the collective to control the friction with the landing surface while in the traffic pattern to ensure the pilot's intentions were mutually understood. He further reported that he should have maintained a guarded position on the flight controls regardless of the pilot's abilities to decrease the flight instructor's reaction time for maneuver recovery.

Enstrom Helicopter Corporation has published the Enstrom 280F Training Maneuvers Manual (2014). This manual discusses objectives and descriptions for a shallow approach and run-on landing, and states in part:

Caution, Enstrom does not endorse practicing run-on landings. Run-on landings should only be accomplished on a smooth, hard surface; and should always be planned to the center of the runway to preclude sliding off the runway, and overturning.

After ground contact, maintain heading with pedals and maintain collective position. Ensure that power is maintained until the helicopter comes to a complete stop to insure directional control.

The Federal Aviation Administration has published the Helicopter Instructor's Handbook FAA-H-8083-4 (2012). This handbook provides instructional information for a shallow approach and run-on landing and states in part:

In any case, do not rapidly lower the collective after touchdown. Smooth reduction of collective prevents a rapid stop that could result in damage to the aircraft or injury to the crew.

For helicopters equipped with skids, it may be better to practice running landings on a hard surface runway instead of on a grassy field because there is less probability of catching a skid, which can lead to dynamic rollover. In addition, check the condition of the skid shoes before and after practicing running takeoffs and landings.

Probable cause

The pilot's improper collective application at touchdown during a practice run-on landing, which resulted in the main rotor system impacting the tailboom and the forward portion of the fuselage impacting terrain during remedial action by the flight instructor. Contributing to the accident was the flight instructor's delayed remedial action.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA163
Event ID
20160328X33033
Case number
GAA16CA163
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. 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: cbcdf85e1549b1c473cd0af89e23fe43c532a6751b26bf7b9e5f2d769bfe2b68; retrieved 2026-09-16T03:14:52.566Z.