WPR17LA116

NTSB accident investigation · Extra Flugzeugbau EA 300/S · Pendelton, OR · May 20, 2017

Accident · No injuriesLimited investigationFinal report
Date
May 20, 2017, 14:59 local (21:59 UTC)
Place
Pendelton, OR
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N68PWExtra Flugzeugbau EA 300/S
Defining event
Takeoff-rejected takeoff: Part(s) separation from AC
Weather
Visual (VMC) · Day
Status
Completed · report April 8, 2019
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
FAA FSDO
FAA report
20170520007909A
Case key
95272

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 failure to follow checklists to ensure the canopy was secured before takeoff.

Findings · 4

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.

Doors: passenger/crew doorsAircraft › Aircraft structures · Incorrect use/operationExtra Flugzeugbau EA 300/S: 1 caseAll aircraft: 86 casesProbable cause
Object/animal/substance: sign/markerEnvironmental issues › Physical environment · Contributed to outcomeExtra Flugzeugbau EA 300/S: 1 caseAll aircraft: 214 cases

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

The private pilot reported that, shortly after starting the takeoff roll for the local flight, the canopy lifted up and then separated from the airplane. The airplane subsequently veered left, exited the runway, and struck an airport runway sign during the aborted takeoff, which resulted in substantial damage to the canopy and wing. Postaccident examination of the airplane did not reveal any anomalies with the canopy, canopy attachment bolts, mounting bolt holes, latches, or locking mechanism that would have precluded normal operation. Two normal checklists (the Before Starting Engine and Taxi checklists) in the airplane's pilot's operating handbook call for the pilot to check that the canopy is closed and locked before takeoff. The pilot stated that he did not remember checking that the canopy was locked and also stated that he was fairly sure that it was not latched; thus, it is likely that the pilot did not ensure that the canopy was properly secured before takeoff.

Factual narrative

On May 20, 2017, about 1459 Pacific daylight time, the canopy of an experimental Extra Flugzeugbau EA 300/S airplane, N68PW, departed from the airplane during takeoff roll from Eastern Oregon Regional Airport (PDT) Pendleton, Oregon. The private pilot was not injured. The airplane was substantially damaged to the canopy and wing. The airplane was registered to Precision Aerosports LLC and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no flight plan had been filed for the local flight that was originating at the time. During a telephone interview with a National Transportation Safety Board investigator, the pilot stated that shortly after the start of the takeoff roll, the canopy began to lift up and separate from the airplane. The airplane subsequently veered left, exited the runway, and struck an airport runway sign, during the aborted takeoff. The pilot reported that he did not remember checking that the canopy was locked and was fairly sure it was not latched. The pilot reported no mechanical malfunction or failure that would have precluded normal operation. Postaccident examination of the airplane revealed no anomalies with the canopy, canopy attachment bolts, mounting bolt holes, latches, or locking mechanism. Additionally, no cracking or corrosion was observed. The canopy is manufactured in one section and is operated manually by the pilot and opens by lifting it to the right. The canopy has fore and aft interior locking handles, located on the left side of the canopy frame, that must be squeezed together to unlock the canopy. Both locking handles must be in the outward position when locked. A placard located near the locking handles of the cockpit indicates the unlock and locked positions. The airplane Pilot's Operating Handbook contains a checklist item, to close and lock the canopy, both in the Before Starting Engine, and the Taxi, checklists. Further, a caution about the canopy states: "handles of the lock mechanism must be in opposite position indicated with a red line on the canopy frame. Check gap between canopy frame and fuselage fairing!"

Aircraft

Registration
N68PW
Reported as
Extra Flugzeugbau EA 300/S (S)
Category
Airplane
Serial number
030
Built
1999
Airframe hours
2,398.89
Engine
Lycoming AEIO-580-X, 350 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Special, Experimental (Special)
Last inspection
Annual · May 7, 2017
Departed
PDT · Pendelton, OR
Destination
PDT · Pendelton, OR
Airport
PDT · Eastern Oregon Rgnl At Pendlet, runway 29, 5,581 × 100 ft, asphalt
Equipment
None

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
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Last flight review
June 25, 2017
Seat
Single
Restraint
5-point
Flight hours
590 total · 133 in this make and model · 540 as pilot in command · 11 in the last 90 days · 3 in the last 30 days · 2 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
290° at 5 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
72 °F, dew point 46 °F
Altimeter
30.06 inHg
Observed at
PDT

Docket · 2

The files NTSB released with the investigation on February 12, 2019, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.1 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.