ATL83FKQ03 · Air Tractor AT-301
Air Tractor AT-301 · Accident: airframe, component or system failure while maneuvering
From SNE · REDWOOD, MS to an unrecorded destination
Event
- NTSB case
- ATL83FKQ03
- 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-301
- Aircraft type
- Air Tractor AT-301
- 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
- N8511S
- Operator
- Martin L. Hallman · private individual
- Onboard fatalities
- Unknown
- Route
- From SNE · REDWOOD, MSTo 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
- 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
- Other maintenance personnel › Maintenance, inspection, poor
- Other maintenance personnel › Maintenance, lubrication, poor
- Propeller system/accessories, counterweight › Failure, total
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT MADE A FORCED LANDING IN A SOYBEAN FIELD AFTER SEVERE VIBRATION DEVELOPED DURING A SPRAYING OPERATION. THE PILOT STATED THAT THE POWERPLANT AND FLT CONTROLS WERE FUNCTIONING NORMALLY AT THE TIME OF THE ACCIDENT. AN ON-SCENE INVESTIGATION REVEALED THAT THE COUNTERWEIGHT BEARING SHAFT (P/N 63546) BROKE ALLOWING THE PROPELLER BLADE TO GO TO HIGHER PITCH WHILE THE OTHER BLADE REMAINED AT CRUISE PITCH SETTING. EXAMINATION OF BOTH PROPELLER BLADE COUNTERWEIGHTS REVEALED THAT THE INTERNAL PARTS HAD MINIMUM AMOUNT OF LUBRICATION. THE SHAFT THAT BROKE WAS ALSO RUSTY AND THE INNER BEARING RACE WAS BROKEN WITH 5 BALL BEARING MISSING. THERE WERE OTHER MAINTENANCE DICREPANCIES ON THIS SHAFT ASSEMBLY. THE TOTAL TIME OF THIS HAMILTON STANDARD 12D40 PROPELLER IS UNKNOWN. THE TIME SINCE THE ACFT WAS INSPECTED IS 194 HOURS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL83FKQ03
- Event ID
- 20001214X43990
- Case number
- ATL83FKQ03
- 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: ecbc3c9d4407eecf32fc29ee2a6618259d048f5f43e54b13566e27ee33dfe1f7; retrieved 2026-09-23T21:29:26.484Z.