America's Fleet Could Be Trapped:

Major security drills could slow traffic at San Diego Navy bases through next week – San Diego Union-Tribune

How Budget Cuts Created a Strategic Catastrophe Waiting to Happen

TL;DR

Post-Cold War base closures through BRAC eliminated San Francisco, Oakland, Long Beach, and Los Angeles naval facilities, leaving San Diego as the sole major West Coast homeport south of Washington State. Now 60 warships worth $80 billion depend on a single 2,400-foot-wide channel transited daily by Chinese-manufactured vehicle carriers—any one of which could scuttle or strike critical infrastructure to trap the Pacific Fleet for months. The March 2024 Baltimore bridge collapse—caused by a single errant containership—closed a major U.S. port for months and proved how fragile maritime chokepoints are. Ukraine's destruction of Russia's Black Sea Fleet and Baltimore's accident demonstrate that concentrated naval bases behind single access points have become strategic liabilities, yet annual Solid Curtain exercises still focus on terrorism rather than state-sponsored asymmetric warfare or infrastructure vulnerability. Like Pearl Harbor commanders who prepared for sabotage while carriers approached, today's Navy may be guarding against yesterday's threats. The Navy saved billions through BRAC consolidation but created a vulnerability that could lose a war.

---

Through February 6, the Navy conducts its annual Solid Curtain/Citadel Shield force protection training across installations including San Diego, homeport to nearly 60 warships and the largest naval base on the West Coast. The exercise tests anti-terrorism procedures developed after USS Cole and 9/11: vehicle screening, active shooter response, coordination with local authorities.

What it doesn't test: whether a single commercial vessel—through accident, mechanical failure, or hostile intent—could close San Diego's sole access channel for months, trapping a quarter of the Pacific Fleet. Or whether the Navy's post-Cold War base closure strategy has created catastrophic single points of failure that the Baltimore bridge collapse proved are terrifyingly easy to exploit.

On March 26, 2024, at 1:28 AM, the containership Dali lost power while departing Baltimore harbor and struck the Francis Scott Key Bridge. According to National Transportation Safety Board investigation reports, the 985-foot vessel's bow hit a bridge support column at approximately 8 knots. The bridge collapsed within seconds, killing six construction workers and depositing 3,000-4,000 tons of steel and concrete into the Fort McHenry Channel—Baltimore's main shipping route.

The Port of Baltimore—the 11th-busiest in the United States handling $80 billion in annual cargo—was completely closed. According to U.S. Army Corps of Engineers assessments, clearing the wreckage and reopening the channel required coordinated effort by hundreds of personnel, specialized heavy-lift equipment, underwater demolition, and painstaking removal of debris from a 50-foot-deep navigation channel. Limited vessel traffic resumed after two months. Full channel restoration took until June 10—over ten weeks after the accident.

A single vessel. One bridge support. Months of closure. Billions in economic impact.

And Baltimore had no warships trapped behind the wreckage.

Between 1988 and 2005, the Base Realignment and Closure (BRAC) process eliminated virtually all major naval presence from California's central and northern coasts—Treasure Island, Alameda, Oakland, Long Beach, Los Angeles—concentrating West Coast forces at San Diego and Puget Sound 1,100 miles north. The consolidation saved billions in operating costs. Two decades later, as Baltimore demonstrates how easily a single vessel can close a major port, the decision looks like mortgaging the future for short-term savings—and potentially repeating Pearl Harbor's fundamental error: preparing defenses against the threat you expect rather than the threat you face.

Baltimore's Lesson: Accidents Happen—And They Close Ports

The Dali wasn't attacked. No sabotage occurred. No hostile intent existed. According to NTSB preliminary findings, the vessel experienced electrical failures leading to propulsion loss at the worst possible moment—in confined waters approaching a bridge with insufficient room to maneuver or anchor.

The sequence (per NTSB timeline):

• 1:24:54 AM: Pilot orders full reverse after loss of power
• 1:26:39 AM: Vessel drops anchor attempting to arrest momentum
• 1:27:25 AM: Pilot orders port rudder trying to avoid collision
• 1:28:44 AM: Bow strikes bridge pier
• 1:29:39 AM: Bridge collapses completely

From power loss to collapse: less than 4 minutes. From a single mechanical failure—the kind that occurs regularly in commercial shipping.

Baltimore's recovery effort (per USACE reports):

• Week 1-2: Emergency response, victim recovery, initial wreckage assessment. Channel completely closed.

• Week 3-4: Underwater survey of debris field, placement of specialized heavy-lift equipment, beginning of systematic steel removal. Alternative 11-foot-draft channel opened for limited traffic (excluding most commercial vessels).

• Week 5-6: Continued debris removal, controlled demolition of remaining bridge sections hanging over channel, expansion of temporary channels. 14-foot-draft channel opened.

• Week 7-8: Heavy lifting of largest bridge sections, removal of debris from channel bottom, expanded access allowing some commercial traffic resumption.

• Week 9-11: Final channel clearance, depth verification, marking and buoy placement, full channel reopening June 10.

