Plane crash map Find crash sites, wreckage and more

N399Q accident description

Oregon map... Oregon list
Crash location 42.538889°N, 122.903889°W
Nearest city White City, OR
42.437348°N, 122.858930°W
7.4 miles away
Tail number N399Q
Accident date 13 Jul 2013
Aircraft type Quarnoccio Avid Flyer
Additional details: None

NTSB Factual Report


On July 13, 2013, about 1630 Pacific daylight time, an experimental amateur-built Avid Flyer light sport airplane, N399Q, was substantially damaged during an off-airport forced landing following a complete loss of engine power near Beagle Skyranch airport (OR96), White City, Oregon. The private pilot/owner was not injured. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no flight plan was filed for the flight.

According to the pilot, the preflight inspection, engine start, taxi-out, run-up, takeoff and initial climbout were all normal. The departure was conducted to the south from the unpaved runway at the non-towered airport. After takeoff, the pilot turned the airplane to the left (east) and continued climbing. He then noticed that the engine coolant temperature was rising faster than expected, and initiated a turnback to the airport. At an altitude of about 750 feet above the ground, he noticed the coolant temperature was still rising, so he reduced the power, and crossed over the airport in preparation for entering a left downwind leg to land back on the runway to the north (since hills precluded landing to the south). When the airplane was abeam of the pilot's target landing location on the runway, the engine rpm decreased from 6,000 to about 3,500 rpm, and then the engine ceased operating. The pilot recognized that he would be unable to reach the runway, and selected a field as his new landing site. When the airplane was on short final, the pilot recognized that the airplane would not clear a double row of steel post fences that bordered the field perpendicular to the final approach path. The pilot "stalled" the airplane to get it on the ground quickly, and "skidded" into the fence.

Subsequent to the accident, the airplane was recovered by the pilot and some acquaintances, who placed it on a trailer and returned it to the pilot's home airport.


According to the pilot, he held a private pilot certificate, with an airplane single-engine land rating. He reported that he had a total flight experience of about 146 hours, with approximately 23 hours in the accident airplane make and model.

His most recent flight review was completed in August 2012, and his most recent Federal Aviation Administration (FAA) third-class medical certificate was issued in December 2012.


The airplane was manufactured in July 1990. It was equipped with a Rotax 582 series engine. The accident pilot purchased the airplane in the fall of 2009, and thereby became its fourth owner.

The cooling system was a pressurized liquid (water and antifreeze) type, with an integrated water pump and a radiator. According to the Rotax engine installation manual, coolant flow rate should be between 60 and 70 liters per minute, and the coolant in the system must be "under pressure" in order to prevent pump cavitation. System pressurization was to be accomplished by means of a pressure cap with a release pressure of approximately 0.9 bar (13 psi). The system included an overflow bottle, and the installation manual specified monitoring of this bottle as a means of ensuring correct cooling system pressurization and operation. The manual stated that the average coolant operating temperature should be between 60 and 80 degrees C (140 to 175 degrees F), and that the maximum allowable coolant operating temperature was 80 degrees C.

Maintenance records indicated that the most recent annual condition inspection was completed on March 6, 2013. At that time the hour meter indicated 578.4 hours, and the engine had a total time in service of 126.3 hours. The hour meter indicated 581.8 hours after the accident.

Separate post impact examinations of the airplane by the pilot and an FAA inspector did not reveal any reasons for the elevated coolant temperature and the engine failure.


The 1653 automated weather observation at Rogue Valley International airport (MFR), Medford, located about 9 miles south of the accident site, included winds from 290 degrees at 10 knots, visibility 10 miles, clear skies, temperature 32 degrees C, dew point 7 degrees C, and an altimeter setting of 29.91 inches of mercury.


According to FAA information, OR96 was a private airstrip, equipped with a single turf runway designated 15/33. The runway measured 3,000 feet by 130 feet, and the airport elevation was listed as 1,436 feet above mean sea level.


The airplane came to rest upright. The airplane sustained damage due to the pilot's intentional stall and the airplane's impact with the steel pole fence that extended perpendicular to the flight path. Damaged components included the landing gear, propeller, engine cowling, right wing struts, and left wing tip.

In his post accident written statement to the NTSB, the pilot reported that the "normal" coolant temperature during climb was 195 degrees F. That value is 20 degrees F above the maximum allowable coolant temperature specified in the engine manufacturer's installation manual. The investigation did not verify that the engine cooling system was equipped in accordance with the engine manufacturer's installation manual, and did not verify the integrity or functionality of the entire cooling system. The accuracy of the installed engine coolant temperature indicating system was not determined. The reason for the differences between the pilot's reported normal coolant temperature of 195 degrees F, and the maximum allowable coolant temperature specified by the installation manual (175 degrees F), was not determined.

NTSB Probable Cause

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.

(c) 2009-2018 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.