UAP Incursions at Malmstrom AFB and Nuclear Sites (2000–2010)

Between 2000 and 2010, a series of claims and official events pushed U.S. nuclear installations back onto the UAP radar. The decade did not produce a trove of newly declassified, sensor-rich incidents at Malmstrom itself, the oft-cited Malmstrom shutdown narrative derives from the 1960s, but it did see: (1) renewed affidavits and public testimony by veterans tied to Malmstrom and other missile wings (surfacing prominently in September 2010), (2) a high-visibility command-and-control outage of 50 Minuteman III missiles at F.E. Warren AFB (October 23, 2010), which fueled UAP speculation despite an official explanation pointing to a hardware/network fault, and (3) reinforced policy attention to anomalous activity near nuclear assets. This article assembles what the public record actually contains for 2000–2010, separates claims from documents, and frames the national-security context for researchers. Where possible, we link to primary sources (DoD, DVIDS, NARA, AARO, and FOIA-hosted materials). CBS News

Scope & method

• Temporal focus: January 1, 2000–December 31, 2010.
• Sites considered: Malmstrom AFB (341st Missile Wing) and other U.S. nuclear-related sites when relevant to the Malmstrom discourse (e.g., F.E. Warren AFB outage, September 2010 National Press Club testimony referencing Malmstrom).
• Evidence hierarchy: official documents and releases; reputable contemporary reporting citing officials; FOIA-released records; sworn affidavits; researcher compilations.
• Out of scope (contextualized only): the 1960s Malmstrom shutdown narratives except where they resurface in the 2000–2010 public record.

The 2000–2010 window

September 27–28, 2010: Veterans’ press event puts Malmstrom back in the headlines

On September 27, 2010, seven former USAF officers held a National Press Club briefing in Washington, D.C., asserting that UAP had visited nuclear bases and in some cases disabled missiles. The next day, CBS News summarized the event; ABC News ran a contemporaneous piece the same day as the briefing. Both outlets specifically referenced Malmstrom AFB (Montana) as central to some speakers’ claims (notably those of former launch officer Robert Salas). Affidavits connected to Malmstrom were subsequently posted for public scrutiny. CBS News ABC News 

What the documents are:

• Affidavits from former Malmstrom personnel (posted via DocumentCloud) describe 1960s events; they were publicized in 2010 but do not document a new 2000s incident. DocumentCloud
• News coverage provides secondary reporting of the 2010 press event and the claims therein. CBS News

Key point for 2000–2010: In this decade, Malmstrom’s prominence in the UAP–nuclear discussion derived primarily from renewed veteran testimony and media attention- not from a newly documented, sensor-resolved intrusion on Malmstrom grounds in that period.

October 23, 2010: F.E. Warren AFB loses comms with 50 ICBMs (national-security incident)

On Saturday morning, October 23, 2010, launch control officers at F.E. Warren AFB, Wyoming temporarily lost reliable communications and status monitoring for 50 Minuteman III missiles (five Launch Control Centers worth of silos)—an extraordinary scope compared to typical, isolated outages. The event lasted roughly 45 minutes. DoD and Air Force Global Strike Command briefed senior leadership; the event drew widespread coverage. DVIDS, the Defense Department’s official distribution channel, published a same-week statement emphasizing no significant threat, backup monitoring, and a hardware failure as the apparent root cause. DVIDS WIRED

Importance to the UAP record:

• Although no official link to UAP was made (or evidenced) by the Air Force, the timing—coming just days after the high-profile press conference – fueled public speculation about a UAP connection to nuclear command-and-control vulnerabilities. CBS News
• Multiple outlets (e.g., Wired/Danger Room, The Atlantic blog) provided granular descriptions of the outage and the scale of the missile squadron involved, noting the President was briefed—facts that shape the national-security stakes of any anomalous proximate activity, UAP or otherwise. WIRED

What the record shows (2000–2010):

• Official cause: a single hardware/network fault propagated across a squadron-scale segment of the command-and-control network. No official UAP involvement documented. DVIDS

2000–2010: FOIA & archival activity that kept Malmstrom in view

