The Ever Forward, a Hong Kong flagged ship operated by Evergreen, the 7th largest container shipping line in the world, was on its way from the port of Baltimore in Maryland US to Norfolk when it is said to have missed a southbound turn in the Chesapeake Bay and ran aground around 00:15 hrs (UTC) on the 13th of March 2022 near Gibson Island in the Chesapeake Bay channel..
The U.S. Coast Guard based in Maryland conducted a marine casualty investigation into the incident and arrived at two key conclusions
- Failure to maintain situational awareness and attention while navigating
- Inadequate bridge resource management
Why did the Ever Forward run aground
Quoting from my previous article about Who is a Marine Pilot and what is their role in the maritime industry,
The pilot has the onerous task of navigating the ship into the local port as they have overall expertise on specific local conditions existing in the port area. The local pilots are aware of channel depths, any dredging operations done, navigational hazards like underwater cables, and other obstacles. In general, they provide local knowledge and experience to the Captain of the ship to ensure that navigational safety and the environment are not compromised.
In the case of the Ever Forward, it was under the direction and control of a licensed Maryland State Pilot..
The Maryland Pilot was on the bridge directing the ship in the presence of the Master of the ship and the bridge team.. The Master subsequently left for dinner and eventually a 3rd Officer, Deck Cadet, and an Able Bodied Seaman were on the bridge along with the Maryland Pilot..
As per the report from the Coast Guard, no order was given by the Maryland Pilot to make a turn at the charted waypoint in order to proceed in accordance with the voyage plan.. Since there was no order from the Maryland Pilot, the helmsman continued on the previously ordered course..
By the time the pilot recognized that the turn was missed and tried to correct the course, the ship was grounded outside the Craighill Channel, east of Lighted Buoy 16..
The Maryland Pilot’s attempts along with the bridge team to free the ship failed.. The Master of the ship (back on the bridge) performed a series of safety checks in accordance with the ship’s Safety Management System (SMS), prior to continuing efforts to free the ship..
The Master of the ship eventually notified the ship’s shoreside representative that the EVER FORWARD required assistance and the Maryland Pilot was subsequently replaced by another licensed pilot..
The investigations revealed that during the transit, the Maryland Pilot was solely relying on his Portable Pilot Unit (PPU) as the primary means of navigation as he was in the practice of intentionally not using any other navigation equipment while underway, citing a distrust of ship’s equipment that was not his own and instances of equipment breaking while a pilot was using it..
The investigation also revealed that just prior to the grounding, the Maryland pilot exited the active navigation of his PPU to view a previous transit and also made a series of five phone calls amounting to over 60 minutes of time during the course of his outbound transit.. The Maryland Pilot was also texting and drafting emails immediately before the grounding occurred regarding issues he experienced with facility line handlers..
Points of concern
The Maryland Pilot was in the midst of almost hour-long personal calls and work-related texts during the transit of the Ever Forward..
While I am not a maritime or navigational expert by any means, apart from the above issue of texting and driving, I have the below concerns..
- The Maryland Pilot cited “a distrust of vessel equipment that was not his own
and instances of equipment breaking while a pilot was using it” as per the report.. Surely you cannot navigate a ship without trusting its equipment and while the report says nothing about whether this distrust was communicated to the Master of the ship or bridge team, I think this is a matter of concern..
- As a consequence of the above distrust, the Maryland Pilot “was solely relying on his Portable Pilot Unit (PPU) as the primary means of navigation“
- However, at the time of the incident, he was viewing another screen on his PPU – the only equipment being relied upon for the transit – for an issue relating to data from another voyage, which caused the recording of the Ever Forward transit to be stopped till after the grounding of the ship when the Maryland Pilot returned to the active screen..
- In my view, point 3 is key as there was no active screen for the Maryland Pilot to refer to when the ship missed the turning at the charted waypoint..
- Added to the above, the report states that all the ship’s charts (paper and electronic) were up-to-date and if the Maryland Pilot was not confident of the ship’s equipment, he could have made use of the paper charts which were being used by the bridge team, especially since his PPU was not on the active transit..
- I found the absence of the Master of the ship or at least his 2nd in command during transit with the pilot on board a bit off.. I am not sure whether this is normal, but I am told that “I do raise a point here”..
If you are an experienced Marine Pilot, I would like to know whether what the Maryland Pilot felt in terms of his trust level with the ship’s equipment is correct and does this happen often..??
That would then open up another discussion in terms of tools used to do the job in the maritime industry..
The U.S. Coast Guard determined no mechanical issues or equipment failures contributed to this marine casualty and the causal factors that contributed to this casualty (include)
- Failure to maintain situational awareness and attention while navigating – read “texting and calling while piloting“
- Inadequate bridge resource management – possibly to be read as “the absence of the Master or 2nd in command on the bridge at the time of transit“