The U.S. aircraft register, updated daily
Accidents · NTSB ERA23FA048 · Final report

Beech A36 accident near Harlan, Kentucky, November 3, 2022

On November 3, 2022 at about 2:09 pm local time, a 1977 Beech A36, registered N84R, was destroyed in an accident during approach (VFR pattern final) near Harlan, Kentucky (Tucker-Guthrie Meml airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot’s visual flight rules flight into instrument meteorological conditions during an approach to land at an airport in mountainous terrain, which resulted in controlled flight into terrain. Contributing to the accident was the pilot’s hazardous anti-authority attitude.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 3, 2022 · about 2:09 pm local time
Place
Harlan, Kentucky · Tucker-Guthrie Meml · map
Type
Accident
Injuries
1 person was killed.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Beech A36, built 1977 · all A36s on the register
Registration
N84R · registry record · serial E-1146
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot was a physician, and the purpose of flight was to attend to his patients for scheduled appointments at a medical office near the destination airport. He had frequently flown into the airport, which was located in mountainous terrain. Review of flight track data found that the flight followed a route that was consistent with what the pilot had entered into a flight planning application shortly before flight. Upon arrival in the destination airport area, the pilot announced over the airport’s common traffic advisory frequency that he would circle to land. There were no further communications recorded from the pilot. Flight track data revealed that the airplane completed a total of three approaches to the runway. The weather conditions reported at the time of the approaches were low instrument flight rule (IFR) conditions. Based upon hourly weather observations at the airport, surveillance video, and a pilot-rated witness located at the airport, visibility was likely restricted to 200-300 ft due to fog and low clouds. Based upon a witness statement and flight track data, it is likely that on each approach the pilot descended to a lower altitude in search of the runway environment. On the third and final approach, the airplane impacted a ravine and steep rock wall about 50 ft below the runway elevation and 375 ft short of the runway threshold (the runway sat atop of rising terrain, with a valley below). Based on this information, it is likely that the pilot descended below the runway elevation on final approach, which resulted in the pilot’s controlled flight into terrain while searching for the runway environment. The pilot did not file a flight plan, nor communicate with air traffic control during the flight after departing under visual flight rules (VFR). The airport had one published GPS circling instrument approach procedure. The airplane’s flight path and altitude were not consistent with this approach, and the weather conditions were far below published visibility and cloud ceiling minimums for the approach. Additionally, a few weeks before the accident, the airport had issued a Notice to Air Mission, which advised that the runway end identifier lights, and all airport lights, were out of service. Due to the extremely low visibility and clouds, it is unlikely that the runway lights would have aided the pilot’s search for the runway environment. Review of the pilot’s past flights into the accident airport found that he routinely conducted teardrop circling maneuvers to land in poor weather. Within the 90 days before the accident, a total of four flights were identified in which the pilot was able to land by circling over the airport under IFR or low IFR weather conditions. The approaches were likely conducted under VFR and into instrument meteorological conditions (IMC), given that the altitudes and flight track flown were not consistent with the published instrument approach procedure. There was one additional flight located in the pilot’s logbook, about four years before the accident, where remarks noted that he attempted an approach to the accident airport to check the low IFR conditions. The remarks noted that the low IFR conditions were confirmed during an approach, and he subsequently diverted to a nearby airport that he also frequently flew to. This nearby airport’s weather reporting station, around the time of the accident, reported similar low IFR conditions to the accident airport. There was no record that the pilot received a weather briefing before the flight, and it is not known what information he reviewed. Had he checked the weather, he would have seen that the destination airport was reporting low IFR conditions, as well as the other nearby airport that he had diverted two on the flight four years prior. While the pilot had logged several hours of actual instrument flight experience in the preceding 90 days before the accident, he did not possess instrument currency for the accident flight (nor had he filed an IFR flight plan). The investigation found that the pilot routinely flew VFR to the accident airport and conducted circling maneuvers to land into IMC. The pilot’s repeated VFR flight into IMC, his decision to fly an approach that was not consistent with the instrument approach procedure published for the airport, and lack of instrument currency demonstrated an anti-authority hazardous attitude, in which he repeatedly disregarded regulations and demonstrated poor judgement. It is possible that the pilot’s decision to conduct the flight was in-part influenced by his scheduled appointments with his patients, which would have increased the external pressures to complete the approach to landing. Toxicology testing revealed that the pilot had used phentermine, a stimulant and anorectic medication used to treat obesity. The drug also has a possible side benefit of increased alertness. Methamphetamine was also detected at low levels in some of the pilot’s tissue specimens; methamphetamine is also a central nervous stimulant and can be medically indicated to treat obesity. Due to extensive injuries, no blood specimens were available for toxicological testing, so whether these medications were at therapeutic levels could not be determined. The pilot’s use of prohibited substances, in addition to his decisions to habitually fly to the airport under VFR and into IMC, is a further example of poor judgment and an anti-authority hazardous attitude. The detection of these medications was more emblematic of his disregard of safety and rules than of impairment. Thus, while stimulants were detected in the pilot’s tissues, it is unlikely that the effects of the pilot’s use of phentermine and methamphetamine contributed to this accident. The sedating antihistamine chlorpheniramine was also detected in the pilot’s liver and muscle tissue, which is commonly taken to treat colds. Due to the lack of specimens available for toxicology testing, it is unknown whether the pilot had experienced side effects or if chlorpheniramine was at therapeutic levels. Thus, it could not be determined if the effects from the pilot’s use of chlorpheniramine was a factor in this accident.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Controlled flight into terrain or object (CFIT) during approach (VFR pattern final)
  2. VFR encounter with IMC during approach (VFR pattern final) defining event

The NTSB's findings

  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Decision related to condition
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low visibility › Decision related to condition
  • Personnel issues › Psychological › Personality/attitude › Personality › Pilot
  • Environmental issues › Task environment › Pressures/demands › Time/schedule pressure › Decision related to condition

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 3,754 hours in all; 3,421 in this make and model; 58 in the last 90 days; 3,535 as pilot in command
  • Last flight review: March 30, 2021
  • Medical certificate: BasicMed (without waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 5,416 hours
  • Last inspection: annual inspection, December 12, 2021
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Continental Motors IO-520-BA (piston); 945 hours total
  • Fire on the ground

The flight

  • Departed from: DKX Knoxville TN at 1:32 pm
  • Destination: I35 Harlan KY
  • Flight plan: none
  • Runway 8, 3,461 ft by 75 ft

Weather at the time

  • Light: daylight
  • Visibility: 0.2 statute miles
  • Sky: overcast at 200 ft
  • Temperature: 46°F (8°C), dew point 46°F (8°C)
  • Altimeter: 30.37 inHg
  • Observation at 10:15 am from I35

Weather report (METAR): METAR KI35 031415Z AUTO 00000KT M1/4SM OVC002 08/08 A3037 RMK AO2 T00820082

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

20 documents, released by the NTSB on April 25, 2024. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Airworthiness and Technical Factors Factual Report PDF, 32 pages · our copy View Download
2 Memorandum for Record (Witness_helicopter Pilot) PDF, 2 pages · our copy View Download
3 Memorandum for Record (Airport Management) PDF, 3 pages · our copy View Download
4 Memorandum for Record (Spouse of Pilot) PDF, 1 page · our copy View Download
5 Pilot Logbook Review PDF, 11 pages · our copy View Download
6 Memorandum for Record (ForeFlight Data) PDF, 3 pages · our copy View Download
7 Memorandum for Record (Leidos Flight Service) PDF, 1 page · our copy View Download
8 NTSB Factual Review (Meteorological Information) PDF, 6 pages · our copy View Download
9 FAA Chart Supplement PDF, 1 page · our copy View Download
10 RNAV Gps-a Approach Chart PDF, 1 page · our copy View Download
11 FAA NOTAM Search Results I35 PDF, 1 page · our copy View Download
12 I35 Audio - 0930L audio · our copy View Download
13 I35 Audio 1000L audio · our copy View Download
14 Annual Mx Endorsements PDF, 2 pages · our copy View Download
15 Kml Track and Location Data map file · our copy Download
16 Medical Factual PDF, 5 pages · our copy View Download
17 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page · our copy View Download
18 Toxicological Report PDF, 2 pages · our copy View Download
19 Statement of Party Representatives to NTSB Investigation PDF, 1 page · our copy View Download
20 Textron Aviation Technical Review PDF, 1 page · our copy View Download

The same docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.