FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24FA265 · Vans RV6 A

17 Jun 2024 · Methuen, MA, United States

Vans RV6 A · Accident: fuel starvation during initial climb

From Lawrence Municipal Airport (LWM) to an unrecorded destination

Report a problem

Event

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

Vans RV6 A

Aircraft type
Vans RV6
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
N715PA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lawrence Municipal Airport (LWM), Lawrence, MATo not recorded
Aircraft age
About 7 years (built 2017)
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
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
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

  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Shortly after takeoff, the airplane’s engine lost power and the pilot made a forced landing to a river. The airplane came to rest inverted in about 3 ft of water and the pilot was fatally injured. Fuel and engine performance data downloaded from the airplane’s onboard engine monitor revealed that the loss of engine was immediately preceded by a loss of fuel pressure. The data also showed that when the pilot first started the engine prior to takeoff, the left fuel tank was nearly full, and the right fuel tank was empty. The fuel selector was positioned to the right tank at the accident site. Postaccident examination of the airplane revealed that neither wing fuel tank was breached, and no evidence of any preexisting fuel leaks were observed. The engine was test-run on the airframe using the airplane’s fuel system. The engine started and ran without interruption though its full power band with the fuel selectors on both the left and right tanks. The examination of the engine and fuel system revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. An autopsy of the pilot’s remains, along with the results of postaccident toxicological testing, indicated that he had medical conditions (diabetes, high blood pressure, and atherosclerosis) that, in conjunction with his age (80 years), were associated with some increased risk of an impairing or incapacitating cardiovascular event. There was no autopsy evidence that such an event occurred, although such an event does not leave reliable autopsy evidence if it occurs just before death. The pilot’s postmortem HbA1c indicated that he had diabetes, and that it was marginally controlled in the few months prior to the accident. Toxicology results indicated that he was using diabetes medications. He was at increased risk of both abnormally high blood glucose (from diabetes) and abnormally low blood glucose (from medication effects). The negative vitreous glucose result makes it unlikely that the pilot was experiencing severe high blood sugar with major metabolic disturbance at the time of the accident. The combination of the negative vitreous glucose result with the elevated urine glucose measurement does not exclude the possibility of low, somewhat high, or fluctuating blood sugar at the time of the accident; furthermore, some common diabetes symptoms, such as fatigue and blurry vision, do not directly correspond to blood sugar values in a simple way. The pilot received a third-class aviation medical certificate roughly 8 months before the accident, and the likelihood is low that any chronic diabetes-related retinopathy or neuropathy progressed rapidly since then; however, because diabetes was not reported to the FAA as of that date, no targeted FAA evaluation for chronic diabetes complications was performed. Overall, there is no specific evidence that the pilot was impaired by effects of his diabetes at the time of the accident, although the possibility of some impairing effects, such as fatigue, blurry vision, or diminished concentration, cannot be excluded.

Probable cause

The pilot’s failure to manage the available fuel supply, which resulted in a total loss of engine power due to fuel starvation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24FA265
Event ID
20240617194485
Case number
ERA24FA265
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, cause areas. 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: 5e4a5f088160b3e921d7a0c893e46c41f7d4d2786de913da973909e22f35b07e; retrieved 2026-09-15T08:18:48.394Z.