eFlight
Accidents · NTSB WPR21FA233 · Final report

Piper PA-22-135 accident near White City, Oregon, June 20, 2021

On June 20, 2021 at about 9:40 pm local time, a Piper PA-22-135, registered N2618A, was destroyed in an accident during approach (VFR go-around) near White City, Oregon (Beagle Sky Ranch airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s failure to maintain control of the airplane during a go-around, which resulted in a collision with trees. Contributing to the accident was the pilot’s impairment due to his medical conditions and the effects of his medications.

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

What the record shows

Date
June 20, 2021 · about 9:40 pm local time · cases in 2021
Place
White City, Oregon · Beagle Sky Ranch · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Piper PA-22-135 · all PA-22-135s on the register
Registration
N2618A · registry record · serial 18-2186
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot was repositioning his airplane to the accident airport for an annual inspection. He had planned to have a friend meet him at the destination airport to drive him home. The friend waiting to pick the pilot up at the destination airport stated that the pilot initiated a go-around when the airplane was not aligned with the runway on the first landing attempt. The friend stated that the pilot attempted another landing and once again the airplane was not aligned with the runway, so the pilot initiated another go-around. The pilot made two landing attempts, and during the last attempt, the airplane contacted trees off the left side of the departure end of the runway. The airplane then impacted terrain and a postimpact fire ensued. At the time of the accident, the density altitude at the airport was over 4,000 ft. A witness located at a residential airpark about 5 nautical miles from the pilot’s intended destination, where the accident subsequently occurred, reported that the accident airplane had landed at their private airpark just before the accident. They were worried because the airplane’s approach was erratic, and fast, and touched down about midfield and bounced before it went out of their view. The witness went to find the airplane and found it parked in his front yard. The pilot seemed lethargic, confused, and slow to answer questions. The pilot asked multiple times if he was at his destination airport, and the witnesses replied that he was not. Witnesses reported that about 20 minutes later the pilot departed from their airport. The witness reported that, although the airplane’s engine was running and sounded normal, it also sounded like the pilot had only applied partial power on takeoff. The witness noted that the airplane did not appear to be under control during the takeoff. Postaccident examination of the airframe and engine revealed no mechanical anomalies that would have precluded normal operation. According to the pilot’s wife, the pilot had heart issues that included two previous heart attacks, one of which was 3 weeks before the accident. The pilot’s wife also stated that her husband was easily confused, irritable, and was in poor health. His two visits to the emergency room about 10 days before the accident suggest that the pilot’s condition was not well-controlled. The pilot’s toxicology testing detected gabapentin, doxylamine, dextromethorphan, torsemide and carvedilol in his system. In addition, the pilot’s autopsy identified severe cardiovascular disease, chronic kidney disease, and previous atrial fibrillation. Based on the operational evidence, the pilot had actively attempted several landings when the accident occurred; therefore, it is unlikely that the pilot experienced sudden incapacitation. However, operational evidence and witness reports indicate that the pilot was behaving in a confused manner. The pilot was taking a diuretic medication and other medications that decrease sweating and body cooling. He was also taking gabapentin, which is associated with dizziness and sleepiness. Even without a heat stressor, people with chronic heart failure can experience mental confusion and impaired thinking. The pilot also had moderate chronic kidney failure that would decrease his heat tolerance. Additionally, heat stress can further impact kidney function. Decline in kidney function with subsequent buildup of body wastes in the blood can lead to confusion. Given the high outside temperatures, the pilot’s medical conditions, as well as the prescribed medication detected in his system, it is likely that the pilot experienced mental confusion and impaired thinking/judgement, which resulted in his inability to safely operate the airplane.

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. Collision with terrain or object (not controlled flight into terrain) during approach (VFR go-around)
  2. Loss of control in flight during approach (VFR go-around) defining event

The NTSB's findings

  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • Personnel issues › Physical › Impairment/incapacitation › Prescription medication › Pilot
  • Personnel issues › Physical › Health/Fitness › Use of medication/drugs › Pilot
  • Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Effect on equipment

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 623 hours in all; 0 in this make and model
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: unk
  • Injury: fatal

The aircraft

  • Last inspection: annual inspection, March 19, 2020
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-290-D2 (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: MFR Meford OR
  • Flight plan: none
  • Runway 15/3, 3,000 ft by 130 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 66°F (19°C), dew point 52°F (11°C)
  • Altimeter: 29.90 inHg
  • Observation at 2:53 am from KMFR, 10 miles away

Weather report (METAR): KMFR 200953Z AUTO 00000KT 10SM CLR 19/11 A2990 RMK AO2 SLP113 T01940111

Injuries

FatalSeriousMinorNone
Flight crew1

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

9 documents, released by the NTSB on September 27, 2023. 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 Witness Statements - Belknap PDF, 1 page · our copy View Download
2 Witness Statements PDF, 3 pages · our copy View Download
3 Witness Statements (FAA) PDF, 2 pages · our copy View Download
4 Maps or Charts of Accident Area (Googleearth) map file · our copy Download
5 NTSB Medical Review PDF, 3 pages · our copy View Download
6 Toxicological Report PDF, 1 page · our copy View Download
7 NTSB on Site Examination Report PDF, 13 pages · our copy View Download
8 Statement of Party Representatives to NTSB Investigation - Piper PDF, 1 page · our copy View Download
9 Statement of Party Representatives to NTSB Investigation - Lycoming PDF, 1 page · our copy View Download

The same docket at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR21FA233.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.