Comments on: Independent Panel Releases Report on Cosco Busan http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/ A Blog About Ships Sat, 20 Mar 2010 21:40:03 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: john Denham http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/comment-page-1/#comment-6739 john Denham Mon, 04 Feb 2008 14:59:21 +0000 http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/#comment-6739 The present ISPR report as I understand is part1 of 2 reports. I found the brief timeline in the introduction-summary to be inconsistant with the animation and navigational data. With the 0827- 0831 animation I found further conflicts with the probable scenario. The present ISPR report as I understand is part1 of 2 reports. I found the brief timeline in the introduction-summary to be inconsistant with the animation and navigational data. With the 0827- 0831 animation I found further conflicts with the probable scenario.

]]> By: john Denham http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/comment-page-1/#comment-6740 john Denham Mon, 04 Feb 2008 14:59:21 +0000 http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/#comment-6740 The present ISPR report as I understand is part1 of 2 reports. I found the brief timeline in the introduction-summary to be inconsistant with the animation and navigational data. With the 0827- 0831 animation I found further conflicts with the probable scenario. The present ISPR report as I understand is part1 of 2 reports. I found the brief timeline in the introduction-summary to be inconsistant with the animation and navigational data. With the 0827- 0831 animation I found further conflicts with the probable scenario.

]]> By: john Denham http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/comment-page-1/#comment-13593 john Denham Mon, 04 Feb 2008 11:59:21 +0000 http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/#comment-13593 The present ISPR report as I understand is part1 of 2 reports. I found the brief timeline in the introduction-summary to be inconsistant with the animation and navigational data. With the 0827- 0831 animation I found further conflicts with the probable scenario. The present ISPR report as I understand is part1 of 2 reports. I found the brief timeline in the introduction-summary to be inconsistant with the animation and navigational data. With the 0827- 0831 animation I found further conflicts with the probable scenario.

]]> By: john Denham http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/comment-page-1/#comment-13594 john Denham Mon, 04 Feb 2008 11:59:21 +0000 http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/#comment-13594 The present ISPR report as I understand is part1 of 2 reports. I found the brief timeline in the introduction-summary to be inconsistant with the animation and navigational data. With the 0827- 0831 animation I found further conflicts with the probable scenario. The present ISPR report as I understand is part1 of 2 reports. I found the brief timeline in the introduction-summary to be inconsistant with the animation and navigational data. With the 0827- 0831 animation I found further conflicts with the probable scenario.

]]> By: reader http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/comment-page-1/#comment-6710 reader Sun, 03 Feb 2008 04:05:56 +0000 http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/#comment-6710 There is a reasonably good timed animation showing the the period 08:28:52 PST - 08:31:37 PST here: http://s3.amazonaws.com/gcaptain-s3/maritime/video/dec07/CB_Thru_Span_2_dbl-Desktop.m4v as explained here: Cosco Busan - ECDIS Tracking w/ Google Maps http://gcaptain.com/maritime/blog/cosco-busan-google-earth-tracking/ There is a reasonably good timed animation showing the the period 08:28:52 PST – 08:31:37 PST here:
http://s3.amazonaws.com/gcaptain-s3/maritime/video/dec07/CB_Thru_Span_2_dbl-Desktop.m4v

as explained here:
Cosco Busan – ECDIS Tracking w/ Google Maps
http://gcaptain.com/maritime/blog/cosco-busan-google-earth-tracking/

]]> By: reader http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/comment-page-1/#comment-6707 reader Sun, 03 Feb 2008 03:34:04 +0000 http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/#comment-6707 The period 08:27:27 PST - 08:31:37 PST is reasonably well documented in an animation here: http://s3.amazonaws.com/gcaptain-s3/maritime/video/dec07/CB_Thru_Span_2_dbl-Desktop.m4v as explained here: http://gcaptain.com/maritime/blog/cosco-busan-google-earth-tracking/ It is my understanding that the ISPR was meant to deal with the response to the allision, leaving the cause of the allision to other investigations; in particular but not limited to the NTSB. The period 08:27:27 PST – 08:31:37 PST is reasonably well documented in an animation here:

http://s3.amazonaws.com/gcaptain-s3/maritime/video/dec07/CB_Thru_Span_2_dbl-Desktop.m4v

as explained here:

http://gcaptain.com/maritime/blog/cosco-busan-google-earth-tracking/

