N637HP

HISTORY OF FLIGHTOn October 10, 2021, at 1357 eastern daylight time, a Robinson R44 II, N637HP, was destroyed when it was involved in an accident in Cornwall, New York. The pilot was fatally injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

According to fueling records, the pilot purchased 24.6 gallons of fuel before his departure from Floyd Bennet Memorial Airport (GFL), Glenn Falls, New York. The flight departed about 1247 with a destination of MacArthur Airport (ISP), Ronkonkoma, New York, where the helicopter was based.

According to ADS-B tracking data and National Weather Service (NWS) records, as the helicopter flew south along the Hudson River at an altitude of 1,800 to 1,900 ft above mean sea level (msl), the overcast cloud ceiling height was decreasing. As it passed by Poughkeepsie, NY (POU) at 1349, the ceiling reported there was about 2,364 ft msl. At 1353, about 7 miles further south, the helicopter passed by the Stewart International Airport (SWF) where the ceiling was reported to be about 1,991 ft msl. At 1356, the helicopter began to climb (see figure 1).

Figure 1 – Helicopter’s ADS-B-derived flight track (red/green dots) and cloud heights at nearby airports (yellow text)

According to NWS weather surveillance radar data, near the time the climb began, the helicopter encountered an area of light intensity echoes that were moving to the north-northwest (see figure 2).

Figure 2 – Helicopter’s flight track (magenta) and weather radar base reflectivity at 1357

At 1356:03 while at an altitude of 1,875 ft msl, and a ground speed of 101 knots, the helicopter began to climb straight ahead. About 9 seconds later, it reached an altitude of 2,025 ft, which was above the cloud ceiling height reported at SWF (1,991 ft). About 5 seconds later it began the first of two right turns (see figure 3). The first turn lasted about 9 seconds, with an average turn rate of 7 to 11° per second.

Figure 3 – Helicopter’s flight track during climbing turn and subsequent descent (red and green dots)

From the start of the climb until about the end of the first right turn, the rate of climb continually increased, and the airspeed continually decreased. At the end of the first turn, the rate of climb plateaued at about 2,400 feet per minute, and the airspeed had decreased to about 45 knots. Just as the rate of climb plateaued, the airspeed trend reversed and began to increase. The helicopter continued to climb for about 10 seconds, as the airspeed increased to about 95 knots. During this time the second right turn began, lasted for about 9 seconds, at an average turn rate of 9-12° per second. At 1356:34, just before the end of the second turn, the helicopter began to descend rapidly from its peak altitude of 2,650 ft. About 6 seconds later, the descent rate reached 7,200 feet per minute. As it descended through 1,900 ft (just below the cloud ceiling height reported at SWF), the descent rate reached 16,200 feet per minute. The tracking data ended about 2 seconds later, about 0.6 nautical miles north of the accident site. The entire flight was about 70 minutes long and the accident site was located about 120 nautical miles south of GFL.

A witness on a hiking trail about 0.1 mile southeast of the accident site reported hearing the helicopter’s engine “falter and die.” One to two seconds later, he heard a swishing sound, which he attributed to the helicopter “spinning” or being “out of control;” however, he could not see the helicopter due to the tree canopy. Shortly thereafter, he heard a series of loud noises that he described as “backfires, at machine gun speed” for about 2 seconds, which he surmised was “the engine catching and the rotors slapping,” and then the sounds stopped. He reported that the visibility was “clear,” and the clouds were higher than the mountain peaks; there was no fog over the river, and he could see the river clearly from his location on the hiking trail.

