Showing posts with label Arleigh Burke-class destroyers. Show all posts
Showing posts with label Arleigh Burke-class destroyers. Show all posts

Sunday, November 5, 2017

Is The U.S. Navy Being Truthful With Its Report On Recent Crash Incidents?

Authored by Duance Norman via Free Market Shooter blog,



Recently, Free Market Shooter (as well as the US Navy) questioned the cause of a string of crashes involving Navy destroyers and cruisers... all occurring this year:


Recently, the US military, unable to come up with a cause for the incidents, began investigating something else – “compromised computer systems”:


 


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.


 


Naval investigators are scrambling to determine the causes of the mishaps, including whether hackers infiltrated the computer systems of the USS John S. McCain ahead of the collision on Aug. 21, Tighe said during an appearance at the Center for Strategic and International Studies in Washington.


 


The presumption that has been made is that these vessels are being hacked, China is the responsible party, given the proximity of the vessel crashes to the nation, as well as recent incidents where the US and China have butted heads.  But it is worth asking; are these vessels being hacked?  More importantly, if they are being hacked, who is hacking the vessels, and why?



However, this author did not discount other possible causes for the incidents, including complacent Navy sailors…


It is also worth noting that US Navy vessels do not broadcast an AIS signal (which can be seen on www.marinetraffic.com) with their respective position, like nearly all other vessels, due to obvious security/defense reasons. You almost never hear news of large commercial ships crashing into each other, which is due not just to AIS, but due to the fact that they actively try to broadcast their position by other means, such as running lights.


 


Which brings in the possibility of simple human error from US Navy operators as being the cause of these crashes.  Could it be that simple complacency and/or lack of proper training has resulted in these incidents? Given the professionalism of our military, that seems unlikely, but it wouldn’t be the first (and almost certainly won’t be the last) time it has happened.



…a theme which was commonly brought up in responses to this article after it was posted on The Burning Platform:


  • Here’s a more likely scenario – its driven and manned by a bunch of incompetent sailors, who very well may have gotten there through some kind of affirmative action nonsense, or social promotion, where pople get qualifications on things they aren’t competent enough to handle because no CO wants to get accused of racism or sexism for failing a black/women/whatever person on the oral board for underway watches. I’ve never been in the Navy, but I’ve seen it, many times. People given way more responsiblity that they are competent to handle, and you just sit back and wait for them to do something stupid, while hoping no one gets hurt. Also, they are probably spending more time doing mandated training on SJW type nonsense than learning how to sail their boat.

  • Never attribute something to highly complex malice when it can easily be contributed to stupidity and/or incompetence. Thats how Occam would slice it.

  • A complete breakdown in seafaring culture, from top to bottom. The lookouts either failed or had their reports ignored. The radarmen failed to kep track. The bridge lookouts failed, the officer of the deck failed, and the C/O failed by not ensuring that he had competent people at every position. His C/O failed because he knew that the ship captain was incapable of taut management, and likely knew that many of the junior officers and petty officers were untrained and incompetent.

  • A complete failure of culture. God help them if they become hard targets in a shooting engagement.

  • I’ve worked on vessels in the oil field my whole life and have seen the decline in discipline and accountability. With so many wireless devices it’s almost impossible to keep people focused on their task. If they would disconnect the internet from these vessels and keel hull a few of the captains most of the problem would go away.

  • Hacking, GPS spoofing, etc are all things that should be investigated. However IMO they are unlikely. What seems more likely to me is there is a breakdown of operational discipline.

  • However this was brought on is open for much debate. A large factor that I think contributes, is the shift away from the military from being an instrument of death to our enemies to a global force for good and social engineering experiments.


And in the case of the USS Fitzgerald and USS John S. McCain, the Navy has ruled that incompetence was indeed the cause of the incidents:


The collision between Fitzgerald and Crystal was avoidable and resulted from an accumulation of smaller errors over time, ultimately resulting in a lack of adherence to sound navigational practices. Specifically, Fitzgerald’s watch teams disregarded established norms of basic contact management and, more importantly, leadership failed to adhere to well-established protocols put in place to prevent collisions. In addition, the ship’s triad was absent during an evolution where their experience, guidance and example would have greatly benefited the ship.


 


