N379DH

HISTORY OF FLIGHTOn August 10, 2022, about 1459 Pacific daylight time, a Cirrus SR22, N379DH, was destroyed when it was involved in an accident near Blyn, Washington. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight.

The pilot’s wife reported that the pilot had departed Friday Harbor and intended to fly to Olympia, where he was going to rent a vehicle and drive to West Port, Washington, for a 4-day fishing trip.

Recorded ADS-B data showed the airplane departed runway 16 at the Friday Harbor Airport (FHR), Friday Harbor, Washington, about 1445, and proceeded on a southerly heading and climbed to an altitude of about 1,100 ft msl. The data showed the airplane continued south until about 1458:14, when a loss of ADS-B contact occurred. ADS-B contact was reestablished at 1458:51, with the airplane flying on an easterly heading. At 1458:52, the data showed a right turn to a southerly heading and a descent to 900 ft msl at 1459:07, when a second loss of ADS-B contact occurred. As seen in Figure 1, ADS-B contact was reestablished at 1459:13 and showed the airplane on a southerly heading at an altitude of 1,100 ft msl. The last ADS-B target was at 1459:19, at an altitude of 1,400 ft msl located about 0.63 miles northeast of the accident site.

Figure 1: ADS-B Track

The National Transportation Safety Board (NTSB) Vehicle Recorders Laboratory recovered data from the PFD and MFD that captured the accident flight. The data showed that when ADS-B data stopped the airplane started a right turn from a heading of about 169° magnetic to a 238° magnetic heading over about 11 seconds. Throughout this time, the airplane had climbed to 1,460 ft msl and then descended to 1,363 ft msl at the time of the last recorded data point, located about 930 ft east of the accident site.

The data showed that engine parameters were captured every 6 seconds, and that during takeoff, engine power settings had increased to 2,720 rpm and 29.2 inches of manifold pressure. About 1 minute 42 seconds later, engine power settings were reduced to 2,440 rpm and 19.7 inches of manifold pressure. Engine power settings remained consistent at that setting for about 7 minutes 36 seconds, when it was reduced to 2,200 rpm and 16.4 inches of manifold pressure. About 54 seconds later, engine power was increased to 2,280 rpm and 17.6 inches of manifold pressure. The settings remained consistent for about 3 minutes 18 seconds, when engine power was increased. Engine power settings remained increasing over the last 36 seconds of recorded data to 2,680 rpm and 25.8 inches of manifold pressure.

The data showed cylinder No. 6’s cylinder head temperature (CHT) had reached 500° F 48 seconds after takeoff power was applied, and remained at 500° F for 10 minutes 18 seconds, when it began to fluctuate between 487° F and 498° F. All of the remaining cylinders’ CHTs remained consistent and varied between 249° F and 283° F. Additionally, exhaust gas temperatures remained consistent among all 6 cylinders throughout the accident flight. AIRCRAFT INFORMATIONThe airplane was equipped with an Avidyne PFD and MFD. Additionally, the airplane had analog gauges, including indicators for airspeed, attitude, altimeter, tachometer, oil temperature, oil pressure, amperage, volts, fuel flow, and fuel pressure.

A pre-purchase report supplied by a maintenance facility, dated December 14, 2020, stated in part that “PFD & MFD Screens showing signs of possible failures.”

A representative from another maintenance facility reported that in the beginning of July 2022, the pilot/owner of the airplane had contacted their facility about issues involving the PFD and MFD, to which he advised the pilot/owner to fly the airplane to their facility for inspection. The representative stated that upon arrival, he inspected the displays and found that neither display was working. He noted that the PFD had a magenta backdrop that indicated “an internal power fail” and the MFD was operative, but the backlighting of the display was not functioning, which made it “virtually impossible to see.” The representative added that the pilot/owner asked him if the airplane was able to be flown in the condition it was in, and he had advised the pilot/owner that it was not.

Review of maintenance logbooks revealed no entries regarding the repair or replacement of the PFD or MFD. Additionally, no reference to a static system check per CFR 91.111 was observed. METEOROLOGICAL INFORMATIONLaw enforcement reported that when they arrived at the accident site, they observed a fog bank that was about 700 ft above the ground and about ¼ mile north of the accident site.

