SAFENET


SAFENET

Wildland Fire Safety & Health Reporting Network

SAFENET Event Information
Create Agency Corrective Action

SAFENET ID:
20170719-0002        [Corrective Actions]
Event Start Date:
07/18/2017 1145
Event Stop Date:
07/18/2017 1900 
Incident Name:
Hudson
Fire Number:
 
State:
California
Jurisdiction:
Other
Local Unit:
Incident Type:
Wildland
Incident Activity:
Support
Stage of Incident:
Initial Attack
Position Title:
Fire Fighter 
Task:
Initial Attack 
Management Level:
3
Resources Involved:
1 type 1 crew, 2 type 2IA crews, 4 type 3 engines, 1 type 4 engine, 6 type 6 engines, 3 tpye 2 helicopters 
Contributing Factors
Contributing Factors:
Communications
Human Factors:
Performance  
Other Factors:
 
Narrative
Describe in detail what happened including the concern or potential issue, the environment (weather, terrain, fire behavior, etc), and the resulting health issue.
Currently, we are having complications with our radio communications system; which may, potentially, become a definite hazard and/or safety issue.
The issue began, approximately, a week ago with the start of The Whittier Fire and it operating on an emergency communication channel (FOREST NET). In turn, the forest dispatch is having difficulties with communication to the remaining units on the forest. In an attempt to mitigate the issue, dispatch has had all traffic go through administrative net, including, occurring new incidents.
Now, the forest dispatch is operating on a backup system and being on a backup system, communications with dispatch has been a nightmare. Resources are unable to hear their unit being dispatched to incidents and once on an incident the Incident Commander is having trouble relaying important information to dispatch. Repeaters were staying open for 5 to 10 seconds after releasing the mic button and were not transmitting important radio traffic. Plus, dispatch having to dispatch resources on multiple tones.
On July 18th, 2017, my engine was dispatched to the Hudson fire. We were informed incidents would be relayed through our Admin Net, however, the tone out for the fire came over Forest Net. The tone out was broken, scratchy, and difficult to comprehend the information being transmitted about the fire. The dispatch was trying to do check backs on multiple repeaters, which took a while for all resources dispatched to confirm response. The Initial size up was scratchy and hard to hear on the forest net repeat channel. When my engine got on scene we were unaware of the command and tactical channel change and thought that the command channel was still on forest net. Only after we spoke face to face to the new incident commander did we learn about the channel change.
The simulcast is a problem, in all, we are seeking a solution that will mitigate communication problems with dispatch and other units on the forest.
In closing 1- the biggest issue is the simulcast system. Every morning we hear the weather and daily fire staffing information multiple times because dispatch has to broadcast this info on multiple repeaters. This is not a big deal but when we have an incident the first on engine is trying to give a size up, updated fire conditions, and ordering more resources. The radio is open but undenounced to the IC dispatch is on other repeaters still dispatching resources and also has to get check backs from those resources
In closing 2- the Whitter fire was using our forest net for over a week after the type 1 team took over the incident. Which hindered our daily fire fighter operations.
Immediate Action Taken
Reporting Individual : please describe actions you took to correct or mitigate the unsafe/unhealthful event.
the captain of my engine tied in with the Hudson incident commander and got the proper channels for the fire.


Corrective Actions

20170719-0002-CA001

Return to Top