N84R

HISTORY OF FLIGHTOn November 3, 2022, about 1009 eastern daylight time, a Beech A36 airplane, N84R, was destroyed when it impacted terrain at the Tucker-Guthrie Memorial Airport (I35) Harlan, Kentucky. The private pilot was fatally injured. The airplane was operated by the pilot as a personal flight conducted under the provisions of Title 14 Code of Federal Regulations Part 91.

According to the pilot’s family and I35 airport personnel, the pilot frequently flew into the accident airport for work. The pilot was a physician, and he was scheduled to see patients in Harlan, Kentucky on the day of the accident.

According to automatic dependent surveillance – broadcast (ADS-B) data, the airplane departed from Knoxville Downtown Island Airport (DKX), Knoxville, Tennessee, at 0932. There was no record of a flight plan or weather briefing for the flight, nor was there any communication with air traffic control.

The flight track was consistent with a route of flight the pilot had entered into the flight planning application Foreflight about 0929. The route contained multiple user defined waypoints towards the I35 airport. The reported ADS-B altitude data for the entirety of the flight was in error and did not correspond to a reliable value.

Review of archived audio recordings of the I35 common traffic advisory frequency found that as the pilot entered the traffic pattern area he stated, “Harlan Tucker Guthrie bonanza 84 romeo is two and a half to the west will circle for landing Harlan Tucker Guthrie.” There were no further radio communications recorded.

The flight track data revealed that the airplane completed multiple approaches and maneuvers over the airport environment. About 0958, the airplane flew over runway 8 and made a slight right turn followed by a left 180° teardrop turn. This was the first pass over runway 8. About 1000, the airplane flew over runway 26 on an extended centerline before it made another left teardrop 180° turn back toward runway 8. About 1002, the airplane made a second pass over runway 8 before it made a slight right turn again and another left 180° teardrop turn. About 1005, the airplane flew over runway 26 on a longer extended centerline before it made another left 180° teardrop turn to intercept an extended centerline course for runway 8. This was the third and final approach to runway 8.

About 1009, the airplane followed an extended centerline course toward runway 8. The last recorded position was at 1009:54, about 0.1 nautical mile from the runway 8 threshold. Subsequently, the airplane impacted a ravine and steep rock wall about 50 ft below the runway elevation and 375 ft from the runway 8 threshold. Figure 1 displays an overview of the ADS-B flight track.

Figure 1 - ADS-B flight track displaying the three approaches to runway 8 in addition to the 180° left teardrop turns (displayed in white). The green line represents the first approach. The yellow line represents the second approach and the red line represents the third and final approach.

According to a pilot-rated witness that was at the I35 airport terminal, he heard the accident airplane complete two approaches to runway 8. He did not visually observe the accident airplane due to the fog and low clouds. The first approach seemed to be high, and the second approach sounded “really low.” For both passes the witness reported that the engine noise was a steady piston engine sound, with no noticeable increases or decreases in power.

After the second pass, the witness assumed the airplane had performed a missed approach. The engine sound became more distant from the airport, and he did not hear the accident airplane again, nor did he hear the accident airplane’s eventual impact with terrain. PERSONNEL INFORMATIONReview of the pilot’s electronic logbook found that his most recent flight review and instrument proficiency check (IPC) was completed on March 30, 2021. In the past six months, the pilot logged three instrument approaches. The last flight logged was on October 28, 2022. The pilot did not meet the instrument currency requirements as prescribed in Federal Aviation Regulation § 61.57(c) Recent flight experience, which in-part required the completion of six instrument approaches.

Review of commercially available flight track data for the accident airplane, and review of the pilot’s logbook from August 1, 2022, to November 1, 2022, found that the pilot had completed over 35 flights originating from either McGhee Tyson Airport (TYS), Knoxville, Tennessee, or DKX airport (the accident departure airport), to Middlesboro Bell County Airport (1A6), Middlesboro, Kentucky, or I35 airport. The 1A6 airport was along the route of flight between DKX and I35, located about 23 miles southwest from I35. In the three months before the accident, the pilot landed at I35 at least 15 times.

