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

Brantly B-2B accident near Weaverville, California, May 27, 2011

On May 27, 2011 at about 9:15 pm local time, a Brantly B-2B (helicopter), registered N222DW, was substantially damaged in an accident during enroute (cruise) near Weaverville, California (Weaverville airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The student pilot's decision to fly in windy conditions that exceeded his capabilities, which resulted in his subsequent loss of helicopter control. Contributing to the accident was his lack of flight experience in the accident helicopter.

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

What the record shows

Date
May 27, 2011 · about 9:15 pm local time · cases in 2011
Place
Weaverville, California · Weaverville · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Brantly B-2B · all B-2Bs on the register
Registration
N222DW · registry record · serial 181
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The student pilot’s solo flight endorsement prohibited flight in gusty wind conditions such as those existing at the time of departure along his route of flight and at his planned destination. Additionally, his route of flight would have been over mountainous terrain, which would have further exacerbated the conditions and resulted in updrafts, downdrafts, and turbulence at his flight altitude. A witness, who was located close to the accident site, reported unusually strong wind for the area at the time of the accident. The pilot did not request a weather briefing prior to the flight. The wreckage distribution was consistent with a level impact with trees in the direction of flight. No indications of an in-flight breakup, bird strike, or fire were present, and damage to the main rotor system was consistent with it operating at a high level of rotational energy. The throttle was noted in the closed position, consistent with an autorotation event; however, it is possible the pilot may have closed the throttle just prior to, or during, the impact sequence. The student pilot had received about 120 hours of helicopter flight training over the 3 1/2-year period prior to the accident. (The pilot's flight logbook had been defaced, thus an accurate assessment of his total flight experience was not possible.) During that time, he had used the services of about nine flight instructors, with only the last instructor endorsing him for solo flight about 2 weeks before the accident. The accident flight was most likely his second solo flight in the accident helicopter. Acquaintances and previous instructors recounted that the pilot often exhibited poor decision-making traits, was headstrong, stubborn, and overconfident. Although the pilot performed maintenance and unapproved modifications to the helicopter, the modifications did not appear to have been causal to the accident, and a postaccident examination did not reveal any anomalies with the airframe or engine that would have precluded normal operation.

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

What happened, in order

  1. Other weather encounter during enroute (cruise)
  2. Inflight upset during enroute (cruise) defining event
  3. Collision with terrain or object (not controlled flight into terrain) during enroute (cruise)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student pilot
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Student pilot
  • factor Personnel issues › Experience/knowledge › Experience/qualifications › Total experience › Student pilot
  • Environmental issues › Conditions/weather/phenomena › Turbulence › Terrain induced turbulence › Ability to respond/compensate

Dual student

  • Flight time: 110 hours in all; 7 in this make and model; 15 as pilot in command
  • Last flight review: May 14, 2011
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: rgt
  • Injury: fatal

The aircraft

  • Airframe total time: 699 hours
  • Last inspection: annual inspection, December 14, 2010; 12 hours since
  • Maximum gross weight: 1,670 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming IVO-360-A1A (piston); 0 hours total

The flight

  • Departed from: F62 Hayfork CA at 8:30 pm
  • Destination: O54 Weaverville CA
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 250° at 7 knots, gusting 22
  • Visibility: 10 statute miles
  • Sky: broken clouds at 6,500 ft; a few clouds at 5,500 ft
  • Temperature: 57°F (14°C), dew point 36°F (2°C)
  • Observation at 9:15 pm from O54, 3 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

23 documents, released by the NTSB on March 14, 2012. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Witness Statements PDF, 7 pages View Download
2 Photo 1 – Helicopter During Takeoff of Accident Flight – Provided by Jim Walters PDF, 1 page View Download
3 Photo 2 – Helicopter at Accident Site PDF, 1 page View Download
4 Photo 3 - Helicopter at Accident Site PDF, 1 page View Download
5 Photo 4 – Main Rotor Blade Remnants PDF, 1 page View Download
6 Photo 5 – Modified Collective Friction Lock PDF, 1 page View Download
7 Photo 6 - Combination Oil Pressure, Fuel Quantity, and Engine Temperature Gauge PDF, 1 page View Download
8 Photo 7 – Rotor Head PDF, 1 page View Download
9 Photo 8 – Engine PDF, 1 page View Download
10 Photo 9 – Top Spark Plugs PDF, 1 page View Download
11 Photo 10 – Fuel Servo Venturi Contamination PDF, 1 page View Download
12 Photo 11 – Left Side of Fuselage PDF, 1 page View Download
13 Photo 12 – Gascolator PDF, 1 page View Download
14 Photo 13 – Low Fuel Warning Bulb PDF, 1 page View Download
15 Photo 14 – Grease Contamination of Venturi Slots PDF, 1 page View Download
16 Image 1 - Accident Location Relative to Departure and Arrival Airports PDF, 1 page View Download
17 Pilot Logbook Excerpts PDF, 14 pages View Download
18 Airframe and Engine Examination Report PDF, 8 pages View Download
19 Fuel Servo Examination Report PDF, 3 pages View Download
20 Airframe and Engine Logbook Excerpts PDF, 4 pages View Download
21 Toxicological Report PDF, 1 page View Download
22 Surface Winds PDF, 1 page View Download
23 Evidence Control Form PDF, 6 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR11FA239.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.