FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW96LA177 · Air Tractor AT-502B

18 Apr 1996 · Pond Creek, OK, United States

Homestead Farms Flying Service Air Tractor AT-502B · Accident: loss of control in flight during initial climb

From Trust Landing Airport (OK72) to an unrecorded destination

Report a problem

Event

NTSB case
FTW96LA177
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
0
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
N6050D
Onboard fatalities
Unknown
Route
From Trust Landing Airport (OK72)To 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
Initial climb
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
Loss of control in flight
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
Stall/mush
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

  • Pilot in command › Airspeed, not obtained/maintained
  • Pilot in command › Planning/decision, improper
  • Pilot in command › Stall/mush, inadvertent

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

NTSB narrative

According to the pilot, he had routinely flown off the 2,800 foot runway with a similar load; however, on this takeoff, the airplane was not airborne at the usual place. The pilot attempted to dump the chemical load, but he missed the dump handle. After reaching the end of the runway, the airplane became airborne, crossed a ravine where the ground dropped off approximately 30 feet into a creek bed, and impacted terrain on the far side of the creek. The pilot reported that he normally followed the manufacturer's recommended short field takeoff procedure, which called for the use of a 10 degree flap setting; however, he indicated that he might not have used the flaps on the accident flight.

Probable cause

The pilot's improper planning/decision and failure to obtain/maintain sufficient airspeed to climb after takeoff, which resulted in a stall/mush and subsequent collision with terrain. Factors relating to the accident were: failure of the pilot to follow short field takeoff procedures, and his delay in jettisoning the chemical load.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW96LA177
Event ID
20001208X05565
Case number
FTW96LA177
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. 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: c29720f5d01e73339f9b7a382c4ef30a7a9d5130828c7838ca8c872f3b9adb25; retrieved 2026-09-22T22:37:25.191Z.