11.02.2013 Views

Commodore Clipper - Marine Accident Investigation Branch

Commodore Clipper - Marine Accident Investigation Branch

Commodore Clipper - Marine Accident Investigation Branch

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

4<br />

1.2 BACkGROUND<br />

<strong>Commodore</strong> <strong>Clipper</strong> provided a passenger and vehicle freight service linking St.<br />

Peter Port, Guernsey and St. Helier, Jersey in the Channel Islands with Portsmouth.<br />

One round trip of all three ports was completed in each 24-hour period from<br />

Monday to Saturday. At the time of the accident, <strong>Commodore</strong> <strong>Clipper</strong> was on the<br />

overnight leg, from St. Helier to Portsmouth. The vessel was certified to carry 500<br />

passengers, but 62 were on board at the time. The vehicle decks were almost full to<br />

capacity, mainly with unaccompanied road freight trailers.<br />

1.3 EVENTS LEADING UP TO THE FIRE<br />

1.3.1 Cargo operations in Jersey<br />

On 15 June 2010, <strong>Commodore</strong> <strong>Clipper</strong> sailed from St. Peter Port at 1747 and arrived<br />

at St. Helier at 1940. The main season for exporting Jersey Royal potatoes was<br />

reaching its end; 24 of the 77 trailers that were loaded on board were refrigerated<br />

units, carrying pre-packaged potatoes for delivery straight to supermarkets. There<br />

were too many refrigerated trailers to allow them all to be loaded on the upper<br />

vehicle deck (deck 5), which was in the open air and would have allowed their<br />

diesel-powered fridge units to be run. Consequently, those refrigerated trailers<br />

that could be powered from the ship’s electrical system were loaded onto the main<br />

vehicle deck (deck 3). These trailers were connected to power sockets on deck 3 by<br />

staff working for the haulage company, using cables provided on board <strong>Commodore</strong><br />

<strong>Clipper</strong>.<br />

1.3.2 Departure from Jersey and return passage<br />

1.4 FIRE<br />

Cargo operations and ship stability calculations were completed and <strong>Commodore</strong><br />

<strong>Clipper</strong> departed from St. Helier at 2145. The weather was fair, the ship made good<br />

progress to Portsmouth and was able to reduce to a more economical speed. Crew<br />

conducted fire and security checks of the accommodation through the night hours.<br />

The Officer of the Watch (OOW) and lookout maintained a periodic check on the<br />

vehicle decks from the bridge, by monitoring the closed circuit television (CCTV) and<br />

fire detection systems.<br />

Masters, deck officers and managers had identified that the vessel’s repetitive daily<br />

schedule did not provide bridge watchkeepers with the best opportunities to rest if<br />

traditional watch handover times were kept. Accordingly, the two second officers<br />

handed over the bridge watch at 0230. Navigational traffic was light and there<br />

were no indications of any problems on board. At about 0240, the off-going second<br />

officer made his way from the bridge to the mess room. He did not notice anything<br />

untoward or smell any smoke as he passed through the accommodation.<br />

1.4.1 Early fire development<br />

At 0237, the picture recorded by CCTV camera 7 on the port side of the main<br />

vehicle deck started to get hazy (Figure 1). The vehicle deck lighting began to<br />

appear more diffused and the picture gradually faded grey. Shortly afterwards a<br />

machinery control alarm showed an earth fault at the bus-tie breaker linking the two<br />

parts of the main 400V electrical distribution system. The third engineer, on duty in<br />

the engine control room, also heard the noise of the breaker opening. Two minutes<br />

later, at 0241, the image recorded on CCTV camera 6, at the centreline of the main<br />

vehicle deck (Figure 2), began to darken.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!