Editing Critiques/2009-05-05

From PCSAR

Revision as of 02:50, 20 May 2009 by 192.168.23.77 (Talk)

(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)

WARNING: You are editing an out-of-date revision of this page. If you save it, any changes made since this revision will be lost.

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

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.

== 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: {{SugRef|1}}

=== 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: {{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 ===
Mandate Relevant to Incidents:
* Obtaining and keeping equipment ready.
suggestions identified: {{SugRef|4}}
=== PCSAR Call-Out Committee ===
Mandate Relevant to Incidents:
* Respond to First Call from Tasking Agency
* Contacting members during an incident.
suggestions identified: {{SugRef|1}}, {{SugRef|2}}
=== PCSAR Membership Committee ===
Mandate Relevant to Incidents:
* Recruiting members.
* Tracking members contact information, skills and equipment.
suggestions identified: {{SugRef|1}}, {{SugRef|2}}
=== PCSAR Training Committee ===
Mandate Relevant to Incidents:
* Training members.
suggestions identified: {{SugRef|3}}, {{SugRef|12}}, {{SugRef|13}}, {{SugRef|14}}, {{SugRef|15}}, {{SugRef|16}}, {{SugRef|19}}, {{SugRef|20}}, {{SugRef|21}}
=== Tasking Agency ===
Mandate Relevant to Incidents:
* Overall legal responsibility for incident.
suggestions identified: {{SugRef|8}}
=== Fellow Responding Organizations ===
Mandate Relevant to Incidents:
* Response to incident in accordance with their individual mandate and ability.
suggestions identified: none

== Suggestions by functional area ==
=== first notification / tasking ===
=== call-out ===

* {{sug|1}} 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.

** preplan 2009-05-19
*** Good to have on-call caller.  
*** Use regular members to fill in gaps for on-call caller.  Refer to training. 
*** Easy to recruit for (e.g. high schoolers).

* {{sug|2}} 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.

** preplan 2009-05-19
*** Have current information on the web site. 
*** Reorganize list to be more user friendly.  Sub lists?
**** plan a larger discussion with call-out people.

=== investigation ===
=== communications ===

* {{sug|3}} 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.
** preplan 2009-05-19
*** need clear language of team designations, designation of combined team
*** need clear designation of combined team leader

=== resources ===

* {{sug|4}} Suggest get gel pens which won't freeze.

=== family liaison ===
=== (de)briefing ===

* {{sug|5}} Map becoming available only after given assignment relative to locations is sometimes confusing.  Suggest map orientation should be first.
** preplan 2009-05-19
*** Come up with a standard format for briefing.  Develop check list.

* {{sug|6}} Debriefing forms don't match urban context.  Suggest rework wording.
** preplan 2009-05-19
*** add vehicle as type of team
*** critical spacing only applies to Type II or Type III
*** need training for the debriefer

=== searching ===

* {{sug|7}} Suggest have minimum of 2 people approach door for member safety and to give assurance of legitimacy to resident.
** preplan 2009-05-19
*** Reflective vests or anything to show that we are not prowlers.  Needs to be stressed don't fall into trap of assuming everyone recognizes we are there to help.

* {{sug|8}} 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.
** preplan 2009-05-19
*** probably not enough vehicles available from police
*** would not work well with many yards, too many fences, too high
*** risk to night vision
*** risk of people walking beside vehicle
*** not effective back alleys

* {{sug|9}} Suggest having roving support vehicle for urban search teams for food, water, warming, transport.
** preplan 2009-05-19
*** effective for shifting priorities
*** access to washroom facilities
*** yellow flashing light would highten awareness that something is having, magnetic search and rescue decals

* {{sug|10}} Suggest mark sidewalk with chalk in urban search to indicate what has/hasn't been searched by which team.  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.
** preplan 2009-05-19
*** difficult to recognize from other end

* {{sug|11}} 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.
** preplan 2009-05-19
*** agreed

* {{sug|12}} 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.
** preplan 2009-05-19
*** should be brought up during training
*** remind overhead to plan on macro scale

* {{sug|13}} 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.
** preplan 2009-05-19
*** a quick burst doesn't need to be communicated
**** should be reported in debriefing
*** a diversion or abandoning original assignment doesn't
*** training issue

* {{sug|14}} Suggest when spotting subject, maintain visual contact until part of party approaches.  Can lose perspective as approach.
** preplan 2009-05-19
*** should be brought up during training

=== extrication ===

* {{sug|15}} Having many people approach Alzheimer sufferer likely to cause trauma.

* {{sug|16}} Suggest use rope as tag line when extracting stretcher on slope.

=== stand down ===
=== CISM ===
=== prevention, public education ===
=== travel ===

* {{sug|17}} Suggest continued use of carpooling to search in e.g. Lethbridge.  Better safety on way back when tired.

* {{sug|18}} Suggest having arrangement to call-in when driving alone back from a tiring search (e.g. night search).  To confirm safe arrival.

=== logistics ===
=== planning ===
=== media ===
=== post ops ===
=== learning ===
(e.g., how this critique was organized, mock search goals, exercise techniques)

* {{sug|19}} Suggest encourage members in field to discuss overhead decisions after search as learning opportunity.

* {{sug|20}} Suggest everyone get experience of working comms and command post.

* {{sug|21}} Suggest better learning if everyone can see handling of first approach to subject.

Please note that all contributions to PCSAR are considered to be released under the Attribution-Share Alike 3.0 Unported (see PCSAR:Copyrights for details). If you don't want your writing to be edited mercilessly and redistributed at will, then don't submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. DO NOT SUBMIT COPYRIGHTED WORK WITHOUT PERMISSION!

Summary:

Cancel | Editing help (opens in new window)

Templates used on this page:

Retrieved from "http://pcsar.dyndns.org/mediawiki/index.php/Critiques/2009-05-05"

Editing Critiques/2009-05-05

From PCSAR

Views

Personal tools

Navigation

Search

Toolbox