LAX01LA114 · Air Tractor AT-802 A
Sarita Aerial Contractors Air Tractor AT-802 A · Accident: overrun during landing
From Maricopa, AZ (no airport) to Maricopa, AZ (no airport)
Event
- NTSB case
- LAX01LA114
- 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-802 A
- 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
- N6059L
- Operator
- Sarita Aerial Contractors
- Onboard fatalities
- Unknown
- Route
- From Maricopa, AZ (no airport)To Maricopa, AZ (no airport)
- 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
- Landing · flare/touchdown
- 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
- Overrun
- 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
- Airport facilities, runway overrun area › Inadequate
- Ground personnel › Planning/decision, improper
- Object › Vehicle
Approximate · Estimated position: the centre of Maricopa, AZ, the place the record names. Not the accident site.
NTSB narrative
The orientation of the runway was 340 degrees. The weather at the nearest reporting station indicated that the winds were from 100 degrees at 6 knots. This would have resulted in a 4-knot rear quartering tailwind and a 2-knot crosswind from the right. Using the performance data listed in the airplane's pilot operating handbook, the landing distance was calculated to be 2,109 feet, without using reverse. The Gila River West runway on which the accident occurred was 2,400 feet long. Assuming that the airplane was flown at the reference speed of 73 knots, with no wind, and touched down on the threshold, there would have been only 291 feet remaining on the runway. The tailwind present at the time of the accident would have increased the landing distance required, and thereby reducing the available runway. The presence of an irrigation sump at the end of the runway would have eliminated any margin for error, and made it impossible to overrun the runway safely. The placement of a truck along the side of the runway at the departure end further limits available options in the event of a long landing or overrun. Under the conditions at the time of the accident, there would have been no allowance for error either in pilot technique, or in a real or perceived mechanical malfunction. These factors would force the pilot to make sudden, last minute maneuvers to avoid obstacles at the end of the runway. During an engine inspection, performed by factory personnel, and witnessed by an inspector from the Federal Aviation Administration Southwest Manufacturing District Office (FAA MIDO-41), the engine was operated up to 30 percent of its power range with no anomalies noted. The power was reduced to idle several times and the propeller did not feather. The propeller operated throughout the operating range, including beta, with no defects noted. It was noted that with the power lever in the full aft position, the beta plunger was slightly depressed. This may have been enough to allow the propeller to go slightly past the low pitch stop, toward reverse, when the power lever was pulled back to the idle position. It was observed that rubbing had occurred between the two controls. The FAA inspector and assisting personnel attempted to force the throttle lever to move the propeller control lever aft. The two levers did move aft together, only when the power lever was pulled inboard against the propeller control lever. However, the propeller control lever could not be made to move past the feather detent. If the throttle had been closed, the propeller would move to the low pitch (high rpm) position even with the propeller control pulled aft to the control stop.
Probable cause
Inadequate selection of landing facilities and improper placement of vehicles near the runway. An additional factor was the use of a runway which resulted in a downwind landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01LA114
- Event ID
- 20010316X00596
- Case number
- LAX01LA114
- 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: ae0d80f4d752bde1fbf4867bdde3c2aac6fb4acad374982b557781f78b20638c; retrieved 2026-09-22T12:06:28.918Z.