What the Declassified Paper Trail Actually Shows

Back in March 1967, central Montana had itself a week that still gets whispered about from Great Falls to Belt.

Now here’s where folks get tangled up. There were two separate events that month. Same base. Same region. Different files.

First, there was a burst of UFO reports in the Great Falls area — including claims of a “landing” near Belt, Montana.

Second, there was the now-famous Echo Flight missile shutdown, where ten nuclear missiles went offline within seconds of each other.

Both events are documented. However, and this part matters, the primary records do not link them together.

Still… when you lay them side by side, the story sure feels like it’s leaning toward something.

The Montana Stage: Wind, Wheat & Nuclear Deterrence

Before we get to glowing ravines and missile hiccups, you’ve got to understand the setting.

In 1967, Malmstrom Air Force Base oversaw one of the largest missile fields in America. According to official Malmstrom-hosted heritage materials describing the 341st Strategic Missile Wing (341 SMW):

Three 50-missile squadrons
Each divided into five flights
Ten missiles per flight
One underground Launch Control Center (LCC) per flight

By April of that year, the missile complex covered 23,500 square miles — making it the largest missile field in the United States.

That’s a whole lotta prairie.

Belt, Montana? That’s about 20 miles southeast of Great Falls. Wheat fields. Coulees. Deep ravines where headlights disappear at night.

I’ve crossed those ridges myself. Wind cuts sideways through your fur. Sound travels funny. And when a light shows up where no light should be? You notice.

The Night of the “Landing” Near Belt

On March 25, 1967, an UNCLASSIFIED PRIORITY message was transmitted from Malmstrom titled:

“Preliminary UFO Report”
Timestamp: P 251224Z MAR 67

It stated that between 2100 and 0400 MST, Malmstrom agencies received numerous UFO sighting reports in the Great Falls area. It also reported:

“Reports of a UFO landing near Belt, Montana were received from several sources including deputies of Cascade County Sheriff’s Office.”

Now that ain’t barroom gossip. That’s an official transmission.

You can view the declassified message pages here:
Internet Archive – Malmstrom Messages
https://archive.org/

The message noted that the site would be placed under surveillance. A sheriff’s ground search and a Malmstrom helicopter air search were scheduled. A follow-up report would come later.

And it did.

What Witnesses Claimed

According to the Project Blue Book case packet (hosted by NICAP):

Project Blue Book Belt Case File
http://www.nicap.org/

A truck driver reported seeing a “huge dome shaped object” emitting an intense bright light in a ravine around 9:00 p.m. on March 24. He said it lifted, then settled again. The sighting occurred near the Belt turnoff while he was heading toward Great Falls.

Now picture that. You’re driving a Montana highway at night in ’67. AM radio humming. Nothing but dark coulees around you. Then suddenly — a bright dome in a ravine.

I don’t blame the man for reporting it.

However, when law enforcement and Malmstrom personnel searched the area, both by ground and by helicopter, they found nothing.

No scorch marks.
No debris.
No craft.

Just prairie.

Why It Was Marked “Unidentified”

The case ultimately received a Project 10073 Record Card designation:

Conclusion: UNIDENTIFIED

Now before someone hollers, “See! Aliens!” — let’s be careful.

According to the Department of Defense’s 1966 Project Blue Book explanation:

Project Blue Book Explainer (DoD)
https://www.archives.gov/

Blue Book categorized reports as:

Identified
Insufficient Data
Unidentified

“Unidentified” meant the report contained enough data, but the object could not be matched to known phenomena. It did not mean extraterrestrial.

That distinction matters.

The National Archives further explains Blue Book’s evaluation system here:
https://www.archives.gov/

Meanwhile, reporting procedures were governed under Air Force Regulation 200-2, which required prompt reporting and electrical transmission within three days of a sighting.

AFR 200-2 Background
https://www.archives.gov/

So the quick “Preliminary” message followed by a detailed investigation? That was standard procedure.

