WPR10FA009

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.

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.

HISTORY OF FLIGHT On October 8, 2009, about 1305 Pacific daylight time, a Piper PA-12, N2087C, impacted the terrain after lifting off from Runway 28 at Skagit Regional Airport, Burlington, Washington. The private pilot, who was the sole occupant, was killed by the accident sequence, and the airplane, which was owned and operated by the pilot, sustained substantial damage. The local 14 Code of Federal Regulations Part 91 flight took place in visual meteorological conditions. No flight plan had been filed. According to family members and friends of the pilot, he began a near total rebuild/restoration of the airplane about six months prior to the accident. Although most of the work was done at his home, since the project was nearly completed, he brought the airplane to Skagit Regional Airport on a trailer sometime within the two weeks prior to the accident (the exact date was not determined). Individuals who talked with the pilot after the airplane was brought to the airport said that his plan was to complete what remained of the rebuild there at the airport, and then to have it inspected and signed-off by an airframe and powerplant (A&P) mechanic with Inspection Authorization (IA) who had helped him with project sign-offs in the past. According to the aforementioned A&P/IA mechanic, the pilot talked to him about doing a pre-signoff inspection on a specific weekend near the end of September, but he was not available then, and suggested the subsequent weekend instead. Reportedly, the pilot indicated he did not want to wait that long, and that he would try to get another A&P/IA to do the inspection/signoff sooner. The pilot then told the mechanic that if it turned out he needed him to do the signoff he would get back in touch with him; which he had not done as of the day of the accident. There were no records indicating a sign-off inspection had been completed by some other A&P/IA. It could not be determined what time the pilot arrived at the airport on the day of the accident, but about 90 minutes before he taxied out to the runway, he stopped his truck in front of another hangar and asked the two pilots at that location, neither of which knew him personally, if they needed help with anything. They both responded that they did not need any help, and then the pilot of the PA-12 asked them if they would be willing to help him briefly with his airplane. They both said they would be glad to help him, and they then walked over to his hangar. Once there, he asked one of them to hold a piece of metal tubing (believed to be a fuel tank vent tube) while he went up on the top of the wing and connected it to the fuel tank. In order to make the connection, the pilot removed the fuel tank cover panel from the top of the wing. Once the task was completed, the PA-12 pilot chatted for awhile with the other two pilots, telling them about the many other airplanes that he had restored, and a little bit about N2087C. He showed them his extended baggage compartment, and talked briefly about some of the other things he had been doing to the airplane. According to these two pilots, he said that his goal for that day was to do an engine run on the recently overhauled engine. He did not say anything about doing a taxi test or a test flight that day, and both of the pilots said that they were surprised when the pilot later taxied to the runway. Their surprise was based upon the fact that they had seen many unsecured panels and other items that they felt still needed to be completed prior to any IA signoff or flight. About 15 minutes after the two pilots got back to their hangar; they heard the engine of the PA-12 start up and then run for about four to five minutes, at what sounded to them like a medium power setting. They said that during the engine run they did not hear any changes in the power setting, or any sound change that would be consistent with a carburetor heat or magneto check. After the engine stopped running, neither of the pilots heard it start again for about 15 minutes. Then, very soon after hearing the engine start up a second time, the two pilots saw the PA-12 pilot taxi the airplane out to the run-up area near the approach end of Runway 28. Although their view of the run-up area was partially blocked by a parked airplane, they said that once there, the PA-12 pilot either stopped very briefly, or did not stop at all prior to pulling onto the runway. Regardless of whether he stopped or not, they were sure they did not hear him do any kind of an engine run-up in that area before taking the runway. Soon after the airplane pulled onto the runway, the engine was advanced to what witnesses thought sounded like full power, and then the airplane made a "very short" takeoff roll before lifting off. Most of the witnesses thought the initial liftoff looked normal, but 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 (agl). Then, with the engine still at what sounded like full power, the airplane slowed, fell off on the right wing, and descend near vertically into the grass-covered terrain near the side of the runway. According to the witnesses, at the moment of impact it still sounded like the engine was at full power. Reportedly, immediately after the impact, the airplane "bounced" about 20 feet to the north and fell over onto its back. Soon after the impact, a small fire started in the area of the carburetor, but it was quickly put out by two individuals from a nearby fixed-base operator (FBO) who ran to the scene with extinguishers. PERSONNEL INFORMATION The 69 year old private pilot held ratings for Airplane Single Engine Land (ASEL) and Airplane Single Engine SEA (ASES). His last FAA medical, a class 3, was completed on May 5, 2009. At the time of the medical he had accumulate about 3,500 hours of flying time, with about 20 of those hours being in the six months prior to the date of the medical. No records were found to indicate when he had completed his last flight review. METEOROLOGICAL INFORMATION The 1256 aviation surface weather observation (METAR) for Skagit Regional Airport recorded winds from 320 degrees at six knots; a visibility of eight statute miles; few clouds at 1,000 feet; a broken ceiling at 12,000 feet; a temperature of 12 degrees Celsius; a dew point of 08 degrees Celsius; and an altimeter setting of 30.17 inches or mercury. WRECKAGE AND IMPACT INFORMATION The airplane impacted the level grassy terrain about 50 feet beyond the north edge of Runway 28, about 1,100 feet west of the Runway 28 approach threshold. All of the aircraft's structural components were present at that location. The engine and the engine compartment firewall had been forced directly aft into the forward part of the pilot compartment. The crankshaft propeller flange had fractured from the crankshaft, and the propeller, which was still attached to the flange, was located at the point of impact, which was about 15 feet south of the main wreckage. The leading edges of both wings were crushed almost directly aft along their entire span, with the outboard one-half of the right wing being crushed both aft and downward. Both of the left wing lift struts were bent near their midpoint, and right wing forward lift strut was bent near its midpoint. The top half of the rudder and vertical stabilizer were bent to the right, and the entire span of the horizontal stabilizer was twisted about ten degrees in the clockwise direction (looking from the rear). The remainder of the airplane's structure showed little damage. The Investigator-In-Charge conducted a flight control continuity check, and determined that there was connective continuity and correct function within the aileron system, the rudder system, and the variable–pitch trimable horizontal stabilizer. The stabilizer trim indicator on the left side of the pilot compartment was found in a