The automated surface observation system (ASOS) located at FHR, at an elevation of 113 ft msl, reported 6 minutes before the accident airplane took off that the visibility was 9 statute miles, with a scattered cloud layer at 800 ft and an overcast cloud layer at 10,000 ft.

The automated weather observation system (AWOS) located at the Jefferson County International Airport, Port Townsend, Washington, at an elevation of 110 ft msl, located about 5.5 miles east-northeast of the accident site, reported about 5 minutes before the time of the accident that visibility was 10 statute miles, with an overcast cloud layer at 800 ft.

A depiction of the observations from the NWS Aviation Weather Center’s Helicopter Emergency Medical System (HEMS) METAR display with the weather radar overlay is included as Figure 2 with the accident site marked by the red star.

The display showed general VFR to MVFR conditions over the area with an area of IFR conditions in the vicinity of the accident site. The station models showed a generally diffluent, or easily dissolving, wind pattern over the area with winds from the northwest in the vicinity of the accident site and from the southeast over the departure airport.

Figure 2: NWS Aviation Weather Center’s METAR display at 1510 PDT with weather radar overlaid and approximate accident site. AIRPORT INFORMATIONThe airplane was equipped with an Avidyne PFD and MFD. Additionally, the airplane had analog gauges, including indicators for airspeed, attitude, altimeter, tachometer, oil temperature, oil pressure, amperage, volts, fuel flow, and fuel pressure.

A pre-purchase report supplied by a maintenance facility, dated December 14, 2020, stated in part that “PFD & MFD Screens showing signs of possible failures.”

A representative from another maintenance facility reported that in the beginning of July 2022, the pilot/owner of the airplane had contacted their facility about issues involving the PFD and MFD, to which he advised the pilot/owner to fly the airplane to their facility for inspection. The representative stated that upon arrival, he inspected the displays and found that neither display was working. He noted that the PFD had a magenta backdrop that indicated “an internal power fail” and the MFD was operative, but the backlighting of the display was not functioning, which made it “virtually impossible to see.” The representative added that the pilot/owner asked him if the airplane was able to be flown in the condition it was in, and he had advised the pilot/owner that it was not.

Review of maintenance logbooks revealed no entries regarding the repair or replacement of the PFD or MFD. Additionally, no reference to a static system check per CFR 91.111 was observed. WRECKAGE AND IMPACT INFORMATIONExamination of the accident site revealed that the airplane impacted a heavily wooded area at an elevation of 1,286 ft msl. The first identified point of contact was a freshly topped tree with composite material fragments located near the tree root. The debris path initially extended along an approximate 270° heading for about 300 ft before shifting to an approximate 312° heading, which extended for about 155 ft. All major structural components of the airplane were located within the debris path. Throughout the debris path, numerous trees, 70 to 80 ft in height, were topped. One tree, located adjacent to the fuselage, was stripped of its bark along the eastern side of the tree from about 5 ft above the ground to the area it was topped.

The fuselage came to rest inverted on a heading of about 301°. The forward part of the fuselage was fractured in half just aft of the lower part of the windshield. The upper cabin roof was separated and located throughout the debris path. The Cirrus Airframe Parachute System (CAPS) handle was found extended with no securing pin on the separated part of cabin roof structure. The parachute remained stowed within its deployment bag. The CAPS rocket was found secure to its cables, separated from the airframe, and was partially wrapped around the tree with stripped bark. The rocket was not expended. The engine was separated from the engine mount and found inverted within the wreckage debris path.

Impact damage to both the PFD and MFD precluded functional testing of either display.

Examination of the engine revealed that both magnetos, standby alternator, and starter were separated from their mounts. The upper area of the crankcase had a crack that spanned between the Nos. 5 and 6 cylinders. The Nos. 2-, 4-, and 6- cylinder fuel injectors were pulled away from their respective cylinders. The No. 6 cylinder exhibited impact damage to the cylinder head, and the induction rocker arm and housing were separated.

The upper spark plugs, rocker box covers, and fuel pump were removed. The crankshaft would not rotate by hand. All 6 cylinders were examined internally using a lighted borescope and exhibited varying degrees of corrosion. The intake and exhaust valves on cylinders Nos. 1, 2, 3, 5, and 6 were unremarkable. The valves on cylinder No. 4 could not be examined due to the position of the piston. The No. 6 cylinder exhibited no evidence of heat distress or evidence of high cylinder head temperature operation.

Six holes w...