CEN18LA064 · Pipistrel DOO Ajdovscina VIRUS SW
Pipistrel DOO Ajdovscina VIRUS SW · Accident: fuel starvation while maneuvering
From Paulding, OH to Paulding, OH
Event
- NTSB case
- CEN18LA064
- 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
Pipistrel DOO Ajdovscina VIRUS SW
- Aircraft type
- Pipistrel Doo Ajdovscina VIRUS SW
- Category
- Glider
- 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
- N4JW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Paulding, OHTo Paulding, OH
- Aircraft age
- Built the same year (2017)
- 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
- Maneuvering
- 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
- Fuel starvation
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Fluids/miscellaneous hardware
- Environmental issues › Physical environment
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airline transport pilot was conducting a local flight in his motor-powered glider. The pilot had the right fuel tank selected and was flying in a counterclockwise direction around a ground reference point when the engine began to lose power. The pilot switched fuel tanks with no improvement and selected a nearby road for a forced landing. During the landing roll on the ice-covered road, the glider's left wing impacted a bush, and the glider exited the road; the nosewheel broke off when it impacted a ditch.
The flight manual indicated that all basic nonaerobatic maneuvers are permitted within the operational speed range, which included steep turns with a maximum bank of 60°. The recommended fuel, per the flight manual, was an unleaded super grade. A warning directed that use of fuel with alcohol content and/or other additives is not permitted. Testing of recovered fuel revealed that it contained about 5% alcohol. However, examination of the fuel system revealed no evidence of preimpact malfunctions or failures that would have precluded normal operation, and the engine was operational during a postaccident engine run.
Although the pilot reported the glider had 5 to 6 gallons of fuel in each of the two main tanks, a second engine test run was conducted where the engine was intentionally fuel starved. Data from the avionics and engine computers were then downloaded, plotted, and compared to data from the accident flight. Both the accident data and the fuel starvation test data similarly showed the engine began to run roughly as the rpm and fuel flow began to fluctuate. Additionally, avionics data showed that both the accident flight data and the fuel starvation test run data had similar indications.
The glider's GPS tracked the accident flight from the point of takeoff to the point of the forced landing. This GPS data and the engine data were plotted to determine where the fluctuating engine rpm consistent with engine roughness and the loss of engine power occurred. The glider departed, climbed, and made multiple left turns with multiple altitude changes. The data showed the glider was in a left climbing turn when the engine began to lose power after fluctuations in engine rpm.
Based on the available data, it is likely the fuel unported during the glider's climbing turn, which resulted in fuel starvation and the loss of engine power.
Probable cause
The loss of engine power while the motor-powered glider was maneuvering due to the fuel unporting in its fuel tank, which resulted in fuel starvation and a subsequent forced landing on unsuitable terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18LA064
- Event ID
- 20180102X10253
- Case number
- CEN18LA064
- 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. 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: b2ef1e85f90a75f1d2d745623238a5df1c37d32e534dac75d387c6cbd271d2de; retrieved 2026-09-16T06:15:05.746Z.