# NTSB ERA20FA097: Aviastroitel AC 4C, N912ES, Front Royal, VA, February 9, 2020 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Final report - Date: February 9, 2020, 13:20 local (18:20 UTC) - Place: Front Royal, VA - Coordinates: 38.549999, -78.139999 - Nearby events: https://openairdocs.org/map.md?lat=38.5500&lon=-78.1400&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern downwind: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: Fatal - Injuries: 1 fatal - Status: Completed - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 100916 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA20FA097 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/100916/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=100916 - Page: https://openairdocs.org/ntsb/ERA20FA097 ## Probable cause The pilot's exceedance of the glider’s critical angle of attack while maneuvering for landing, which resulted in an aerodynamic stall and subsequent loss of control. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cooper James R AC-4C, 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=056075Y), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: airspeed](https://openairdocs.org/ntsb-findings/01062010): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cooper James R AC-4C, 1 case](https://openairdocs.org/ntsb-findings/01062010/cases.md?model=056075Y), [All aircraft, 1,681 cases](https://openairdocs.org/ntsb-findings/01062010/cases.md) - [Performance/control parameters: angle of attack](https://openairdocs.org/ntsb-findings/01062042): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cooper James R AC-4C, 1 case](https://openairdocs.org/ntsb-findings/01062042/cases.md?model=056075Y), [All aircraft, 990 cases](https://openairdocs.org/ntsb-findings/01062042/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern downwind: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Cooper James R AC-4C, 1 case](https://openairdocs.org/ntsb-events/240/sequence.md?model=056075Y), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Approach-VFR pattern downwind: Aerodynamic stall/spin](https://openairdocs.org/ntsb-events/241); cases with it: [Cooper James R AC-4C, 1 case](https://openairdocs.org/ntsb-events/241/sequence.md?model=056075Y), [All aircraft, 1,529 cases](https://openairdocs.org/ntsb-events/241/sequence.md) - [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cooper James R AC-4C, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=056075Y), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis Prior to the flight, the pilot told a fellow soaring club member that he was going to practice speed control in the traffic pattern. The panel-mounted radio in the glider was not working, so the pilot had to use a handheld radio to communicate. However, no witnesses recalled hearing any communications from the pilot after he disconnected from the tow plane. About 1 hour after the pilot departed, a club member saw his glider on downwind for runway 28. The glider appeared to have a nose-up attitude, was moving "slower than normal," and appeared to be at "minimum sink" speed. At this time, another club glider had just executed a practice premature termination of tow (PTT) maneuver from runway 28 and was landing in the opposite direction on runway 10. The club member thought that the accident pilot had slowed down to wait for that glider to clear the runway, and due to spacing, the accident pilot might have to fly over the top of them and land. The club member turned his attention away from the accident glider and did not see the accident. The flight instructor who had just completed the PTT maneuver said that they had just finished their landing rollout on runway 10 when he looked up and saw the glider in a fully involved spin toward the ground. The glider impacted wooded terrain about a 1/2 mile northwest of the airport. Postaccident examination of the glider revealed no mechanical anomalies that would have precluded normal operation prior to the accident. An index card with airspeeds written on it was found in the wreckage. According to the airspeeds listed, the glider's minimum sink speed was 39 knots, and the stall speed was 37 knots. The pilot's handheld radio was found stowed in a storage pouch that was attached to the right side of the cockpit wall. The radio exhibited some impact damage to the battery section and was inoperable. It was not determined why the pilot was not using his handheld radio to communicate. The club's duty officer who was monitoring the airport's traffic frequency the accident pilot was always meticulous with making radio calls, and it was unlike him not to do so on the day of the accident. Since the pilot stated that he was going to practice speed control in the pattern and was observed flying slower than normal and near minimum sink speed on the downwind leg of the traffic pattern, he may have been distracted by traffic on the runway. It is likely the pilot exceeded the glider's critical angle of attack and entered an aerodynamic stall at an altitude that was too low to recover. ## Factual narrative On February 9, 2020, about 1320 eastern standard time, an experimental amateur-built Aviastroitel AC-4C glider, N912ES, was substantially damaged when it was involved in an accident near the Front-Royal Warren County Airport (FRR), Front Royal, Virginia. The pilot was fatally injured. The glider was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot was a member of the Skyline Soaring Club, which was based at FRR. A club member helped the pilot assemble his glider and complete a comprehensive positive flight control check. The club member said the flight control check (which included the divebrakes) was normal. The pilot told him that he planned to practice "speed control" in the traffic pattern. The glider's panel mounted radio was not working, so the pilot had to use a handheld radio. However, another club member who was monitoring the airport's common traffic advisory frequency (CTAF) that afternoon as duty officer did not hear the pilot make any radio calls prior to the accident. According to club records, the pilot departed FRR about 1225. A third club member said that he and a passenger were flying in another glider when they caught up with the accident pilot while airborne. About 10-15 minutes prior to the accident, they flew a thermal together before the third club member and his passenger returned to FRR. The third club member said he encountered "a huge updraft" when he made a right turn from the downwind leg to base leg of the traffic pattern for runway 28. He said the updraft, which he estimated was about 10 knots, caught him off guard, but he was able to correct for it and land uneventfully. Once the third club member exited his glider, he saw the accident glider in the traffic pattern. It was midfield on the right downwind leg for runway 28. He said the glider appeared to have a nose-up attitude and was moving "slower than normal." The third club member thought that the pilot was flying at "minimum sink" speed, which he said was not unusual in the traffic pattern. At this time, another club glider had just executed a practice premature termination of tow (PTT) maneuver from runway 28 and was landing in the opposite direction on runway 10. The third club member thought that the accident pilot had slowed down to wait for that glider to clear the runway, and he made a comment to his passenger that the accident pilot might have to fly over the top of them and land. The third club member turned his attention away from the accident glider and when he looked back up, the glider was no longer in the traffic pattern. He said he never heard the accident pilot make any radio calls that day. The flight instructor who had just completed the PTT maneuver said that they had just finished their landing rollout on runway 10 when he looked up to his left and saw a "white glider" in a fully involved spin toward the ground. He did not see the impact and was unsure what direction it was spinning. The flight instructorsaid that he did not hear any radio communications from the pilot prior to the accident. The soaring club's tow pilot flew over the area where the spinning glider was last observed and located it in the woods about a 1/2 mile northwest of the airport. The tow pilot also said that he had towed the accident glider to altitude about an hour earlier. During the tow flight, he was communicating over the radio with the accident pilot. The club's duty officer at the time of the accident said he never would have launched the glider performing the PTT maneuver if he had known that another glider was in the traffic pattern. The duty officer said the accident pilot was always meticulous with making radio calls and it was unlike him not to do so on the day of the accident. On-scene examination revealed the glider came to rest upright on rolling terrain at the base of a cluster of trees. The cockpit area was displaced to the right. Several broken tree branches were on top of and around the main wreckage. All major components of the glider were accounted for at the accident site. Both wings remained attached to the fuselage, and the tail section had separated but remained attached via control cables. A portion of the left wing's wing tip was located about 20 ft southwest of the main wreckage. Several broken pieces of the Plexiglas canopy were found around the main wreckage. The right wing exhibited some impact damage, but the aileron was secure and undamaged. The divebrake was extended and was being held up by tree branches. When the branches were removed, the divebrake fully retracted into its wing box. The left wing exhibited more impact damage than the right wing. There was a large gash in the leading edge of the left wing and the top of the wing was fractured back to the aileron's inboard attach point. The aileron was separated from the inboard attach point but remained attached to the outboard attach point. The aileron was also fractured mid-span. The trailing edge of the left wing at the wing root was crushed and appeared to be slightly pulled away from the fuselage. The divebrake was fully retracted in its respective wing box. Flight control continuity was established for the ailerons, the rudder and the divebrakes from the cockpit to the flight control surfaces. The divebrake handle in the cockpit was found in the forward and unlocked position. The divebrake's aluminum control rod aft of the handle was bent about 30° consistent with impact damage. When the divebrake handle was pushed aft, both divebrakes simultaneously extended. The trim was set in the second notch position. The elevator did not move when the flight control stick was moved. Further examination revealed that that the elevator control tube rod end that attached to the elevator bell crank located directly below the control stick was impact damaged and fractured. When the fractured elevator control tube was manually moved, the glider's elevator moved freely. An index card was found in thewreckage that contained several flight speeds written on it. According to the card, the glider's minimum sink speed was calculated to be 39 knots and the stall speed was 37 knots. The pilot's handheld radio was found stowed in a storage pouch that was attached to the right side of the cockpit wall. The radio exhibited some impact damage to the battery section and was inoperable. ## Aircraft - Registration: [N912ES](https://openairdocs.org/deregistered/N912ES-2022-07-30), registration cancelled 2022-07-30, S/N 002K, built 2002 (OpenAirDocs) - Reported make and model: Aviastroitel AC 4C (No Series) - Registry model: [Cooper James R AC-4C](https://openairdocs.org/model/cooper-james-r-ac-4c) (registry code 056075Y) (OpenAirDocs) - Registry engine: [NONE](https://openairdocs.org/engine/none) (registry code 00000, none) (OpenAirDocs) - Category: Glider, amateur-built - Serial number: 002K - Year built: 2002 - Airframe hours: 120.4 - Engines: none - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Condition, February 13, 2019 - Departed: FRR, Front Royal, VA - Destination: FRR, Front Royal, VA - Airport: FRR, Front Royal-Warren County - Equipment: None ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 65; injuries: fatal; flight engineer, commercial, airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, with waivers/limitations; seat: center; restraint: 4-point; toxicology performed; flight hours: 18,800 total, 16.5 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 250° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 46 °F, dew point 27 °F - Altimeter: 30.40 inHg - Observed at: FRR, 1 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20200209000579A](https://openairdocs.org/incident/20200209000579A), Feb 9, 2020: Cooper James R AC-4C, Front Royal, VA, Substantial damage, 1 fatal. On 09FEB2020, [privacy data omitted] departed kfrr from runway 28, in his single pilot, russia AC-4C glider at approximately 1224HRS. At approximately 1324HRS… ## Docket (10 files) The files NTSB released with the investigation on January 26, 2022, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=100916. 28.5 MB in all. - NTSB record of conversation - witness (preflight) (item 1, PDF, 1 page, 100 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9954665&FileExtension=pdf&FileName=NTSB%20ROC%20Witness%20Preflight-Rel.pdf - NTSB roc - witness (traffic pattern) (item 2, PDF, 1 page, 98 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9954080&FileExtension=pdf&FileName=NTSB%20ROC%20Witness-Rel.pdf - NTSB record of conversation - flight instructor (item 3, PDF, 1 page, 94 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9954248&FileExtension=pdf&FileName=NTSB%20ROC%20Flight%20Instructor-Rel.pdf - NTSB record of conversation - tow pilot (item 4, PDF, 1 page, 100 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9954089&FileExtension=pdf&FileName=NTSB%20ROC%20Tow%20Pilot-Rel.pdf - NTSB record of conversation - duty officer (item 5, PDF, 1 page, 100 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9954741&FileExtension=pdf&FileName=NTSB%20ROC%20DO-Rel.pdf - Photos (item 6, PDF, 7 pages, 2.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9954548&FileExtension=pdf&FileName=Photo%20Array-Rel.pdf - Maintenance record (item 7, PDF, 1 page, 23.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9954674&FileExtension=pdf&FileName=Last%20Condition%20Inspection_Redacted-Rel.pdf - Toxicological report (item 8, PDF, 1 page, 739 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9953258&FileExtension=pdf&FileName=TOX%20REPORT%20FAA_Redacted-Rel.pdf - Memorandum - medical and pathological information (item 9, PDF, 1 page, 115 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=13141860&FileExtension=pdf&FileName=A_ERA20FA097%20Autopsy%20Memorandum-Rel.pdf - Release of aircraft wreckage and ecf (item 10, PDF, 2 pages, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=9959300&FileExtension=pdf&FileName=WRECKAGE%20RELEASE%202_Redacted-Rel.pdf From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.