The collision between John S. McCain and Alnic MC was also avoidable and resulted primarily from complacency, over-confidence and lack of procedural compliance. A major contributing factor to the collision was sub-standard level of knowledge regarding the operation of the ship control console. In particular, McCain’s commanding officer disregarded recommendations from his executive officer, navigator and senior watch officer to set sea and anchor watch teams in a timely fashion to ensure the safe and effective operation of the ship. With regard to procedures, no one on the Bridge watch team, to include the commanding officer and executive officer, were properly trained on how to correctly operate the ship control console during a steering casualty.



Is the Navy being truthful in its assessment of these incidents?  More than likely, yes.  But it should be acknowledged that the Navy could be “covering up” another cause of the incident, which could be anything from the aforementioned hacking, to problems with the Navy’s Aegis system, as was previously stated on Free Market Shooter:


A far more likely scenario is that there is a problem with the Aegis system and/or other navigation systems on US naval vessels. The US Navy, known to cover up all sorts of problems in the past, would have every reason to mask the true reason behind these collisions if they are tied to a defective weapons system. Notably, the unreliable nature of the US ground-based interceptor program under questionable test conditions has led many to believe that the system is just another failed defense project sucking up billions of taxpayer dollars.  It is not far-fetched to believe that one of our deployed systems is operating with a serious defect that has been swept under the rug by the DoD.



It is also worth acknowledging that if hacking indeed was to blame, the Navy would not acknowledge it publicly.  If hacking was the culprit, the Navy would not want the enemy to know that it had isolated the issue and corrected it, allowing the enemy to go along in the belief that they could continue to compromise Navy vessels.



However, in the cases of all of these US Navy crashes, the simplest explanation is likely the correct one, and the simplest explanation is the one that the Navy provided – a complete breakdown in seafaring culture.  Still, it has to be acknowledged that the Navy could be covering for a far larger problem. 









Wednesday, August 23, 2017

Chief Of Naval Operations "Looking Into" Possibility Ships Were Hacked

Authored by Mac Slavo via SHTFplan.com,


Tragedy struck the USS John S. McCain on Monday, when the destroyer collided with a merchant ship off the coast of Singapore, leaving 10 sailors missing and five injured. The US Navy is still struggling to find all of the remains of the missing sailors, and has ordered an operational pause for all naval fleets around the world as investigators try to figure out exactly why this terrible accident occurred.



Among the possible causes that are being looked into, one has a raised a few eyebrows. Over the summer there have been two accidental collisions involving the 7th fleet, and a total of 4 similar incidents this year. This has led some Navy officials to suspect that a cyber attack may have been responsible for the crash, as well as other recent Naval accidents.





The Navy has not ruled out an intentional action behind the latest deadly collision between a Navy destroyer and a merchant ship, the chief of naval operations told reporters Monday.



“That’s is certainly something we are giving full consideration to but we have no indication that that’s the case—yet,” Adm. John Richardson, the CNO, said at the Pentagon.



“But we’re looking at every possibility, so we’re not leaving anything to chance,” he said.



Asked if that includes the possibility the electronic defenses on the guided missile destroyer USS John S. McCain were hacked in a cyber attack, Richardson said investigators will look into all possible causes.



“We’ll take a look at all of that, as we did with the Fitzgerald,” the four-star admiral said, referring to another Navy warship collision with a merchant ship in June near Japan.



So far the Navy has made it clear that there currently isn’t any evidence that the neither USS McCain, nor any other naval vessel, has suffered from a cyber attack. However, there are quite a few top notch cyber security experts who think that all of these collisions probably have something in common.





“There’s something more than just human error going on because there would have been a lot of humans to be checks and balances,” Jeff Stutzman, an ex-information warfare specialist in the Navy, who now works at a cyber threat intelligence company, told McClatchyDC.


 


“When you are going through the Strait of Malacca, you can’t tell me that a Navy destroyer doesn’t have a full navigation team going with full lookouts on every wing and extra people on radar,” he said.


 


Itay Glick, the founder of cyber security firm Votiro, told news.com.au that the possibility of cyber interference was the first thing that came to his mind when he heard about the incident.


 


“I don’t believe in coincidence,” Glick told the website.


 


