Category Archives: oops

BREAKING: Fire on Halifax Bound Ship.

** I have sticky’d this post to the top of the front page, and will continue with chronological updates. New posts will appear below this.

The container ship Yantain Express, suffered a container fire yesterday. Efforts to fight the fire were reportedly suspended due to weather.

The ship is a regular caller to Halifax on the EC5 Service and was due today at Fairview cove. That arrival has since been delayed. Hapag lloyd issued the following statement

The crew of 8 officers and 15 seafarers is unharmed. Efforts to extinguish the fire in the containers were launched immediately but have had to be suspended for the time being due to a significant deterioration of weather conditions.

The 7,510 TEU vessel, which is 320 meters long and sails under German flag in the East Coast Loop 5 (EC5) service, was built in 2002 and was on its way from Colombo to Halifax via the Suez Canal. At present, the ship is approximately 650 nautical miles off the coast of Canada.

It is still too early to make a precise estimate of any damage to the vessel or its cargo. Hapag-Lloyd is closely cooperating with all relevant authorities.

Updates will Follow as they are known

UPDATE Jan 4, 1449:
SAR responsibility is with the USCG 5th District (Mid Atlantic) out of Virginia. Awaiting updates from Marlant PAO and USCG 5th PAO.

the last Halifax container fire was in 2001 aboard the 3800TEU Kitano

UPDATE 1542:

USCG 5th District PAO informed me that they were notified of the situation this morning, with the ship approximately 980nm South East of Cape Cod. The USCG watch-standers are monitoring the situation at this time. there is a Good Samaritan vessel on Scene, but no other response at this time.

Photo reportedly from a crew member, sent to maritimeBulletin.net

UPDATE 2255:
questions were raised about the authenticity of the above photo. nothing can be confirmed, however there look to be several orange Hapag-Lloyd Containers, and several magenta ONE containers, which suggests a recent photo from a ship operating for the Alliance.

Word is the tug Smit Nicobar is on scene to assist with firefighting, and the BigLift vessel Happy Ranger responded to the initial call and is standing by.

Update Jan 5, 0920:
Hapag-Lloyd spokes person Tim Seifert told me that overnight conditions were still to dangerous for firefighting to continue, and they are waiting on improved weather. the tug did arrive on scene to assist. he was unable to confirm if the photo above is real.

Update 1447:
the supply vessel Maersk Mobiliser has sailed from St. Johns NF to respond. The ship is giving an eta of 4am, Monday the 7th to arrive on scene.

UPDATE 1600:

photo posted to maritimeBulletin.net

UPDATE Jan 6, 1200:
12 of the crew have been transferred to the Smit Nicobar, the remainder will be taken off the ship. the Maersk Mobiliser is planning to tow the the ship to Halifax. Weather has improved, and firefighting from the Smit Nicobar is underway.

UPDATE 1300:
the remainder of the crew has been safely removed to the Smit Nicobar. Hapag Llyod reports all crew are unharmed. Firefighting efforts from the tug are ongoing. the ship is now reported to be 800NM off Nova Scotia.

Update Jan 7, 1000:
Maersk Mobiliser encountered heavy weather, and has not reached the ship yet, but is about 80nm away. Hapag-Lloyd has stated that the fire is not under control and has intensified at times. The USCG reports that firefighting is continuing today. The Happy Ranger departed after the arrival of the Smit Nicobar.

UPDATE 1043:

Minor Update – this is now the 5th most popular post of all time.

UPDATE 1252:
Maersk Mobiliser has arrived on scene, and will assist with firefighting efforts before towing the Yantain Express to Halifax.

Update 1428:
the Halifax Employers Association is giving an ETA of the 18:00 on the 16th for the Arrival of Yantain Express. this is probably an optimistic estimate. The tow at a max speed of 5 knots will take about 10Days.

UPDATE Jan 8, 0956:
USCG is reporting that the fire is still burning, with firefighting efforts continuing on and off last night.

UPDATE 1146:
Fire is still burning, Yantain Express is now drifting further from Halifax- now over 1112 nautical miles away.

This has to now be a significant fire. possibly spread to multiple stacks, or into the holds below deck.

