Excerpt from U.S. Coast Guard “Proceedings of the Marine Safety & Security Council” magazine. Click on Part I or Part II for previous entries.
Aboard the Seafarer
After the collision with the outbound freighter, the captain was unable to disconnect the Seafarer from the flaming tank barge.
As heavy, black smoke surrounded the pilothouse, he placed the throttles ahead slow, rudder position hard left, to ground the tow near Mullet Key. He then left the pilothouse to muster personnel.
As noted in the Marine Board of Investigation report:
“[As] captain … and mate … reached the last flight of stairs leading to the wheelhouse, captain … could hear windows exploding and glass hitting the deck. The two men abandoned their attempt to enter the pilothouse.
By now, the smoke had increased to the point that personnel at deck level were having difficulty seeing and breathing. The life raft was inaccessible because of its location on the upper deck. Captain … ordered the crew to abandon ship.
When the crew entered the water … they could see smoke and flames above them. Captain … heard … two or three explosions.
The crew was later rescued by the pilot boat Manatee. The fire burned throughout the day ... The Seafarer suffered extensive fire damage, and the Ocean 255 was a constructive total loss.”
On the Bridge of the Balsa 37
This vessel was involved in both collisions and suffered much damage. The main concern was that the vessel would capsize or sink and block the channel. As stated in the USCG report:
“Captain … arrived on the bridge and ordered all hands to muster for the emergency and had pilot … take the ship to anchorage near Egmont Key.
As the Balsa 37 proceeded toward anchorage, the chief mate opened the cargo hatches and observed sea water in both cargo holds ... Concerned for the vessel’s stability, captain … grounded the [vessel] near Egmont Key.
The ship remained aground for several days until lightering and salvage operations could be completed.”
On the Capt. Fred Bouchard
The USCG report set the scene:
“Pilot … immediately made a distress call on Channel 16. Pilot … advised captain … to make a course correction to keep the tow in the channel. He then called the pilot boat Manatee and directed [it] toward the scene to pick up any survivors [from the Seafarer].
Following the two collisions, the [assist tug] initially let out 60 meters of line to move away from possible hazards. After determining it was safe, the master had his crew again make the tug fast alongside the B. No. 155.
The Bouchard tow later anchored approximately one and one-half miles west of the Sunshine Skyway Bridge. The B. No. 155 was later offloaded and taken to dry dock … for damage survey and repairs.”
In part IV we will explore the aftermath, the conclusions from the Marine Board of Investigation, and lessons learned from this calamity.
For more information:
Full article is available at www.uscg.mil/proceedings. Click on “archives” and then “2007-08 Vol. 64, Number 4” (Winter 2007-08).
Subscribe online at http://www.uscg.mil/proceedings/subscribe.asp.
Direct requests for print copies of this edition to: HQS-DG-NMCProceedings@uscg.mil.
A discussion forum on Marine Safety, Recreational Boating Safety, and waterways managment as we work together to protect maritime commerce and mobility, the marine environment, and safety of life at sea.
Thursday, May 13, 2010
Lessons Learned—Collision, Fire in Tampa Bay—Part III
Posted by
Editor Sarah Webster, at USCG Proceedings of the MSSC (DCO-84)
Subscribe to:
Post Comments (Atom)
Topics
- acrylonitrile
- Aids to Navigation
- AMSEA
- Anhydrous Ammonia
- Automatic Identification System
- Auxiliary
- Benkert
- Boat Accidents
- Boat U.S.
- Boating Improvements
- Boating Safety
- Boating Safety Enhancement
- Boy Scouts of America
- BUI
- Calicchio
- campaign
- Champion's Point of View
- Champion’s Point of View
- chemical
- Chemical of the Quarter
- Citizen's Action Network
- Coast Guard
- Coast Guard Authorization Act
- Coast Guard Auxiliary
- COLREGS
- Combating Piracy
- commercial fishing
- commercial fishing safety
- deck
- derelict vessels
- digital edition
- Director’s Perspective
- e-Navigation
- education
- engineering
- Environmental Protection
- fatalities
- fishing safety training
- Fishing Vessel Safety
- fishing vessels
- fleet
- Flotation
- Global Supply Chain
- HIstory
- Icebreaking
- information managers
- Information Technology
- International Maritime Organization
- Investigations and Analysis
- Leadership
- legislation
- Lessons Learned
- life jackets
- lifesaving equipment
- Marine Inspectors
- Marine Safety
- Marine Safety Enhancement
- Marine Safety Performance Plan
- Marine Transportation System
- Merchant Mariners and Credentials
- National Recreational Boating
- navigation
- navigational safety
- New Orleans
- non-profit
- Paddle Sports
- Partnerships
- Partnerships and Outreach
- Pilotage
- Pollution Prevention
- Ports
- Prevention Professionals
- Proceedings
- queries
- Recreational Boating Safety
- Recreational Boating.
- Recruitment Efforts
- Regulations
- risk
- risk assessment
- safety
- Safety Afloat
- search and rescue
- Security
- swim
- Technology
- Tiger Team
- training
- training contract
- training programs
- trends
- tug
- United Safe Boasting Institute
- Updates and New
- Vessels
- virtual learning
- Water Safety
- Waterways
- Waterways Management
Blog Archive
-
▼
2010
(124)
-
▼
May
(10)
- The Office of Global Maritime Situational Awarenes...
- The North Pacific Coast Guard Forum
- Interagency Success Stories
- Lessons Learned—Collision, Fire in Tampa Bay—Part IV
- An Advance Look at the 2010 Update to the Marine S...
- Lessons Learned—Collision, Fire in Tampa Bay—Part III
- Lessons Learned—Collision, Fire in Tampa Bay—Part II
- Lessons Learned—Collision, Fire in Tampa Bay—Part I
- The Successful Use of the Auxiliary in the Sector
- Upcoming in Proceedings
-
▼
May
(10)
USCG Sites and Blogs
- Homeport
- National Maritime Center
- National Vessel Documentation Center
- Coast Guard Auxiliary
- Boating Safety Division
- National Maritime Security Advisory Council
- Coast Guard Marine Information Exchange
- AMVER
- AMVER Blog
- Marine Safety Center
- Proceedings of the Marine Safety and Security Council
- Coast Guard
- iCommandant – Web Journal of Adm. Thad Allen
- CGLANT Director of Operations
- Coast Guard All Hands – MCPO-CG and MCPO-CGRF
- More blogs via USCG Compass Blogroll
Other CG Preventtion Relevant Sites and Blogs
- DHS Leadership Journal
- House CG&MT Subcommittee
- Senate Oceans, Atmosphere, Fisheries & CG Subcommittee
- Sec DOT's Blog
- Sec State Blog
- Committee for the Marine Transportation System
- Bryant's Maritime Blog
- CGBlog
- Int'l Chamber of Shipping
- gCaptain Blog
- Int'l Maritime Organization
- Journal of Commerce
- KennebecCaptain
- Lloyds List Blog
- Marine Log
- Marine Safety by 'Safety Doc'
- MarineLink - Coast Guard stories
- Maritime Executive
- Maritime Journal News
- Monitor by Dieselduck
- Off Soundings
- Professional Mariner
- Scuttlebutt (Fred's Place) - CG News
- Sea Fever
- Towmasters
Comment Policy
We welcome your comments on postings at all Coast Guard sites/journals. These are sponsored by the U.S. Coast Guard to provide a forum to talk about our work providing maritime safety, security and stewardship for the American people to secure the homeland, save lives and property, protect the environment, and promote economic prosperity.
Please note: Anonymous comments have been disabled for this journal. It is preferred that you use your real name when posting a comment. WE WILL POST THE NAME YOU ENTER WHEN YOU SUBMIT YOUR COMMENT. Also, you are welcome to use Open ID or other user technologies that may be available.
All comments submitted are moderated and will be reviewed before posting. The Coast Guard retains the discretion to determine which comments it will post and which it will not. We expect all contributors to be respectful. We will not post comments that contain personal attacks of any kind; refer to Coast Guard or other employees by name; contain offensive terms that target specific ethnic or racial groups, or contain vulgar language. We will also not post comments that are spam, are clearly off topic or that promote services or products. Posted comments will be in English. We are not able to post comments in other languages.
We will make our best effort to promptly post those comments that are consistent with the Comment Policy, but given the need to manage federal resources, moderating and posting of comments will usually occur only during regular business hours, Monday through Friday. Comments submitted outside of business hours will be read and posted as quickly as possible.
Please note: Anonymous comments have been disabled for this journal. It is preferred that you use your real name when posting a comment. WE WILL POST THE NAME YOU ENTER WHEN YOU SUBMIT YOUR COMMENT. Also, you are welcome to use Open ID or other user technologies that may be available.
All comments submitted are moderated and will be reviewed before posting. The Coast Guard retains the discretion to determine which comments it will post and which it will not. We expect all contributors to be respectful. We will not post comments that contain personal attacks of any kind; refer to Coast Guard or other employees by name; contain offensive terms that target specific ethnic or racial groups, or contain vulgar language. We will also not post comments that are spam, are clearly off topic or that promote services or products. Posted comments will be in English. We are not able to post comments in other languages.
We will make our best effort to promptly post those comments that are consistent with the Comment Policy, but given the need to manage federal resources, moderating and posting of comments will usually occur only during regular business hours, Monday through Friday. Comments submitted outside of business hours will be read and posted as quickly as possible.
This is an official United States Coast Guard posting for the Public's information.
Our posting does not endorse this site or anything on it, including links to other sites,
and we disclaim responsibility and liability for the site and its content.
0 comments:
Post a Comment