 |
2nd Light Forums |
 |
 |  |
|
Topic Title: Bermuda Triangle Topic Summary: El Faro disappears Created On: 10/07/2015 09:17 AM |
Linear : Threading : Single : Branch |
 Topic Tools
|
 10/07/2015 09:17 AM
|
|
|
The captain of the 790-foot El Faro planned to bypass Hurricane Joaquin, but some kind of mechanical failure left the U.S. container ship with 33 people aboard helplessly - and tragically - adrift in the path of the powerful storm, the vessel's owners say.
------------------------- Water dissolving...and water removing There is water at the bottom of the ocean |
|
|
|
|
|
10/07/2015 10:05 AM
|
|
|
sad, avoidable tragedy... guessing she got broadside to the swell, rolled too far, and capsized that way, with nobody having a chance to safely abandon ship
|
|
|
|
|
|
10/08/2015 09:56 AM
|
|
|
Terrible journalism, but some insightful reader commentary here
Get your facts straight. The ship sinking due the loss of propulsion is the propaganda from Tote Marine. The AIS track data found on marinetraffic.com clearly indicates the ship was traveling at about 19 knots when it was well into the sphere of the cyclone. Furthermore, the captain on a course heading of 130 degrees never changed his heading more than 10 degrees from when El Faro left Jacksonville on Tuesday night. The captain knowingly took this 40 year old container ship directly into the eye of a category 4 hurricane. At 8:00 AM EDT on Wednesday, El Faro was approximately 85 miles off the coast of Florida when NOAA first forecast that Joaquin was now officially a hurricane, intensifying, and on a course of 235 degrees. During the entire day on Wednesday NOAA issued forecasts on Joaquin indicating a significant drop in barometric pressure while the storm heading remained constant. Progression of the track of Joaquin and the track of El Faro were on a direct collision course. Another fact of concern was once El Faro was north of the island chain it was impossible to head south. Only a fool or someone being pressured by superiors would have attempted this passage on a 40 year old ro ro container ship with no possible escape plan. The potential of leaking hatches and ultimately mechanical failure should have been factored into any decision made to continue this passage. This was manslaughter not a series of unfortunate events. last email from ship (from second mate to her mom) - "We are heading straight into it, Category 3, last we checked. Winds are super bad. Love to everyone." Seems that they had a plan . " indicates the ship was traveling at about 19 knots when it was well into the sphere of the cyclone." ... Really? Not that CURRENTS or wind had anything to do with that. nobrainge OCTOBER 08, 2015 - 12:37 PM Mr. Head, had the vessel been adrift the course heading would have changed. Also, the El Faro maintained an almost constant 18.5-19.2 knot speed on the entire leg. This ship went almost top speed in the jaws of that hurricane. Yes, but my point is that a 40 year old single source propulsion vessel should never have been deliberately put into a category 4 storm given all of the advanced warning. Also, once it got too far into the passage the southern exit was blocked by the barrier reefs. Lots of bad decisions made with good data. This should never have happened. There has to be a reason and I challenge it was just bad luck. REALmaven OCTOBER 08, 2015 - 10:20 AM Mariners Rule 1 - "Never cross the T" - translation ,never cross the track or predicted track of a tropical storm. Maximum safe operating windspeed for Container ship of this size and age = 34 mph. Chance of 790' container ship safely transiting a Cat 3 or 4 storm = 0. The Captain did not sail into the hurricane as much as it exploded all around him. A ship's observation, presumably the last El Faro contact, transmitted a weather observation of 52 foot seas, 50 Kt winds, 149 nautical miles from the storm. Phil Klotzbach, a renowned tropical meteorologist noted around midnight Oct. 1, that the storm had intensified 40kts in 24hrs, the fastest intensification of the Atlantic season. I personally noted an ongoing 45 mb atmospheric drop in 24 hours around the same timeframe, which approaches the physical limits for evacuating air from a cyclone (barometer from 29.26 inches to 27.88 inches in 24 hrs.) The Hurricane Hunters, at great risk, transitioned to "search mode" in the eye of the hurricane, reducing flight level to 300 FEET!!! in an effort to spot the El Faro which had reported losing power. The Coast Guard search commenced into still-dangerous conditions at the earliest possible moment, could attest. The El Faro encountered under-predicted intensification, unprecedented wave heights and the loss of headway in a very short period of time. Simply put, they sailed into a trap. REALmaven OCTOBER 08, 2015 - 12:24 PM Nonsense. Look at NHC predictions and track info . It is spot on. The only trap was leaving port. |
|
|
|
|
|
10/09/2015 01:00 PM
|
|
|
http://www.foxnews.com/us/2015...-into-track-hurricane/
According to the data, El Faro's last, best chance to avoid the storm came at 5 p.m. Sept. 30, when it sailed past the "Hole in the Wall", a gap in the Bahamas archipelago that would have taken it toward Cuba. Early on the morning of Oct. 1, Reuters reported the tracking data showed El Faro was still traveling at 17 knots, close to 20 miles per hours, despite the eye of Joaquin being only 50 miles away. The ship's last log, shortly before 4 a.m. ET Oct. 1, showed it was traveling at 10.7 knots (12.3 miles per hour). and https://gcaptain.com/we-wont-l...at-didnt/#.VhgpxN9VhHx Edited: 10/09/2015 at 01:55 PM by RegularJoe |
|
|
|
|
|
11/02/2015 03:49 PM
|
|
|
Vessel found, identity confirmed:
3 miles down |
|
|
|
|
|
09/18/2016 09:02 AM
|
|
|
Voyage Data Recorder was recovered about a month ago, contains 26 hours of data.
Not much detail released yet (from what I've found), but captain gave order to abandon ship about 10 minutes before the recordings end. http://elfaroincident.com/el-f...-news-release-8-24-16/ |
|
|
|
|
|
FORUMS
:
NPNR
:
Bermuda Triangle
|
Topic Tools |
FuseTalk Basic Edition - © 1999-2024 FuseTalk Inc. All rights reserved.