MIA03LA094 · Air Tractor AT- 401
Air Tractor AT- 401 · Accident: in flight collision with object while maneuvering
From New Hibiscus Airpark (X52) to New Hibiscus Airpark (X52)
Event
- NTSB case
- MIA03LA094
- 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- 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
- N4549N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From New Hibiscus Airpark (X52), Vero Beach, FLTo New Hibiscus Airpark (X52)
- 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
- Destroyed
Cause areas
- Pilot in command › In-flight planning/decision, poor
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 stated that he doesn't remember the accident, but he did report that during a spray run, he overshot the end of the field due to sun in his eyes. He also reported there was no mechanical failure or malfunction. According to the president of the Indian River Flying Service, Inc., the pilot was just starting to pull-up after completing a spray pass when the airplane collided with a tree then the ground. According to an officer with the Indian River County Sheriff Department, the airplane collided with a tree located in an open area, then impacted the ground. A debris path was scattered over a 300 to 350 yard area. The wreckage comprised of two large pieces, and a chemical odor was noted at the accident site.
Probable cause
The poor in-flight planning by the pilot-in-command for his overhsooting the pull-up following a spray pass resulting in the in-flight collision with trees then terrain. Contributing to the accident was sunglare that the pilot encountered during the spray pass.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA03LA094
- Event ID
- 20030414X00498
- Case number
- MIA03LA094
- 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: 5da1083375fc482fddeeb7d22bb3a84604e99476fdd32028b07c8dffe9d6d63c; retrieved 2026-09-21T09:29:17.507Z.