WPR15LA235
2015-08-06 · Bellingham, Washington, United States · Minor · 1 aircraft · Status: Completed
Airport BLI
N917AB has since been reassigned. It is now registered to a different aircraft (SIAI-MARCHETTI S.205/22R), which was not involved in this event.
Aircraft involved
Probable cause & findings
A partial loss of engine power for reasons that could not be determined because postaccident examination revealed no mechanical malfunctions or anomalies that would have precluded normal operation.
Factual narrative
On August 6, 2015, about 2000 Pacific daylight time, an experimental amateur-built Cleveland Nieuport #11 airplane, N917AB, experienced a partial loss of engine power during a maintenance check flight and landed short of a closed runway at Bellingham International Airport, Bellingham, Washington. The commercial pilot sustained minor injuries. The airplane was substantially damaged. 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, and no flight plan had been filed for the local flight, which was originating at the time of the accident.The pilot reported that the engine had just been replaced during a recent condition inspection. Prior to the flight, the engine had been run 5 times, which included the initial run, test run, engine tuning, taxi test and subsequent high-speed taxi test. The pilot stated that he intended to fly over the airport to remain within gliding distance of the runway. Just after takeoff from runway 16, at an altitude of 700 ft above ground level, a reduction in engine rpm was observed despite the throttle being at full power. The pilot noted that the engine rpm was still decaying, that he heard no unusual sounds from the engine, and that it was not running rough. The pilot further reported that he notified the tower controller that he was having engine problems and was subsequently cleared to land runway 34. While the engine rpm continued to decrease, the pilot realized that he was unable to reach runway 34 and attempted to land on a closed runway, while observing that the engine rpm had decreased from 3,000 to 2,500, then down to 2,000, which was an rpm setting for a power off approach to landing. The pilot then observed a stand of trees directly in front of his position, at which time he maneuvered to avoid striking them, along with an adjacent airport perimeter fence. Subsequently, the airplane landed hard and nosed over in a grassy area short of the runway. The airplane was powered by a Hummel, 76 HP, Volkswagen 2180 cc engine with dual weber carburetors, and a single point electronic ignition system. Examination of the airplane was performed by the pilot, an airframe and powerplant mechanic, and a Federal Aviation Administration (FAA) inspector. The FAA inspector reported that the examination revealed that the fuel system appeared to be in operable condition. Further examination revealed that the fuel tank was void of any fuel, and that a vent line at the top of the fuel tank was separated from the tank as a result of the accident. The fuel lines were intact to the fuel pump, which was a stock Volkswagen style fuel pump. The pump was removed and operated normally when actuated by hand. The carburetor throats were clear and clean. The throttle linkages were not damaged and moved freely. The idle and full throttle stops were intact, and the throttle linkage moved to both stops. The Volkswagen style ignition system featured a Bosch distributor with stock ignition wires and spark plugs. In addition, the ignition coil was also stock. The FAA inspector stated that the original points and condenser were replaced when the engine was equipped with an electronic type automotive ignition system. The ignition system revealed evidence of damage. The engine was rotated in the direction of rotation and the distributor shaft rotated correctly with a slight amount of delay. The drive gear revealed some backlash, which according to a mechanic, was normal for the engine. Engine valve train continuity was established throughout the engine. The FAA inspector reported that they did not observe any evidence of mechanical anomalies with the airframe or engine. The commercial pilot reported that the accident flight was the first flight following replacement of the experimental engine. During takeoff/initial climb, the engine began to lose power, so he attempted to land on the runway opposite the departure runway, likely due to a large body of water straight ahead. During the 180° turn, the pilot realized that the airplane would not reach the runway, so he decided to land on one of the airport's closed runways. The airplane landed short of that runway and nosed over. A postaccident examination of the engine revealed no evidence of any preexisting mechanical malfunctions that would have precluded normal operation. The reason for the partial loss of engine power could not be determined. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Not determined-Not determined-(general)-(general)-Unknown/Not determined - C
Verbatim from NTSB's published report. Source file
NTSB_2015_WPR15LA235.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (maintenance). All research papers
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA) From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2026 · Article (Reliability Engineering & System Safety) Understanding human error in military aviation maintenance: The role of Performance shaping factors, cognitive workload and error orientation
- Semantic Scholar 2025 · Article (Applied Sciences) Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Semantic Scholar 2024 · Article (Defence Science Journal) Modelling of Human Factors in Aviation Maintenance Using HFACS ME Human Factors Analysis and Classification System Maintenance Extension and Bayesian Network
Aircraft maintenance is a complex task involving a skilled human workforce, spare parts, and various other resources. Human factors are an inherent element of the human workforce.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER) A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER) Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…