The U.S. aircraft register, updated daily
Accidents · NTSB WPR17LA159 · Final report

Robinson Helicopter Company R44 II accident near Van Nuys, California, July 21, 2017

On July 21, 2017 at about 7:11 pm local time, a 2007 Robinson Helicopter Company R44 II, registered N3254E, was substantially damaged in an accident during enroute (cruise) near Van Nuys, California (Van Nuys airport). It was an other work-use flight under general aviation rules (Part 91). 3 people were seriously injured and 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

An improper repair of the right magneto's tachometer and governor signal wire, which failed during cruise flight and initiated a simultaneous malfunction of both the engine tachometer and governor control system, which resulted in erroneous and contradictory information between the engine tachometer and main rotor tachometer that led the pilot to perform a forced landing. Contributing to the accident was the lack of guidance on how to address the simultaneous failure or malfunction of both the engine tachometer and governor control system.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 21, 2017 · about 7:11 pm local time
Place
Van Nuys, California · Van Nuys · map
Type
Accident
Injuries
3 people were seriously injured and 1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Robinson Helicopter Company R44 II II, built 2007
Registration
N3254E · no longer on the register · serial 11702
Damage
Substantial damage
Flight
Other work-use flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

**This report was modified on July 26, 2022. Please see the public docket for this accident to view the original report.** The commercial pilot reported that, during a local sightseeing flight over a densely populated area, he heard an unusual sound and saw that the engine tachometer was indicating a higher-than-normal engine rpm. He reduced engine power and attempted to manipulate the helicopter controls to align the engine and rotor speeds to no avail. Subsequently, the rotor rpm began decaying, and the pilot assumed the helicopter had experienced a catastrophic drive failure and chose to conduct an autorotation, during which the helicopter landed hard. The airframe sustained substantial damage. Postaccident examination of the helicopter and engine did not reveal evidence of any mechanical malfunctions or failures that would have precluded normal operation, and witness signatures indicated that the engine was producing power at the time of ground impact. However, a wire within the right magneto, which provided a signal to both the engine governor and engine tachometer on the instrument panel, was found detached at a solder joint where it had been soldered to the connector rather than crimped. Further, neither the wire nor its connector was aviation-grade. The investigation could not determine when the modification to the wire was made. Review of onboard video and a spectrographic analysis of the recorded audio revealed that the engine rpm initially decreased but then appeared to be restored a few seconds later while the helicopter slowed. For about the next 40 seconds, the engine continued to operate at the same rpm and the helicopter continued to slow and gradually descend. The engine rpm then quickly decreased, and the helicopter rapidly descended in a manner consistent with the pilot initiating an autorotation. The detached wire would have resulted in both the tachometer and governor not receiving a correct engine rpm signal. As a result, the engine governor would not have been able to make appropriate adjustments to engine power as demand changed, and the pilot would not have had a way to gauge engine power and make corrective manual throttle inputs. The pilot's statement that the tachometer rpm increased does not match a scenario where the wire completely detached. However, it is possible that the event was initiated when the wire remained partially connected and thus created a spurious increase in signal frequency to the tachometer and governor due to vibrations. Thus, in this scenario, the tachometer would read higher than normal and the engine rpm would decrease as the governor tried to compensate for the high engine rpm signal. The Helicopter's Operating Handbook provided separate procedures for the failure of the engine governor and tachometer but not for the failure of both. Because the engine governor control system and engine tachometer both share a common speed signal source and thereby a common failure point, this signal wire failure left the pilot with a confusing set of cues and no definitive procedures for corrective action. In addition, the helicopter's low rotor rpm warning horn was not working, but the low rotor lamp was working. This failure would have resulted in another set of contradictory cues for the pilot to process, further compounding the confusion he was likely experiencing during the high-stress event.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Sys/Comp malf/fail (non-power) during enroute (cruise) defining event
  2. Autorotation Off-field or emergency landing
  3. Autorotation Hard landing
  4. Autorotation Collision with terrain or object (not controlled flight into terrain)

The NTSB's findings

  • cause Aircraft › Aircraft systems › Indicating/recording systems › Instrument wiring › Incorrect service/maintenance
  • factor Organizational issues › Development › Design › Policy/procedure development › Manufacturer
  • factor Aircraft › Aircraft systems › Indicating/recording systems › Instrument wiring › Incorrect service/maintenance
  • Personnel issues › Action/decision › Info processing/decision › Understanding/comprehension › Pilot
  • Environmental issues › Physical environment › Object/animal/substance › Fence/fence post › Contributed to outcome

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: instructor: helicopter; instructor: instrument helicopter; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 1,700 hours in all; 1,112 in this make and model; 116 in the last 90 days; 75 in the last 30 days; 1,640 as pilot in command
  • Last flight review: February 8, 2017
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: rgt
  • Injury: serious injuries

The aircraft

  • Airframe total time: 2,661 hours
  • Last inspection: 100-hour inspection, July 13, 2017; 19 hours since
  • Maximum gross weight: 2,500 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming IO-540-AE1A5 (piston); 2,661 hours total

The flight

  • Departed from: VNY Van Nuys CA at 6:12 pm
  • Destination: VNY Van Nuys CA
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 140° at 7 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 84°F (29°C), dew point 59°F (15°C)
  • Altimeter: 29.95 inHg
  • Observation at 6:51 pm from KVNY, 3 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers3

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.