It is my understanding that the ISPR was meant to deal with the response to the allision, leaving the cause of the allision to other investigations; in particular but not limited to the NTSB.

]]> By: reader http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/comment-page-1/#comment-13592 reader Sun, 03 Feb 2008 01:05:56 +0000 http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/#comment-13592 There is a reasonably good timed animation showing the the period 08:28:52 PST - 08:31:37 PST here:<br><a href="http://s3.amazonaws.com/gcaptain-s3/maritime/video/dec07/CB_Thru_Span_2_dbl-Desktop.m4v">http://s3.amazonaws.com/gcaptain-s3/maritime/vi...</a><br><br>as explained here:<br>Cosco Busan - ECDIS Tracking w/ Google Maps<br><a href="http://gcaptain.com/maritime/blog/cosco-busan-google-earth-tracking/">http://gcaptain.com/maritime/blog/cosco-busan-g...</a> There is a reasonably good timed animation showing the the period 08:28:52 PST – 08:31:37 PST here:
http://s3.amazonaws.com/gcaptain-s3/maritime/vi...

as explained here:
Cosco Busan – ECDIS Tracking w/ Google Maps
http://gcaptain.com/maritime/blog/cosco-busan-g...

]]> By: reader http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/comment-page-1/#comment-13591 reader Sun, 03 Feb 2008 00:34:04 +0000 http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/#comment-13591 The period 08:27:27 PST - 08:31:37 PST is reasonably well documented in an animation here:<br><br><a href="http://s3.amazonaws.com/gcaptain-s3/maritime/video/dec07/CB_Thru_Span_2_dbl-Desktop.m4v">http://s3.amazonaws.com/gcaptain-s3/maritime/vi...</a><br><br>as explained here:<br><br><a href="http://gcaptain.com/maritime/blog/cosco-busan-google-earth-tracking/">http://gcaptain.com/maritime/blog/cosco-busan-g...</a><br><br>It is my understanding that the ISPR was meant to deal with the response to the allision, leaving the cause of the allision to other investigations; in particular but not limited to the NTSB. The period 08:27:27 PST – 08:31:37 PST is reasonably well documented in an animation here:

http://s3.amazonaws.com/gcaptain-s3/maritime/vi...

as explained here:

http://gcaptain.com/maritime/blog/cosco-busan-g...

It is my understanding that the ISPR was meant to deal with the response to the allision, leaving the cause of the allision to other investigations; in particular but not limited to the NTSB.

]]> By: john Denham http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/comment-page-1/#comment-6659 john Denham Fri, 01 Feb 2008 17:31:33 +0000 http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/#comment-6659 My perusal of the summary disclosed several inconsistancies in the BREIF TIMELINE OF EVENTS. From events 0820 through 0829 does not appear navigationally feasible. If this is a pre-cursor of the ISPR expertness, we will never know why the COSCO BUSAN allided with the fender on D tower. My chart analysis using reported speed and stated facts produce different situations than can have actually happened. I feel the statements maybe true but are not sequentlualy correct. My perusal of the summary disclosed several inconsistancies in the BREIF TIMELINE OF EVENTS. From events 0820 through 0829 does not appear navigationally feasible. If this is a pre-cursor of the ISPR expertness, we will never know why the COSCO BUSAN allided with the fender on D tower. My chart analysis using reported speed and stated facts produce different situations than can have actually happened. I feel the statements maybe true but are not sequentlualy correct.

]]> By: john Denham http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/comment-page-1/#comment-13590 john Denham Fri, 01 Feb 2008 14:31:33 +0000 http://gcaptain.com/maritime/blog/independent-panel-releases-report-on-cosco-busan/#comment-13590 My perusal of the summary disclosed several inconsistancies in the BREIF TIMELINE OF EVENTS. From events 0820 through 0829 does not appear navigationally feasible. If this is a pre-cursor of the ISPR expertness, we will never know why the COSCO BUSAN allided with the fender on D tower. My chart analysis using reported speed and stated facts produce different situations than can have actually happened. I feel the statements maybe true but are not sequentlualy correct. My perusal of the summary disclosed several inconsistancies in the BREIF TIMELINE OF EVENTS. From events 0820 through 0829 does not appear navigationally feasible. If this is a pre-cursor of the ISPR expertness, we will never know why the COSCO BUSAN allided with the fender on D tower. My chart analysis using reported speed and stated facts produce different situations than can have actually happened. I feel the statements maybe true but are not sequentlualy correct.

]]>