SAFENET


SAFENET

Wildland Fire Safety & Health Reporting Network

SAFENET Event Information
Create Agency Response

SAFENET ID:
20190603-0002        [Corrective Actions]
Event Start Date:
06/02/2019 1530
Event Stop Date:
 
Incident Name:
SCHAFFER MEDICAL
Fire Number:
 
State:
California
Jurisdiction:
USFS
Local Unit:
Big Valley Ranger District - Modoc NF
Incident Type:
All Hazard, Training
Incident Activity:
Support, Transport to/from
Stage of Incident:
Other
Position Title:
Center Manager 
Task:
Life Flight, Federal Employee 
Management Level:
4
Resources Involved:
Modoc T2 IA, MDF E-354, Cal Fire Helicopter 202, SEMSA AIR (Life Flight), PHI Life Flight, REACH Life Flight 
Contributing Factors
Contributing Factors:
Communications, Equipment
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.
Ongoing technical issue with "switches" being installed into network connecting points. These have caused WILDCAD to crash intermittently. These were installed two weeks ago, with local IT communicating with contacts @ CIO to remedy the crashes with little progress.

Our local IT contact has been assured that its being handled, but without follow up and the problem continues on.

These intermittent crashing affected our ability in a life flight and medical transport for a federal employee.

During the 2 hour incident, the program crashed approximately 11 times. Forcing the users to exit and sometimes restart computer entirely.

This caused a delay in relaying pertinent information to medical resources, such as Landing Zone information, call signs, ETA's of responding resources, and other misc information.

The center was able to respond and use other programs to keep track of pertinent information and to log it back into CAD when the program was running.

It should be noted that the problem isn't with WILDCAD itself, but the switch/network "upgrade" that hinders its communication with the server which causes the crash.
Immediate Action Taken
Reporting Individual : please describe actions you took to correct or mitigate the unsafe/unhealthful event.
The Center was quick to respond, seeing these outages occurring at a higher rate. We went to Pen and Paper tracking of the incident and coordinating with those who still had access to WildCAD. Once pertinent information was able to be extracted, went to pen and paper tracking using Wildcad secondary.

Dispatchers migrated to laptops who could access the WIFI and didn't have there network reset over and over.


Communicated with local IT support to stress the importance of our network issues being remedied, as it hindered emergency medical efforts. He related that it didn't seem to be progressing 2 weeks after the fact. Submitted Help Desk Ticket for network issues so the problem can be seen from "multiple points"


Agency Response

20190603-0002-CA001

Return to Top