Accident Details
Probable Cause and Findings
The loss of engine power due to the contamination of the fuel manifold valve, and the pilot's continued operation of the airplane with known maintenance discrepancies.
Aircraft Information
Registered Owner (Historical)
Analysis
1.1 History of the Flight
On February 8, 2007, at 1544 mountain standard time, a Cessna T210R, N6390U, collided with terrain and farm equipment during the takeoff-initial climb from runway 17 at Rexburg-Madison County Airport, Rexburg, Idaho. The pilot, who was also the registered owner of the airplane, was operating it under the provisions of 14 CFR Part 91. The private pilot, the sole occupant, sustained fatal injuries; the airplane was destroyed. Visual meteorological conditions prevailed and an instrument flight plan was filed. The flight was originating at the time and destined for Lincoln Regional Airport/ Karl Harder Field, Lincoln, California.
According to a family member of the pilot, the pilot traveled to Rexburg every 2 to 3 weeks to visit family members and oversee his private businesses in the area. He rented a hangar at Rexburg.
One witness reported seeing the airplane depart normally, and then he heard a "popping" sound and saw a trail of black smoke. The engine then lost power and the airplane began turning to the right. It appeared to the witness that the pilot was attempting to turn back to the runway. The airplane then dove down to the right, with the right wing impacting the ground. Flames quickly consumed the airplane.
Another witness, who was standing outside, stated that the airplane had just departed. He heard a pop noise from the airplane and then saw black smoke. The airplane began to lose airspeed and it turned to the right. The airplane then dove down to the right and the right wing impacted the ground first.
A witness was standing outside of his house and noticed the airplane because it appeared lower than normal. As he looked up, he noted smoke emitting from the airplane. The witness then stated that he "…heard the pilot shut off the engine and he was gliding into the wind." A few moments later he heard the airplane impact farm equipment machinery and saw smoke immediately.
1.2 Personnel Information
1.2.1 Pilot Information
The pilot held a private pilot certificate and was certified to fly in instrument conditions. His last medical was issued on December 5, 2006, and it was a third class. It held the limitation that the pilot must wear corrective lenses. The pilot reported 1,258 flight hours on his last medical application. The pilot's logbook was obtained from his family. It showed that the last entry was dated February 2, 2007. The pilot had accrued approximately 1,333 hours total flight time with 938 hours in the accident airplane. He logged about 60 hours over the 90 days preceding the accident.
1.3 Aircraft Information
1.3.1 General Aircraft History
The Cessna T210R was manufactured in 1986. The airplane had been involved in an accident on June 7, 1988, in Tampa, Florida. During a forced landing following a loss of engine power, the airplane impacted the top of an office trailer and guy wire before coming to rest on a roadway. A FAA Form 337 was filed on November 1, 1990, that showed repairs to the fuselage, wings, horizontal stabilizer, and elevators. According to Federal Aviation Administration aircraft registration records, the airplane was sold to the accident pilot on April 3, 2003.
The airplane was powered by a Teledyne Continental Motors TSIO-520-CE engine that was equipped with a McCauley D3A34C 410B three-bladed propeller. The engine was overhauled on July 29, 1999.
Following the pilot's purchase of the airplane in 2003, the annual inspections were completed by a local aviation maintenance technician (AMT) with inspection authorization, who lived near the pilot's California residence. The California AMT was interviewed regarding the maintenance that he performed on the airplane. The last annual inspection was completed in April of 2006. The California AMT had completed two other annual inspections on the airplane. Other than the annual inspections, the California AMT did not perform any maintenance on the airplane.
On April 30, 2004, the cylinders were replaced with cylinder kit 655470A4 at Lincoln Skyways, Lincoln, California, at a total tachometer time of 2,193.8 hours. According to the engine manufacturer, this was an incorrect installation for the TSIO-520-CE engine. The difference between this cylinder kit and the correct cylinder kit were the intake inserts and the machining on the cylinder heads. The intake inserts were tapered on the ordered kit. According to the engine manufacturer's representative, the tapered cylinders would allow for an increase in horsepower.
The last annual inspection was completed on April 18, 2006, at a total airframe time of 2,699.2 hours. During the last annual inspection, the California AMT noted in the engine logbook that cylinders 3, 2, 4, and 6 were at the minimum allowable compression and would be sent in for rework.
The California AMT noted that he had heard that the cylinders were replaced later in 2006. In the logbook endorsements, the California AMT noted that the fuel screens were cleaned. The California AMT stated that he pulled the fuel control valve/throttle body screen and the airframe fuel system screen located at the lowest point in the fuel system. Based on his recollection, he said that he did not find any major contamination in the screens.
On an aircraft owner's group website forum, the pilot expressed frustration regarding the maintenance that had been performed on the airplane's engine. In October of 2006, he noted that the incorrect cylinders had been installed on the engine (approximately 600 hours prior in April, 2004).
On November 12, 2006, at an airframe total time of time of 2,824.5, the cylinders were replaced with the correct cylinders by a maintenance facility in Rexburg.
The pilot requested that the Rexburg AMT change the airplane's engine cylinders due to oil consumption and low compression. The pilot left the airplane with the AMT for 5 days while he completed the work. During this time, the Rexburg AMT noted that the linkage for the fuel injection system was badly worn and loose, and that it needed to be repaired and calibrated. The pilot told the Rexburg AMT that he was aware of the problem and would look into it at a later date.
According to the Rexburg AMT, the pilot had experienced two other power loss events at Rexburg within the past 18 months. The first event occurred when the pilot departed and was in the initial climb out phase of his departure. During the initial climb, the airplane began trailing smoke and descending like it had lost engine power. At some point, power was restored and the pilot continued to California. When the pilot returned to Rexburg several weeks later, the Rexburg AMT asked him about the power interruption. The pilot told him that if he did not warm up the engine enough, or lean the mixture for takeoff, the engine would lose power because the mixture was too rich.
The Rexburg AMT further stated that in September of 2006, the pilot was taking several people, including a family member, for an airplane ride. The temperature was near freezing. During the takeoff roll, near the airplane's rotation point, the engine lost power. The engine then regained power and then it lost power again. At this point, the pilot was more than half way down the runway so he aborted the takeoff. He taxied back to runway 17 and departed normally.
The Rexburg AMT completed various routine maintenance items on the airplane. About two weeks prior to the accident, he changed the right vacuum pump and again advised the pilot about the worn fuel injection linkages. The pilot told him that the problem would be addressed at a later time.
A family member of the pilot was interviewed by the NTSB investigator. He reported that the engine had lost power on several occasions in the past, just following takeoff. The first time it happened was during takeoff, right after the landing gear lifted from the runway. The fuel pressure became high and the engine lost power. The pilot made an adjustment (the family member thought the adjustment was with the throttle), and power was restored. The first time it happened the family member was alarmed, but the pilot explained to him that it was due to "over-fueling" and it was something he was able to control.
Further review of the maintenance records did not show any maintenance on the fuel pump (serial number G18704B) or the fuel manifold valve (serial number G108703C) since the engine overhaul in 1999. During this overhaul, the fuel pump and manifold valve had been remanufactured.
1.3.2 Fueling
The airplane was fueled with 58.8 gallons of 100 Low Lead (100 LL) fuel (topped off) just prior to departure from Rexburg.
1.4 Meteorological Information
The closest official aviation weather reporting station was Rexburg. The following conditions were reported at 1553: visibility, 10 statute miles; sky condition, few clouds at 4,200 feet; temperature, 42 degrees Fahrenheit; dew point, 34 degrees Fahrenheit; wind from 210 degrees at 9 knots; and altimeter, 30.05 inches of Mercury.
1.5 Wreckage and Impact Information
The National Transportation Safety Board investigator, a Federal Aviation Administration inspector, and a representative from Cessna Aircraft Company responded to the accident scene on February 9.
The airplane came to rest upright in a farm machinery yard located off the west- southwest end of runway 17 at Rexburg Airport and was extensively damaged from fire and impact. The main wreckage was 600 feet from the end of the runway. The airport was separated from the farm machinery yard by a paved road that generally ran from north to south. The first identified point of contact was a gouge in the soil on the east side (airport side) of the road, containing fiberglass fragments and paint chips. Moving west-southwest approximately 11 feet, investigators identified several scrape marks on the paved surface of the road. From the scrape marks, two curled gouges, located 3 ...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# SEA07FA061