IAD98LA050 · McClead VARIEZE
McClead VARIEZE · Accident: total loss of engine power (non-mechanical) en route
From Waterbury Oxford Airport (OXC) to an unrecorded destination
Event
- NTSB case
- IAD98LA050
- 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
- 0
- 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
McClead VARIEZE
- Aircraft type
- Mcclead 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
- N728RJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Waterbury Oxford Airport (OXC), Waterbury, CTTo 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 exhaustion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Fluid, fuel › Exhaustion
- Fuel system, cap › Not secured
- Pilot in command › Aircraft preflight, inadequate
Approximate · Estimated position: the centre of Middlebury, CT, the place the record names. Not the accident site.
NTSB narrative
The pilot altered his preflight inspection, on the day of the accident, by putting an additive into the fuel. He stated that after doing so, he 'may not have tightened the right gas cap.' The pilot visually checked the fuel tanks, and reported 16 gallons of fuel onboard. He departed for a local flight and approximately 35 minutes later, while doing air work, the engine 'suddenly quit'. He attempted to glide back to the airport, and when he realized he would not make the runway, he performed a forced landing into a wooded area. Examination revealed the fuel tanks had maintained their integrity, with no indication of leakage. The right fuel cap was found off, hanging by its chain with no fuel in the tank and no indication of soil contamination beneath the tank. A 'trace' of fuel was found in the left tank and the center tank was empty. A Federal Aviation Administration Safety Inspector stated that no fuel was shown on either fuel gauge and no fuel was found in the fuel lines or carburetor, with about a half ounce of fuel in the fuel filter. There was no fuel smell on the ground surrounding the airplane.
Probable cause
the pilot's inadequate preflight when he did not secure the right wing fuel tank cap which led to fuel exhaustion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD98LA050
- Event ID
- 20001211X09882
- Case number
- IAD98LA050
- 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. 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: f2936114012cfebcc4ea2c7a1e66594f19a17f1c013a8779369c722a6f6e154a; retrieved 2026-09-21T20:51:39.597Z.