LAX07FA026

In-flight structural failure of the horizontal stabilizer and wings for undetermined reasons.

Recorded radar data showed that the airplane was at 2,600 feet mean sea level cruising on course. It entered a gradual climb to 2,800 feet, leveled off, and then entered a 2,000-foot-per-minute rate of descent, which was followed by a profusion of primary radar targets around the secondary target. The wreckage was found within 1/2 mile of the last radar return with signatures consistent with an in-flight breakup. Several witnesses were found and none saw any adverse weather conditions in the area. One witness said the airplane had been in straight and level flight just prior to the breakup. The airframe was examined by Safety Board engineering and metallurgical specialists. Other than some assembly anomalies unrelated to the breakup, no evidence of any assembly contrary to design plans or material deficiency was found that related to the integrity of wings, stabilizer, or flight control surfaces. No evidence of fatigue, corrosion, or previous damage was found. The separation of the wings and horizontal stabilizer was in a downward direction. All observed fracture surfaces were overload, and no oscillatory loading of the control surfaces was apparent. Analysis of the radar data revealed that the climb and descent that occurred before the breakup did not require aggressive control inputs. The pitch angle would have changed about 0.4 degrees per second during the climb, and would have decreased about 0.75 degrees per second in the descent, with generated load factors ranging between 1.04 G and 0.88 G. A radar return is only received once every 4.5 seconds and contains uncertainties in both altitude and position measurements. Consequently, the radar may not have detected an abrupt control input that would overload the aircraft structure before the airplane position and altitude changed significantly. While there is no evidence of an abrupt control input or aggressive maneuvering in the available radar data, because of the limitations in the data, the possibility of an abrupt control input cannot be excluded. This airplane is very responsive in pitch control. One of the handling quality characteristics designed by the airplane's manufacturer is that movement of the control stick produces large and rapid changes in pitch attitude.