The photos below Show what the spacing is like between stacks. Not an ideal place to fight a fire.

Note the Open hold on the right in the photo below.

View this post on Instagram

Lashing

A post shared by Peter Ziobrowski (@ziobrop) on

View this post on Instagram

More underneath

A post shared by Peter Ziobrowski (@ziobrop) on

View this post on Instagram

Middle hatch

A post shared by Peter Ziobrowski (@ziobrop) on

UPDATE Jan 9 0835:
the tugs are making progress however smoke is still pouring out of the ship according to a Canadian Press Report. the firefighting is taking place under the Direction of Smit, who have likely been hired on as salvors.

UPDATE Jan 10 1000:
Yantain Express looks to be under tow. its now heading towards Halifax at 1.5kn. The HEA is currently showing an eta of the 20th.

Update 1122:
Hapag-Lloyd has released a statement. Wednesday evening the fire was brought under control and is contained. 5 crew were transferred from the Smit Nicobar back to the Yantain express, and the ship was brought under tow by the Maersk Mobiliser, bound for Halifax. a third tug has been dispatched, with an eta of the 13th

UPDATE 1155:
We now have a Damage Report From Hapag-Lloyd:
Further to our CustomerInfo of January 7, 2019 we would like to provide you with following status update:
Based on the currently available information, we have to assume that all cargo in Bay 12 on deck and forward is directly affected by the fire, also all cargo in Hold 1 (Bay 1 to 9). Further, we have to expect that all cargo in Hold 2 (Bay 11 to 17) is affected by fire, smoke and / or damage caused by firefighting water. Damage caused by smoke, heat and / or firefighting water in adjacent areas is possible.
All Reefers in Bay 1 to 24 are without power and switched off. All other Bays with Reefers are continuously supplied with power and in operation.

red line shows stack 24 which is the extent of cargo loss.

Each stack has 3 number assigned to it. Odd numbers are for 20′ containers, and evens are for 40′ containers. essentially this is suggesting that all cargo in the first 8 stacks is effected.

UPDATE Jan 14 1000:

latest from CBC’s Brett Ruskin. I talked to him on Friday. Also Latest position.

UPDATE 1100:
I have been told that Hapag-Lloyd is sending a vessel direct to Halifax. Over the weekend the Tug Atlantic Enterprise arrived at pier 9. Owned by Donjon Marine of New Jersey, they work in a joint venture with Smit providing salvage services. it is assumed to be here as part of the salvage effort.

Atlantic Enterprise at pier 9

UPDATE 1203:
Shanghai trader sailed from Bremerhaven on the the 12th. Hapag Llyod shows it calling on the EC5 service with stops in Halifax and New York. due to arrive on the 18th, according to marine traffic. this will likely move undamaged cargo from the ship. the ship is rated at 5047Teu, and was built in 2005. Owned by Lomar Shipping, this is likely an available vessel for charter.

UPDATE 1324:
The tug Atlantic Enterprise is due to Sail at 9am tomorrow – its currently giving its destination as New Jersey. It arrived from New York.

UPDATE 1500:
the tug Sovereign sailed from Rotterdam with an eta of the 15th. vessel track suggests firefighting efforts have resumed, as weather is reported to be good. The tug is owned by Boskallis – smit’s parent company.

third tug responding
vessel tracks.

UPDATE Jan 15 0750:
The Horizon Star sailed around 6am from Halifax giving Yantain Express as her destination. I have reached out to Horizon Maritime for comment on the tasking.

UPDATE 1318:
TC has received a request for a place of refuge from the salvers.

Position as of noon Atlantic.

due to the length of this post, i have unsticked it from the front page, and replaced it with a link.

UPDATE 1521:
The Horizon Star is apparently bringing a salvage team and supplies to the incident.

UPDATE 2251:

The Philippine embassy in Ottawa released a statement:
“All 17 Filipino seafarers on board the Yantian Express have arrived safely in Halifax, Nova Scotia, on 14 January 2019, after they were evacuated from the burning container ship. Philippine Honorary Vice Consul in Halifax Ms. Elizabeth Eustaquio-Domondon reported that the seafarers were in high spirits and were being assisted by their fleet manager to arrange their return to the Philippines. The Filipino community in Halifax also met the seafarers and provided them with food and other necessities.”

