LAX01LA283

NTSB accident investigation · Aerospatiale AS 355F1 · Vinton, CA · August 18, 2001

Accident · No injuriesLimited investigationFinal report
Date
August 18, 2001, 14:25 local (21:25 UTC)
Place
Vinton, CA
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Maneuvering
Aircraft
N53LHAerospatiale AS 355F1
Weather
Visual (VMC) · Day
Status
Completed · report May 28, 2002
Report
Approved by Office Director
Parties
FAA Flt Stnds Dist Office
FAA report
20010818022649A
Case key
53058

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 pilot's selection of an unsuitable landing site, which caused "brown-out" conditions during departure liftoff and resulted in loss of control of the helicopter.

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 control - in flightHover - in ground effect
Terrain condition - loose gravel/sandy
Visual/aural perceptionPilot in commandCause
Unsuitable terrain or takeoff/landing/taxi area - selectedPilot in commandCause
Weather condition - sand/dust storm
Roll overEmergency landing

Analysis

The pilot of the med-vac helicopter reported that, during liftoff at the remote site, he encountered a loss of visual reference due to a "brown out" condition created by blowing dust at 3 feet agl. He then attempted to land the helicopter without any visual reference; however, the right skid contacted the ground first. A rolling motion to the left was created and, after the left skid contacted the ground, a dynamic rollover ensued. The helicopter came to rest on its left side.

Factual narrative

On August 18, 2001, at 1425 hours Pacific daylight time, an Aerospatiale AS 355F1 helicopter, N53LH, rolled onto its side and came to rest during takeoff at a remote location, 4 miles east of Vinton, California. The commercial certificated pilot, two flight nurses, and one patient were not injured. The helicopter was substantially damaged. The on-demand, air taxi, medical transport flight was operated under 14 CFR Part 135, by Rocky Mountain Holdings, LLC. Visual meteorological conditions prevailed and a company VFR flight plan was filed. The flight was destined for Reno, Nevada.

According to the operator, the pilot reported that, during liftoff, he encountered a loss of visual reference due to a "brown out" condition at 3 feet above ground level. He attempted to land the helicopter without any visual reference; however, the right skid contacted the ground first. A rolling motion to the left was created and, after the left skid contacted the ground, a dynamic rollover ensued. The helicopter came to rest on its left side.

Aircraft

Registration
N53LH
Reported as
Aerospatiale AS 355F1
Category
Helicopter
Serial number
5093
Airframe hours
7,374
Engine
Allison 250-C20F, 420 horsepower, turbo shaft
Damage
Substantial damage
Fire
On-Ground
Flight
Part 135
Registered owner
Rocky Mountain Holdings, LLC
Airworthiness certificate
Standard, Normal
Last inspection
AAIP · July 10, 2001 · 3 hours before
Departed
Vinton, CA
Destination
Reno, NV
Flight plan
Company VFR

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
39
Injuries
None
Certificates
Private, Commercial
Airplane ratings
Single-engine land
Instrument ratings
Helicopter
Medical
Class 2, Valid Medical--no waivers/lim.
Seat
Right
Flight hours
3,750 total · 275 in this make and model

Weather

Conditions
Visual (VMC) · Day
Wind
350° at 8 knots
Visibility
10 statute miles
Lowest ceiling
18,000 ft broken
Temperature
91 °F, dew point 45 °F
Altimeter
30.09 inHg
Observed at
RNO, 22 nm away

Docket · 1

The files NTSB released with the investigation on January 30, 2002, on NTSB’s docket system: statements, records, photos and specialists’ reports. 453 KB 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.