<?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: The Anatomy of Allisions</title>
	<atom:link href="http://gcaptain.com/the-anatomy-of-allisions/feed/" rel="self" type="application/rss+xml" />
	<link>http://gcaptain.com/the-anatomy-of-allisions/?1153</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 23:08:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: The Anatomy of Allisions [ GCaptain ]</title>
		<link>http://gcaptain.com/the-anatomy-of-allisions/?1153#comment-11850</link>
		<dc:creator>The Anatomy of Allisions [ GCaptain ]</dc:creator>
		<pubDate>Sat, 07 Jun 2008 19:28:37 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/the-anatomy-of-allisions/#comment-11850</guid>
		<description>[...] 21st 2008 10:57am  [-] From: gcaptain.com  [...]</description>
		<content:encoded><![CDATA[<p>[...] 21st 2008 10:57am  [-] From: gcaptain.com  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OneEighteen</title>
		<link>http://gcaptain.com/the-anatomy-of-allisions/?1153#comment-7050</link>
		<dc:creator>OneEighteen</dc:creator>
		<pubDate>Fri, 22 Feb 2008 17:42:28 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/the-anatomy-of-allisions/#comment-7050</guid>
		<description>&quot;managers and supervisory persons must be held responsible to verify that the requirements of the regulations, rules and procedures have been met&quot;

Oh, boy.  Another ream of paperwork to be filled out by the mates and captain.  

One of the problems we face in the industry today is nonsense requirements from a host of people who have never navigated a vessel in their lives and who are trying to cover every inch of their ass with a memo and a signature.

An example:  On many ships a mate is now assigned to record in a logbook the number and time each buoy in the channel is passed.  With over 50 pairs of beacons in a 30 mile stretch of Galveston Bay the mate is constantly engaged in this task and unavailable for anything useful.  He/she is not effectively monitoring the progress of the transit, is not learning any shiphandling skills, and (at night) is a nuisance running around turning on and off lights, parting darken bridge curtains,  and generally preventing everyone else on the bridge from fully becoming adjusted to night navigation. 
Safety would be better served by having a mate doing his duty &quot;in the ordinary practice of seamen&quot; instead of complying with a CYA requirement from some distant dock-wholloper who has never been to sea.</description>
		<content:encoded><![CDATA[<p>&#8220;managers and supervisory persons must be held responsible to verify that the requirements of the regulations, rules and procedures have been met&#8221;</p>
<p>Oh, boy.  Another ream of paperwork to be filled out by the mates and captain.  </p>
<p>One of the problems we face in the industry today is nonsense requirements from a host of people who have never navigated a vessel in their lives and who are trying to cover every inch of their ass with a memo and a signature.</p>
<p>An example:  On many ships a mate is now assigned to record in a logbook the number and time each buoy in the channel is passed.  With over 50 pairs of beacons in a 30 mile stretch of Galveston Bay the mate is constantly engaged in this task and unavailable for anything useful.  He/she is not effectively monitoring the progress of the transit, is not learning any shiphandling skills, and (at night) is a nuisance running around turning on and off lights, parting darken bridge curtains,  and generally preventing everyone else on the bridge from fully becoming adjusted to night navigation.<br />
Safety would be better served by having a mate doing his duty &#8220;in the ordinary practice of seamen&#8221; instead of complying with a CYA requirement from some distant dock-wholloper who has never been to sea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OneEighteen</title>
		<link>http://gcaptain.com/the-anatomy-of-allisions/?1153#comment-13651</link>
		<dc:creator>OneEighteen</dc:creator>
		<pubDate>Fri, 22 Feb 2008 14:42:28 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/the-anatomy-of-allisions/#comment-13651</guid>
		<description>&quot;managers and supervisory persons must be held responsible to verify that the requirements of the regulations, rules and procedures have been met&quot;&lt;br&gt;&lt;br&gt;Oh, boy.  Another ream of paperwork to be filled out by the mates and captain.  &lt;br&gt;&lt;br&gt;One of the problems we face in the industry today is nonsense requirements from a host of people who have never navigated a vessel in their lives and who are trying to cover every inch of their ass with a memo and a signature.&lt;br&gt;&lt;br&gt;An example:  On many ships a mate is now assigned to record in a logbook the number and time each buoy in the channel is passed.  With over 50 pairs of beacons in a 30 mile stretch of Galveston Bay the mate is constantly engaged in this task and unavailable for anything useful.  He/she is not effectively monitoring the progress of the transit, is not learning any shiphandling skills, and (at night) is a nuisance running around turning on and off lights, parting darken bridge curtains,  and generally preventing everyone else on the bridge from fully becoming adjusted to night navigation. &lt;br&gt;Safety would be better served by having a mate doing his duty &quot;in the ordinary practice of seamen&quot; instead of complying with a CYA requirement from some distant dock-wholloper who has never been to sea.</description>
		<content:encoded><![CDATA[<p>&#8220;managers and supervisory persons must be held responsible to verify that the requirements of the regulations, rules and procedures have been met&#8221;</p>
<p>Oh, boy.  Another ream of paperwork to be filled out by the mates and captain.  </p>
<p>One of the problems we face in the industry today is nonsense requirements from a host of people who have never navigated a vessel in their lives and who are trying to cover every inch of their ass with a memo and a signature.</p>
<p>An example:  On many ships a mate is now assigned to record in a logbook the number and time each buoy in the channel is passed.  With over 50 pairs of beacons in a 30 mile stretch of Galveston Bay the mate is constantly engaged in this task and unavailable for anything useful.  He/she is not effectively monitoring the progress of the transit, is not learning any shiphandling skills, and (at night) is a nuisance running around turning on and off lights, parting darken bridge curtains,  and generally preventing everyone else on the bridge from fully becoming adjusted to night navigation. <br />Safety would be better served by having a mate doing his duty &#8220;in the ordinary practice of seamen&#8221; instead of complying with a CYA requirement from some distant dock-wholloper who has never been to sea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Denham</title>
		<link>http://gcaptain.com/the-anatomy-of-allisions/?1153#comment-7034</link>
		<dc:creator>John Denham</dc:creator>
		<pubDate>Thu, 21 Feb 2008 16:15:09 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/the-anatomy-of-allisions/#comment-7034</guid>
		<description>In my pulished blog on tugs and bridges  a graphic did not come through. What was portrayed is the assumed make up of the two tugs and the barge (tandem)  to comprise  a 628 foot flotilla. Included was  an estimate of the salt water displacement tonnage of the three units. One should view the displacement comparison of the two tugs to the barge and consider the effect of the current. On a near similar transit with a very large floating oil rig  and three,  much less capable tugs,  it was exciting. JGD</description>
		<content:encoded><![CDATA[<p>In my pulished blog on tugs and bridges  a graphic did not come through. What was portrayed is the assumed make up of the two tugs and the barge (tandem)  to comprise  a 628 foot flotilla. Included was  an estimate of the salt water displacement tonnage of the three units. One should view the displacement comparison of the two tugs to the barge and consider the effect of the current. On a near similar transit with a very large floating oil rig  and three,  much less capable tugs,  it was exciting. JGD</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Denham</title>
		<link>http://gcaptain.com/the-anatomy-of-allisions/?1153#comment-13650</link>
		<dc:creator>John Denham</dc:creator>
		<pubDate>Thu, 21 Feb 2008 13:15:09 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/the-anatomy-of-allisions/#comment-13650</guid>
		<description>In my pulished blog on tugs and bridges  a graphic did not come through. What was portrayed is the assumed make up of the two tugs and the barge (tandem)  to comprise  a 628 foot flotilla. Included was  an estimate of the salt water displacement tonnage of the three units. One should view the displacement comparison of the two tugs to the barge and consider the effect of the current. On a near similar transit with a very large floating oil rig  and three,  much less capable tugs,  it was exciting. JGD</description>
		<content:encoded><![CDATA[<p>In my pulished blog on tugs and bridges  a graphic did not come through. What was portrayed is the assumed make up of the two tugs and the barge (tandem)  to comprise  a 628 foot flotilla. Included was  an estimate of the salt water displacement tonnage of the three units. One should view the displacement comparison of the two tugs to the barge and consider the effect of the current. On a near similar transit with a very large floating oil rig  and three,  much less capable tugs,  it was exciting. JGD</p>
]]></content:encoded>
	</item>
</channel>
</rss>