The Tug Atlantic enterprise appears to have sailed out towards the Yantain express, and likely brought the crew back to Halifax. Its unclear how the Crew were transferred from the Smit Nicobar, as the two ships remained about 600km apart.

UPDATE Jan 16 11:50:
G-captain has photos from a crew member of a ship that passed 3 miles from the Yantain Express. the photos were taken yesterday, and smoke is still rising. for the bow of the ship.

Photo: Cameron Brunick via gCaptain

It looks as though the center of the stacks have collapsed and at least 3, if not 4 are significantly damaged. More photos are available at gCaptain

Photo: Cameron Brunick via gCaptain
Photo: Cameron Brunick via gCaptain

UPDATE 1300:
CBC was also provided the photos form the same source.

UPDATE 1330:
Smit Nicobar has sailed for Mexico, which was where it was headed before it responded to the fire. Horizon Explorer is still on route. No word on the Sovereign, which was sailing form Rotterdam. Maersk Mobiliser is in front, so the tow may have resumed at a speed of 2 knots.

UPDATE Jan 17, 0947:
the tug Sovereign has arrived on scene. the Ship may be under tow again, based on speeds and tug position.

UPDATE 2243:
Hapag Lloyd released an update today:
“The salvage operations show continuous progress.

The fire is widely contained and meanwhile the ocean-going tug “Union Sovereign” has arrived at the vessels position on January 15, 2019 to further assist the operations. Another ocean-going tug is on its way.

At this time, it is not yet possible to make a precise estimate of any damage to Yantian Express or its cargo; this can only be more clearly assessed once the vessel reaches a port.

Unfortunately, we cannot provide you with an ETA at the moment; this will be advised as soon as determined. We regret any inconvenience caused by this incident and shall keep you closely informed on actual development of the rescue operation and further proceedings.”

UPDATE Jan 20 2328:
The tow has been underway since the 16th, they have covered ~270nautical miles, making 70 nautical miles per day. Halifax no longer appears to be the destination – One of the tugs is showing Freeport Bahamas as the destination, and the shanghai trader arrived in Savannah Georgia today. That ship was dispatched from Bremerhaven to collect the undamaged containers.

Jan 20 position.

The reason for the change in location is unclear. Certainly not having to deal with North Atlantic weather could be one factor, Another possibility is that Canada refused a place of Refuge. request. I have requested status on this with Transport Canada, and will be attempting to figure out the ships new Destination.

UPDATE Jan 21 1314:
Maersk Mobiliser and Sovereign are giving their destination as Freeport Bahamas. Horizion Star is Headed back to Halifax, with an ETA of the 25th. No Word on a place of refuge from TC or the USCG as of yet.

Freeport does have a sizeable container terminal, equipped for transshipment so its certainly a plausible location.

UPDATE 1433:
We have a response from Transport Canada.

Transport Canada has received the initial request for a Place of Refuge from the vessel MV Yantian Express.
 
While Transport Canada continues to review the request for compliance with regulatory requirements, the salvage master has not confirmed Halifax as the next port for the MV Yantian Express

Note: I discussed the Insurance implications of this incident, and what a Place of Refuge is in the Chronicle Herald

Sincerity Ace on Fire in Pacific.

sister ship Cougar Ace at Autoport. COugar ace developed a list off Alaska, but was saved.

The PCTC Sincerity Ace caught fire Dec 31, 1800 nautical miles west of Hawaii. The crew attempted to fight the fire, but has since abandoned ship. 16 were picked up safe, 3 were found deceased in the water, and 2 are missing.

A car fire is a job by itself. Put that car fire in an enclosed space, with additional vehicles in very close proximity, and the fire has the potential to become very large very quickly. A photo posted to social media shows the ship with significant damage to the side of the ship reaching from the upper part of the Blue section, right to the top of the vessel. This suggests multiple decks are involved. – the area of the fire would be where the ramps between decks are located, providing a channel for fire spread.

