Critiques/2010-03-21

From PCSAR

< Critiques(Difference between revisions)
Jump to: navigation, search
(→communications)
Current revision (05:55, 16 April 2014) (edit) (undo)
 
(37 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}}
+
-
 
+
-
* {{sug|17}} Team's request of contact and then forgotten.
+
-
** med - train for radio operator
+
-
 
+
-
* {{sug|18}} turn radios off/down at CP
+
-
** concern about family
+
-
** feedback
+
-
** noise
+
-
** med
+
-
 
+
-
* {{sug|19}} level of detail of patient status
+
-
** privacy
+
-
** First priority was information. Not guarding communications.
+
-
** not
+
-
 
+
-
* {{sug|20}} + had multiple forms of communication
+
-
 
+
-
 
+
-
* {{sug|21}} being able to state urgency level of comm.
+
-
** med: train "break"
+
-
 
+
-
* {{sug|22}} "Stand by" does not mean stop activity.
+
-
** med: training
+
-
 
+
-
* {{sug|23}} Reports to distinguish types of tracks, footprints vs. sleds.
+
-
** repeat
+
-
 
+
-
=== resources ===
+
-
{{quote-page|{{PAGENAME}}/Sug24}}
+
-
{{quote-page|{{PAGENAME}}/Sug25}}
+
-
{{quote-page|{{PAGENAME}}/Sug26}}
+
-
 
+
-
=== family liaison ===
+
-
=== (de)briefing ===
+
-
* {{sug|27}} include area overview in briefing
+
-
** land owner give briefing to all teams of the lay of the land.
+
-
** clues missed, perhaps b/c not briefed by the family member
+
-
** how do we evaluate family as resource?
+
-
** low
+
-
* {{sug|28}} + teams deployed quickly
+
-
** teams got out quickly when they were tasked.
+
-
 
+
-
{{quote-page|{{PAGENAME}}/Sug29}}
+
-
{{quote-page|{{PAGENAME}}/Sug30}}
+
-
 
+
-
* {{sug|31}} use white boards to adapt to different arrival times
+
-
** trailer not available
+
-
** white sheets in overhead box
+
-
** low
+
-
 
+
-
=== searching ===
+
-
* {{sug|32}} listen to your TL
+
-
** obvious, low
+
-
* {{sug|33}} tracking - preserve intersection and funnel points
+
-
** when tracking, when coming to intersection, gate, check natural traps, gates, etc. check for sign before going in.
+
-
** training objective
+
-
** high
+
-
 
+
-
{{quote-page|{{PAGENAME}}/Sug34}}
+
-
 
+
-
* {{Sug|35}} Keep sharpie in pack to mark tape.
+
-
** training: low
+
-
 
+
-
* {{Sug|36}} bystanders asking questions.
+
-
** training: low
+
-
** need higher trained person as TL, would know to send to contact.
+
-
 
+
-
* {{Sug|37}} walking 1 behind the other,
+
-
** training: med
+
-
 
