Join our crew and become one of the 104,013 members that receive our newsletter.

NTSB Determines Probable Cause of EL FARO Sinking

NTSB Determines Probable Cause of EL FARO Sinking

GCaptain
Total Views: 1773
December 12, 2017

The El Faro is shown in this undated handout photo provided by Tote Maritime in Jacksonville, Florida, October 2, 2015. Photo: Tote Maritime

Captain’s Decisions, Shipping Company’s Poor Safety Oversight Led to Sinking, the NTSB Says

The deadliest shipping disaster involving a U.S.-flagged vessel in more than 30 years was caused by a captain’s failure to avoid sailing into a hurricane despite numerous opportunities to route a course away from the hazardous weather, the National Transportation Safety Board announced during a public meeting Tuesday.

The 790-foot, cargo vessel, S.S. El Faro, en route from Jacksonville, Florida, to San Juan, Puerto Rico, sank October 1, 2015, in the Atlantic Ocean during Hurricane Joaquin, taking the lives of all 33 aboard.

During Tuesday’s meeting, the board voted to adopt the probable cause, which cited the captain’s decisions and the shipping company’s inadequate oversight among numerous contributing factors, and concluded the NTSB’s 26-month investigation into the accident.  The board also voted to adopt 81 findings, 53 recommendations, along with the NTSB’s entire report. 

Read the Executive summary, including 81 findings, 53 recommendation and the probable cause of the Oct. 2015 sinking of the cargo ship El Faro.

“We may never understand why the captain failed to heed his crew’s concerns about sailing into the path of a hurricane, or why he refused to chart a safer course away from such dangerous weather,” said NTSB Chairman Robert L. Sumwalt. “But we know all too well the devastating consequences of those decisions.”

SS El Faro. Photo: MarineTraffic.com/

NTSB investigators worked closely with the U.S. military and federal- and private-sector partners to locate the wreckage, photo- and video-document the ship and related debris field, and recover the El Faro’s voyage data recorder from more than 15,000 feet under the surface of the sea – which proved critical to the investigation. 

See Also: NTSB Chairman’s Opening Statement

The ship departed Florida Sept. 29, 2015, and had a range of navigation options that would have allowed it to steer clear of the storm that later became a Category 4 hurricane. The captain, consulting outdated weather forecasts and ignoring the suggestions of his bridge officers to take the ship farther south and away from the storm, ordered a course that intersected with the path of a hurricane that pounded the ship with 35-foot seas and 100 mph winds.

As the ship sailed into the outer bands of the storm, about five hours prior to the sinking, its speed decreased and it began to list to starboard due to severe wind and seas. In the last few hours of the voyage, the crew struggled to deal with a cascading series of events, any one of which could have endangered the ship on its own.

Seawater entered the ship through cargo loading and other openings on a partially enclosed deck in the ship’s hull, pooled on the starboard side and poured through an open hatch into a cargo hold. The hold began to fill with seawater, and automobiles in the hold broke free of lashings and likely ruptured a fire main pipe that could have allowed thousands of gallons of seawater per minute into the ship – faster than could be removed by bilge pumps.

el faro track
Color-enhanced satellite imagery of Hurricane Joaquin taken close to the accident time. El Faro’s track is identified by the green line.

About 90 minutes before the sinking the listing ship lost its propulsion and was unable to maneuver, leaving it at the mercy of the sea. Although the captain ordered the crew to abandon ship when the sinking was imminent, the crew’s chances of survival were significantly reduced because El Faro was equipped with life rafts and open uncovered lifeboats, which met requirements but were ineffective in hurricane conditions.

The NTSB also said that the poor oversight and inadequate safety management system of the ship’s operator, TOTE, contributed to the sinking.

“Although El Faro and its crew should never have found themselves in such treacherous weather, that ship was not destined to sink,” said Sumwalt. “If the crew had more information about the status of the hatches, how to best manage the flooding situation, and the ship’s vulnerabilities when in a sustained list, the accident might have been prevented.”

WATCH: NTSB Video Details El Faro Sinking

As a result of the 26-month long investigation, the NTSB made 29 recommendations to the U.S. Coast Guard, two to the Federal Communications Commission, one to the National Ocean and Atmospheric Administration, nine to the International Association of Classification Societies, one to the American Bureau of Shipping, one to Furuno Electric Company and 10 to TOTE Services.

The executive summary, including the findings, probable cause and safety recommendations is available can be found at https://go.usa.gov/xnRAn.

The complete accident report will be available in several weeks.

Additional information related to this investigation, including news releases, photographs, videos, and a link to the accident docket containing more than 30,000 pages of factual material, is available on the El Faro accident investigation page at http://go.usa.gov/xnRTW.

 
 
 

Weekly Insights from the Helm

Dive into a sea of information with our meticulously curated weekly “Dispatch” email. It’s more than just a newsletter; it’s your personal maritime briefing.

Sign Up
Back to Main
polygon icon polygon icon

Why Join gCaptain Club?

Be Informed: Stay updated with the latest maritime news and trends.

Connect: Network with a community of maritime professionals and enthusiasts.

Gain Insights: Receive exclusive content and personal perspectives from our CEO.

Sign Up
close

JOIN OUR CREW

Maritime and offshore news trusted by our 104,013 members delivered daily straight to your inbox.

Join Our Crew

Join the 104,013 members that receive our newsletter.