A second witness located about 1/2-mile northwest of the accident site reported hearing a “loud noise” that he believed was the helicopter’s engine. When he turned toward the noise, he observed the helicopter in a nose-down attitude of nearly 90°, travelling at a “high speed…straight down.” The witness lost sight of the helicopter as it descended below a tree line; shortly thereafter, he “heard it crash.” The noise he associated with the helicopter’s engine was continuous until the sound of impact. PERSONNEL INFORMATIONThe pilot held a private pilot certificate with rotorcraft-helicopter rating. He did not have an instrument rating. A review of his logbook revealed that he had not recorded any actual or simulated instrument flight experience, and no instrument training was noted in the remarks section of any log entries. In November 2020, one flight was remarked with “IFR Conditions, asked for special VFR.” In May of 2021, one flight was remarked with “low clouds, rain, autopilot through clouds.” AIRCRAFT INFORMATIONThe helicopter was equipped with inflatable landing gear floats and a flight control stability augmentation system. METEOROLOGICAL INFORMATIONWeather conditions reported at the nearest reporting station (SWF) at the time of the accident included wind from 070° at 5 knots, visibility 5 miles in mist, ceiling overcast at 1,500 ft agl, (1,991 ft msl, based on the station’s elevation), temperature 16° C, dew point temperature 14° C, altimeter setting 30.20 inches of mercury. Data from other reporting stations along the route of flight near the accident and toward the destination airport indicated that overcast ceiling heights were decreasing from north to south. Infrared satellite imagery depicted a thick layer of clouds that obscured the accident site, with cloud tops near 27,000 ft. Weather surveillance radar imagery depicted a small area of light echoes near the end of the ADS-B data, and a large area of light to moderate echoes between the accident site and the intended destination (ISP). The radar’s lowest scanning beam was centered about 5,800 ft msl over the accident site.

The Terminal Aerodrome Forecast (TAF) issued at 0723 expected marginal visual flight rules conditions to prevail at SWF, with visibility of 6 statute miles or greater and overcast cloud ceilings at 1,200 ft above ground level (agl). The next closest TAF, also issued at 0723, expected instrument flight rules (IFR) conditions to prevail at Westchester County Airport (HPN), White Plains, New York (located 25 nautical miles southeast of the accident site), with visibility 5 statute miles in light rain showers, and cloud ceiling overcast at 800 ft agl.

A national weather service AIRMET Sierra, current at the time of the accident, advised of IFR conditions expected due to ceilings below 1,000 ft agl and/or and visibility below 3 miles in precipitation and mist. The AIRMET extended over the accident site and the planned destination. There were no other SIGMETs, convective SIGMETs, or CWA’s current for the area during the period surrounding the flight.

A search of the FAA contract Automated Flight Service Station provider Leidos indicated that they, and no other 3rd party vendors utilizing the Lockheed Flight Service (LFS) System, had any contact with the pilot of the accident helicopter on the day of the accident. A separate search of ForeFlight records indicated that the pilot had an account with the vendor and had used the application at 1113, and that he had created a route string for a flight from ISP to GFL via the Hudson River and back to ISP at an altitude of 1,000 ft. Before the flight, the following airports were viewed in the application (which includes the latest METAR, TAFs, and NOTAMs): Brookhaven Airport (HGV), Shirly, New York, and Minute Man Air Field (6B6), Stow, Massachusetts. The pilot did not view any weather imagery inside the application. No formal route briefing was requested and there was no confirmation the pilot reviewed or searched for the current inflight weather advisories for the area. The pilot had multiple tablet devices in the cockpit, all of which were too damaged to examine after the accident. AIRPORT INFORMATIONThe helicopter was equipped with inflatable landing gear floats and a flight control stability augmentation system. WRECKAGE AND IMPACT INFORMATIONExamination of the accident scene revealed a debris path that was about 110 ft-long and oriented on a heading of about 168° magnetic. It began with damaged treetops and broken limbs, where the tail rotor assembly and fragments of the tail rotor guard were located. The tail rotor blades were largely intact with leading edge gouge damage. The main impact crater, which contained fragmented landing gear components, was about 60 ft from the damaged tree, with the main wreckage located about 60 ft beyond the impact crater. The fuselage was fragmented and compressed from the nose toward the rear seats.

Flight control continuity could not be confirmed due to impact damage and some system portions were not located. However, all flight control attachment fittings remained attached at their ends. Most of the flight control push-pull tubes were fractured, some in multiple locations, consistent with overload.

The overriding clutch operated normally and smoothly when rotated by hand. The upper drive sheave had impact marks on the front and rear faces adjacent to the clutch centering strut and fuselage frame tubes, respectively. A 3-inch imprint consistent with the starter ring gear was present in the grooves of the upper sheave. The main and auxiliary fuel tanks were impact damaged; their bladders were breached, and a trace amount of fuel remained in the bladders. Some vegetation surrounding the impact crater and the main wreckage showed evidence of fuel blight. A portion of each main rotor blade (about 4 to 6 ft) remained attached to the hub. Most of the spar of one blade also remained attached. Fragments of damaged main rotor blades ...