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 Baltimore, ship brings down bridge, mass casualties

page: 19
33
<< 16  17  18    20  21  22 >>

log in

join
share:

posted on Mar, 28 2024 @ 11:59 AM
link   
a reply to: Threadbarer

That is not a good job...it is called doing your job. You do not get kudos for things you are supposed to do.



posted on Mar, 28 2024 @ 12:57 PM
link   
Black Box Recovered - Investigation Underway

NTSB Releases Data on DALI’s Black Box, Reveals No CCTV Footage Found, Sensors Cut Off and Turned Backed On, Voice Recorder Disrupted By Background Noise


On Tuesday evening, Homendy and NTSB investigator Marcel Muise held a press conference to reveal the data on the DALI’s black box, also known as the Voyage Data Recorder (VDR).

NTSB investigator Marcel Muise revealed there were about six hours of VDR on data and included a timeline of midnight to 6 am.

Before revealing the data on the VDR, Muise warned that the quality of the voice recording and radio data was hard to comprehend due to background noise.

Muise then shared that the “VDR sensor data ceased recording. The VDR audio continued to record using the redundant power source.”

“VDR resumed recording sensor data, and during this time, steering commands and rutter orders were recorded on the audio,” added Muise.

Muise continued, “The ship’s pilot made a very high-frequency radio call for tugs in the vicinity to assist. About this time, the pilot dispatcher phoned the Maryland Transportation Authority duty officer regarding the blackout.”

He concluded his statement by adding that “The ship’s speed over ground was recorded at just under 7 knots. From this moment to approximately 1:29:33, the VDR audio recorded sounds consistent with the collision of the bridge.”





posted on Mar, 28 2024 @ 04:50 PM
link   
a reply to: IndieA

Things to Consider about this Incident...........





posted on Mar, 28 2024 @ 05:14 PM
link   
a reply to: Zanti Misfit

Based on the thumbnail, I can only assume we're at the point where the bridge's collapse is being blamed on Jewish Space Lasers.

Marge? Is that you?



posted on Mar, 28 2024 @ 05:48 PM
link   
a reply to: Threadbarer

No , that is Misleading and has No Bearing on the Actual Video . If you even Viewed it before Commenting you would have Realize that .....

edit on 28-3-2024 by Zanti Misfit because: (no reason given)



posted on Mar, 28 2024 @ 05:54 PM
link   

originally posted by: Threadbarer
a reply to: Zanti Misfit

Based on the thumbnail, I can only assume we're at the point where the bridge's collapse is being blamed on Jewish Space Lasers.

Marge? Is that you?


Something must be important enough to cover-up or why else would wild banshee diversions be happening? Why would somebody waste time on insane deflections? 🤤



posted on Mar, 28 2024 @ 05:56 PM
link   
a reply to: xuenchen

Yes. Why are you wasting so much effort making insane deflections?



posted on Mar, 28 2024 @ 05:56 PM
link   
a reply to: Zanti Misfit

Good Video 👍🦊



posted on Mar, 28 2024 @ 08:12 PM
link   
a reply to: Threadbarer

That's not how it works.

Ships are booked in to certain ports. Sometimes they have to anchor out at sea near the port for a period before they come in. Some ports are higher security than others. Baltimore, you'd expect, would be quite a high level of security.

There are many factors at play that can delay a ships entry to port and who pays the extra costs via the company taking a hit depends on where the blame lies, usually an insurance company covers it unless the Captain has to take a hit to the pay packet.

Knowledge gained from my time as a Supervisor in Maritime Security.



posted on Mar, 28 2024 @ 08:16 PM
link   
a reply to: xuenchen

The government must have known it was coming down, because of the crafted response , The black box turning off etc By maritime law it had to have a pilot onboard, and where were the tugs? Clown world gets more bizzare.



posted on Mar, 28 2024 @ 08:37 PM
link   
a reply to: annonentity

It had two harbor pilots onboard. They also put out a call for nearby tugs when they lost power.



posted on Mar, 28 2024 @ 09:15 PM
link   
a reply to: IndieA

The fact that this is missing the key data tells me that it was not a simple accident.



posted on Mar, 28 2024 @ 09:33 PM
link   

originally posted by: matafuchs
a reply to: IndieA

The fact that this is missing the key data tells me that it was not a simple accident.


Yep. Too many coincidences.



posted on Mar, 28 2024 @ 09:52 PM
link   
a reply to: Threadbarer

Then it starts to look more like a cyber attack. Computers a vunerability...who would have thunk it?



