CHI05LA004 · Malone VANS RV-6A
Malone VANS RV-6A · Accident: total loss of engine power (non-mechanical) during initial climb
From Joliet Regional Airport (JOT) to Lewis University Airport (LOT)
Event
- NTSB case
- CHI05LA004
- 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
Malone VANS RV-6A
- Aircraft type
- Malone VANS RV-6A
- 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
- N85MM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Joliet Regional Airport (JOT), Joliet, ILTo Lewis University Airport (LOT), Romeoville, IL
- 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
- Initial climb
- 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
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Aircraft preflight, inadequate
- Pilot in command › Fuel consumption calculations, 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 amateur-built airplane was destroyed during a forced landing shortly after takeoff in night visual meteorological conditions. A witness reported that the pilot landed about 1930 cdt and taxied to the fuel pumps, but no fuel was available until the next morning. The witness offered to drain 5 gallons of fuel from an airplane nearby. The pilot declined the offer of fuel and told the witness that he intended to fly to another airport located about 10 miles away, and obtain fuel there. The witness reported that the pilot "didn't seem concerned about fuel" and the he "didn't say anything about his flight plan." Another witness reported that he observed the airplane depart. He reported that the pilot taxied the airplane about 150 yards from the fuel pumps to runway 12. He reported that the pilot did not do an engine run-up or magneto check before departing. He reported that the airplane became airborne within the first one-third of the runway. The airplane climbed to 500 - 700 feet above ground level and about the time that it cleared runway 12, the engine backfired twice and quit. He reported that the airplane made a right hand turn and impacted the terrain about 5 - 7 seconds after the engine stopped running. The witness did not report hearing the engine running after it backfired. Witnesses who live near the accident site reported hearing the airplane's engine prior to impact. One witness reported observing the airplane "spiraling" down. A lieutenant of the police department reported that there was no evidence of a fuel spill at the accident site. He reported that the fire department did not wash down the accident site with water since there was no evidence of fuel. Inspection of the accident site revealed the following conditions: 1) No fuel odor apparent in or around the aircraft. 2) No signs of a fuel spill or fuel leaking in the vicinity of the crash site. 3) No fuel in the left or right fuel tank. 4) No signs of a fuel fire. The airplane's fuel tanks held a total of 38 gallons. Pages from a maintenance form used for recording engine performance parameters, such as altitude, rpm, manifold pressure, fuel flow, cylinder head temperature, and exhaust gas temperature, were found in the airplane following the accident. The recordings indicated the average fuel flow was about 12.2 gph at 4,500 feet mean sea level at 2,700 rpm. Flight control continuity was established between the cockpit controls and their respective flight control surfaces. The propeller was broken free of the engine at the propeller flange. Both propeller blades exhibited leading edge gouging, chordwise scratching, and blade twist. The data downloaded from the pilot's Garmin GPS 296 indicated that the airplane departed Erie, Pennsylvania, about 1751 eastern daylight time, and arrived at Joliet, Illinois, about 1940 central daylight time, a distance of 437 nautical miles traveled in 2 hours and 49 minutes. The pilot started to taxi at 1952 cdt and departed on the accident flight.
Probable cause
The total loss of engine power due to fuel exhaustion as a result of the pilot's inadequate preflight and inadequate fuel consumption calculations, also causal was the pilot's failure to maintain aircraft control during the forced landing. A factor was the night condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05LA004
- Event ID
- 20041021X01673
- Case number
- CHI05LA004
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2004-10-15.
- API snapshot SHA-256: 7342a62cbfdb309b9507ed211cd159bc3a97f656720d82341d2f7a42181dc8ac; retrieved 2026-09-20T18:18:43.480Z.