FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD05LA147 · Hanson VariEze

4 Sept 2005 · New Cumberland, PA, United States

Hanson VariEze · Accident: total loss of engine power (non-mechanical) en route

From Capital City Airport (CXY) to an unrecorded destination

Report a problem

Event

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

Hanson VariEze

Aircraft type
Hanson VARIEZE
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
N220EZ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Capital City Airport (CXY), New Cumberland, PATo not recorded
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
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
Total loss of engine power (non-mechanical)
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 contamination; 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

  • Owner/builder › Maintenance, inspection, inadequate

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 had been airborne for about 5 minutes when the engine lost power. The pilot then force landed in a field, and the airplane nosed over. During a post-accident examination, the propeller was replaced, and the engine was started and operated for about 5 minutes at 1,700 rpm. The fuel system was also examined, and the fuel screens in both fuel tanks were found to be covered in a "fine muddy silt," consistent with mud dauber activity. A subsequent fuel analysis revealed that particulate contamination and gum levels were "very high." The fuel tanks had been open during the airplane's construction, and the airplane had about 30 hours of operation at the time of the accident.

Probable cause

The owner/builder's inadequate fuel tank inspection during construction, which resulted in fuel contamination and subsequent fuel starvation to the engine.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD05LA147
Event ID
20060109X00032
Case number
IAD05LA147
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: cfdac62593c4a071df631cea9e581b3665130e42fec519a194c92cb48ebd75f1; retrieved 2026-09-21T18:54:39.966Z.