“Both USS McCain and USS Fitzgerald were part of the 7th Fleet, there is a relationship between these two events and there may be a connection,” he added.



The only other question that remains is, if these collisions were caused by cyber attacks, who is responsible? One likely culprit seems to be China. For years the Chinese government has complained about the US Navy’s presence in the South China Sea, which they claim as their territorial waters. In fact, following the USS McCain’s accident, the Global Times, which is effectively a mouthpiece of the government, claimed that Chinese citizens were celebrating the collision.


It’s also important to consider the fact that many US Naval vessels are riddled with counterfeit parts from China. A Senate led investigation in 2012 found that our ships contained over a million counterfeit parts, mostly of Chinese origin. Obviously, this raises the possibility that the Chinese government may have used black markets to secretly funnel parts to the US Navy, which contain backdoors that are easily exploitable.


But perhaps what’s most telling, is how a state-run Chinese media outlet responded to the USS McCain collision, by suggesting that the US Navy has become a dangerous presence for commercial shipping in the South China Sea.





BEIJING (Reuters) – The U.S. navy’s latest collision at sea, the fourth in its Pacific fleet this year, shows it is becoming an increasing risk to shipping in Asia despite its claims of helping to protect freedom of navigation, an official Chinese newspaper said…


 


…The state-run China Daily said in an editorial on Tuesday that people will wonder why such a sophisticated navy keeps having these problems.


 


“The investigations into the latest collision will take time to reach their conclusions, but there is no denying the fact that the increased activities by U.S. warships in Asia-Pacific since Washington initiated its rebalancing to the region are making them a growing risk to commercial shipping,” it said.



There’s no proof that China has been hacking our ships, but the possibility can’t be ruled out.

Monday, August 21, 2017

US Navy Halts Pacific Fleet Operations As Historical Path Of Collided Warship Emerges

Following the second collision of US warships in two months, the US Navy"s Chief of Naval Operations (CNO) has calling for a comprehensive review of recent incidents in the Pacific in the wake of the USS John McCain collision with an oil tanker early Monday morning. In a video, Chief of Naval Operations Adm. John Richardson called for an "operational pause" with commands and leaders across the fleet, and a deeper look into the training and certification of forces operating in  the Navy"s 7th Fleet - those in and around Japan.



"I have directed fleet commanders to immediately conduct an operational pause with commands and leaders across the fleet, to ensure we are taking all appropriate immediate measures to enhance the Navy"s safe and effective operation around the world.... This is the second major collision in the last three months, and is the latest in a series of major incidents, particularly in the Pacific theater," said Richardson. "This trend demands more forceful action."


That review "will examine the process by which we train and certify our forward deployed forces in Japan to be ready for operations and war," according to Richardson. "This will include, but not be limited to, trends in operational tempo, performance, maintenance, equipment and personnel. It will also focus on surface warfare training and career development, including tactical and navigational proficiency."


According to CBS, the investigative team will be diverse, including people from across the Navy (both officer and enlisted), and experts from outside the Navy and the private sector.



As shown earlier, the USS John S. McCain suffered extensive hull damage after colliding with the oil/chemical tanker called the Alnic MC. Five sailors were injured and another 10 remain missing.



Richardson noted that the review, led by Adm. Phil Davidson, Commander of the U.S. Fleet Forces Command, will be on a "tight timeline" in order to address the problems and "quickly make corrective actions."


Earlier at a briefing in Amman, Jordan, Defense Secretary James Mattis offered his thoughts and prayers to the sailors and families of those on board the USS John McCain, saying an investigation is currently underway to determine what exactly happened and caused the crash.  Mattis added the CNO"s broader investigation will put together an inquiry into all related accidents incidents at sea to address all existing factors, including the USS Fitzgerald.


“He has put together a broader inquiry to look into these incidents and to determine any of the causal factors to determine what’s going on,” Defense Secretary James Mattis told reporters while traveling in Amman, Jordan.


Meanwhile, courtesy of Bloomberg, the historical movement of both the USS John S. McCain and the Alnic MC tanker was revealed, swowing both the path of both ships as they ultimately collided just east of Singapore.




Missile Destroyer USS John McCain Collides With Oil Tanker Near Straits Of Malacca

