Arcturus72: A "sharp turn", huh?
siyuntz: Does this mean the bridge crew of the Fitzgerald are still boned?
Arcturus72: siyuntz: Does this mean the bridge crew of the Fitzgerald are still boned?I've never heard of a CO who kept his command after something like this, but I'm curious now... I know I wouldn't want to be one of the bridge crew right now...Even if you did everything right, I'm sure right now they all feel like that one scene in Sully, where he's just been told that one of the engines was still at idle... You just KNOW you're screwed...
Kouta: siyuntz: Does this mean the bridge crew of the Fitzgerald are still boned?Yes.
Arcturus72: Even if you did everything right, I'm sure right now they all feel like that one scene in Sully, where he's just been told that one of the engines was still at idle...
gregscott: ISIS is active in the Philippines. This makes me wonder if the freighter's bridge was crewed by Jihadists.
omegaic: This is going to be an interesting investigation. I wonder what the deal was the the MV doubling back on its course.
NewportBarGuy: [img.fark.net image 313x474]
RomeoEightJuliet: omegaic: This is going to be an interesting investigation. I wonder what the deal was the the MV doubling back on its course.I'm very dubious of any report stating the Crystal double-backed and then hit the Fitzgerald. It's possible, sure. But looking at the track, I think the most logical explanation is the collision happened before they turned around.[img.fark.net image 650x390]I would speculate the collision happened at point A. One report had both vessels heading ENE, so that slight jog to the north prior to point A would explain the damage to Crystal's port side, and Fitzgerald's starboard.From A to B would be where Crystal assessed what happened and conducted muster, damage control, etc.At point B they returned to course consistent with their base course to keep in known water and point C is where they turned around to investigate the other ship and provide any assistance, if needed.Point D, a return to Point A, is where they stopped at the initial collision point to investigate the Fitzgerald. And D through E is their departure from the scene, en route safe harbor.But that track from point B to D is precisely what I would expect a lumbering vessel to do if they just had a collision and returned to the scene to investigate and/or assist.Anyway, that's just my guess on it using scant information. We'll know soon enough what happened, right down to the minute.
SloppyFrenchKisser: Seven servicemen's lives were lost.And still Trump has ignored this.Useless POTUS.
maddog2030: http://www.dailymail.co.uk/news/article-4612334/USS-Fitzgerald-involved-collision-merchant-vessel.html?utm_source=fark&utm_medium=website&utm_content=link&ICID=ref_farkLooks like a bunch of strange turns, scroll through the pix to the vessel track plot.
NotThatGuyAgain: I cannot fathom ho much damage is below the waterline since the container ship has one of these bows:[img.fark.net image 632x452]
siyuntz: gregscott: ISIS is active in the Philippines. This makes me wonder if the freighter's bridge was crewed by Jihadists.If that were the case, though, wouldn't they have taken credit for it already...
winedrinkingman: Since it was a Filipino crewed ship, most of the sailors on board probably were US Navy veterans. Hell, a quarter of the Fitzgerald's crew were probably Filipino. I do not think it was intentional, unless the guy steering the cargo ship was pissed about friends and family getting deported by the Trump crackdowns
Want more stories with less ads? Try
It's what the cool kids are doing.It's also how we pay the bills.
Sign up for the Fark NotNewsletter!
Links are submitted by members of the Fark community.
When community members submit a link, they also write a custom headline for the story.
Other Farkers comment on the links. This is the number of comments. Click here to read them.
You need to create an account to submit links or post comments.
Click here to submit a link.
Also on Fark
Submit a Link »
Copyright © 1999 - 2017 Fark, Inc | Last updated: Sep 25 2017 18:03:51
Article keywords powered by IBM WatsonRuntime: 0.553 sec (553 ms)