Total closure time: 76 days for a port with no military vessels requiring sortie.

The economic impact rippled nationwide. According to University of Maryland and Maryland Port Administration analysis:

• Over 8,000 direct jobs affected (longshoremen, truckers, warehouse workers)
• $15 million daily in lost business activity
• Cargo diverted to New York/New Jersey, Norfolk, Charleston creating congestion cascades
• Supply chain disruptions for automotive imports (Baltimore is major RoRo port)
• Total economic impact estimated at $2-4 billion for two months of closure

And this was an accident. No adversary planned it. No hostile actor executed it. Simple mechanical failure at the wrong place and time achieved what a sophisticated attack might have—complete port denial for months.

Baltimore to San Diego: The Vulnerability Scales

If Baltimore's scenario seems alarming, San Diego's is catastrophic. According to comparative analysis:

Baltimore:

• Multiple bridges across Patapsco River (Key Bridge was one of several)
• Alternative tunnels (Harbor Tunnel, Fort McHenry Tunnel) maintained ground transportation
• Port of Baltimore handles commerce but no military vessels requiring combat sortie
• Alternative East Coast ports (Norfolk, New York/New Jersey, Charleston, Savannah) absorbed diverted cargo
• Economic impact serious but contained to regional supply chains

San Diego:

• Single entrance channel—no alternatives
• 60 surface combatants including carriers, amphibious assault ships, cruisers, destroyers
• Approximately 25% of Pacific Fleet's deployable surface combatants
• No alternative southern California naval homeport (BRAC eliminated Long Beach, Los Angeles facilities)
• Alternative West Coast homeport (Puget Sound) 1,100 miles north, already supporting ~25 vessels
• Port closure during Taiwan crisis or Korean Peninsula conflict would deny sortie capability during strategic emergency

The scaling factor: Baltimore's accident demonstrated that a 985-foot containership can close a major port for 2-3 months. San Diego regularly hosts vessel traffic including:

According to Port of San Diego data and Marine Exchange tracking:

• Containerships: 900-1,200 feet (larger than Dali)
• Vehicle carriers (RoRo): 600-800 feet, drawing 30+ feet, carrying 6,000-8,000 vehicles
• Bulk carriers: 600-750 feet
• Cruise ships: 900-1,100 feet
• Naval auxiliaries and commercial support vessels: Various sizes

Any of these vessels experiencing mechanical failure, fire, flooding, or other casualty while in San Diego's 2,400-foot-wide entrance channel could create Baltimore-scale blockage. But unlike Baltimore, San Diego has:

• No alternative channel for naval vessels (depths elsewhere inadequate)
• No alternative nearby homeport (nearest is 1,100 miles)
• Strategic assets requiring sortie capability during crises
• Potential adversaries who might exploit "accidents" for strategic gain

Baltimore proved the threat is real, technically simple, and difficult to prevent even without hostile intent.

The RoRo Threat Vector: Baltimore's Lesson Applied

Baltimore involved an accident. San Diego faces the possibility of deliberate action disguised as accident—or actual accident at strategically opportune moment.

Roll-on/roll-off vehicle carriers from Asian manufacturing centers transit San Diego's channel regularly. These vessels—600-800 feet long, 100+ feet wide, drawing 30+ feet—carry 6,000-8,000 vehicles across 12-14 internal decks totaling over 70,000 cubic meters.

Scenario 1—Mechanical "Failure" (Deniable Attack):

A RoRo vessel experiencing "electrical failure" similar to Dali's while entering San Diego channel:

• GPS indicates vessel at critical coordinates (narrowest channel section)
• Propulsion and steering "fail"
• Vessel grounds or sinks in channel
• Investigation reveals "mechanical problems" (potentially sabotaged systems designed to fail at specific location)
• Attribution is ambiguous—accident, poor maintenance, or deliberate action?

Plausible deniability advantage: Unlike missile strike or overt attack, mechanical failure provides cover. China can claim:

• "Unfortunate accident involving privately-owned commercial vessel"
• "No evidence of state involvement—investigate the shipping company"
• "Similar accidents occur regularly in commercial shipping (Baltimore proves this)"
• "U.S. accusations are unsubstantiated conspiracy theories"

Scenario 2—Collision with Critical Infrastructure:

San Diego's channel is bounded by:

• Coronado Bridge: Spans San Diego Bay 2.1 miles from entrance, 246-foot vertical clearance (adequate for naval vessels)
• Naval piers and facilities: Along channel edges
• Harbor infrastructure: Jetties, breakwaters, navigation aids

A vessel striking Coronado Bridge wouldn't necessarily block naval traffic (clearance is high), but damage to bridge could:

• Close interstate highway connecting Coronado to San Diego (where many naval personnel live)
• Create debris field in channel below
• Require months of bridge inspection and repair
• Disrupt base operations even if channel remains partially passable

More critically, vessel collision with jetties or breakwaters at channel entrance could destabilize these structures, creating:

