FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN03LA109 · Air Tractor AT-802A

22 Jun 2003 · Las Vegas, NM, United States

Air Tractor AT-802A · Accident: in flight collision with object while maneuvering

From Las Vegas Municipal Airport (LVS) to an unrecorded destination

Report a problem

Event

NTSB case
DEN03LA109
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-802A

Aircraft type
Air Tractor AT-802
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
N8505E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Las Vegas Municipal Airport (LVS), Las Vegas, NMTo 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
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 › Visual lookout, 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

The pilot was on his fourth sortie of the day, dropping retardant on a forest fire. He lowered flaps to 20 degrees and slowed the airplane to 100 to 120 knots in preparation for the drop. He passed the initial point in a slight right bank with a 500 to 600 foot per minute rate of descent and approximately a 3-degree glide angle. He momentarily diverted his attention to smoke rising from the target area. When he looked back, he saw a dead snag immediately in front of the airplane. He was unable to avoid hitting the tree due to its proximity and his rate of closure. The impact deflected the right elevator full down. The airplane pitched nose down and struck a second tree. The pilot regained limited control and returned to the airport, where he made an uneventful landing.

Probable cause

the pilot's failure to maintain obstacle clearance and visual lookout. Contributing factors were his attention being diverted and the trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN03LA109
Event ID
20030627X00967
Case number
DEN03LA109
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: de049e79a9abb1d739b5ad8907370e82f193982421713719530db72c873068ba; retrieved 2026-09-22T09:06:17.632Z.