FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13CA425 · Cessna M337B

12 Sept 2013 · Spanish Fork, UT, United States

Artemis Cessna M337B · Accident: fuel exhaustion while maneuvering

From U77 · Spanish Fork, UT to U77 · Spanish Fork, UT

Report a problem

Event

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

Cessna M337B

Aircraft type
Cessna 337
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
N87653
Operator
Artemis
Onboard fatalities
Unknown
Route
From U77 · Spanish Fork, UTTo U77 · Spanish Fork, UT
Aircraft age
About 45 years (built 1968)
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
Maneuvering · low-altitude flying
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 exhaustion
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 › Psychological

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

NTSB narrative

The pilot reported that on the day of the accident, he elected to fly with a light, and slightly uneven, load of fuel to accommodate for the extra equipment and people onboard. During the low altitude flight, the pilot was not transferring fuel from the right wing fuel tanks to the left wing fuel tanks. Subsequently, the left wing fuel tanks ran empty and the forward engine lost power. The pilot elected to land in a nearby corn field. During the landing, the airplane's forward engine firewall sustained substantial damage. The pilot reported no preimpact mechanical failures or malfunctions with the airframe or engines that would have precluded normal operation.

Probable cause

The pilot's failure to properly manage fuel which resulted in fuel exhaustion and subsequent loss of power to the forward engine.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13CA425
Event ID
20130927X32557
Case number
WPR13CA425
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. 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: 2f577d4ef08a76a9fd2128dd6373a92b4914c54e5553b46cff3da9b7007f9ee5; retrieved 2026-09-15T22:55:04.688Z.