Critiques/2009-05-05
From PCSAR
(→PCSAR Board) |
|||
(40 intermediate revisions not shown.) | |||
Line 23: | Line 23: | ||
* Relationships with Tasking Agencies and Fellow Responding Organizations. | * Relationships with Tasking Agencies and Fellow Responding Organizations. | ||
* Financing, budget | * Financing, budget | ||
- | suggestions identified: {{ | + | suggestions identified: {{SugRef|1}} |
=== PCSAR Preplan Committee === | === PCSAR Preplan Committee === | ||
Line 30: | Line 30: | ||
* Standard Operating Procedures for incidents. | * Standard Operating Procedures for incidents. | ||
* Post incident critique, review and follow-up. | * Post incident critique, review and follow-up. | ||
- | suggestions identified | + | suggestions identified: {{SugRef|1}}, {{SugRef|2}}, {{SugRef|3}}, {{SugRef|5}}, {{SugRef|6}}, {{SugRef|7}}, {{SugRef|8}}, {{SugRef|9}}, {{SugRef|10}}, {{SugRef|11}}, {{SugRef|12}}, {{SugRef|13}}, {{SugRef|16}}, {{SugRef|17}}, {{SugRef|18}}, {{SugRef|19}} |
=== PCSAR Equipment Committee === | === PCSAR Equipment Committee === | ||
Mandate Relevant to Incidents: | Mandate Relevant to Incidents: | ||
* Obtaining and keeping equipment ready. | * Obtaining and keeping equipment ready. | ||
- | suggestions identified | + | suggestions identified: {{SugRef|4}} |
=== PCSAR Call-Out Committee === | === PCSAR Call-Out Committee === | ||
Mandate Relevant to Incidents: | Mandate Relevant to Incidents: | ||
* Respond to First Call from Tasking Agency | * Respond to First Call from Tasking Agency | ||
* Contacting members during an incident. | * Contacting members during an incident. | ||
- | suggestions identified | + | suggestions identified: {{SugRef|1}}, {{SugRef|2}} |
=== PCSAR Membership Committee === | === PCSAR Membership Committee === | ||
Mandate Relevant to Incidents: | Mandate Relevant to Incidents: | ||
* Recruiting members. | * Recruiting members. | ||
* Tracking members contact information, skills and equipment. | * Tracking members contact information, skills and equipment. | ||
- | suggestions identified | + | suggestions identified: {{SugRef|1}}, {{SugRef|2}} |
=== PCSAR Training Committee === | === PCSAR Training Committee === | ||
Mandate Relevant to Incidents: | Mandate Relevant to Incidents: | ||
* Training members. | * Training members. | ||
- | suggestions identified | + | suggestions identified: {{SugRef|3}}, {{SugRef|12}}, {{SugRef|13}}, {{SugRef|14}}, {{SugRef|15}}, {{SugRef|16}}, {{SugRef|19}}, {{SugRef|20}}, {{SugRef|21}} |
=== Tasking Agency === | === Tasking Agency === | ||
Mandate Relevant to Incidents: | Mandate Relevant to Incidents: | ||
* Overall legal responsibility for incident. | * Overall legal responsibility for incident. | ||
- | suggestions identified | + | suggestions identified: {{SugRef|8}} |
=== Fellow Responding Organizations === | === Fellow Responding Organizations === | ||
Mandate Relevant to Incidents: | Mandate Relevant to Incidents: | ||
* Response to incident in accordance with their individual mandate and ability. | * Response to incident in accordance with their individual mandate and ability. | ||
- | suggestions identified | + | suggestions identified: none |
== Suggestions by functional area == | == Suggestions by functional area == | ||
+ | [[Category:Suggestion compendium]] | ||
=== first notification / tasking === | === first notification / tasking === | ||
=== call-out === | === call-out === | ||
- | + | {{quote-page|Critiques/2009-05-05/Sug1}} | |
- | + | {{quote-page|Critiques/2009-05-05/Sug2}} | |
- | + | ||
- | + | ||
=== investigation === | === investigation === | ||
=== communications === | === communications === | ||
- | + | {{quote-page|Critiques/2009-05-05/Sug3}} | |
- | + | ||
=== resources === | === resources === | ||
- | + | {{quote-page|Critiques/2009-05-05/Sug4}} | |
=== family liaison === | === family liaison === | ||
=== (de)briefing === | === (de)briefing === | ||
- | + | {{quote-page|Critiques/2009-05-05/Sug5}} | |
- | + | {{quote-page|Critiques/2009-05-05/Sug6}} | |
- | + | ||
=== searching === | === searching === | ||
- | + | {{quote-page|Critiques/2009-05-05/Sug7}} | |
- | + | {{quote-page|Critiques/2009-05-05/Sug8}} | |
- | + | {{quote-page|Critiques/2009-05-05/Sug9}} | |
- | + | {{quote-page|Critiques/2009-05-05/Sug10}} | |
- | + | {{quote-page|Critiques/2009-05-05/Sug11}} | |
- | + | {{quote-page|Critiques/2009-05-05/Sug12}} | |
- | + | {{quote-page|Critiques/2009-05-05/Sug13}} | |
- | + | {{quote-page|Critiques/2009-05-05/Sug14}} | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
=== extrication === | === extrication === | ||
- | + | {{quote-page|Critiques/2009-05-05/Sug15}} | |
- | + | {{quote-page|Critiques/2009-05-05/Sug16}} | |
- | + | ||
- | + | ||
=== stand down === | === stand down === | ||
Line 110: | Line 97: | ||
=== prevention, public education === | === prevention, public education === | ||
=== travel === | === travel === | ||
- | + | {{quote-page|Critiques/2009-05-05/Sug17}} | |
- | + | {{quote-page|Critiques/2009-05-05/Sug18}} | |
- | + | ||
- | + | ||
=== logistics === | === logistics === | ||
Line 122: | Line 107: | ||
(e.g., how this critique was organized, mock search goals, exercise techniques) | (e.g., how this critique was organized, mock search goals, exercise techniques) | ||
- | + | {{quote-page|Critiques/2009-05-05/Sug19}} | |
- | + | {{quote-page|Critiques/2009-05-05/Sug20}} | |
- | + | {{quote-page|Critiques/2009-05-05/Sug21}} | |
- | + | ||
- | + |
Current revision
Suggestions coming from the May 5 critique and submitted separately regarding the May 5 mock search and the previous Anderson search.
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.
[edit] 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.
[edit] 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: #1
[edit] 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: #1, #2, #3, #5, #6, #7, #8, #9, #10, #11, #12, #13, #16, #17, #18, #19
[edit] PCSAR Equipment Committee
Mandate Relevant to Incidents:
- Obtaining and keeping equipment ready.
suggestions identified: #4
[edit] PCSAR Call-Out Committee
Mandate Relevant to Incidents:
- Respond to First Call from Tasking Agency
- Contacting members during an incident.
suggestions identified: #1, #2
[edit] PCSAR Membership Committee
Mandate Relevant to Incidents:
- Recruiting members.
- Tracking members contact information, skills and equipment.
suggestions identified: #1, #2
[edit] PCSAR Training Committee
Mandate Relevant to Incidents:
- Training members.
suggestions identified: #3, #12, #13, #14, #15, #16, #19, #20, #21
[edit] Tasking Agency
Mandate Relevant to Incidents:
- Overall legal responsibility for incident.
suggestions identified: #8
[edit] Fellow Responding Organizations
Mandate Relevant to Incidents:
- Response to incident in accordance with their individual mandate and ability.
suggestions identified: none
[edit] Suggestions by functional area
[edit] first notification / tasking
[edit] call-out
|
|
[edit] investigation
[edit] communications
|
[edit] resources
|
[edit] family liaison
[edit] (de)briefing
|
|
[edit] searching
|
|
|
Could make easier to recognize sweep boundaries. Could be tied to end of walking/tracking stick. Could develop convention for markings "X" like disaster search.
|
|
|
|
|
[edit] extrication
|
|
[edit] stand down
[edit] CISM
[edit] prevention, public education
[edit] travel
preplan 2009-05-19
preplan 2010-06-15
|
|
[edit] logistics
[edit] planning
[edit] media
[edit] post ops
[edit] learning
(e.g., how this critique was organized, mock search goals, exercise techniques)
|
|
|
Committee handling | Suggestion/Committee/List/membership +, Suggestion/Committee/List/unassigned +, Suggestion/Committee/List/training +, and Suggestion/Committee/List/preplan + |
Description | Not able to get call-out people on incidents. Suggest have lead call-out coordinator on-call for month or 2 week period like manager-on-call. Suggest get more call-out people. +, Using old call out list. Confusion when coordinating with other call-out person. Some people called twice. Suggest use same list. Suggest having index by name and split index. +, Merging teams can cause confusion in command/reporting structure. Suggest clear language of merging vs. working together. Suggest switch to single FRS channel for new team. +, Suggest get gel pens which won't freeze. +, Map becoming available only after given assignment relative to locations is sometimes confusing. Suggest map orientation should be first. +, Debriefing forms don't match urban context. Suggest rework wording. +, Suggest have minimum of 2 people approach door for member safety and to give assurance of legitimacy to resident +, Suggest when urban searching at night have patrol vehicle or other equipped with alley lights and search lights accompany teams to speed up searching of front yards and vehicles. Could expect Pincher RCMP to support in this way. +, Suggest having roving support vehicle for urban search teams for food, water, warming, transport +, Suggest mark sidewalk with chalk in urban search to indicate what has/hasn't been searched by which team +, Suggest wear reflective vests for urban night search for higher visibility vs normal street clothes. Makes team seem less suspicious when seen by resident in their yard +, Suggest search areas that are difficult can be reexamined by strategically spotting from point of advantage. E.g. thick brush along creek spotted from other side. +, Discussion of degree of discretion to work outside assigned segment. Suggest need for clarification of when should talk to command post vs. decide on own. +, Suggest when spotting subject, maintain visual contact until part of party approaches. Can lose perspective as approach. +, Having many people approach Alzheimer sufferer likely to cause trauma +, Suggest use rope as belay line when extracting stretcher on slope +, Suggest continued use of carpooling to search in e.g. Lethbridge. Better safety on way back when tired +, Suggest having arrangement to call-in when driving alone back from a tiring search (e.g. night search). To confirm safe arrival +, Suggest encourage members in field to discuss overhead decisions after search as learning opportunity +, Suggest everyone get experience of working comms and command post +, and Suggest better learning if everyone can see handling of first approach to subject. + |
Difficulty to implement | medium +, not rated +, hard +, done +, and easy + |
Full page name | Critiques/2009-05-05 + |
Review | tasked + |
Sequence number | 1 +, 2 +, 3 +, 4 +, 5 +, 6 +, 7 +, 8 +, 9 +, 10 +, 11 +, 12 +, 13 +, 14 +, 15 +, 16 +, 17 +, 18 +, 19 +, 20 +, and 21 + |
Value to PCSAR mandate | high +, none +, low +, not rated +, and medium + |
Categories: Suggestion compendium | Committee membership | Value high | Difficulty medium | Committee unassigned | Value none | Difficulty not rated | Committee training | Value low | Difficulty hard | Value not rated | Difficulty done | Value medium | Difficulty easy | Committee preplan | Review/Brett Wuth