Excerpt from U.S. Coast Guard Proceedings of the Marine Safety & Security Council magazine by Ms. Krista Reddington, technical writer.
Lessons learned from USCG casualty reports are regularly featured in Proceedings of the Marine Safety & Security Council magazine. These articles explore marine incidents and the causal factors, outline the subsequent U.S. Coast Guard marine casualty investigations, and describe the lessons learned as a result.
The Voyage Begins
Early in the morning of January 18, 2006, the uninspected tug Valour sank into the chilly, wind-blown sea off the coast of Wilmington, N.C. Three crewmembers aboard the vessel lost their lives in the incident. Several factors contributed to the sinking of the tug; unfortunately, almost all can be attributed to human error.
On January 17, 2006, the chief mate noticed the vessel was listing slightly to port and ordered the assistant engineer on watch to pump 15 minutes’ worth of ballast into the #18 starboard ballast tank. Nearly five hours later, the captain took over the watch and ordered the chief engineer to pump the #18 starboard ballast tank dry. At 10:30 p.m., the chief mate entered the wheelhouse to inform the captain of the slight starboard list that was consistent with the vessel’s stability letter; the wind and waves pushing the tug and barge due north may have increased this natural list.
Between 11:00 a.m. and 11:15 p.m., the second mate and captain noticed the tug had first begun to level, then list to port, then roll to port. The captain contacted the chief engineer to determine what actions were being taken at the time and ordered him to pump out all ballast. The captain sounded the general alarm at 11:20 p.m., and crew was informed via the public announcement system that there was an emergency in the engine room and to assist the chief engineer as necessary. At this point, the vessel was listing approximately 15 degrees to port in the increasingly rough waters.
Miscommunication Leads to Mistrust
At 11:30 p.m., the captain radioed the tug Independence, which was approximately 30 miles away, to report they had taken on water but the engineer was working on it. As the captain sent a “mayday” transmission to the Coast Guard, the chief mate went below to retrieve his survival gear. On his way, he fell down the ladder from the wheel house to the stack deck passageway. The captain heard a noise and rushed from the wheel to investigate. He found the chief mate lying on the deck where he had landed.
The second mate immediately went to assist the chief mate while the captain returned to the wheelhouse. He notified the Coast Guard that the tug had an injured crewmember and may require a helicopter. The second mate found the chief mate dazed, with his legs awkwardly folded and apparently broken; he was clutching his chest and said he could not feel his legs and was having trouble breathing.
The story continues in part 2.
For more information:
Full article is available at http://www.uscg.mil/proceedings/summer2010.
Subscribe online at http://www.uscg.mil/proceedings/subscribe.asp.
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, December 1, 2011
Lessons Learned —Failed Assumptions Lead to a Fatal Sinking at Sea—Part 1
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
-
▼
2011
(126)
-
▼
December
(10)
- Better Safe Than Sunk—Part 2
- Better Safe Than Sunk—Part 1
- Lessons Learned: A Turn for the Worse-- Part 4
- Lessons Learned: A Turn for the Worse-- Part 3
- Lessons Learned: A Turn for the Worse—Part 2
- Lessons Learned: A Turn for the Worse—Part 1
- Fish Safe!
- The North Pacific Fishing Vessel Owners’ Associati...
- Lessons Learned —Failed Assumptions Lead to a Fata...
- Lessons Learned —Failed Assumptions Lead to a Fata...
-
▼
December
(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.
1 comments:
Failed assumptions can always lead to fatal results so as in this case.
Job requirements
Post a Comment