Two months after seven US sailors died after the US Navy Destroyer USS Fitzgerald collided with a merchant vessel off the coast of Japan, moments ago the US Navy said that in an near replica of that incident, the guided-missile destroyer USS John S. McCain was involved in a collision with another merchant vessel, the Alnic MC, an oil/chemical tanker east of Singapore and the Strait of Malacca on August 21.



The collision was reported at 6:24 a.m. Japan Standard Time, while the ship was transiting to a routine port visit in Singapore. Initial reports indicate the warship sustained damage to its port side aft. No immediate word on any casualties. Search and rescue efforts are under way in coordination with local authorities, the Navy said.


Here is the latest update from the US 7th Fleet:





The guided-missile destroyer USS John S. McCain (DDG 56) was involved in a collision with the merchant vessel Alnic MC while underway east of the Straits of Malacca and Singapore on Aug. 21. The collision was reported at 6:24 a.m. Japan Standard Time, while the ship was transiting to a routine port visit in Singapore.



The ship is currently sailing under its own power and heading to port.



Search and rescue efforts are underway in coordination with local authorities. In addition to tug boats out of Singapore, the Republic of Singapore Navy ship RSS Gallant (97), RSN helicopters and Police Coast Guard vessel Basking Shark (55) are currently in the area to render assistance.



MV-22s and SH-60s from USS America are also responding.



Initial reports indicate John S. McCain sustained damage to her port side aft. The extent of damage and personnel injuries is being determined. The incident will be investigated.



CNN reports that according to preliminary information there have been minor injuries from the collision, although a full accounting of the crew is still underway.



The Straits of Malacca, located between Malaysia and Singapore, is one of the world"s most important naval chokepoints; it sees the transit of over 15 million barrels of oil per day, mostly headed toward China and Japan. As we reported back in 2014, "if one were so inclined, halting seaborne trade routes at the Strait of Malacca would hobble the entire Chinese economy overnight, something the Chinese leadership is surely aware of, and is certainly considering alternatives to, such as land pipelines into Iran (via India), as well as Kazakhstan and Russia."




The warship is named after John S. McCain, Sr., and John S. McCain, Jr., both Admirals in the U.S. Navy, and the grandfather and father, respectively, of the neocon Arizona senator. This crash comes days after the top three leaders aboard the USS Fitzgerald were relieved of command. That warship was damaged badly in a collision off the coast of Japan that killed seven sailors in June.


According to MarineTraffic data, the merchant ship Alnic MC with which the guided US missile destroyer collided, is an oil/chemical tanker...



... which was built in 2008, and has a dead weight of 50,760 tons.


Monday, June 26, 2017

US Destroyer Ignored Warnings Ahead Of Deadly Collision

The latest update on the mysterious circumstances surrounding a collision between a Philippines’ flagged container ship and a Navy destroyer that left seven sailors dead has arrived, courtesy of Reuters.


The news agency is reporting exclusively that the USS Fitzgerald ignore the much-larger cargo ship’s repeated warnings to get out of its path of travel.





“In the first detailed account from one of those directly involved, the cargo ship"s captain said the ACX Crystal had signaled with flashing lights after the Fitzgerald "suddenly" steamed on to a course to cross its path.



The container ship steered hard to starboard (right) to avoid the warship, but hit the Fitzgerald 10 minutes later at 1:30 a.m., according to a copy of Captain Ronald Advincula"s report to Japanese ship owner Dainichi Investment Corporation that was seen by Reuters."



The incident has spurred no fewer than six investigations, including two internal hearings by the US Navy and a probe by the United States Coast Guard (USCG) on behalf of the National Transportation Safety Board. The Japan Transport Safety Board, the JCG and the Philippines government are also conducting separate investigations.



However, the details of what transpired during the June 17 collision remain sketchy because, as Reuters, noted, nobody is talking.





“The U.S. Navy declined to comment and Reuters was not able to independently verify the account.



A spokesman for the U.S. Navy"s Seventh Fleet in Yokosuka, the Fitzgerald"s home port, said he was unable to comment on an ongoing investigation.



Spokesmen from the Japan Coast Guard (JCG), U.S. Coast Guard and ship owner, Dainichi Invest, also declined to comment.”



