12 Sep 2009: GRUMMAN AMERICAN AVN. CORP. AA-1B — THOMAS JEFFREY N

12 Sep 2009: GRUMMAN AMERICAN AVN. CORP. AA-1B (N9682L) — THOMAS JEFFREY N

No fatalities • Creswell, OR, United States

Probable cause

A partial loss of engine power due to the malfunction of the engine's right magneto.

— NTSB Determination

Accident narrative

On September 12, 2009, about 1230 Pacific daylight time, a Grumman AA-1B, N9682L, nosed over during an attempted emergency landing soon after takeoff from Hobby Field, Creswell, Oregon. The private pilot and his passenger received minor injuries, and the airplane, which was owned and operated by the pilot, sustained substantial damage. The local Title 14 Code of Federal Regulations Part 91 personal flight was operating in visual meteorological conditions. No flight plan had been filed.

According to the pilot, soon after taking off from runway 33, the airplane's engine experienced a partial loss of power. The pilot was able to climb to about 300 feet above ground level (AGL), but the airplane would not climb any higher. The pilot then switched fuel tanks, tried the carburetor heat, and turned on the electric fuel pump, but none of those actions helped, and the airplane began to lose altitude. The pilot then tried switching to the right magneto alone, and then to the left magneto alone. While on the right magneto only, the engine appeared to "stumble badly" and appeared to be trying to kick back. The pilot then switched to the left magneto only, and the engine smoothed out, but there was insufficient power for him to maintain altitude, and the airplane continued to descend. At that point, because he was approaching some trees that he did not feel he would clear, the pilot made a forced landing in a rough open field. Although the touchdown was uneventful, during the landing roll the pilot realized that he was heading toward a manufactured home, and he did not think he would be able to stop before impacting it. He therefore pushed full forward on the control wheel and applied hard braking. As a result of those actions, the airplane's nose wheel dug into the rough terrain, and the airplane nosed over onto its back.

During a post-accident interview, the pilot stated that the airplane's engine had a longstanding history of occasional momentary power interruptions, especially at lower power settings upon entering the traffic pattern after a flight. He further stated that he felt it was probably a problem with one of the magnetos, and that he had occasionally experienced rough running of the right magneto during the pre-takeoff run-up check. In addition, he said that about a month prior to the accident, after returning from a long flight, he told his mechanic that the problem seemed to have gotten progressively worse. According to the pilot, the accident flight was the first flight after the mechanic checked the airplane, and when the mechanic inspected the engine he could not duplicate the problem on the ground, nor was he able to find any issue or anomaly that would have caused the problem.

On the day of the accident, the pilot started the engine, taxied to the run-up area, and then performed a magneto check. Although the engine ran smoothly on the left magneto, when the pilot selected the right magneto the engine ran rough. He therefore pushed the throttle to the full power position and leaned the engine. After doing this for a short period of time the engine started running smoothly, and it was able to achieve full static power. Then, according to the pilot, he pulled onto the runway and took off, with the engine running smoothly until just after liftoff.

After the accident, a Federal Aviation Administration (FAA) Airworthiness Inspector supervised an inspection of the airplane's engine and fuel delivery system. As part of that inspection process, both magnetos and their respective wiring harnesses were removed for further testing and teardown inspection. In addition, the carburetor was removed, disassembled, and inspected.

The disassembly and inspection of the carburetor did not reveal any anomalies or issues with the float, float valve, or accelerator pump, and there were no signs of contamination in either the carburetor bowl or the intake finger screen.

During the inspection of the magneto/spark plug system, the spark plugs were found to exhibit normal wear patterns, with no sign of shorting or contamination (the spark plugs in the number one cylinder were oil soaked because of the position of the engine while the airplane remained inverted). The magnetos were correctly set at 25 degrees before top dead center, and were securely fastened to their respective pads. The correct operation of the ignition switch was verified, and the "P" leads were in good conditions and securely fastened.

The magnetos, with their respective wiring harnesses, were taken to FligthCraft Portland, where, after replacement of the wire leads that were damaged during the accident sequence, each magneto was run on the test bench. During the test bench run, each magneto fired on all four cylinder positions.

After the test bench run, each magneto was disassembled, inspected, and tested. The disassembling technician rated the left magneto internal condition as "good," with no defects found, and all its internal components tested within serviceable limits. After disassembly, the right magneto was rated in "fair" condition, and during the testing sequence, the secondary coil windings failed the serviceable limits tests. According to the Slick Magneto Manual, the serviceable resistance limit of the secondary coil windings is 13,000 to 20,500 ohms. The right magneto secondary coil windings on the accident aircraft tested at 81,000 ohms. This result was achieved in an air-conditioned facility, and according to the technician, under high temperature conditions the resistance could be expected to become further out of serviceable limits. According to the pilot, the ambient temperature at the time of his takeoff was 82 degrees Fahrenheit.

No other anomalies or evidence of malfunctions that would have contributed to a loss of power were found.

Contributing factors

  • cause Malfunction
  • Contributed to outcome

Conditions

Weather
VMC, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.