posted on Mar, 29 2024 @ 05:48 AM
link   
a reply to: matafuchs

Data wasn't missing. The black box on ships is not like ones on planes.



posted on Mar, 29 2024 @ 09:57 AM
link   
Baltimore bridge collapse update: Investigators reveal timeline of events leading up to ship crash


Federal investigators unveiled new details about what occurred in the minutes before a hulking cargo ship lost power and slammed into Baltimore's Francis Scott Key Bridge, including the pilot's urgent call for assistance and authorities' efforts to clear people off the bridge.



NTSB crews used the ship's voyage data recorder, or VDR, to piece together a rough timeline of events leading up to the collision. But it will take months for them to gather the piles of physical evidence, maintenance records, ship data and witness interviews required to deliver a full report, Homendy said.



Here's the NTSB's timeline in hours, minutes and seconds:

Approximately 12:39 a.m.: The ship departed from Seagirt Marine Terminal.

By 1:07:00 a.m.: The ship had entered the Fort McHenry Channel.

01:24:59 a.m.: Numerous audible alarms were recorded on the ship's bridge audio. At about the same time, the VDR stopped recording ship system data but was able to continue recording audio using a different power source.

01:26:02 a.m.: The VDR resumed recording ship system data. During this time, steering commands and orders regarding the rudder were captured on audio.

01:26:39 a.m.: The ship's pilot made a general very high frequency (VHF) radio call for tugboats in the vicinity to assist the vessel. Around this time, the pilot association dispatcher contacted the Maryland Transportation Authority duty officer regarding the blackout, according to transit authority data.

Around 01:27:04 a.m.: The pilot ordered that the ship's port anchor be dropped and issued additional steering commands.

Around 01:27:25 a.m.: The pilot issued a radio call over the VHF radio, reporting that the vessel had lost all power and was approaching the bridge. Around this time, the transit authority duty officer radioed two of its units - one on each side of the bridge - that were already on scene and ordered them to close traffic on the bridge. All lanes were then shut down.

Around 01:29 a.m.: The ship's speed over ground was recorded at just under 8 miles per hour. From this moment until approximately 1:29:33, the VDR audio recorded sounds consistent with the collision with the bridge. Additionally, MDTA dash cameras show the bridge lights extinguishing.

01:29:39 a.m.: The pilot radioed the US Coast Guard to report the bridge was down.



posted on Mar, 29 2024 @ 10:01 AM
link   

originally posted by: Threadbarer
a reply to: matafuchs

Data wasn't missing. The black box on ships is not like ones on planes.


The article listed above on this page clearly says "VDR stopped logging data" according to NTSB

How is it you claim that's not so.



posted on Mar, 29 2024 @ 10:06 AM
link   
a reply to: Phoenix

I don't know, but maybe due to power outage?



posted on Mar, 29 2024 @ 10:17 AM
link   
a reply to: Phoenix




The article listed above on this page clearly says "VDR stopped logging data" according to NTSB


if the sensors don't have power they couldn't feed the VDR. even if VDR is on a battery back up. notice they said it kept recording audio.


At about the same time, the VDR stopped recording ship system data but was able to continue recording audio using a different power source.


the power going off and on may have caused a switching glitch while the system was trying to reboot.



posted on Mar, 29 2024 @ 10:41 AM
link   
a reply to: Threadbarer

I am getting f'n sick of you trying to explain things to me and everyone else like we are kids. Really tired of it. Especially when you are wrong and then try to backtrack.

The VDR is the ships 'black box'.

Link


A VDR is like a ‘Black Box’ recorder on a plane (although it is actually colored orange). It records sounds on the bridge (the bridge is where the ship is controlled from) in a continual loop (usually a 24 hour loop), as well as takes in key data feeds from the bridge. These are then stored in a microchip within a water-tight container on the outside of a ship, to be retrieved in the event of a maritime incident or sinking.


The question is, why would they suddenly lose power? All ships will have a secondary power source just for the VDR.


1:24:59 a.m. -- Numerous audible alarms go off on the bridge of the container ship. The VDR temporarily goes off.


3 minutes go by.


1:27:04 a.m. -- The pilot aboard the Dali orders the vessel's port anchor be dropped, according to the VDR.


Here is an example. There are many kinds of VDR and back ups but this is to show the theory behind it.

Link

Call it terrorism. Call it a hijacking. Call it what you want but when there is an accident like this and the only way to prove what happened suddenly goes dark it is going to lead to some serious questions.




top topics



 
33
<< 16  17  18    20  21  22 >>

log in

join