WPR12LA212

NTSB accident investigation · Schweizer 269C-1 · Hillsboro, OR · May 13, 2012

Accident · No injuriesLimited investigationFinal report
Date
May 13, 2012, 14:54 local (21:54 UTC)
Place
Hillsboro, OR
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N61482Schweizer 269C-1
Defining event
Initial climb: Loss of control in flight
Weather
Visual (VMC) · Day
Status
Completed · report August 13, 2013
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
Federal Aviation Adminsitration
FAA report
20120513008249A
Case key
83674

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 flight instructor's improper decision to take off from a hover with low rotor rpm.

Findings · 3

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.

Performance/control parameters: powerplant parametersAircraft › Aircraft oper/perf/capability · Not attained/maintainedAll aircraft: 81 casesProbable cause
Performance/control parameters: prop/rotor parametersAircraft › Aircraft oper/perf/capability · Not attained/maintainedAll aircraft: 182 casesProbable cause
Action: incorrect action selectionPersonnel issues › Action/decision · Instructor/check pilotAll aircraft: 397 casesProbable cause

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

While conducting a series of off-airport landings, the pilot receiving instruction circled the area and initiated a second approach to the predetermined landing area. During the approach and hover, the flight instructor observed the engine and rotor rpms at the bottom of the green arc and advised the pilot to bring the engine rpm back to the top of the green arc. The pilot informed the flight instructor that they were at full throttle, and the flight instructor took control of the helicopter. After hovering for about 30 seconds, the flight instructor performed a left turn and initiated takeoff. As the helicopter transitioned through effective translational lift, the flight instructor observed the engine and rotor rpms drop further, and the helicopter began to descend. The flight instructor maneuvered the helicopter toward a level road; however, the helicopter landed on sloping terrain and the tail rotor struck the ground. Postaccident examination of the helicopter revealed no mechanical malfunctions or failures that would have precluded normal operation. The engine was subsequently successfully started and run, with no anomalies noted. It is likely that if the instructor had landed the helicopter after taking control from the pilot receiving instruction, he would have been able to increase the engine and rotor rpms back to the top of the green arc and then make a successful takeoff.

Factual narrative

On May 13, 2012, about 1454, Pacific daylight time, a Schweizer 269C-1, N61482, sustained substantial damage during an off-airport landing near Hillsboro, Oregon. The helicopter was registered to and operated by Hillsboro Aviation Inc., Hillsboro, Oregon, under the provisions of Title 14 Code of Federal Regulations Part 91 as an instructional flight. The certified flight instructor (CFI) and private pilot receiving instruction were not injured. Visual meteorological conditions prevailed and a company flight plan was filed for the flight. The local flight originated from the Portland-Hillsboro Airport (HIO), Hillsboro, Oregon, about 1415.In a written statement to the National Transportation Safety Board (NTSB) investigator-in-charge (IIC), the CFI reported that after departure, he located an off-airport landing area at an elevation of about 1,000 feet mean sea level (msl) to practice off airport landings. After circling the area, the pilot receiving instruction initiated an approach to the landing area from the south. Following an uneventful landing and takeoff, the pilot receiving instruction circled the area and initiated a second approach from the west to a hover over the intended landing area. The CFI observed the engine revolutions per minute (RPM) at the bottom of the green arc, about 2,500, and asked the pilot receiving instruction to bring the RPMs back to the top of the arc. The pilot informed the CFI that they were at full throttle and the CFI took control of the helicopter. About 30 seconds later, the CFI turned the helicopter to the north and initiated takeoff. As the helicopter transitioned through effective translational lift (ETL), the CFI observed the RPMs drop to about 2,300 to 2,400 and the helicopter began to descend. The CFI maneuvered the helicopter towards a level road, however, was unable to make it. Subsequently, the helicopter landed on sloping terrain and the tail rotor struck the ground. In a written statement to the NTSB IIC, the pilot receiving instruction reported that the first off-airport landing was performed to the north and was uneventful. The pilot initiated a second approach to the same landing area to the east and maneuvered the helicopter to an approximate 1 to 3 foot hover, when the CFI told him to roll on throttle as the engine RPM was at the bottom of the green arc. The pilot further reported that the CFI took over the controls, verified the gauges, and initiated a takeoff to the left. The CFI accelerated the helicopter over the ground as it sloped downhill, however, the engine RPMs were "drooping." The pilot stated that he last observed the engine RPM needle indicate between 2,200 and 2,300 RPM and could hear the engine "drooping." He added that as the CFI attempted to land the helicopter on a road, he heard the sound of the engine and rotor RPM dropping as the helicopter landed in a clear area just below the road. Both the CFI and pilot receiving instruction did not recall if they heard a low rotor RPMwarning or saw an illuminated warning light during the accident sequence. Review of the Pilot's Operating Handbook for the accident make/model helicopter revealed that the green arc of the engine RPM is from 2,530 to 2,700 RPM. Examination of the helicopter by a Federal Aviation Administration (FAA) inspector revealed that the helicopter sustained structural damage to the tailboom and the vertical stabilizer was separated. The FAA inspector stated that following recovery of the helicopter and a brief inspection of the engine, the engine was started and ran uneventfully with no anomalies noted.

Aircraft

Registration
N61482
Reported as
Schweizer 269C-1
Category
Helicopter
Serial number
0081
Airframe hours
4,105
Engine
Lycoming HO-360, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Instructional · Part 91
Operator
Hillsboro Aviation Inc
Registered owner
Hillsboro Aviation Inc
Airworthiness certificate
Standard, Normal; Unknown
Last inspection
Annual · May 9, 2012 · 13 hours before
Departed
Hillsboro, OR
Destination
Hillsboro, OR
Flight plan
Unknown

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Flight instructor
Age
30
Injuries
None
Certificates
Flight instructor, Commercial
Instrument ratings
Helicopter
Medical
Class 2
Last flight review
October 18, 2010
Seat
Left
Flight hours
475 total · 48 in this make and model · 381 as pilot in command · 55 in the last 90 days · 37 in the last 30 days · 6 in the last 24 hours
Role
Pilot
Age
31
Injuries
None
Certificate
Private
Medical
Class 2, With waivers/limitations
Last flight review
February 19, 2012
Seat
Right
Flight hours
121 total · 3 in this make and model · 60 as pilot in command · 52 in the last 90 days · 25 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
60° at 6 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
82 °F, dew point 43 °F
Altimeter
30.04 inHg

Docket · 7

The files NTSB released with the investigation on June 14, 2013, on NTSB’s docket system: statements, records, photos and specialists’ reports. 6.0 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.