Cruisers Forum
 


Join CruisersForum Today

Reply
 
Thread Tools Rate Thread Display Modes
Old 26-10-2013, 21:09   #1
Registered User

Join Date: Jun 2013
Location: Santa Cruz, CA
Posts: 114
WSF Hyak collision update.

I was aboard the Hyak last week and talked to one of the crew about the accident. I was told that the 2nd mate was on the bridge (maybe at the helm). An order was given for right rudder and the helmsman went to port and that is how the accident occurred. I could have the right/left thing backwards but that what I heard. I also beard the officers involved will lose their jobs.

Thats all I have.
__________________

__________________
Captain Bligh is offline   Reply With Quote
Old 26-10-2013, 21:21   #2
Registered User
 
Delfin's Avatar

Join Date: Aug 2010
Location: Anacortes, WA
Boat: 55' Romsdal
Posts: 1,390
Re: WSF Hyak collision update.

Quote:
Originally Posted by Captain Bligh View Post
I was aboard the Hyak last week and talked to one of the crew about the accident. I was told that the 2nd mate was on the bridge (maybe at the helm). An order was given for right rudder and the helmsman went to port and that is how the accident occurred. I could have the right/left thing backwards but that what I heard. I also beard the officers involved will lose their jobs.

Thats all I have.
Since they ran over a sailboat from the stern, it's hard to imagine another outcome.
__________________

__________________
http://delfin.talkspot.com
When stupidity is a sufficient explanation, there is no need to appeal to another cause.
- Ulmann's Razor
Delfin is offline   Reply With Quote
Old 26-10-2013, 21:32   #3
Moderator
 
Paul Elliott's Avatar

Cruisers Forum Supporter

Join Date: Sep 2006
Posts: 3,858
Images: 4
Re: WSF Hyak collision update.

I'm not trying to excuse the crew of the Hyak, but I ride on those ferries quite often and I can see myself getting confused about right/left/port/starboard. These things have no fixed bow or stern, have wheelhouses at both ends, have two sets of nav lights, etc, etc. Sometimes "End A" is the bow, and sometimes "End B" is.

Actually, I rode on the Hyak yesterday afternoon. It's probably a good thing I wasn't steering!
__________________
Paul Elliott, S/V VALIS - Pacific Seacraft 44 #16 - Friday Harbor, WA
www.sailvalis.com
Paul Elliott is offline   Reply With Quote
Old 27-10-2013, 10:58   #4
Senior Cruiser
 
senormechanico's Avatar

Cruisers Forum Supporter

Join Date: Aug 2003
Boat: Dragonfly 1000 trimaran
Posts: 5,821
Re: WSF Hyak collision update.

I was on the Mukilteo ferry the other morning.
We had left the dock in heavy fog and had been underway for about 5 minutes.
I stayed in the car (aft in the center of the boat) while my wife went topside.
All of a sudden, the boat throttles went to idle and immediately went into full reverse.
A woman's voice gave a terse announcement over the intercom saying, "BRACE FOR IMPACT !"
The throttle stayed at full reverse for about 20 seconds before going to idle.
We didn't hit, but my wife saw the boat we almost hit.
She said it was a blue work boat, about 60 feet long with an arch across the stern.
She estimated that we were about 30 feet away from a collision.
There were no horns sounded from either vessel.
Even if the other boat didn't have AIS, wouldn't you think the ferry crew would have been watching their radar???

Eventually, the same voice came on the intercom and said, "Don't worry folks, everything's OK and we'll resume our crossing in a few minutes."

(after I change my underwear??? ) my thoughts...



Here's a story about it from AP


Updated: 4:02 p.m. Thursday, Oct. 24, 2013 | Posted: 4:02 p.m. Thursday, Oct. 24, 2013

Near collision for Washington ferry in fog

  • 0 0 0 New

The Associated Press
SEATTLE
The Coast Guard says a Washington state ferry nearly collided with a fishing boat in the fog Thursday morning near Clinton.
Spokesman Jordan Akiyama in Seattle says the ferry Cathlamet had just left on its Puget Sound crossing to Mukilteo, about 10:35 a.m. when it nearly hit the 60-foot fishing boat near the Clinton terminal because of the poor visibility.
He says ferry passengers were told to brace for impact. The 328-foot ferry made a hard turn to avoid a collision then continued on its way.
Akiyama says the fishing boat was in the wrong and did not have the automated identification system the Coast Guard uses to monitor vessel traffic.

Copyright The Associated Press
__________________
Memento,homo, quia pulvis es, et in pulverem reverteris.
senormechanico is offline   Reply With Quote
Old 27-10-2013, 16:39   #5
Registered User
 
