UFO files: TIMOTHY radar detection of unknown blip near Seattle, 22 June 1954

The latest drop from the Dept. of War UFO 03 document release has surfaced a crisp 1954 radar log that places an unknown blip on TIMOTHY radar just north of Seattle. The incident lasted ten minutes, triggered two fighter scrambles, and left no physical trace behind. It is the sort of tidy, time-stamped case that keeps modern analysts comparing notes with today’s sensor data.

Radar scope lights up

The TIMOTHY radar control scope first registered the contact at 0314Z on 22 June 1954 in georef square LE 1604. Controllers logged an estimated speed of 200 knots and an altitude of roughly 15,000 feet. The track appeared, vanished, then reappeared twice more before disappearing for good.

Each return lasted only seconds, yet the spacing suggested deliberate movement rather than random noise. No known aircraft schedule matched the coordinates or timing. The brief window forced the crew to decide quickly whether they were seeing weather, a misidentified flight, or something else.

Within moments the console crew passed the plot to MERCURY, the 25th Air Division’s Direction Center. Standard intercept protocol kicked in without debate.

Two F-86Ds get the call

MERCURY vectored Pronto Blue #1 and Pronto Blue #2, a pair of F-86D Sabres from the 317th Fighter Interceptor Squadron. The jets were already on alert status and launched within minutes of the hand-off.

Both pilots carried roughly 145 hours in the Sabre and more than 270 total fighter hours. Their combined experience gave the ground controllers confidence that any visual confirmation would be reliable.

Radio traffic between the pilots and MERCURY remained clear throughout the short chase. No civilian or military aircraft admitted to being in the area at the time.

Ground observers join the net

An additional 25th Air Division pilot flying a T-33 trainer overhead heard the entire exchange. His vantage gave controllers a third set of ears on frequency, reducing the chance of misheard coordinates.

The T-33 pilot reported no visual contact of his own, yet the shared channel kept everyone synchronized on the blip’s last known position. That redundancy mattered when the target dropped off TIMOTHY’s scope for the final time.

Ground radar and airborne observers together formed a closed reporting loop typical of 1950s air-defense drills, now preserved in the declassified packet.

Ten minutes and out

The entire sequence, from first ping to final fade, spanned ten minutes. After the third and last return, TIMOTHY logged the contact as off-scope and did not reacquire it.

Controllers noted the intermittent nature of the track but recorded no equipment faults or weather returns that could explain the pattern. The brevity left little room for follow-up collection.

By the time the Sabres reached the last plotted location, the sky was empty. The mission log closed with the simple notation “no contact.”

What the log leaves open

The FBI memo that captured the incident offers no conclusion on the blip’s identity. It simply forwards the 25th Air Division summary to Wright-Patterson’s Air Technical Intelligence Center for further study.

Weather records, commercial flight plans, and nearby balloon releases have never been cross-checked in the released file, leaving analysts to wonder whether mundane sources were ever ruled out.

The absence of those checks is common in period reports; the emphasis was on rapid response, not exhaustive explanation.

Chain of command at work

The hand-off from TIMOTHY to MERCURY to the alert fighters illustrates how 1954 air defense treated every unknown return as potentially hostile until proven otherwise. The process was automatic once the scope lit up.

Each station logged its actions in real time, creating the paper trail now sitting in the Dept. of War UFO 03 release. Those contemporaneous notes are what give the case its value today.

Modern radar analysts still study the same sequence to test how today’s software would classify the same brief, intermittent return.

Why the record matters now

The Pronto Blue scramble shows that interceptor response times in 1954 were already measured in minutes, not hours. That speed benchmark is still referenced when current commands run similar drills.

The TIMOTHY radar detection also supplies a fixed latitude-longitude box and an exact clock time, two data points that let researchers overlay wind, temperature, and known traffic from the same evening.

Few 1950s cases arrive with such narrow parameters, which is why this single page continues to circulate among UAP historians.

Comparing sensor limits then and now

TIMOTHY’s ten-minute window highlights the mechanical constraints of vacuum-tube radars: narrow beams, manual tilt, and film-plot logging. Today’s phased-array sets would likely hold the track longer.

Yet the human loop—scope to controller to pilot—remains structurally unchanged. The 1954 transcript therefore functions as a baseline for measuring how much the technology layer has improved while the decision chain has stayed constant.

That continuity is one reason the file keeps resurfacing whenever agencies revisit historical sensor performance.

Paper trail ends here

The released memo stops at the hand-off to Wright-Patterson. No follow-up telex or ATIC evaluation appears in the same folder, so the ultimate classification of the blip is still unknown.

Researchers can only note that the case file carries no “identified” stamp and no “balloon” or “aircraft” notation, leaving the entry in the open-file category.

For now, the TIMOTHY radar detection stands as one cleanly documented moment when an unknown return prompted two jets to chase empty sky over Seattle.

Forward glance

Archivists expect more granular radar logs from the same era to surface in later Dept. of War UFO 03 tranches. Each new page lets analysts refine speed, altitude, and response-time models that still guide today’s intercept doctrine. The 1954 Seattle blip remains the earliest precisely timed example in the current release, a single data point that continues to anchor the conversation.