<?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: Pilotage Paradox &#8211; A Look Into The Cosco Busan Allision</title>
	<atom:link href="http://gcaptain.com/pilotage-paradox/feed/" rel="self" type="application/rss+xml" />
	<link>http://gcaptain.com/pilotage-paradox/?2484</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: SPOT Messenger Contest - The Results Are In!</title>
		<link>http://gcaptain.com/pilotage-paradox/?2484#comment-14234</link>
		<dc:creator>SPOT Messenger Contest - The Results Are In!</dc:creator>
		<pubDate>Wed, 08 Oct 2008 18:10:26 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=2484#comment-14234</guid>
		<description>[...] Kurt for his comment on Pilotage Paradox - A Look Into The Cosco Busan Allision [...]</description>
		<content:encoded><![CDATA[<p>[...] Kurt for his comment on Pilotage Paradox &#8211; A Look Into The Cosco Busan Allision [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: henningp</title>
		<link>http://gcaptain.com/pilotage-paradox/?2484#comment-20922</link>
		<dc:creator>henningp</dc:creator>
		<pubDate>Thu, 25 Sep 2008 16:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=2484#comment-20922</guid>
		<description>Fact is that most pilots do not care a sh... about the OOW but require Master to talk to.&lt;br&gt;Bad habit, but well, what to expect if masters still instruct their mates to be called before course changes (even for collision avoidance on high seas).... and of course the mates do show themselves accordingly confident!</description>
		<content:encoded><![CDATA[<p>Fact is that most pilots do not care a sh&#8230; about the OOW but require Master to talk to.<br />Bad habit, but well, what to expect if masters still instruct their mates to be called before course changes (even for collision avoidance on high seas)&#8230;. and of course the mates do show themselves accordingly confident!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: henningp</title>
		<link>http://gcaptain.com/pilotage-paradox/?2484#comment-14143</link>
		<dc:creator>henningp</dc:creator>
		<pubDate>Thu, 25 Sep 2008 09:32:55 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=2484#comment-14143</guid>
		<description>Fact is that most pilots do not care a sh... about the OOW but require Master to talk to.&lt;br&gt;Bad habit, but well, what to expect if masters still instruct their mates to be called before course changes (even for collision avoidance on high seas).... and of course the mates do show themselves accordingly confident!</description>
		<content:encoded><![CDATA[<p>Fact is that most pilots do not care a sh&#8230; about the OOW but require Master to talk to.<br />Bad habit, but well, what to expect if masters still instruct their mates to be called before course changes (even for collision avoidance on high seas)&#8230;. and of course the mates do show themselves accordingly confident!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cosco Busan Update &#124; Bob Couttie's Maritime Accident Casebook</title>
		<link>http://gcaptain.com/pilotage-paradox/?2484#comment-14110</link>
		<dc:creator>Cosco Busan Update &#124; Bob Couttie's Maritime Accident Casebook</dc:creator>
		<pubDate>Fri, 19 Sep 2008 18:18:30 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=2484#comment-14110</guid>
		<description>[...] we recently had the privilege to reprint an article Paul Drouin wrote for Seaways magazine. (LINK: http://gcaptain.com/maritime/blog/pilotage-paradox/ [...]</description>
		<content:encoded><![CDATA[<p>[...] we recently had the privilege to reprint an article Paul Drouin wrote for Seaways magazine. (LINK: http://gcaptain.com/maritime/blog/pilotage-paradox/ [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kurt</title>
		<link>http://gcaptain.com/pilotage-paradox/?2484#comment-14105</link>
		<dc:creator>Kurt</dc:creator>
		<pubDate>Fri, 19 Sep 2008 13:43:37 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=2484#comment-14105</guid>
		<description>Thanks for the article.  I made a quick movie out of the radar images in the NTSB report...&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://schwehr.org/blog/archives/2008-09.html#e2008-09-19T10_39_48.txt&quot;&gt;http://schwehr.org/blog/archives/2008-09.html#e...&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Thanks for the article.  I made a quick movie out of the radar images in the NTSB report&#8230;</p>
<p><a href="http://schwehr.org/blog/archives/2008-09.html#e2008-09-19T10_39_48.txt">http://schwehr.org/blog/archives/2008-09.html#e&#8230;</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://gcaptain.com/pilotage-paradox/?2484#comment-14097</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Fri, 19 Sep 2008 09:59:09 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=2484#comment-14097</guid>
		<description>Brisbane has found a way to include the OOW as a functional member of the team. As each pilotage area is different, their own solutions may also be different. However, they must all find a way to function as a team.</description>
		<content:encoded><![CDATA[<p>Brisbane has found a way to include the OOW as a functional member of the team. As each pilotage area is different, their own solutions may also be different. However, they must all find a way to function as a team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://gcaptain.com/pilotage-paradox/?2484#comment-14098</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Fri, 19 Sep 2008 09:52:07 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=2484#comment-14098</guid>
		<description>John,&lt;br&gt;&lt;br&gt;I don&#039;t quite understand what you mean when you say, &quot;Under keel clearance does have a maneuvering effect in current and changing water depths, but not relevant in this case. Using only NTSB data at time 08 27 37 Cosco Busan has no feasible alternative course change to the right.&quot;&lt;br&gt;&lt;br&gt;My point was, as the CB came to port (and then, of course, too much so), the tidal current would push on the ship with greater force (and hence send it off the intended course faster) with low UKC than if UKC had been greater. All of this contributing to the loss of situational awareness of the bridge team - i.e.&quot;where are we now?&quot;</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>I don&#39;t quite understand what you mean when you say, &#8220;Under keel clearance does have a maneuvering effect in current and changing water depths, but not relevant in this case. Using only NTSB data at time 08 27 37 Cosco Busan has no feasible alternative course change to the right.&#8221;</p>
<p>My point was, as the CB came to port (and then, of course, too much so), the tidal current would push on the ship with greater force (and hence send it off the intended course faster) with low UKC than if UKC had been greater. All of this contributing to the loss of situational awareness of the bridge team &#8211; i.e.&#8221;where are we now?&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Denham</title>
		<link>http://gcaptain.com/pilotage-paradox/?2484#comment-14094</link>
		<dc:creator>John Denham</dc:creator>
		<pubDate>Fri, 19 Sep 2008 04:38:11 +0000</pubDate>
		<guid isPermaLink="false">http://gcaptain.com/maritime/blog/?p=2484#comment-14094</guid>
		<description>The pardox is concurred in however the explanation appears incomplete. The &quot;root cause&quot; is failure to comply with existing regulations, and an interpretation of who is directing the navigation of the vessel; an employed pilot not a ship’s officer or a ship’s officer licensed to pilot. (33CFR Part 164.11). Compulsory pilotage standards for duties and responsibility of &quot;pilots in charge of a vessel&quot; have been legally established in Atlee v N.W. Packet Co., (1874) ,88 U.S. 389, 22l.ed. 619.&lt;br&gt;&lt;br&gt;By law, custom, tradition and attitude many pilots that have not experienced the courts continue to perform as &quot;one man shows.&quot; However one must recognize the difference between a river pilot and a bar/harbor pilot: e.g navigating the San Francisco Bar Channel and the ports on San Francisco Bay and the pilots that navigate to Sacramento and Stockton, California. Hearings, inquiries and investigation seldom develop the &quot;root cause&quot; of accidents because they have limited experience, knowledge and mostly are guided by bureaucratic constraints and therefore if fault is found, send the culprit to ship handling training. Why, because there is no other appropriate remedy available.&lt;br&gt;&lt;br&gt;The statement that transiting the Oakland Bar Channel is a &quot;relatively simple matter&quot; is misleading in that the bar channel is nearly perpendicular to the currents and the published predictions are frequently inaccurate. Therefore, in limited visibility the person directing the navigation must rely on radar navigation to determine set and drift. Also, as one transits the bar channel the effect of the current changes. Experience in this case dictates: in fog, concentrate on radar navigation.&lt;br&gt;&lt;br&gt;Regardless, no one knows what actually occurred except the Captain of COSCO BUSAN and pilot Cota i,e: why so many rudder orders? What passage plan was discussed? Was the track plotted on the chart 588 accepted by the pilot and Master? The NTSB hearing produced exceptional testimony and information however, no analysis or report has been produced, but professional mariners and second guessers have theories.&lt;br&gt;&lt;br&gt;Under keel clearance does have a maneuvering effect in current and changing water depths, but not relevant in this case. Using only NTSB data at time 08 27 37 Cosco Busan has no feasible alternative course change to the right.&lt;br&gt;&lt;br&gt;Most importantly, is the mostly common practice of pilots and ships not using BRM as a safety feature in voyages and navigation practice. The non-functional practice of BRM is concurred in. Although taught, stressed and published it is not universally followed; and now the cause is known!&lt;br&gt;&lt;br&gt;Lastly as I recall, Brisbane Australia has a relatively calm and secured bay for pilot operations that allow discussion. Not so on at the sea boarding stations at some west coast pilot stations, however there is no rule that demand full speed till otherwise required.&lt;br&gt;&lt;br&gt;Essentially, if the BRM is to be accepted and function then the professional pilots must be implementers. JGD</description>
		<content:encoded><![CDATA[<p>The pardox is concurred in however the explanation appears incomplete. The &#8220;root cause&#8221; is failure to comply with existing regulations, and an interpretation of who is directing the navigation of the vessel; an employed pilot not a ship’s officer or a ship’s officer licensed to pilot. (33CFR Part 164.11). Compulsory pilotage standards for duties and responsibility of &#8220;pilots in charge of a vessel&#8221; have been legally established in Atlee v N.W. Packet Co., (1874) ,88 U.S. 389, 22l.ed. 619.</p>
<p>By law, custom, tradition and attitude many pilots that have not experienced the courts continue to perform as &#8220;one man shows.&#8221; However one must recognize the difference between a river pilot and a bar/harbor pilot: e.g navigating the San Francisco Bar Channel and the ports on San Francisco Bay and the pilots that navigate to Sacramento and Stockton, California. Hearings, inquiries and investigation seldom develop the &#8220;root cause&#8221; of accidents because they have limited experience, knowledge and mostly are guided by bureaucratic constraints and therefore if fault is found, send the culprit to ship handling training. Why, because there is no other appropriate remedy available.</p>
<p>The statement that transiting the Oakland Bar Channel is a &#8220;relatively simple matter&#8221; is misleading in that the bar channel is nearly perpendicular to the currents and the published predictions are frequently inaccurate. Therefore, in limited visibility the person directing the navigation must rely on radar navigation to determine set and drift. Also, as one transits the bar channel the effect of the current changes. Experience in this case dictates: in fog, concentrate on radar navigation.</p>
<p>Regardless, no one knows what actually occurred except the Captain of COSCO BUSAN and pilot Cota i,e: why so many rudder orders? What passage plan was discussed? Was the track plotted on the chart 588 accepted by the pilot and Master? The NTSB hearing produced exceptional testimony and information however, no analysis or report has been produced, but professional mariners and second guessers have theories.</p>
<p>Under keel clearance does have a maneuvering effect in current and changing water depths, but not relevant in this case. Using only NTSB data at time 08 27 37 Cosco Busan has no feasible alternative course change to the right.</p>
<p>Most importantly, is the mostly common practice of pilots and ships not using BRM as a safety feature in voyages and navigation practice. The non-functional practice of BRM is concurred in. Although taught, stressed and published it is not universally followed; and now the cause is known!</p>
<p>Lastly as I recall, Brisbane Australia has a relatively calm and secured bay for pilot operations that allow discussion. Not so on at the sea boarding stations at some west coast pilot stations, however there is no rule that demand full speed till otherwise required.</p>
<p>Essentially, if the BRM is to be accepted and function then the professional pilots must be implementers. JGD</p>
]]></content:encoded>
	</item>
</channel>
</rss>