Delfin's Avatar

Join Date: Aug 2010
Location: Anacortes, WA
Boat: 55' Romsdal
Posts: 1,390
Re: WSF Hyak collision update.

Quote:
Originally Posted by senormechanico View Post
I was on the Mukilteo ferry the other morning.
We had left the dock in heavy fog and had been underway for about 5 minutes.
I stayed in the car (aft in the center of the boat) while my wife went topside.
All of a sudden, the boat throttles went to idle and immediately went into full reverse.
A woman's voice gave a terse announcement over the intercom saying, "BRACE FOR IMPACT !"
The throttle stayed at full reverse for about 20 seconds before going to idle.
We didn't hit, but my wife saw the boat we almost hit.
She said it was a blue work boat, about 60 feet long with an arch across the stern.
She estimated that we were about 30 feet away from a collision.
There were no horns sounded from either vessel.
Even if the other boat didn't have AIS, wouldn't you think the ferry crew would have been watching their radar???

Eventually, the same voice came on the intercom and said, "Don't worry folks, everything's OK and we'll resume our crossing in a few minutes."

(after I change my underwear??? ) my thoughts...



Here's a story about it from AP


Updated: 4:02 p.m. Thursday, Oct. 24, 2013 | Posted: 4:02 p.m. Thursday, Oct. 24, 2013

Near collision for Washington ferry in fog

  • 0 0 0 New

The Associated Press
SEATTLE
The Coast Guard says a Washington state ferry nearly collided with a fishing boat in the fog Thursday morning near Clinton.
Spokesman Jordan Akiyama in Seattle says the ferry Cathlamet had just left on its Puget Sound crossing to Mukilteo, about 10:35 a.m. when it nearly hit the 60-foot fishing boat near the Clinton terminal because of the poor visibility.
He says ferry passengers were told to brace for impact. The 328-foot ferry made a hard turn to avoid a collision then continued on its way.
Akiyama says the fishing boat was in the wrong and did not have the automated identification system the Coast Guard uses to monitor vessel traffic.

Copyright The Associated Press
One would hope they were watching the radar, but if they came within 30 feet, clearly not. Not encouraging.
__________________
http://delfin.talkspot.com
When stupidity is a sufficient explanation, there is no need to appeal to another cause.
- Ulmann's Razor
Delfin is offline   Reply With Quote
Old 27-10-2013, 17:19   #6
Senior Cruiser
 
Captain Bill's Avatar

Cruisers Forum Supporter

Join Date: Apr 2008
Location: On the boat
Boat: Endeavourcat Sailcat 44
Posts: 2,313
Re: WSF Hyak collision update.

Did they really say that the fishing boat was in the wrong because it did not have AIS? Being under 65 feet it was not required to have AIS. Is the CG going to start blaming accidents on boats without AIS even if they aren't required? It sounds to me like the ferry crew was not watching the radar which they are required to do if they have it on board.
__________________
Captain Bill is offline   Reply With Quote
Old 27-10-2013, 19:32   #7
Moderator
 
Paul Elliott's Avatar

Cruisers Forum Supporter

Join Date: Sep 2006
Posts: 3,858
Images: 4
Re: WSF Hyak collision update.

Quote:
Originally Posted by Captain Bill View Post
Did they really say that the fishing boat was in the wrong because it did not have AIS? Being under 65 feet it was not required to have AIS. Is the CG going to start blaming accidents on boats without AIS even if they aren't required? It sounds to me like the ferry crew was not watching the radar which they are required to do if they have it on board.
I don't think so. That's how I read it at first, but careful parsing of the statement
Quote:
Akiyama says the fishing boat was in the wrong and did not have the automated identification system the Coast Guard uses to monitor vessel traffic.
tells me they meant this:
1) The fishing boat was in the wrong.
2) Also, the fishing boat didn't have an AIS transponder.

AIS is not required for the fishing boat, but it might have been useful in this case.
__________________
Paul Elliott, S/V VALIS - Pacific Seacraft 44 #16 - Friday Harbor, WA
www.sailvalis.com
Paul Elliott is offline   Reply With Quote
Old 13-11-2013, 22:35   #8
Registered User

Join Date: Jun 2013
Location: Santa Cruz, CA
Posts: 114
Latest news. Ferry at fault.
http://www.wsdot.wa.gov/News/2013/11/Hyak_111313.htm
__________________
Captain Bligh is offline   Reply With Quote
Old 13-11-2013, 23:13   #9
Moderator
 
Paul Elliott's Avatar

Cruisers Forum Supporter

Join Date: Sep 2006
Posts: 3,858
Images: 4
Re: WSF Hyak collision update.

