FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17LA003 · Melborn JOE B KOLB SPORT 600

9 Oct 2016 · Roberts, ID, United States

Melborn JOE B KOLB SPORT 600 · Accident: loss of engine power (partial) en route

From Roberts, ID to Joslin Field Magic Valley Regional Airport (TWF)

Report a problem

Event

NTSB case
WPR17LA003
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

Melborn JOE B KOLB SPORT 600

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
N914NK
Operator
Unknown
Onboard fatalities
Unknown
Route
From Roberts, IDTo Joslin Field Magic Valley Regional Airport (TWF), Twin Falls, ID
Aircraft age
About 12 years (built 2004)
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
En route · climb to cruise
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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that, after participating in a recreational fly-in event, he completed a successful engine run-up and the high-speed taxi test and departed the airstrip. As the airplane reached about 100 ft above ground level, the engine began losing power. The pilot initiated a slight right turn, followed by a left-turn teardrop maneuver. The pilot engaged the airplane's auxiliary fuel pump to maintain engine power, but the propeller stopped rotating a few seconds later. The airplane touched down about 200 ft south of the runway on sage brush, subsequently impacted a debris pile during the landing roll, nosed over, and then came to rest inverted, which resulted in substantial damage to the rudder. After the first taxi test, the pilot returned to the tie-down area and told the property owner that the engine had experienced possible vapor lock but added that he felt comfortable with the engine's ability to develop power after the taxi test. The pilot told the property owner that the engine had experienced vapor lock during previous flights.

During postaccident testing, the engine ran continuously despite momentary interruptions of power during the first three test runs. During two subsequent test runs, the engine power was advanced to full power, and it ran smoothly without interruptions; the cause of the power interruptions in the first three runs could not be determined. Postaccident examination of the engine revealed that the carburetor floats were 24% and 42% heavier than prescribed by the manufacturer's guidance. However, the heavier float weight likely would not have resulted in the in-flight loss of power due to the constant introduction of fuel through the fuel inlet at higher engine speeds.

The carburetor needle clips were found repositioned to the leanest (No. 1) setting, which the pilot had requested. Although the engine manufacturer recommended that the needle clip position remain in the No. 2 position, the engine ran continuously during the engine run, which was accomplished with both carburetor needle clips in the No. 1 position. Therefore, the carburetor needle clip adjustment likely did not contribute to the loss of power.

A representative of the engine manufacturer reported that this particular engine configuration was susceptible to vapor lock and that low fuel in either wing tank may allow air to be ingested, which may lead to vapor lock and fuel starvation. In this case, the engine was still hot from the previous flight and high-speed taxi, which could have increased the potential for heat-induced vapor lock. However, the accident pilot's prior encounters with vapor lock could not be verified, and the airplane was equipped with a fuel return line, which would have prevented the formation of vapor lock. Additionally, air ingestion was unlikely because the low quantity of fuel found in the fuel tank was likely due to postaccident fuel migration. Further, the airplane was equipped with a header tank, which also would have made air ingestion unlikely even if the left tank was empty in flight. Given that the engine did not display any anomalies during the postaccident engine run that would have precluded normal operation, the reason for the in-flight loss of power could not be determined.

Probable cause

A total loss of engine power for reasons that could not be determined based on the available information.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17LA003
Event ID
20161012X13615
Case number
WPR17LA003
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: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: a6ebd90fb936af96b3b3097d0be2416b40143acf0e0b46997d32574714ab2326; retrieved 2026-09-16T04:23:07.045Z.