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

Bell 407 accident near Charlottesville, Virginia, August 12, 2017

On August 12, 2017 at about 8:49 pm local time, a 2000 Bell 407 (helicopter), registered N31VA, was destroyed in an accident during maneuvering near Charlottesville, Virginia. It was a public-use flight (state) under public-use (government) rules. 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's loss of helicopter control after entry into vortex ring state, leading to a high rate of descent to the ground with a right spin. Contributing to the accident was the pilot's lack of recent and recurrent training in vortex ring state recognition and recovery.

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

What the record shows

Date
August 12, 2017 · about 8:49 pm local time
Place
Charlottesville, Virginia · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Bell 407, built 2000 · all 407s on the register
Registration
N31VA · no longer on the register · serial 53465
Damage
Destroyed
Flight
Public-use flight (state) · public-use (government) rules

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

The helicopter pilot and observer were conducting an aerial observation flight. The helicopter had been providing the Virginia State Police (VSP) with a continuous video downlink of the public demonstrations that were occurring in Charlottesville, Virginia, when the flight crew was tasked to provide overwatch for a motorcade. Radar data indicated that the helicopter was flying at an altitude of about 2,200 ft mean sea level (msl) in the area of the motorcade before it began to turn to the right and descend rapidly. Radar data also indicated that, about 30 seconds later, the helicopter was descending through 1,450 ft msl at a groundspeed of 30 knots. Shortly afterward, the helicopter descended below the area of radar coverage, and radar contact was lost. A witness aboard another helicopter observed the accident helicopter descending in an upright position into trees at a high rate of descent. The helicopter impacted the ground and a postcrash fire ensued.    Video from a security camera, which was located about 1.2 miles from the accident site captured the helicopter toward the end of the flight and showed that the helicopter was descending vertically at a constant acceleration and with increasing negative vertical speed until ground impact. Photographs of the accident helicopter that were taken by a ground witness revealed that, about the time that the helicopter began its vertical descent, the helicopter was yawing to the right at a rate between 87° and 97° per second. The damage to the main wreckage was consistent with impact forces and the postcrash fire. Hard-body foreign object damage observed on the first-stage compressor blades was consistent with the ingestion of metallic helicopter debris after the helicopter impacted trees and the ground. Thus, the engine was operating at the time of impact. The aft section of the tailboom was found about 100 to 150 feet from the main wreckage site, and pieces of the tail rotor control tube from the midsection of the tailboom were near the main wreckage and the aft section of the tailboom. Signatures of main rotor contact were observed at multiple locations along the aft section of the tailboom. Given the proximity of the aft section of the tailboom to the main wreckage site, the main rotor would likely have contacted the tailboom shortly before ground impact and not during the onset of the right yaw. Although the pedal restrictor control system (PRCS) cam was found in the engaged position, examination of the PRCS found no anomalies consistent with a system malfunction. Therefore, the PRCS cam could have activated during the vertical descent and have limited left pedal forward travel, particularly if the helicopter's nose was lowered during the descent and the resulting airspeed was more than 55 knots (the airspeed at which left pedal travel would be restricted). Regardless, even if the PRCS were engaged, sufficient pedal travel would have been present to maintain heading in a hover out of ground effect. The pilot's autopsy found moderate coronary artery disease without evidence of a previous scar or heart damage. Although the pilot could have been incapacitated by a number of medical conditions, such as a seizure, sudden loss of consciousness, or arrhythmia, that would have left no evidence at autopsy, he did not have a higher risk for such events even with his moderate coronary artery disease. Thus, the pilot's medical condition was not a factor in this accident. Toward the end of the flight, the helicopter's low forward airspeed while descending was consistent with the helicopter entering vortex ring state. As a result, even though power was applied, the helicopter was unable to reduce the descent rate, and it continued descending with an estimated vertical acceleration between 10.5 and 13.5 ft/s2. Anecdotal information indicated that the pilot had knowledge of vortex ring state, but review of the pilot's training records indicated that he had not received any formal recurrent vortex ring state recognition and recovery training during his 16 years with the VSP aviation unit. Also, the VSP aviation unit training manual did not include vortex ring state recognition and recovery in any of the sample lesson plans for initial or recurrent training, and the associated maneuvers were considered to be optional. The helicopter was not equipped with, and was not required to be equipped with, crash-resistant flight recorders. The recovered engine control unit data revealed a sharp increase in torque, from 54% to 104% immediately before the helicopter's descent. Insufficient left pedal input with increasing torque can result in a right yaw that can develop into a spin. The lack of flight recorder data for this accident precluded an evaluation of the pilot's actions before the overtorque and the right yaw. Additionally, the lack of flight recorder data precluded a determination of the pilot's actions during the helicopter's entry into vortex ring state, including any attempt to recover. Last, the available data were insufficient to determine if the right yaw began immediately before or after the helicopter's encounter with the vortex ring state. This accident demonstrates the benefit of crash-resistant flight recorders aboard turbine-powered, nonexperimental, nonrestricted-category aircraft that are not currently required to be so equipped.

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. Loss of control in flight during maneuvering defining event
  2. Part(s) separation from AC during uncontrolled descent
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
  4. Fire/smoke (post-impact) during post (impact)

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Personnel issues › Experience/knowledge › Training › Recurrent instruct/training › Pilot

Pilot

  • Certificate: airline transport pilot, flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: helicopter; instructor: instrument airplane; instructor: instrument helicopter; instrument: airplane; instrument: helicopter; rotorcraft: helicopter
  • Flight time: 5,831 hours in all; 787 in this make and model; 19 in the last 90 days; 6 in the last 30 days; 5,727 as pilot in command; 2,306 on instruments
  • Last flight review: November 15, 2016
  • Medical certificate: Class 2 (with waivers/limitations)
  • Seat: rgt
  • Injury: fatal

Other crew

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 97 hours in all
  • Last flight review: December 21, 2016
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 6,000 hours
  • Last inspection: 100-hour inspection, August 3, 2017; 17 hours since
  • Maximum gross weight: 5,501 lb
  • Seats: 7
  • Landing gear: fixed
  • Engine: Rolls-Royce Corporation 250-C47B (turboshaft); 5,610 hours total
  • Fire on the ground
  • Operator: Virginia State Police

The flight

  • Departed from: CHO Charlottesville VA at 8:00 pm
  • Destination: CHO Charlottesville VA
  • Flight plan: none
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 190° at 6 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 86°F (30°C), dew point 72°F (22°C)
  • Altimeter: 29.87 inHg
  • Observation at 8:53 pm from CHO, 7 miles away

Injuries

FatalSeriousMinorNone
Flight crew2

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

19 documents, released by the NTSB on May 13, 2020. 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.

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

Other NTSB records under N31VA the same tail number, which may have belonged to a different aircraft at the time

2010-05-11ERA10TA261 · accident near Abingdon, VA · substantial damage · no injuries

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.