I also thought that they were running silent. So was there a sounding really or no? If so, did the sounding really show anything?
I have not made my mind up about this, but it does not seem like it should end this guys career.
The unstated risk is that we create a bunch of risk averse general mcclellands when a war breaks out.
You said everything I was going to - To effectively end this guys career over this is simply wrong (and it encompasses a wrongheaded type philosophy).
The issue of the charts is fairly easy to figure out (as an ex-navigator). On a large area chart you generally lay out your over all track. My guess is that is the one that they were using when they hit. On such a chart, not all hazards to navigation would be noted. But any prudent navigator would check the smaller area charts with the track for the specific areas you are transiting. Those are the charts that show local hazards to navigation and must be checked just for that. It appears they did not check them nor did they have them on the chart table for the CO or the OOD. Otherwise, no collision.
So they had the information, but just figured it to be an easy transit to Australia, and what possibly could be in the way with all that deep water on the large area chart. Also remember that the sub was a basket case and he was sent in to straighten it out. Too often, nuc skippers start with the plant, then ops, weps and admin while nav may be low on the list. Been there, done that.
The Navy did right. The CO got off easy. My guess is there are more axes to fall, especially the navigator.