FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24LA331 · Aero Commander 200 D

26 Jul 2024 · Valdosta, GA, United States

Aero Commander 200 D · Accident: system/component malfunction/failure (non-power) on approach

Report a problem

Event

NTSB case
ERA24LA331
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
Event fatalities
Unknown
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

Aero Commander 200 D

Aircraft type
Aero Commander 200
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
N326WR
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 58 years (built 1966)
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
Approach · VFR pattern downwind
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
System/component malfunction/failure (non-power)
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

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

NTSB narrative

After filling the fuel tanks, the flight instructor flew the airplane on multiple flights with different fuel tanks selected, including the right main fuel tank, with no discrepancies. The instructor and a pilot who was receiving familiarization training in the airplane then departed with the fuel selector on the right main fuel tank. They performed airwork with the fuel selector on a different tank before switching back to the right main fuel tank for an approach and landing. Before departing again, the pilot and instructor reviewed the fuel quantity indications and decided to keep the fuel selector on the right main tank position because the indicated quantity appeared sufficient to sustain engine operation. After departure, the flight remained in the airport traffic pattern. After turning onto the downwind leg, the engine lost power, regained it momentarily, then lost power completely. Turning on the auxiliary fuel pump did not restore engine power. The flight instructor took control of the airplane and elected to land in a field after determining the airplane could not reach a closed runway at the airport. After touchdown, the airplane bounced then came to an abrupt stop with substantial damage to both wings and the fuselage.

Postaccident examination of the airplane determined that the right main fuel tank had collapsed inward despite no corresponding damage to the surrounding wing structure and wing skin. Further examination of the right main fuel tank’s fuel vent line utilizing compressed air found that an insect nest had extensively blocked it. This blockage would have prevented air from entering the tank as fuel was consumed and allowed a partial vacuum to develop inside the tank. The inward collapse also trapped the fuel quantity transmitter arm, and resulted in the fuel quantity gauge indicating more fuel than was actually present. As fuel continued to be consumed from the unvented tank, the erroneous fuel quantity indication prevented the flight crew from accurately assessing the remaining usable fuel. Before the takeoff that preceded the loss of engine power, the pilots selected the right main fuel tank based on the indicated fuel quantity, although the tank actually contained insufficient usable fuel. After departure, the engine lost total power due to fuel starvation when the fuel remaining in the selected tank was exhausted. Although the pilots activated the auxiliary fuel pump and the instructor directed the left-seat pilot to select another fuel tank, selection of the right fuel tank did not occur before the pilots’ attention became solely focused on executing the forced landing.

Probable cause

An insect nest in the right main fuel tank’s vent line, which resulted in an inaccurate fuel level reading, fuel starvation, and a total loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24LA331
Event ID
20240730194806
Case number
ERA24LA331
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, 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: 9730001f7615328ad54af148bff28c2ef3edeae7c6eba43e9763382f7c312213; retrieved 2026-09-16T19:06:34.404Z.