12 Sep 2010: Savage Savage-Cozy

12 Sep 2010: Savage Savage-Cozy (N9699) — Unknown operator

No fatalities • Aurora, OR, United States

Probable cause

The pilot’s failure to maintain control of the airplane following a loss of engine power in the traffic pattern; the cause of the loss of engine power for reasons that could not be determined because postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation.

— NTSB Determination

Accident narrative

On September 11, 2010, about 1740 Pacific daylight time, an experimental Savage-Cozy airplane, N9699, experienced a loss of engine power while in the traffic pattern, and the pilot attempted to land on a taxiway at the Aurora State Airport (UAO), Aurora, Oregon. The private pilot/owner operated the airplane under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. The pilot, the sole occupant, received serious injuries. The airplane sustained substantial damage after it collided with a hangar and came to rest inverted. Visual meteorological conditions prevailed for the local flight, which departed about 1730, and no flight plan had been filed.

According to a witness, while the airplane was in the pattern, he heard "strange noises" emanating from the engine. The pilot attempted to land the airplane on a taxiway; however, it struck the top of a hangar, and came to rest inverted near the hangar.

The National Transportation Safety Board (NTSB) Vehicle Recorders Division downloaded a global positioning satellite unit (GPS). The flight track indicated that the pilot completed one takeoff and landing, and was turning downwind on a second pattern. The track turns back toward the middle of the runway at a 45-degree angle prior to the airplane reaching the downwind leg. The airplane then turned right to a parallel track close to the runway. Near the end of the runway, the track turns left and stops at the accident site. Total elapsed time was about 11 minutes.

The owner did not return the NTSB Accident/Incident Report form 6120.1. There were no logbooks made available to the Federal Aviation Administration (FAA) or the NTSB. During the examination of the engine, the FAA inspector noted that the engine data plate had been removed, but appeared to be a Lycoming IO-360 engine.

An FAA inspector examined the airframe and engine following the accident. His detailed examination notes are part of the public docket.

The FAA inspector stated that the bottom spark plugs were automotive type with electronic ignition, which could not be tested due to damage to the ignition system. A magneto fired the top spark plugs, and it sparked at all posts when tested. A borescope inspection revealed no mechanical deformation on the valves, cylinder walls, or internal cylinder head. The inspector observed light corrosion on the cylinder walls, and normal deposits on the piston heads. The fuel shutoff valve was in the ON position. He observed no contamination of the oil screen. He identified no mechanical anomalies that would have precluded normal operation.

An aviation routine weather report (METAR) for UAO was issued at 1753 PDT. It stated: wind from 020 degrees at 3 knots; visibility 10 miles; sky clear; temperature 23/73 degrees Celsius/Fahrenheit; dew point 06/43 degrees Celsius/Fahrenheit; altimeter 30.06 inches of Mercury.

Contributing factors

  • Effect on operation

Conditions

Weather
VMC, wind 020/03kt, 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.