Posts tagged as:

uscg policy

button

Comment on NTSB findings

by Douglas Gould on July 17, 2011

After rushing off to do some towing the other day, I now have time to put some comments down in enk (electronic ink). First, here is the link to the NTSB one page synopsis of the pending full accident report (which is due out in a few weeks):

http://www.ntsb.gov/news/events/2011/sandiego_ca/synopsis.html

The NTSB clearly lays the blame for this tragedy entirely on the US Coast Guard:

The National Transportation Safety Board determines the probable cause of the collision between the CG 33118 and the Sea Ray was the failure of the CG 33118 crew to see and avoid the Sea Ray because of the excessive speed at which the coxswain operated the CG 33118, given the prevailing darkness, background lighting, and high vessel density and the U.S. Coast Guard’s lack of effective oversight of its small boat operations both nationally and at Coast Guard Station San Diego.

from the coxswain to the station brass and right up to the national level. Lack of oversight is not a phrase that will increase chances of promotion for those in charge of USCG Station San Diego, and the NTSB report will make it very hard for those at command level to shirk their burden of responsibility.

To refresh your memory, CG 33118 (a 33′ RIB) was responding to a report of a grounded boat inside San Diego Bay, and at one point was doing ~42kts through a dark harbor full of spectator boats after a Christmas boat parade. They hit a small boat en route to the grounding and one person died as a result of the collision

Since the accident, much of the news coming out of the investigation focused on the use of cell phones as a possible contributing factor (see my post here). Interestingly, now that the investigation is complete, that is now just one of fifteen contributing factors. #2 on the list caught my attention:

The vessel grounding to which the CG 33118 responded was not an emergency and did not necessitate a high-speed response that reached 42 knots at one point. (boldface added)

This point is where the entire topic fetches up, and I think even the NTSB failed to fully illuminate the issue. The real question is not why was the USCG rushing to a grounded boat in Harbor Island Lagoon, but why were they responding at all? The record shows that the grounded sailor stated he was in no danger, and a MARB was broadcast from USCGSD. The policy is very clear on this, and states that for non-emergency cases, the USCG will find other sources of assistance. Why was 33118 even heading in that direction in contradiction of stated USCG policy?

Has the CG become bureaucratically predisposed to treat every single case as an emergency; anxious to bask in the headlines? (see previous post here)  Perhaps, but I don’t think so. I fear something even more insidious is going on. The trend I have seen is for the CG to jump on low risk cases, like grounded sailboats in protected harbors, while at the same time, the SAR commanders actually avoid high risk cases where a mishap would have them called before a Captain’s Mast, or even jeopardize their career.

I know, you’re thinking “give ‘em a break” and “it’s an isolated case, Doug. You’re blowing it out of proportion.” Am I?

Allow me to illustrate a startling contrast to the above with a recent personal experience with the Coast Guard Sector New England. About two weeks ago, I relieved a commercial fisherman who was towing a disabled 55′ Viking sportfisher from the offshore fishing grounds. The Viking had suffered a small electric fire and one of their crew had been injured during the melee of firefighting.  He had a badly lacerated upper lip, two missing front teeth and cut gums. The crew of the Viking had requested that the USCG arrange an evacuation of the injured party so he could get immediate medical attention on the mainland, while I was going to tow the Viking to the mainland. The tow was going to take about 3.5 hours.

After numerous phone calls from our office, we were informed that the USCG “has declined a medivac” for this situation. WTF?!? The seas were calm and the victim was ambularoty; all they needed to do was send a fast boat to rendezvous with us. The owner of the Viking finally phoned a personal friend with a fast RIB to come out 18 miles and meet us to take his injured crew to shore. Somehow, I don’t think you’ll see that case in the USCG news feed…

So, on the one hand, we have the USCG actually killing an 8 year old boy while they rush to the scene of a non-emergency grounding when no request for assistance was made; and on the other hand, the USCG refuses to comply with a request to evacuate a rather serverly injured boater.

The USCG has become a dysfunctional bureaucracy plagued by inconsistent decisions and a command structure that circumvents accountability. You might not agree with me, but the National Transportation Safety Board does.

Share
button

2010 Boating Accidents Report

by Douglas Gould on June 17, 2011

Every year, the U.S. Coast Guard compiles statistics on reported recreational boating accidents. These statistics are derived from accident reports that are filed by the owners / operators of recreational vessels involved in accidents. The fifty states, five U.S. territories and the District of Columbia submit accident report data to the Coast Guard for inclusion in the annual Boating Statistics publication. The [annual] Boating Statistics publications are available here for you to download.

Download the PDF 2010 report here, or read it below. If nothing else, read the summary on page 6. One thing I found surprising was “Operator Inattention” was one of the primary causes of boating accidents. They don’t list operator distraction as a separate category yet, but I suspect they will in the future, as they find more and more accidents are caused by electronic distraction; mainly cell phones.

The report doesn’t include statistics from commercial activities, but there have been a number of high profile accidents in the past few years that are being attributed to cell phone distractions in the pilot house. The DUKW boat collision in PA and the Coast Guard vs 21′ Sea Ray in San Diego come to mind, not to mention a few tragedies in our own industry.

The report is very readable and filled with interesting charts and graphs.

 

 

Share

Will my prediction come true?

Back in August of 2010, I made a prediction [here]: I’m going on the record now as saying that the USCG will impose some kind of policy restricting the use of cell phones on commercial vessels within 24 months. If we learn that the tugboat driver in Philly who hit that Duck Boat last month [...]

Share
March 8, 2011 Read the full article →

NTSB urges policy on cell use on Coast Guard boats

I posted a few months ago [here] about the recent studies re: driving and cell phone distractions. When people die, the National Transportation Safety Board likes to do some poking around, and they found an interesting similarity concerning two recent collisions between USCG assets and private boats. Seems the Coasties are on the phone or [...]

Share
August 11, 2010 Read the full article →

Out of gas brings $2MM towboat to the “rescue”

Oh, boy. Don’t get me started….. Here is a story that might bite the USCG boys in NYC right in the transom. Gee, having some press tag along to promote these brand new (yawn… same twin jet technology I’ve been driving for 8 years) $2 million boats seemed like such a good idea. Yeah, give [...]

Share
June 2, 2010 Read the full article →

New police boat to help Coast Guard

New Suffolk police boat to help Coast Guard Gosh, so many reactions to this news piece. I love this headline, “… to help Coast Guard.” Gee, when did the City of Suffolk, VA. Police last help the Coast Guard execute a MARB? No, I don’t mean respond to a MARB, I mean make the broadcast. [...]

Share
May 21, 2010 Read the full article →