13 May 2012: SCHWEIZER 269C-1 — HILLSBORO AVIATION INC

13 May 2012: SCHWEIZER 269C-1 (N61482) — HILLSBORO AVIATION INC

No fatalities • Hillsboro, OR, United States

Probable cause

The flight instructor's improper decision to take off from a hover with low rotor rpm.

— NTSB Determination

Accident 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 RPM warning 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.

Contributing factors

  • cause Powerplant parameters — Not attained/maintained
  • cause Prop/rotor parameters — Not attained/maintained
  • cause Instructor/check pilot

Conditions

Weather
VMC, wind 060/06kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.