FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI03LA289 · Air Tractor AT-502B

22 Aug 2003 · Westside, IA, United States

Westerlin and Harrington Flying Ser Air Tractor AT-502B · Accident: total loss of engine power (non-mechanical) while maneuvering

From Arthur N Neu Airport (CIN) to an unrecorded destination

Report a problem

Event

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

Air Tractor AT-502B

Aircraft type
Air Tractor AT-502
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
N5007G
Onboard fatalities
Unknown
Route
From Arthur N Neu Airport (CIN), Carroll, IATo not recorded
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 137: Agricultural
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 · aerial application
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
Substantial

Cause areas

  • Fluid, fuel › Exhaustion
  • Pilot in command › Preflight planning/preparation, 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 aircraft was substantially damaged during a forced landing following a complete loss of engine power due to fuel exhaustion. The pilot reported completing a final agricultural application pass when the engine abruptly lost power. He noted: "There was no place to land, I hit the fuel boost pump and the [aircraft] powered up again for 1 or 2 seconds." This allowed the pilot to clear a farm house and set-up for a forced landing in an alfalfa field. The aircraft subsequently impacted an "up sloping draw ... a terrace and went into a steep gully," according to the pilot. A post-accident examination found no evidence of fuel on-board. Both fuel tanks were empty and there was no sign of fuel on the ground in the vicinity of the aircraft. The pilot reported no malfunctions with the aircraft prior to the loss of engine power. No anomalies associated with a pre-impact failure were observed during the post-accident inspection. The pilot reportedly had a standing request with the fixed base operator that the aircraft be filled to the 3/4 tabs each time it was fueled. He stated that the fuel gauges "have been very undependable this summer," so after each refueling he would enter 162 gallons into the fuel flow meter. Due to his lack of confidence in the fuel gauges, the pilot was using the fuel flow meter to monitor his in-flight fuel status. The pilot stated that he did not visually verify the fuel quantity after refueling prior to the accident flight.

Probable cause

The pilot's inadequate preflight planning/preparation which led to fuel exhaustion and subsequent loss of engine power. Contributing factors were the unsuitable terrain encountered, and the terrace/embankment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI03LA289
Event ID
20030828X01422
Case number
CHI03LA289
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: 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: 4dc9c0f143367284e4722facf8c4588ac0d26bafc005b7450d3dcdb10da83c43; retrieved 2026-09-21T19:23:22.478Z.