CHI01LA152

NTSB accident investigation · Allen Rotorway 162F · Jerseyville, IL · June 3, 2001

Accident · No injuriesLimited investigationFinal report
Date
June 3, 2001, 10:15 local (15:15 UTC)
Place
Jerseyville, IL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N242KAAllen Rotorway 162F
Weather
Visual (VMC) · Day
Status
Completed · report May 28, 2002
Report
Approved by Office Director
Parties
Federal Aviation Administration
FAA report
20010603013659A
Case key
53255

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 improper autorotation by the pilot. Contributing factors were the engine failure for undetermined reason(s) and the muddy terrain.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Loss of engine powerCruise
Reason for occurrence undeterminedFactor
In flight collision with terrain/waterEmergency descent/landing
Autorotation - improperPilot in commandCause
Terrain condition - muddyFactor

Analysis

The experimental amateur-built helicopter impacted muddy terrain and rolled over when its skids became stuck in the mud during an emergency autorotation following a total loss of engine power. The pilot reported that after the number one electronic control unit (ECU) had failed followed by the number two ECU failing while returning to the departure point at an airspeed of 40 mph and at an altitude of 100 feet agl. An operation at 40 mph and at 100 feet agl was within the shaded region of the height velocity envelope for the helicopter. A postaccident engine run was performed while operating on the primary and secondary fully automated digital electronic control systems. Inspection of the number one electronic control unit revealed two resistors damaged within its circuit board. The number one ECU was found to be inoperative during testing and the number two ECU did not communicate with the number one ECU.

Factual narrative

On June 3, 2001, at 1015 central daylight time, an experimental amateur-built Allen Rotorway 162F, N242KA, sustained substantial damage on impact with terrain following a loss of engine power after takeoff from a farm field near Jerseyville, Illinois. Visual meteorological conditions prevailed at the time of the accident. The 14 CFR Part 91 personal flight was not operating on a flight plan. The private pilot reported no injuries. The local flight was originating at the time of the accident.

In a written statement, the pilot reported "After preflight and startup I allowed the engine to warm up to green arc (mandatory to prevent over pressurization of cooling system). After warmup, all systems in the green I lifted to a hover did a 360 [degree] clearing turn and departed to the south. Approx. 200' AGL 65 mph I noticed the split tach had failed. Almost [immediately] I got a red light indicating No. 1 ECU had failed. I made a 180 [degree] turn back to the pad. At about 100' 40 mph No. 2 ECU failed cutting the engine. Autorotated, [flared] a little late striking tail rotor. Still having forward motion the skids stuck in the mud and the aircraft rolled on to its right side. Shut off all switches and fuel and departed the A/C."

According to the Rotorway 162F pilot operating handbook, a red instrument light annunciation of the electronic control unit (ECU) 1 indicates that the primary ECU is off. Also, flight at 100 feet agl and 40 mph operation is within the shaded area of the height velocity envelope. Referring to the Rotorcraft Flying Handbook (FAA-H-8083-21), the height/velocity (H/V) diagram depicts the critical combination of airspeed and altitude should an engine failure occur. Operating within the shaded area of the H/V diagram may not allow enough time for the critical transition from powered flight to autorotation.

Postaccident examination of the engine by the Federal Aviation Administration (FAA) revealed that the helicopter was fueled with 91-octane automotive fuel. Both electric fuel pumps were operated and fuel was available at the injector ports. The oil screen was checked and reported to be normal. The engine was run at idle and accelerated to 2,600 rpm. After a short period of time, the primary fully automated digital electronic control (FADEC) system was turned off and the secondary FADEC system took control of the engine and it ran normally, but slightly rougher. Both FADEC computer systems were then removed and shipped to Rotorway International, Chandler, Arizona, for inspection and testing.

Inspection and testing of the ECU's, under the supervision of the FAA, revealed that the number one ECU was inoperative and the number two ECU was operational, but it would not communicate with number one ECU. Inspection of the number one ECU's circuit board revealed that the "L1" and "L3" resistors were damaged.

Aircraft

Registration
N242KA
Reported as
Allen Rotorway 162F
Category
Helicopter, amateur-built
Serial number
6307
Airframe hours
135.4
Engine
Rotorway 162F, 150 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Steven Allen
Airworthiness certificate
Special, Experimental (Special)
Last inspection
Annual · April 29, 2001 · 1.3 hours before
Departed
PVT · Jerseyville, IL

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

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
46
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 2
Last flight review
March 23, 2000
Seat
Left
Flight hours
472 total · 153 in this make and model · 392 as pilot in command · 5 in the last 90 days · 2 in the last 30 days · 0 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
Variable at 3 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
61 °F, dew point 54 °F
Altimeter
29.88 inHg
Observed at
SET, 20 nm away

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.