Amateur-built AVID FLYER accident near White City, Oregon, July 13, 2013
On July 13, 2013 at about 11:30 pm local time, a 1990 amateur-built AVID FLYER, registered N399Q, was substantially damaged in an accident during enroute (climb to cruise) near White City, Oregon (Beagle Skyranch airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Excessive engine operating temperature, which resulted in engine failure and a forced landing. The reason for the excessive engine operating temperature could not be determined during postaccident engine examination.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 13, 2013 · about 11:30 pm local time · cases in 2013
- Place
- White City, Oregon · Beagle Skyranch · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built AVID FLYER, built 1990
- Registration
- N399Q · registry record · serial 399
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that he departed in the experimental amateur-built airplane and that, during climbout, he noticed that the engine coolant temperature was above normal and continuing to rise, so he initiated a turnback toward the airport. The pilot retarded the throttle slightly and leveled off, but the temperature continued to rise. The airplane crossed the runway midfield and then entered the downwind leg. The engine rpm dropped, and the engine began running roughly and then quit as the pilot began turning the airplane onto the base leg. The pilot recognized that he would be unable to reach the runway, so he selected a field short of the threshold for a forced landing. The pilot intentionally stalled the airplane a few feet above the ground to touch down sooner because he wouldn't be able to clear a fence ahead. The airplane landed hard, and the main landing gear bungees failed. The airplane then struck the fence. The investigation could not determine why the engine coolant operating temperature reported by the pilot exceeded the engine manufacturer's maximum operating temperature or the accuracy of the installed engine temperature indication system. However, the timing of the pilot's observation of unusual coolant temperature and the subsequent loss of engine power support an engine overtemperature-related problem; postaccident engine examination was unable to determine the reason for the coolant overtemperature.
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
- Powerplant sys/comp malf/fail during enroute (climb to cruise)
- Loss of engine power (total) during enroute (climb to cruise) defining event
- Off-field or emergency landing during enroute (climb to cruise)
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
- Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng liquid cooling › Malfunction other cases naming the engine
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 146 hours in all; 23 in this make and model
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 578.4 hours
- Last inspection: annual inspection, March 6, 2013; 1 hours since
- Maximum gross weight: 941 lb
- Seats: 2
- Landing gear: fixed
- Engine: Rotax 582 (piston); 152 hours total
The flight
- Departed from: OR96 White City OR
- Destination: OR96 White City OR
- Flight plan: not recorded
Weather at the time
- Light: daylight
- Wind: from 290° at 10 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 90°F (32°C), dew point 45°F (7°C)
- Altimeter: 29.90 inHg
- Observation at 11:53 pm from MFR, 9 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on July 23, 2015. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Record of Conversation - Pilot | PDF, 2 pages | View Download |
| 3 | Jackson County Sheriff’s Office Report | PDF, 6 pages | View Download |
| 4 | Site and Airplane Information | PDF, 8 pages | View Download |
| 5 | Metars | PDF, 1 page | View Download |
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
- N399Q on the register today · the tail number may have moved to another aircraft since
- Engine: Rotax 582 62 aircraft carry this series today · as the NTSB recorded it
- Beagle Sky Ranch Airport · nearest airport
- Accidents and incidents in Oregon 1,864 since 1982 · 279 in the last ten years
- Oregon 6,998 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR13LA363.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.