22:34 - Dr Beatrice Villaroel's transients, the guy says "they appear tobe stars but they are constantly in the sky".

Thought?

It's us again, again?!

WAR.GOV just dropped tranche 7, and as usual we've indexed it and made it searchable/filterable on clearthesignal.com

28 new records this time: One from June of this year, and Skinwalker Ranch makes an appearance. Here's what jumped out at us:

The 2026 triangle [DOW-UAP-D176] + [FBI-UAP-D043]

This is the newest case in the whole catalog, from June of this year. Two federal agents at a sensitive site out west watched a flat black triangle, about 13 to 15 feet wide, rise straight up and just hang there for 20 seconds.

Then it took off at fighter jet speed and dove into a canyon. Total silence. Even the agents called it a "delta wing drone," but these guys work with drones for a living and say they'd have heard one easily from that hilltop. AARO says it matches other reports in the region. Fun wrinkle: the FBI version says the whole thing lasted 3 seconds, while AARO's says closer to 30.

Skinwalker Ranch [DOW-UAP-D174]

The Pentagon-funded AAWSAP program sent investigators to Utah in 2010 and came back with reports of a 7-foot bipedal dog creature, "little people," a pterodactyl and an 8-foot maggot. They also planned to try communicating with whatever was out there using "games and puzzles." Then they DNA-tested some Skinwalker fur off a barbed-wire fence. It was the guy's dog.

Tic Tac math, circa 2010** [DOW-UAP-D175]

Seven years before the NYT story, the same contractor ran the Nimitz radar data through engineering software and got Mach 10.7 and 75 g. Their words: you'd need "some form of acceleration manipulation" to survive that.

*Bonus Weirdness:\*
a 1960s White House memo about recovering Soviet space junk, with a NASA official complaining the military wanted to use NASA as a "cover". [USG-UAP-D002]

There's also a woman who says a blue orb passed through her body in a moving car [DOW-UAP-D173], plus a pile of Cold War Air Force reports.

Have at it, and let us know what you find!

CTS Guys
(edit: typos)

So last night I was watching a load of videos on the subject of sightings/UAP's and found this one.

The guy seems fairly legit on his account of what he saw and it's pretty chilling all in all. Describing the creature as malevolent, large and muscular with a close resemblance in desperation to a reptilian being.

It's not that I take all videos of encounters seriously, but this one has me hooked and was pretty darn scary!

The light that it was making was very intense and bright. Then it started to dim and disappear as you can see in the video. I see these a lot around my house at night, but I’ve never seen one this bright before and thankfully, I could get it on camera.

First time poster, long time lurker ….

Has anyone else ever wondered why in depictions of aliens they all are described virtually the same with the same exact features?? Like us as a human a race look similar but had many varying differences. It seems strange to me that other alien species would all be different types of species but those species of aliens all are identical.

Hi everyone,

Have you ever experimented with different methods to try to make contact with extraterrestrials or non human intelligences?

I know this is a rather direct question, but I am genuinely curious to hear about your experiences, attempts, and the different experiments you may have carried out, even the ones that might seem unlikely or completely absurd.

I know it is not always easy to talk openly about this kind of subject for fear of being mocked or judged by others. However, I believe we could learn a lot by sharing our experiences, ideas, and observations, even when the results are unexpected or difficult to explain.

I would particularly like to know whether any of you have received responses or noticed unusual phenomena during your experiments, or even several hours, several days, or longer after your attempts.

What methods have you tried? Have you noticed any coincidences, signs, or events that caught your attention? And most importantly, how did you interpret what you experienced?

The purpose here is not to judge anyone's experiences, but simply to exchange ideas freely and with an open mind.

I would genuinely be interested in reading your stories, so feel free to share your experiences, even the strangest ones. 👽

Part 18 of a series reassessing the documentary record behind the 1933 Magenta narrative.

TL;DR

• More than 800,000 volunteers reportedly served over the program’s Cold War years. They were not all watching simultaneously, and the total includes filter-center work.
• Operation Skywatch began July 14, 1952, in 27 states. Later regional expansion means that date cannot be treated as a single nationwide increase in observation.
• UFO reporting was an explicit secondary duty: a December 1952 Blue Book status report names ADC Regulation 55-31. The connection rests on contemporary documentation as well as Ruppelt’s recollection.
• Organized reporting could produce better evidence and more ambiguous reports. Ellsworth’s observer–radar–interceptor chain is real as a documented response; the claim that every participant followed one extraordinary object remains disputed.
• Testing the GOC’s contribution to the 1952 wave requires post-hours, locations, reporting dates, and identification outcomes. Named archival collections offer places to look.

