The U.S. aircraft register, updated daily
Accidents · NTSB LAX07LA173 · Final report

Westland Helicopters Wasp HAS MK1 accident near Ramona, California, May 25, 2007

On May 25, 2007 at about 2:50 am local time, a Westland Helicopters Wasp HAS MK1, registered N612VH, was substantially damaged in an accident near Ramona, California. It was a flight test under general aviation rules (Part 91). 3 people had minor injuries; 1 other was unhurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

Failure of the pilot to maintain clearance from a tree while performing a precautionary landing. Contributing to the accident was the failure of a snubber dampener that induced a severe vibration in the rotor system.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
May 25, 2007 · about 2:50 am local time · cases in 2007
Place
Ramona, California · map
Type
Accident
Injuries
3 people had minor injuries; 1 other was unhurt.
Weather
visual conditions (good weather)
Aircraft
Westland Helicopters Wasp HAS MK1
Registration
N612VH · registry record · serial F8-7411
Damage
Substantial damage
Flight
Flight test · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot reported that during the flight a severe vibration began throughout the helicopter. The pilot was attempting to make a precautionary landing when the tail rotor stuck a tree. Maintenance personnel for the operator indicated that the vibration was due to a failure of one of the snubber dampeners on a main rotor blade.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

Pilot

  • Certificate: private
  • Ratings: rotorcraft: helicopter
  • Flight time: 1,021 hours in all; 11 in this make and model; 9 in the last 90 days; 7 in the last 30 days; 916 as pilot in command
  • Last flight review: June 1, 2006
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 2,911 hours
  • Last inspection: continuous airworthiness programme, September 1, 2006; 10 hours since
  • Maximum gross weight: 5,500 lb
  • Seats: 5
  • Landing gear: fixed
  • Engine: Rolls-Royce Nimbus 103 (turboshaft); 0 hours total

The flight

  • Departed from: L39 Ramona CA at 1:30 am
  • Flight plan: none

Weather at the time

  • Wind: from 250° at 6 knots
  • Visibility: 8 statute miles
  • Sky: overcast at 1,200 ft
  • Temperature: 61°F (16°C), dew point 52°F (11°C)
  • Altimeter: 29.94 inHg
  • Observation at 1:53 am from CRQ, 17 miles away

Injuries

FatalSeriousMinorNone
Crew1
Passengers3

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Connections how this case links to the rest of the register

Aircraft
  • N612VH on the register today · the tail number may have moved to another aircraft since
  • Engine: Rolls-Royce Nimbus 103 · as the NTSB recorded it
Place

The whole map of how records connect · these connections as data: /graph/accident/LAX07LA173.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.