Free Republic
Browse · Search
News/Activism
Topics · Post Article

Skip to comments.

USS Fitzgerald collision wasn't reported for nearly an hour, Japan says
CBS News ^ | June 19, 2017

Posted on 06/19/2017 10:20:48 AM PDT by Kaslin

Last Updated Jun 19, 2017 11:37 AM EDT

TOKYO -- Japan's coast guard is investigating why it took nearly an hour for a deadly collision between a U.S. Navy destroyer and a container ship to be reported.

A coast guard official said Monday they are trying to find out what the crew of the Philippine-flagged ACX Crystal was doing before reporting the collision off Japan's coast to authorities 50 minutes later.

The ACX Crystal collided with the USS Fitzgerald off Japan's coast, killing seven of the destroyer's crew of nearly 300. The ships collided early Saturday morning, when the Navy said most of the 300 sailors on board would have been sleeping. Authorities have declined to speculate on a cause while the crash remains under investigation.

A track of the much-larger container ship's route by MarineTraffic, a vessel-tracking service, shows it made a sudden turn as if trying to avoid something at about 1:30 a.m., before continuing eastward. It then made a U-turn and returned around 2:30 a.m. to the area near the collision.

The impact crushed the starboard side of the Fitzgerald. The ship was listing as it sailed into its home port in Yokosuka, Japan, Saturday, CBS News correspondent Ben Tracy reports. The commander of the U.S. 7th Fleet said the sailors' actions kept the ship from sinking.

"This was not a small collision," Vice Adm. Joseph Aucoin said. "It was right near the pilot's house, and there is a big puncture."

(Excerpt) Read more at cbsnews.com ...


TOPICS: Foreign Affairs; Front Page News; Japan
KEYWORDS: maritime; usnavy; ussfitzgerald
Navigation: use the links below to view more comments.
first previous 1-2021-4041-6061-80 ... 201-215 next last
To: Kaslin

The Navy says they are sticking to the later time for the collision.

We still only have photos and a track on the container ship.

The destroyer was not in a war zone.

There are explanations for why they were hit.

Nobody knows yet what the container ship was saying on the radio.

It is possible that they were using the radio to lure the destroyer closer.

What I’m not going to do is disparage our Sailors when we don’t have enough facts.


21 posted on 06/19/2017 10:46:22 AM PDT by blueunicorn6 ("A crack shot and a good dancer")
[ Post Reply | Private Reply | To 1 | View Replies]

To: thorvaldr

Yeah, what’s even weirder is trying to miss each other in the night, which ought to be fairly easy or trying to connect with each other night, with no modern electronics, which should be somewhat harder...


