Within Minnesota UFOs
Which Minnesota Cases Did Blue Book Leave Unexplained?
Pilot reports, technical witnesses and official classifications show why several early Minnesota sightings resisted easy explanation.
On this page
- Hamel and the alleged landing trace
- Mankato and Twin Cities air sightings
- What unidentified and insufficient data meant
Page outline Jump by section
Introduction
Project Blue Book’s strongest Minnesota files are not necessarily the most dramatic stories. They are the reports in which official investigators had something more than a distant anonymous light: military pilots, technically trained observers, an instrument-assisted sighting, checks against radar and air traffic, or an alleged ground trace that could be examined. The leading files are the 1948 Hamel landing claim, the 1951 Mankato pilot encounter and two Twin Cities-area sightings from 1953.
None proves that an extraordinary craft visited Minnesota. Hamel lacks a secure final classification and yielded no unusual laboratory result. Mankato was extremely brief and rested on one pilot’s perception. The General Mills engineers recorded angular movement, but their impressive speed estimate depended on an assumed distance. Their value lies elsewhere: they show how a sincere, credible report could remain unresolved even after the Air Force checked balloons, aircraft, weather, radar and witness reliability.
Hamel and the alleged landing trace
The Hamel report began on 11 August 1948, before the name Project Blue Book existed. It was handled during Project Sign, the first of the Air Force programmes whose files were later absorbed into the Blue Book archive. A local postmaster relayed a farmer’s account that his sons, aged eight and ten, had seen a plate-like object descend near the family home. The earliest FBI correspondence described it as a silver-coloured object resembling two plates, reportedly landing or striking the ground about eight feet from one boy before rapidly departing.[Wikimedia Commons]upload.wikimedia.orgWikimedia Commons…
Later material in the file contains a more developed account. The boys described a dull grey object roughly two feet across, with no visible windows or wires, which made a whistling noise, spun and rose steeply. An investigator found a depression at the reported landing point: the ground appeared compressed and projecting stones had apparently been flattened. Photographs were taken and soil was collected, although rain had partly filled and disturbed the depression before the military examination.[FOX 9 Minneapolis-St. Paul]fox9.comOpen source on fox9.com.
That physical trace is why Hamel has remained more memorable than most childhood sighting reports. Yet it did not become persuasive physical evidence. A request to the FBI laboratory acknowledged that the sample came from the alleged landing site but also warned that there was no control sample from the surrounding soil. Without a comparison sample, any chemical or structural difference would have been difficult to interpret.[Wikimedia Commons]upload.wikimedia.orgWikimedia Commons…
The surviving record indicates that the FBI examination found nothing abnormal. The Army Chemical Corps nevertheless showed interest and requested photographs and surface samples for further analysis. Its letter said that some of its scientists wanted, but the available 30-page file does not preserve a clear final analytical result from that work.[Wikimedia Commons]upload.wikimedia.orgWikimedia Commons…
Hamel therefore deserves a careful rather than sensational description. It is a documented alleged close encounter, investigated promptly enough for officials to inspect the site, but the witnesses were young children, no adult saw the object, no photograph of it exists and the supposed trace was neither protected nor scientifically sampled under controlled conditions. The FBI itself later noted that it had received the matter for information and was unable to undertake a further investigation.[Wikimedia Commons]upload.wikimedia.orgWikimedia Commons…
It is also misleading to call Hamel an unquestioned “Blue Book unknown”. The archive does not provide an unambiguous final evaluation comparable with the record cards for later cases. A notation that no astronomical explanation fitted the account only excludes one family of possibilities; it does not establish that a structured craft landed there. Hamel is strongest as an archival case showing unusually serious official interest, not as proof that the ground depression had an exotic cause.
Mankato’s five-second pilot encounter
The Mankato case of 24 November 1951 is stronger in witness training but weaker in duration. Two F-51 fighters were flying a combat air patrol south of Minneapolis at about 25,000 feet. The flight leader reported a small, milky-white object shaped like a flying wing. It appeared to hang motionless ahead before passing roughly 100 feet above and 100 feet to the left of his aircraft. He saw it for about five seconds; his wingman did not.[govweird]govweird.commankato mn november 1951Project Blue Book: Mankato, Minnesota, November 1951 · govweird…
The pilot reported no sound, exhaust or trail. After the object passed, the fighters turned in an unsuccessful attempt to see or catch it. The investigation checked several ordinary possibilities. Ground radar had shown only the two fighters. A weather balloon launched in the region had travelled far to the south-east, making it a poor geographical match. Lowry Air Force Base reported no relevant classified aircraft activity, and the weather was clear with long visibility.[govweird]govweird.commankato mn november 1951Project Blue Book: Mankato, Minnesota, November 1951 · govweird…
The record card ultimately carries an “unidentified” evaluation, although “probably balloon” also appears as a tentative possibility in the paperwork. That tension is important. It suggests that investigators considered a conventional explanation plausible but could not correlate it securely with the reported position and movement. The word “unidentified” was therefore an administrative conclusion about the available evidence, not a judgement that the object possessed extraordinary technology.[govweird]govweird.commankato mn november 1951Project Blue Book: Mankato, Minnesota, November 1951 · govweird…
Mankato’s strongest feature is the apparent close pass reported by a military pilot. If the stated distance and eight-foot span were accurate, this was not merely a star or remote light. Its central weakness is that those values were visual estimates made during a five-second encounter, with no radar return, photograph or confirmation from the nearby wingman. A small object seen at an uncertain distance can appear to move, hover or pass close when the geometry is misunderstood.
The case consequently sits in a useful middle ground. It is harder to dismiss than a casual report because the witness was airborne, trained and subject to an official inquiry. It remains too thin to support firm claims about the object’s true size, range or speed. Blue Book’s inability to identify it reflects that unresolved gap.
Why the General Mills case mattered
The 15 October 1953 Minneapolis report is arguably Minnesota’s strongest early technical-observer file. Three engineers from General Mills Aeronautical Laboratories were tracking a 79-foot high-altitude balloon from the roof of their Minneapolis facility when they noticed a separate vapour or smoke trail moving southward below the Sun. One observer used the balloon-tracking theodolite, an instrument that measures precise angles, to follow the phenomenon.[govweird]govweird.comminneapolis mn october 1953Project Blue Book: Minneapolis, Minnesota, October 1953 · govweird…
The reported movement was unusual. The object crossed ten degrees of sky in nine seconds, then appeared to enter a steep dive lasting roughly ten to fifteen seconds. It flashed or reflected sunlight several times, levelled out as a grey, indistinct mass and disappeared in a final flash. No sound was heard.[govweird]govweird.comminneapolis mn october 1953Project Blue Book: Minneapolis, Minnesota, October 1953 · govweird…
Assuming an altitude of 40,000 feet, investigators calculated a horizontal speed of about 900 miles per hour. At 60,000 feet, it would have been nearer 1,200 mph. Those figures made the report impressive in the early jet age, but they were not direct measurements. The theodolite supplied angular motion; the altitude of the unknown object was estimated. A nearer object would have been slower and smaller, while a more distant one would have been faster and larger.[Internet Archive]archive.orgInternet Archive Full text of "The Hynek UFO ReportInternet Archive Full text of "The Hynek UFO Report
The witnesses themselves thought a jet aircraft was the most likely broad explanation. Their difficulty was reconciling that answer with the apparent manoeuvre, absence of engine noise and reported trail behaviour. Air Defence Command records showed two F-86 jets in the wider area, south and west of Minneapolis, at about the relevant time, but investigators could not establish a definite match.[govweird]govweird.comminneapolis mn october 1953Project Blue Book: Minneapolis, Minnesota, October 1953 · govweird…
This is where the file’s real strength lies. The witnesses were not simply impressed by a bright light. They were engineers engaged in an aeronautical observation, knew that a large research balloon was already in view, attempted to describe the second phenomenon technically and considered the ordinary aircraft hypothesis themselves. Blue Book consultant J. Allen Hynek later highlighted the case as “The Case of the Three Baffled Engineers” and described it as a Blue Book unidentified.[Internet Archive]archive.orgInternet Archive Full text of "The Hynek UFO ReportInternet Archive Full text of "The Hynek UFO Report
Even so, the case did not produce a fixed image, radar track or range measurement. The object’s grey appearance and flashing could fit sunlight reflecting from an aircraft, while perspective can make a receding or turning object appear to dive. The absence of sound is suggestive rather than decisive because wind, distance, engine orientation and background conditions affect audibility.
The catalogue history is also untidy. A modern archival presentation labels the file “Insufficient Data” at the top while its summary and reproduced evaluation identify the Air Force conclusion as “unknown”; Hynek likewise treated it as unidentified. That discrepancy is a reminder that Blue Book records can contain preliminary labels, later assessments and inconsistent indexing within the same case family.[govweird]govweird.comminneapolis mn october 1953Project Blue Book: Minneapolis, Minnesota, October 1953 · govweird…
Twin Cities lights without radar confirmation
A second Twin Cities report, dated 30 November 1953, involved two Air Force pilots and a civilian who watched a bright, round light over Minneapolis for about half an hour. It reportedly remained stationary, changed among white, red, blue, green and yellow, and appeared about the size of a pea held at arm’s length. Minneapolis–St Paul airport personnel looked for it, but radar detected no corresponding target. The file also noted that no known balloon or aircraft was in the reported area.[FOX 9 Minneapolis-St. Paul]fox9.comOpen source on fox9.com.
The long duration and multiple witnesses give the case some evidential value, but its reported characteristics also invite a conventional explanation. A stationary, colour-changing point of light is a familiar description of a bright star or planet seen through turbulent air. Apparent altitude estimates for isolated lights are notoriously unreliable because there is no visible scale or known distance. The lack of radar confirmation weakens the idea that a solid object was hovering nearby, although radar in 1953 did not detect every small, distant or poorly reflecting target.
The surviving file does not clearly state a final Blue Book classification. That makes it less secure as an “unexplained” Minnesota case than Mankato or the engineers’ report. It is better understood as an unresolved-looking file in which the record preserves checks against local traffic but lacks the astronomical and atmospheric reconstruction needed for a confident conclusion.
A related 1954 pilot report, in which a light appeared to follow an Air Force flight towards Minneapolis for hundreds of miles, was marked unidentified after radar stations failed to confirm a target. Yet this case again involved a light with no reliable range. A distant star, planet or aircraft can seem to accompany a moving aeroplane because its bearing changes very little. The length of an observation does not solve that geometry problem unless independent position data are available.[FOX 9 Minneapolis-St. Paul]fox9.comOpen source on fox9.com.
What “unidentified” and “insufficient data” meant
Blue Book’s own guidance separated reports into three broad outcomes. “Identified” meant that investigators believed sufficient information supported a positive explanation. “Insufficient data” meant that one or more essentials—such as time, duration, position, weather or manner of disappearance—were missing. “Unidentified” was reserved for reports that appeared to contain enough relevant information for analysis but could not be correlated with a known object or phenomenon.[Defense Logistics Agency]esd.whs.milDefense Logistics Agency
That distinction helps explain why an unresolved case was not necessarily the strongest case. A vague report might resist explanation simply because the file was incomplete; it belonged under insufficient data. An unidentified case was supposed to have survived a more meaningful comparison with aircraft, balloons, astronomical objects and weather. Even then, the Air Force explicitly stated that it found no evidence that reports in the unidentified category were extraterrestrial vehicles.[U.S. Air Force]af.milunidentified flying objects and air force project blue bookAir ForceUnidentified Flying Objects and Air Force Project Blue BookThere was no evidence indicating that sightings categorized as "unide…
Minnesota’s leading files also reveal how unevenly those categories could be applied. Mankato contains a formal unidentified judgement alongside a tentative balloon suggestion. The Minneapolis engineers’ case is variously presented as unknown, unidentified and insufficient data. Hamel attracted several agencies but lacks a plainly preserved final classification. The paperwork is evidence of investigation, not a perfectly consistent scientific database.
The most defensible ranking therefore depends on the question being asked:
- Best alleged physical-trace file: Hamel, because officials inspected and sampled the site, although the sampling was poorly controlled and produced no demonstrated anomaly.
- Best military pilot file: Mankato, because a trained pilot reported a close aerial object and investigators checked radar, balloons and restricted aircraft activity.
- Best technical-observer file: the General Mills engineers’ sighting, because three aeronautical specialists used a theodolite and supplied enough detail for a substantial investigation.
- Most plausible astronomical-style report: the November 1953 stationary, colour-changing Minneapolis light, whose lack of radar confirmation and uncertain range substantially weaken the solid-craft interpretation.
Which cases genuinely remained strong?
The General Mills case stands out as Minnesota’s most information-rich Blue Book-era unknown. Its multiple technical witnesses, instrument-assisted angular observation and recorded investigation place it above the average sighting report. Mankato follows because of the military pilot and the checks against local flight and balloon activity, though the five-second duration and lack of corroboration are serious limitations.
Hamel is historically significant but evidentially weaker. The alleged landing mark gave investigators something tangible to inspect, yet no anomalous substance or lasting physical effect was established. The Twin Cities light reports remain interesting chiefly because military and airport personnel were involved, not because the files prove unusual performance.
Taken together, these cases show what “strong” means in Minnesota’s official UFO archive. It does not mean confirmed spacecraft, impossible manoeuvres or evidence of visitors from elsewhere. It means that the report contained enough credible detail to justify federal attention and that the available conventional explanations did not fully settle the matter. The files preserve genuine uncertainty—but also the limits of visual estimation, incomplete records and Cold War-era investigative practice.
Amazon book picks
Further Reading
Books and field guides related to Which Minnesota Cases Did Blue Book Leave Unexplained?. Use these as the next step if you want deeper reading beyond the article.
The Report on Unidentified Flying Objects
Directly relevant to Project Blue Book investigations.
The UFO Experience: A Scientific Inquiry
Written by Blue Book's scientific consultant.
eBay marketplace picks
Marketplace Samples
Live-tested eBay searches with available results related to this page.
Selected fromUFO poster oneBay.co.uk.
Endnotes
1.
Source: upload.wikimedia.org
Link:https://upload.wikimedia.org/wikipedia/commons/f/fd/Project_Blue_Book_report_-_1948-08-6387249-Hamel-Minnesota.pdf
Source snippet
Wikimedia Commons...
2.
Source: govweird.com
Title: mankato mn november 1951
Link:https://www.govweird.com/topics/ufo/project-blue-book/mankato-mn-november-1951
Source snippet
Project Blue Book: Mankato, Minnesota, November 1951 · govweird...
Published: november 1951
3.
Source: govweird.com
Title: minneapolis mn october 1953
Link:https://www.govweird.com/topics/ufo/project-blue-book/minneapolis-mn-october-1953
Source snippet
Project Blue Book: Minneapolis, Minnesota, October 1953 · govweird...
Published: october 1953
4.
Source: archive.org
Title: Internet Archive Full text of “The Hynek UFO Report”
Link:https://archive.org/stream/TheHynekUFOReport/The_Hynek_UFO_Report_djvu.txt
5.
Source: esd.whs.mil
Title: Defense Logistics Agency
Link:https://www.esd.whs.mil/Portals/54/Documents/FOID/Reading%20Room/UFOsandUAPs/proj_b1.pdf?ver=2017-05-22-113513-837
6.
Source: af.mil
Title: unidentified flying objects and air force project blue book
Link:https://www.af.mil/About-Us/Fact-Sheets/Display/Article/104590/unidentified-flying-objects-and-air-force-project-blue-book/
Source snippet
Air ForceUnidentified Flying Objects and Air Force Project Blue BookThere was no evidence indicating that sightings categorized as "unide...
7.
Source: archive.org
Title: Brad Sparks Comprehensive Catalog of 1,600 Project Blue Book UFO Unknowns
Link:https://archive.org/download/BernardSieglerTechnicsAndTime1TheFaultOfEpimetheus/Brad%20Sparks%20-%20Comprehensive%20Catalog%20of%201%2C600%20Project%20Blue%20Book%20UFO%20Unknowns.pdf
Source snippet
Comprehensive Catalog of 1600 Project Blue Book UFO...2 Oct 2009 — Blue Book IFO cases as Unexplained UFO cases, investigations from 194...
8.
Source: ia601301.us.archive.org
Link:https://ia601301.us.archive.org/28/items/monticola1967west/monticola1967west.pdf
Source snippet
MonticolaMankato, and Minnesota. It is the Monlicola's purpose to leave the detailed history up to a forthcoming volume. J. Hamill...
9.
Source: archive.org
Link:https://archive.org/download/annualcommenceme1975nort/annualcommenceme1975nort.pdf
10.
Source: archive.org
Link:https://archive.org/download/1971congressiona008514mbp/1971congressiona008514mbp.pdf
11.
Source: archive.org
Title: Popular Mechanics 04 1961 djvu.txt
Link:https://archive.org/stream/PopularMechanics1961/Popular%20Mechanics-04-1961_djvu.txt
12.
Source: archive.org
Title: usaf signm
Link:https://archive.org/details/usaf-signm
13.
Source: archive.org
Link:https://archive.org/stream/usaf-signm/USAF-SIGNM_djvu.txt
14.
Source: archive.org
Link:https://archive.org/stream/ProjectBlueBookSpecialReport14/pbbsr14_djvu.txt
15.
Source: upload.wikimedia.org
Title: Project Blue Book, BBA PBSR1 300
Link:https://upload.wikimedia.org/wikipedia/commons/3/3b/Project_Blue_Book%2C_BBA-PBSR1-300.pdf
16.
Source: upload.wikimedia.org
Title: Project Blue Book, BBA PBSR8 300
Link:https://upload.wikimedia.org/wikipedia/commons/5/5c/Project_Blue_Book%2C_BBA-PBSR8-300.pdf
17.
Source: history.com
Title: Project Blue Book
Link:https://www.history.com/articles/project-blue-book
18.
Source: history.com
Title: ufo dogfight gorman us plane fargo
Link:https://www.history.com/articles/ufo-dogfight-gorman-us-plane-fargo
19.
Source: war.gov
Title: J1 ~ ~<:JL.Excerpt of letter dated
Link:https://www.war.gov/medialink/ufo/061226/release_03/documents/DOW-UAP-D088_US-AirForce_Analysis-of-Flying-Objects-in-the-US_101-172.pdf
20.
Source: fox9.com
Link:https://www.fox9.com/news/minnesota-ufos-project-blue-book-case-files
21.
Source: archives.gov
Title: Project BLUE BOOK
Link:https://www.archives.gov/research/military/air-force/ufos
22.
Source: Wikipedia
Title: Project Blue Book
Link:https://en.wikipedia.org/wiki/Project_Blue_Book
Additional References
23.
Source: youtube.com
Title: Minnesota’s most notorious UFO sighting remains a mystery four decades later
Link:https://www.youtube.com/watch?v=Gss_sbU-Ypc
Source snippet
Finding Minnesota: Deputy's UFO Encounter...
24.
Source: cia.gov
Link:https://www.cia.gov/readingroom/docs/CIA-RDP81R00560R000100060001-5.pdf
25.
Source: archives.gov
Link:https://www.archives.gov/research/jfk/warren-commission-report/chapter-6.html
26.
Source: archives.gov
Link:https://www.archives.gov/research/jfk/select-committee-report/part-1c.html
27.
Source: archives.gov
Link:https://www.archives.gov/files/research/microfilm/t175-3.pdf
28.
Source: archives.gov
Link:https://www.archives.gov/research/holocaust/finding-aid/military/rg-226-3b.html
29.
Source: ojp.gov
Link:https://www.ojp.gov/pdffiles1/Digitization/113506-113520NCJRS.pdf
30.
Source: archives.gov
Link:https://www.archives.gov/files/declassification/iscap/pdf/2014-004-doc01.pdf
31.
Source: nsa.gov
Link:https://www.nsa.gov/portals/75/documents/news-features/declassified-documents/ufo/usaf_fact_sheet_95_03.pdf
32.
Source: obamawhitehouse.archives.gov
Link:https://obamawhitehouse.archives.gov/sites/default/files/microsites/ostp/NSTC/latent_fingerprint_report_may_2015.pdf