<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SPOT the problem</title>
	<atom:link href="http://www.kayakquixotica.com/2008/07/31/spot-the-problem/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kayakquixotica.com/2008/07/31/spot-the-problem/</link>
	<description>Tilting At Waves</description>
	<lastBuildDate>Thu, 02 Feb 2012 14:23:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: derrick</title>
		<link>http://www.kayakquixotica.com/2008/07/31/spot-the-problem/comment-page-1/#comment-4854</link>
		<dc:creator>derrick</dc:creator>
		<pubDate>Fri, 01 Aug 2008 14:19:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.kayakquixotica.com/?p=1520#comment-4854</guid>
		<description>Sorry Marius,

Paddlewise is a listserve, so you have to be on the list to get the emails. (You can sign up on the website) That&#039;s why I gave an overview for the sake of the blog.</description>
		<content:encoded><![CDATA[<p>Sorry Marius,</p>
<p>Paddlewise is a listserve, so you have to be on the list to get the emails. (You can sign up on the website) That&#8217;s why I gave an overview for the sake of the blog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marius</title>
		<link>http://www.kayakquixotica.com/2008/07/31/spot-the-problem/comment-page-1/#comment-4851</link>
		<dc:creator>Marius</dc:creator>
		<pubDate>Fri, 01 Aug 2008 12:40:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.kayakquixotica.com/?p=1520#comment-4851</guid>
		<description>I would love to contribute to this conversation, unfortunately I have no idea where to find the story - the &quot;URL&quot; is not very helpful as it points to the root of the website.

Derrick, would you be so kind as to use a bit more precise link next time?</description>
		<content:encoded><![CDATA[<p>I would love to contribute to this conversation, unfortunately I have no idea where to find the story &#8211; the &#8220;URL&#8221; is not very helpful as it points to the root of the website.</p>
<p>Derrick, would you be so kind as to use a bit more precise link next time?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: derrick</title>
		<link>http://www.kayakquixotica.com/2008/07/31/spot-the-problem/comment-page-1/#comment-4850</link>
		<dc:creator>derrick</dc:creator>
		<pubDate>Fri, 01 Aug 2008 11:30:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.kayakquixotica.com/?p=1520#comment-4850</guid>
		<description>TJB - Well put. Knowing how much time it takes to type out a clear and detailed comment I really appreciate it.  Oh, and I agree with your assessment by the way.  There has to be some clear agreements on who does what when.</description>
		<content:encoded><![CDATA[<p>TJB &#8211; Well put. Knowing how much time it takes to type out a clear and detailed comment I really appreciate it.  Oh, and I agree with your assessment by the way.  There has to be some clear agreements on who does what when.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TJB</title>
		<link>http://www.kayakquixotica.com/2008/07/31/spot-the-problem/comment-page-1/#comment-4848</link>
		<dc:creator>TJB</dc:creator>
		<pubDate>Fri, 01 Aug 2008 02:34:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.kayakquixotica.com/?p=1520#comment-4848</guid>
		<description>The way to address this issue is to have a well-established protocol in place as part of your float plan so that those following one&#039;s SPOT know not to call for help just because the SPOT stops transmitting.

Such a protocol recognizes the fact that there are many reasons for an interruption in transmission--mechanical failure, batteries run down, operator forgets to press OK button, inability of operator to have clear view of sky (e.g., waiting out thunderstorm in a cave).

One&#039;s &quot;support team&quot; might view lack of transmission with concern, but hopefully other parts of the float plan then kick in.  For example, if someone stops transmitting a day away from a town from which they had planned to call the team and two days go by without a call, then that likely would be enough to at least alert the authorities.

Finally, I think folks wrongly view the only options as (a) do nothing at the risk of having someone&#039;s loss of life on your conscience or (b) calling in the  rescue squad cavalry.  From limited experience I think there is a third way, namely, calling up the emergency response personnel and sharing your concerns that there has been a sudden lose of SPOT transmissions.  This might prompt them to keep an eye out for the person/people in the field.  They also likely will be willing to work with the support team in deciding when to initiate more intensive rescue efforts (e.g., in example above, when person in field fails to make phone call from nearby town).

In sum, effective use of SPOT requires close attention to one&#039;s float plan and support team.  That extra attention is an inherently good thing and is in my opinion one of the reasons people should give serious consideration to the SPOT device.</description>
		<content:encoded><![CDATA[<p>The way to address this issue is to have a well-established protocol in place as part of your float plan so that those following one&#8217;s SPOT know not to call for help just because the SPOT stops transmitting.</p>
<p>Such a protocol recognizes the fact that there are many reasons for an interruption in transmission&#8211;mechanical failure, batteries run down, operator forgets to press OK button, inability of operator to have clear view of sky (e.g., waiting out thunderstorm in a cave).</p>
<p>One&#8217;s &#8220;support team&#8221; might view lack of transmission with concern, but hopefully other parts of the float plan then kick in.  For example, if someone stops transmitting a day away from a town from which they had planned to call the team and two days go by without a call, then that likely would be enough to at least alert the authorities.</p>
<p>Finally, I think folks wrongly view the only options as (a) do nothing at the risk of having someone&#8217;s loss of life on your conscience or (b) calling in the  rescue squad cavalry.  From limited experience I think there is a third way, namely, calling up the emergency response personnel and sharing your concerns that there has been a sudden lose of SPOT transmissions.  This might prompt them to keep an eye out for the person/people in the field.  They also likely will be willing to work with the support team in deciding when to initiate more intensive rescue efforts (e.g., in example above, when person in field fails to make phone call from nearby town).</p>
<p>In sum, effective use of SPOT requires close attention to one&#8217;s float plan and support team.  That extra attention is an inherently good thing and is in my opinion one of the reasons people should give serious consideration to the SPOT device.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: derrick</title>
		<link>http://www.kayakquixotica.com/2008/07/31/spot-the-problem/comment-page-1/#comment-4847</link>
		<dc:creator>derrick</dc:creator>
		<pubDate>Fri, 01 Aug 2008 00:45:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.kayakquixotica.com/?p=1520#comment-4847</guid>
		<description>I&#039;m not sure we can over-simplify it by assuming everyone is stupid.  They are not.  What they are are friends and families who care about someone.  They are not going to NOT call if they think it&#039;s nessisary. They will always err on the side of caution. You can&#039;t dis them for that.

However, there does probably need to be some communication about what the &quot;ok&quot; should mean.  Adventures should not imply that a lack of checking in is a problem.  There are all sorts of issues and distractions that can cause you not to &quot;check in&quot;.  Together everyone has to agree that in a real emergency only the adventurer will call in the calvary. 

Basically we just have another way to communicate and we&#039;ll have to work out some ground rules but I&#039;m not sure it&#039;s SPOTs problem.  I can think of plenty of silly situations where SAR has been called in just because someone had a dead battery or miscommunicated when they would check in. (long before SPOT) It&#039;s nothing new, just a new, in-expensive way for mis-communications to occur.  I think it sort itself out as people see what can happen.  SPOT would certainly be wise if they would suggest some communication ground rules to their customers.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure we can over-simplify it by assuming everyone is stupid.  They are not.  What they are are friends and families who care about someone.  They are not going to NOT call if they think it&#8217;s nessisary. They will always err on the side of caution. You can&#8217;t dis them for that.</p>
<p>However, there does probably need to be some communication about what the &#8220;ok&#8221; should mean.  Adventures should not imply that a lack of checking in is a problem.  There are all sorts of issues and distractions that can cause you not to &#8220;check in&#8221;.  Together everyone has to agree that in a real emergency only the adventurer will call in the calvary. </p>
<p>Basically we just have another way to communicate and we&#8217;ll have to work out some ground rules but I&#8217;m not sure it&#8217;s SPOTs problem.  I can think of plenty of silly situations where SAR has been called in just because someone had a dead battery or miscommunicated when they would check in. (long before SPOT) It&#8217;s nothing new, just a new, in-expensive way for mis-communications to occur.  I think it sort itself out as people see what can happen.  SPOT would certainly be wise if they would suggest some communication ground rules to their customers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

