UFO Sightings at Nuclear Facilities: The 1967 Malmstrom AFB Incident That Disabled 10 ICBMs
Unidentified Flying Objects (UFOs) have long fascinated both the general public and military personnel. In 1967, an extraordinary incident occurred at Malmstrom Air Force Base that continues to intrigue UFO researchers and military analysts alike. During a routine evening at Oscar flight, where missile launch officers were monitoring ten Minuteman I intercontinental ballistic missiles, strange lights were observed in the sky by security personnel, followed by a glowing reddish-orange pulsating object hovering near the facility.
What makes this case particularly compelling is what happened next - all ten nuclear missiles simultaneously went into an "unlaunchable status" with guidance and control system failures while the unidentified object was present. This wasn't due to power failure, as the facility maintained power throughout the incident. Such a systematic shutdown was unprecedented according to military personnel who served at the base, raising serious questions about the technological capabilities demonstrated during this encounter.
Key Takeaways
In 1967, a UFO incident at Malmstrom Air Force Base coincided with all ten nuclear missiles simultaneously becoming inoperable.
Security personnel observed strange lights performing impossible aerial maneuvers before a glowing reddish-orange object appeared hovering near the facility.
Military officials confirmed this was not an Air Force exercise, and the missiles required specialized retargeting procedures to become operational again.
UFO Disturbance at Military Base
Strange Light Observations
On March 24, 1967, unusual aerial phenomena were reported near Malmstrom Air Force Base. Local residents in Great Falls, Montana and farmers in surrounding areas had previously documented similar sightings in the local newspaper. These initial reports described lights moving in ways that defied conventional aircraft capabilities - making instant stops, reversing direction, and executing perfect 90-degree turns without any engine noise.
The first alert came from a topside security guard who contacted the missile launch officer on duty. The guard described these unusual aerial lights with professional concern, emphasizing they were "not airplanes" based on their impossible maneuvers. At this early stage, the officer acknowledged the report but didn't consider it serious enough for escalation.
The Oscar Flight Incident
Approximately five minutes after the initial call, the security guard contacted the command center again with heightened urgency. The situation had dramatically escalated. The guard's voice conveyed genuine fear as he reported a large, glowing reddish-orange pulsating object hovering directly above the front gate of the Oscar Flight facility.
All security personnel had drawn their weapons and surrounded the perimeter. The missile launch officer immediately recognized the potential threat and advised the guard to secure the launch control center. During this exchange, one guard reportedly sustained a hand injury, though this was likely from contact with the perimeter's barbed wire rather than any direct interaction with the object.
While this confrontation was occurring aboveground, the command capsule stationed 60 feet underground suddenly erupted with warning alarms. The control panel indicated something unprecedented - all ten Minuteman I intercontinental ballistic missiles had sequentially gone into "no-go" status. Each missile displayed the same failure mode: guidance and control system failure.
Guards' Encounter With the UFO
The security team maintained a defensive position while the mysterious object remained stationed above the facility. All personnel reported seeing the same phenomenon - a large, pulsating reddish-orange light hovering with no apparent propulsion system or noise.
During this standoff, additional security alerts indicated possible intrusions at two missile silo locations situated 1-2 miles from the main command center. The incident reached its conclusion when the object reportedly departed "at high speed" according to security personnel.
This event stands as particularly significant because it represents the only recorded instance during this officer's three-year service period where multiple missiles simultaneously became non-operational. Importantly, this was not caused by power failure - the facility maintained electricity throughout the incident, and the missiles had triple-redundant power systems including backup generators and battery reserves.
The following day, the missile crew was relieved through normal protocols and returned to base via helicopter. During subsequent debriefing with squadron leadership and Air Force Office of Special Investigations (AFOSI) personnel, it was explicitly confirmed this was not an Air Force training exercise, as operational missiles were required to remain functional at all times.
Missile Operations Officer Experience
As a missile launch officer stationed at Malmstrom Air Force Base in 1967, the officer was responsible for controlling ten Minuteman I intercontinental ballistic missiles. These nuclear-capable missiles required constant monitoring and operational readiness. The officer served in this capacity for three years, managing critical defense systems from a secure underground command center located 60 feet below ground.
Protocol During Aerial Anomaly Incidents
When the topside security guard reported unusual aerial phenomena on March 24, 1967, the officer initially followed standard reporting procedures. After receiving a second, more urgent call describing a glowing reddish-orange pulsating object hovering near the entrance, the officer issued specific security directives. The commander instructed security personnel to:
Maintain complete perimeter security
Deploy guards with weapons drawn
Ensure no unauthorized access to the launch control facility
Report any changes in the situation immediately
The security team, consisting of six to seven armed guards, maintained positions around the facility while the strange object remained visible. One guard sustained a minor hand injury during the incident, though this was apparently unrelated to the aerial phenomenon itself.
Missile System Deactivation Sequence
Shortly after the aerial object was reported, the launch control center experienced an unprecedented system failure. The missile status indicators revealed a troubling sequence of events:
Alert tones and warning systems activated automatically
First one missile, then all ten missiles displayed "unlaunchable" status
Diagnostic checks indicated "guidance and control system failure" on all missiles
Intrusion detection systems activated at multiple launch facilities
This comprehensive shutdown was exceptional for several important reasons:
System Redundancies:
Triple-redundant power systems remained operational
Backup generators maintained power to the facility
Battery systems were functioning normally
Historical Context: During the officer's three-year assignment, this was the only occurrence of multiple simultaneous missile failures without explanation. Following the incident, specialized targeting teams were dispatched to restore the missiles to operational status, as the inertial guidance systems (which predated GPS technology) required recalibration.
The officer was debriefed by squadron commanders and Air Force Office of Special Investigations personnel upon return to base, with officials confirming this was not a planned military exercise.
Post-Incident Protocols
After incidents involving unidentified flying objects at military installations, proper procedures must be followed to ensure complete documentation and appropriate responses. These protocols help maintain operational integrity and provide valuable information for analysis.
Personnel Debrief and Documentation
Following the incident at Oscar Flight where all ten Minuteman missiles went offline simultaneously during a UFO encounter, crew members must be properly relieved and debriefed. The outgoing crew is transported back to base via helicopter as part of standard rotation procedures. This isn't a punitive measure but rather normal protocol for missile launch officers completing their 24-hour shifts. Detailed reports must be filed documenting all observed phenomena, communications with security personnel, system failures, and timestamps of events. Any physical evidence, including security footage or readings from monitoring equipment, should be preserved and submitted with reports.
Command Review and Investigation
After returning to base, missile officers must report directly to their Squadron Commander for a comprehensive debrief. The Air Force Office of Special Investigations (AFOSI) typically participates in these meetings, especially when incidents involve unexplained phenomena or system failures. During these sessions, officers should clarify that the events were not part of scheduled exercises or tests. Command staff generally assures personnel that unauthorized exercises would never be conducted with operational nuclear missiles, as these systems must remain functional at all times for national security.
The investigation typically includes technical teams who must be dispatched to assess and restore missile functionality. For guidance system failures like those reported at Oscar Flight, specialized targeting teams must recalibrate the inertial guidance systems since these older systems relied on gyroscopes, accelerometers, and velocity meters rather than GPS technology.
Military protocol requires maintaining confidentiality about such incidents, with information compartmentalized on a need-to-know basis to protect operational security.