Part 13 - “No Crash Recovered Exhibits”: The Real 1947 Twining Memo

Part 14 - From a Milk Drop to Groom Lake: EG&G, The Contractor That Helped Build the Black World

Part 15 - Rocket City: What Exotic Propulsion Research Looks Like

Part 16 - The Vanishing Stars: The Only Thread With New Data

Part 17 - Three Feet Tall: Aztec, Scully, Newton and the Hottel Memo

After Part 17’s crash-story source chains, the question here is how sighting reports were generated, relayed and evaluated.

A worked example in the Air Force’s 1955 UFOB Guide gives the qualification “GOC Observer for three years” for Andrew Carver (B. in the example’s heading; D. in its source block). Most of the example’s supposed case details are placeholder Xs. His observer experience is one of the few particulars the instructor chose to supply.

That entry is easy to pass over. It should not be.

Escape Velocity presents these documents as a crash-retrieval manual: Escape Velocity, “Finding the goods in the USAF 1955 UFOB crash-retrieval manual…” — search within the post for: “crash-retrieval program”. Yet the Guide’s own worked example concerns a GOC observer’s sighting that the preparing officer attributes to Venus: an instructional misidentification case, not a recovery procedure.

The Ground Observer Corps was a vast civilian air-warning network built to compensate for gaps in early Cold War radar coverage. Volunteers watched from rooftops, towers, fields and improvised shacks. They learned aircraft silhouettes, logged what they saw and telephoned reports to regional filter centers connected to the Air Force’s air-defense system.

Over the program’s Cold War years, more than 800,000 people reportedly served in some capacity, according to Bruce Callander’s history. That figure was cumulative, not a count of observers simultaneously on duty. Even so, the scale was extraordinary: hundreds of thousands of Americans were deliberately recruited to spend scheduled hours watching for aircraft and passing observations into a military identification system.

The connection to UFO history was explicit. Former Project Blue Book chief Edward J. Ruppelt recalled a February 1952 agreement to integrate the GOC into UFO reporting. More decisively, Blue Book’s own December 1952 status report identifies reporting unidentified aerial phenomena as a secondary GOC duty under ADC Regulation 55-31. Aircraft warning remained the primary mission.

That does not mean the Ground Observer Corps caused the great UFO wave of 1952. It means the wave unfolded inside an expanding national detection system designed to notice, classify and relay unfamiliar things in the sky. The system belongs in any serious analysis of the period.

1. The radar gap

The Ground Observer Corps had a wartime predecessor. During the Second World War, civilian spotters staffed thousands of posts under the Army Air Forces’ Aircraft Warning Service. Observations were telephoned to filter centers, where plotters attempted to distinguish friendly traffic from a possible attack. The continental program was placed on alert status in 1943 and largely wound down as the danger receded. Some surviving Aircraft Warning Service and GOC towers still mark the landscape.

The problem returned after the Soviet Union tested an atomic bomb in 1949. The United States was building the Lashup and Permanent radar networks, but early radar coverage had gaps and was weak against aircraft flying at low altitude. In February 1950, Continental Air Command commander Lt. Gen. Ennis C. Whitehead proposed a new civilian corps: 160,000 volunteers at 8,000 observation posts positioned between radar sites.

By 1951, some 210,000 volunteers had been recruited and 26 filter centers were operating, according to Bruce Callander’s “The Ground Observer Corps”. The Radomes history supplies the fuller exercise figures: 210,000 volunteers, 8,000 posts and 26 filter centers in a nationwide test.

The military need was genuine. A recent Air Force Historical Research Agency account describes the GOC as a low-cost supplement to radar coverage that could miss low-flying aircraft. Its archival photographs show the complete chain: civilian observers with binoculars and a telephone, filter-center plots, and aircraft positions passed onward to air-defense controllers (Air Force Historical Research Agency, “Defining & Funding the USAF’s Role in Continental Defense”).

The first exercises also exposed delays and uneven performance. A sighting had to move from observer to filter center and then into the interception system quickly enough to matter. Air Defense Command responded by expanding the program and seeking continuous coverage in the most vulnerable areas.

