Minot Air Force Base, in northwestern North Dakota, was one of the most sensitive places in America in 1968. It was a principal Strategic Air Command dual-wing base: the 5th Bombardment Wing flew fifteen B-52H Stratofortress strategic bombers, and the 91st Strategic Missile Wing controlled 150 Minuteman intercontinental ballistic missiles in underground launch facilities scattered across the prairie. In the early morning hours of 24 October 1968, over more than three hours, maintenance and security personnel across that missile complex, a radar station, and the crew of a returning B-52 all reported the same thing: a large, glowing, unidentified object, moving in ways no aircraft could. Project Blue Book investigated and concluded it was a combination of radar error, a plasma ball, and the stars. The men who were there have spent the decades since saying otherwise.
The ground sightings
The night began on the ground, in the missile field. At about 2:15 a.m., a security team — a “camper team” — posted at Launch Facility Oscar-6, nineteen miles north of the base, reported a large glowing object that “went down by some trees not far away.” The team was providing aboveground security for a target alignment team working underground in the silo, with a nuclear weapon exposed below. Concerned about an unidentified object near the site, they closed the facility and reported the sighting to Staff Sergeant William Smith, the Oscar-Flight security controller.
At about 2:30 a.m., a missile maintenance team, Airman First Class Robert O’Connor and Airman First Class Lloyd Isley, en route to the November-7 launch facility, reported an unusual light in the east to Base Operations. At about 3:08 a.m., another security team observed a self-luminous object alternating colours in the south-southeast, at an estimated distance of ten to twelve miles. The reports were coming from different teams, in different places, describing the same kind of object: large, glowing, changing colour, and moving.
Base Operations, receiving the reports, did what the procedures required: it alerted Radar Approach Control and the crew of a B-52H that was returning to Minot from a routine ten-hour training mission.
The B-52 encounter
The B-52’s crew that night was a full one: aircraft commander Captain Don Cagle, co-pilot Captain Bradford Runyon Jr., radar navigator Major Chuck Richey, navigator Captain Patrick McCaslin, electronic warfare officer Captain Thomas Goduto, and gunner Technical Sergeant Arlie Judd. A non-crew pilot, Major James Partin, was also aboard. The aircraft had flown out to Grand Forks and was returning to Minot at about 3:00 a.m., practising high-altitude manoeuvres to the east of the base.
At about 3:52 a.m., as the B-52 began a wide turn, ground controllers told the crew that the object was being picked up on weather radar as well, and that it should be at their one o’clock position, three miles away. The B-52’s own radar then detected the return at co-altitude, three miles off. As the bomber banked through a roughly six-mile-diameter turn, the return maintained a constant three-mile separation — pacing the aircraft, in formation, through a 180-degree turn.
Then, as the B-52 began its descent back toward the runway, the return suddenly changed position. In a single sweep of the radar — less than three seconds — it closed from three miles to one mile. Subsequent sweeps showed it matching the B-52’s forward velocity. Navigator Patrick McCaslin, decades later, described the moment plainly: he had never seen anything on radar move laterally two miles in three seconds and then stop, holding perfect formation at one mile. At the same instant as the return’s abrupt movement, both of the B-52’s UHF radios ceased to transmit on all frequencies. The object paced the aircraft off its left wing for nearly twenty miles. Near the end of the descent, the radarscope camera filmed the return as it appeared to spiral around behind the B-52, after which it disappeared from the scope and radio communications returned to normal.
The radarscope photographs survived in the Project Blue Book file, in poor-quality reproductions. Runyon later wrote that they showed a return “about five times as large as a KC-135 tanker”, with a closing rate of 3,000 miles per hour.
The object on the ground
The encounter was not over when the B-52 landed. Radar Approach Control vectored the crew to overfly a stationary object on or near the ground. After turning onto the downwind leg of the traffic pattern, the pilots observed a large, illuminated object ahead of the aircraft for several minutes. Major Partin compared it, in his account, to a glowing object on the ground. The crew watched it at close range as they turned onto the base leg over it.
After the B-52 landed, both the outer and inner perimeter alarms at the remote missile Launch Facility Oscar-7 went off. A security team sent to investigate found a padlocked entry hatch open, with a plug-style gate secured by a padlock removed from it. The duration of the reported observations that night was over three hours, from about 2:15 to 5:34 a.m.
Runyon later added a detail that does not appear in the Blue Book file: he said he was told at a briefing the next day that a 20-ton lid over a missile silo had been moved, that the chain-link fence around the silo had been crushed, and that an alarm had gone off at one of the silos. That account comes from Runyon alone, and it is not in the official record — a distinction the case’s researchers are careful to preserve.
The investigation
The case was officially examined by Lieutenant Colonel Arthur Werlich, the officer in charge of UFO investigations at the base. He provided details and evidence to Project Blue Book, the Air Force’s UFO investigation programme, which concluded that what had been seen was possibly a combination of “anomalous propagation” of radar returns, a plasma ball, and celestial bodies. Blue Book also concluded that the break-in at Oscar-7 was unrelated to the sightings.
Werlich’s own report was more cautious than Blue Book’s conclusion. He listed four occurrences that he said could not be explained: the cause of the radar echo, the cause of the loss of the B-52’s UHF radio transmission, the cause of the B-52’s air-visual observation and the simultaneous ground observation in the same location, and the cause of the Oscar-7 break-in. He avoided commenting on the cause of the radar and air-visual encounters, and his analysis focused mainly on trying to show that most of the ground observations had been misidentifications of the B-52 itself — a claim that is difficult to sustain for sightings that began before the bomber returned to the area.
The case lay dormant for thirty years. In 2000, Bradford Runyon contacted the Center for UFO Studies and filled out a sighting report form. The case caught the interest of the Sign Historical Group, a civilian research organisation, which conducted a thorough investigation, including many interviews with witnesses, and published its material as part of the Sign Oral History Project, on a website devoted to the case. Researcher Thomas Tulien’s narrative of the events, based on the Blue Book file and the witness interviews, is now the most complete account available.
Why Minot is different
Minot is different from most UFO cases in one crucial respect: it happened at a nuclear base, and it was recorded by the military’s own systems. The radar returns were photographed. The radio failure was logged. The missile-site alarms were recorded. The investigating officer listed four things he could not explain. This is not a case that rests on a single witness’s memory. It rests on a paper trail that the Air Force itself created, and that paper trail does not support the Air Force’s own conclusion.
That does not mean the object was a spacecraft. It means that the official explanation — anomalous propagation, plasma, and stars — does not account for the radar return that paced a B-52 for twenty miles, or for the radios that stopped transmitting at the exact moment the return moved, or for the object that the crew and ground observers watched in the same place at the same time, or for the alarms at Oscar-7. Blue Book’s conclusion was, in effect, a list of three things that might explain parts of the case, applied to a case whose parts do not fit them.
The Minot incident is also a reminder of how the UFO question looked from inside the military. The men involved were not enthusiasts. They were a bomber crew, missile security teams, and a radar station, doing their jobs on a night when something appeared over a field of nuclear weapons and stayed for three hours. Their reports were filed through proper channels, investigated by a proper officer, and then filed away with a conclusion that the investigating officer himself did not fully endorse. Fifty-eight years later, the file is still open in every sense that matters.
What is documented, and what is not
Documented facts: In the early morning of 24 October 1968, security and maintenance personnel at Minot Air Force Base, North Dakota, reported a large glowing object near missile launch facilities, beginning at about 2:15 a.m. at Oscar-6; observations continued until about 5:34 a.m. A returning B-52H crew (Captain Don Cagle, Captain Bradford Runyon Jr., Major Chuck Richey, Captain Patrick McCaslin, Captain Thomas Goduto, Technical Sergeant Arlie Judd) tracked a radar return at three miles that closed to one mile in a single radar sweep, paced the aircraft for nearly twenty miles, and was filmed by the radarscope camera; both UHF radios failed to transmit during the encounter. The crew later observed a large illuminated object on the ground. After landing, alarms activated at Launch Facility Oscar-7, where a padlocked entry hatch was found open. Investigating officer Lieutenant Colonel Arthur Werlich listed four occurrences he could not explain; Project Blue Book concluded the case was possibly anomalous propagation, a plasma ball, and celestial bodies, and that the break-in was unrelated. Runyon contacted the Center for UFO Studies in 2000, and the Sign Historical Group later investigated the case in depth.
Unverified or disputed claims: The claim that the object was an unknown craft rests on the radar record, the radio failure, and the crew’s accounts, but no wreckage, photograph of the object itself, or independent radar recording has been produced. The claim that a 20-ton silo lid was moved comes from Runyon’s later account of a briefing and does not appear in the Blue Book file. The claim that the ground sightings were misidentifications of the B-52 is contradicted by the timing of the earliest reports, which preceded the bomber’s return. Blue Book’s explanation of anomalous propagation, plasma, and stars does not account for the radar return’s behaviour or the simultaneous air and ground observations.
Sources
- https://minotb52ufo.com/investigation/section-5.php
- https://podcastufo.com/part-2-a-1968-ufo-incident-at-minot-afb/
- https://www.academia.edu/69394036/A_Narrative_of_UFO_Events_at_Minot_Air_Force_Base_North_Dakota
- https://www.ufo-hunters.com/sightings/search/55b275deee28c4778c9e0225/UFO%20Sighting%20in%20Minot,%20North%20Dakota%20(United%20States)%20on%20Thursday%2024%20October%201968