CHI08CA245 · Air Tractor 301
Air Tractor 301 · Accident: system/component malfunction/failure (non-power) during landing
From Herreid Municipal Airport (5T4) to an unrecorded destination
Event
- NTSB case
- CHI08CA245
- 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 301
- Aircraft type
- Air Tractor 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
- N3161A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Herreid Municipal Airport (5T4), Herreid, SDTo 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
- Landing · landing roll
- 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
- System/component malfunction/failure (non-power)
- 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 oper/perf/capability
- Aircraft › Aircraft systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot returned for landing in the tailwheel configured airplane after an agricultural application flight. He executed a normal landing on runway 12 (2,230 feet by 200 feet, asphalt/turf) and kept the tail up as long as possible as the airplane slowed. The pilot stated that when the tailwheel touched down it felt as if the tail was dragging on the ground and the airplane drifted to the right. He applied opposite rudder but was unable to stop the drift. He subsequently applied the brakes, which spun the airplane around and brought it to a stop partially off the runway. The pilot reported that after the accident he observed a bolt securing the tailwheel had failed. The bolt was discarded and was not available for further examination. The pilot commented that he will proactively inspect and replace the tailwheel bolts before each spray season.
Probable cause
Failure of one of the tailwheel bolts on landing and the pilot's subsequent inability to maintain directional control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08CA245
- Event ID
- 20080919X01504
- Case number
- CHI08CA245
- 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, coordinates. 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: 0e6362dafbffa72f0e020de1762f797bfeee52213cbdecbe60d9bfc21d02b61a; retrieved 2026-09-15T10:15:14.733Z.