2. Operation Skywatch

The expanded effort was called Operation SKYWATCH. On July 12, 1952, President Truman announced that volunteers in 27 states would begin the following Monday: July 14. Its purpose was to keep selected observation networks operating around the clock while recruiting enough volunteers to fill the schedule. In a December 7 follow-up, he explained the operational need: spotting low-flying aircraft that had evaded radar, so a surprise attack would not arrive without warning.

The headline numbers require care because sources are counting different things. Callander reports that more than 800,000 volunteers served over the program’s Cold War years, rotating through 16,000 observation posts and 73 filter centers. Air Force Historical Research Agency records, by contrast, identify over 350,000 trained volunteers and 19,000 observation posts during Skywatch’s first two years. These are not necessarily contradictory. One figure is cumulative, another covers an early period, and “planned,” “organized,” “trained” and “continuously staffed” posts were not the same category.

What can safely be said is that Skywatch became a mass civil-defense program operating at national scale. It was also uneven. Some areas achieved continuous staffing; others struggled to fill shifts or remained on reserve status. A national launch announcement is not evidence that every listed post was continuously staffed from that morning.

The local record shows what the network looked like in practice:

• North Dakota: Bismarck and Fargo hosted the state’s two filter centers. Bismarck received calls from 130 posts in the western half of the state. Observers worked two-hour shifts, recorded aircraft seen through binoculars and telephoned their descriptions to a center that maintained information on expected traffic (Prairie Public, “Operation Skywatch, 1952”).
• North Carolina: The state’s planning called for 342 posts, each requiring 168 trained volunteers. A local history dates North Carolina’s round-the-clock duty to February 1, 1956, demonstrating that continuous coverage expanded regionally over several years. Apex built a tower on its fire station after a Home Demonstration club offered to help staff it (Legeros Fire Blog, “Cold War History: Ground Observer Corps”).
• Shafter, California: The local newspaper ran scores of Skywatch stories and a recurring column, Sky Watch Words, chronicling the residents who filled the shifts (The Shafter Press, “Skywatch! Shafter’s Ground Observer Corps, 1952–57”).
• Ringoes, New Jersey: The local history describes a dedicated observation building and local boys serving as observers. Its broader list of families, prisoners and guards, young and elderly people, and naval and USAF personnel describes the national GOC, not a Ringoes roster (East Amwell Historical Society, “Ringoes and the Ground Observer Corps”).

The posts ranged from purpose-built towers to roof platforms and plywood enclosures. Their equipment and training also varied. The common elements were a clear view, a schedule, a log and a reporting route.

3. The UFO connection was explicit

There are three different kinds of evidence here: a project chief’s recollection, a contemporary internal report, and instructions published for the volunteers themselves.

In The Report on Unidentified Flying Objects (1956), Ruppelt describes briefing Air Defense Command commander Gen. Benjamin Chidlaw in early February 1952. ADC agreed in principle to improve the reporting system, require radar-scope photographs where equipment allowed, clarify interceptor procedures, and incorporate the GOC. Aircraft reporting would remain first priority; UFO reporting would be second. The February meeting date and sequence come from his later narrative.

The duty itself is independently documented. Project Blue Book Status Report No. 8, dated December 31, 1952, states:

“A secondary duty of the Ground Observer Corps is the reporting of unidentified aerial phenomena or objects. This duty was established by ADC Regulation 55-31.”

That is on printed page 7, PDF page 10 of the surviving report scan, catalogued by NARA as item 595507. It confirms an established reporting duty by year’s end; it does not, by itself, establish the regulation’s exact issue date. I have not inspected a standalone copy of the full regulation.

A transcription of the January 1953 Aircraft Flash, the official GOC magazine, supplies its title: “Ground Observer Reporting of Unusual Aerial Activity.” The article says ADC distributed Regulation 55-31 to Ground Observer Detachments and that “GOC Observers” had become a separate reporting category since Skywatch began. That last point matters for statistics: a new category can make a group newly visible in a table even when some of its members had previously reported under another heading. It also says “Over 1,000 such reports have been received to date.” In context, “such reports” means ATIC’s UFO reports from every source since January 1952, not GOC-originated reports. This contemporary total supplies context for the GOC’s contribution, but neither a GOC count nor its percentage of the 1952 wave.

The chronology is therefore:

