Skip to main content

SS EL FARO VDR TRANSCRIPT

NAUTICAL LOG has published Posts about this tragic ship sinking since the very first report of her loss.  Today the NTSB has released her VDR data in particular the Navigation Bridge voice recorder - it is not good.  This Post is compiled from multiple Media sources.

On October 01, 2015 the SS El Faro a freighter sank with all hands, 33 crewmembers lost their lives and no bodies were ever recovered though one was sighted by the USCG in a survival suit but not picked-up.  By an extraordinary search, resumed at the insistence of a U.S. Senator from the State of Florida, the VDR was found  and now after months of investigation some results have been released. 

The ship left Jacksonville, Fl. bound for San Juan, PR and sailed directly into the eye of a Category 4 hurricane named Joaquin.  Why the ship was where it was in the first place is a question yet to be fully answered but it seems that the Master was more focused on fuel consumption than plotting the path of the hurricane Joaquin and changing course to avoid the worst affect.  This in spite of the Officers pointing out that the ship had closed to just 22 nautical miles from the hurricane's centre.  Then at 0615 the vessel lost power, listed severely and at around 0730 sank with the loss of all hands.  It seems extraordinary that apparently twice before her sinking while he still had power to do so the Master had declined to alter course based it appears on his consideration of an extra 160 nautical miles the additional fuel it would consume and getting permission from the Company to alter course.  This is not good vessel management it is not even good sense.  Since the transcript is 510 pages long one would have to read it in its entirety to learn all that happened however several points have been extracted by the Media.  From these it is evident that navigation was done with an over-dependency on electronics using a system called BVS, which NAUTICAL LOG is not familiar with, and that this system seemed to fail or be inaccurate as were the reports from the National Hurricane Center in Miami, Fl.  All one can say as to that latter statement is that having lived in South Florida for 40 years one has considerable faith in the NHC professional work.  From their own recorded words in the transcript the Master and Officers did not appear to have the professional knowledge to make their own assessment of the situation as a whole or if they did have it the ability to apply that professional knowledge.  By and large reading the transcript extracts quoting the Navigation Bridge staff conversations gives an impression of persons who have no experience of being in Command or standing Watch in a ship whatsoever.

The U.S. Merchant Marine is completely bound by Unions, the Officers have one and the Seamen a separate one.  This seems to restrict the actions the Master and Officers can or are willing to take and adding this to a Company's policies removes the actual decision-making from the Master limiting the range and ability to make decisions.  Reading the transcript is a very sobering affair considering the actual results of this Master's actions or lack thereof and the somewhat flippant remarks made by him in the hearing of the Officers and crew on the Bridge.   This is never a good or wise thing to do in front of one's crew and clearly, again from the conversations recorded, caused considerable distress to several of those crewmembers.

Good Watch.

Comments

Popular posts from this blog

PAINT LOCKER FIRES

The photographs above are revealing in several ways, lets have a look. Clearly the Japanese Maritime Self Defence Force (JMSDF) vessel JS "Kurama" impacted the Korean container ship MS "Carina Star" just aft of the turn of the fo'cs'le on the Starboard side. Please note that's the Starboard side, thus it appears JS "Kurama" would have shown "Carina Star" the red port sidelight and "Carina Star" would have shown JS "Kurama" the green starboard sidelight. This impact point would tend to suggest that JS "Kurama" was the 'stand-on' vessel and the MS "Carina Star" is the 'giving-way' vessel. Until there is a complete plot of the tracks made good of both these vessels and the position in the Kanmon Strait of the point of collision no determination can actually be made. As a result of this impact there was severe bow damage to JS "Kurama" and in addition a massive f...

HOW TO WEAR A LIFEJACKET

A popular U.S.-based cruise ship style A popular European ferry style Several times during the year NAUTICAL LOG has had visitors searching for lifejacket instructions. With two just over Christmas we decided to publish something for everybody to see and read. Choose a Coast Guard approved life-jacket and make sure it is undamaged. Make sure life-jackets are readily accessible, never locked away. Check the fit, there are adult, child and infant sizes, the correct one MUST be used. Choose bright colour life-jackets so as to be seen easily by Search and Rescue (SAR). Put your life-jacket ON BEFORE you leave the berth. Make sure you have a light and whistle attached AND they BOTH WORK. Good Watch

CYCLONES AND SENTINELS

USCG Sentinel-class which are based on the Netherlands Damen Stan-class USCGC opened hull view USCG Sentinel-class interior layout USN Cyclone-class In the NAUTICAL LOG Press Release folder comes news of Bollinger Shipyards in Lockport, LA. The United States Coast Guard has awarded a $166.1 million option to start production of four ' Sentinel-class' Fast Response Cutters (FRCs). This latest award brings a total of eight FRCs under production at Bollinger with a value of $410.7 million. The current FRC contract contains options for up to 34 cutters and is worth $1.5 billion if they are all exercised. Recently the United States Navy limited operation of its 'Cyclone-class' coastal patrol boats stationed in Bahrain and Norfolk, VA. Any vessel operation would depend on sea state and speed restrictions. This was due to structural damage as the vessels reach the 15 year mark which is considered close to the operational limit. This is apparently not a design fault but ...