Reviews & Ratings for the City-Of-Rotterdam
IMO: 9473468
Vehicles Carrier, Panama
Photos
Vessel Details
MMSI
372002000
Callsign
3FUA7
Width
22.0 m
Length
140.0 m
Reviews (1)
Johnny
2025-01-01
Position: Second Engineer
Advantages:
Looking for information about this vessel. Looking for info about this vessel? How was the atmosphere onboard?
Disadvantages:
No personal experience yet, just gathering info.
Featured Review Articles
Lessons Learned from the Collision Involving City-Of-Rotterdam
The City-Of-Rotterdam has been at the center of scrutiny following a significant maritime incident that occurred on December 3, 2015, when it collided with the 'Primula Seaways' in the River Humber. This collision has since led to legal repercussions...
Read Full ReviewLatest News (3)
Four-Month Prison Sentences for Captain and Pilot of the City of Rotterdam Following Collision
In a recent legal decision, the captain and pilot of the cargo vessel 'City of Rotterdam' have each been handed four-month prison sentences due to their involvement in a maritime accident with the vessel 'Primula Seaways' that occurred on December 3, 2015. Captain Ruslan Urumov and pilot Gehan Sirimanne both admitted guilt to charges of conduct endangering a ship. However, the court has granted a suspension of their sentences for a duration of 18 months. As part of the ruling, Sirimanne will also be responsible for covering $60,000 in court costs, which will be paid by his former employer, Associated British Ports. On that fateful evening, the 'City of Rotterdam' set sail from the port of Inningham in England. As the ship navigated outbound, it encountered significant winds and a strong tidal stream that diverted its course toward the inbound lane where the 'Primula Seaways' was traveling at a speed of 14 knots. A watchstander from the Vessel Traffic Service (VTS) foresaw the impending danger and warned the 'Primula Seaways', but corrective actions were insufficient. Despite the pilot's attempts to make a series of gradual course adjustments to counteract the wind and tide, a collision ensued. The 'City of Rotterdam' sustained extensive damage above and below the waterline, including a considerable breach along her port bow. Meanwhile, the 'Primula Seaways' required substantial repairs estimated at around $3 million affecting her bow and forecastle. An investigation by the UK Marine Accident Investigation Branch (MAIB) attributed the incident to the pilot's loss of situational awareness, exacerbated by an unconventional bridge design of the 'City of Rotterdam'. The MAIB noted that the pilot misjudged the ship’s directional movement due to a phenomenon known as 'relative motion illusion'. The semi-circular layout of the bridge windows, which limits the pilot's forward view to only one window directly ahead, contributed to this confusion. Consequently, only the centerline is visible, which can leave watchstanders disoriented, even when aware. Audio recordings from the voyage revealed that before the accident, pilot Sirimanne mistakenly thought he was navigating in the direction he was facing. Captain Urumov was present on the bridge but did not take action until it was too late to avert the collision. During the court proceedings, it was noted that both individuals had a well-respected standing in the maritime industry, with over 30 years of sea experience each. Judge Jeremy Richardson acknowledged the role that the ship’s design played in the accident during the sentencing, highlighting the complexities nautical professionals face.
Pilot Error Leads to Collision of City of Rotterdam and Primula Seaways in December 2015
A recent report by the Marine Accident Investigation Branch (MAIB) reveals that a disoriented pilot was responsible for the collision between the vessels 'City of Rotterdam' and 'Primula Seaways' on the River Humber. This unfortunate incident occurred in December 2015, primarily due to a navigational judgment error made by the pilot of the 'City of Rotterdam.' The findings of this investigation were published on February 8, 2017. For a detailed account of the events leading to this maritime accident, you can access the full MAIB report [here](https://assets.publishing.service.gov.uk/media/58984f60ed915d06e1000025/MAIBInvReport3_2017.pdf).
Repairs Concluded for City of Rotterdam After Collision
The extensive repairs to the 'City of Rotterdam,' which sustained damage from its collision with the 'Primula Seaways' on December 3, have officially been completed. The shipyard at Port of Tyne finished the necessary work by February 28 at 2:30 p.m. Following the repairs, the vessel departed British waters and headed for Zeebrugge, marking its first port of call post-accident, where it docked on February 29 at 1 p.m. It will then continue its journey to Esbjerg.
Frequently Asked Questions
🌊 Did City-Of-Rotterdam sink or have any sinking incidents?
Based on available news reports, City-Of-Rotterdam has been mentioned in connection with sinking-related incidents. There have been 2 news reports mentioning sinking incidents. For detailed information about specific incidents, please refer to the latest news section above.
🤕 Were there any injuries or accidents on City-Of-Rotterdam?
Based on available news reports, City-Of-Rotterdam has been mentioned in connection with injury-related incidents. There have been 3 news reports mentioning injury incidents. For detailed information about specific incidents, please refer to the latest news section above.
⚙️ Did City-Of-Rotterdam have any engine problems?
Based on available news reports, City-Of-Rotterdam has been mentioned in connection with engine-related incidents. There have been 2 news reports mentioning engine problems. For detailed information about specific incidents, please refer to the latest news section above.
💥 Was City-Of-Rotterdam involved in any collisions?
Based on available news reports, City-Of-Rotterdam has been mentioned in connection with collision-related incidents. There have been 3 news reports mentioning collisions. For detailed information about specific incidents, please refer to the latest news section above.