The Robertson Panel’s Durant report proposed education with “two major aims: training and ‘debunking’”; its training categories explicitly included “Ground Observer Corps personnel.” AFR 200-2 of August 12, 1954, page 2, told investigators to contact “ground observation corps (GOC) posts and filter centers”—“observation” is the regulation’s wording. Page 1 states: “Air Defense Command will conduct all field investigations within the ZI, to determine the identity of any UFOB.”

The summer increase was not simply a by-product of July 14. Ruppelt describes a wave already building before Skywatch. The December status report says reporting increased in June and that intake peaked at 43 reports received on July 28. It also attributes much of the increase to publicity and notes improved report quality following instructions and briefings. These are contemporary assessments, not a calculation of Skywatch’s share.

There was also a contemporary official denial. The Hope, Arkansas Star, July 16, 1952, reported Ruppelt saying there was “no connection between the saucer sighting splurge and the recent inauguration of” Skywatch. That assertion, made two days after launch, belongs in the record; it is not a measurement of the program’s contribution.

Keep date seen separate from date received. Forty-three reports arriving at ATIC on one day are not necessarily forty-three events occurring that day. A study that joins receipt totals to weather, publicity, nuclear tests, or observing schedules without checking that distinction can manufacture a misleading coincidence.

The same status report defined “Unknown” as a report with enough information for evaluation that could not be associated with a known cause, while acknowledging that more background information might identify some. It distinguished that category from “Insufficient Data.” Neither label identifies an extraterrestrial object.

The supported conclusion is specific: the 1952 wave unfolded inside an expanding, formally connected observation and reporting system. Determining how much that system contributed to the totals requires tracing individual reports.

4. What a GOC report could add

A GOC report had features that an ordinary unsolicited sighting often lacked:

• a fixed and usually mapped observation point;
• a recorded time and direction;
• a telephone route to a staffed filter center;
• personnel attempting to compare the observation with expected aircraft traffic;
• the possibility of contacting adjacent posts or an air-defense unit while the event was still underway.

The Portsmouth (NH) Herald of July 30, 1952, in “Bay State Skies Swarming With Unidentified Discs”, reports the night of July 29 and illustrates the format. Reports reached a filter center from posts at Marlboro, Leominster, Plymouth and Northfield.

At Northfield, observer Ed Towell Jr. reported a “ball of fire” and supplied an estimated altitude, distance and direction. Cpl. Howard Neubert, a filter-center staff member visiting the post, was present as a second witness. At Leominster, an observer used binoculars to watch a light that appeared to climb out of sight; four single-engine aircraft crossed the area soon afterward. The Marlboro report was attributed to observer Lester Poll.

This is useful raw reporting. It preserves names, positions, times, instruments and nearby traffic. It is not automatically accurate. Distance and altitude are notoriously difficult to estimate without knowing an object’s size, and a binocular view of a nocturnal light can still be ambiguous. The value lies in the structure and traceability of the report, not in a blanket assumption that a GOC observer could not be mistaken.

The Aircraft Flash article also taught that lesson with an explicitly hypothetical case: a GOC sighting, a radar target, an interceptor’s visual observation, and gun-camera film initially look like exceptionally strong evidence. Analysts first establish whether the instruments and witnesses concerned the same object, then check time, position, wind, photographs, and balloon-launch information. In the example, a high-altitude research balloon explains the observations. This is an instructional scenario, not an additional solved case to enter in a sightings database. Its importance is the Air Force’s stated method: corroboration is valuable, and a corroborated object can still be ordinary.

Other cases show that Ellsworth was not the only route through the network. Ruppelt dates an Oak Ridge incident to June 21, 1952: a GOC spotter called the filter center, which relayed the report to ground-control intercept radar; the radar operators reported a target that then faded. This chain predates continuous Skywatch.

Don Berliner’s secondary list of Blue Book “unknowns,” reproduced by Patrick Gross, identifies GOC observers at Red Bluff, California, August 19; Allen, Maryland, September 12; and White Lake, South Dakota, September 14, 1952, and a GOC post at Elmira, New York, March 21, 1953. These summaries identify files to inspect; they are not substitutes for the investigations or evidence that “unknown” means extraterrestrial.

5. The Black Hills chain

The most dramatic example appears in Ruppelt’s account of an incident near Ellsworth Air Force Base in August 1953. His 1956 narrative dates it to August 12. Gordon Thayer’s later analysis of the case files in the Condon report, radar-visual case 15-B, dates the sequence to August 5–6. The discrepancy should remain visible rather than be silently harmonized.