• FOIA releases referencing Malmstrom: A 2001 FOIA package (archived by The Black Vault) reproduced excerpts from the 1967 Malmstrom command history, including the oft-quoted line that rumors of UFOs were “disproven” with a Mobile Strike Team reporting no unusual activity. Its release year (2001) falls in our window and was repeatedly cited in 2000s media coverage, even though the underlying event is older. The Black Vault Documents
• NARA’s UAP portal: By the late 2000s and 2010s, the National Archives began consolidating UAP holdings guidance online; today’s portal helps researchers locate earlier Malmstrom-related records across record groups. (Useful for tracing how 2000s journalists sourced Malmstrom documents.) National Archives
• AARO’s Historical Record Report (2024, cited here for context): Although outside our decade, AARO’s Volume 1 directly addresses the long-running nukes-and-UAP narrative (Malmstrom, Minot, Ellsworth, Vandenberg), reporting that it found no corroborating evidence for UAP disabling U.S. nuclear weapons in the historical cases it reviewed. This is critical context for interpreting the 2010s testimonies that resurfaced during our target decade. U.S. Department of War

Claims vs. Documents: a structured comparison (2000–2010)

A. Claims in the public square (2000–2010)

1. “UAP disrupted missiles at Malmstrom.”

• Source in our window: 2010 National Press Club testimonies and contemporaneous media; affidavits posted online. CBS News ABC News 
• Underlying events: 1960s; not 2000–2010.
• Status of evidence (2000–2010): Public testimony and sworn statements; no new released telemetry or multi-sensor data from the 2000–2010 decade tying UAP to missile disablements at Malmstrom.

2. “UAP were implicated in the F.E. Warren 50-missile outage (Oct. 2010).”

• Source in our window: Speculative commentary rippled across defense policy blogs and some media, often juxtaposing the outage with the press event. The Atlantic
• Official statement: DVIDS/AFGSC: significant hardware/network issue; no UAP attribution. DVIDS
• Status of evidence (2000–2010): No official record linking UAP to the outage; no declassified sensor tracks or incident logs indicating anomalous craft in the missile complex at the relevant times.

B. Documents & official records (2000–2010)

• DVIDS news release (Oct. 27, 2010) on F.E. Warren: “no significant threat,” ~45-minute loss of comms to 50 Minuteman III; root cause a hardware failure; backup monitoring in place. DVIDS
• Contemporary reporting (Oct. 26, 2010): Wired’s Danger Room provided details on scope (319th Missile Squadron), error codes (“launch facility down”), and high-level briefings; The Atlantic punctuated the policy optics (arms-control moment). WIRED
• Affidavits posted (2010): sworn statements describing 1960s Malmstrom events, amplified in 2010 media. DocumentCloud
• FOIA (2001): Malmstrom command history excerpt declining a UFO connection during the 1967 fault, cited often in the 2000s. The Black Vault Documents

Analytical timeline (2000–2010)

• 2000–2009:
  • Malmstrom: No newly declassified UAP intrusions documented in the public record for this decade; the base surfaces in retrospective discussions and occasional local press revisiting the 1967 narratives. greatfallstribune.com
  • Nuclear/UAP discourse grows: Wider public interest consolidates around the nukes & UAP theme, building toward the 2010 press event. (Background archival activity and FOIA publications, like the 2001 Malmstrom packet, feed this loop.) The Black Vault Documents
• September 27–28, 2010:
  • National Press Club briefing; ABC News and CBS News amplify Malmstrom-related testimonies alleging missile disablements by UAP. ABC News
• October 23–27, 2010:
  • F.E. Warren AFB: 50 Minuteman III missiles experience a 45-minute communications/monitoring disruption; DVIDS and Air Force officials brief that a hardware failure was the root cause; the incident triggers Presidential-level attention according to contemporary reports. DVIDS

National-security frame

Why these stories—claims and outages alike—matter to defense planners:

1. Deterrence credibility & continuity of control
   A multi-dozen-missile C2 outage (even if brief and prosaic in cause) challenges assumptions about redundancy, cyber-resilience, and fault isolation. The F.E. Warren event triggered senior-level briefings precisely because perception—both domestic and adversarial—matters in extended deterrence. DVIDS
2. Pattern-of-life intelligence near nuclear assets
   Decades of UAP narratives cluster around nuclear weapons complexes. Whether or not every claim holds, the pattern obliges watchfulness. Today’s AARO work and declassification posture explicitly try to standardize reporting to separate misidentifications from genuine unknowns without dulling alertness at sensitive sites. AARO
3. Information hazard vs. public trust
   When outages occur near the time of public allegations about UAP at nuclear sites, vacuum of information can breed speculation. Rapid, clear official reporting (as in the DVIDS statement) helps stabilize the narrative—without foreclosing further inquiry. DVIDS
