LAX07TA227 · Bell 205 A1++
US Dept Of Agriculture Bell 205 A1++ · Accident: in flight collision with object while maneuvering
From Happy Camp Airport (36S) to an unrecorded destination
Event
- NTSB case
- LAX07TA227
- 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
Bell 205 A1++
- Aircraft type
- Bell 205
- Category
- Helicopter
- 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
- N205BR
- Operator
- US Dept. of Agriculture
- Onboard fatalities
- Unknown
- Route
- From Happy Camp Airport (36S), Happy Camp, CATo 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 133: Rotorcraft Ext. Load
- 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 · hover in ground effect
- 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 › 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
The accident occurred while the helicopter was supporting firefighting efforts with long-line operations. Two days prior to the accident, the division group supervisor (DIVS) anchored a colored reflective panel used for indicating landing and drop zones at the accident location. The DIVS stated that no site assessment was performed at the time of the panel placement because the placement was not intended to be the indicator of the drop zone for blivet deliveries. The terrain in the area consisted of steep slopes and trees varying in height from 75 to 200 feet. One day prior to the accident, the location of the panel was not changed from the previous day and remained as placed by the DIVS. The accident helicopter, equipped with a 150-foot-long line, then made the blivet drop within 3 feet of the panel. The marshaller stated he warned the pilot about the proximity of one tree that was located to the right and upslope. Two ground crew members distanced themselves from the blivet drop because they were concerned with their own safety due to the tree hazards. The division safety officer visited the site immediately after the blivet operation and there was no discussion regarding the aircraft use, the drop zone, or any discernment on the part of any crew member regarding the safety of the operation. In addition, there was no discussion about the operation during the "After-Action Review" (AAR) at the overnight camp that evening. On the day of the accident prior to the day's missions, there was no safety assessment or organized AAR conducted. The accident pilot was told that he would be delivering two more blivets to the same drop zone and back hauling the empty blivets that had been delivered the day before. At the intended drop zone, two crew members, who were not the same from the previous day, were so concerned about the potential for an accident that they briefed each other three times on what action would be taken in the event of an accident; however, this was not discussed with the pilot. The panel was not moved and the drop zone site remained in the same location as the previous day. The marshaller communicated with the DIVS that a longer long-line was recommended so the helicopter could remain above the trees; however, the helicopter had already departed. Witnesses observed that as the blivets were set down on the ground, the helicopter drifted to the right and the main rotor blades contacted a 165-foot-tall tree about 15 feet from the top. The long-line, along with the blivets, remained attached to the helicopter as it made a turn to the left, stopped momentarily, and then flew downhill to ground impact. The helicopter impacted several trees and was destroyed by post impact fire. No anomalies were noted with the airframe and engine that would have precluded normal operation prior to the accident. The helicopter was approved for the pilot to operate the aircraft from the left seat. Visibility to the right side of the helicopter was partially obstructed by aircraft structure, passenger seats, and the seat headrests.
Probable cause
the pilot's failure to maintain clearance with the trees during a long-line operation. Contributing factors were the Forest Service's inadequate communication between crews, failure to properly assess the safety of the intended drop zone, reduced visibility to the right side of the helicopter, and the trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07TA227
- Event ID
- 20070804X01107
- Case number
- LAX07TA227
- 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: 08600d2f686e1c90b3854df9fdb2258389a530ee6121e5f5c4023a92996ba0eb; retrieved 2026-09-20T16:26:54.710Z.