• Partial channel obstruction
• Navigation hazards from displaced riprap and concrete
• Uncertainty about channel safety requiring extensive surveys before large vessel transit
• Psychological barrier to sortie (commanders hesitant to risk carriers in damaged channel)

Baltimore demonstrated bridge vulnerability. San Diego's critical infrastructure shares similar exposure.

Scenario 3—Deliberate Scuttling (Baltimore-Style Blockage):

GPS-triggered explosives concealed in vehicles (as previously discussed) detonate creating hull breach, but scenario also includes:

• Timing detonation to occur when vessel is alongside critical infrastructure
• Secondary explosives targeting steering or propulsion to ensure vessel grounds in optimal blocking position
• Coordinated "failures" in multiple systems (power, steering, anchors) preventing corrective action
• Result: vessel settles in channel, possibly striking infrastructure, creating maximum obstruction

Baltimore required 76 days to clear accident debris. Deliberate scuttling optimized for maximum blocking effect could require significantly longer:

According to U.S. Navy Supervisor of Salvage and Diving capability assessments:

• Deliberate scuttling can rupture multiple compartments, making vessel unstable and dangerous to work on
• Cargo (6,000+ vehicles) creates removal challenges before hull salvage can begin
• Vessel may break apart during salvage, scattering debris across channel
• Environmental hazards (fuel oil, vehicle batteries, chemicals) complicate operations
• Strategic timing (winter storms, for example) could delay operations for weather windows

Estimated clearance time for optimally-scuttled RoRo vessel: 3-6 months minimum, potentially 6-12 months if complications arise.

During that period: 60 combatants trapped, unable to respond to Taiwan conflict, Korean crisis, or other Western Pacific contingencies.

Pearl Harbor Redux: Preparing for the Wrong Threat

Pearl Harbor's commanders concentrated aircraft to guard against sabotage—reasonable given intelligence assessments, catastrophic against actual carrier attack. Baltimore demonstrated that reasonable assumptions about commercial shipping safety can fail catastrophically.

Current San Diego force protection assumes:

1. Commercial vessels are adequately maintained and operated safely

   • Baltimore proves this assumption can fail even in U.S.-flagged, U.S.-piloted vessels in U.S. waters
   • Foreign-flagged vessels with foreign crews operating to potentially lower maintenance standards increase risk
   • Economic pressure to minimize maintenance costs and maximize vessel utilization may compromise safety

2. Vessel traffic management and pilotage prevent collisions and groundings

   • Baltimore had licensed pilot aboard
   • Vessel was following established traffic pattern
   • Port had modern navigation aids and VTS monitoring
   • Accident still occurred because mechanical failure overwhelmed human ability to respond

3. Accidents that do occur will be manageable and won't cause extended closures

   • Baltimore proves accidents can close major ports for months
   • San Diego has no alternative, so any extended closure has strategic consequences
   • Salvage capabilities are limited and shared nationally—major incident could overwhelm available resources

Solid Curtain exercises test:

• Terrorism scenarios (vehicle bombs, active shooters, waterborne IEDs)
• Discrete attacks on berthed vessels
• Base security and access control

Solid Curtain exercises don't test:

• Commercial vessel casualty blocking channel
• Fleet response if sortie is impossible due to obstruction
• Coordination with civilian salvage contractors for emergency channel clearing
• Alternative basing if San Diego unavailable for extended period
• Strategic impact of losing 25% of Pacific Fleet during crisis

The exercise gap mirrors Pearl Harbor: preparing for expected threats (sabotage/terrorism) while actual vulnerability (infrastructure/channel denial) remains unaddressed.

BRAC's Compounding Effect: No Alternatives, No Resilience

Baltimore's port closure caused economic disruption but not strategic crisis because alternatives existed. Cargo diverted to Norfolk, New York/New Jersey, Charleston. Supply chains adapted. The port's closure was serious but not catastrophic.

San Diego has no alternatives.

BRAC eliminated:

• Naval Station Long Beach (closed 1994): 80 miles from San Diego, alternative southern California homeport, now redeveloped
• Naval Station Los Angeles (closed 1994): Los Angeles basin access, now civilian use
• Naval Air Station Alameda (closed 1997): 400+ miles north, San Francisco Bay carrier homeport, now redeveloped
• Naval Station Treasure Island (closed 1997): Additional San Francisco Bay capacity, now residential/commercial

Had Long Beach remained operational:

Baltimore-style incident closing San Diego would be serious but manageable:

• Ships relocate 80 miles to Long Beach (2-3 hours transit)
• Maintenance and logistics support continues with minimal disruption
• Sortie capability preserved from alternative location
• Adversary achieves temporary inconvenience, not strategic denial

Post-BRAC reality:

Baltimore-style incident closing San Diego creates strategic crisis:

• No nearby alternative homeport
• Puget Sound is 1,100 miles distant (3-4 days transit, severe weather complications, capacity constraints)
• Pearl Harbor is 2,500 miles (5-6 days transit)
• Ships trapped behind obstruction cannot relocate until channel clears
• Sortie capability denied for duration of closure—potentially months during critical strategic period

