Crew Reviews, Ratings & Info for Lyrika
IMO: 9080675
General Cargo Ship, Latvia
Photos
Vessel Details
MMSI
275553000
Callsign
YLLY
Width
12.0 m
Length
89.0 m
Reviews (1)
Eugene
2025-04-22
Position: Safety Officer
Advantages:
Looking for information about this vessel. Trying to find out more about this ship? Was the pay decent?
Disadvantages:
No personal experience yet, just gathering info.
Latest News (3)
Urgent Medical Evacuation Near Tarifa: Crew Member Airlifted from 'Lyrika'
In a swift response to a medical emergency, the Rome Maritime Rescue Coordination Centre (MRCC) initiated a medevac for a crew member aboard the vessel 'Lyrika', which was navigating approximately seven nautical miles southwest of Tarifa. The ship was en route from Gdansk to Limassol when the situation arose. The Tarifa branch of Salvamento Marítimo quickly sprang into action, deploying the Helimer 211 helicopter to facilitate the evacuation. The affected crew member was airlifted and subsequently taken to Jerez Airport, where arrangements were made for immediate transfer to a hospital for further medical care.
Weser Incident: Cargo Ship Lyrika Collides with Dredger Barge
On October 1, 2018, at approximately 4:45 PM, the cargo vessel 'Lyrika' experienced a rudder malfunction while navigating the Weser River near Bremen-Farge, en route from Bremen to Hamburg. The loss of steering control caused the ship to drift off its intended path, resulting in a collision with a nearby moored dredger barge and tug. Fortunately, the 'Lyrika' sustained only minor abrasions, and a towing wire on the starboard side was severed in the impact. After assessing the situation, the ship continued to Brake for further examination. Authorities from the Bremen police initiated an investigation into the incident. The 'Lyrika' departed Brake on the evening of October 2 at 5 PM, successfully reaching Hamburg by October 4 at 5:50 AM. Later that same afternoon, it set sail for Buckie, with an expected time of arrival on October 8. For more details, visit the German report with accompanying photographs here: https://www.presseportal.de/blaulicht/pm/35235/4080194
Freighter Collision Near Heligoland: Key Details Unveiled
On February 12, 2012, a maritime incident occurred 20 kilometers southeast of Heligoland, where the freighter 'Lyrika' sustained damage after a collision at 10:15 p.m. The vessel, which was anchored at the time, was struck by another freighter that failed to stop following the impact. The Federal Police later tracked down the offending vessel, discovering that its captain was operating under the influence, with a blood alcohol level of 0.7 per thousand. As a consequence, the captain was fined €5,300 by prosecutors in Itzehoe. The ship involved in the collision managed to dock in Hamburg later that night, while the 'Lyrika' made its way to Cuxhaven for a thorough damage assessment.
Frequently Asked Questions
🤕 Were there any injuries or accidents on Lyrika?
Based on available news reports, Lyrika has been mentioned in connection with injury-related incidents. There have been 1 news reports mentioning injury incidents. For detailed information about specific incidents, please refer to the latest news section above.
🛠️ Did Lyrika experience any breakdowns or mechanical failures?
Based on available news reports, Lyrika has been mentioned in connection with breakdown-related incidents. There have been 1 news reports mentioning breakdowns. For detailed information about specific incidents, please refer to the latest news section above.
💥 Was Lyrika involved in any collisions?
Based on available news reports, Lyrika has been mentioned in connection with collision-related incidents. There have been 2 news reports mentioning collisions. For detailed information about specific incidents, please refer to the latest news section above.
🧑🚒 Was Lyrika involved in any migrant rescue operations?
Based on available news reports, Lyrika has been mentioned in connection with migrant-related incidents. There have been 1 news reports mentioning migrant operations. For detailed information about specific incidents, please refer to the latest news section above.