Summary and Key Points: During the 1980s, the USS Enterprise aircraft carrier experienced a series of troubling incidents, leading some to wonder if it was jinxed.
-In 1985, it collided with the submerged Bishop Rock, suffering a 60-foot hull breach that nearly sank it. Quick action by its crew prevented disaster, protecting its nuclear propulsion system.
Naval Station Norfolk, Va. (Feb. 29, 2004) – Sailors aboard the nuclear powered aircraft carrier USS Enterprise (CVN 65) “man the rails” as the carrier approaches its pier at her homeport of Naval Station Norfolk, Va. The carrier and its strike group are returning after completing a six-month deployment in support of the global war of terrorism, including Operations Iraqi Freedom and Enduring Freedom. U.S. Navy photo by Photographer’s Mate 3rd Class Sondra Howett. (RELEASED)
-In 1983, the ship ran aground near Alameda, California, due to navigation errors, and in 1986, two sailors died from chemical exposure after safety procedures were ignored.
-These events highlight both crew heroics and leadership lapses, underscoring the complexity of naval operations and the importance of rigorous safety protocols.
Was the Aircraft Carrier USS Enterprise Jinxed During the 1980s?
If you were around during the presidency of Ronald Reagan you know that the Commander-in-Chief wanted as many warships in the water as possible to match the Soviet Union’s own naval build-up. But one time Reagan probably wished one of the Navy’s best aircraft carriers would have been parked in port. In what is a scary footnote to history, the USS Enterprise hit a rocky undersea island 100 miles off the cost of San Diego in 1985.
Gash in Ship’s Hull Sprang Up During Training
People thought the worst when it happened. The Enterprise had a nuclear-powered propulsion system and that could have endangered the waters in the region, perhaps even affecting the environmental ecosystem around the small island.
The carrier was on a training mission when the accident occurred. The inside of the ship was not damaged. There were also no problems with the nuclear generator after the crash.
But the Big “E” was having problems in the 1980s, as this wasn’t the carrier’s only mishap. It had run aground near Alameda, California in 1983 after it was beset by steering problems. The incidents made everyone hold their breath as some feared that the Enterprise was a bad luck ship during the Reagan-era.
A 60-feet Long Hole Was Torn
Before the reef incident, the Enterprise was conducting a large Operational Readiness Exercise. Then the Big E ran into a feature called “Bishop Rock” – a 13-mile long submerged island. The damage was extensive to the hull tearing a hole 60 feet long. The hull was supposed to be torpedo resistant but it was no match for undersea rock. The Enterprise had four propellors and three were damaged beyond repair and the port keel was missing.
Quick Thinking By Officers and Enlisted Sailor Saved the Ship
The captain had to “counterflood” the ship to keep it from sinking. The crew quickly worked on the damage to save the carrier. They displayed excellent seamanship and teamwork to maintain ballast and keep the ship from capsizing.
Captain Robert L. Leuschner Jr. was having difficulties during the exercise before the accident. The Enterprise was going through simulated attacks and all hands were at battle stations. The navigator noticed the carrier was getting close to the submerged feature and warned the skipper about the problem. Airplanes were landing and launching.
Something Weird Was Happening that Distracted the Captain
Then something strange happened. The captain heard a report of a “gunman” that was threatening sailors below decks. This turned out to be a false alarm but this news rattled Leuschner. He had been listening intently to what he thought was going to be a huge problem and wasn’t paying attention to where the ship was heading.
The carrier then hit the undersea island and paid the price. Divers had to assess the damage and the captain was heart-stricken to learn how damaged the Enterprise was. Fortunately, the sailors were trained well for the emergency and there were no casualties and the ship didn’t sink. Plus, the nuclear reactor wasn’t hurt and that could have caused huge environmental damages not to mention radiation that could have placed the crew in danger.
The Aircraft Carrier USS Enterprise Was Having Bad Luck
The 1983 incident was also harrowing. Enterprise was returning to home port in Alameda, California after an eight-month patrol in the Indo-Pacific. It went under the Golden Gate Bridge, but its navigation was off and it missed the 400-yard-wide, 40-foot-deep ship channel. Then it ran aground on a huge sandbar and began listing to port. The Enterprise crew had to act fast as the carrier could have continued to be ensconced into the sandbar. Then it could have been stuck for good. Fortunately, after much effort the Enterprise was freed by several tugboats.
This wasn’t all of the Enterprise’s bad luck in the 1980s. In 1986, there was a deadly incident aboard the carrier. Two petty officers were killed by exposure to chemical fumes. The Navy determined they were in a “restricted area without authorization.”
Image: Creative Commons.
The captain said “the storeroom must be tested for air quality and oxygen levels and authorization papers must be signed documenting the tests before crew members can enter the room. These procedures were not followed,” he explained.
The Enterprise was somehow jinxed during the 1980s. Sometimes the crew performed admirably, other times the ship’s leadership and enlisted sailors conducted themselves questionably. The carriers nowadays are much more attuned to the potential of accidents. Navigation due to GPS is much better. But the navy can be dangerous and mistakes happen. Let’s just hope the sailors and officers are trained to the utmost of their ability to make sure nothing like the run of bad luck that happened to the Enterprise ever occurs again.
About the Author: Dr. Brent M. Eastwood
Brent M. Eastwood, PhD is the author of Don’t Turn Your Back On the World: a Conservative Foreign Policy and Humans, Machines, and Data: Future Trends in Warfare plus two other books. Brent was the founder and CEO of a tech firm that predicted world events using artificial intelligence. He served as a legislative fellow for U.S. Senator Tim Scott and advised the senator on defense and foreign policy issues. He has taught at American University, George Washington University, and George Mason University. Brent is a former U.S. Army Infantry officer. He can be followed on X @BMEastwood.
