3 Sep 2010: BELL 47G 5 — Frank Gomes

3 Sep 2010: BELL 47G 5 (N4427F) — Frank Gomes

No fatalities • Salinas, CA, United States

Probable cause

The pilot's visual flight rules flight into instrument meteorological conditions, which resulted in his spatial disorientation and loss of helicopter control.

— NTSB Determination

Accident narrative

On September 3, 2010, about 0600 Pacific daylight time, a Bell 47G-5 helicopter, N4427F, was substantially damaged following impact with terrain near Salinas, California. The commercial pilot, the sole occupant, was seriously injured. Gomes Farm Air Service of Salinas, was operating the helicopter under the provisions of Title 14 Code of Federal Regulations Part 91. Instrument meteorological conditions prevailed at the time of the accident, and a flight plan was not filed. The repositioning flight had departed the Salinas Municipal Airport (SNS) about 0550, with its destination being an off-airport work site about 3 miles west of SNS.

According to a Federal Aviation Administration (FAA) aviation safety inspector who conducted a telephone interview with the pilot shortly after the accident, the pilot stated that he was flying about 50 feet above the ground and was concerned about the power lines that were hidden by the fog. The pilot reported that he then climbed up to about 80 feet above ground level (agl), which put him in the fog, and when he turned on the landing light in an attempt to illuminate the ground references and identify the power lines, it caused a temporary blinding condition that caused him to become disoriented. The pilot stated that he then attempted a 180-degree turn toward the airport, which resulted in a loss of control and impact with the highway pavement. The pilot reported no mechanical problems with the helicopter.

In a written report submitted to the National Transportation Safety Board investigator-in-charge (IIC) several days after the accident, the pilot reported that abeam the airport’s control tower at an altitude of about 75 feet mean sea level (msl) and after turning west toward the interstate highway that borders the airport on the west, he could clearly see a [sugar plant] about 2 miles away. The pilot stated that after reaching the interstate highway he climbed to 100 feet msl and remained clear of clouds, with visibility “2 miles plus.” The pilot revealed that when the helicopter was over the interstate highway’s median strip between the north and southbound lanes, visibility began to deteriorate. The pilot reported that at this time he decided to turn around and return to the airport, as well as to descend in an attempt to re-establish visual contact [with ground references]. The pilot stated that during the descent and course reversal the tail section of the helicopter collided with a guard rail on the highway. The helicopter subsequently impacted the highway pavement and came to rest inverted partially in a southbound lane. The helicopter sustained substantial damage to its airframe.

A truck driver who was traveling southbound on the interstate highway reported seeing the helicopter approaching her position from the right side; it was moving from side to side. The witness stated that the helicopter subsequently impacted the terrain and rolled over, coming to rest partially inverted. The witness added that the forward visibility at the time of the accident was about 250 feet, and it was also very foggy.

At 0546, a special observation was reported by the SNS Automated Surface Observing System (ASOS), which revealed wind calm, visibility 2 ½ miles, mist, overcast clouds at 100 feet, temperature 13 degrees Celsius, dew point 12 degrees Celsius, and an altimeter setting of 29.96 inches of Mercury.

At 0553, the SNS ASOS reported wind calm, visibility 2 ½ miles, mist, overcast clouds at 100 feet, temperature 13 degrees Celsius, dew point 12 degrees Celsius, and an altimeter setting of 29.97 inches of Mercury.

Contributing factors

  • cause Pilot
  • cause Pilot
  • cause Pilot
  • Contributed to outcome

Conditions

Weather
IMC, vis 2sm

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.