- Date
- March 26, 2016, 10:30 local (14:30 UTC)
- Place
- Sodus, NY
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N5698YEnstrom F280
- Defining event
- Landing-flare/touchdown: Abnormal runway contact
- Weather
- Visual (VMC) · Day
- Status
- Completed · report May 3, 2016
- Report
- Approved by Office Director
- NTSB office
- General Aviation Accidents
- Parties
- FAA Rochester FSDO
- FAA report
- 20160326024449A
- Case key
- 92905
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
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.
Findings · 4
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
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 stopthat 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.
Factual 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 stopthat 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.
Aircraft
- Registration
- N5698Y
- Reported as
- Enstrom F280 (F)
- Category
- Helicopter
- Serial number
- 1212
- Built
- 1981
- Airframe hours
- 2,070
- Engine
- Lycoming HIO-360-F1AD, 225 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Instructional · Part 91
- Operator
- B.A.C. Services
- Registered owner
- B.A.C. Services
- Airworthiness certificate
- Standard, Normal
- Last inspection
- 100 hour · October 27, 2015
- Departed
- SDC · Sodus, NY
- Destination
- SDC · Sodus, NY
- Airport
- SDC · Williamson-Sodus, runway 10, 3,801 × 60 ft, grass/turf
- Equipment
- None
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew · 2
As NTSB recorded them. NTSB leaves out names.
- Role
- Flight instructor
- Age
- 52
- Injuries
- None
- Certificates
- Commercial, Flight instructor
- Airplane ratings
- Single-engine land
- Instrument ratings
- Helicopter
- Medical
- Class 2, With waivers/limitations
- Last flight review
- April 15, 2015
- Seat
- Right
- Restraint
- 3-point
- Flight hours
- 3,847 total · 151 in this make and model · 3,657 as pilot in command · 44 in the last 90 days · 20 in the last 30 days · 18 in the last 24 hours
- Role
- Student pilot
- Age
- 56
- Injuries
- None
- Certificates
- Flight instructor, Commercial
- Airplane ratings
- Single-engine sea, Single-engine land
- Instrument ratings
- Airplane
- Medical
- Class 2, With waivers/limitations
- Last flight review
- December 19, 2015
- Seat
- Left
- Restraint
- 3-point
- Flight hours
- 1,698 total · 9 in this make and model · 1,593 as pilot in command · 7 in the last 90 days · 5 in the last 30 days · 1 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 110° at 5 knots
- Visibility
- 10 statute miles
- Temperature
- 34 °F, dew point 25 °F
- Altimeter
- 30.34 inHg
- Observed at
- KROC, 25 nm away
Docket · 2
The files NTSB released with the investigation on April 21, 2016, on NTSB’s docket system: statements, records, photos and specialists’ reports. 3.9 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.