FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09CA323 · Air Tractor INC. AT-502

29 May 2009 · Mendota, IL, United States

R & R Flight Service Air Tractor INC. AT-502 · Accident: runway excursion during takeoff

From Grandpas' Farm Mendota Airport (0C7) to Grandpas' Farm Mendota Airport (0C7)

Report a problem

Event

NTSB case
CEN09CA323
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 INC. AT-502

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
N198LA
Onboard fatalities
Unknown
Route
From Grandpas' Farm Mendota Airport (0C7), Mendota, ILTo Grandpas' Farm Mendota Airport (0C7), Mendota, IL
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
Takeoff
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
Runway excursion
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 handling/service
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The agricultural airplane was loaded about 300 pounds over its maximum gross weight for a commercial aerial application flight. The pilot stated that the airplane had not become airborne after traveling 3/4 down the runway. At that point in the takeoff, the pilot attempted to lift off, but the airplane settled back onto the runway. The airplane then overran the runway and hit a hill after which the airplane became airborne and then impacted the ground with its right wing tip and left wing, resulting in substantial damage. The pilot sustained minor injuries.

Probable cause

The pilot's inadequate preflight planning and preparation and his failure to perform an aborted takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09CA323
Event ID
20090601X22459
Case number
CEN09CA323
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: 63f88b31e20afc4f7dd9d0e58f17f0641c1eddc3d9403f6193a68aaee95c488f; retrieved 2026-09-15T11:15:05.714Z.