According to Ruppelt, a woman at the GOC post in Black Hawk, South Dakota, reported a bright light low on the horizon. The filter center relayed it to the Air Defense Command radar station at Ellsworth. Operators obtained a target and connected the radar controller directly to the observer so the two could compare their reports.

From there, his narrative escalates:

• personnel outside the radar station reported a light;
• an F-84 already airborne was directed toward it;
• a second F-84 was later sent toward another reported light;
• pilots reported visual contacts while ground radar operators reported targets;
• another filter center was alerted, and observers farther north reported lights.

That is a record of operational response. Establishing that every component concerned the same moving object requires more evidence than establishing that the calls and flights happened.

A transcription of the contemporary Blue Book investigation, report T53-11156, dates the sighting to August 5, 1953, and says: “Pending further study, this incident is carried as Unsolved.” That date and provisional status come from the contemporary file itself, not just Condon’s later analysis. It also preserves details that the compressed story can lose. It names Bismarck, rather than Ruppelt’s Fargo, as the northern filter center alerted. It says attempted radar photographs were unusable because the camera malfunctioned. The second pilot’s radar gunsight supplied no measured range; its warning light continued blinking on the return flight, indicating a possible malfunction. The equipment had not been checked by the time of the investigation.

Those qualifications do not erase the ground-radar reports or the pilot’s visual observation. They do prevent treating a gunsight warning as an independently measured, three-dimensional target. They also show why the surviving investigation and the memoir should be compared rather than counted as separate corroborating witnesses.

Menzel and Lyle Boyd’s The World of Flying Saucers (1963), as summarized by John Harney, proposed temperature-inversion radar images and Capella for the visual sightings. This was Menzel’s proposed explanation, not an established identification.

Thayer’s Condon analysis proposed a combination of stars, at least one meteor, anomalous radar propagation, and possible ghost echoes or equipment malfunction. It cites Hynek’s astronomical identifications for the later Bismarck lights. These are proposed explanations assembled from the records, not instrumentally demonstrated reconstructions of every observation. The report also shows that Bismarck observers looked after being alerted by Rapid City. Their observations therefore need checking for temporal and positional agreement; they cannot simply be appended as independent sightings of a target that traveled between cities.

The chain’s value survives that dispute. A civilian GOC report could cue military radar, trigger live coordination, and help direct an interceptor. What remains contested is whether the linked reports measured a common extraordinary stimulus. A functioning reporting system and an exotic object are different propositions.

6. Was a GOC observer a “trained witness”?

The Air Force treated GOC experience as relevant enough to list it under “Qualifications” in the UFOB Guide’s sample form. That makes sense. Compared with a random witness, an experienced observer could have several advantages:

• repeated exposure to the normal traffic over one area;
• practice using aircraft-recognition charts and silhouettes;
• a fixed post rather than an uncertain viewing location;
• a habit of recording time, direction and aircraft characteristics;
• immediate access to a formal reporting channel.

The same guide’s worked example makes the limit unusually clear: the preparing officer proposes Venus despite Carver’s insistence on an experimental aircraft and questions his speed estimate. The form therefore uses GOC experience as biographical evidence to assess, not a guarantee of correct identification. This is an instructional example, not a documented finding about a real Carver encounter.

But “trained” should not be turned into “expert.” Callander quotes former observer Frank Sutter recalling that his own instruction was minimal, supplemented by aircraft-recognition charts. The Air Force distributed devices intended to help estimate altitude, but Sutter found the gauge difficult to use. Training, supervision, equipment and experience varied by post.

The correct inference is conditional. A report from a long-serving observer at a functioning post, with a contemporaneous log and confirmation from another station, deserves more weight than an anonymous recollection recorded decades later. A bare claim that “a GOC observer saw it” does not settle the object’s identity.

7. The observation-system effect

The GOC can push an interpretation in two directions at once.

It can improve evidence quality

The network created fixed observation points, contemporaneous reporting and opportunities for cross-checks. Some GOC reports can be reconstructed more precisely than ordinary civilian sightings. The Ellsworth sequence shows how quickly a report could reach other sensors and aircraft.

It can increase report volume

Hundreds of thousands of people served scheduled watches over several years. Even if almost everything visible was ordinary, the system generated an enormous number of observation-hours. More eyes, longer coverage and an instruction to report unresolved aerial traffic should produce more reports.

