# Accident 20140603008199A: Emery Mark ROTORWAY 162F, Merced, CA, June 3, 2014

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 3, 2014, 19:09 local time
- Place: Merced, CA
- Airport: Merced Municipal/Macready Field
- Damage: Destroyed
- Phase of flight: Descent
- Operating rules: General operating rules (Part 91)
- Location: 37.3100° N, 120.5167° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=37.3100&lon=-120.5167&mi=10
- Aircraft: N78291, a cancelled registration (https://openairdocs.org/deregistered/N78291-2018-03-06) (OpenAirDocs)
- Registry model: Emery Mark ROTORWAY 162F (registry code 05602DC, https://openairdocs.org/model/emery-mark-rotorway-162f) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: EMERY MARK ROTORWAY 162F
- Reported engine: AMA/EXPR RI 162FA
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- NTSB investigation: [NTSB WPR14LA225](https://openairdocs.org/ntsb/WPR14LA225) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20140603008199A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

THE PILOT OF THIS EXPERIMENTAL ROTORWAY HELICOPTER REPORTED THAT IT HAD JUST BEGAN AN ASSENT FROM A PRACTICE RAPID DECENT WHEN IT LOST TAIL ROTOR CONTROL. HE REPORTED THAT THE AIRCRAFT EXPERIENCED 1 1/2 HORIZONTAL ROTATIONS BEFORE LANDING IN A CORN FIELD. THE RIGHT SKID PARTIALLY BUCKLED AND THE CRAFT ROLLED TO THE RIGHT 90 DEGREES. IT CAUGHT FIRE AND THE ENTIRE BUBBLE/FUSELAGE WAS CONSUMED. THE PILOT AND ONE PASSENGER ESCAPED WITHOUT INJURY.

EXAMINATION OF THE TAIL BOOM AND BELT DRIVE SYSTEM INDICATED THAT THE MIDDLE OR INTERMEDIATE TAIL ROTOR DRIVE BELT HAD BROKEN. THE PRIMARY BELT WAS CONSUMED IN THE FIRE. THE FINAL DRIVE BELT WAS INTACT AND IN PLACE. THE BROKEN SECONDARY DRIVE BELT WAS RECOVERED AND SENT TO THE NTSB FOR ANALYSIS.

OF NOTE, THE SECONDARY DRIVE BELT HAD BROKEN APPROXIMATELY ONE MONTH AGO. THE REPLACEMENT BELT HAD APPROXIMATELY 4 HOURS TOTAL TIME.

THE PILOT HAD PERFORMED NUMEROUS ENGINE RUNS, & HOVER, AND ADJUSTING THE BELT TENSIONS AFTER EACH. HE STATED THAT HE HAD FLOWN AROUND THE PATTERN AT MCE WITHOUT PROBLEM, THEN CHECKED THE BELTS, WITHOUT ANY ADJUSTMENT NECESSARY.

VISUAL EXAMINATION OF THE BROKEN BELT FOUND TWO OTHER PLACES WHERE THE BELT APPEARED TO BE WEAKENED, UNKNOWN IF FROM MANUFACTURER OR STRESS FROM USE.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB WPR14LA225](https://openairdocs.org/ntsb/WPR14LA225), Jun 4, 2014: Emery Mark Rotorway 162F (N78291), Merced, CA, destroyed. Probable cause: The helicopter pilot/owner's decision to install a belt type not recommended by the kit manufacturer in the tail rotor drive system using the incorrect tension values, which led to the belt’s…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.