|
#1
|
|||
|
|||
|
MCLEAN, Va. — Complacency and poor management of surface contacts led to the March 20 collision between the attack submarine Hartford and the amphibious transport dock New Orleans in the Strait of Hormuz, according to the Navy’s leader of the undersea fleet.
Speaking Wednesday at the annual Naval Submarine League meeting, Submarine Force commander Vice Adm. Jay Donnelly described a control room with “a lot of informality” and a “series of personnel failures” he blamed on the sub’s leadership. The collision, which happened at night, came as the sub was making a submerged transit to Jebel Ali, its last port call before heading home to Groton, Conn. The crew had just finished an intense operational phase of its deployment and “everybody let down their guard” for what was actually one of the most challenging phases, crossing the strait at periscope depth, he said. “There was a great deal of complacency involved in the crew,” he said. “They had been at sea for 63 days operating in areas with high contact density.” After the collision, both ships limped into Bahrain, New Orleans with a giant gash in the hull and Hartford with a sail partially torn from its hull, among other damage. No one was seriously injured in either crew. Hartford’s damage was complicated and the ship is still in the yard. New Orleans rejoined the fleet from Bahrain. The commanding officer of Hartford, Cmdr. Ryan Brookhart, and chief of the boat Master Chief Electronics Technician (SS) Stefan Prevot were both fired after the incident. Speaking in response to a question after his prepared remarks, Donnelly said he had just spent a day on Capitol Hill last week explaining the incident to House and Senate armed services committees. He also noted that more or better technology would not have helped the situation, as the sub knew the New Orleans and another ship were nearby. “There were a whole host of watchstanders that failed to recognize the sensor data that was presented to them,” he said. Lessons learned are already being integrated into submariner training, he added. Article: http://www.navytimes.com/news/2009/1...ssons_102809w/ |
|
#2
|
|||
|
|||
|
Clearly an example of poor leadership. A Navigator listening to his IPOD while supervising is an example of a leader tyring to fit in with their sailors. Sailors need mentoring and a leader who can "LEAD BY EXAMPLE". UNSAT.
__________________
"It is very tempting to rationalize-to "rig" the probable outcome to make it seem that the alternative that favors you is also "found" to be the one that does the most good. When you rationalize, you violate the impartiality requirement." -John Hospers Navy EOA |
|
#3
|
|||
|
|||
|
This is a much better article.
http://www.navytimes.com/news/2009/1...tford_111509w/ It clarifies what the Nav was doing. He should have been in the Control Room. Skipper's fault on that one.
__________________
The current special guest sig: "Happily, Chief Sweety Buns!" CVal, 5:59 PM, 19 Nov 2009. Cabal Director of Transportation Accounts Payable ‹(•¿•)› Pro Deo Et Patria |
|
#4
|
|||
|
|||
|
The navigator was listening to his iPod during a critical evolution.
Watchstanders were known to sleep on the job. Stereo speakers were rigged for music in the radio room. An informal atmosphere — along with crew complacency, a “weak” command and inferior submariner skills — are named as contributors to the March 20 collision between the attack submarine Hartford and the amphibious transport dock New Orleans in the Strait of Hormuz. And according to a heavily redacted 102-page Judge Advocate General Manual investigation obtained by Navy Times through a Freedom of Information Act request, what turned into a major embarrassment for the submarine fleet was entirely “avoidable.” The collision happened just after midnight in calm seas as Hartford was at periscope depth and southbound, crossing the strait bound for a port call in Jebel Ali, United Arab Emirates. New Orleans — 70 days into its first deployment — was westbound, exiting the surface transit lane of the strait. The state-of-the-art gator was entering the Persian Gulf as part of the Boxer Amphibious Ready Group. The ships crashed as they intersected. Fifteen sailors on Hartford were hurt, none more seriously than during a typical swim call, according to the boat’s corpsman. No one on New Orleans was injured. The crew of New Orleans “bears no fault” for the accident, the report said. When it was all over, Hartford would take one month to limp home to Groton, Conn., on the surface, its captain and chief of the boat both fired. Today, Hartford is still undergoing extensive repairs to its bent sail, internal components and damaged bow planes at General Dynamics Electric Boat in Groton. Industry experts estimate the bill to be more than $100 million. New Orleans suffered a 16-by-18-foot gash in its hull. It would spend 53 days in Bahrain undergoing $2.3 million in repairs while stranding embarked leathernecks from the 13th Marine Expeditionary Unit. Problems at the top Blame for the whole debacle lands squarely with a command team on Hartford that tolerated an “informal” atmosphere on the ship, the report said. Cmdr. Ryan Brookhart was detached for cause and chief of the boat Master Chief Electronics Technician (SS) Stefan Prevot was reassigned to Submarine Squadron 4 in the aftermath. The navigator, executive officer and weapons officer underwent nonjudicial punishment, as did 10 sailors. Also, administrative action was taken against three direct support element members assigned to Naval Information Operations Command in Georgia as well as a fleet intelligence specialist based near Washington, D.C. The report did not explain what role they played. The report’s final endorsement, by Fleet Forces Command head Adm. John Harvey, called the accident the result of “nearly 30 tactical and watchstander errors” in the hour before the collision. He also noted that the command failed to hold subordinates accountable, “and a high price has been paid for that shortcoming.” Harvey also directed the submarine force to review all collisions back to the attack sub Greeneville’s fatal crash into a Japanese fisheries training boat in 2001 near Hawaii. Vice Adm. Jay Donnelly, Submarine Force commander, spoke candidly about the mishap Oct. 28 during the annual Naval Submarine League meeting in McLean, Va. He said the crew had just finished an intense operational phase of its deployment and “everybody let down their guard” for what was actually one of the most challenging phases, crossing the strait at periscope depth. He also noted that more or better technology would not have helped the situation, as the sub crew knew New Orleans and another ship were nearby. A bigger issue The collision illustrates the force’s larger problem with contact management. An internal message sent by Submarine Force Pacific commander Rear Adm. Douglas McAneny less than a month after the collision urged commanders and commodores to boost crews’ ability to track surface contacts. “Over several months” prior to the incident, hundreds of watchstanders were tested in their ability to understand how to analyze the movement of surface contacts. The exams yielded results of 10 percent to 15 percent passing grades among enlisted watchstanders and 60 percent of officers. “Given the attention I have personally placed on submerged contact management in briefing the waterfronts, this is unacceptable,” McAneny wrote in the message obtained by Navy Times. Not up to standard At the time of the collision, the sub was southbound at periscope depth, periodically raising and lowering its periscope. When the ships collided, the New Orleans crew felt “a shudder and rumbling.” That bridge team slowed to 3 knots and launched a small boat to look for damage. The big amphib had flooding in ballast and fuel tanks and listed “1.5 degrees to starboard.” On Hartford, the crash caused the door of the control room to be jammed shut by a battle lantern, a fuel leak in the machinery room, and “light smoke” in that space and in the torpedo room. The bow planes were not working and the periscopes would not rise. The towed array was retrieved and baffles cleared before conducting an emergency blow and surfacing 3,000 yards from New Orleans. It took the crew nearly four hours using “wedges and a portable hydraulic jack” to pry open hatches up to the bridge. Blame is on Brookhart for failing to plan the “strait transit and crossing evolution,” for failing to communicate the plan, and leaving watchstanders without “the heightened risk that should have been foremost on everyone’s mind.” But the watchstanders were not up to standard to begin with, according to the report. Control room understanding of contact management was found to be poor enough that crewmembers “routinely failed to critically evaluate the validity” of computer-generated contact information with “raw sensor data.” But as McAneny urged commanders to get their crews up to standard, the causes of the collision point to leadership. Brookhart, the executive officer and COB were together tagged with setting a command climate that lacked a “questioning attitude” that is expected in the submarine force and for fostering a “general level of complacency.” It was felt by even the youngest sailors. Helmsmen — always the newest crew — told investigators they often would “slouch in their seats with one hand on the controls,” and would “take off their shoes while driving the ship.” Sailors also reported a lax attitude in the sonar division about taking breaks. On the night of the crash, sonar operators chatted “for the majority of the time [in the hour before] the collision.” An officer of the deck did not look through the periscope prior to the collision after taking over contact management duties. The navigator, off-watch, was found to have been taking an engineering exam in the wardroom “while listening to his iPod,” despite the hazardous evolution underway. Brookhart was never in the control room during any time crossing the strait, the investigators found. Prior to the accident, speakers had been installed in the ultra-sensitive radio room “that allowed music to be played from an iPod while on watch. This was hidden from the Chain of Command.” Perhaps most shocking was this revelation: “Many crewmembers stated there were numerous ‘known’ sleepers [five specific names were reiterated by the majority of those crewmembers interviewed]. Those personnel would routinely fall asleep [‘nod off’] on watch, and no disciplinary action was taken.” Two of the known sleepers were on watch during the collision, the report states. The investigating team does make a point at the end of the report to say most of the sailors on the ship were of an “absolutely superb caliber” now “hungering for effective leadership” and “eager to restore their ship’s standing.” Article: http://www.militarytimes.com/news/20...tford_111509w/ |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|