FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15LA053 · Beech F33A

15 Nov 2014 · Clinton, CT, United States

Beech F33A · Accident: fuel starvation en route

From Groton New London Airport (GON) to Orange County Airport (MGJ)

Report a problem

Event

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

Beech F33A

Aircraft type
Beechcraft 33
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
N4548S
Operator
Unknown
Onboard fatalities
Unknown
Route
From Groton New London Airport (GON), Groton, CTTo Orange County Airport (MGJ), Montgomery, NY
Aircraft age
About 39 years (built 1975)
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
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 › Aircraft systems
  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the commercial pilot, earlier on the day of the accident, she had flown the airplane from her home airport to the airport from which the accident flight departed. Before departing on the return flight to her home airport, she noted about 20 gallons of fuel in each main wing tank for the 45-minute flight. After taking off and establishing the airplane on course, she climbed the airplane to 4,500 ft mean sea level; trimmed the airplane for cruise flight; and set engine rpm to 2,300, manifold pressure to 23 inches of mercury, and fuel flow to 13 gallons per hour. Sometime later, she heard "a loud explosive bang - like a gunshot." She immediately checked her instruments and noted that the rpm had risen to over 2,500. She then reduced the propeller control with no effect. The airplane started to "shudder." The rpm dropped to 2,000, the airspeed had dropped off, and the airplane began to lose altitude. She then checked her propeller setting and aggressively advanced the propeller, but there was no increase in rpm. She contacted air traffic control, reported engine problems, and declared an emergency; the controller advised her to land at a nearby airport. The pilot turned toward the airport but was unable to see it. When she realized that she was not going to find the airport or an open area, she decided not to put the landing gear down because she was aiming to land the airplane on top of the trees. She reached down to shut the fuel selector off because she was afraid there might be a fire once she crashed. Because she was approaching the trees, she did not look at the fuel selector handle to check its setting. She knew she turned the handle but was not sure if she had fully turned it to the off position from the right tank position. The airplane then collided with the trees and sustained substantial damage.

Postaccident examination of the propeller and engine revealed no evidence of preexisting malfunctions or failures that would have precluded normal operation. An engine run in a test cell revealed that it operated normally with no anomalies noted. Further examination of the airplane revealed that it had not been configured by the pilot per the manufacturer's published guidance in the pilot's operating handbook and Federal Aviation Administration-approved airplane flight manual for a loss of engine power, maximum glide configuration, or landing without power.

First responders did not report evidence of a fuel spill, although both wing tip tanks and wing fuel bladders were breached. The tip tanks were totally devoid of fuel, but fuel was in the undamaged portion of each of the wing tank's fuel bladders. About 17 gallons of fuel were recovered from the right-wing tank, and less than 1 gallon of fuel was recovered from the left-wing tank. The fuel selector was in the left tank position. The fuel strainer was clean, free of debris, and devoid of fuel. No fuel was recovered from the fuel supply line to the engine-driven fuel pump.

Examination of the electronic fuel-flow indicator, which presented information to the pilot about the fuel usage and could display the total fuel used and the remaining fuel on board, revealed that it had not been initialized by the pilot in quite some time. An accurate fuel-remaining value relied on the pilot to initialize the device when refueling. A review of fueling information revealed that the pilot had not refueled the airplane at her home airport earlier that day; further, she did not refuel before departing on the accident flight. Because the pilot had not refueled before either flight on the day of the accident and had not initialized the fuel-flow indicator, it is likely that she did not perform adequate preflight fuel planning and improperly managed the fuel in flight, which led to fuel starvation.

Probable cause

The pilot's inadequate fuel planning and improper fuel management, which resulted in a total loss of engine power due to fuel starvation. Contributing to the accident was the pilot's failure to follow proper procedures in response to the loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15LA053
Event ID
20141117X83502
Case number
ERA15LA053
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. 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: b9cd35585cce8320bdfdbad06c66912f2c3ae48521ee34c7f6a8af3475535925; retrieved 2026-09-16T01:56:01.495Z.