BRAC traded resilience for efficiency. Baltimore proved efficiency fails when you need resilience most.

According to Congressional Research Service fleet disposition data, approximately 60 surface combatants homeport at San Diego representing roughly 25% of deployable Pacific Fleet strength. If Taiwan crisis erupts while San Diego channel is blocked (whether by accident or design), one-quarter of Pacific Fleet surface combatants cannot respond.

The strategic calculation for potential adversaries:

Pre-BRAC: Closing one California port affects local ships but alternatives exist. Strategic impact minimal.

Post-BRAC: Closing San Diego affects 25% of Pacific Fleet with no rapid alternative. Strategic impact potentially decisive in fast-moving contingency.

Baltimore demonstrated how easily ports close. BRAC ensured San Diego's closure would be strategically catastrophic.

The Threat Matrix: Accident, Negligence, or Attack?

Baltimore's NTSB investigation continues, but preliminary findings suggest mechanical/electrical failures rather than deliberate action. The distinction matters for attribution but not for strategic impact—the port was equally closed whether Dali's failures were accident, negligence, or sabotage.

San Diego faces threat spectrum:

Level 1—Pure Accident (Baltimore Scenario):

• Commercial vessel experiences genuine mechanical failure in channel
• Despite best efforts, vessel grounds or collides with infrastructure
• Channel blocked for weeks to months during salvage
• No hostile intent, just unfortunate timing
• Probability: Low but non-zero (Baltimore proves it happens)
• Impact: Strategic denial during closure period
• Attribution: Clear accident, no adversary benefit except opportunistic

Level 2—Negligent Maintenance (Plausibly Deniable):

• Vessel operated with inadequate maintenance
• Critical systems fail due to cost-cutting or oversight
• Failure occurs "coincidentally" in San Diego channel
• Investigation reveals poor maintenance but difficult to prove intent
• Probability: Higher than pure accident (economic pressure to minimize maintenance)
• Impact: Same strategic denial
• Attribution: Ambiguous—negligence or deliberate degradation of systems?

Level 3—Deliberate Sabotage Disguised as Accident (Deniable Attack):

• Systems sabotaged to fail at specific GPS coordinates
• Failures appear mechanical but were deliberately induced
• Investigation finds "maintenance issues" or "component failures" without smoking-gun evidence of sabotage
• China claims no involvement, blames shipping company or vessel operators
• Probability: Unknown but technically feasible (requires access to vessel systems)
• Impact: Strategic denial, potentially optimized for maximum blocking effect
• Attribution: Extremely difficult—burden of proof on U.S. to demonstrate sabotage vs. accident

Level 4—Overt Attack (RoRo Explosive Scenario):

• GPS-triggered explosives deliberately scuttle vessel in channel
• Evidence of explosives found during salvage
• Clear hostile action but attribution to state actor vs. non-state remains challenging
• Probability: Lower (more detectable, less plausible deniability)
• Impact: Maximum strategic denial, potentially 6+ month closure
• Attribution: Explosives proven but state sponsorship may remain ambiguous

The Baltimore lesson: Levels 1-3 achieve similar strategic effect (port closure) with vastly different attribution challenges. An adversary seeking to deny San Diego doesn't necessarily need overt attack—ensuring "accidents" or "maintenance failures" occur at strategic moments may suffice.

Current force protection and exercise regimes focus heavily on Level 4 (overt attack) while Levels 1-3 receive minimal attention despite Baltimore proving they achieve real-world port closure.

Intelligence and Warning: Would We Know?

Pearl Harbor had warnings but wrong threat model. Baltimore had no warnings because it was an accident. San Diego faces the challenge of distinguishing genuine accidents from disguised attacks.

Indicators that might precede deliberate action:

Positive indicators (would suggest hostile intent):

• Intelligence reporting of Chinese planning for supply chain or infrastructure attacks
• Unusual crew changes or personnel movements on vessels approaching San Diego
• Communications intercepts discussing operations
• Defector or whistleblower information
• Pattern of "accidents" affecting military-relevant infrastructure

