This news report [1] confirms there were two pilots at the time of the accident. Baltimore Port runs a dock pilot from the Key Bridge to the port itself, and after the Key Bridge, a harbor pilot who takes the ship (I believe the rule is any vessel > 100 tons, and all non-domestic ships of any tonnage must by Maryland state law be piloted in this manner) out to the mouth of the bay.
The after-accident report and insurer and re-insurer wranglings will be a fascinating read, I'm sure. It will be a miracle if the taxpayers escape unscathed for the rebuilding of the transit spanning the harbor, and it falls entirely upon the insurers and re-insurers.
As dramatic as this accident was though, and the many parallels I can draw from its lessons to software engineering, IT operations, cybersecurity and so on, I'm not as sanguine believing it will really drive home to organization leaderships the evergreen advice to pay down your tech debt, maintenance matters, organizational culture/esprit de corps counts, the operational teams are just as important as the engineering teams, etc.
The after-accident report and insurer and re-insurer wranglings will be a fascinating read, I'm sure. It will be a miracle if the taxpayers escape unscathed for the rebuilding of the transit spanning the harbor, and it falls entirely upon the insurers and re-insurers.
As dramatic as this accident was though, and the many parallels I can draw from its lessons to software engineering, IT operations, cybersecurity and so on, I'm not as sanguine believing it will really drive home to organization leaderships the evergreen advice to pay down your tech debt, maintenance matters, organizational culture/esprit de corps counts, the operational teams are just as important as the engineering teams, etc.
[1] https://fox59.com/news/national-world/cargo-ship-hits-baltim...