As Reuters reports, investigators will examine witness testimony and electronic data to determine how a naval destroyer fitted with sophisticated radar could be struck by a vessel more than three times its size. Another focus of the probes has been the length of time it took the ACX Crystal to report the collision. The JCG says it was first notified at 2:25 a.m., nearly an hour after the accident. In his report, the ACX Crystal"s captain said there was "confusion" on his ship"s bridge, and that it turned around and returned to the collision site after continuing for 6 nautical miles.


As we reported three days ago, data obtained from the ACX Crystal suggests the ship was on autopilot at the time of the collision, which has raised the specter that the incident was caused by sophisticated hackers.


And while investigators say they’ve found no evidence the collision was intentional, that the ship was relying on its computerized navigation system at the team of the collision means hackers could’ve infiltrated into the ship’s navigation system and steered it into the Navy ship – though the collision off the coast of Japan could’ve just as easily been caused by a malfunction, or human error if the system’s warning signals were ignored.


The incident left the highest rarity of such crashes has also raised questions about what caused the collision, and who might be at fault.


Collisions at sea involving Navy ships are extremely uncommon, occurring only once or twice a decade. Indeed, the incident amounted to the worst loss of life for the Navy since the bombing of the USS Cole in Yemen’s Aden harbor, an incident that left 17 sailors dead.


US naval history includes a few notable accidents. In 2005, the USS San Francisco, a Los Angeles-class submarine, hit a seamount or underwater mountain, injuring dozens of crew. In 2001, the USS Greeneville, another Los Angeles-class sub, performed an emergency ballast blow for special visitors aboard the vessel, surfacing quickly and hitting a Japanese fishing ship on the surface near Hawaii, killing nine crew members of the Japanese vessel.


In one of the Navy’s worst incidents, the aircraft carrier Wasp in April 1952 collided with the destroyer Hobson in the North Atlantic, killing 176 men.


Mr. McGrath declined to speculate as to what occurred or who or what might be to blame in the Fitzgerald incident. The collision occurred in darkness in a high-traffic area of the Pacific, he said. The most concerning aspect of the collision, from the destroyer’s point of view, is the damage to the Fitzgerald’s starboard side below the waterline, resulting from the container ship’s construction and the way its bow hit, he said.


the Fitzgerald collided with the merchant vessel, which was more than three times its size, some 56 nautical miles southwest of Yokosuka early on Saturday. Three people were evacuated to the U.S. Naval Hospital in Yokosuka after the collision, including the ship"s commanding officer, Bryce Benson, who was reported to be in stable condition. According to Reuters, Benson took command of the Fitzgerald on May 13. He had previously commanded a minesweeper based in Sasebo in western Japan.


The Fitzgerald limped into port on Saturday evening, listing around 5 degrees, a U.S. Navy spokesman in Yokosuka said. The flooding was in two berthing compartments, the radio room and auxiliary machine room, he said. There were 285 crew onboard.
 

Saturday, June 24, 2017

Container Ship Was On Autopilot When It Struck USS Fitzergerald

A deadly collision between the Philippine-registered container ship ACX Crystal and Navy destroyer USS Fitzgerald that left seven sailors dead earlier this week occurred while the ACX was on autopilot, according to a report in the Washington Free Beacon.


While investigators say they’ve found no evidence the collision was intentional, that the ship was relying on its computerized navigation system at the team of the collision means hackers could’ve infiltrated into the ship’s navigation system and steered it into the Navy ship – though the collision off the coast of Japan could’ve just as easily been caused by a malfunction, or human error if the system’s warning signals were ignored.





“The Philippines-flagged cargo ship ACX Crystal was under control of a computerized navigation system that was steering and guiding the container vessel, according to officials familiar with preliminary results of an ongoing Navy investigation.



Investigators so far found no evidence the collision was deliberate.



Nevertheless, an accident during computerized navigation raises the possibility the container ship"s computer system could have been hacked and the ship deliberately steered into the USS Fitzgerald, an Arleigh Burke-class guided missile destroyer.”



The ship’s tracking data, particularly a part of the record showing how the ship reacted after the collision, is the most telling piece of evidence that it was on autopilot, sources told the Free Beacon that it’s clear the container ship was on autopilot.





Commercial ship autopilot systems normally require someone to input manually the course for the ship travel. The computer program then steers the ship by controlling the steering gear to turn the rudder.



