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:
20250905-0001
Event Start Date:
08/22/2025 1200
Event Stop Date:
 
Incident Name:
2025 ABC MISC LIGHTNING
Fire Number:
P5EK1725 0516 
State:
California
Jurisdiction:
USFS
Local Unit:
Stanislaus National Forest ECC
Incident Type:
Wildland
Incident Activity:
Support
Stage of Incident:
Extended Attack, Mop Up
Position Title:
Assistant Center Manager 
Task:
 
Management Level:
5
Resources Involved:
 
Contributing Factors
Contributing Factors:
Communications
Human Factors:
 
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.
On 08/22/2025, we had a dispatcher working on the IA floor at position 1 as the Call Taker / Aircraft dispatcher. Mid afternoon, he was kicked off of the network. We restarted the computer to try to fix the problem and he was unable to log back in to the computer. We opened a CIO ticket and were told that the computer was retired and there was nothing that could be done. To mitigate the problem, we took a computer out of our expanded dispatch and moved it to position 1 on the IA floor.
As of 09/05/2025, we have 21 active fires on forest from 2 recent lightning busts.
We have 4 IA floor dispatch consoles and on 09/05/2025 we had a dispatcher working at each console. Midday, the dispatcher at position 1 was kicked off of the internet, but network status showed connected. I opened a CIO ticket. Position 1 dispatcher was working as an aircraft dispatcher. Shortly after, the dispatcher at position 2, who was working as a Law Enforcement dispatcher, was kicked off of the network. During this time, we received a phone call from CIO about my earlier ticket stating that position 1 was a retired & scrapped computer, so we were unable to log into it. CIO closed my ticket on position 1, but kept my ticket for position 2 open. While talking to CIO about position 2, a dispatcher checked the expanded computers and found that of the 3 remaining expanded computers (since we had already moved one to the IA floor), 1 was kicked off of the network. Also during this time, the dispatcher at position 4, who was working as the Initial Attack dispatcher, was kicked out of Microsoft programs. I relayed to CIO that at this point we had 5 computers kicked off of the network and 21 active fires with ground resources on scene and aviation resources flying. CIO elevated my ticket since we had so many computers impacted.
This is a huge safety concern, as we are down dispatch consoles while we have firefighters responding to fires, Law Enforcement incidents occurring, and aviation flying.
This is an ongoing issue we are experiencing.
Immediate Action Taken
Reporting Individual : please describe actions you took to correct or mitigate the unsafe/unhealthful event.
Before opening CIO tickets, we tried to fix the issue ourselves. We checked all of the cables and initially tried restarting the computers, but soon realized that restarting could set us further back as we could be unable to get back in. I opened CIO tickets, one on 08/22/2025, and 2 on 09/05/2025. My first ticket from 09/05/2025 was closed once they realized that the computer was retired. My second ticket was elevated when we told them we had 4 computers impacted, though I should have said it was 5. I also contacted an IT specialist and had him look at the status of all of the computers that have been impacted. He found that all of the computers were retired/scrapped. We replaced two IA floor desktops with the two remaining expanded computers, but they are unable to manage all of the monitors that dispatch consoles require. This leaves us with a completely unusable expanded dispatch as there are no computers left, and a short IA floor as we have 3 of the 4 IA Dispatch Floor computers working. I emailed CIO end user hardware, explained the severity of the incident and requested they contact me ASAP. They have not contacted me yet. CIO has previously reached out about our new computers, but they have not been shipped. This means that we are losing computers without the replacements on the way. When I opened the 08/22/2025 ticket, I explained that the old computers could not be retired before we had the new computers. I explained the severity of impacted operations in an Emergency Communications Center. I repeated this sentiment while opening the tickets on 09/05/025. We are doing everything we can to keep the IA floor functioning.


Return to Top