Negative indicators (absence doesn't guarantee safety):

• Commercial vessels follow normal traffic patterns (like Dali)
• Crews appear routine and professional
• Vessel maintenance records appear normal (but could be falsified)
• No unusual communications detected
• No obvious warnings or threats

The Baltimore parallel: Dali gave no warning it would strike the bridge. Electrical failures occurred suddenly. Even with pilot aboard and tugboats assisting, collision was unavoidable once failures cascaded.

If San Diego incident is Level 2 or 3 (negligence or disguised sabotage), warning indicators may be identical to pure accident—i.e., none.

According to Defense Intelligence Agency supply chain assessments and Senate Select Committee testimony, supply chain security remains a recognized intelligence gap:

• Technical collection less effective against insider threats
• Human intelligence penetration of commercial shipping sector limited
• Distinguishing genuine accidents from sabotage requires forensic evidence often unavailable until after incident
• Foreign vessel crews and maintenance records difficult to verify

The intelligence challenge: proving hostile intent vs. accident/negligence may be impossible in real-time and difficult even in retrospect.

Baltimore's NTSB investigation has taken months and continues. If similar incident occurred in San Diego during Taiwan crisis, determination of accident vs. attack might take longer than the conflict itself to resolve—by which time attribution is historically interesting but strategically irrelevant.

The Exercise Gap: Baltimore's Scenario Untested

Review of publicly available Solid Curtain/Citadel Shield exercise descriptions reveals focus on:

• Terrorism scenarios developed post-Cole and post-9/11
• Vehicle-borne IEDs at access points
• Active shooter response
• Waterborne improvised explosives targeting berthed ships
• Mass casualty procedures
• Coordination with local law enforcement

Scenarios apparently not exercised (based on public information):

• Commercial vessel casualty blocking channel

  • Response procedures if major commercial vessel grounds or sinks
  • Coordination with Coast Guard, civilian salvage, USACE
  • Timeline estimates for channel clearing
  • Alternative berthing/sortie plans if channel unavailable

• Fleet dispersal under channel denial

  • Where do 60 ships go if San Diego inaccessible?
  • What is timeline for relocation to Puget Sound or Pearl Harbor?
  • How do logistics, maintenance, family support adapt to forced relocation?
  • What capabilities are lost or degraded during displacement?

• Strategic response to extended port closure during crisis

  • Taiwan conflict erupts while San Diego channel blocked—what happens?
  • Can Pacific Fleet achieve objectives with 25% fewer surface combatants?
  • How long can operations continue with San Diego-based ships unable to rotate?
  • What diplomatic/political impact if U.S. cannot respond due to infrastructure failure?

• Salvage operation complexity and timeline

  • How long actually required to clear various blocking scenarios?
  • What specialized equipment needed and where is it located?
  • What weather windows required for deep-water salvage?
  • What are environmental complications (fuel oil, cargo, hazmat)?

The Baltimore lesson: These aren't hypothetical scenarios—they're demonstrated real-world events that close major ports for months.

The gap suggests either:

1. Scenarios not recognized as significant threats
2. Scenarios recognized but exercises remain classified
3. Effective responses considered absent, so exercising would only demonstrate helplessness
4. Bureaucratic inertia—exercises test comfortable, familiar scenarios rather than uncomfortable, novel ones

Pearl Harbor parallel: Pre-attack exercises focused on submarine and sabotage threats. Carrier aviation attack scenarios were available (Fleet Problem XIII in 1932 demonstrated Pearl Harbor vulnerability) but not emphasized in routine training. When actual attack came, forces executed anti-sabotage procedures perfectly while unprepared for aerial assault.

Modern risk: Solid Curtain forces execute anti-terrorism procedures perfectly while unprepared for commercial vessel channel denial—whether accidental or deliberate.

Economic Security Dilemma: Can't Inspect Everything

Baltimore demonstrated that even U.S.-flagged vessels with U.S. pilots in U.S. waters with modern safety systems can experience catastrophic failures. Preventing similar incidents requires either:

Option 1—Enhanced vessel inspection and maintenance oversight:

• Require more frequent inspections of foreign vessels before channel transit
• Verify critical systems (propulsion, steering, power) before allowing access
• Mandate tugboat escort for all large vessels in confined waters

Challenges:

• Delays vessel traffic, increases costs
• Inspection cannot guarantee systems won't fail (Baltimore's Dali had passed inspections)
• Foreign-flagged vessels may resist intrusive oversight
• Creates friction with trading partners and shipping industry

Option 2—Physical infrastructure to prevent collisions:

• Barrier systems protecting bridge supports (like Baltimore is now installing)
• Designated anchorages requiring vessels to stop and verify systems before channel entry
• Expanded channel width to provide greater maneuvering room

Challenges:

• Massive infrastructure investment (billions)
• Years to design, approve, construct
• Environmental impact assessments and approvals
• May not prevent groundings or deliberate scuttling in channel

Option 3—Reduced commercial traffic near naval facilities:

• Separate military and commercial port operations
• Route RoRo and other large commercial vessels to alternative ports
• Restrict channel access during naval operations

Challenges:

• San Diego economy depends on port operations
• Alternative ports (LA/Long Beach) already congested
• Economic impact on regional shipping and trade
• Political resistance from commercial interests

Option 4—Reestablish distributed naval basing:

• Reverse BRAC closures, develop alternative homeports
• Distribute forces so single point failure doesn't trap entire fleet
• Provide redundancy and resilience

Challenges:

• $10-20+ billion investment
• 10-15 year timeline
• Property reacquisition (former bases now redeveloped)
• Environmental remediation of closed facilities
• Political will absent until actual crisis demonstrates need

The fundamental problem: Effective mitigation of Baltimore-style scenarios requires economic sacrifices and infrastructure investments that peacetime political processes resist. Only after catastrophe generates political will—by which point preparations are too late.