The system also can be synchronized with an electronic chart system to allow the program to follow courses of a voyage plan.



Tracking data broadcast from the Crystal as part of the Automatic Identification System (AIS) shows the ship changed course by 90 degrees to the right and slightly reduced its speed between around 1:32 a.m. and 1:34 a.m. After that time, the data shows the ship turned to the left and resumed a northeastern coarse along its original track line.



Private naval analyst Steffan Watkins said the course data indicates the ship was running on autopilot. "The ACX Crystal powered out of the deviation it performed at 1:30, which was likely the impact with the USS Fitzgerald, pushing it off course while trying to free itself from being hung on the bow below the waterline," Watkins told the Free Beacon.



The ship then continued to sail on for another 15 minutes, increasing speed before eventually reducing speed and turning around. 



"This shows the autopilot was engaged because nobody would power out of an accident with another ship and keep sailing back on course. It’s unthinkable," he added.



Speaking at a news conference earlier this week, Vice Admiral Joseph Aucoin said the impact crushed berthing cabins below the waterline and ripped open a large hole in the vessel. Bodies of the missing sailors were found in the berthing cabins. Aucoin declined to say how many of the seven missing sailors had been recovered, but Japanese media said all had died.





The damage to the ship was significant, Aucoin said.


“There was a big gash under the water," Aucoin said at Yokosuka naval base, home of the U.S. Seventh Fleet, the docked Fitzgerald behind him. "A significant portion of the crew was sleeping" when the destroyer collided with the Philippine-flagged container ship, destroying the commander"s cabin, he said.



The Fitzgerald is salvageable, he said, but repairs will likely take months. "Hopefully less than a year. You will see the USS Fitzgerald back," Aucoin said.


The rarity of such crashes has also raised questions about what caused the collision, and who might be at fault.


As the WSJ notes, collisions at sea involving Navy ships are extremely uncommon, according to Bryan McGrath, a former destroyer captain, who said they occur only once or twice a decade, if that. He said he couldn’t remember a recent collision that was this consequential.





“There are 275 ships in the Navy and 100 are under way all over the world,” navigating “millions and millions of miles” every year, said Mr. McGrath, who retired in 2008 and is now a consultant. “This is very, very rare.



US naval history includes a few notable accidents. In 2005, the USS San Francisco, a Los Angeles-class submarine, hit a seamount or underwater mountain, injuring dozens of crew. In 2001, the USS Greeneville, another Los Angeles-class sub, performed an emergency ballast blow for special visitors aboard the vessel, surfacing quickly and hitting a Japanese fishing ship on the surface near Hawaii, killing nine crew members of the Japanese vessel.



In one of the Navy’s worst incidents, the aircraft carrier Wasp in April 1952 collided with the destroyer Hobson in the North Atlantic, killing 176 men.


Mr. McGrath declined to speculate as to what occurred or who or what might be to blame in the Fitzgerald incident. The collision occurred in darkness in a high-traffic area of the Pacific, he said. The most concerning aspect of the collision, from the destroyer’s point of view, is the damage to the Fitzgerald’s starboard side below the waterline, resulting from the container ship’s construction and the way its bow hit, he said.


the Fitzgerald collided with the merchant vessel, which was more than three times its size, some 56 nautical miles southwest of Yokosuka early on Saturday. Three people were evacuated to the U.S. Naval Hospital in Yokosuka after the collision, including the ship"s commanding officer, Bryce Benson, who was reported to be in stable condition. According to Reuters, Benson took command of the Fitzgerald on May 13. He had previously commanded a minesweeper based in Sasebo in western Japan.


The Fitzgerald limped into port on Saturday evening, listing around 5 degrees, a U.S. Navy spokesman in Yokosuka said. The flooding was in two berthing compartments, the radio room and auxiliary machine room, he said. There were 285 crew onboard.

Saturday, June 17, 2017

US Navy Destroyer Collides With Merchant Vessel Off Japan

The USS Fitzgerald, a guided missile destroyer, collided with a merchant vessel southwest of Yokosuka, Japan, the U.S. Navy said in a statement on Friday afternoon. The crash happened at approximately 2:30 a.m. local time on June 17, and the Navy requested Japan"s Coast Guard"s assistance.


