Discover the Scotland-Bay: Ratings & Maritime News
IMO: 9276200
Bulk Carrier, Palau
Photos
Vessel Details
MMSI
511101118
Callsign
T8A4379
Width
27.0 m
Length
170.0 m
Reviews (1)
Terry
2024-02-28
Position: Radio Officer
Advantages:
Looking for information about this vessel. Any reviews on this vessel? Was the crew alright?
Disadvantages:
No personal experience yet, just gathering info.
Latest News (3)
ATSB Releases Final Report on 'Portland Bay' Near Grounding Incident
On May 15, 2025, the Australian Transport Safety Bureau (ATSB) issued its final report addressing the near grounding of the 'Portland Bay', now rebranded as 'Scotland Bay', which occurred near Sydney in July 2022. The investigation prompted formal recommendations to three government agencies and a salvage operator. The incident unfolded on July 3, when the vessel was docked at Port Kembla. Due to worsening weather conditions, the harbour master and ship’s master made the decision to navigate the ship offshore until the weather improved. However, after departing Port Kembla, the 'Portland Bay' was found to be operating significantly closer to the coast than the prescribed limit of 50 nautical miles set by the ship’s own protocols. Early on July 4, as the vessel was drifting approximately 12 miles from the coast, a main engine failure occurred, causing the ship to drift perilously close to the rocky shoreline. The master of the vessel encountered delays when reporting the incident, and further complications arose when NSW authorities failed to relay this information promptly to the Australian Maritime Safety Authority (AMSA). It took several emergency broadcasts and a radio distress call before help was dispatched. A harbour tug arrived nearly five hours after the ship lost power. By that time, the master had deployed both anchors one mile off Royal National Park's rocky shoreline, successfully slowing the vessel’s drift until additional harbour tugs arrived hours later. Despite these efforts, a tug’s towline failed, causing the 'Portland Bay' to drift towards the shore once again, necessitating a second deployment of both anchors. Exacerbating the situation was the delay in activating the state’s designated emergency tug, the 'Svitzer Glenrock'. The Port Authority of NSW led the initial response, with AMSA and NSW Maritime supporting. The request for the 'Svitzer Glenrock' was made around midday on July 4 but was mishandled between the agencies, leading to an unacceptable wait of nearly 13 hours before the tug was dispatched. After a challenging 90-nautical-mile journey from Newcastle, the 'Svitzer Glenrock' finally arrived 30 hours post-disablement and, more than 48 hours after the emergency began, the vessel was safely towed into Port Botany for repairs. The ATSB investigation revealed eight critical safety concerns related to the emergency response, emphasizing a lack of coordination among the involved agencies. The report highlighted deficiencies in effective implementation of procedures by AMSA and the Port Authority of NSW, as well as NSW Maritime’s failure to prepare for such incidents. Although the efforts of the initial responding tug crew were commendable under adverse conditions, the report criticized the inadequacy of the three deployed harbour tugs which were not equipped for effective towage in rough seas, especially considering 'Portland Bay's 15,500-tonne weight. AMSA, along with the ship’s management company, has begun addressing several of the safety concerns outlined in the report. However, ATSB identified that eight safety issues remain unresolved. Consequently, safety recommendations were made for AMSA, the Port Authority of NSW, NSW Maritime, and United Salvage to enhance responses to maritime emergencies. These recommendations include improved implementation of emergency procedures, better understanding of responsibilities, and clear communication of salvage capabilities. The ATSB will continue monitoring these organizations for progress on implementing the proposed safety actions. For full details of the report, visit the ATSB's official publication page.
Critical Timeline Revealed of 'Portland Bay' Near Miss with NSW Coast
The Australian Transport Safety Bureau (ATSB) has unveiled a comprehensive timeline detailing a frightening incident involving the cargo vessel 'Portland Bay' which occurred on July 4, 2022, amidst treacherous seas. Around 6 a.m., the ship experienced a catastrophic engine failure, propelling it perilously close to the coastline of New South Wales. Despite the initial detection of smoke onboard, authorities in Port Kembla were only alerted at 6:58 a.m., nearly an hour after the incident began. On July 3, 'Portland Bay' was instructed by Vessel Traffic Services to depart Port Kembla due to the rough weather that posed a threat to both the wharf and the ship itself. Early on the 4th, the main engine was cut but was later restarted just as the vessel began to surge and roll violently in the turbulent waters. At approximately 4:50 a.m., two fire detectors in the engine room activated, prompting the crew to identify smoke shortly thereafter. By around 5 a.m., the chief mate began to reduce the main engine's speed, moving to dead slow ahead shortly after. At around 6 a.m., the master of the vessel notified the ship's managers of the engine failure and the deteriorating situation; however, no alert was sent to Vessel Traffic Services at that time. An urgency message was finally broadcast at 7 a.m., placing the ship about 11 miles south of Botany Bay and 5.8 miles offshore. Marine Rescue NSW acknowledged the message, but it wasn't until 7:44 a.m. that the Australian Maritime Safety Authority was informed, by which point the vessel was at significant risk of running aground. By 8 a.m., plans were underway for a potential evacuation, considering the imminent danger of the ship grounding on the rocky shore. Just minutes later, the master issued distress alerts via maritime satellite communications and radio frequencies. At 8:30 a.m., the general emergency alarm was sounded as the captain contemplated abandonment. Though rescue helicopters arrived by 9 a.m., they had to abort rescue attempts due to the instability of the ship. Ultimately, as the vessel drifted dangerously close—just one nautical mile offshore and in 45 meters of water—the master managed to anchor it. Tugboats were dispatched to brave the perilous seas and facilitate the rescue of the crew. The forthcoming ATSB final report will examine all contributing factors, including onboard emergency responses and actions from maritime authorities.
Filipino Captain Faces Penalties for Sulfur Pollution on Portland Bay
On October 14, 2012, the Philippine captain of the cargo vessel 'Portland Bay', which was docked at Elbe Port in Brunsbüttel, encountered legal troubles due to excessive sulfur in the ship's diesel fuel. The vessel, which had recently transported copper concentrate from Brazil, was found to be operating without low-sulfur diesel fuel. During a routine inspection conducted by the Brunsbüttel water police, authorities discovered that the sulfur content of the onboard fuel ranged between 0.18% and 0.32%. As a result, the captain was required to pay a guarantee deposit of €1,780. Facing potential misdemeanor proceedings, the captain is now awaiting further developments regarding the situation.
Frequently Asked Questions
🔥 Were there any fires on Scotland-Bay?
Based on available news reports, Scotland-Bay has been mentioned in connection with fire-related incidents. There have been 1 news reports mentioning fire incidents. For detailed information about specific incidents, please refer to the latest news section above.
🌊 Did Scotland-Bay sink or have any sinking incidents?
Based on available news reports, Scotland-Bay 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.
🛠️ Did Scotland-Bay experience any breakdowns or mechanical failures?
Based on available news reports, Scotland-Bay has been mentioned in connection with breakdown-related incidents. There have been 2 news reports mentioning breakdowns. For detailed information about specific incidents, please refer to the latest news section above.
⚙️ Did Scotland-Bay have any engine problems?
Based on available news reports, Scotland-Bay 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 Scotland-Bay involved in any migrant rescue operations?
Based on available news reports, Scotland-Bay 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.
🛢️ Did Scotland-Bay have any oil spills or pollution incidents?
Based on available news reports, Scotland-Bay 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.