FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12FA217 · Oliver Joseph ZODIAC CH 601XL

30 Mar 2012 · Belmont, OH, United States

Oliver Joseph ZODIAC CH 601XL · Accident: loss of engine power (total) en route

From Mifflin County Airport (KRVL) to Spirit of St Louis Airport (KSUS)

Report a problem

Event

NTSB case
CEN12FA217
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
1 · 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

Oliver Joseph ZODIAC CH 601XL

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
N8060J
Onboard fatalities
Unknown
Route
From Mifflin County Airport (KRVL), Mifflin County, PATo Spirit of St Louis Airport (KSUS), Spirit of St L, MO
Aircraft age
Not recorded
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 · 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 (total)
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 power plant
  • Personnel issues › Psychological

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 had previously flown the experimental, amateur-built airplane cross-country to a potential buyer; the sale was not completed and the airplane did not fly for several months until arrangements could be made to return the airplane. The pilot was ferrying the airplane on the return flight. A witness reported seeing the airplane in cruise flight when its engine “cut out” and its attitude dipped slightly then leveled; the airplane then nosed over and descended straight down, impacting the ground in a residential yard. Another witness reported that the engine “roared loudly” and sped up just before the airplane nosed over. A review of the airplane maintenance records revealed an annotation dated about 4 months before the accident indicating that the pilot had previously performed a precautionary landing due to a rough running engine. The reason for the rough running engine and any repairs made were not found in the airplane records.

A postcrash examination of the airplane’s engine showed heavy sooting and contaminants in the carburetor inlet, the inlet side of the carburetor slide, the outlet side of the butterfly valve, and the lower outlet portion of the venturi, which exhibited a distinct washing of the soot. The inlet side of the venturi had minor sooting. The outlet side of the slide was relatively free of sooting but exhibited a varnish or gum-type build-up. The slide was found in the closed position and did not move freely; however, it would move if a prying force was applied to the bottom of the slide. Sooting patterns on the outlet side of the engine components are usually indicative of a leaking intake valve, which could cause blowback of gases into the intake manifold and carburetor. If severe enough, this blowback could result in engine failure. In addition, the build-up observed on the carburetor slide was much more than normal and could have caused the slide to stick open during the accident flight. If the throttle were reduced while the slide was stuck, air flow would be reduced while fuel flow remained high, resulting in a rich mixture that could stop the engine. The engine would again run at full throttle but not at any reduced throttle setting. Although the carburetor slide was found in the closed position, a problem with engine operation would be expected with a slide that does not move freely. Based on the examination of the carburetor and other engine components, it is likely that the engine experienced a loss of power. The witness statements indicating the airplane’s sudden drop in altitude suggest that the pilot’s attention was focused on the engine problem rather than maintaining airplane control, resulting in the airplane entering a rapid descent and impacting terrain.

Probable cause

The loss of engine power and the pilot’s diverted attention to the engine power loss, which resulted in a rapid descent and impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12FA217
Event ID
20120402X82357
Case number
CEN12FA217
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: 174d5082ad0159d5cb54bed161ed607663a4a8c678b4de020ba05eaf49fef04f; retrieved 2026-09-13T22:17:29.197Z.