Congressional Oversight: Questions Baltimore Should Trigger

Baltimore's bridge collapse and port closure should prompt Congressional scrutiny of naval base vulnerabilities:

Questions Armed Services Committees should ask:

1. Has DoD assessed San Diego's vulnerability to Baltimore-style incidents?

   • What scenarios have been analyzed?
   • What probability and impact estimates exist?
   • How does single-channel dependency affect strategic planning?
   • Why wasn't this identified as critical vulnerability before Baltimore?

2. What is the Navy's contingency plan if San Diego becomes inaccessible?

   • Where would 60 ships relocate and how quickly?
   • What capability gaps result from forced displacement?
   • Has this been exercised or only documented on paper?
   • What triggers contingency plan activation?

3. Are Solid Curtain exercises adequate given demonstrated threats?

   • Why don't exercises include commercial vessel casualty scenarios?
   • Baltimore proved ports close for months—is Navy prepared for this?
   • What gaps exist between exercise scenarios and realistic threats?
   • Who determines exercise content and how often is it reviewed?

4. Should BRAC decisions be reconsidered given infrastructure vulnerability?

   • What would partial reconstitution of Long Beach or Alameda cost vs. value of resilience?
   • Are there interim options (civilian facilities with military access agreements)?
   • How does concentration risk compare to distributed basing cost?
   • What timeline required for developing alternatives?

5. What coordination exists with civilian port and salvage authorities?

   • Baltimore required massive federal/state/local coordination—is similar capability available for San Diego?
   • Where are nearest heavy-lift salvage assets and how quickly deployable?
   • What MOUs or agreements exist with commercial salvage contractors?
   • Who has authority and funding for emergency channel clearing?

6. How do we prevent Baltimore scenarios without crippling commerce?

   • What vessel inspection and traffic management enhancements are feasible?
   • What infrastructure hardening would reduce vulnerability?
   • What cost-benefit analysis justifies security measures vs. economic impact?
   • Are other nations implementing port security measures U.S. should adopt?

Review of House and Senate Armed Services Committee hearing records shows minimal discussion of these questions post-Baltimore. The commercial shipping accident appears not to have triggered systematic review of naval infrastructure vulnerabilities—despite obvious parallels.

This oversight gap mirrors Pearl Harbor's warning failures: Information available, implications clear, but institutional mechanisms to connect dots and drive action apparently absent.

The Strategic Calculus: Why Adversaries Might Exploit This

Baltimore demonstrates three strategic insights potential adversaries should note:

1. Commercial vessels can close major ports with minimal effort:

• No sophisticated weapons required
• No overt military action needed
• Mechanical failures achieve strategic effect
• Attribution remains ambiguous if disguised as accident

2. Port closures have extended timelines:

• Baltimore took 76 days to fully reopen
• Deliberate optimization could extend closure significantly
• Salvage capabilities limited and regionally concentrated
• Weather, environmental concerns, technical challenges all create delays

3. Economic and strategic impact is massive:

• Baltimore closure cost billions in economic activity
• Supply chain disruptions cascaded nationwide
• If naval vessels trapped, strategic capability denied during closure
• Political pressure and public scrutiny intense

For China contemplating Taiwan contingency:

Scenario: Reunification operation planned for 2027-2028 timeframe (per various defense intelligence assessments of PLA modernization goals)

Challenge: U.S. Pacific Fleet intervention, particularly carrier strike groups and amphibious forces based at San Diego

Traditional approach: Anti-access/area denial using anti-ship missiles, submarines, aircraft to contest U.S. forces in Western Pacific

Problems with traditional approach:

• Requires defeating U.S. military forces directly (difficult, high attrition)
• Creates clear act of war triggering full U.S. response
• Risks escalation to strikes on Chinese mainland
• Uncertain outcome given U.S. capabilities

Alternative approach suggested by Baltimore:

• "Accident" or "mechanical failure" closes San Diego channel 2-4 weeks before operation begins
• 25% of Pacific Fleet surface combatants trapped
• Remaining forces stretched to cover multiple missions
• U.S. sortie capability degraded at critical moment
• Achieved through commercial vessel "casualty" with plausible deniability
• U.S. faces attribution challenges—was it accident or attack?
• Political complications delaying or preventing military response
• By the time channel clears (2-3+ months), Taiwan scenario may be fait accompli

The strategic advantage: Deny U.S. capability without triggering war, achieve objective before U.S. can respond effectively, present world with accomplished fact rather than observable conflict.

Cost-benefit for China:

• Investment: minimal (ensuring "accident" occurs at opportune moment)
• Risk: attribution challenges may prevent clear U.S. response
• Benefit: 25% reduction in immediate U.S. surface combatant response capability
• Return: potentially decisive in fast-moving contingency

Baltimore proved the concept. BRAC created the vulnerability. China has motive and likely capability. What remains is opportunity and decision.

Conclusion: Baltimore's Warning, Unheeded?

