Discover the Omskiy-137: Ratings & Maritime News
IMO: 8873087
General Cargo Ship, Russia
Photos
Vessel Details
MMSI
273313900
Callsign
UANQ
Width
15.0 m
Length
108.0 m
Reviews (1)
Steven
2025-01-28
Position: Cook
Advantages:
Looking for information about this vessel. Has anyone worked on this vessel? Any red flags?
Disadvantages:
No personal experience yet, just gathering info.
Latest News (2)
Grounding on Svir River
The "Omskiy 138" ran agorund on the Svir River in the Podporozhsky district on Aug 14, 2019, at 5 a.m. while moving towards Ivinsky. The ship suffered a leak at port side and water ingress. It was carrying a cargo of 2.500 tons tons of timber, bound for Sweden, and a had on board a crew of 12. The crew was unable to control the water ingress in the bballast tanks. The ship, which was stuck outside the fairway, was to be lightered. A part of the cargo was to be loaded onto the sister ship "Omskiy 133" with a floating crane.
Grounding on the Neva
The 'Omskiy 137' ran aground on July 3, 2018, at 3.10 a.m. near the Volodarskiy Bridge in St. Petersburg on the Neva river at kilometer mark 1368. The ship was proceeding downstream with cargo of wood chips, bound for Södra Monsteras and ran aground while anchoring. It was refloated around midday and taken to a nearby berth for inspections. Later that day it was moved upriver and moored outside the city limits in pos. 59° 50.74' N 030° 29.61' E where it remained on July 4.
Frequently Asked Questions
🌊 Did Omskiy-137 sink or have any sinking incidents?
Based on available news reports, Omskiy-137 has been mentioned in connection with sinking-related incidents. There have been 1 news reports mentioning sinking incidents. For detailed information about specific incidents, please refer to the latest news section above.
🛢️ Did Omskiy-137 have any oil spills or pollution incidents?
Based on available news reports, Omskiy-137 has been mentioned in connection with spill-related incidents. There have been 1 news reports mentioning spills. For detailed information about specific incidents, please refer to the latest news section above.