LLMpediaThe first transparent, open encyclopedia generated by LLMs

USS Miami (SSN-755) fire

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Expansion Funnel Raw 54 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted54
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
USS Miami (SSN-755) fire
Ship nameUSS Miami (SSN-755)
Ship namesakeMiami, Florida
BuilderElectric Boat, Groton, Connecticut
OperatorUnited States Navy
ClassLos Angeles-class submarine
Ordered30 November 1979
Laid down5 May 1986
Launched23 August 1988
Commissioned20 January 1990
Decommissioned28 March 2014
FateDecommissioned and scrapped (Puget Sound Naval Shipyard)

USS Miami (SSN-755) fire USS Miami (SSN-755) fire was a major peacetime incident aboard a Los Angeles-class submarine berthed at Naval Station Bremerton in Bremerton, Washington during 2012 that resulted from arson and produced extensive damage, extensive repair considerations, and significant legal action. The event drew attention from the United States Navy, media outlets including The New York Times and CNN, congressional oversight, and naval safety organizations, and it influenced submarine force maintenance policy and personnel discipline.

Background and specifications

USS Miami was a Los Angeles-class submarine—one of the attack submarine class vessels designed to operate in anti-submarine warfare and intelligence roles for the United States Navy. Built by Electric Boat in Groton, Connecticut, Miami was commissioned in 1990 and assigned to Submarine Squadron 11 and Submarine Group operations in the Pacific Fleet; she deployed to regions including the Western Pacific and supported operations connected to the Persian Gulf and Operation Desert Storm. The submarine displaced about 6,900 tons submerged, was powered by a S6G reactor producing steam-driven turbines, carried torpedoes and Tomahawk cruise missiles in later-configured boats, and employed advanced sonar suites such as the BQQ-5 and fire-control systems used by contemporaneous Los Angeles-class boats. USS Miami’s crewing, maintenance, and overhaul cycles involved facilities like the Puget Sound Naval Shipyard and scheduling coordinated with the Navy Board of Inspection and Survey protocols.

2012 arson and fire incident

On 23 May 2012, while moored at Naval Station Bremerton undergoing an engineered overhaul process, a deliberate act of arson initiated a fire aboard the surfaced submarine. The blaze originated in a berthing area and rapidly produced smoke and heat that reached compartments containing auxiliary systems; responding units included Bremerton Fire Department, Naval Base Kitsap emergency teams, and shipboard firefighting parties drawn from Miami’s crew and nearby vessels. Media coverage by organizations such as The Seattle Times, NPR, and Fox News chronicled the firefighting response, while the United States Navy Criminal Investigative Service (NCIS) launched an investigation. The incident involved coordination with local law enforcement including the Kitsap County Sheriff's Office and drew statements from senior officials in Navy Region Northwest and Chief of Naval Operations staff.

Damage assessment and repair decision

Initial assessments estimated extensive damage to internal systems, habitability spaces, and hull coatings, prompting technical surveys by Naval Sea Systems Command (NAVSEA) engineers, Puget Sound Naval Shipyard evaluators, and classification societies consulted by the Navy. Inspection teams cataloged damage to electrical distribution, environmental control systems, and noise-mitigation features crucial to acoustic stealth in submarine warfare. Cost estimates for restoration were weighed against remaining service life metrics, lifecycle cost projections used by the Department of the Navy, and procurement considerations including forthcoming Virginia-class submarine delivery schedules and constrained Defense budget allocations debated in United States Congress committees. After deliberation, Navy leadership concluded that repair costs and timetable impacts rendered full restoration impractical, leading to a decision to decommission the vessel rather than return Miami to frontline service.

NCIS and local prosecutors pursued a criminal investigation that identified a shipyard worker as the arson suspect. The case involved coordination among Kitsap County Prosecutor offices, federal prosecutors, and defense counsel in the United States District Court system when charges were considered; proceedings referenced statutes under the United States Code concerning destruction of government property and arson. Evidence included witness statements from crew members, surveillance reviewed by Bremerton Police Department, and forensic examinations of fire patterns by specialists from NAVSEA and independent fire investigators. The accused faced court-martial-style civilian trials and sentencing in state court; outcomes included convictions, incarceration, restitution orders aimed at offsetting repair costs, and administrative separations affecting shipyard employment. The legal aftermath also prompted internal discipline within Naval Sea Systems Command oversight offices and review boards addressing contractor access and security clearance protocols.

Aftermath and decommissioning

Following the decision to retire USS Miami, formal decommissioning actions were completed in 2014 at Puget Sound Naval Shipyard with the vessel struck from the Naval Vessel Register. Decommissioning involved demilitarization processes consistent with Navy policy, defueling of the S6G reactor and disposition of nuclear materials coordinated with the Naval Nuclear Propulsion Program led by the United States Navy and the Department of Energy partners. Hull disposal and recycling were conducted via the Nuclear Ship and Submarine Recycling Program at Puget Sound, with salvage tasks integrated into broader shipbreaking efforts overseen by NAVSEA. The retirement reduced the count of active Los Angeles-class submarines and accelerated force structure planning involving transfers to Submarine Group units and adjustments to Pacific Fleet operational readiness.

Operational and safety implications

The Miami incident prompted reassessments of shipyard security, contractor vetting, and in-port submarine fire-fighting readiness across commands including Naval Sea Systems Command, Commander, Navy Installations Command, and Navy Region Northwest. Recommendations from internal reviews influenced policy updates to access control at Naval Shipyards, shipboard damage-control training promulgated by Chief of Naval Operations directives, and coordination protocols between civilian fire agencies and Navy emergency response teams. The event was cited in Congressional hearings on naval maintenance infrastructure and budgetary prioritization by panels such as the House Armed Services Committee and Senate Armed Services Committee, and it informed discussions about lifecycle sustainment of legacy platforms versus procurement of Virginia-class submarine replacements. The loss emphasized the interplay between human factors, industrial security, and fleet readiness in modern undersea warfare.

Category:Los Angeles-class submarines Category:2012 fires Category:Maritime incidents in 2012