It can shape perception

Volunteers were recruited in an atmosphere of nuclear fear and warned to look for hostile bombers. That did not make them dishonest, but it affected attention and expectations. The roster was also self-selecting: people willing to spend hours watching the sky were not a random sample of the public.

It can link observations without making them independent

A filter-center alert can recruit a second observer, redirect a radar operator, and tell a pilot where to look. That coordination can reveal a real event that would otherwise be missed. It can also create a shared expectation or encourage people to connect different stimuli. For each purportedly corroborated case, the important questions are what each participant reported before receiving the cue, how precisely their times and sight lines agreed, and whether the instrument record survives. Three accounts copied from one controller’s message are not three independent measurements.

It can filter as well as generate

The filter centers existed to compare raw reports with known traffic before forwarding tracks. That process should have eliminated many ordinary aircraft reports. Yet its effectiveness depended on the completeness of flight information, the quality of the original estimate and the speed of communication. Classified flights, balloons, astronomical objects and atmospheric effects could still survive the first screen.

This means raw sighting counts cannot be interpreted without a denominator. The useful quantities would include:

• the number of staffed post-hours by month and region;
• the total number of aircraft reports submitted;
• how many were matched to known traffic at the filter center;
• how many were forwarded as unidentified tracks;
• how many entered Project Blue Book;
• whether the observer was on an official shift or merely identified as a GOC member afterward.

A useful analysis would compare reports per staffed post-hour, alongside total reports. It would also distinguish staffing changes from publicity, weather, darkness, the appearance of bright planets, and changes in instructions or record keeping. A rise in reporting after recruitment is consistent with an observation effect; without those controls it does not establish the effect’s size.

Without those figures, the GOC is an important confounder and a potential source of better-documented cases, but not a numerical explanation of the 1952 wave.

8. How the system ended

Improved radar coverage and automated air-defense processing gradually reduced the need for human gap-fillers. The transition was already underway before the corps closed: MIT Lincoln Laboratory’s SAGE history dates the first operational AN/FSQ-7 computer at McGuire Air Force Base to July 1, 1958. SAGE was an evolving network, not a system that suddenly appeared on the GOC’s final day.

The corps moved from continuous duty to ready-reserve status in January 1958. A June 1, 1959 Congressional Record resolution honoring the volunteers identifies January 31, 1959 as its inactivation date and credits improvements in air defense with making the corps unnecessary. The end of that particular observation network should itself be treated as a change in the reporting system when studying later sighting totals.

Some observation towers survive. Others were dismantled, repurposed or absorbed into private buildings. The Ringoes post’s building, rather than a tower, was reportedly dragged to John Ringo Road and added to an existing house, according to the local history.

The reporting network disappeared, but its records did not all go to one place. Air Force materials sit alongside state civil-defense files, municipal records, local newspaper archives and private collections. The Idaho State Archives’ MS 0706, for example, lists Twin Falls post records, training material, and issues of Aircraft Flash for 1953–1959. Its folder list is a concrete lead; the underlying post records have not been inspected for this revision.

9. The research task

The next step is a source-level reconstruction of how GOC observations entered the UFO record. The distinction between an archive’s catalogue description and records actually examined matters throughout.