4. Historical reevaluation and oversight
   AARO’s Historical Record Report (2024)—though outside the decade—indicates the U.S. Government’s posture to re-audit legacy claims. For 2000–2010 researchers, this later work is useful as a null-hypothesis check against the decade’s resurgent allegations. U.S. Department of War

Data triage for investigators

To harmonize claims with documented facts, apply the following checklist:

1. Time-correlation: If a claim references a base and a date/time, cross-check official logs/releases within ±24h. For Oct 23, 2010, primary references are DVIDS and contemporaneous reporting. DVIDS
2. Asset specificity: Distinguish Malmstrom (Montana; 341st MW) from F.E. Warren (Wyoming; 90th MW). Some secondary sources conflate facilities; clarity matters. stratcom.mil
3. Sensor modality: Ask: Where are radar tracks, optical, SIGINT, security-camera timestamps? 2000–2010 public record provides testimony and press coverage, but no released multi-sensor package tying a UAP to F.E. Warren’s outage. DVIDS
4. Archival anchors: Use NARA’s UAP collections for Malmstrom-related historical documents; verify FOIA provenance (e.g., the 2001 Malmstrom command history excerpt). National Archives
5. Official reassessments: Incorporate AARO HRR (2024) conclusions in background sections to communicate what has, and has not, been corroborated by government re-reviews of nuclear-site UAP claims. U.S. Department of Defense

What we can (and cannot) say from the record

Malmstrom AFB (2000–2010)

• Can say: The decade produced renewed, high-visibility testimonies referencing older Malmstrom events; it produced no newly declassified, sensor-rich Malmstrom UAP incursion from the 2000–2010 window itself. The frequently cited command history excerpt (released 2001) states that UFO rumors at the time of the 1967 fault were “disproven” by a Mobile Strike Team—again, a 1960s finding resurfacing in the 2000s via FOIA. The Black Vault Documents
• Cannot say (from 2000–2010 docs): That a new Malmstrom UAP incursion occurred in the decade, validated by official USAF documentation released in that timeframe.

F.E. Warren AFB outage (Oct. 2010)

• Can say: It was a serious, widely briefed command-and-control disruption affecting 50 missiles for about 45 minutes; DVIDS and Air Force statements attribute it to a hardware/network fault; the event captured national-security attention during a sensitive arms-control moment. DVID WIRED
• Cannot say (from public docs): That UAP causation was substantiated by released evidence.

Implications for nuclear sites

1. Signal vs. noise discipline
   The Malmstrom narrative demonstrates how historical claims can dominate a decade’s discourse without new primary data. Researchers should weight documented 2000–2010 events (e.g., F.E. Warren outage) more heavily than rehashed older incidents unless new artifacts are produced.
2. National-security posture
   Outages like F.E. Warren, regardless of cause, underscore the imperative to instrument missile fields with better forensic sensors (e.g., wide-area persistent surveillance, integrated radar/EO/IR, robust logging) so that if UAP are proximate to an outage, the record speaks beyond testimony.
3. Transparency as a stabilizer
   The DVIDS release model – prompt, factual, constrained – helps prevent speculation run-ups. Future incidents benefit from time-synced data drops (even if redacted) to allow independent correlation.
4. Institutional review
   AARO HRR’s willingness to name bases (Malmstrom, Minot, Ellsworth, Vandenberg) and publish findings is a net positive; for the 2000–2010 corpus, it provides an official null against which new material, if any, must rise. U.S. Department of War

FAQs

Q1: Did Malmstrom AFB report a new UAP incursion in 2000–2010 backed by official documentation?
A: No such Malmstrom-specific 2000–2010 incident appears in the public, declassified record. The Malmstrom story in this decade is mainly testimony about past (1960s) events publicized in 2010. ABC News

Q2: Was the Oct. 23, 2010 F.E. Warren outage caused by UAP?
A: No official evidence supports that. The DVIDS statement attributes the outage to a hardware/network fault; media reports supply operational detail, not a UAP link. DVIDS

Q3: Why include AARO’s 2024 report in a 2000–2010 article?
A: It is the most current official review of nukes-and-UAP claims (including Malmstrom) and provides government-level adjudication that bears directly on how we interpret the 2010 testimonies. U.S. Department of War

Future-proofing data collection

• FOIA priorities: flight-line logs, SATCOM/LC2 network error logs, security forces blotters, radar scopes near missile fields in Sept–Oct 2010 for cross-correlation.
• Data fusion: If an environmental or hardware cause is cited, demand forensic artifacts (component failure reports, network event traces) that can be time-aligned with any aerial observations.
• Terminology discipline: Use UAP consistently; when quoting historical sources that use UFO, indicate that they refer to UAP in modern taxonomy.

Bottom line

For 2000–2010, the public record shows renewed claims about Malmstrom (centered on older incidents) and one major, documented nuclear C2 outage (F.E. Warren, Oct. 2010) that was not officially linked to UAP. The national-security salience of nuclear-site anomalies is indisputable; what remains disputed is whether UAP played an operational role in the events that galvanized public attention in this decade. Absent multi-sensor evidence and with AARO’s later review finding no corroboration of UAP disabling U.S. nuclear weapons, the investigative posture here is: keep the aperture open but the standards high.

References

• DVIDS (DoD): “No Significant Threat From Missile Communication Glitch, Officials Say” (Oct. 27, 2010). (Official statement on the F.E. Warren outage.) DVIDS
• Wired (Danger Room): “Communication With 50 Nuke Missiles Dropped in ICBM Snafu” (Oct. 26, 2010). (Contemporaneous details and context.) WIRED
• The Atlantic (blog): “Failure Shuts Down Squadron of Nuclear Missiles” (Oct. 26, 2010). (Policy optics; presidential briefing noted.) The Atlantic
• ABC News (Sept. 27, 2010): “Former Airmen to Govt.: Come Clean on UFOs.” (Press event coverage.) ABC News
• CBS News (Sept. 28, 2010): “Ex-Air Force Personnel: UFOs Deactivated Nukes.” (Press event coverage.) CBS News
• Affidavits (DocumentCloud): Malmstrom-related sworn statements circulated in conjunction with the 2010 press briefing. DocumentCloud
• FOIA (Black Vault, 2001 release): Malmstrom 1967 command history excerpt (rumors of UFOs “disproven”). (Cited in 2000s coverage.) The Black Vault Documents
• AARO Historical Record Report—Vol. 1 (2024) (contextual to the decade’s claims): treatment of Malmstrom/Minot/Ellsworth/Vandenberg narratives and conclusions. U.S. Department of War
• NARA UAP portal: research guide to UAP holdings across archives (for Malmstrom case file workups). National Archives

Claims Taxonomy

• Verified:
  F.E. Warren AFB, Oct. 23, 2010 — 50-missile communications/monitoring outage; official DVIDS/AFGSC statements and multiple contemporaneous reports confirm scope, duration, and briefings; cause stated as hardware fault. No official UAP link. DVIDS
• Probable:
  None identified in 2000–2010 tying UAP directly to nuclear-site effects with strong but incomplete evidence. If future declassifications add multi-sensor corroboration, entries may migrate.
• Disputed:
  Malmstrom disablement narratives (resurfacing via 2010 testimony/affidavits) vs. the 1967 command history excerpt stating UFO rumors were disproven. In our 2000–2010 window, these remain claims rather than newly documented events. The Black Vault Documents
• Legend:
  Not applicable for 2000–2010; older Cold-War cases fall outside our temporal scope.
• Misidentification:
  Media conflation of Malmstrom and F.E. Warren in secondary discussions; also occasional associative attributions of UAP to the 2010 outage without supporting documentation.

Speculation labels

• Hypothesis:
  Temporal clustering between public claims (Sept. 2010) and a high-impact C2 outage (Oct. 2010) may have amplified UAP attribution in public discourse through availability bias, rather than indicating a causal link. (Testable via content analysis of media and social data around those dates cross-referenced with official logs.)
• Researcher Opinion:
  Stand-up of standardized incident capture (raw radar tracks, ADS-B/Mode-S around missile fields, synchronized security-camera metadata, and narrative 1592/3502-style reports) would materially improve future adjudication of nuclear-site UAP claims.
• Witness Interpretation:
  Personnel in missile alert facilities experiencing unusual alarms/outages might reasonably associate them with simultaneous light or aerial observations reported by security teams—particularly absent immediate technical fault isolation. This is human-factors predictable, not evidence of causation.

SEO keywords

UAP Malmstrom 2000s, Malmstrom nuclear UAP, F.E. Warren 2010 missile outage, nuclear base UAP incursions, Minuteman III communications failure, National Press Club UAP 2010, AARO Historical Record Report nuclear sites, UAP nuclear security implications, affidavits Malmstrom, FOIA Malmstrom command history, DVIDS Warren outage statement.