|
Contract Number:
|
Design Number:
|
| Library File Number: | Submitted Date: 11/20/2012 |
|
SR/Terminal/Vessel: M/V Wenatchee |
Region: WSF |
| Contract Title: M/V Wenatchee, Hard Landing at Pier 52, Seattle August 30, 2009 | |
|
EXPERIENCE: Describe the particular situation or event. At approximately 11:00 AM on Sunday, August 30, 2009, the MV Wenatchee (ON 10613 09), carrying out her normal operating schedule on the Seattle - Bainbridge Island route, was making an approach to Colman Terminal (Pier 52) in heavy fog when the vessel did not stop and impacted the left wingwall of Slip #3 (viewed from land) with the bow of the ship with sufficient force to cause moderate damage to the vessel and wingwall structure. No crew injuries were experienced. One passenger fell to the deck as a result of the lurching motion and sustained a facial injury. Damage to the ship was contained to the foremost portion of the main car deck and supporting structure completely above the waterline. No environmental impact was experienced. Immediately after the incident, the ferry was successfully moved to slip #2 and traffic was discharged uneventfully. Following inspection of the ship and terminal by WSF and US Coast Guard representatives, slip #3 was deemed out-of-service. The vessel was permitted to proceed directly to Todd's Shipyard for emergency dockside repairs. Vessel repairs were completed by Friday, September 4, 2009 and, following sea trials, the vessel resumed service that day. Total cost of vessel repairs was approximately $86,000. Repairs to slip #3 were completed on Thursday, September 3, 2009 at a cost of approximately $140,000. |
|
|
LESSON: Describe what knowledge was gained from the experience. The proximate cause of the accident was a ship handling misjudgment complicated by restricted visibility and a delay in requesting the on-line placement of the third alternator . Contributing to the incident was a loss of situational awareness through distracted focus on small boat traffic and a breakdown communicating distances and speeds to the conning officer (Bridge Resource Management). No deficiencies or mechanical problems were discovered in the propulsion system of the vessel. All navigational and electronic equipment was functioning properly. |
|
|
RECOMMENDATION: Describe how the knowledge gained can be used. 1. Whenever possible in a hard landing situation, announcements should be made over the public address system to all passengers and crew to "brace for possible impact" to hopefully minimize any injuries caused by unfamiliar ship motions. Safety Management System procedures should be reviewed for modification as necessary with any appropriate additions. 2. That the principles of sound Bridge Resource Management (BRM) should be reinforced and discussed in WSF training sessions involving Staff Masters, Licensed Deck Officers and bridge team members. Appropriate communication standards for all watch standers should be developed. 3. That Jumbo Mark II vessels traveling in restricted visibility should have three alternators available for immediate maneuvering as necessary. 4. That a standard policy be developed to guide Masters in their actions introducing the third alternator into the propulsion loop aboard Jumbo Mark II vessels. The previous Fleet Advisory (Attachment 30) and recent Quick Notice should be codified in the Safety Management System (SMS) manuals and all the Jumbo Mark II Vessel specific manuals. 5. That SMS training plans to all levels of the organization incorporate the ISM Code philosophy of continuous review and improvement of WSF SMS manuals. The Safety Management System should not only reflect how operations are carried out, but also adapt to reflect changing procedures. SMS communications to all levels of the organization should stress that input is needed by all concerned to update the SMS manuals to make it a living document. 6. That Washington State Ferries develop and promulgate a system by which "Lessons Learned" from marine incidents such as this can be shared with operational crews. |
|
|
Project Delivery Method: Design-Build Design-Build Phase: Operations |
Categories: Allision |
|
Share this Lesson |
|
|
For assistance with Lessons Learned, or if you have questions or comments, |