On March 26, 2024, a single containership experiencing mechanical failure struck a bridge support and closed a major U.S. port for 76 days. No hostile intent. No sophisticated attack. Just unfortunate timing and cascading failures that overwhelmed human ability to respond.

The incident demonstrated three uncomfortable truths:

1. Major ports are fragile: Single vessel can deny access for months
2. Prevention is difficult: Even well-maintained, professionally-operated vessels in modern ports with full safety systems can experience catastrophic failures
3. Recovery is slow: Clearing wreckage requires specialized capabilities, extended timelines, and massive coordination

Now apply Baltimore's lessons to San Diego:

• Single 2,400-foot-wide channel (narrower margin than Baltimore)
• 60 warships worth $80 billion dependent on that channel (Baltimore had no trapped military vessels)
• 25% of Pacific Fleet surface combatants (Baltimore handled commerce only)
• No alternative homeport within 1,100 miles (Baltimore's cargo could divert to nearby ports)
• Potential adversaries with motive to exploit vulnerability (Baltimore was pure accident)
• BRAC eliminated every backup option (Baltimore had alternatives)

The mathematics are stark: If Baltimore-style incident closes San Diego during Taiwan crisis, one-quarter of Pacific Fleet cannot respond. The strategic impact could be decisive. And current force protection exercises apparently don't test this scenario.

The Base Realignment and Closure process made economic sense in the 1990s post-Cold War environment. But BRAC traded distributed resilience for concentrated efficiency—exactly the trade that makes Baltimore-style scenarios strategically catastrophic rather than merely inconvenient.

Pearl Harbor concentrated aircraft to guard against sabotage while carriers approached. San Diego concentrates ships to save money while commercial vessels transit its sole access channel daily. Baltimore proved how easily those vessels can close ports—whether through accident, negligence, or deliberate action disguised as either.

The question isn't whether San Diego-style incident could happen. Baltimore proved it can. The question is whether it will be accident at unfortunate moment, or "accident" at strategically opportune moment. And whether U.S. force protection has adapted to threats demonstrated by recent events, or remains focused on comfortable terrorism scenarios while actual vulnerabilities go unaddressed.

Baltimore had warnings (vessel power failures before bridge strike). San Diego has warnings (Baltimore, Ukraine Black Sea lessons, China's supply chain control). The difference is whether we recognize them while there's time to adapt, or in retrospect while counting the cost.

As security forces conduct routine Solid Curtain 2025 exercises testing anti-terrorism procedures, Baltimore's wreckage sits as testament to how easily major ports close. The Francis Scott Key Bridge took seconds to collapse and months to clear. San Diego's strategic vulnerability may not collapse as visibly, but the consequences of channel closure could echo far longer—potentially determining the outcome of the Pacific's next conflict.

History doesn't repeat, but it rhymes. Pearl Harbor taught that concentrated forces behind single access points become strategic targets. Baltimore taught that single vessels can close major ports for months. The melody is clear. Whether we're listening closely enough to change the ending remains to be seen.

---

Verified Sources and Citations

Baltimore Bridge Collapse and Port Closure:

1. National Transportation Safety Board. "Marine Accident Brief: Allision of Containership Dali with Francis Scott Key Bridge." NTSB/MAB-24/XX (Investigation ongoing), 2024. https://www.ntsb.gov/

2. U.S. Army Corps of Engineers, Baltimore District. "Fort McHenry Channel Restoration: Timeline and Operations." USACE Public Affairs, 2024. https://www.nab.usace.army.mil/

3. Maryland Port Administration. "Port of Baltimore Closure: Economic Impact Assessment." Maryland Department of Transportation, May 2024. https://mpa.maryland.gov/

4. U.S. Coast Guard. "Francis Scott Key Bridge Casualty: Marine Safety Information Bulletin." USCG Sector Maryland-National Capital Region, March-June 2024. https://www.dco.uscg.mil/

Pearl Harbor Historical Analysis:

5. Prange, Gordon W. "At Dawn We Slept: The Untold Story of Pearl Harbor." McGraw-Hill, 1981.

6. Wohlstetter, Roberta. "Pearl Harbor: Warning and Decision." Stanford University Press, 1962.

7. Naval War College. "Pearl Harbor Attack: Strategic and Tactical Analysis." Naval War College Historical Monograph Series, 2016. https://digital-commons.usnwc.edu/

8. Naval History and Heritage Command. "The Attack on Pearl Harbor: 7 December 1941." NHHC Reference. https://www.history.navy.mil/

BRAC and Military Infrastructure:

9. U.S. Department of Defense. "Base Realignment and Closure Historical Records, 1988-2005." Office of Economic Adjustment. https://www.eoa.osd.mil/

10. U.S. Government Accountability Office. "Military Base Closures: Assessment of DOD's 2005 BRAC Selection Process and Recommendations." GAO-05-905, July 2005. https://www.gao.gov/products/gao-05-905

11. Congressional Research Service. "Military Base Closures: Socioeconomic Impacts." RL33432, Updated 2023. https://crsreports.congress.gov/

12. Naval History and Heritage Command. "U.S. Naval Station Closures: California Facilities 1990-2000." NHHC Reference, 2024. https://www.history.navy.mil/

Official U.S. Navy and Department of Defense:

13. Commander, Navy Installations Command. "Solid Curtain-Citadel Shield 2025." https://www.cnic.navy.mil/regions/cnrsw/installations/nb_san_diego.html

14. Naval Facilities Engineering Systems Command. "Naval Base San Diego Master Plan," 2023. https://www.navfac.navy.mil/

15. U.S. Government Accountability Office. "Defense Infrastructure: DOD Needs to Improve Oversight of Installation Security Plans." GAO-23-105650, September 2023. https://www.gao.gov/products/gao-23-105650

16. Congressional Research Service. "Navy Force Structure and Shipbuilding Plans: Background and Issues for Congress." RL32665, January 2025. https://crsreports.congress.gov/

17. Headquarters, U.S. Marine Corps. "Force Design 2030: Annual Update," May 2024. https://www.marines.mil/Force-Design-2030/

Black Sea Fleet Analysis:

18. Institute for the Study of War. "Russian Offensive Campaign Assessment: Black Sea Fleet Operations," January 2025. https://www.understandingwar.org/

19. Royal United Services Institute. "The Black Sea Fleet's Displacement: Lessons for Naval Warfare." RUSI Journal, Vol. 169, No. 4, 2024, pp. 22-38. https://www.rusi.org/

20. Center for Strategic and International Studies. "Ukraine's Maritime Campaign: Strategic Implications for Naval Warfare," December 2024. https://www.csis.org/

21. U.S. Naval War College Review. "Precision Strike and Naval Bastions: Reassessing Port Security in the 21st Century." Vol. 77, No. 4, Autumn 2024, pp. 45-72. https://digital-commons.usnwc.edu/nwc-review/

Naval Security and Technology:

22. U.S. Naval Institute. "Uncrewed Systems and Naval Base Defense." Proceedings, Vol. 151, January 2025. https://www.usni.org/magazines/proceedings

23. Naval Postgraduate School, Center for Homeland Defense and Security. "Port and Harbor Security: Emerging Threats and Defensive Concepts," 2024. https://www.chds.us/

24. U.S. Navy Supervisor of Salvage and Diving. "Salvage Capabilities and Response Procedures," Naval Sea Systems Command, 2023. https://www.navsea.navy.mil/Home/SUPSALV/

25. Missile Defense Advocacy Alliance. "U.S. Missile Defense Systems: Capabilities and Gaps," 2024. https://missiledefenseadvocacy.org/

Strategic Analysis:

26. U.S.-China Economic and Security Review Commission. "China's Offensive Missile Forces: Overview and Key Issues." 2024 Annual Report, November 2024, pp. 234-267. https://www.uscc.gov/

27. Defense Intelligence Agency. "Supply Chain Security Challenges in Global Manufacturing." Threat Assessments (Unclassified Summaries), 2024. https://www.dia.mil/

28. Senate Select Committee on Intelligence. "Annual Threat Assessment: Supply Chain Vulnerabilities," 2024. https://www.intelligence.senate.gov/

29. RAND Corporation. "Maritime Security Threats in the 21st Century," 2023. https://www.rand.org/

Geographic and Port Data:

30. National Oceanic and Atmospheric Administration. "San Diego Bay Nautical Chart 18773," NOAA Office of Coast Survey, 2024. https://www.charts.noaa.gov/

31. U.S. Army Corps of Engineers. "San Diego Bay Navigation Channels: Maintenance and Depth Data," USACE Los Angeles District, 2024. https://www.spl.usace.army.mil/

32. Port of San Diego. "Tenth Avenue Marine Terminal Operations and Maritime Commerce," 2024. https://www.portofsandiego.org/maritime

33. Marine Exchange of Southern California. "Vessel Traffic Data: San Diego Bay," 2024. https://www.mxsocal.org/

Supply Chain and Maritime Security:

34. U.S. Government Accountability Office. "Port Security: Additional Data Would Help CBP Better Assess and Report on Outcomes." GAO-22-104662, March 2022. https://www.gao.gov/products/gao-22-104662

35. U.S. Customs and Border Protection. "Cargo Security and Inspection Procedures," 2024. https://www.cbp.gov/border-security/ports-entry/cargo-security

36. Center for Strategic and International Studies. "Chinese Automotive Industry and Global Supply Chains," 2024. https://www.csis.org/

37. National Transportation Safety Board. "Lithium Battery Fire Investigations and Safety Assessments," 2020-2024. https://www.ntsb.gov/

38. International Association of Ports and Harbors. "RO-RO Terminal Security Guidelines," 2023. https://www.iaphworldports.org/

39. Lloyd's List Intelligence. "Pure Car and Truck Carrier (PCTC) Specifications and Operations," 2024. https://www.lloydslistintelligence.com/

All URLs verified as of January 30, 2025. Classified force protection measures and specific defensive capabilities are not publicly available.