3 ms·
That Husky Racer incident is interesting - particularly because correct weight data was eventually given by the shippers, but that data didn't propagate through
by oasisbob 9y ago
That Husky Racer incident is interesting - particularly because correct weight data was eventually given by the shippers, but that data didn't propagate through Maersk's systems. Wonder if a dependence on removable media had anything to do with it.
> The MAIB preliminary examination of the accident found that the inaccurate container weights were on the loading plan because of a system shortcoming which did not update the operations department when the shipper provided more accurate contents details to the carrier.
> The Deputy Chief Inspector of Marine Accidents has written to Maersk Line advising that its operations department should use the most accurate container weights and ship stability data available. [1]
[1] https://www.gov.uk/maib-reports/collapse-of-containers-on-container-feeder-vessel-husky-racer-in-bremerhaven-germany-resulting-in-the-loss-of-18-containers-overboard https://www.gov.uk/maib-reports/collapse-of-containers-on-co...
- bkor 9y ago> Wonder if a dependence on removable media had anything to do with it. Not at all. It's better to ignore that bit out of the article. You actually have loads of parties giving a weight of a container. E.g. when the booking is made, then when they give the shipping instructions, then later maybe from a trucker when it's delivered to the terminal, lastly possibly given by the terminal itself (though most don't have it). What might have occurred that instead of having a sane design whereby you just update a weight of a container it works by having multiple different fields for these things. This as not always you can trust some input. E.g. weight given by a trucker in Germany might be ok, but it might be utter xxx in another country. I find it interesting that it was just an advice though. I'd prefer if they would have more ability to force changes and also across companies.