ASN Wikibase Occurrence # 197472
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Saturday 12 August 2017 |
| Time: | 16:49 |
| Type: |  Bell 407 |
| Owner/operator: | Virginia State Police |
| Registration: | N31VA |
| MSN: | 53465 |
| Year of manufacture: | 2000 |
| Total airframe hrs: | 6000 hours |
| Engine model: | Rolls-Royce Corporation 250-C47B |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | near Charlottesville, VA -
 United States of America
|
| Phase: | Manoeuvring (airshow, firefighting, ag.ops.) |
| Nature: | Aerial patrol |
| Departure airport: | Charlottesville-Albemarle Airport, VA (CHO/KCHO) |
| Charlottesville-Albemarle Airport, VA (CHO/KCHO) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
On August 12, 2017, about 1649 eastern daylight time, a Bell 407 helicopter, N31VA, was destroyed when it was involved in an accident in Charlottesville, Virginia. The pilot and the observer were fatally injured. The helicopter was operated as a public aerial observation flight.
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 turbinepowered, nonexperimental, nonrestricted-category aircraft that are not currently required to be so equipped.
Probable Cause: 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.
Accident investigation:
 |
|
Sources:
http://www.dailymail.co.uk/news/article-4785418/Police-helicopter-crashes-near-Charlottesville.html#ixzz4paCU6n67
http://www.nydailynews.com/news/national/killed-chopper-crash-va-charlottesville-clashes-article-1.3406606
http://www.richmond.com/news/virginia/state-police-helicopter-crashes-near-birdwood-golf-course-witnesses-say/article_429c00cc-dd49-5dfd-94ab-8d43e7eeb71a.html
http://www.nydailynews.com/news/national/killed-chopper-crash-va-charlottesville-clashes-article-1.3406606
http://www.vsp.state.va.us/BFO_Aviation.shtm
NTSB
FAA
http://www.nbc29.com/story/36132237/ntsb-releases-latest-details-on-state-police-helicopter-crash
https://www.ntsb.gov/news/press-releases/Pages/PR20170905.aspx
http://aerossurance.com/helicopters/vrs-virginia-state-police-b407/
History of this aircraft
Other occurrences involving this aircraft
| 11 May 2010 | N31VA | Virginia State Police | 0 | Abingdon, VA | |
sub |
Location
Images:
Photo: NTSB
Media:
After a change in tasking from surveillance to escorting the Governor's motorcade, this police helicopter climbed and slowed, falling victim to Vortex Ring State (VRS) say the #NTSB. https://t.co/ZtQk3mUfM7 #police #helicopter #accident #flightsafety #aviationsafety pic.twitter.com/JTiUbkCUTm
— Aerossurance (@Aerossurance) July 18, 2020
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 12-Aug-2017 22:35 | Iceman 29 | Added |
| 12-Aug-2017 22:38 | Iceman 29 | Updated [Aircraft type, Operator, Nature, Embed code] |
| 12-Aug-2017 22:42 | Iceman 29 | Updated [Operator, Total occupants, Embed code] |
| 13-Aug-2017 08:20 | Iceman 29 | Updated [Embed code] |
| 13-Aug-2017 08:36 | Iceman 29 | Updated [Source, Embed code] |
| 13-Aug-2017 09:26 | Aerossurance | Updated [Time, Operator, Location, Phase, Source, Embed code, Narrative] |
| 13-Aug-2017 13:50 | Aerossurance | Updated [Registration, Cn, Source, Narrative] |
| 14-Aug-2017 19:45 | harro | Updated [Source, Narrative] |
| 14-Aug-2017 20:08 | Aerossurance | Updated [Time, Departure airport, Destination airport, Source, Narrative] |
| 14-Aug-2017 20:11 | Aerossurance | Updated [Narrative] |
| 06-Sep-2017 15:05 | Aerossurance | Updated [Source, Narrative] |
| 18-Jul-2020 11:05 | Aerossurance | Updated [Source, Narrative] |
| 18-Jul-2020 11:13 | Aerossurance | Updated [Embed code] |
| 31-May-2023 04:10 | Ron Averes | Updated [[Embed code]] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation