- Date
- October 14, 2015, 11:45 local (18:45 UTC)
- Place
- Battle Ground, WA
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Takeoff
- Aircraft
- N533RCChristopher Tom Kitfox 5
- Defining event
- Takeoff: Loss of engine power (total)
- Weather
- Visual (VMC) · Day
- Status
- Completed · report November 6, 2019
- Report
- Approved by Office Director
- NTSB office
- Western Pacific Region
- Parties
- Federal Aviation Administration
- FAA report
- 20151014016949A
- Case key
- 92174
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The total loss of engine power for reasons that could not be determined because postaccident examination of the engine revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation.
Findings · 2
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
The private pilot reported that, shortly after takeoff from his grass airstrip for a local, personal flight, the engine began running roughly but that it then regained full power. The airplane climbed to about 300 ft above ground level, at which point, the engine began running roughly again, and it then lost all power. When the pilot realized that the airplane could not reach a nearby airport, he maneuvered the airplane back toward the grass airstrip because there were multiple fields in the area. As the pilot maneuvered around trees and fences for the forced landing, the airplane impacted a fence, nosed over, and then came to rest inverted. The pilot had refueled the airplane with automotive fuel from a container. The pilot stated that, although he drained fuel from the fuel tanks during the preflight inspection and found no contaminants, he thought that there might have been some water in the fuel line. Postaccident engine examination revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. The reason for the loss of engine power could not be determined.
Factual narrative
On October 14, 2015, about 1145 Pacific daylight time, an experimental amateur built Christopher Kitfox 5 airplane, N533RC, collided with a fence following a loss of engine power during the takeoff climb from a private grass strip near Battle Ground, Washington. The private pilot and passenger were not injured; the airplane sustained substantial damage. The airplane was registered to and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed at the time of the accident, and no flight plan was filed. The local flight was originating at the time of the accident. According to the pilot, after take off from his grass airstrip, he made a left 45o climbing turn when the engine began to run rough, then it regained full power. The airplane climbed to about 300 ft above ground when the engine ran rough again, then lost power. The pilot realized that he did not have sufficient altitude to make it to nearby Goheen Airport (W52), Battle Ground so he turned back toward the departure airstrip as he knew there were multiple open fields in the area. As he maneuvered around trees and fences for a forced landing, the airplane subsequently collided with a fence and nosed over, coming to rest inverted. The pilot stated that he had drained fuel during the preflight check and reported no water present; however, he believed that there may have been a "slug of water" in the fuel line. A Federal Aviation Administration (FAA) inspector examined the engine. The pilot had fueled the airplane from a nearby gas station. The fuel is placed in a plastic cylindrical gas container and then the airplane is refueled. A visual inspection of the fuel revealed no contamination. The sample of fuel recovered from the filter housing was opaque and cloudy compared to the sample taken from the airplane's header tank. The FAA inspector reported that after cleaning the oil-soaked spark plugs, and installing a fuel filter, he checked the fuel pressure of both pumps at 48 psi, which fell in the normal operating range of the fuel pump. The engine was then started and ran normally, except for a vibration, which was attributed to the broken propeller blades.
Aircraft
- Registration
- N533RC
- Reported as
- Christopher Tom Kitfox 5
- Category
- Airplane, amateur-built
- Serial number
- 0127
- Built
- 2001
- Airframe hours
- 342
- Engine
- Firewall Forward CAM 125, 125 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Special, Experimental (Special)
- Last inspection
- Condition · June 9, 2015 · 27 hours before
- Departed
- NA · Battle Ground, WA
- Destination
- NA · Battle Ground, WA
- Airport
- NA · Private Strip, runway NA, 2,000 × 40 ft, grass/turf
- Equipment
- Electronic flight bag or handheld device, Handheld GPS
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 51
- Injuries
- None
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 3, With waivers/limitations
- Last flight review
- June 5, 2013
- Seat
- Left
- Restraint
- 4-point
- Flight hours
- 288 total · 185 in this make and model
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 20° at 8 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 61 °F, dew point 48 °F
- Altimeter
- 30.13 inHg
- Observed at
- SPB, 250 nm away
Docket · 4
The files NTSB released with the investigation on April 18, 2019, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.6 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.