WPR10LA456 · Savage Savage-Cozy
Savage Savage-Cozy · Accident: loss of engine power (partial) on approach
From Aurora State Airport (UAO) to Aurora State Airport (UAO)
Event
- NTSB case
- WPR10LA456
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Savage Savage-Cozy
- Aircraft type
- Savage SAVAGE-COZY
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N9699
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Aurora State Airport (UAO), Aurora, ORTo Aurora State Airport (UAO), Aurora, OR
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern downwind
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of engine power (partial)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10LA456
- Event ID
- 20100913X44246
- Case number
- WPR10LA456
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2010-09-12.
- API snapshot SHA-256: b40b1ee8134e33efb33a50bcacce59360d871ae6a8b755510114547c1b45825b; retrieved 2026-09-15T15:11:10.809Z.