WPR13LA283

NTSB accident investigation · Extra 300/LT · Adrian, OR · June 23, 2013

Accident · FatalLimited investigationFinal report
Date
June 23, 2013, 11:01 local (18:01 UTC)
Place
Adrian, OR
Injuries
1 fatal
Damage
Substantial damage
Phase of flight
Maneuvering
Aircraft
N169TMExtra 300/LT
Defining event
Maneuvering-low-alt flying: Low altitude operation/event
Weather
Visual (VMC) · Day
Status
Completed · report May 13, 2015
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
FAA Boise FSDO
FAA report
20130623010569A
Case key
87273

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The pilot's improper decision to conduct low-level maneuvering in a river canyon with power lines, which resulted in his failure to maintain clearance from the power lines.

Findings · 5

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

Witnesses reported that they observed the airplane flying at a low level through a river canyon—one witness stated it was following the canyon's contours—and then colliding with a marked power line strung across the river. The airplane subsequently impacted the ground. Scratch marks from the wire were observed on the left wing. First responders reported that the pilot was in the rear seat, which might have hampered his forward visibility and led to his failure to see the power lines. The toxicological report identified the presence of ramipril and atorvastatin in the pilot's urine; however, neither of these medications are impairing. The toxicology testing also detected a very low level of morphine in the pilot's urine, which indicates that he had used a medication containing an opioid within a few days of the accident. However, because it was no longer detectable in the blood, it is not likely that the pilot was impaired by the medication at the time of the accident.

Factual narrative

On June 23, 2013, about 1101 Pacific daylight time, an experimental Extra Flugzeugproduktions EA 300/LT, N169TM, collided in flight with power lines near Adrian, Oregon. The pilot/owner was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The private pilot sustained fatal injuries; the airplane sustained substantial damage from impact forces. The local personal flight departed Ontario, Oregon, at an undetermined time. Visual meteorological conditions (VMC) prevailed, and no flight plan had been filed. A witness was preparing to fish when he heard the airplane's engine. He observed the airplane fly through the river canyon above him; it was following the contours of the canyon. He saw the airplane collide with large power lines (5/8-inch cable) across the Owyhee River, about 1/2 mile down river from the Owyhee Dam. The airplane continued on, but he could not see it any longer due to the canyon walls. Another witness was fishing, and heard the airplane come around a corner downriver from him. He thought that the pilot initiated a climb to avoid the power lines. The airplane went into a flat spin, and flew into the power lines before contacting the ground. Another witness, who is a private pilot, was fishing about 2 miles away. He heard the engine get extremely loud, and thought that meant that the airplane was descending rapidly. He observed the airplane flying in the area the previous day, and estimated its speed at 200 miles per hour. A first responder reported that the pilot was in the rear seat, and they observed scratch marks from a wire on the left wing. The Malheur County Medical Examiner authorized an autopsy by the Saint Alphonsus Medical Center-Ontario Department of Pathology. The FAA Forensic Toxicology Research Team, Oklahoma City, Oklahoma, performed toxicological testing of specimens of the pilot. Analysis of the specimens contained no findings for carbon monoxide or volatiles. They did not perform tests for cyanide. The report contained the following findings for tested drugs: Atorvastatin detected in urine, Atorvastatin not detected in blood; 0.07 (ug/ml, ug/g) morphine detected in urine, morphine not detected in blood (cavity); Ramipril detected in urine, Ramipril not detected in blood. Ramipril was used to treat high blood pressure, and Atorvastatin was used to treat elevated cholesterol. A Federal Aviation Administration (FAA) inspector examined the wreckage on scene. The airplane came to rest upright. There was extensive damage to the airplane forward of the wings. The landing gear collapsed downward. The power lines were marked with orange spherical balls.

Aircraft

Registration
N169TM
Reported as
Extra 300/LT
Category
Airplane
Serial number
LT007
Built
2011
Airframe hours
59
Engine
Lycoming AEIO-580-B1A, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Edward Claugus
Registered owner
Edward Claugus
Airworthiness certificate
Special, Experimental (Special)
Last inspection
Condition · December 1, 2012
Departed
Ontario, OR
Destination
Ontario, OR

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
52
Injuries
Fatal
Certificate
Private
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 3, Without waivers/limitations
Seat
Rear
Toxicology
Performed
Flight hours
2,517 total

Weather

Conditions
Visual (VMC) · Day
Wind
80° at 5 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
66 °F, dew point 45 °F
Altimeter
29.82 inHg
Observed at
KEUL, 28 nm away

Docket · 9

The files NTSB released with the investigation on April 8, 2015, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.2 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.