Re: Another U.S. Naval Collision...
Mon Aug 21, 2017 7:16 am
Pablo wrote:usrifle wrote:I don't get it...We have the most advanced Ship board Radars in the World, and we run into other Ships?
Or they run into us
Port. AFT.
WTF??
They must have run a red light.
From the pictures of the damage, I would conclude that they were t-boned by the other vessel. The hull breach is rather obviously caused by the bow of the other ship, and even the prow damage at the deck line and railing is obvious.
Whatever negligence caused this collision, one thing is clear. The Mcain was struck by another vessel. Not the other way around.
Re: Another U.S. Naval Collision...
Mon Aug 21, 2017 3:28 pm
Is it common for a destroyer to run around with an empty Harpoon missile tube?
Re: Another U.S. Naval Collision...
Mon Aug 21, 2017 3:47 pm
is hacking of e systems on either ship out of the question in these incidents? All the drivers are relying on instruments, correct?
/
/
Re: Another U.S. Naval Collision...
Mon Aug 21, 2017 3:48 pm
Guntrader wrote:Is it common for a destroyer to run around with an empty Harpoon missile tube?
A north Korean ship had a boiler explode.....
Re: Another U.S. Naval Collision...
Mon Aug 21, 2017 4:57 pm
Mediumrarechicken wrote:Guntrader wrote:Is it common for a destroyer to run around with an empty Harpoon missile tube?
A north Korean ship had a boiler explode.....
Hate when that happens!
Re: Another U.S. Naval Collision...
Mon Aug 21, 2017 5:11 pm
RockHopper wrote:
Whatever negligence caused this collision, one thing is clear. The Mcain was struck by another vessel. Not the other way around.
larger ship right of way, he crossed in front
as USrifle mention you have all these damn electronics sensors and alarms WTF.....too many ships around they turn em off???????
Re: Another U.S. Naval Collision...
Mon Aug 21, 2017 7:22 pm
cmica wrote:RockHopper wrote:
Whatever negligence caused this collision, one thing is clear. The Mcain was struck by another vessel. Not the other way around.
larger ship right of way, he crossed in front
as USrifle mention you have all these damn electronics sensors and alarms WTF.....too many ships around they turn em off???????
As I said...ran a red light. This kind of thing makes me wonder about U.S. Warships navigational etiquette. I mean, what happens if they're rude coming into port. Does DC get a ticket in the mail?
I don't know what fleet security tactics might come into play, but do they always pay attention to rules that everyone else plays by? I'm not trying to cleverly suggest my opinion in a kmfr7 style, passive-aggressive suggestion. I just wonder if we don't occasionally suffer a bloody nose because of the size of our swagger. If anyone has inside information on that, I'd welcome an education.
Re: Another U.S. Naval Collision...
Mon Aug 21, 2017 11:57 pm
Don't they use actual lookouts anymore?
In the late 70's, early 80's the aft lookout station was where the deck crew rotated every hour to smoke weed with their buddies, and the forward station was used for the half baked guys to look at the moon or stars.
Even so, with a stoned deck crew and Fred Flintstone radar we weren't hit by another ship, and I never even heard of it happening back then.
CIC would detect a ship from 20+ miles away and lookouts would report or confirm it.
No surprises, especially not a ship of that size.
US Navy collisions stoke cyber threat concerns
http://www.mcclatchydc.com/news/nation- ... 70432.html
In the late 70's, early 80's the aft lookout station was where the deck crew rotated every hour to smoke weed with their buddies, and the forward station was used for the half baked guys to look at the moon or stars.
Even so, with a stoned deck crew and Fred Flintstone radar we weren't hit by another ship, and I never even heard of it happening back then.
CIC would detect a ship from 20+ miles away and lookouts would report or confirm it.
No surprises, especially not a ship of that size.
US Navy collisions stoke cyber threat concerns
http://www.mcclatchydc.com/news/nation- ... 70432.html
Re: Another U.S. Naval Collision...
Fri Sep 15, 2017 12:49 am
Do they contract their security to Geek Squad???
There has also been a longtime problem with compromised IC's and boards from China.
But again, simply no excuse for not manning a proper deck watch.
http://foreignpolicy.com/2017/09/14/u-s ... berattack/
"The military is examining whether compromised computer systems were responsible for one of two U.S. Navy destroyer collisions with merchant vessels that occurred in recent months, Vice Admiral Jan Tighe, the deputy chief of naval operations for information warfare, said on Thursday.
There has also been a longtime problem with compromised IC's and boards from China.
But again, simply no excuse for not manning a proper deck watch.
http://foreignpolicy.com/2017/09/14/u-s ... berattack/
"The military is examining whether compromised computer systems were responsible for one of two U.S. Navy destroyer collisions with merchant vessels that occurred in recent months, Vice Admiral Jan Tighe, the deputy chief of naval operations for information warfare, said on Thursday.
Re: Another U.S. Naval Collision...
Fri Sep 15, 2017 9:24 am
Back in the 60's, when we went in to a port overseas, you always had a local "pilot" who came on board and guided the ship into the dock. The "pilot" was responsible for a safe docking.
I worked in the CIC, and sat on the radar scope to make sure we were not run into, that we did not hit anyone either, and to help navigate into the harbor. The radar was an old one they no longer use, but you could see the buoys on the side of the channel and we had the chart marked with our intended course into the dock. Any thing that was not normal was reported to the bridge.
cootduster
I worked in the CIC, and sat on the radar scope to make sure we were not run into, that we did not hit anyone either, and to help navigate into the harbor. The radar was an old one they no longer use, but you could see the buoys on the side of the channel and we had the chart marked with our intended course into the dock. Any thing that was not normal was reported to the bridge.
cootduster