Controlling the fire will likely prove to be very difficult, as there will be limited direct access to the flames without boarding the vessel. the fire will probably need to burn itself out, then the salvagers can put out any hot spots.

General Arrangement of the Cougar Ace, showing deck layout.

The ship was built in 2009, and is part of the MOL car carrier fleet. The ship called at Autoport once in February 2013.

UPDATE: Jan 4/19

Sincerity Ace is reportedly still on fire and listing to starboard. the search for the one remaining unaccounted for crew member has been called off.

USCG Photo from Dec 31

Fires on Car carriers are not a new Issue. Last year the Honor caught fire after a recalled part in a car aboard the ship triggered the blaze. Another Ship, Courage had a similar fire in 2015.

in May 2018, the Auto Banner Caught fire in port in Korea, leading to the dramatic video above.

747 Crashes at End of Runway 14 YHZ


Wednesday Morning a Sky Lease Cargo plane, operating as flight KKE 4854 arrived from Chicago and slid off the end of runway 14 while landing at YHZ. the crew of 4 suffered minor injuries. the The plane took out the localizer antenna at the end of the runway, had the landing gear collapse, and lost both inboard engines. A large crease (below) suggests this is a Hull loss incident.

the 747-400 was arriving empty to load seafood for china. Im told the Chinese characters on the other side read “Have fish every year”

 

A TSB conference yesterday suggested weather may have been a factor, with strong Tail and cross winds, and Rain at the time, the Incident occurred at the end of the shorter of the 2 runways – with strong winds and rains the pilots decision to use that runway will also be a source of inquiry. the TSB reports the winds were 250degress magnetic, which is almost a perfect cross wind fro landing on runway 14.

in 2004, another cargo plane, also a 747 crashed on takeoff. MK airlines flight 1602 was not configured properly for flight, and crashed at the end of runway 23.  AC 624 landed short of runway 05 in March 2015. Improvements made after the crash of MK1602 likely significantly reduced the severity of that crash.

 

Operations were more or less normal, with the main 05/23 runway in operation, while the investigation continues.

 

UPDATE 11/14:

ATC Audio is available. the video also lists some limits for landing.

Norweigan frigate KNM Helge Ingstad Struck by Tanker, In danger of sinking

KNM Helge is a Nansen Class Frigate. Pictured is KNM Thor Heyerdahl on a2012 port visit to Halifax

The Norwegian frigate KNM Helge Ingstad was stuck early this morning by the tanker SOLA TS while anchored west of Bergen. The tanker had just loaded North Sea Crude oil, and was departing the fjord when the incident happened.

the frigate appears to have been stuck in the stern area, and flooding continues, with the latest images showing the frigate nearly on its side, a significantly worse state then shortly after the collision, when the frigate was simply low in the stern. the ship also appears to have deliberately run aground at the bow, in an attempt to keep the ship from sinking,

the Frigate was participating in the Nato Exercise Trident Juncture, which also featured Canadian frigates HMCS Halifax and HMCS Toronto. the 137 crew members were able to evacuate the ship, with 7 minor injuries reported. Marine traffic reports the frigate was not broadcasting AIS at the time.

 

UPDATE 11/09:

New imagery from the Norwegians this morning. looks like the ship has settled on her side. She was not broadcasting AIS at the time of the collision, and appears to have been holed by the tankers protruding anchor hawsepipe, which looks to have left a large gash from the hanger aft.

Still taken from this video

 

from yesterday:

Update 11/10:

she looks to be down more on her side.

Update 11/13:
Shes Sunk. Overnight the 7 lines holding the ship to shore broke, and she slipped beneath the waves. The Norwegian government announced on the 12th that the ship was secure.

Word is she was actually sailing when the incident occured, and not anchored, and was aware of the presence of the outgoing tanker. An audio log obtained by Norwegian media has revealed that the frigate failed to change course despite repeated warnings that she was on collision course with the tanker. Significant questions about Seamanship and damage control need to be asked after this incident.

 

Update 11/14

TSB Report into Arca1 Grounding

The Transportation Safety Board released its report into the Grounding of the Arca 1 Off Sydney NS.  The investigation found that