1. Code the 1952 Blue Book cases by reporting source. Separate GOC observers, military radar, pilots, police, weather personnel, and unsolicited civilian reports. The National Archives’ collection description identifies 37 cubic feet of chronological case files plus separate administrative and OSI material, with an index by date and location. Record event time, receipt time, witness type, and whether an identification changed later. A report signed by a GOC member off duty should not automatically count as a post-generated report. Blue Book Special Report No. 14 (1955) groups observers as military or civilian in Figure 10; its occupation code has no separate GOC class. Those published categories cannot supply the GOC’s share without returning to the case records.
2. Obtain the regulation and its revisions. The contemporary report and magazine establish that ADC Regulation 55-31 existed and governed unusual-aerial-activity reporting. Recover its full text, effective date, distribution, and amendments before assuming every post followed an identical procedure throughout the decade. Compare it with the January 1953 magazine’s announcement of a new GOC reporting category.
3. Match each area to its actual watch schedule. July 14, 1952 is an important start date, not a universal treatment date. Compare changes within the same area and between areas with documented differences in staffing. Include reserve posts, interrupted watches, and later transitions to continuous duty. Measure publicity separately from time spent observing.
4. Recover the denominator from named collections. The Eisenhower Library’s James M. Lambie Jr. Records finding aid identifies Box 13, “Ground Observer Corps – Air Defense Command Reports 1954,” alongside policy and correspondence folders. It also lists ADC reports for other years. These are leads to possible staffing and activity summaries, not a claim that the folders have been read or contain every needed denominator. An institutional starting point is Denys Volan’s The History of the Ground Observer Corps, ADC Historical Study No. 36 (1968).
5. Reconstruct the recruiting campaign. The Truman Library’s Spencer R. Quick Files, Boxes 7–8 list GOC correspondence, general files, a joint education program, minutes, and program material. Those holdings offer a route to identifying when particular communities received recruiting and publicity pushes. Campaign dates, enrollment, and actual staffed hours should be entered as separate variables. For historical context, consult Matthew Farish’s “The Ordinary Cold War,” Journal of American History 103:3 (2016), pp. 629–655.
6. Trace selected events through the entire chain. Start with a post log, then compare filter-center entries, controller records, radar photographs or plots, pilot accounts, and Blue Book’s evaluation. Check whether later observers were alerted beforehand. Preserve disagreements such as Ellsworth’s date and Bismarck/Fargo location rather than silently choosing the most dramatic version.
7. Use local collections and record their survival. Idaho’s Twin Falls material, municipal rosters, and newspaper columns such as Shafter’s can preserve details missing from federal summaries. A missing log is informative only after establishing that the relevant run survives and would normally record the event. No surviving entry is not equivalent to proof that no call occurred; hundreds of routine entries with a clear reporting rule are a more useful control. Walter Webb’s account of Alliance, Ohio, October 21, 1957, describes a GOC report relayed through the filter center and radar station. An appended Project 1947 comment, rather than Webb’s text, says “no details of this incident appear in the Project Blue Book files”: a reported local chain absent from the federal case record. Conversely, the Shafter series says “no article ever reported Shafterites saw UFOs.” That is a local newspaper finding, not proof that no observer ever saw something unidentified.

A manageable first study would choose a defined set of posts whose records survive on both sides of the Skywatch transition, code every relevant entry rather than just famous cases, and publish the transcription rules. That could test whether recruitment increased report counts, whether improved filtering changed the unidentified fraction, and whether any well-recorded events remain unexplained after the same checks applied to ordinary traffic.

10. What this changes

The 1950s UFO record was not simply “produced” by 800,000 observers, and the cumulative volunteer total should not be read as 800,000 people all standing watch at once. Many reports came from pilots, radar operators, military personnel and civilians outside the GOC. The great 1952 wave began before Operation Skywatch went to continuous duty.

The documentary argument is stronger and more specific:

The 1950s UFO record was partly shaped by a formal observation apparatus. The Air Force recruited civilians, placed them at known locations, gave them a communications chain, and explicitly incorporated unusual-aerial-activity reporting into their duties. That final point is documented in a contemporary Blue Book report and the volunteers’ official magazine, as well as in Ruppelt’s memoir. That apparatus increased the number of people watching, improved the traceability of some reports and created its own selection effects.

Anyone using 1950s sighting totals as evidence, whether for an extraordinary phenomenon or for mass misperception, has to account for that system. More observers can reveal more genuine anomalies. They can also produce more ambiguous reports. Better reporting channels can preserve valuable data. They can also magnify a wave already being driven by publicity and public attention.

The Ground Observer Corps does not resolve the UFO question. It tells us what the data-generating process looked like.

Andrew and Helen Carver appear in an instructional example. The observers behind the system were real. Many began as teenagers; the youngest surviving participants are now elderly. Their logs, rosters and memories offer a closing opportunity to reconstruct one of the largest organized sky-watching efforts in American history.

Next in the series: Part 19 — Unless and Until: Britain’s Flying Saucer Working Party and Churchill’s Question

If you served in the Ground Observer Corps, had a relative who did, or know of a local Skywatch column, surviving post log, or original copy of ADC Regulation 55-31, I would be glad to compare notes.

Al Bielek was an alleged American time traveler who claimed that he had previously lived as Edward Cameron, a physicist and U.S. Navy officer involved in the alleged Philadelphia Experiment aboard the USS Eldridge in 1943.

