|
|
(17 intermediate revisions not shown.) |
Line 1: |
Line 1: |
| + | {{Critique report/Header}} |
| + | |
| Suggestions coming from the March 21, 2010 critique | | Suggestions coming from the March 21, 2010 critique |
- | regarding the March 20 mock search and the March 7 avalanche response. | + | regarding the March 20 mock search and the March 7 avalanche response. |
| | | |
| Pincher Creek SAR routinely performs a critique after a Search and | | Pincher Creek SAR routinely performs a critique after a Search and |
Line 9: |
Line 11: |
| that are brought forward through the critique process are presented in | | that are brought forward through the critique process are presented in |
| this report. | | this report. |
| + | == Participants == |
| | | |
- | == Committee / Organization == | + | == Rough notes == |
- | 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 ===
| + | == Suggestions == |
- | Mandate Relevant to Incidents:
| + | {{Suggestion list}} |
- | * Overall ability of PCSAR to accomplish its mission.
| + | == Committee / Organization == |
- | * Organizational policies
| + | {{Critique report/Committees}} |
- | * Relationships with Tasking Agencies and Fellow Responding Organizations.
| + | |
- | * Financing, budget
| + | |
- | suggestions identified:
| + | |
- | | + | |
- | === 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:
| + | |
- | === PCSAR Equipment Committee ===
| + | |
- | Mandate Relevant to Incidents:
| + | |
- | * Obtaining and keeping equipment ready.
| + | |
- | suggestions identified:
| + | |
- | === PCSAR Call-Out Committee ===
| + | |
- | Mandate Relevant to Incidents:
| + | |
- | * Respond to First Call from Tasking Agency
| + | |
- | * Contacting members during an incident.
| + | |
- | suggestions identified:
| + | |
- | === PCSAR Membership Committee ===
| + | |
- | Mandate Relevant to Incidents:
| + | |
- | * Recruiting members.
| + | |
- | * Tracking members contact information, skills and equipment.
| + | |
- | suggestions identified:
| + | |
- | === PCSAR Training Committee ===
| + | |
- | Mandate Relevant to Incidents:
| + | |
- | * Training members.
| + | |
- | suggestions identified:
| + | |
- | === Tasking Agency ===
| + | |
- | Mandate Relevant to Incidents:
| + | |
- | * Overall legal responsibility for incident.
| + | |
- | suggestions identified:
| + | |
- | === Fellow Responding Organizations ===
| + | |
- | Mandate Relevant to Incidents:
| + | |
- | * Response to incident in accordance with their individual mandate and ability.
| + | |
- | suggestions identified:
| + | |
- | | + | |
- | == Suggestions by functional area == | + | |
- | === mandate ===
| + | |
- | {{quote-page|{{PAGENAME}}/Sug1}} | + | |
- | | + | |
- | === first notification / tasking ===
| + | |
- | * {{sug|2}} clarify purpose of task
| + | |
- | ** not
| + | |
- | * {{sug|3}} on-call person to have call-out list on person - program cell phone
| + | |
- | ** already done
| + | |
- | {{quote-page|{{PAGENAME}}/Sug4}}
| + | |
- | | + | |
- | * {{sug|5}} + immediate notification by RCMP, ramp up resources
| + | |
- | ** ack
| + | |
- | {{quote-page|{{PAGENAME}}/Sug6}}
| + | |
- | | + | |
- | === call-out === | + | |
- | * {{sug|7}} wait before rushing to maximize prep time
| + | |
- | ** we're stood down often
| + | |
- | ** not
| + | |
- | * {{sug|8}} be prepared for call out at any time
| + | |
- | ** done
| + | |
- | {{quote-page|{{PAGENAME}}/Sug9}}
| + | |
- | | + | |
- | * {{sug|10}} + had comms between different training sites
| + | |
- | | + | |
- | * {{sug|11}} stage people at the scene
| + | |
- | ack
| + | |
- | | + | |
- | === investigation ===
| + | |
- | * {{sug|12}} + feed into the search manager info from Family, without taking time out from the search
| + | |
- | | + | |
- | === communications ===
| + | |
- | {{quote-page|{{PAGENAME}}/Sug13}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug14}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug15}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug16}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug17}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug18}}
| + | |
- | | + | |
- | * {{sug|19}} level of detail of patient status
| + | |
- | ** privacy
| + | |
- | ** First priority was information. Not guarding communications.
| + | |
- | ** not
| + | |
- | | + | |
- | * {{sug|20}} + had multiple forms of communication
| + | |
- | | + | |
- | {{quote-page|{{PAGENAME}}/Sug21}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug22}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug23}}
| + | |
- | | + | |
- | === resources ===
| + | |
- | {{quote-page|{{PAGENAME}}/Sug24}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug25}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug26}}
| + | |
- | | + | |
- | === family liaison ===
| + | |
- | === (de)briefing ===
| + | |
- | {{quote-page|{{PAGENAME}}/Sug27}}
| + | |
- | | + | |
- | * {{sug|28}} + teams deployed quickly
| + | |
- | ** teams got out quickly when they were tasked.
| + | |
- | | + | |
- | {{quote-page|{{PAGENAME}}/Sug29}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug30}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug31}}
| + | |
- | | + | |
- | === searching ===
| + | |
- | {{quote-page|{{PAGENAME}}/Sug32}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug33}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug34}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug35}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug36}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug37}}
| + | |
- | | + | |
- | | + | |
- | * {{Sug|38}} reinterpretation of assignment. when does a clue become a change of assignment? Could you change assigned search type without confirmation from command.
| + | |
- | ** comes with experience
| + | |
- | | + | |
- | === extrication ===
| + | |
- | {{quote-page|{{PAGENAME}}/Sug39}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug40}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug41}}
| + | |
- | | + | |
- | === access/return from segment ===
| + | |
- | * {{sug|42}} never split team returning from field
| + | |
- | ** training exercise artifact
| + | |
- | | + | |
- | === stand down ===
| + | |
- | {{quote-page|{{PAGENAME}}/Sug43}}
| + | |
- | | + | |
- | === CISM ===
| + | |
- | === prevention, public education ===
| + | |
- | === travel ===
| + | |
- | {{quote-page|{{PAGENAME}}/Sug44}}
| + | |
- | | + | |
- | === planning ===
| + | |
- | {{quote-page|{{PAGENAME}}/Sug45}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug46}}
| + | |
- | | + | |
- | === logistics ===
| + | |
- | {{quote-page|{{PAGENAME}}/Sug47}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug48}}
| + | |
- | * {{sug|49}} assign task through central pt.
| + | |
- | ** incident specific
| + | |
- | ** use safety office
| + | |
- | | + | |
- | * {{sug|50}} Put ambulance on stage, or standby.
| + | |
- | ** previous sug: medical preplan
| + | |
- | | + | |
- | === operations ===
| + | |
- | * {{sug|51}} balancing priorities with multiple subjects
| + | |
- | ** handled appropriate
| + | |
- | | + | |
- | === media ===
| + | |
- | === family ===
| + | |
- | * {{sug|52}} + family liaison
| + | |
- | | + | |
- | === post ops ===
| + | |
- | * {{sug|53}} Nobody should leave until everything is packed up to go. Don't leave until released.
| + | |
- | ** same as before
| + | |
- | | + | |
- | === learning ===
| + | |
- | (e.g., how this critique was organized, mock search goals, exercise techniques)
| + | |
- | | + | |
- | * {{sug|54}} more scenarios
| + | |
- | ** on the mock
| + | |
- | ** not more subjects
| + | |
- | ** command post issue
| + | |
- | | + | |
- | === misc ===
| + | |
- | * {{sug|55}} use the best equipment -> index criteria
| + | |
- | ** not understood
| + | |
- | | + | |
- | * {{sug|56}} get stuff ready sooner, incl. vehicle
| + | |
- | ** covered earlier
| + | |
- | * {{sug|57}} identify & communicate CP
| + | |
- | ** SAR signs on vehicle
| + | |
- | ** low
| + | |
- | {{quote-page|{{PAGENAME}}/Sug58}}
| + | |
- | {{quote-page|{{PAGENAME}}/Sug59}}
| + | |
- | | + | |
- | * {{sug|60}} + accountability at hill
| + | |
- | | + | |
- | * {{sug|61}} Had radio reception, but no phone reception. use mountain safety office.
| + | |
- | ** Knowing in advance where good facilities are at CMR - e.g. command post.
| + | |
- | ** handled
| + | |
Suggestions coming from the March 21, 2010 critique
regarding the March 20 mock search and the March 7 avalanche response.
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.
# | Suggestion | Referred to |
---|
0001 | define level of response | unassigned |
0002 | clarify purpose of task | unassigned |
0003 | on-call person to have call-out list on person - program cell phone | unassigned |
0004 | + delegate to other
- Transfer of command, but didn't let people know.
| unassigned |
0005 | + immediate notification by RCMP, ramp up resources | unassigned |
0006 | orient new RCMP | preplan |
0007 | wait before rushing to maximize prep time
we're stood down often | unassigned |
0008 | be prepared for call out at any time | unassigned |
0009 | develop a preplan for incidents during training | unassigned |
0010 | + had comms between different training sites | unassigned |
0011 | stage people at the scene | unassigned |
0012 | + feed into the search manager info from Family, without taking time out from the search | unassigned |
0013 | precise communications - track description | training |
0014 | + field communication | preplan |
0015 | be clear on understanding - confirm | unassigned |
0016 | too much radio traffic - finish conversation / standby | training |
0017 | Team request of by radio for command post, told to stand by, and then forgotten. | unassigned |
0018 | turn radios off/down at CP
concern about family
feedback
noise | unassigned |
0019 | level of detail of patient status
| unassigned |
0020 | + had multiple forms of communication | unassigned |
0021 | being able to state urgency level of comm | training |
0022 | "Stand by" does not mean stop activity | training |
0023 | Reports to distinguish types of tracks, footprints vs. sleds | preplan |
0024 | getting the stretcher out of the SARCAR was difficult | unassigned |
0025 | Have equipment out and ready | preplan |
0026 | Tied up manager b/c was making sure the trailer was there | equipment |
0027 | include area overview in briefing | unassigned |
0028 | + teams deployed quickly
teams got out quickly when they were tasked. | unassigned |
0029 | avalanche: briefing "scattered" | preplan |
0030 | chain of command unclear, adhoc | preplan |
0031 | use white boards to adapt to different arrival times | unassigned |
0032 | listen to your TL | unassigned |
0033 | tracking - preserve intersection and funnel points | training |
0034 | accountability process (vehicles, houses, etc.) | preplan |
0035 | Keep sharpie in pack to mark tape | training |
0036 | bystanders asking questions | training |
0037 | type 1 search on narrow trail: walk 1 behind the other, 1 look forward, 1 left, 1 right | training |
0038 | reinterpretation of assignment. when does a clue become a change of assignment? Could you change assigned search type without confirmation from command. | unassigned |
0039 | decision making around patient transport | training |
0042 | never split team returning from field | unassigned |
0043 | don't leave until released | unassigned |
0044 | facilitate vehicle access to search site | preplan |
0045 | develop medical response plan at Command Post | preplan |
0046 | use people that know the area, even if family | unassigned |
0047 | assess outside EMS capabilities | unassigned |
0048 | check who was qualified | unassigned |
0049 | assign task through central pt | preplan |
0051 | balancing priorities with multiple subjects | unassigned |
0052 | + family liaison | unassigned |
0053 | Nobody should leave until everything is packed up to go. Don't leave until released. | unassigned |
0054 | more scenarios
on the mock
not more subjects
command post issue | training |
0055 | use the best equipment -> index criteria | unassigned |
0056 | get stuff ready sooner, incl. vehicle | preplan |
0057 | identify & communicate CP | unassigned |
0058 | identify & communicate who's in charge (Incident Commander) | preplan |
0059 | visible identification (vests?) - responders | preplan |
0060 | + accountability at hill | unassigned |
0061 | Had radio reception, but no phone reception. use mountain safety office.
Knowing in advance where good facilities are at CMR - e.g. command post. | unassigned |
[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.
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: none
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: 6, 14, 23, 25, 29, 30, 34, 44, 45, 49, 56, 58, and 59
PCSAR Equipment Committee
Mandate Relevant to Incidents:
- Obtaining and keeping equipment ready.
suggestions identified: 26
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:
suggestions identified: 13, 16, 21, 22, 33, 35, 36, 37, 39, and 54
PCSAR Technology Committee
Mandate Relevant to Incidents:
suggestions identified: none