CHI07LA208 · Air Tractor AT-301
Air Tractor AT-301 · Accident: in flight collision with object while maneuvering
From Eby Field (II74) to an unrecorded destination
Event
- NTSB case
- CHI07LA208
- 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
- 1 · 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-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
- N3158W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Eby Field (II74), Wakarusa, INTo 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
- In flight collision with object
- 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
- Tree(s)
- 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 › Clearance, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
"THIS CASE WAS MODIFIED SEPTEMBER 19, 2008."
The pilot was spraying a short field that had wooded areas on both the north and south ends of the field when the accident occurred. Data from the global positioning system (GPS) that was onboard the airplane indicated the airplane was heading north prior to entering a right turn to the south just prior to impacting the trees. The initial tree impact was at the edge of a heavily wooded area, adjacent to the field that was being sprayed. The airplane continued into the wooded area contacting trees up to 12 inches in diameter, prior to coming to rest inverted. Clean, freshly cut branches were located along the impact trail. The pilot began flying aerial application flights a couple a weeks prior to the accident.
Probable cause
The pilot's failure to maintain clearance with the trees during the aerial application flight. Factors associated with the accident were the trees and the pilot's lack of experience in flying aerial application flights.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07LA208
- Event ID
- 20070717X00946
- Case number
- CHI07LA208
- 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, 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: 67bea39a827f1306c57b5a88f2b419d971f7fac7604686017d7d178fb2889e7e; retrieved 2026-09-20T16:28:28.918Z.