no electronic recordings, cameras, or CCTV footage were found on DALI, VDR sensor data was interrupted while being turned on and off

the National Transportation Safety Board (NTSB) Chair Jennifer Homendy announced the voyage data recorder known as the “black box’ was recovered from the DALI cargo ship that crashed into the Francis Scott Key bridge early Tuesday morning.

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.”

Before the content on the black box was revealed, Homendy noted a group of operations and engineering groups boarded the DALI to do a walk-through of the ship’s bridge and engine room to find any electronic recorders, cameras, or CCTV footage but could not find any.

The alarms first sounded on the Dali around 1:24 a.m. Tuesday, an NTSB official said in a Wednesday evening news conference, citing preliminary information from the container ship’s voice data recorder.

About a minute and a half later, the ship’s pilot used a high-frequency radio to request assistance, helping to alert the on-duty Maryland Transportation Authority officer. The pilot called for “tugs in the vicinity,” which help vessels leave the port and get into its main channel. Before the Dali hit the bridge, it had no tugs. Thirty seconds later, the pilot ordered the ship’s anchor to be dropped and gave “additional steering commands,” said Marcel Muise, the lead investigator.

At 1:27 a.m., the pilot reported that the Dali had lost all power and was approaching the bridge, Muise said. At the time, there were two Maryland Transportation Authority units at the scene because of the ongoing construction, and those units shut down all lanes of traffic on the bridge, according to Muise.
He said the voice data recorder captured “sounds consistent with the collision” at 1:29 a.m. Around this time, the lights on the Key Bridge also went out.

I knew it.

look at the timeline.

1:24 - event starts
1:27 - power loss
1:29 - collision

Perps had 5 minutes to record GPS coords‚
generate a vector‚ remap it back to simulation
runs and determine the exact time to re-activate
with steering instructions to target the pylon.

.

the first thing professional hackers do is remove
as many history logs as they can‚ to remove when
and how they broke in.?

.

This should be perma pined

My guess days before .looks like each ocean going ship can become battle ram.

Coming from an engineering standpoint if I circled the exact target spot where to take out the major support they bullseyes it. What a coincidinky!

Of course.

56 containers of hazardous materials

764 tons of hazardous materials

Some are class 9 to include lithium ion batteries.

yeah during the previous failure a few days before

.

"sheen" from breached containers was noted on the water way.

9/11 by sea instead of air.

.

Are the lack of the data in the logs due to a shitty design of the VDR and its data recording, where loss of ship power results in no data uptake? That'd be one reason to cut the power, if one wanted to steer a ship into a bridge, not to mention the power loss is being used to explain the strike. One of the first recommendations that they ought to make for increased safety are better systems for recording ship parameters into the VDR.

This is why cyber attacks are the perfect weapon....no evidence, since its all electronic.

I cant even imagine the finger pointing and problems with even a MINOR EMP event, let alone a major nuclear-caused one.

Impossible to figure out anything, and NO...We wont be talking about it here on GLP, or anywhere, when they clamp down because of "security concerns".

Dhs using elons nro mazor 5ghz sattelite.

they almost certainly used existing ship steering
training software to create the simulation runs.

my guess is you can find that class of ship
modeled in software with its speed and
turning capabilities already embedded.

probably even an API to export the runs in
some standard format and ability to
replay them.

.

.

21 crew members plus two pilots



13 min mark of the YouTube video is especially interesting documenting the VDR on and off again

Why is VDR audio data using a redundant power source, but not the sensor data? It would seem that important sensor data should be also have a redundant power source. They have big gaping holes in the data stream during the period that the ship was moving in the direction of the bridge.

VERY suspicious!

also, an all indian crew is VERY suspicious!

isn't the crew usually more disparate?

At 17 min in~ NTSB explains VDRs are very basic and not comparable to a black box on commercial airliners



.

Paying off 23 non-whites of one nationality seems easy peasy.

I'd say so, if cutting power to the ship results in huge gaping holes in the data stream.

I heard from an expert yesterday saying they are the same thing and that it would definitely provide all the info and he knew about the power outages....so, that obviously shoulx not be a factor.


INDIANS ATTACKED US.

WHO PAID THEM?!?!?!?!?!

FUCKING JEWS, OF COURSE!

Perfect example of human inefficiency, and willingness to spend money to upgrade outdated systems...

All the shit CTs fret about could be easily explained if we upgraded info systems so data would be recorded...then we could have some REAL conversations, when it doesnt work, and its obviously manipulated...

until then, we are just internet pariahs, feeding off of insecurities...LOL

Bridge length 9,090 feet length.


30,060 vehicles per day use the bridge


Fracture critical bridge.


Bridge was in Satisfactory condition.

no

Hell, with that design, all you would have to do is cut power, steer the ship into the bridge, while speaking into the microphone like you are actually doing the opposite. Maybe quickly correct, after you're dead on target, and flip the power back on to get some data points that seem to match the previous audio, and then call it in that you just knocked down the bridge. With the data recorder down, it might not show if someone had rigged the system to still supply necessary power to the rudder system. If that's the case, hopefully they can pick it up with the audio, after it is filtered.

Where are our number tards when you need them?

If I had any doubt that it was deliberate...that is now gone.

This is the cameras in the jail turned off at the same time that Epstein hanged himself moment.