SAFENET

SAFENET Notification

  • Monthly System Maintenance that was scheduled this past Saturday did not occur. It has been rescheduled for Saturday September 20. It will begin at 7am (MDT) and last approximately four hours. During this time frame, there will be a disruption in service and applications will be unavailable. If you are not able to access the application after the completion of the maintenance, please direct your issues to the following email: BLM_HQ_590@blm.gov

SAFENET

Wildland Fire Safety & Health Reporting Network

SAFENET Event Information
Create Agency Response

SAFENET ID:
20250906-0002
Event Start Date:
09/06/2025 1718
Event Stop Date:
 
Incident Name:
WOOD
Fire Number:
S9H7 
State:
California
Jurisdiction:
USFS
Local Unit:
CA-SHF
Incident Type:
Wildland
Incident Activity:
Support, Readiness/Preparedness
Stage of Incident:
Initial Attack, Extended Attack
Position Title:
Asst Center Manager - Dispatch 
Task:
E-106, AFF, WildCAD 
Management Level:
N/A
Resources Involved:
Aircraft, Crews, Engines, Overhead 
Contributing Factors
Contributing Factors:
Communications, Equipment, Other
Human Factors:
Decision Making, Leadership, Risk Assessment, Performance, Situational Awareness  
Other Factors:
USFS Network - Lumen 
Narrative
Describe in detail what happened including the concern or potential issue, the environment (weather, terrain, fire behavior, etc), and the resulting health issue.
In a dispatch center, during the Initial Attack response for a new fire, the internet that our systems are tied to, became increasingly deteriorated, to the point of not being able to perform our duties. This led to unsafe conditions for all resources responding to this fire. We could not identify locations of the fire due to map in WildCAD not loading on several computers.

We use an electronic 106 to dispatch firefighting aircraft over the intercom to the incident. Poor network issues resulted in the aircraft dispatcher being unable to load the FC-106 and provide timely dispatching of aircraft.

Poor network issues resulted in our aircraft dispatcher being unable to Flight Follow aircraft using AFF, which is an unsafe, life-threatening event. If an aircraft went down, we would have no way of knowing where its last location was.

Our CAD which dispatches resources was not performing as it should due to network issues and we could not identify what resources were responding and/or what resources were still needed for the incident, as well as being unable to record information in the log of the incident.
Immediate Action Taken
Reporting Individual : please describe actions you took to correct or mitigate the unsafe/unhealthful event.
We had to use printed staffing sheets and a wall map to identify closest resources to respond to the incident. We had to hand write notes from the IC and responding units and then at a later time transcribe them into the CAD card.

We switched and rotated several computers that seemed to have fewer issues, or loaded for a short time, information we needed. One computer seemed to have AFF that worked and loaded, while another seemed able to load the electronic 106. Then after awhile the computer that originally had problems, would start working again.

Flight following was accomplished using several computers to find one less affected, as well as asking for state, Calfire, to assist in flight following from their computers.


Return to Top