2012-10-02 Mock/Critque
From PCSAR
Suggestions coming from the 2012-10-02 critique regarding the mock of the same date.
Pincher Creek SAR routinely performs a critique after a Search and Rescue incident in order to learn what should be done differently or the same in the next similar incident. Critiques are not about criticism but rather about learning. They are normally chaired by a Search Manager that was not involved in the incident. The suggestions that are brought forward through the critique process are presented in this report.
Participants
Rough notes
Committee / Organization
The suggestions are being passed on to the indicated organizations/committees for their consideration. We recognize that not all suggestions may be appropriate, and some may already have been implemented.
PCSAR Board
Mandate Relevant to Incidents:
- Overall ability of PCSAR to accomplish its mission.
- Organizational policies
- Relationships with Tasking Agencies and Fellow Responding Organizations.
- Financing, budget
suggestions identified: 32
Tasking Agency
Mandate Relevant to Incidents:
- Overall legal responsibility for incident.
Suggestions for the Tasking Agency are passed through the Board.
Fellow Responding Organizations
Mandate Relevant to Incidents:
- Response to incident in accordance with their individual mandate and ability.
Suggestions for fellow responding organizations are passed through the Board.
PCSAR Preplan Committee
Mandate Relevant to Incidents:
- Expertise in search and rescue.
- Standard Operating Procedures for incidents.
- Post incident critique, review and follow-up.
suggestions identified: 3, 7, 11, 12, 25, 26, 27, and 34
PCSAR Equipment Committee
Mandate Relevant to Incidents:
- Obtaining and keeping equipment ready.
suggestions identified: 2, 4, 6, 14, 16, 17, 18, 19, 20, 21, 22, 23, and 24
PCSAR Call-Out Committee
Mandate Relevant to Incidents:
- Respond to First Call from Tasking Agency
- Contacting members during an incident.
suggestions identified: none
PCSAR Membership Committee
Mandate Relevant to Incidents:
- Recruiting members.
- Tracking members contact information, skills and equipment.
suggestions identified: none
PCSAR Training Committee
Mandate Relevant to Incidents:
- Training members.
suggestions identified: 1, 5, 8, 9, 10, 13, 15, 28, 29, 30, 31, 33, 35, and 36
PCSAR Technology Committee
Mandate Relevant to Incidents:
- Technology support
suggestions identified: none
Suggestions by functional area
mandate
first notification / tasking
call-out
|
|
investigation
communications
|
|
|
|
resources
(de)briefing
searching
|
|
|
add to search guidelines to have one 2 person team in a vehicle doing roving patrols if warranted |
|
|
|
need to be more aware of segment sizes, difficulty etc. |
|
|
extrication
access/return from segment
stand down
CISM
prevention, public education
travel
|
|
planning
|
|
|
E.g. St. Mike's school was open mention during training for urban search theory |
logistics
|
|
|
label appropriately, make a map of layout and contents then pass off to training for familiarty |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Near the radio cabinet? |
|
|
operations
|
doesn't really apply, value to having all team members for briefing and debriefing. |
|
|
|
frs are usually deployed, must have been an oversight |
|
|
|
|
|
CP is in charge. They decide what activity is next. E.g. returning to base. Radio in with suggested changes of activity. |
|
|
media
family
post ops
learning
|
|
|
|
|
|
|
|
|
|
|
|
|
|
misc
| Committee handling | Suggestion/Committee/List/board +, Suggestion/Committee/List/training +, Suggestion/Committee/List/preplan +, and Suggestion/Committee/List/equipment + |
| Description | there should be a bigger turn out to training events +, need training on radio protocol +, technology always fails; e.g. radio, cell +, TL strategized by distance would have to travel to various assigned search locales +, urban searching done by vehicle +, use of dog in urban search; can handle large area +, the search segment was too large to be searched +, Need clarity when 2 teams come under one team leader +, Move CP to LKP +, The MCP map table was good. +, Urban search should anticipate may have to search open buildings or buildings that have subsequently locked +, Couldn't open the door. Need orientation. +, time spent looking for stuff in CP +, new CP worked well; radios good; cell phone good +, Need instructions on how to operate generator. +, Need instructions on driving the MCP +, MCP needs CO detector +, MCP needs curtain dividing sections +, MCP needs better place to hang radio mic cord, or perhaps a longer cord, or bungie cord +, MCP radio needs headset +, There's a leak in the MCP +, The heat in the MCP works well +, Only team leaders should be in new command post; room is limited. +, Having Ops Section Chief at the CP table was good; close to the door +, teams should have internal communications (e.g. FRS) for search efficiency +, Operations area of MCP needs file holder or accordion file +, MCP needs clock by table +, Teams in field should stick to assigned tasks, refer back to CP with changes. +, difficulty with only 2 teams +, Didn't know notes were in C.P. +, weather limited ability to track +, It was not clear what operational activities should be simulated, e.g. medical/stretcher equipment +, exercise should change size depending on number of teams available +, Jeff (RCMP) willing to help with training +, Recommend first aid review +, and Exercise felt disjointed; RCMP usually are involved earlier in incident + |
| Difficulty to implement | not rated +, done +, and easy + |
| Full page name | 2012-10-02 Mock/Critque + |
| Sequence number | 32 +, 30 +, 36 +, 25 +, 27 +, 28 +, 29 +, 35 +, 3 +, 21 +, 26 +, 2 +, 4 +, 6 +, 14 +, 15 +, 16 +, 17 +, 20 +, 22 +, 23 +, 24 +, 7 +, 11 +, 12 +, 18 +, 19 +, 33 +, 34 +, 1 +, 5 +, 8 +, 9 +, 10 +, 13 +, and 31 + |
| Value to PCSAR mandate | not rated +, medium +, and none + |
