FTW00LA030 · Air Tractor AT-802A
Air Tractor AT-802A · Accident: airframe, component or system failure during takeoff
From 2F5 to an unrecorded destination
Event
- NTSB case
- FTW00LA030
- 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-802A
- Aircraft type
- Air Tractor AT-802
- 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
- N6044A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 2F5To 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
- Takeoff · roll/run
- 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
- Airframe, component or system failure
- 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
- Flt control syst, rudder control cable/rod › Separation
- Flt control syst, rudder control cable/rod › Worn
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was departing from runway 16 for a local aerial application flight, when the pilot heard a 'loud bang,' and 'the right rudder pedal fell to the floor.' The airplane veered to the left, exited the runway, ground-looped, and came to rest upright. Postaccident examination of the airplane revealed that the right rudder cable separated at the aft fairlead. Examination of the rudder cable by the NTSB Materials Laboratory revealed that the individual separated strands of the cable had a flat and shiny appearance, indicative of wear. The wear was primarily on one side of the cable, extending around 90 degrees of the cable's circumference. Air Tractor issued a service letter on August 27, 1999, advising operators of rudder cable wear at the aft fairlead on the AT-802 and AT-802A. The service letter stated that a new cable, which incorporated a stainless steel sleeve that is crimped to the cable in the area of the fairlead, was available. The operator was aware of the service letter, but had not replaced the rudder cables.
Probable cause
The separation of the rudder control cable at the aft fairlead, as a result of wear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00LA030
- Event ID
- 20001212X19967
- Case number
- FTW00LA030
- 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: fcd92358a259660837a100c113a10ee2616cfde68e46b5ea69c74669e66ab733; retrieved 2026-09-22T13:55:23.220Z.