Damn it man! Didn't just collide, it knocked that sucker down, destroyed it. Wonder if any big targets happened to be crossing at the time. Those last trucks off were dang sure lucky.
Clear, and better footage here. Looks like the ship was billowing a lot of smoke before the hit. IMO, steering controls, or power could have been damaged from a fire. Or, considering how much smoke there is, the captain steering the ship could have been blinded by the smoke. Smoke that thick is impossible to see through at night, and lights do nothing- possibly explaining why ship lights turn off/on.
But, the lights turning off/on could also be caused by damaged electric power systems, or maybe even a person trying whatever they could do to try signal a warning to drivers on the bridge.
My hunch at this time is that there was a massive fire on the ship, likely caused from EV batteries, and hot enough to do major internal damage to the ship.
The smoke is likely from the main engines due to either full reverse to try to avoid the bridge or full ramming speed. I don't think it was an EV fire, as the ship isn't still burning.
The light outages just before collision is interesting. I assumed it was indicative of power and possible control issues aboard the vessel, but you are right it could have been an attempt at a warning. I wish there was audio to see, uhh hear, if they were sounding their horn to warn of an impending collision.
All that said, it is mighty peculiar that they hit and destroyed a bridge with THAT name. Its also possible the captain was sabotaged as well.
Watching this ship & knowing that ships can be hacked & controlled (dickbutt before the Suez canal was blocked on the tracking radar gave that evidence), it could be a foreign power attacking, or even our own whitehats for some reason.
Doing a hard reset to try & gain control again might do it, but my limited understanding of basic hacking leads me to believe that even resetting all power is a futile attempt & you might gain seconds or minutes (if lucky) of control back.
It would be better to be able to cut all network/GPS signals (maybe jam them) to prevent external communications.
Here is some analysis by some shipping "expert". I put it in quotes, because I have no idea who this guy is. But I think its worth a listen. At the very least, he has real time tracking of the ship and you can see they were on course and in channel until around the power blip. Then when power comes back on and the smoke really bellows, the ship begins to slow down, but its too late.
Perhaps, but assuming this was just another average and routine morning preparing for a 30-day journey and all systems go, it stands to reason that the ship would still be traveling rapidly after engine failure.
Damn it man! Didn't just collide, it knocked that sucker down, destroyed it. Wonder if any big targets happened to be crossing at the time. Those last trucks off were dang sure lucky.
Probably a DEI crew in charge.
Prayers for the innocent.
https://twitter.com/indiancrusher/status/1772531393027076111?s=20
Clear, and better footage here. Looks like the ship was billowing a lot of smoke before the hit. IMO, steering controls, or power could have been damaged from a fire. Or, considering how much smoke there is, the captain steering the ship could have been blinded by the smoke. Smoke that thick is impossible to see through at night, and lights do nothing- possibly explaining why ship lights turn off/on.
But, the lights turning off/on could also be caused by damaged electric power systems, or maybe even a person trying whatever they could do to try signal a warning to drivers on the bridge.
My hunch at this time is that there was a massive fire on the ship, likely caused from EV batteries, and hot enough to do major internal damage to the ship.
The smoke is likely from the main engines due to either full reverse to try to avoid the bridge or full ramming speed. I don't think it was an EV fire, as the ship isn't still burning.
The light outages just before collision is interesting. I assumed it was indicative of power and possible control issues aboard the vessel, but you are right it could have been an attempt at a warning. I wish there was audio to see, uhh hear, if they were sounding their horn to warn of an impending collision.
All that said, it is mighty peculiar that they hit and destroyed a bridge with THAT name. Its also possible the captain was sabotaged as well.
Agreed, the smoke is because of the engines running at max rpm.
The lights going on and off could have been an attempt by the crew to regain control of the ship, after being hacked.
Watching this ship & knowing that ships can be hacked & controlled (dickbutt before the Suez canal was blocked on the tracking radar gave that evidence), it could be a foreign power attacking, or even our own whitehats for some reason.
Doing a hard reset to try & gain control again might do it, but my limited understanding of basic hacking leads me to believe that even resetting all power is a futile attempt & you might gain seconds or minutes (if lucky) of control back.
It would be better to be able to cut all network/GPS signals (maybe jam them) to prevent external communications.
Another interesting thought. 👌
Here is some analysis by some shipping "expert". I put it in quotes, because I have no idea who this guy is. But I think its worth a listen. At the very least, he has real time tracking of the ship and you can see they were on course and in channel until around the power blip. Then when power comes back on and the smoke really bellows, the ship begins to slow down, but its too late.
https://www.youtube.com/watch?v=N39w6aQFKSQ
Or warning everyone around them of danger?
full ramming speed, remotely controlled ship
Perhaps, but assuming this was just another average and routine morning preparing for a 30-day journey and all systems go, it stands to reason that the ship would still be traveling rapidly after engine failure.
It could be from the smoke stacks. https://www.marineinsight.com/tech/black-smoke-coming-ships-funnel-port/
Apparently, the smoke should not be black in port however.