eFlight
Accidents · NTSB WPR10LA456 · Final report

Amateur-built Savage-Cozy accident near Aurora, Oregon, September 12, 2010

On September 12, 2010, a amateur-built Savage-Cozy, registered N9699, was substantially damaged in an accident during approach (VFR pattern downwind) near Aurora, Oregon (Aurora State Airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 12, 2010 · cases in 2010
Place
Aurora, Oregon · Aurora State Airport · cases near this airport · map
Type
Accident
Injuries
1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Amateur-built Savage-Cozy
Registration
N9699 · no longer on the register · serial CC1017
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

According to a witness, while the airplane was in the traffic pattern, he heard "strange noises" emanating from the engine. A plot from an onboard global positioning system unit indicated that the airplane had completed one takeoff and landing, and a second orbit of the traffic pattern had occurred. The track then showed the airplane turn back toward the middle of the runway at a 45-degree angle before the airplane reached the downwind leg. The track showed the airplane then turn right to parallel the runway. Near the end of the runway, the airplane turned left and crashed. Total elapsed time was about 11 minutes. The pilot was likely attempting to land on a taxiway due to the loss of engine power described by the witness; however, the airplane struck the top of a hangar and came to rest inverted. A postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of engine power (partial) during approach (VFR pattern downwind) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during landing

The NTSB's findings

  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • Environmental issues › Physical environment › Object/animal/substance › Residence/building › Effect on operation

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 145 hours in all; 28 in this make and model; 28 in the last 90 days; 53 as pilot in command
  • Last flight review: May 27, 2010
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Landing gear: retractable
  • Engine: Lycoming IO-360 (piston); 0 hours total

The flight

  • Departed from: UAO Aurora OR
  • Destination: UAO Aurora OR
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 020° at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 73°F (23°C), dew point 43°F (6°C)
  • Altimeter: 30.05 inHg

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

7 documents, released by the NTSB on July 31, 2012. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR10LA456.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.