Still… unresolved is unresolved.

And Montanans don’t forget unresolved.

Eight Days Earlier: The Echo Flight Shutdown

Now let’s rewind to March 16, 1967.

A declassified Strategic Air Command (SAC) message — originally marked SECRET and later declassified under EO 12958 — carries the subject:

“Loss of Strategic Alert, Echo Flt, … Malmstrom AFB”

It states:

“All ten missiles in Echo Flight at Malmstrom lost strategic alert within ten seconds of each other.”

Time: 0845L
Date: 16 March 1967

The message continues:

The missiles were restored to alert.
The cause was unknown at the time of writing.
Guidance and control computers were “upset momentarily.”
SAC called it a matter of “grave concern.”
An urgent, in-depth analysis was requested.
Boeing engineers requested access to logs and interviews.

You can view the declassified SAC message here:
Internet Archive – SAC Message
https://archive.org/

Now listen close.

It does not mention UFOs.
It does not mention lights.
It does not assign blame.

It documents a simultaneous alert loss and headquarters-level concern.

And that alone is enough to make Cold War brass sit upright.

What “Lost Strategic Alert” Actually Means

In plain English, “alert” means the missiles were in ready status to respond to an authenticated presidential order.

“Lost strategic alert” means they were no longer in that ready condition until restored.

It does not mean they launched.
It does not mean someone almost turned keys.

However, a near-simultaneous shutdown of an entire flight suggests something systemic. That’s likely why SAC demanded urgent analysis and asked about fleet-wide implications.

That inference comes from the tone of the message itself — especially the phrase “grave concern.”

When nuclear deterrence is your job, you don’t shrug at ten missiles blinking out together.

Are The Two Events Connected?

Here’s the honest truth from the paperwork:

The Air Force documents show a UFO report surge near Belt on March 24–25.
They show a missile alert loss on March 16.

They do not connect them.

Same region. Same month. Same base.
But no official causal link appears in the primary messages.

And sometimes, that gap is what fuels the legend.

Why This Story Still Lives in Montana

Great Falls has long been part of UFO lore, especially since the 1950 Mariana incident. The Great Falls History Museum maintains clippings and vertical files on that case and other sightings.

Great Falls History Museum Blog
https://www.greatfallshistorymuseum.org/

Montana towns remember what Washington forgets.

I’ve heard old-timers in Cascade County swear something lit up the coulees that week. I’ve also heard former missileers say the hum in those underground capsules could get downright eerie.

Now I ain’t sayin’ little green men strolled through Belt.

But I am sayin’ this:

The paper trail is real.
The missile shutdown happened.
The Belt landing was reported and investigated.
The result was “Unidentified.”
And no official explanation tied it all together.

That’s not conspiracy.
That’s documentation.

Where the Records Live Today

If you want to dig deeper, the National Archives maintains Project Blue Book textual records on 94 rolls of microfilm (Publication T-1206).

Guide to Blue Book Records
https://www.archives.gov/

They also list relevant record groups, including RG 341 (Headquarters U.S. Air Force), here:

NARA UFO/UAP Record Groups
https://www.archives.gov/

The files are public.

Dusty. But public.

A Final Word From the Treeline

I’ve seen northern lights dance over the Highwoods like green fire. I’ve watched meteors split the sky clean in two. And I’ve heard machinery hum under prairie soil in ways that make your molars ache.

So could ten missiles glitch?

Sure.

Could a trucker misjudge a bright light in a ravine?

Absolutely.

Could something stranger have happened?

Well now… I wasn’t in that capsule, and I wasn’t in that ravine.

But I was in Montana.

And when the wind moves across 23,500 square miles of fenced-off prairie, it carries stories with it.

The files show procedure.
They show urgency.
They show uncertainty.

And uncertainty, my friends, is where folklore takes root.

Keep your boots on the ground.
Keep your eyes on the sky.

Because out here in the 406… both deserve attention.

The 406 Life

What Happened at Malmstrom?