https://www.washingtonpost.com/worl...0d4e6ec070a_story.html?utm_term=.7c242c4363e2 WTF, i understand we operate in some busy places. But we have had two in just a couple of months. Thats nuts to me and either someone is seriously screwing the pooch or someone has figured out how to screw with our radars.
Busy places? Like a freaking ocean? What the hell is going on with these squids @HalloweenRun ? They aren't trying to back the damn thing into a slip at the local marina. Its a damn battleship on an ocean. Like with literally nothing around for miles except for that ONE thing...and you crash into it! Obama hurt us worse than we thought
I am stunned. I was on two surface ships that operated in both that area and out of Yokuka. Busy as hell, but everyone knew that. Neither CO would never had not been on the bridge that close to Tokyo Wan. I don't know any details on this second collision. The previous SECNAV, Ray Mabis, appears to have been much more interested in social engineering rather that the real navy's mission. Perhaps we are seeing the results of those that advanced under his tenure. Navy cynics, of which there are many are leaning that way. I will say, navigating those very confined waterways, following the Nautical Rules of the Road, when so many vessels are either on autopilot, or they don't care, is very complex and requires vigilance and professionalism. But, it's been that way forever, and these collisions are out of control. Totally unsat and reveal a huge problem in the surface navy.
Shane, believe it or not, an awfully lot of ships get funneled in to some very constricted places, but that is nothing new. This spate of collisions. I used to tell people that going into Tokyo Bay was like I-85 in Atlanta, except you could sink!
No shit. Are these phuckers driving drunk, asleep at the wheel or just can't read an instrument? They can't see vessels atop the water, what are they going to do in a time of war and the enemy deploys subs?
