Accident Piper PA-12 Super Cruiser N2087C,
ASN logo
ASN Wikibase Occurrence # 68661
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Thursday 8 October 2009
Time:13:05
Type:Silhouette image of generic PA12 model; specific model in this crash may look slightly different    
Piper PA-12 Super Cruiser
Owner/operator:Private
Registration: N2087C
MSN: 12-3497
Engine model:Lycoming O-235-C
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Substantial
Category:Accident
Location:Skagit Regional Airport, Burlington Washington -   United States of America
Phase: Take off
Nature:Private
Departure airport:Burlington, WA (KBVS)
Destination airport:Burlington, WA (KBVS)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The pilot was nearing the completion of a rebuild/restoration of the airplane, but it had not yet been inspected and signed off by a mechanic with an Inspection Authorization. On the day of the accident the pilot was planning on doing a test run of the recently overhauled engine. Witnesses reported that the pilot ran the engine for about five minutes and then shut it down. Then, about fifteen minutes later, he started the engine again and taxied out to the active runway. Without performing a magneto or carburetor heat check, the pilot pulled onto the runway and added what sounded to witnesses like full power. The airplane then made a "very short" takeoff roll before lifting off. Although the liftoff appeared normal to the witnesses, soon thereafter the nose of the airplane pitched up to a near-vertical attitude. It then climbed to an altitude of between 150 to 200 feet above ground level. Then, with the engine still at what sounded like full power, the airplane slowed, fell off on the right wing, and descended near vertically into the grass-covered terrain near the side of the runway. A postaccident teardown inspection found that the elevator control cables had been connected to the incorrect elevator control horns, resulting in a reversal of control inputs at the elevator. A mechanic who had signed off many of the pilot's previous rebuild projects stated that he had found reversed control cables on two other airplanes the pilot had completed. The mechanic also stated that the pilot had done "high speed taxi tests" on a number of other rebuilt airplanes prior to the time they were inspected and signed off. The mechanic had warned the pilot about the dangers of doing so, but the pilot had continued the practice.

Toxicology testing of specimens from the pilot was consistent with the recent use of a medication containing diphenhydramine, an over-the-counter impairing antihistamine. Family members described a 10-year history of a skin condition consistent with chronic urticaria (hives) that resulted in severe recurrent itching and which had frequently occurred while the pilot was working on aircraft. The pilot had not indicated any conditions or medication use at the time of his last Application for Airman Medical Certificate, less than 5 months prior to the accident. Although the pilot likely would have had no opportunity to recover the aircraft once it became airborne, it is possible that impairment from the use of diphenhydramine or distraction from chronic urticaria contributed to the pilot’s failure to correctly rig the elevator cables. However, the investigation could not determine whether impairment or distraction played a role in the accident.
Probable Cause: The pilot's in-flight loss of control due to his failure to correctly connect the elevator control cables during the restoration/rebuild of the airplane. Contributing to this accident was the pilot's decision to perform a high-speed taxi test prior to having the airplane inspected by a certificated mechanic, which resulted in inadvertent flight.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: WPR10FA009
Status: Investigation completed
Duration: 7 months
Download report: Final report

Sources:

NTSB
FAA register: http://www.goskagit.com/home/article/small_plane_crashes_at_skagit_county_airport1/
https://www.seattlepi.com/local/6420ap_wa_small_plane_crash.html?source=mypi
http://komonews.com/news/local/63789372.html

http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=2087C&x=27&y=12
https://www.ntsb.gov/aviationquery/brief.aspx?ev_id=20091009X21520&key=1

Location

Revision history:

Date/timeContributorUpdates
08-Oct-2009 20:57 cmlynn Added
09-Oct-2009 02:31 RobertMB Updated
09-Oct-2009 22:07 Geno Updated
28-Oct-2011 02:38 Geno Updated [Time, Operator, Source, Narrative]
21-Dec-2016 19:25 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
02-Dec-2017 17:07 ASN Update Bot Updated [Operator, Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org