Here's the report from the Board of Inquiry: http://www.wsdot.wa.gov/NR/rdonlyres...portforWeb.pdf
__________________
Paul Elliott, S/V VALIS - Pacific Seacraft 44 #16 - Friday Harbor, WA
www.sailvalis.com
Paul Elliott is offline   Reply With Quote
Old 13-11-2013, 23:19   #10
Registered User

Join Date: Jun 2013
Location: Santa Cruz, CA
Posts: 114
Yeah. Its a good read. Very informative. Its amazing how quickly that situation developed. There was no room for error. Unfortunately an error occurred.
__________________
Captain Bligh is offline   Reply With Quote
Old 14-11-2013, 02:53   #11
Nearly an old salt
 
goboatingnow's Avatar

Cruisers Forum Supporter

Join Date: Jun 2009
Posts: 13,649
Images: 3
One feels sorry for the capitain. It shows how lack of situational awareness can develop quickly into an incident. Noteworthy despite the debate here the yacht shares no blame at all.

Dave
__________________
Check out my new blog on smart boat technology, networking and gadgets for the connected sailor! - http://smartboats.tumblr.com
goboatingnow is offline   Reply With Quote
Old 14-11-2013, 05:41   #12
cruiser

Join Date: Nov 2013
Posts: 31
Re: WSF Hyak collision update.

Quote:
Originally Posted by goboatingnow View Post
One feels sorry for the capitain. It shows how lack of situational awareness can develop quickly into an incident.
Dave

...How much can I sue him for?...ahahaaaa

That can only happened in America, probably in some other "Gordon Gekko" countries. they can not wait to sue for compensation and try to milk as much money as possible. There is no collision, nothing happened, no casualties, if that happened somewhere in the med perhaps even in northern Europe no one would even mention it.

this happened in croatia couple of a years ago. they all went to the first pub to have a drink, crew and pssengres together. there wasn't one single crew member sacked, or passenger pressed charges against company.

__________________
gloriax is offline   Reply With Quote
Old 14-11-2013, 06:19   #13
cruiser

Join Date: Nov 2013
Posts: 31
Re: WSF Hyak collision update.

Quote:
Originally Posted by gloriax View Post

...How much can I sue him for?...ahahaaaa

That can only happened in America, probably in some other "Gordon Gekko" countries. they can not wait to sue for compensation and try to milk as much money as possible. There is no collision, nothing happened, no casualties, if that happened somewhere in the med perhaps even in northern Europe no one would even mention it.

sorry, I should mention it. my post is reply for

"Near collision for Washington ferry in fog
__________________
gloriax is offline   Reply With Quote
Old 14-11-2013, 06:20   #14
Marine Service Provider
 
Maine Sail's Avatar

Join Date: Jan 2007
Location: Maine
Boat: CS-36T - Cupecoy
Posts: 3,060
Re: WSF Hyak collision update.

I find it interesting that in earlier reports the rudder command was stated as turn LEFT not turn to PORT yet the report only mentions a "non-specific rudder command of port"?

I find it confusing what a non-specific turn to port is; “come to port and sound the whistle if you deem it necessary.” command? I suppose non-specific means how much rudder to port...?

Am I alone on the earlier reports that the bridge command was "Turn left and sound the whistle of you deem it necessary."......

Are they attempting to diminish something by saying "non-specific port command" vs. "The Captain gave a non-specific order to turn left".......?

How does a paid professional mistake port for starboard? This stuff is so engrained in the brain that it would seem unrealistic for a mistake like this to happen.......?? I can see where "left" might cause that sort of momentary lapse to someone expecting to hear PORT or STARBOARD, but port is port on a vessel and starboard is starboard.......... This is Play-Doh & Lego level elementary learning......
__________________
Marine How To Articles
Maine Sail is offline   Reply With Quote
Old 14-11-2013, 07:27   #15
Senior Cruiser

Cruisers Forum Supporter

Join Date: Nov 2005
Location: Out there doin' it
Boat: 47' Olympic Adventure
Posts: 2,633
Re: WSF Hyak collision update.

Quote:
Originally Posted by goboatingnow View Post
Noteworthy despite the debate here the yacht shares no blame at all.
On that point, it is an internal investigation - WSF's own look at how they went wrong and how they can improve. I think a USCG investigation would probably include a little more information about the yacht, and would look at the watch kept and actions taken/not taken.
__________________

__________________
Lodesman is offline   Reply With Quote
Reply

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off




Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -7. The time now is 08:46.


Google+
Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
Social Knowledge Networks
Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.

ShowCase vBulletin Plugins by Drive Thru Online, Inc.