WPR15GA005 · Marsh Aviation S 2F3AT
Usda Forest Service Fepp Marsh Aviation S 2F3AT · Accident: low altitude operation/event while maneuvering
From Columbia Airport (O22) to El Portal, CA
Event
- NTSB case
- WPR15GA005
- 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
- Government
- 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
Marsh Aviation S 2F3AT
- Aircraft type
- Marsh S-2
- 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
- N449DF
- Operator
- Usda Forest Service Fepp
- Onboard fatalities
- Unknown
- Route
- From Columbia Airport (O22), Columbia, CATo El Portal, CA
- Aircraft age
- About 13 years (built 2001)
- 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
- Public Aircraft
- 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 · low-altitude flying
- 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
- Low altitude operation/event
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airline transport pilot was conducting a visual flight rules, public firefighting retardant drop flight on an active fire. The airplane, call sign "Tanker 81," was supported by two other aircraft: an orbiting Air Tactical aircraft (ATGS) that coordinated the aerial operations with ground units and an Aerial Supervision Module (ASM) that flew ahead of the tanker to define the route and the drop initiation point. After successfully conducting one drop, Tanker 81 was reloaded with fire retardant, and it then returned to the fire area. The accident pilot coordinated his next drop with the ATGS and then followed the ASM to the drop.
According to the ASM pilot, he flew the proposed drop route and initiated smoke to show the Tanker 81 pilot the desired drop location. The route included a slight left turn to final and a right turn on exit over descending terrain. The ASM had descended to 4,000 ft msl during the run, and described a predominate tree off to the right of the flightpath as a hazard, and instructed the accident pilot to stay to the left of it. The ASM pilot also described "very clear, smooth air over the drop area." He asked the Tanker 81 pilot if he had seen the smoke and if the route looked OK to him? The Tanker 81 pilot responded that "it looked OK." The ASM then climbed to 5,100 ft msl to lead the drop run. The ASM joined the pattern on the downwind and then told the Tanker 81 pilot that he could descend to 5,100 ft msl. He continued to describe the drop and flightpath to the tanker pilot and told him that there was some thin top smoke on final but that he could see through it and that they would break out of the smoke before reaching the drop area. He added that the last response he received from the tanker pilot was when he said, "OK."
Witnesses reported seeing the accident, and one of them provided a video that was taken from a vantage point along a mountain trail that was above Tanker 81's flightpath. The video revealed that while on approach, Tanker 81 struck trees with its left wing. Following the impact with the trees, the airplane entered a descending left roll, and it then impacted on the top of an approximate 800-ft-tall rock cliff. A fire erupted during the impact, the airplane fragmented, and the main wreckage was projected over the cliff and scattered over a wide river valley below the cliff face.
An examination of the wreckage site confirmed that the airplane's left wing had struck trees, and the outboard section of the left wing had separated from the airplane. Examination of the two engines revealed impact signatures consistent with their producing power at the time of impact. The pilot was in radio communications with either the fire base, the ATGS, or the ASM throughout the accident flight, and he did not report any concerns about the flight or mechanical issues.
Probable cause
The pilot's failure to maintain clearance from trees while maneuvering at a low altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR15GA005
- Event ID
- 20141007X20706
- Case number
- WPR15GA005
- 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: 64e87aecd01f5937850afada7f80b2ba5947e0912f47df5d2ae70376466f299a; retrieved 2026-09-14T17:27:22.345Z.