Aerial footage of the destroyer after the collision



The Navy said the Fitzgerald collided with a merchant vessel 56 nautical miles southwest of Yokosuka and the extent of injuries to U.S. personnel "is being determined." It added that the Navy had requested the assistance of the Japanese Coast Guard.


According to Reuters, Japan"s NHK public television website reported that the commercial vessel is a Philippines container ship and that the destroyer had suffered some flooding and was "unable to operate".



Full navy statement below:





USS Fitzgerald (DDG 62) was involved in a collision with a merchant vessel at approximately 2:30 a.m. local time, June 17, while operating about 56 nautical miles southwest of Yokosuka, Japan.



The U.S. Navy has requested Japanese Coast Guard assistance in responding to the collision.



The extent of damage is being determined. The extent of personnel injuries is being determined. The incident will be investigated.



The Fitzgerald recently made a port call to the US Navy"s Subic Bay base in the Philippines and conducted patrols in the South China Sea. The destroyer maintains constant contact with Japan as it is forward-based in Yokosuka.


The latest weekly summary of US naval asset around the world is shown in the map below. It shows that the the Nimitz carrier group is headed for the Middle East, via Hawaii, while the Vinson is also leaving the Korean peninsula. Meanwhile, the Persian Gulf is lightly attended, following the departure of the USS Bush which recently was headed west in the Med, only to make an unexpected 180 and is now parked off the coast of Israel.


Wednesday, February 15, 2017

Multiple Russian Jets Buzz US Destroyer In "Unsafe" Encounter

First, a Russian spy ship spotted off the US East Coast. Then Russia being accused of deploying a banned ground-launched ballistic missile.


Now, in the latest escalation in military tensions between the two nations which were supposed to be mending frayed diplomatic relations, Reuters reports that multiple Russian military aircraft came close to U.S. Navy destroyer USS Porter (located in close proximity to Russia in the Black Sea) on Feb. 10, incidents considered "unsafe and unprofessional," a U.S. official said on Tuesday.



Guided-missile destroyer USS Porter sails in the Bosphorus, on its way to the
Mediterranean Sea, in Istanbul, Turkey, February 11, 2017.


"There were several incidents involving multiple Russian aircraft," said Navy Capt. Danny Hernandez, spokesman for the European Command. "They were assessed by the commanding officer as unsafe and unprofessional."





The first buzzing involved two Russian Su-24 jet fighters followed by a single Su-24 and, in a third incident, an IL-38 transport aircraft. The passes were described by Hernandez, the Eucom spokesman, as ranging from unusually low altitude to low altitude and high speed.



"These incidents are always concerning because they could result in miscalculation or accident," he said.



According to the Free Beacon, the Russian aircraft operated without their electronic identifying transponders activated. Transponders on aircraft are monitored closely by air defense officers charged with protecting the ship and identifying hostile and friendly aircraft on radar. The Russian aircraft also failed to respond to several radio requests from the Porter to halt the overflights.


Surprisingly, Russia denied the close encounter had ever occured. "There were no incidents of any kind on Feb. 10, related to flights by Russian military jets in the Black Sea near the U.S. Navy destroyer Porter," Russian news agencies cited a spokesman for the Russian Defense Ministry, Major-General Igor Konashenkov, as saying.


"USS Porter queried all aircraft and received no response," Hernandez said. "Such incidents are concerning because they can result in accident or miscalculation," he added. The incidents involving the Su-24 were considered to be unsafe and unprofessional by the commanding officer of the Porter because of their high speed and low altitude, while the IL-38 flew at an unusually low altitude, Hernandez said.


Another U.S. official, speaking on condition of anonymity, said the lone Su-24 came within 200 yards (meters) of the Porter at an altitude of 300 feet (90 meters).


The most recent such "unsafe" close encounter took place in April 2016 when two Russian warplanes flew simulated attack passes near a U.S. guided missile destroyer in the Baltic Sea so close that they created wake in the water.


The one common thread between all these incidents is that US ships were engaged in close proximity to Russia, either the Black Sea or the Baltic - not, say, the Gulf of Mexico - which may explain why Russia is not hardly eager to put up with US presence in the region, especially at a time when NATO continues to pile up forces along Russia"s land border in Eastern Europe.