22 posted on 06/19/2017 10:47:04 AM PDT by Vendome (I've Gotta Be Me - https://www.youtube.com/watch?v=wH-pk2vZG2M)
[ Post Reply | Private Reply | To 12 | View Replies]

To: Cementjungle

I know. I was being snarky. I just don’t understand how a freaking container ship is able to sneak up on a US destroyer and ram it. This situation is just weird.


23 posted on 06/19/2017 10:47:09 AM PDT by ClearCase_guy (Islam: You have to just love a "religion" based on rape and sex slavery.)
[ Post Reply | Private Reply | To 15 | View Replies]

To: al baby

Ahh. Collusion with Japs. Needs a Democrat Senate investigation/S.


24 posted on 06/19/2017 10:47:35 AM PDT by Safetgiver (Islam makes barbarism look genteel.)
[ Post Reply | Private Reply | To 2 | View Replies]

To: Uncle Sam 911

The container ship was being driven by computer? USS Fitzgerald was struck on its starboard (right-hand) side, and maritime rules require vessels to give way to others on that side.
Personnel on destroyer asleep at the wheel?


25 posted on 06/19/2017 10:48:30 AM PDT by navysealdad (http://drdavehouseoffun.com/)
[ Post Reply | Private Reply | To 16 | View Replies]

To: Kaslin
USS Fitzgerald

The Irony!!!

Jack's PT boat was adrift at night

when it was rammed by a Japanese

tincan in WWII.


26 posted on 06/19/2017 10:49:25 AM PDT by Uri’el-2012 (Psalm 119:174 I long for Your salvation, YHvH, Your teaching is my delight.)
[ Post Reply | Private Reply | To 1 | View Replies]

To: Kaslin

None of this makes sense.

If it was a pure accident the incompetence level aboard the destroyer is off the charts.

If it wasn’t a pure accident and they were engaged in some sort of stealthy operation what was the captain doing off the bridge?

Was the container ship suspected of something - like transporting a dirty bomb?

Were they maneuvering in pursuit of the container ship and it backfired?


27 posted on 06/19/2017 10:50:02 AM PDT by Vlad The Inhaler (Best Long Term Prepper Tactic: Beat The Muslim Demographic Tsnami - Have Big Families)
[ Post Reply | Private Reply | To 1 | View Replies]

To: Flintlock

The container ship may have been “holding” for a spot in the harbor/port or for a pilot to be available. The container ship really can’t make much of a sharp turn. It probably takes it 5 or 10 miles to turn. It’s not like turning on land.

The destroyer should have been able to avoid the ACX Crystal even if it was hell bent on ramming...that will be hard for whoever was in charge at the time to explain.


28 posted on 06/19/2017 10:54:28 AM PDT by ltc8k6
[ Post Reply | Private Reply | To 10 | View Replies]

To: UriÂ’el-2012

https://en.wikipedia.org/wiki/William_Charles_Fitzgerald


29 posted on 06/19/2017 10:57:33 AM PDT by ltc8k6
[ Post Reply | Private Reply | To 26 | View Replies]

To: thorvaldr

“For this to work at all, the destroyer would have to be training under some sort of a stealth no emissions protocol and the container ship would have had to have some malfunction causing their radar etc. to be offline. If the destoyer is running passive in the dark and the container ship is making erratic maneuvers AND not emitting anything, maybe. Otherwise, yeah this is pretty weird.”

That tangled reasoning might have led to the collision, but then for the freighter to leave the scene after ?

Looking at the track of the freighter, something stinks. Looks like it doubled back to hit the cruiser then there’s another series of circles later which are unexplained before continuing on to port.


30 posted on 06/19/2017 10:57:55 AM PDT by moehoward
[ Post Reply | Private Reply | To 12 | View Replies]

To: navysealdad

I was Army so I know nothing about Navy vessels. However, I assume there are redundant alarm systems if ships get too close? Should the bells and whistles all have been blaring before the crash on the Fitzgerald and the tanker???


31 posted on 06/19/2017 10:58:40 AM PDT by Uncle Sam 911
[ Post Reply | Private Reply | To 25 | View Replies]

To: outpostinmass2

There was a published route in The Daily Mail IIRC.

The cargo ship’s path was quite erratic.


32 posted on 06/19/2017 10:59:36 AM PDT by SaveFerris (Hebrews 13:2 Do not forget to entertain strangers, for ... some have unwittingly entertained angels)
[ Post Reply | Private Reply | To 14 | View Replies]

To: Presbyterian Reporter

Radio room damage?


33 posted on 06/19/2017 11:02:51 AM PDT by mad_as_he$$
[ Post Reply | Private Reply | To 3 | View Replies]

To: Vendome
In addition to radar the USS Fitzgerald, in a heavily traveled shipping lane, should also have independently detected the freighter via sonar (one of the sailors killed was a sonar technician) and personnel on watch using IR binoculars during nighttime. There's a lot of questions, and probably some people who don't want those questions answered.
34 posted on 06/19/2017 11:03:12 AM PDT by Carl Vehse
[ Post Reply | Private Reply | To 6 | View Replies]

To: moehoward

“That tangled reasoning might have led to the collision, but then for the freighter to leave the scene after ?

Looking at the track of the freighter, something stinks. Looks like it doubled back to hit the cruiser then there’s another series of circles later which are unexplained before continuing on to port.”

We don’t know where that track came from, or where during that track the ships collided, or if the plots are even accurate.

There is nothing in the plot in and of itself that looks suspicious. Ships often zig-zag or make u-turns for time purposes. The port may not be ready for them, a harbor pilot may not be available, etc.


35 posted on 06/19/2017 11:03:26 AM PDT by ltc8k6
[ Post Reply | Private Reply | To 30 | View Replies]

To: Timpanagos1

Captain Morgan?


36 posted on 06/19/2017 11:04:38 AM PDT by mad_as_he$$
[ Post Reply | Private Reply | To 8 | View Replies]

To: Uncle Sam 911

The radar system would alert to intersecting tracks or close proximity tracks.


37 posted on 06/19/2017 11:05:01 AM PDT by ltc8k6
[ Post Reply | Private Reply | To 31 | View Replies]

To: Flintlock

38 posted on 06/19/2017 11:05:38 AM PDT by Travis McGee (EnemiesForeignAndDomestic.com)
[ Post Reply | Private Reply | To 10 | View Replies]

To: Flintlock

(I posted this elsewhere with the above blue chart.)

Fitzgerald collision open discussion: IMHO, this was a deliberate ramming.

My experience aboard USN warships goes back to the 1980s. I was a SEAL officer (1130), not a Surface Warfare Officer (SWO), but on a couple of cruises I had to ride on the flagship with the commodore of an amphibious squadron, instead of riding on the ship carrying my SEAL platoon. Back in those days, as a lieutenant, (O-3), I was the senior frogman in the Amphibious Ready Group, so the commodore (navy captain in charge of a squadron of ships) wanted me on his staff instead of on another ship with my men.

As a result, I sat in on every flag staff meeting (at least twice a day, am and pm) going across the Atlantic a few times, once to Beirut, and another time crossing the Atlantic going to Norway. To keep me busy, I had to play SWO on the flag bridge, standing watch like any SW junior officer. This involved our flag officers setting the overall course for a half dozen amphibious ships sailing in formation. I was on the flag bridge at night going up the English Channel, through the Strait of Gibraltar, and the Strait of Messina between Italy and Sicily. IOW, very congested waters, and not merely making a transit with one ship, but in overall charge (our flag staff, not me) of a half dozen ships in formation.

I mention all that to say that I have a pretty fair idea of what takes place on the bridge of a navy warship at night in congested coastal waters. To me, the Fitzgerald collision does not look like an accident, or an “autopilot malfunction.” Trust me, on the bridge of the navy warship, at least a half dozen very sharp and 100% alert officers, CPOs and petty officers are on duty 24/7. They stand 4 hour watches at night, so they are not all exhausted or anything like that. In fact, strong coffee flows freely at all times.

A petty officer is staring at the radar every single minute, and he is plotting the courses and the Closest Point of Approach (CPA) of every contact he sees. In addition, there is a lookout with a headset in comms with the bridge posted on the bow, the stern, and each bridge wing (outside). It’s a friendly competition to see if the lookout can spot a small boat unseen on radar. Every young set of eyes wants to be the first to spot a contact, and does not want to hear, “Bow lookout, do you see that fishing boat a mile ahead?” The bow lookout wants to be telling the bridge, “I see something ahead, a small boy, do you have it on radar?”

Further: the CO of the ship has standing orders which are reiterated every night that he must be awoken if any contact has a CPA closer than a certain distance of a set number of miles. The distance might vary according to conditions, (traffic, fog, etc), but generally any projected CPA closer than a few miles, and the captain will be on the bridge. The CPA of three miles, for example, might be projected to occur a half hour in the future, but the captain will be brought to the bridge from his “at sea” cabin which is only a few steps away. And when in doubt: get the captain!

Now, looking at the six turns made by the ACX Crystal, it looks to me as if the person at the helm took the decision to make a U-turn and come back in pursuit of lining up a collision attack against the Fitzgerald. There is no innocent explanation for those six turns ending up in a ramming. There are some reports that the Crystal turned off its AIS radar transponder, radios, and running lights.
A lot of effort went into the Crystal lining up a bow-to-bow crossing situation with the USN warship. The standard rule for passing bow to bow is for both ships to turn to starboard, and pass port side to port side. But this is a generalization and there are many exceptions, for example, if the two ships are on parallel but opposite courses so they will already pass starboard to starboard by a wide margin. Or if it’s not really bow to bow, but a crossing situation.

This is where it gets sticky, because one ship might consider that they are passing bow to bow, the other might see it as a crossing situation. In all such cases, both ships will be on the VHF radio from several miles out to clarify the situation so that there is no confusion about what each ship is going to do.

Given all that, how can they still have a collision? One way would be for the ramming ship (if that was his intention) to say, “Don’t worry, I’m turning to port.” And then turn to starboard. In the last thirty seconds to a minute, there is almost nothing anybody can do to prevent a collision, if the ramming ship did something like this, and turned the opposite way from what was expected by the other ship.

It will be interesting to hear from the officers and sailors on the bridge, and the lookouts, but I assume they are all sworn to secrecy. Even how long in advance did the collision alarm sound? One minute? thirty seconds? How about the “danger signal,” of five or more blasts on the horn? Everybody on the Fitzgerald would have heard the danger signal and/or the collision alarm. I’ve been on an amphibious ship that “bumped” another ship doing underway replenishment, and I’ve heard the collision alarm. NOBODY on the ship will have ANY doubt they are about to be hit!
So, in 2017, is it possible that a USN warship could be tricked into being the victim of an intentional ramming, perhaps even “ship jihad?” Yes, I think so. The watch standers on the bridge are going to trust what the person on the other ship is saying on the VHF radio about his intentions. A standard of maritime professionalism is expected, and trust is both given and expected. If the other ship says, “Hold your course, I’m turning to port, I’ll pass behind you,” and then he turns instead to starboard....an intentional ramming can occur.

Can US navy officers, in 2017, be that naïve? I think so again. Look at what happened in Alexandria VA last week. More than twenty Republican congressmen met for baseball practice with no security plan at all. It was just a fluke that Steve Scalise came to practice, and so his two-person security detail was present. Several of these Republican baseball team members were former senior military officers, including a former Army general, yet they didn’t even think about the possibility of a terror attack against them. Much younger officers on a warship might also be a bit too naïve about an unexpected ramming attack.

I look forward to hearing from active or former Surface Warfare Officers or merchant marine sailors.


39 posted on 06/19/2017 11:07:01 AM PDT by Travis McGee (EnemiesForeignAndDomestic.com)
[ Post Reply | Private Reply | To 10 | View Replies]

To: Travis McGee

The track of the Fitz is speculation, though. So that map is basically worthless. We don’t know where the collision occurred.


40 posted on 06/19/2017 11:07:07 AM PDT by ltc8k6
[ Post Reply | Private Reply | To 38 | View Replies]


Navigation: use the links below to view more comments.
first previous 1-2021-4041-6061-80 ... 201-215 next last

Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.

Free Republic
Browse · Search
News/Activism
Topics · Post Article

FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson