Yesterday my comments were published on the front page of The San Francisco Chronicle in an article titled; “Hearing today at Presidio - tough queries for spill captain.”
Prior to being asked to comment the Chronicle’s lead maritime reporter contacted our friend Captain Kelly Sweeny who discussed industry wide problems with marine technology. The article states;
Sweeney said the AIS is “occasionally unreliable,” has blind spots such as when a ship is behind islands or structures, and is “antiquated” when compared with modern electronics.
Rewinding to my conversation with the reporters, the first question asked was; “Captain Sweeny believes the system used by San Francisco’s Vessel Traffic Service (VTS) is antiquated, do you agree?” After requesting further clarification I was asked why the pilot’s data on his Electronic Chart Display was trusted over VTS’s radar and AIS information.
My answer was “VTS’ AIS system is susceptible to the delay inherit in the VHF transmission of AIS data” BUT, to be honest my initial gut reaction was, “no AIS is not antiquated… it was fully implemented less then 3 years ago”, I quickly corrected myself. My second answer was quoted in the article and reads;
“The maritime industry is slow to act on electronic devices,” said Capt. John Konrad, who runs a Web site called gCaptain. “By the time they get approvals on electronics, they are obsolete.”
Why the quick change of opinion? It’s because I love AIS.
This technology, properly called Automatic Identification Systems, allows me to overlay important data on my radar displays. It also allows me to contact a ship with a zero cpa (collision course) with great ease. For example, prior to AIS I would have to say “Calling the vessel in position x.xx degrees N, x.xx degrees west on a course of 267 and speed of 6knots this is the xxx on channel 16″ where now I simply look up the ship’s name and say “This is the xxx calling yyy on channel 16″. Furthermore the AIS display gives me the vessels MMSI number which opens up new and creative ways to avoid collisions. Finally, my AIS digital read-out really saved the day (and my career?) when our radars, as the Cosco Busan’s Pilot John Cota said “conked out”.
That was not my only hesitation. San Francisco Pilots are some of the most respected individuals in our profession (a dream job for myself) and I only have positive things to say about my dealings with VTS. So could they be wrong in their choice of equipment? It seemed unlikely.
In defending VTS and the Coast Guard’s systems another respected expert, Rear Adm. Craig Bone - Coast Guard district commander, commented on questions raised by myself and others. In covering today’s hearing The Chronicle reports;
Bone said he could think of no excuse for the crash. He denied reports by maritime sources claiming the electronic systems the Coast Guard uses are out of date. The pilot equipment and onboard navigational equipment are some of the most advanced, he said.
“There is no basis in my mind for this to have ever occurred,” Bone said. “Something on that ship had to go terribly wrong. It was totally preventable.”
So the question becomes; “If AIS is a loved safety improvement endorsed by maritime experts worldwide why does Captain Kelly (and myself!) consider it antiquated?”
The reason is because we can do better! In the world of cutting edge technology solutions are available now that would have given Cota and VTS a much better chance of avoiding the incident. The problem, that I suspect is an industry wide tendency, is two fold. First we are so far behind the technology curve small improvements, like AIS, seem large and exciting. Second, most licensed captains are Luddites (my self included) who want to make sure a new system is reliable before implementing it aboard ships.
I come to this conclusion because, despite my writings on the need to improve shipboard technology (most notably HERE and HERE), I initially had the same reaction as Adm. Bone but quickly changed my mind. Why? Because Capt. Kelly is correct, our systems are antiquated and when new lifesaving improvements become available we must break away from the statement that has been rehearsed by ship captains for centuries; “Only history will tell if this is a good idea”. Exciting changes are happening worldwide and improvements in communications (the number one failure in all good incident chains) are leading the way. We must change with the times and embrace technology as the benefit is a reduction of incidents and a preservation of the environment and human life.
For more information on this topic visit our Archives.
Still agreeing with Admiral Bone? Take a look at technology used by Tampa Pilots or Maine Pilots, upcoming portable ECDIS units, the VTS tracking system in Valdez, well documented problems with AIS Ask yourself “Can I send an area specific sitor message via GMDSS” or “Why can my son video chat with a pen pal in China while I’m having trouble raising a vessel 1000 yards away… and closing?”

Captain John Konrad is a USCG licensed Master Mariner of Unlimited Tonnage currently working aboard an 835′ship in the Gulf of Mexico. Since graduating from SUNY Maritime College he has sailed 4 of the world’s oceans and reports from his ship via satellite.
Tags: · ais, allision, bay_bridge, boats, Captain_sweeny, carl_nolte, Communication, congressional_hearings, cosco_busan, ecdis, Environment, george_miller, john_cota, Marine Technology, Maritime, MARPOL Incidents, Master Mariner, Nancy_pelosi, oil_spill, radar, Regulations, San Francisco, san_francisco, san_francisco_chronicle, Ships, USCG, vts
In other news The San Jose Mercury News tells us;
The International Maritime Organization saw the Cosco Busan oil spill coming: Last year, it banned new ships from being built with their fuel tanks along the hull beginning in 2010.
In effect, the U.N. agency determined that increasingly large, fast ships that carry as much fuel as a small oil tanker should not carry that fuel along the side of the vessel, directly behind a single-layer hull.
One UC-Berkeley engineering professor compared the design to the Ford Pinto, the 1970s car that gained a reputation for gasoline tanks that could explode in rear-end accidents.
“I think the Pinto is the perfect example,” said Bob Bea, who is also a former oil tanker captain. “We need to recall them and retrofit. Put them (fuel tanks) inside.”
Built in 2001, the Cosco Busan is among the growing number of bigger, faster container ships that have “winged tanks” - fuel tanks arrayed along the sides of the ship.
The IMO convention, adopted in March 2006, requires that by 2010 all new ships with an oil fuel capacity of 600 cubic meters or more must have their fuel tanks deeper inside the ship and behind two walls. That rule affects most large commercial ships, and would have affected the Cosco Busan.
Bea said few are aware of the action taken by the London-based IMO, even within the shipping industry, because the licensing bodies that put those regulations into effect have yet to write and distribute information about it.
The IMO convention applies only to new ships, or those that undergo major modifications. It does not phase out winged tanks, meaning it is likely that container ships with winged tanks will be around for decades.
“We have a fleet full of those damn things out there, and they are exposed and so are we,” Bea said.
The Cosco Busan is capable of carrying 5,500 20-foot containers, about half the capacity of the world’s largest container ships, which carry the equivalent of trains 70 miles long across oceans at 25 knots, or about 30 miles per hour. Continue Reading…
To follow gCaptain’s coverage of the incident CLICK HERE.
To view a photo slideshow of the incident CLICK HERE.
Tags: · allision, bay_bridge, cosco_busan, Environment, marpol, MARPOL Incidents, oils_spill, San Francisco, ship, Video

Coast Guard Photo By CWO Scott Epeprson
I thought I would list a few podcasts, interviews and audio files that relate to the Cosco Busan Incident and the resultant oil spill in San Francisco Bay. If you find any more of interest please leave a comment with link below.
Our first file (click on the player below) is a very informative hour long discussion I heard on the radio earlier today. It is from KQED’s Forum and is nationaly syndicated by NPR. (Direct Link)

With a criminal probe now launched by the U.S. attorney in San Francisco into Wednesday’s crash of the container ship Cosco Busan, Forum looks at whether oil spills are preventable.
Host: Michael Krasny
Guests:
 |
Debbie Hersman, board member of the National Transportation Safety Board |
 |
Paul Rogers, resources and environment writer with the San Jose Mercury News and managing editor of QUEST, KQED’s weekly science and environment program |
 |
Rear Admiral Craig Bone, the U.S. Coast Guard’s top official in California; and George Miller, Democratic congressman from California’s Seventh District. |
 |
Robert Bea, professor of civil engineering at the University of California at Berkeley |
First is the audio file from the US Coast Guard Commandant , Admiral Thad Allen’s meeting with the San Francisco Chronicle. (Direct Link)

Coast Guard talks with Chronicle
Coast Guard Commandant Adm. Thad Allen and Rear Adm. Craig Bone spoke to The Chronicle Monday morning about the oil spill and the Coast Guard’s response time to the incident. Here’s what they had to say:

KQED Forum - Cosco Busan Oil Spill:
Play Now |
Play in Popup |
Download

Coast Guard talks with Chronicle:
Play Now |
Play in Popup |
Download
Tags: · accident, admiral, audio, bay, bay_bridge, coast_guard, commandant, Container Ship, cosco_busan, Craig_Bone, Debbie_Hersman, forum, kqed, Maritime Expert, MARPOL Incidents, npr, ntsb, oil_spill, Paul_Rogers, podcast, Robert_Bea, San Francisco, USCG
The San Francisco Chronicle has published the Pilot’s Report on the Cosco Busan Incident. Here are the parts of interest to mariners;
Meadows said problems also cropped up in “bridge management,” the communication between the pilot, who had years of experience on the bay, and the ship’s officers, who had never navigated the bay in the Cosco Busan. All were supposed to work together and exchange information on how to successfully navigate the harbor.
“While some information was exchanged, perhaps it could be said it wasn’t a full transfer of information. It was enough for the pilot to work with the master and get the ship ready for sea,” Meadows said.
We have previously reported on bridge management also know as Bridge Team Management or BRM.
gCaptain’s BRM related articles;
The article continues;
The Cosco Busan’s radar “conked out” twice - first before departure and again as the ship was near the lighthouse on Yerba Buena Island.
Cota was forced to rely on an electronic chart display, showing the track of the vessel and its speed, plus charts of San Francisco Bay. Meadows said the pilot told him he was “not familiar” with the electronic system on the Cosco Busan. “They are all different,” Meadows said.
Cota asked Mao Cai Sun, the captain of the Cosco Busan, to point on the display to the center of the bridge span between the Delta and Echo towers on the western side of the Bay Bridge.
“The master pointed that out,” Meadows said. “In fact, several times during the trip. That’s what the pilot was heading for.”
…
“The pilot had to go along with what the master indicated on the electronic chart display was the center of the span,” Meadows said. “That turned out to be the tower instead.”
We have received email asking; Should the vessel have left without a working radar? and Did the second radar work? …unfortunately those are questions we can’t answer. You will have to wait until the NTSB investigation report is complete.
Read the full SF Chronicle article HERE.
Related Maritime Blog Posts;
Tags: · bay_bridge, bridge_management, bridge_resource_management, bridge_team, busan, Communication, Container Ship, cosco, ecids, electronic_chart, incident_report, MARPOL Incidents, pasha_bulker, pilot, radar, San Francisco, san_francisco_chronicle, yerba_buena_island
I have been amazed lately by the number of errors in both media reports and political commentary related to the the container ship Cosco Busan that allided with San Francisco’s Bay Bridge. We first reported on the confusion between the words allision and collision but that debate is mostly semantic. The errors have grown as the debate has reached a national audience.
The most troubling mistake is reports that infer or flatly state the vessel is a tanker. This mistake has been made numerous times as can be seen by doing a simple google news search for the incorrect term but most seriously in USA Today’s, America’s most widely distributed newspaper, headline (page A6 of November 12th’s edition): “Coast Guard: Tanker crew tested for substances.”
The media is not the only “informed” party making this mistake. The San Francisco Chronicle reports on a statement by San Francisc’s mayor:
Newsom saw the disaster as an even larger statement on the weakness of America’s dependence on oil.
“We can do better than large oil tankers coming in and out of the bay of San Francisco, and move to a more energy independent future,” he said at Crissy Field. “We’ll continue to have these kinds of disasters inevitably if we continue to have more tankers come in and out to feed our addiction.”
So for those in the media or with a passing interest here is a picture of an Oil Tanker and the Cosco Busan:


The major difference between the two is: a tanker transports liquids and a container ship transports containers filled with solids (i.e. toys, home furnishings, industrial supplies…). So before the flood of emails arrive… if the ship that hit the San Francisco Bay Bridge was not transporting any liquids why did it have 58,000 gallons aboard? The answer is… for the same reason your car carries 24 gallons of gasoline.
The fuel spilled in the bay was all to be used by the ship’s enormous engines during the long transit back to China. Had this ship been an oil tanker the spill could have been as large as the one caused by the oil tanker Exxon Valdez… then again probably not since the oil in those ships are now required to be protected by a double hull.
Tags: · bay_bridge, coast_guard, Container Ship, container_ship, cosco_busan, Engines, Environment, marpol, MARPOL Incidents, news, oil_spill, San Francisco, san_francisco, Tankers, USA_today, USCG
First a note… I am publishing this short clip ahead of my next article because of its importance!
While preparing our upcoming “questions for investigators” article on the Cosco Busan incident we were asked by more than one party a question along this line; with communications failure being a leading cause of incidents and the crew of the Cosco Busan being Chinese of limited english skills (they required translators during the investigation) why do incidents of this type not happen more often?
The answer is Bridge Team Management.
Ok… so what is BRM?
Revisiting a previous post I state:
- Bridge Team (or resource) Management (called BRM in the industry) is a process to use all of your available resources during critical operations. It came from the airline industry which found an alarming number of accidents happened despite prior warning from the equipment or crew…. mostly by captains with military backgrounds and a “I can do this” attitude who did not fully use critical information from either the equipment or junior personnel.Boiled down it’s a class all officers must take in both teamwork and processing the large amounts of data (lookout reports, radar, radio comms, gps charting, weather information….) that pours into the bridge.
- Here’s a more official answer:The Bridge Team Management course introduces the concept of a navigation team to ship masters and watch officers and frames their decision making process toward establishing watch conditions during the course of the voyage. Bridge Team Management techniques will emphasize decision making based upon conditions related to workload and potential threat to the vessel. The intent of the program is to define the individual task and responsibilities of the various team members while developing a situational awareness to prevent individual errors.
In stating the importance of this post I am looking at the media reaction to the incident. In reporting disasters the public is often not satisfied until a single individual is blamed…. quickly. This was the case in the Exxon Valdez oil spill, Tampa Skyway Bridge Disaster and even in the early reports on the Empress of the North grounding where fault was placed on the Jr. Officer on watch who was only weeks out of the Maritime Academy. In the Empress of the North incident gCaptain broke from traditional media and laid the blame on management techniques rather than the “green” officer and we are happy to report he was recently clear of all charges (as was Capt. Hazelwood of the Exxon Valdez).
It is clear to us the Cosco Busan allided with the Bay Bridge because of a breakdown in Bridge Team Management. For example while VTS contacted the ship questing its course did the mate on watch, captain, helmsman or assist tug captain also voice concern? Was the equipment operational and set up properly? As the primary fault for the Exxon Valdez incident was not with Captain Hazelwood (he was cleared of charges and his license was reinstated) John Cota, Pilot aboard the Cosco Busan is not solely at fault for this incident.
The team failed the Cosco Busan not the ship’s Chinese Captain or American Pilot alone. Lets just hope the court of public opinion does not convict either person before the long and thorough investigation is completed. Otherwise they might stand the fate of Captain Hazelwood, cleared of charges and fully licensed to pilot a ship but unable to find a company willing to hire him.
________
Asking yourself how a ship 131 wide could have such trouble in a channel 737 metres wide? Read a more unbelievable story HERE then watch the amazing slideshow HERE.
UPDATE: Bob Couttie of the Maritime Accident Casebook has a very interesting article along similar lines. You can find it HERE.
UPDATE 2:
Criminal probe opened in Bay oil spill
The entire crew of the cargo ship that sideswiped a bridge, causing San Francisco Bay’s worst oil spill in nearly two decades, has been detained as part of a criminal investigation, a Coast Guard official said Sunday.
Capt. William Uberti said he notified the U.S. attorney’s office on Saturday about issues involving management and communication among members of the bridge crew: the helmsman, the watch officer, the ship’s master and the pilot.
Tags: · allision, bay_bridge, bridge_team, China, collision, Communication, communications_failure, Container Ship, cosco_busan, Empress Of The North, Incidents, marpol, MARPOL Incidents, Master Mariner, oil_spill, pasha_bulker, San Francisco, san_francisco, sopep, team_management, Uncategorized
UPDATE: BoatingSF has a new animation that can be found here: COSCO BUSAN’S TRACK - UPDATED
_________________
Our friend John of VesselTrax.com submitted this link to our Maritime News Discoverer. Click on the picture below and watch as the Cosco Busan leaves the dock and embarks on its fateful voyage.
From BoatingSF.com:
Path of the Cosco Busan Hitting the Bay Bridge
The animation below shows the Cosco Busan as it leaves the Port of Oakland on November 7, 2007, and hits the Bay Bridge at 8:30 am on its way to the Golden Gate.
The Cosco Busan is the bright red arrow. (Hover over a ship to see its information.)
You can see that the ship was traveling at an acute angle to the bridge and then turned sharply, directly into the center tower of the bridge. (The towers are highlighted with red dots to make them more visible.)
No cleanup ships show up in our AIS records. It is not clear whether they arrived later, did not have their AIS transponders on, or if for some reason our receiver did not detect their signals. (Coast Guard ships generally do not turn on their AIS transponders, so they do not show up.)

Click here for FULL ANIMATION
Stay Tuned as our licensed ship captain John Konrad is preparing a play-by-play video of this AIS data. In the meantime CLICK HERE for the SFGate’s excellent coverage of the incident.
UPDATE 2:
You can find a complete article on how this animation was made HERE.
Tags: · ais, allision, bay_bridge, beaches, Bridges, cleanup, coast_guard_ships, Container Ship, cosco_busan, fateful_voyage, golden_gate, Incidents, maritime_news, MARPOL Incidents, oil_spill, port_of_oakland, San Francisco, Web 2.0