WPR21FA233 · Piper PA-22-135
Piper PA-22-135 · Accident: loss of control in flight on approach
From Rogue Valley International-Medford Airport (MFR) to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR21FA233
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-22-135
- Aircraft type
- Piper PA-22
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N2618A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Rogue Valley International-Medford Airport (MFR), Meford, ORTo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR go-around
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Physical
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR21FA233
- Event ID
- 20210621103294
- Case number
- WPR21FA233
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: aa2ffe3fd65e6f52683847815c1e9f86a43d156a61e083d3b94ffafca267f35e; retrieved 2026-09-15T07:30:12.939Z.