Welcome to the NavList Message Boards.


A Community Devoted to the Preservation and Practice of Celestial Navigation and Other Methods of Traditional Wayfinding

Compose Your Message

Add Images & Files
    Re: Navy Grounding in PI Digital Charts Blamed
    From: Brad Morris
    Date: 2013 Jan 31, 18:58 -0500

    I surrender!

    I didn't think I was arguing, just discussing.

    I read a New York Times article and commented. 

    On Jan 31, 2013 6:24 PM, "Lu Abel" <luabel@ymail.com> wrote:

    Not to step into the middle of an argument, Brad, but the official news release from the government said that the reef was mislocated by eight miles on the chart.  And, as someone else noted, the reef rises suddenly from water a thousand meters deep or more.  And it's 100 miles offshore and there's nothing else nearby.   So it's understandable that a navigator using these defective charts could easily think that he were in clear, deep water.  

    And for whoever mentioned "piloting," how does one do coastal piloting (which is generally defined as positioning based on shore-based objects) when the "shore" is a few hundred yards of reef that suddenly jumps out of the depth of the ocean?

    Oh, and let's not forget that this grounding took place at 2AM, so I doubt that anyone keeping visual watch would have seen anything.

    I still want to know, though, if the vessel was equipped with a forward-looking depth sounder.

    From: Brad Morris <bradley.r.morris---com>
    To: luabel---com
    Sent: Thursday, January 31, 2013 2:11 PM
    Subject: [NavList 22208] Re: Re: Navy Grounding in PI Digital Charts Blamed

    Hi Frank
    Typical newspaper reporting!  There is no way to tell the order of boarding vs grounding.  Further, the article makes it sound like every ship entering the park is to be boarded first.  Hence my comments.
    To your statement that "Nor is it likely that anything would have been visible on radar except fishing vessels", well that's some marine park!  Fishing vessels!?!  What's being protected?  Fishing grounds?
    I'll wait and see how big the mapping error is.  The magnitude is important, as is the magnitude of the berth the captain gave the danger. 
    On Jan 31, 2013 4:35 PM, "Frank Reed" <FrankReed---com> wrote:

    Brad you wrote:
    "I do understand the part wherein the Park Rangers were denied access to a US Navy warship. The US Navy is not in the habit of permitting foreign nationals to board & inspect her ships, period."
    Right. In fact, would vessels of ANY nation's navy permit boarding by some minor local authorities?
    And you wrote:
    "However, in so denying them, the captain should have become aware that something was amiss. "Why am I in park waters?" "What in the heck was that?" Instead, the captain held course right onto to the reef."
    I don't think that's what happened. The coverage in the NY Times article and repeated in a few other places appears to have the order of events backwards. The vessel was hard aground at 02:00 local time. The local coast guard or park rangers or whatever they were spotted them on radar at 04:00 local time, and that's when they asked to board. They were denied, as normal.
    And you wrote:
    "The captain can blame his charts"
    The charts WERE in error. The mapping agency has admitted this.
    "or, as is more appropriate in coastal waters, piloting. He can claim improper, inadequate or simply missing buoy markings."
    What qualifies as "piloting waters" in USN custom? Is there a specific standard? This group of atolls is really in the middle of nowhere in the Sulu Sea and surrounded by deep water. There are only a couple of uninhabited islets above water in this area. If you have 500 feet of water under the keel but there are dangerous shallows ten miles away, do piloting rules apply? What is the custom? Also, I highly doubt that there are buoys out there except maybe a few markers for good diving locations. It's not likely that there is anything that would have been visible in the middle of the night in heavy seas. Nor is it likely that anything would have been visible on radar except fishing vessels, and they would not have provided any clue to the danger.
    You concluded:
    "Yet in the end, the safety of the ship was his responsibility He failed in that responsibility. The ship is a total loss and that marine reef is damaged. The only good thing is that (apparently) there was no loss of life."
    Sure, the captain will lose his job, and he will be behind a desk from now on. It is indeed his fault.
    The damage to the reef is probably not great, but rest assured that local authorities will get as much press coverage and MONEY out it as they can. As for the ship, I question the accounting that lists its value at over $250 million. They build nuclear submarines for about a billion dollars each, and that's the cost when they're new. This vessel was 25 years old and not a high performance ship by any measure. If an insurance company had covered it as a private vessel, I doubt it would have been valued at more than $50 million at most. Similarly if the US had sold it to the navy of an ally, there's no way in hell they could have gotten over $250 million for it.

    NavList message boards and member settings: www.fer3.com/NavList
    Members may optionally receive posts by email.
    To cancel email delivery, send a message to NoMail[at]fer3.com
    View and reply to this message: http://fer3.com/arc/m2.aspx?i=122207
    View and reply to this message: http://fer3.com/arc/m2.aspx?i=122208

    View and reply to this message: http://fer3.com/arc/m2.aspx?i=122210

    Browse Files

    Drop Files


    What is NavList?

    Join NavList

    (please, no nicknames or handles)
    Do you want to receive all group messages by email?
    Yes No

    You can also join by posting. Your first on-topic post automatically makes you a member.

    Posting Code

    Enter the email address associated with your NavList messages. Your posting code will be emailed to you immediately.

    Email Settings

    Posting Code:

    Custom Index

    Start date: (yyyymm dd)
    End date: (yyyymm dd)

    Visit this site
    Visit this site
    Visit this site
    Visit this site
    Visit this site
    Visit this site