The investigation further reviewed recent commercially available flight track data for the accident airplane and recent flights the pilot had logged to I35 airport. The review identified that the pilot routinely landed at I35 when the airport was reporting instrument flight rule (IFR) conditions or low IFR conditions. The flight track approaches varied; however, multiple flights displayed a similar circling maneuver and approach to runway 8 as in the accident flight.

On September 27, 2022, the pilot completed a flight to I35 and landed at 0950. The Meteorological Aerodrome Reports (METARs) published around the time of the approach indicated IFR conditions. The METAR published nearest to the time of the landing observed a broken cloud ceiling at 100 ft and 10 statute miles of visibility. The flight track data showed that the flight completed a similar circling maneuver pattern over I35 as compared to the accident flight; however, the flight landed after the second approach to runway 8. The flight track was not consistent with the published GPS-A instrument approach procedure.

On September 6, 2022, the pilot completed a flight to I35 and landed at 1048. The METARs published around the time of the approach indicated IFR conditions. The METAR published nearest to the time of the landing observed a broken ceiling at 500 ft and 10 statute miles of visibility. Review of the flight track showed that the pilot completed a straight-in approach to landing, which was not consistent with the GPS-A instrument approach procedure.

On September 1, 2022, the pilot completed a flight to I35 and landed at 1004. The METARs published around the time of the approach indicated IFR conditions with a broken ceiling at 300 ft and 10 statute miles of visibility. Shortly before the approach, visibility was reported as 7 statute miles and the ceiling was overcast at 100 ft. The pilot completed a straight-in approach to runway 8; however, before landing, a 360° right turn was completed before rejoining the final approach and landing on runway 8. The track was not consistent with the GPS-A instrument approach procedure.

On August 30, 2022, the pilot completed a flight to I35 and landed at 0912. The METARs at I35 published around the time of the approach indicated IFR conditions.

On August 28, 2018, an additional notable flight to I35 was identified in the pilot’s logbook. The flight track data were not available. The logbook remarks entry stated that the weather conditions at I35 were IFR, with cloud ceilings reported at 100 ft and visibility at 1/4 statute miles. The remarks further stated that he conducted a “fly by” to check the ceiling at I35 and “confirmed” the weather conditions. He then diverted to 1A6 airport. The logbook remark stated: “IFR at i35 did a fly by to check ceiling reported at 100 and .25 viz. Confirmed, went back to 1a6.” METEOROLOGICAL INFORMATIONAccording to METAR observations around the time of the accident, the I35 airport was experiencing low IFR conditions. About 1015, a METAR observed that the visibility was less than 1/4 statute miles, and the ceiling was overcast 200 ft above ground level (agl). Review of METARS at the I35 airport found that from 0815 to 1055 the visibility was less than 1/4 statute mile, and the ceiling was overcast 200 ft agl. About 1115, about one hour after the accident, the I35 METAR reported VFR conditions, with the visibility improving to 10 statute miles, and scattered clouds at 200 ft agl.

Surveillance video screenshots were provided by the I35 airport at the time of the accident, as viewed in Figure 2.

Figure 2 - Surveillance video screenshot at the time of the accident, as viewed from the airport terminal.

The estimated visibility (based on measurements to known objects via aerial imagery) was limited to about 175 ft due to fog and low clouds. An additional image was provided (figure 3), that displayed improved visibility about an hour and a half after the accident.

Figure 3 - Surveillance video screenshot taken at 1130 the day of the accident, showing that the fog had burnt off and visibility had improved, as viewed from the airport terminal.

The pilot-rated witness reported that near the time of the accident the weather conditions were very foggy. He reported that he could see no farther than the south runway edge area and the red 8-26 runway sign from the terminal fueling area. As measured with aerial imagery, this distance was about 250 - 300 ft.

At Middlesboro Bell County Airport (1A6), Middlesboro, Kentucky, about 23 nautical miles southwest of I35, multiple METARs an hour before and after the accident time reported low IFR conditions due to visibility restricted by fog and mist and low cloud ceilings.

The weather conditions at the departure airport were VFR at the time of the pilot’s takeoff. WRECKAGE AND IMPACT INFORMATIONAll major portions of the airplane were located; a post-impact fire consumed a majority of the cockpit, fuselage, and portions of the left wing. Figure 4 provides an overview of the airport environment approaching runway 8 and the distribution of wreckage.

Figure 4: Overview of the airport environm...