SEA98LA080 · Air Tractor AT-401
Air Tractor AT-401 · Accident: in flight collision with object while maneuvering
From OSGOOD, ID to an unrecorded destination
Event
- NTSB case
- SEA98LA080
- 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-401
- Aircraft type
- Air Tractor AT-401
- 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
- N1009T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From OSGOOD, IDTo 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
- 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
- Wire, transmission
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, who was maneuvering near the power line while applying chemicals to a field, he had just rolled wings-level and descended for another pass when his left wing contacted the top wire of the power line. He said that he saw the line and thought he had clearance, but the aircraft's wing caught the wire near its tip. He reported that after colliding with the power line, the aircraft struck the ground in a 'cart-wheeling' motion. He further stated that he was accustomed to flying the AT-300, but that he had recently purchased the AT-401, and that this was his first application flight using the new aircraft. It was his opinion that the different size and sight-picture of the 401 had caused him to think he had more clearance from the wire than he actually had.
Probable cause
The pilot's failure to maintain clearance from a power transmission line during an aerial application flight. Factors include a power line located just beyond the boundary of the field being sprayed, and the pilot's incorrect judgement of the distance between the wire and his aircraft.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA98LA080
- Event ID
- 20001211X10197
- Case number
- SEA98LA080
- 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: b4c3d133ccff728ee864dc7b8742c14d9a4e626a5432b42c4006d9b0378b2cff; retrieved 2026-09-21T20:50:32.290Z.