the main propulsion clutch was not checked and adjusted before or during the voyage as per the manufacturer’s recommendation. As a result, the clutch failed due to slippage, causing the loss of port propulsion and a reduction of vessel speed. The loss of speed increased the time required to reach Sydney, preventing the vessel’s arrival before weather deteriorated. The vessel gradually could not continue moving forward in the severe weather, causing it to drift to the west. The anchor was deployed to attempt to secure the vessel, but it could not hold and the vessel continued to drift further west towards the shore until it ran aground.

as well, the report notes

the master was not qualified to act as master of the vessel and the motorman was not qualified to act as chief engineer. Voyage planning was carried out in a manner that was not consistent with best practices, as contingencies and limitations were not taken into account.

You can read the Report Here (PDF).

Breaking:Nordika Desgagnés Loses Steering Off Cape Breton

The Nordika Desgagnés has lost steering off cape breton. She Sailed from Montreal bound for Sydney Austrailia. CCGS Sir Wilfred Grenfell is on scene and A tug has been dispatched by the vessel owner to tow the Nordika Desgagnes to Port.

(Above)  current location via Marine Traffic. (Below) CCGS On Scene Photo.

This Story will be continually be updated at http://blog.halifaxshippingnews.ca/2018/03/breakingnordika-desgagnes-looses-steering-off-cape-breton.html

UPDATE 03/16 12:00:
the ship is apparently facing some weather, and is still in roughly the same area of the Ocean.

The M/V Nordika Desgagnés, a multi-purpose cargo ship built in 2010. With a length of143meters, she has a dead weight of17,000tons and a carrying capacity of nearly 20,000cubic meters excluding the main deck, at a draft of 9.70meters. She is equipped with two cranes of 250tons capacity each which can be combined to lift a total of 500tons,has an additional80-ton crane, holds an ice class equivalent to Lloyd’s 1A and can reach a speed of 15knots. a full spec sheet is available (PDF)

UPDATE 13:14:
Reports are that she is now bound for Port Hawksbury under tow by supply vessel Atlantic Tern

UPDATE 16:00:

CCGS Sir Wilfred Grenfell was relieved by CCGS Louis S. St-Laurent. apparently Atlantic Larch attempted the tow first last night, but the tow line failed.

Final Update: the Nordika Desgagnés has been towed to Port Hawksbury, reportedly with Hull damage after one of her cranes came loose. the Tug, Atlantic Tern tied up in Halifax over the weekend.

Derailment in Rockingham Yard

Looks like a couple of empty cars were pushed beyond the end of track, causing a derailment. This occurred on the yard tracks, so it was likely a low speed affair. CN has recently made a number of changes to the tracks here.

TSB Report Into Near Collision of the Summer Bay and Grandeur of the Seas.

On June 29, 2016 the Tour boat Summer Bay had a very near miss with the Grandeur of the Seas. From the TSB Report

the master of the Summer Bay altered course to 071° and crossed the bulbous bow of the Grandeur of the Seas at a distance of about 25 m. The fog signal from the Grandeur of the Seas was heard on the Summer Bay about 10 seconds prior to the course alteration. The Grandeur of the Seas bridge team was unaware that the Summer Bay was crossing their bow until the pilot saw the Summer Bay‘s mast as it appeared from underneath the bow on the starboard side, after it had already crossed.

the weather at the time was foggy, and the Summer Bay altered course, from the pre-arranged passing plan while in the Grandeur of the Seas radar blind spot.

the report indicates that the master of the Summer bay was new to Murphys, and had limited experience operating vessels in Halifax Harbour and in low visibility. Murphy’s also lacked procedures for operations in low visibility.

Murphy’s the Cable Wharf has made the following changes to its tour vessels:

  • It has added automatic identification system units to all vessels except those that are amphibious.
  • It has developed standard operating procedures for its vessel masters in reduced‑visibility conditions.
  • It has commissioned an external audit of its safety management system.

Given the recent issue with the Harbour Queen, one should question if these changes were enough.

The full report can be read at http://www.bst-tsb.gc.ca/eng/rapports-reports/marine/2016/m16a0141/m16a0141.asp



Related Posts Plugin for WordPress, Blogger...