Within North Dakota UFOs
Why the Minot UFO Case Still Stands Out
The 1968 Minot case stands out because witnesses, radar claims, B-52 crew reports and Blue Book documents all overlap.
On this page
- Ground reports from the missile field
- The B 52 radar and radio claims
- What the surviving Blue Book file can and cannot prove
Page outline Jump by section
Introduction
The Minot B-52 case of 24 October 1968 remains one of North Dakota’s most discussed UFO incidents because it is not just a story about lights in the sky. It combines ground reports from missile-field personnel, a returning B-52H crew, radio traffic, a temporary communications problem, official Project Blue Book paperwork and a surviving set of B-52 radarscope photographs. That does not make the object extraterrestrial, or even prove that all witnesses saw the same thing. It does make the case unusually document-rich for a Cold War UFO report from the northern plains. The central question is still the same: did the records preserve a genuine unknown, or a complicated mix of stars, aircraft, radar effects, haze, timing errors and official over-compression? Project Blue Book closed the case with conventional explanations, but the surviving file leaves enough gaps for the Minot incident to remain a serious North Dakota case rather than a simple anecdote. [minotb52ufo.com]minotb52ufo.comOpen source on minotb52ufo.com. [minotb52ufo.com]minotb52ufo.comBlue Book Final Case ReportBlue Book Final Case Report
Why this case matters in North Dakota UFO history
Minot Air Force Base was not an ordinary backdrop. In 1968 it sat inside a Strategic Air Command environment of bombers, missile fields, security teams, maintenance crews and radar procedures. The modern base still illustrates why the location matters: Minot hosts the 5th Bomb Wing and the 91st Missile Wing, and the missile-security mission involves 150 Minuteman III missiles and launch facilities spread through a large missile complex. That present-day structure is not evidence for the 1968 UFO claim, but it helps explain why reports from this region were handled as more than casual rural sightings. [minot.af.mil]minot.af.milOpen source on af.mil.
The incident also took place near the end of the Air Force’s public UFO-investigation era. Project Blue Book ran from 1947 to 1969 under different names and structures, and the Air Force later stated that 701 of 12,618 reports remained “unidentified” when the programme closed. The Minot case was not one of those officially unexplained cases: Blue Book treated it as identifiable through stars, the B-52 itself and a possible plasma or ball-lightning-like phenomenon. That contrast is part of its importance. It is a case in which the official file exists, the official explanation is visible, and later researchers can compare the conclusion against the underlying documents rather than relying only on folklore. [U.S. Air Force]af.milUnidentified Flying Objects and Air Force Project Blue Book > Air Force > Fact Sheet Display…
For North Dakota, the Minot case sits beside the 1948 Gorman “dogfight” over Fargo as one of the state’s two most substantial historic UFO episodes. The Fargo case is remembered for a military pilot’s pursuit of a light; Minot is remembered because ground observers, a bomber crew and radar-related records all overlap. The value of the Minot file is therefore not that it settles the UFO question, but that it shows how hard it can be to separate observation, instrumentation, military procedure and later interpretation when an unusual report occurs inside a high-security aviation setting.
Ground reports from the missile field
The first layer of the case came from personnel on the ground in the missile field north of Minot. The Basic Reporting Data sent from Minot AFB described the initial observers as two electronic maintenance men travelling by government vehicle to the November-7 missile site, about five miles north of Grano. Additional observers were listed near Mohall, Renville, Hartland and Tolley, making this a dispersed set of reports rather than a single viewpoint. [minotb52ufo.com]minotb52ufo.comOpen source on minotb52ufo.com.
The reported object was described in striking but not fully consistent terms. In the Air Force reporting document, visual witnesses described something “just about round” and slightly oblong, usually bright red-orange, with reports of hovering and abrupt changes in direction and speed. One ground description compared its outline, when nearly overhead, to a stingray shape; another part of the same report noted a low, muffled jet-engine sound heard twice. These are vivid claims, but they also show the difficulty of the case: estimates of elevation, azimuth, colour, size and motion were made at night, under haze and over long distances. [minotb52ufo.com]minotb52ufo.comBasic Reporting DataBasic Reporting Data
The ground reports matter because they created the operational chain that brought the B-52 into the story. According to the reporting data, the wing security controller was notified by vehicle radio, adjacent flight security controllers were alerted, and a local B-52 was asked to remain alert for a possible UFO. Blue Book’s later sequence of events placed ground sightings from roughly 0030 through after 0500 local time, with several witnesses reporting lights before, during and after the bomber’s involvement. [minotb52ufo.com]minotb52ufo.comradarscope indexradarscope index
The weakness of the ground evidence is that it is not one clean observation. Some descriptions could fit bright stars seen through haze, autokinesis, aircraft lights, or the B-52 operating in the area. Blue Book made exactly that argument, concluding that the ground visual sightings appeared to be Sirius and the B-52. It pointed to haze, scattered cloud, a temperature inversion, stellar scintillation and the visual illusion in which a stationary light appears to move against a dark background. Those are real mechanisms, and they deserve weight. They do not, however, automatically explain every ground report, especially because the file itself records varying locations, durations and directions. [minotb52ufo.com]minotb52ufo.comShough ReportShough Report
The B-52 radar and radio claims
The second layer is what makes Minot stand apart from most state-level UFO cases: the returning B-52H. In the Basic Reporting Data, the radar observation was described as “air electronics” using an ASQ-38 system in station-keeping mode. The report identified the aircraft as B-52H JAG31 and gave electronic-sighting data from flight level 200 down to about 9,000 feet, followed by a separate visual sighting at about 3,200 feet mean sea level. [minotb52ufo.com]minotb52ufo.comPoher ReportPoher Report
Blue Book’s own sequence of events recorded several key moments. At 0335, the B-52 was asked to look for an orange light. At 0352, the record says the B-52 was in haze and that weather radar placed an object at three miles at the one o’clock position. At 0358, the B-52 lost transmission to the tower, with transmission returning between 0400 and 0402. The radarscope photo sequence was listed as beginning at 0406:15 and ending at 0406:51. Later, at 0435, the pilot was recorded as observing an unidentified orange light while turning onto base leg for landing. [minotb52ufo.com]minotb52ufo.comPOHER ReportPOHER Report
The B-52 crew’s visual report is more cautious than some later retellings. Blue Book summarised Major James Partin’s account as a bright orange ball of light, about 15 miles away in the west-north-west, either on the ground or slightly above it, remaining stationary as he flew towards it. The aircraft then turned onto base leg about a mile south of the light and above it. This is important because the strongest version of the case often imagines a clearly structured craft flying close to the bomber; the surviving official summary, at least in this section, describes a stationary light seen near the ground during approach. [minotb52ufo.com]minotb52ufo.comsection 6section 6
The radar portion is harder to dismiss neatly. The Air Force reporting document described the radar return as single, sharp, irregular and at times rectangular, and larger on scope than a KC-135 during aerial refuelling. It also stated that the radar echo accompanied the aircraft from an initial position 38 nautical miles north-west of the Deering TACAN 300-degree radial to about 14 nautical miles on the 296-degree radial, as the aircraft descended. Those are not casual witness impressions; they are technical claims embedded in a formal report. [minotb52ufo.com]minotb52ufo.comOpen source on minotb52ufo.com.
The radio claim adds another complication but should be handled carefully. The narrative maintained by the Minot case archive says both B-52 UHF radios would not transmit during the close radar encounter, while the Blue Book sequence records a temporary loss of transmission to the tower. Blue Book attributed the radar contact and temporary UHF loss to a plasma similar to ball lightning. The file does not prove that the radio failure and radar return had the same cause, and a correlation in time is not the same as causation. Still, the fact that the communications issue appears in the official sequence is one reason the case has not faded into ordinary “pilot saw light” territory. [minotb52ufo.com]minotb52ufo.comminot afb 40th anniv celebminot afb 40th anniv celeb
What the radarscope photographs add
The surviving radarscope photographs are the feature most often cited by supporters of the case. The Minot archive lists thirteen B-52 radarscope photographs within the Blue Book case file, and also hosts a radarscope photograph index showing frames numbered 771 through 784, plus explanatory material on station-keeping mode and B-52 radarscope-photo interpretation. The documentation page states that the full Blue Book file comprises 145 pages and includes two maps and thirteen B-52 radarscope photographs. [minotb52ufo.com]minotb52ufo.comOpen source on minotb52ufo.com.
The photographs do not function like a modern video or a clean target track. They are still images of a specialised radar display, taken in a short sequence, and their interpretation depends on aircraft position, radar mode, antenna behaviour, timing, range scale, ground returns and possible propagation effects. This is why later technical work on the case has focused less on dramatic witness language and more on reconstruction: where was the B-52, what was the radar showing, how fast would an echo appear to move, and could ordinary phenomena produce the returns?
Martin Shough’s 2006 radar study is one of the key later attempts to test those questions. It treated the photographs as B-52H radarscope images taken north-west of Minot and examined possible explanations including aircraft, missiles, meteors, precipitation, moon returns, lightning, auroral ionisation, birds, insects, satellites, radio-frequency interference, internal noise, electronic spoofing and anomalous propagation. Shough concluded that no convincing explanation for the unidentified echoes had been found, while also noting uncertainties in the Air Force weather data and the need to reconstruct refractivity conditions rather than rely on a simple “temperature inversion” claim. [minotb52ufo.com]minotb52ufo.comBlue Book Final Case ReportBlue Book Final Case Report
Claude Poher’s 2005 analysis went further in trying to build a three-dimensional reconstruction from the radar photographs and air-visual observations. The report’s own table of contents shows how technically ambitious the exercise was, covering B-52 altitude, antenna tilt, echo displacement, possible speeds, acceleration, radar-wave behaviour in ionised gas and the loss of VHF transmissions. That level of modelling can be useful, but it also depends heavily on assumptions about timing, geometry and what the radar return actually represented. It strengthens the case that the photographs deserve technical attention; it does not turn them into a simple proof of an extraordinary craft. [minotb52ufo.com]minotb52ufo.comOpen source on minotb52ufo.com.
The safest reading is that the radarscope images are real evidence of something recorded by the aircraft’s radar system, but not self-explanatory evidence of what that something was. They move the case above a purely testimonial report, yet they also introduce technical ambiguity. Radar can record solid objects, weather, ground returns, interference, anomalous propagation and other effects. The Minot photographs matter because they narrow the debate; they do not end it.
What Project Blue Book decided
Project Blue Book’s final report, dated 13 November 1968, did not leave the case unresolved. It concluded that the ground visual sightings appeared to be Sirius and the B-52, that the B-52 radar contact and temporary UHF transmission loss could be attributed to a plasma similar to ball lightning, and that the B-52 air visual could have been Vega on the horizon, a light on the ground or possibly a plasma. It also separated the reported physical violation of the Oscar-7 lock from the UFO observations, stating that it did not seem related. [minotb52ufo.com]minotb52ufo.comBasic Reporting DataBasic Reporting Data
The strengths of that conclusion are clear. Blue Book did not simply say “unknown light” and stop. It offered specific categories: a bright star low or prominent in the sky, the bomber’s own lights and sound, haze and inversion effects, autokinesis, and a possible plasma-like radar and radio explanation. It also recognised that some witness reports conflicted in timing and duration, and it treated the B-52 pilot’s most definite visual sighting as occurring around 0435 rather than at the earlier ground-report peak. [minotb52ufo.com]minotb52ufo.comradarscope indexradarscope index
The weaknesses are just as important. The plasma explanation is broad and not tightly demonstrated in the final report. Saying a radar contact and radio loss “could be attributed” to a plasma does not show that a plasma was present, that it had the necessary size and persistence, or that it matched the radar sequence. NICAP’s reproduced discussion of the case noted that Blue Book described a “plasma of the ball-lightning class” without explaining how that determination had been reached. [NICAP]nicap.orgUFO ReportUFO Report
The final report also compressed several layers of evidence into a tidy set of labels. That was common in the later Blue Book era, when the Air Force was under pressure to process reports efficiently and the programme itself was nearing termination. The Air Force’s later public summary of Blue Book emphasised that no investigated UFO was found to represent a national-security threat, a technology beyond scientific knowledge, or an extraterrestrial vehicle. Those broad institutional conclusions matter, but they do not remove the need to examine the quality of explanation in individual cases like Minot. [U.S. Air Force]af.milUnidentified Flying Objects and Air Force Project Blue Book > Air Force > Fact Sheet Display…
The main doubts and the best counterarguments
A balanced reading of Minot has to resist two easy stories. The first is the believer’s shortcut: multiple witnesses plus radar plus a nuclear base equals a proven extraordinary craft. The second is the sceptic’s shortcut: Blue Book named Sirius, Vega and plasma, so the case is solved. The records are more awkward than either version.
The strongest sceptical points are practical. Some ground observations lasted a long time, involved lights near the horizon or in the southern sky, and included colours that can be produced by stellar scintillation through haze. The B-52 itself was flying in the area and could plausibly have confused observers who were already trying to track a light. Blue Book also noted haze, clouds and a moderate temperature inversion, all of which can make lights and distances harder to judge at night. [minotb52ufo.com]minotb52ufo.comShough ReportShough Report
The strongest unresolved points are evidential rather than dramatic. The Air Force report rated several witnesses as reliable, listed both ground-visual and air-electronic observation, described a distinct B-52 radar return, and preserved a photo sequence. Later radar analysis by Shough found no convincing explanation among a wide range of conventional possibilities, though that conclusion remains an expert interpretation rather than an official finding. [minotb52ufo.com]minotb52ufo.comPoher ReportPoher Report
The biggest problem for any single explanation is that the case may not be one event. It may be a cluster: some ground witnesses seeing stars or aircraft; the B-52 radar showing an unusual but non-object return; the crew later seeing a ground light or low celestial object; and the Oscar-7 alarm or lock issue being unrelated. That kind of mixed explanation is less satisfying than either “UFO” or “debunked”, but it often fits messy historical cases better.
What the surviving Blue Book file can and cannot prove
The surviving file can prove that something was formally reported from Minot AFB, that the report involved military witnesses, that the B-52 crew and radar system became part of the investigation, and that Project Blue Book received and evaluated the material. It can also prove that the case generated a substantial paper trail: Basic Reporting Data, witness questionnaires, summaries, radar-scope photographs, maps, memoranda and a final report. The archive’s documentation page identifies the case file as number 12,548 and describes 145 pages of records, including thirteen B-52 radarscope photographs. [minotb52ufo.com]minotb52ufo.comPOHER ReportPOHER Report
The file cannot prove that all observers saw the same object. It cannot prove that the radar return was a solid craft. It cannot prove that the radio-transmission problem was caused by the radar target. It cannot prove that the Oscar-7 lock issue was connected to the sightings; Blue Book explicitly treated it as unrelated. It also cannot remove the uncertainty created by night viewing, haze, estimated angles, incomplete witness forms and later reconstructions. [minotb52ufo.com]minotb52ufo.comsection 6section 6
What it can do is preserve a rare Cold War case where the reader can examine the layers separately. Ground reports are one layer. B-52 radar claims are another. B-52 visual observation is another. Radio failure is another. The Blue Book conclusion is another. Later technical analysis is another. Treating those layers separately is the fairest way to understand Minot, because the case becomes weaker when inflated into a single flawless encounter and stronger when recognised as a complex record that still resists a fully tidy explanation.
A fair reading today
The Minot B-52 case still stands out because it occupies the middle ground that serious UFO history often has to deal with. It is not a proven visitation, not a crash legend, not a single anonymous report, and not a case that can be brushed aside as merely “someone saw a light”. It is a North Dakota incident with named military roles, a specific time window, an operational setting, radar-related records and an official explanation that remains debatable.
The best current assessment is that Minot is unresolved in a limited, evidence-led sense. Some parts of the episode may well have conventional explanations, especially the long-duration ground lights. Blue Book’s star-and-aircraft explanation is plausible for portions of the missile-field reports, and its caution about the Oscar-7 lock issue is sensible. The harder part is the B-52 radar sequence and the temporary radio-transmission problem, where the official plasma explanation is possible in wording but thinly demonstrated in the surviving final report. [minotb52ufo.com]minotb52ufo.comOpen source on minotb52ufo.com.
For North Dakota’s UFO history, the case matters less as a claim about aliens than as a test of evidence. It shows why military witnesses can be valuable without being infallible, why radar records can be important without being self-interpreting, and why official explanations can be plausible in parts while still leaving questions. That is why the Minot case remains one of the state’s most useful UFO case studies: it rewards careful reading more than belief, disbelief or folklore.
Amazon book picks
Further Reading
Books and field guides related to Why the Minot UFO Case Still Stands Out. Use these as the next step if you want deeper reading beyond the article.
The Report on Unidentified Flying Objects
Provides historical context for official investigations of cases like Minot.
eBay marketplace picks
Marketplace Samples
Example marketplace items related to this page. Use the search link to explore similar finds on eBay.
Endnotes
-
Source: minotb52ufo.com
Link: https://minotb52ufo.com/ -
Source: minotb52ufo.com
Title: Blue Book Final Case Report
Link: https://minotb52ufo.com/pdf/Blue-Book-Final-Case-Report.pdf -
Source: minotb52ufo.com
Link: https://minotb52ufo.com/doc.php -
Source: minot.af.mil
Link: https://www.minot.af.mil/About-Us/Our-Mission/ -
Source: minot.af.mil
Link: https://www.minot.af.mil/Base-Units/91st-Missile-Wing-Units/ -
Source: af.mil
Title: U.S. Air Force
Link: https://www.af.mil/About-Us/Fact-Sheets/Display/Article/104590/unidentified-flying-objects-and-air-force-project-blue-book/Source snippet
Unidentified Flying Objects and Air Force Project Blue Book > Air Force > Fact Sheet Display...
-
Source: minotb52ufo.com
Title: Basic Reporting Data
Link: https://minotb52ufo.com/pdf/Basic_Reporting_Data.pdf -
Source: nicap.org
Title: UFO Report
Link: https://www.nicap.org/reports/681024minot_hynek.htm -
Source: minotb52ufo.com
Title: radarscope index
Link: https://minotb52ufo.com/radarscopes/radarscope-index.php -
Source: minotb52ufo.com
Title: Shough Report
Link: https://minotb52ufo.com/shough/ms_sec1.php -
Source: minotb52ufo.com
Title: Poher Report
Link: https://minotb52ufo.com/poher/cp-abstract.php -
Source: minotb52ufo.com
Title: POHER Report
Link: https://minotb52ufo.com/poher/pdf/POHER_Report.pdf -
Source: minotb52ufo.com
Title: section 6
Link: https://minotb52ufo.com/investigation/section-6.php -
Source: minotb52ufo.com
Link: https://minotb52ufo.com/poher/cp-part2.php -
Source: minotb52ufo.com
Title: minot afb 40th anniv celeb
Link: https://minotb52ufo.com/archives/minot_afb/minot_afb_40th_anniv_celeb.pdf -
Source: minot.af.mil
Title: minot air force base
Link: https://www.minot.af.mil/About-Us/Fact-Sheets/Display/Article/264277/minot-air-force-base/ -
Source: minot.af.mil
Link: https://www.minot.af.mil/Base-Units/5th-Bomb-Wing-Units/ -
Source: archive.org
Link: https://archive.org/stream/pdfy-4vyHjooOJagoGAwN/Scientific%2BStudy%2BOf%2BUnidentified%2BFlying%2BObjects_djvu.txt -
Source: zenodo.org
Link: https://zenodo.org/records/8331502 -
Source: Wikipedia
Title: Project Blue Book
Link: https://en.wikipedia.org/wiki/Project_Blue_Book -
Source: Wikipedia
Title: Minot Air Force Base
Link: https://en.wikipedia.org/wiki/Minot_Air_Force_Base -
Source: archives.gov
Title: Project BLUE BOOK
Link: https://www.archives.gov/research/military/air-force/ufos -
Source: britannica.com
Title: Project Blue Book
Link: https://www.britannica.com/topic/Project-Blue-Book -
Source: youtube.com
Title: Project Blue Book
Link: https://www.youtube.com/watch?v=_xyesq1k3Ns
Additional References
-
Source: youtube.com
Title: B-52 and missile crews witnessed a UFO at the vicinity of Minot Air Force Base,
Link: https://www.youtube.com/watch?v=jWoJ7UMfVLYSource snippet
2010-09-27: Minot UFO Event Capt Schindele Testimony...
Published: October 24, 1968
-
Source: youtube.com
Link: https://www.youtube.com/watch?v=6pt3DHrKChUSource snippet
Minot B-52 UFO incident 1968 radar 1968-10-24: Credible Pilots & Aircrew Document Minot UFO Tom Owens UAP...
-
Source: youtube.com
Link: https://www.youtube.com/watch?v=vh02kMSJec8Source snippet
The Minot UFO Incident: Unraveling the 1968 Mystery...
-
Source: academia.edu
Link: https://www.academia.edu/105405731/Analysis_of_Radar_and_Air_Visual_UFO_Observations_at_Minot_AFB_North_Dakota_USA_by_Claude_Poher -
Source: facebook.com
Link: https://www.facebook.com/ThunderdomeIsYou/posts/dont-believe-the-official-story-trypticon-ophidian-is-hijacking-the-frequency-to/1508052810682969/?locale=sw_KE -
Source: facebook.com
Link: https://www.facebook.com/MilitaryMetalArtInc/posts/fire-dawgs-world-class-professionals-only-the-best-come-north-minot-afb-is-the-o/1121104226040294/ -
Source: 5thforcesupport.com
Link: https://5thforcesupport.com/wp-content/uploads/2024/06/History-Walk.pdf -
Source: facebook.com
Link: https://www.facebook.com/minotaf/posts/-throwback-thursday-%EF%B8%8Ffrom-fighting-tyranny-over-the-skies-of-europe-during-world/1123680713120346/ -
Source: npshistory.com
Link: https://npshistory.com/publications/mimi/srs.pdf -
Source: academia.edu
Link: https://www.academia.edu/104599778/The_Investigation_of_UFO_Events_at_Minot_Air_Force_Base_North_Dakota
Topic Tree