+
-
* {{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 ===
+
-
 
+
-
* {{sug|39}} decision making around patient transport
+
-
** judgement call
+
-
** training: more practice with these scenarios
+
-
** high
+
-
* {{sug|40}} protocol for subject movement
+
-
** same as 39
+
-
* {{sug|41}} Need training on medical decision making in the field.
+
-
** same as 39
+
-
 
+
-
=== access/return from segment ===
+
-
* {{sug|42}} never split team returning from field
+
-
** training exercise artifact
+
-
 
+
-
=== stand down ===
+
-
* {{sug|43}} don't leave until released
+
-
** low
+
-
 
+
-
=== CISM ===
+
-
=== prevention, public education ===
+
-
=== travel ===
+
-
* {{sug|44}} facilitate vehicle access
+
-
** shutdown highway to get SAR teams into resort
+
-
** difficulty of dust
+
-
** tasking agency
+
-
 
+
-
=== planning ===
+
-
{{quote-page|{{PAGENAME}}/Sug45}}
+
-
 
+
-
* {{sug|46}} use people that know the area, even if family
+
-
** search management team reluctant to use land owner because he was also family member. Very useful to use people that know area. Could have explained roads and trails. Transport.
+
-
** overhead team discuss how much to include family members
+
-
** be prepared to deal with consquences of including family
+
-
* previous
+
-
 
+
-
=== logistics ===
+
-
 
+
-
* {{sug|47}} assess outside EMS capabilities
+
-
** are they able to travel into site
+
-
** discuss ahead of time with PCES
+
-
** med
+
-
 
+
-
* {{sug|48}} check who was qualified
+
-
** track which level of medical training available.
+
-
** low
+
-
 
+
-
* {{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
+

Current revision

This page is based on the Critique report template.

Use that template to make similar pages.

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.

Contents

[hide]

[edit] Participants

[edit] Rough notes

[edit] Suggestions

#  ↓Suggestion  ↓Referred to  ↓
0001define level of responseunassigned
0002clarify purpose of taskunassigned
0003on-call person to have call-out list on person - program cell phoneunassigned
0004+ delegate to other
    • Transfer of command, but didn't let people know.
unassigned
0005+ immediate notification by RCMP, ramp up resourcesunassigned
0006orient new RCMPpreplan
0007wait before rushing to maximize prep time
  • we're stood down often
    		• unassigned
    0008be prepared for call out at any timeunassigned
    0009develop a preplan for incidents during trainingunassigned
    0010+ had comms between different training sitesunassigned
    0011stage people at the sceneunassigned
    0012+ feed into the search manager info from Family, without taking time out from the searchunassigned
    0013precise communications - track descriptiontraining
    0014+ field communicationpreplan
    0015be clear on understanding - confirmunassigned
    0016too much radio traffic - finish conversation / standbytraining
    0017Team request of by radio for command post, told to stand by, and then forgotten.unassigned
    0018turn radios off/down at CP
  • concern about family
  • feedback
  • noise
    		• unassigned
    0019level of detail of patient status
    • privacy
    		unassigned
    0020+ had multiple forms of communicationunassigned
    0021being able to state urgency level of commtraining
    0022"Stand by" does not mean stop activitytraining
    0023Reports to distinguish types of tracks, footprints vs. sledspreplan
    0024getting the stretcher out of the SARCAR was difficultunassigned
    0025Have equipment out and readypreplan
    0026Tied up manager b/c was making sure the trailer was thereequipment
    0027include area overview in briefingunassigned
    0028+ teams deployed quickly
  • teams got out quickly when they were tasked.
    		• unassigned
    0029avalanche: briefing "scattered"preplan
    0030chain of command unclear, adhocpreplan
    0031use white boards to adapt to different arrival timesunassigned
    0032listen to your TLunassigned
    0033tracking - preserve intersection and funnel pointstraining
    0034accountability process (vehicles, houses, etc.)preplan
    0035Keep sharpie in pack to mark tapetraining
    0036bystanders asking questionstraining
    0037type 1 search on narrow trail: walk 1 behind the other, 1 look forward, 1 left, 1 righttraining
    0038reinterpretation of assignment. when does a clue become a change of assignment? Could you change assigned search type without confirmation from command.unassigned
    0039decision making around patient transporttraining
    0042never split team returning from fieldunassigned
    0043don't leave until releasedunassigned
    0044facilitate vehicle access to search sitepreplan
    0045develop medical response plan at Command Postpreplan
    0046use people that know the area, even if familyunassigned
    0047assess outside EMS capabilitiesunassigned
    0048check who was qualifiedunassigned
    0049assign task through central ptpreplan
    0051balancing priorities with multiple subjectsunassigned
    0052+ family liaisonunassigned
    0053Nobody should leave until everything is packed up to go. Don't leave until released.unassigned
    0054more scenarios
  • on the mock
  • not more subjects
  • command post issue
    		• training
    0055use the best equipment -> index criteriaunassigned
    0056get stuff ready sooner, incl. vehiclepreplan
    0057identify & communicate CPunassigned
    0058identify & communicate who's in charge (Incident Commander)preplan
    0059visible identification (vests?) - responderspreplan
    0060+ accountability at hillunassigned
    0061Had radio reception, but no phone reception. use mountain safety office.
  • Knowing in advance where good facilities are at CMR - e.g. command post.
    		• unassigned
    [refresh]
    New suggestion #62

    [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:

    • Training members.

    suggestions identified: 13, 16, 21, 22, 33, 35, 36, 37, 39, and 54

    PCSAR Technology Committee

    Mandate Relevant to Incidents:

    • Technology support

    suggestions identified: none

    Retrieved from "http://pcsar.dyndns.org/mediawiki/index.php/Critiques/2010-03-21"
    Personal tools