It looks like you're using an Ad Blocker.

Please white-list or disable AboveTopSecret.com in your ad-blocking tool.

Thank you.

 

Some features of ATS will be disabled while you continue to use an ad-blocker.

 

Breaking: US Navy destroyer takes on water after collision off Japanese coast

page: 23
56
<< 20  21  22   >>

log in

join
share:

posted on Jun, 26 2017 @ 10:28 AM
link   
a reply to: pteridine

as i tthink i has said earlier in one of the threads on this :

i want to see the log files for both vessels

the equipment spec for ACX crystal shows that she has a fuully integrated bridge suite that SHOULD have recoreded everything thsat happened - and the fitgerald has multiple data recording systems

so lets see - people are pretending to " analyse " the AIS track from the crystal - i just shake my head

the logs is where its at




posted on Jun, 26 2017 @ 10:37 AM
link   


Maybe a container ship captain is spinning a sea story.


Maybe. But everyone else is staying behind "can't comment".



posted on Jun, 26 2017 @ 10:40 AM
link   
a reply to: ignorant_ape

So you are alluding to the public tracking data being incorrect? The true course will differ from that gathered.



posted on Jun, 26 2017 @ 11:02 AM
link   
a reply to: roadgravel




Maybe. But everyone else is staying behind "can't comment".


Thats what caught my attention, I don't think the Navy would allow a false narrative to move forward without correcting the record.



posted on Jun, 26 2017 @ 11:19 AM
link   
EXCLUSIVE-U.S. warship stayed on deadly collision course despite warning-container ship captain


TOKYO, June 26 (Reuters) - A U.S. warship struck by a container vessel in Japanese waters failed to respond to warning signals or take evasive action before a collision that killed seven of its crew, according to a report of the incident by the Philippine cargo ship's captain.

Multiple U.S. and Japanese investigations are under way into how the guided missile destroyer USS Fitzgerald and the much larger ACX Crystal container ship collided in clear weather south of Tokyo Bay in the early hours of June 17.

In the first detailed account from one of those directly involved, the cargo ship's captain said the ACX Crystal had signalled 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 U.S. Navy declined to comment and Reuters was not able to independently verify the account.


Does this fit the opinion of you all who're following this?

peace



posted on Jun, 26 2017 @ 11:22 AM
link   
a reply to: roadgravel

no incorrect - but too coarse - the AIS feeds on public websites are for entertainment purposes only - the sample interval is too long to get any meaningfull data about a collision

the vessels log files will have EVERYTHING

not just position - sampled at a realistic interval - but rudder positions , prop RPM , a time matched radar plot , the radio logs etc etc etc etc

so that is why i am contemptuous of " analysis " of the public AIS track - too much can happen between waypoints

ETA :



^ shows why the public AIS is useles - except as entertainment

the crystam cannot make a 90 degree turn [ in the manner shown ]

edit on 26-6-2017 by ignorant_ape because: (no reason given)



posted on Jun, 26 2017 @ 04:17 PM
link   

originally posted by: jaws1975
a reply to: roadgravel




Maybe. But everyone else is staying behind "can't comment".


Thats what caught my attention, I don't think the Navy would allow a false narrative to move forward without correcting the record.


Maybe it isn't false. The Navy can make a mistake. Happened before.



posted on Jun, 26 2017 @ 04:18 PM
link   
a reply to: ignorant_ape




but too coarse


I can see that point. I wonder if we'll even actually see it from the navy.



posted on Jun, 26 2017 @ 04:19 PM
link   
a reply to: ignorant_ape

AIS was tampered with is what i heard on another board.



posted on Jun, 26 2017 @ 04:26 PM
link   

originally posted by: NoJack
a reply to: ignorant_ape

AIS was tampered with is what i heard on another board.


That doesn't seem like an easy thing to do.



posted on Jun, 26 2017 @ 04:34 PM
link   
a reply to: roadgravel




Maybe it isn't false. The Navy can make a mistake. Happened before.


Ignoring warnings from the container ship isn't a mistake, it's much worse. So now that we know the captain of the ACX Crystal was on the bridge leading up to the collision, why did it take him an hour to report it? There is some high strangeness with this case.



posted on Jun, 26 2017 @ 04:35 PM
link   
a reply to: roadgravel

Manipulation of 1's and zero's I guess. Who knows, the DNC can make it look like Russia hacked the elections, anything is possible.



new topics

top topics



 
56
<< 20  21  22   >>

log in

join