HISTORY OF FLIGHT On November 4, 2006, about 1139 Pacific standard time, an Aircraft Manufacturing & Development Co. (AMD), CH601XL SLSA, N158MD, experienced an in-flight breakup while cruising approximately 11 miles south-southeast of Yuba City, California. The special light sport airplane (S-LSA), referred to as a "Zodiac," was destroyed. The private pilot and passenger were killed. The pilot operated the airplane using the Federal Aviation Administration (FAA) registered name "Zodiac LSA, Inc." Visual meteorological conditions prevailed, and no flight plan was filed. The personal flight was performed under the provisions of 14 Code of Federal Regulations Part 91 and originated from Lincoln, California, about 1129. The pilot's son reported to the National Transportation Safety Board investigator that his father and he jointly operated the airplane. The son was listed as the president of Zodiac LSA, Inc., which was the name that the pilot and his son gave to their company. The family purchased the newly manufactured airplane directly from AMD in July 2006. Following their purchase and the son's introductory flight provided by AMD personnel, the son flew the airplane from AMD's factory in Georgia to his California home. The pilot's son also stated to the Safety Board investigator that in California he and his father flew the airplane together on several occasions. They became familiar with the airplane's operating characteristics, which according to the son were somewhat different than those of the other airplanes their family had owned or operated. The accident flight commenced after the pilot refueled the airplane at the Lincoln Regional Airport. Upon departure, the pilot headed in a westerly direction toward his intended destination, the Willows-Glenn County Airport, Willows, California. Willows is located about 63 miles west-northwest of Lincoln. The pilot's son reported that his parents planned to fly to Willows for lunch. While cruising toward Willows, about 10 minutes after takeoff and 16 miles west of Lincoln, five ground-based witnesses heard the airplane. Two of the witnesses also observed the airplane prior to the breakup. In summary, three of the auditory witnesses reported hearing a "bang" sound. One of these witnesses reported that for about 10 seconds prior to hearing the "bang," the engine was misfiring or sputtering. The sound increased in loudness and ended with a loud "bang." The fourth witness reported to a Sutter County Sheriff's deputy that he had been working in his field when he heard an airplane overhead. The witness opined that the airplane's engine was missing really badly. A few seconds later, as he was looking at it flying an estimated 800 to 1,200 feet above ground level, the airplane "blew up." The wings flew off, parts went everywhere, and the cockpit turned in circles as it descended. The fifth witness reported to the Safety Board investigator that he was a retired United States Air Force mechanic and was familiar with light airplanes. The witness was standing outside his residence, about 0.5-mile southeast of the accident site. In summary, the witness reported that he heard the sound of the airplane's engine, and it sounded fine. It was operating smoothly, its rpm sounded steady in that it was producing a constant tone, and it was not backfiring or sputtering. Then, the witness looked upward in the direction of the engine sound and immediately observed the airplane. The airplane was northwest of his location, and it was cruising in a northwesterly direction. Its wings were level. The airplane was not turning, climbing, or descending. The witnesses further stated that he could clearly see the airplane and saw no evidence of fire or smoke trailing from it. The fifth witness additionally reported that, after a few seconds, he stopped looking at the airplane and started talking on his cell phone. The witness estimated that he looked away from the airplane for about 5 seconds. Then, he heard the sound of the airplane's engine rapidly change rpm. Within about 0.5 seconds, it decreased and then increased, as if the pilot had retarded the throttle and then suddenly changed his mind and restored the power. When the rpm came back up, it did not sound like the engine had over revved. The tone sounded the same as before the power had decreased. The witness reported that immediately after the engine power came back up, he heard the sound of an explosion, which was followed by the sound of metal scraping. Thereafter, he saw what he believed were three distinctive large components falling. The components were the wings and the fuselage. The witnesses stated that it took perhaps 6 to 8 seconds for the airplane to fall, and it fell straight down. As the components descended, the fuselage spiraled around. There was no fire or smoke. The witness opined that, originally, he thought there had been a mid-air collision. However, there was no other aircraft in the area. PERSONNEL INFORMATION Pilot The pilot, age 79, held a private pilot certificate with an airplane single-engine land rating. The pilot's last aviation medical certificate was issued in the third class on February 16, 2005. The certificate bore the following limitation: "Must wear glasses for near and distant vision." Also, the certificate stated "Not valid for any class after February 28, 2006." (The FAA does not require that pilots operating a S-LSA under the accident flight conditions hold any class of medical certificate.) On the February 2005 medical certificate application form the pilot reported that his total pilot time was 1,184 hours. In previous years, when the pilot was issued aviation medical certificates, he reported the following total pilot times: 1,025 hours in February 2003, and 783 hours in February 2001. The pilot's personal flight record logbook indicates that he commenced flying the accident airplane on August 18, 2006. His logbook was endorsed by a certified flight instructor as having satisfactorily completed a flight review and "Zodiac checkout" in the accident airplane on October 28, 2006. According to the logbook, by the accident date the pilot's total logged flight time in all airplanes was about 1,281 hours. The Safety Board investigator's review of the airplane's utilization flight logbook found in the wreckage revealed that between August 18, 2006, and November 4, 2006 (accident date), the pilot was listed as having flown the airplane on nine dates for a total of 20.2 hours. More recently, between October 4, 2006, and November 4, 2006, the logbook indicated that the pilot flew the airplane on six dates for a total of 15.3 hours. Passenger Family members reported that the accident occurred during the wife's first flight in the airplane. The wife was not a pilot and had not received flight instruction. She had previously flown in other family-owned airplanes. The wife was reportedly in good physical condition, swam frequently, and was not handicapped. AIRCRAFT INFORMATION Manufacture The accident airplane was purchased as a factory-assembled S-LSA from AMD. The manufacture of the accident airplane began in Ontario, Canada. The accident airplane's components were then transported to Eastman, Georgia, where the airframe was assembled. The assembly included attaching the wings, stabilizers, flight controls, avionics, and engine. Certification AMD reported that the airplane, serial number 601-016S, was designed and manufactured in accordance with the American Society for Testing and Materials (ASTM) industry consensus standard for light sport aircraft. AMD's Director of Quality Assurance issued the following consensus standard certification statement to the FAA: "I hereby certify that aircraft serial number 601-016S complies with the Consensus Standard(s) identified on this statement of compliance and that the Manufacturer's Continued Airworthiness System will be adhe