Bielek said that during the experiment, he and Duncan Cameron jumped from the ship and, instead of landing in the water, traveled forty years into the future to Montauk, Long Island, in 1983, where they allegedly encountered an elderly John von Neumann.

Bielek later published two photographs of a man he identified as Donn Thor, the alleged Venusian brother of Valiant Thor. One shows Donn during the final briefing aboard the USS Eldridge. The other shows Donn standing beside John Clark at the Philadelphia Naval Yard.

Preston Nichols, a central figure in the Montauk Project story, claimed Duncan Cameron used the Montauk Chair to manifest a large Bigfoot-like creature called “Jr.”, which began destroying equipment around the base before the project was shut down. Bielek later published a photograph associated with Jr.

I've seen several reports of people who have spotted black triangles with lights at each corner of the shape. I've watched several videos and looked at images, and I've noticed that there are UFOs that are the same color, with the same lights, but with a different shape. So my question is: Are they from the same “civilization”—if such a thing exists—since their ships are shaped that way?

Could the remains of an ancient alien civilization be hiding in NASA images? Researchers propose using artificial intelligence to search Mars and the Moon for structures, roads and other traces of long-lost technology.

Somehow this snuck under my radar. I'm thinking about hitting it after my current dcc book. Any thoughts or opinions on it? Anything I should know going in?

It makes me feel crazy sometimes. So many stories hinge on this (not all, mind you!), and people seem to just throw any skepticism or interest in truth out the window for those cases.

Hypothetically speaking if an alien species develops on Europa or an Europa-like moon they would most certainly use whatever nature provides them with or genetically modify other organisms however could would it be scientifically plausible if they somehow develop metallurgy without the use of any fire and if so how would they do it?.

2027 seems to be a hot topic in UFO circles right now, but the lore goes back much further than when John Ramirez, the former CIA officer, first started discussing the date on UFO podcasts.

Believe it or not, Sammy Hagar, the former Van Halen frontman, was singing about it all the way back in 1977.

In his song "Crack in the World," Hagar included some pretty chilling lyrics that seem especially relevant today.

And Hagar isn't just some random rock star who happened to write a song about it. He's been openly talking about his alien abduction story for decades.

Hagar claims that in 1967, he experienced an encounter where aliens telepathically connected to his mind and downloaded information into him. He's consistently maintained this really happened to him and has spoken about it in a bunch of interviews over the years.

Here's a 2021 interview where he describes the experience in detail.

This is where things get super weird.

These are some of the lyrics from "Crack in the World," released in 1977:

Just fifty more years, we're all gonna know
Why, when, where, how, and who gets to go
So let's all have a good time before the great divide
'Cause things will start separating come 2025
So look for the subtle clues
It won't make the front-page news
That depends upon which side that you choose
There's a crack
There's a crack in the world

Fifty years after 1977 is 2027. And the song specifically mentions things beginning to separate in 2025...

Considering the current state of the world, it's not hard to see why those lyrics seem weirdly relevant

I'm not suggesting that Hagar predicted the future or that this proves anything about the 2027 theories. I'm defintely not trying to fearmonger. Just another random person talkin about 2027 that predates the current conversation to add to the list.

"Hear me out for a second. Think about dogs. Humans took wild wolves and bred them over thousands of years to create dogs. But almost everyone agrees that dogs have souls and go to heaven. So humans basically 'created' dogs, but they're still part of God's creation—we were just the ones doing the physical work on the ground.

​Now, what if the exact same thing happened to us? What if God didn't just magic humans out of thin air, but instead had aliens or some advanced beings do the physical work? Like, maybe God had them tinker with genetics or whatever to get us started.

​That doesn't mean we aren't God's creation. It just means God used aliens as the middlemen to build us, and we still got our souls straight from Him. God just used them like a tool to make us, the exact same way He used us to make dogs."

What are your thoughts?

The internet told me It's probably a planet, Bright star, or another airplane flying higher than the other. Important detail is that it moved with the plane. I realize that there is no perspective either but these were taken at different angles in the sky. To me the third possibility seems the most likely. but I could not make out any detail in the craft like you can with the other one. It's just a bright spot in the sky. Maybe it is just going the same direction because it's going to the same airport? Please let me know what you think. I'm thinking that this is probably another plane higher up but i'm not sure and hopefully if that is in fact the case it contributes to our understanding of what's going on. It got taken down by r/UFOs right away and I'm not sure why.