CHI07CA105 · Pavliga Hatz CB-1
Pavliga Hatz CB-1 · Accident: loss of engine power on approach
From Buffalo Municipal Airport (CFE) to Clermont-Ferrand Auvergne airport (CFE)
Event
- NTSB case
- CHI07CA105
- 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
Pavliga Hatz CB-1
- Aircraft type
- Pavliga HATZ CB-1
- 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
- N899P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Buffalo Municipal Airport (CFE), Buffalo, MNTo Clermont-Ferrand Auvergne airport (CFE)
- 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
- Approach · VFR pattern downwind
- First occurrenceThe 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
- 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
- Fuel starvation
- 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
- Fluid, fuel › Starvation
- Fuel system, carburetor › Flow restricted
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane impacted terrain during a forced landing following a total loss of engine power. The pilot reported that during the preflight inspection he visually inspected the fuel tank and no fuel contamination was detected from a gascolator fuel sample. The pilot performed three landings, but while on the downwind leg for the fourth landing "the engine abruptly stopped." Best glide speed was established and the airplane was maneuvered toward the runway for landing. The pilot reported that he "confirmed that carb heat was off and mixture full, rocked the wings and switched mags off and then on, in an attempt to restart the engine." The airplane "just cleared" the perimeter fence and touched down short of the runway in a ditch. The right main gear subsequently separated and the airplane rolled inverted. An on-scene inspection of the airplane indicated that there was sufficient fuel available in the fuel tank and a gascolator fuel sample was free of water and particulate contamination. Examination of the carburetor revealed that the carburetor fuel flow valve would stick in the closed position.
Probable cause
The loss of engine power due to the carburetor fuel flow valve becoming stuck in the closed position, which resulted in fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07CA105
- Event ID
- 20070511X00553
- Case number
- CHI07CA105
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 148403a612b5596d0c900e3cb5d6b92b7b89a90cebcf2a72cbb9684ea83ff5f4; retrieved 2026-09-22T03:54:20.170Z.