The "Orbs Launching Orbs" Western United States Event

Theoretical Alignment

This case aligns weakly with all three major frameworks and strongly with none of them. AARO's own residual "Unrecognized Technology (Pending)" label is explicitly not an anomalous-origin finding — it is an admission that roughly 40 percent of the reported activity could not be matched to a known cause using the data available, which is a very different claim from evidence of non-human origin. The Psycho-Social Hypothesis gets its highest rating here of any framework because six trained federal agents observing ambiguous nighttime light sources under stress, expectation, and each other's influence is exactly the profile misperception researchers study — though the FBI's own assessment that the witnesses were highly credible, the AARO-confirmed flare exercise for roughly 60 percent of the activity, and the specific, physically-argued objection to the flare explanation for the stationary orb complicate a pure misperception reading. No craft morphology, propulsion signature, or occupant claim of any kind appears anywhere in the released record, which is precisely why this case resists confident alignment with the Extraterrestrial or Interdimensional Hypotheses despite the vivid witness language.

Background

On February 19, 2026, President Donald Trump directed the newly renamed Department of War (formerly the Department of Defense), with support from the Office of the Director of National Intelligence, to conduct a government-wide effort to find, review, declassify, and publicly release unresolved UAP-related government records. The resulting program, the Presidential Unsealing and Reporting System for UAP Encounters — abbreviated PURSUE and hosted at war.gov/UFO — began publishing tranches of declassified files on a rolling basis starting May 8, 2026. Then-Secretary of War Pete Hegseth described the effort as intended to give "unprecedented transparency" to files that had "long fueled justified speculation." By its fifth tranche (August 7, 2026), PURSUE had released files drawn from at least the Department of War, the FBI, and NASA, and the war.gov/UFO portal had reportedly logged well over a billion page views.

PURSUE's own published directive is explicit about what the materials in its database actually represent: cases the government "is unable to make a definitive determination on the nature of," a status the directive notes can result simply "from a lack of sufficient data" rather than from any genuinely anomalous quality in the case itself. This distinction matters directly for the case documented here. It is not a UFO video, a radar track, or a piece of recovered material — it is a formal All-domain Anomaly Resolution Office (AARO) analytical memorandum, catalogued as DOW-UAP-D077 and titled "Unresolved Case Analysis Update: Western United States Event," documenting AARO's own investigation into a two-night cluster of sightings reported by federal law enforcement personnel in October 2023. AARO, created within the Department of Defense in 2022 to consolidate the U.S. government's UAP investigative and resolution function, had by mid-2026 built a substantial public track record of case-by-case analysis — from the Aguadilla, Puerto Rico FLIR case that Director Jon Kosloski resolved as balloons or sky lanterns, to the "Chandelier" infrared clip released under the same PURSUE program, still formally unresolved. The Western United States Event sits closer to the Chandelier end of that spectrum than the Aguadilla end: a case AARO itself investigated with real rigor, and could still only partly explain.

Unlike most of the Pentagon's better-known UAP disclosures, this case did not originate with combat aircrew, sensor operators, or intelligence analysts. Its witnesses were federal law enforcement special agents, on duty near an unidentified "sensitive national security site" — the kind of facility the government polices and patrols rather than flies over. That distinction shapes almost everything else about the case: it explains why the site itself has been treated with a level of location secrecy unusual even by PURSUE's own standards (no state, no installation name, no coordinates — a redaction more thorough than AARO applied to most other Release 03 files), and it explains why AARO's own investigative toolkit leaned so heavily on flight logs, radar, and ADS-B correlation rather than gun-camera or targeting-pod footage, since none of the witnesses were operating aircraft or sensors of their own.

Complete Timeline

Date	Event
October 2023 (Night 1)	At dusk, agents from at least one of the three two-person teams stationed near the redacted "sensitive national security site" report an orange "mother orb" appearing for one to two seconds at a time and releasing clusters of two to four smaller red "orbs," repeating the pattern multiple times over several hours. One agent equipped with night-vision goggles (NVGs) separately reports the orange orb crossing roughly 20° of sky in three to five seconds before mechanically "expelling" three red orbs, likened to "grapes being expelled from a basketball," which then move south in a line formation at roughly one-second intervals.
October 2023 (Night 1 or 2)	One agent, separately from the mother-orb sightings, reports an earlier roadway encounter: vehicle headlights appearing to "morph" into an orb-like light, then an "orb-like disk with a halo glow" hovering above the road; the agent attempts a vehicle pursuit at roughly 80 mph without closing the distance, and the object is gone by the time the agent reaches its last position.
October 2023 (Night 2)	A second night of observations follows the same broad pattern reported on Night 1. Across the two-night period, one red "orb" is reported remaining stationary above a ridgeline for several hours — a duration investigators later find difficult to reconcile with any known military flare's burn time or rate of descent.
October 2023 (following days)	Five of the six agents file individual first-person written narrative statements with their respective chain of command, describing what each witnessed independently. No photographs, video, or instrument data are captured by any witness at the time.
2023–2026	The case enters AARO's investigative backlog. Analysts cross-reference the witness accounts against military and commercial flight logs, radar returns, spatial/kinematic estimates, and ADS-B transponder records for the relevant dates, times, and geographic area.
February 19, 2026	President Trump directs the Department of War, with ODNI support, to review and declassify unresolved UAP records under the new PURSUE program.
May 8, 2026	PURSUE's first tranche (Release 01) is published at war.gov/UFO, including an early slide-format summary of the "Western U.S. Event" among roughly 160 other files.
June 5, 2026	AARO Director Jon T. Kosloski signs the formal case-analysis memorandum DOW-UAP-D077, "Unresolved Case Analysis Update: Western United States Event," documenting AARO's completed cross-correlation analysis: roughly 60 percent of the reported activity is attributed to a military aircraft dispensing infrared countermeasure flares during a training exercise; the remaining 40 percent could not be matched to any known aircraft, drone, or natural cause and is classified "Unrecognized Technology (Pending)."
June 12, 2026	PURSUE Release 03 publishes the full Western United States Event case cluster — 19 files in all: the AARO analysis memo (D077), a notional incident map (D078), the five individual narrative statements (D079–D083), and ten FBI-produced digital renderings (FBI-UAP-D014–D023) reconstructing the witnesses' descriptions, plus reported digital video recreations. The release draws immediate national media coverage.

The Witnesses: Six Federal Agents, Three Teams, One Redacted Site

What makes the Western United States Event unusual within AARO's public case file — and part of why AARO itself has repeatedly described it as one of the more thoroughly documented incidents in its holdings — is its witness composition. This is not a single startled observer, and it is not a military aircrew reporting an anomaly encountered in the ordinary course of a mission profile designed to detect things. It is six federal law enforcement special agents, deployed specifically to guard a redacted "sensitive national security site," operating that night in three separate two-person teams stationed at different points around the facility's perimeter or approach routes. Three independent vantage points, watching the same general airspace on the same nights, each producing broadly consistent accounts without (per the declassified record) any indication of cross-contamination between teams in the moment.

Five of the six agents subsequently filed individual, first-person written narrative statements — catalogued as DOW-UAP-D079 through D083 — describing what they personally observed, largely independently of one another's language. The sixth agent's observations appear to have been folded into a teammate's joint account rather than filed as a separate standalone statement, which is the most plausible explanation for why press coverage describing "six agents" and official file listings showing "five narrative statements" are not in conflict; both figures come from the same underlying declassified record. According to reporting on the file, the FBI's own review of the witnesses concluded they were highly credible — a notable assessment given the FBI had no obvious institutional incentive to inflate the credibility of accounts describing behavior this unusual.

Crucially, none of the six agents' names are disclosed anywhere in the declassified record. AARO's release redacts identity along with location: no names, no home agency beyond the general description "federal law enforcement," no specific installation. This is consistent with PURSUE's broader practice on sensitive personnel and facilities elsewhere in its releases, but it does mean this case file cannot link named individual witnesses to key-figures cards the way many of this site's other case files do — the redaction itself is the documented fact.

What the Agents Reported

AARO's own memorandum preserves the witnesses' own descriptive language in quotation marks throughout — "orbs," "mother orb," "hatched" — while explicitly declining to adopt that terminology as an official technical classification, a distinction AARO says is necessary "to maintain the integrity of the narrative accounts" without prejudging what the witnesses actually saw. Stripped of that vocabulary, the reported pattern across multiple independent statements was remarkably consistent: a bright, orange, roughly circular light would appear low in the sky, generally visible for only one to two seconds at a time, and during that brief appearance would release — witnesses used verbs like "launch," "release," and "hatch" — a cluster of two to four smaller, distinctly red lights. The orange light would then disappear. The cycle repeated multiple times over a period described as "several hours" on both nights.

One statement, filed by an agent equipped with night-vision goggles at the time, offers the most kinematically specific account in the file. That agent described the orange orb crossing approximately 20 degrees of sky in three to five seconds before mechanically "expelling" three red orbs — a release the agent likened to "grapes being expelled from a basketball." The three red orbs then moved south in a line formation, spaced at roughly one-second intervals, before fading from view. A separate statement, attributed to "Witness 4" in AARO's internal file numbering, described losing count of the release cycles "after five occurrences," underscoring how repetitive and sustained the phenomenon was over the observation window rather than a single fleeting event.

The reported behavior of the red orbs themselves was the detail AARO's memo flags as the most analytically stubborn. Witnesses across multiple statements described the smaller red orbs exhibiting varied kinematic profiles: horizontal movement that "appear[ed] coordinated" between the individual orbs in a cluster, and apparent changes in altitude during their brief visible flight. Most strikingly, at least one red orb was reported remaining stationary above a ridgeline for several hours — a duration AARO's own memo states is "physically incompatible with the burn time and rate of descent of any known military flare," the single specific data point in the entire memo that AARO uses to justify why a portion of the case resists the flare explanation that otherwise accounts for most of the activity.

Beyond the mother-orb pattern itself, at least one narrative statement — likely the account generating the largest cluster of FBI digital renderings in the release (statement 2, tied to seven separate renderings, D016 through D021) — described a related but distinct earlier encounter the same shift: vehicle headlights on the roadway ahead appeared to "morph" into an orb-like light, which then presented as an "orb-like disk with a halo glow" hovering above the road. The agent attempted a vehicle pursuit at roughly 80 mph, was unable to close the distance, and found nothing at the object's last apparent position upon arrival. Whether this roadway sighting and the mother-orb releases documented the same night represent one connected phenomenon or two separate incidents reported by the same witness is not resolved anywhere in the released file.

No agent captured photograph, video, or any form of sensor data of the phenomenon at the time — a detail AARO's memo states plainly and that later reporting confirmed. The witnesses were performing a security function, not an observation function, and none carried recording equipment suited to nighttime sky photography. The entire evidentiary record for what was actually seen consists of five written narrative statements and, months or years later, ten FBI-produced digital renderings created from those narratives — not photographs, but artist-style reconstructions built to visually communicate what each witness described in words. AARO also released a "notional incident map" (DOW-UAP-D078) illustrating the approximate relative positions and sightlines of the three observation teams, again without disclosing the actual geographic coordinates.

The FBI's Digital Renderings

Because no camera captured any part of the event, the FBI produced a set of ten digital renderings translating specific witness statements into visual form — a practice AARO has used elsewhere in its PURSUE releases when a narrative-only account is judged detailed enough to support a faithful reconstruction. The file numbering shows an uneven distribution: narrative statement 1 generated three renderings (FBI-UAP-D014, D015, D021), while narrative statement 2 — likely the account containing both the mother-orb sequence and the roadway pursuit — generated seven (FBI-UAP-D016 through D020, D022, D023), suggesting it was judged to contain the richest visual detail of the five. These renderings are explicitly not evidence of what was actually in the sky; they are a visualization aid built entirely from witness description, produced years after the fact, with all the interpretive gaps that implies. AARO's release also reportedly includes two digital video recreations of the reported sequence, similarly reconstructed rather than captured.

AARO's Investigation: Cross-Referencing Flight Logs, Radar, and ADS-B

What distinguishes DOW-UAP-D077 from a simple restatement of witness testimony is the analytical work AARO conducted against it. Per the memo, analysts cross-referenced the witness accounts — their described directions, durations, and timing — against commercial and military flight logs, radar returns, spatial and kinematic estimates, and Automatic Dependent Surveillance-Broadcast (ADS-B) transponder records for the relevant nights, times, and geographic area. This is a materially more rigorous evidentiary process than most narrative-only UAP cases receive, and it produced a specific, falsifiable finding rather than a generic "insufficient data" conclusion: flight logs confirmed that a military aircraft was dispensing standard infrared countermeasure flares during a training exercise in the vicinity on the date in question.

Radar and ADS-B correlation, AARO found, "strongly aligns" with approximately 60 percent of the reported activity — the repeated appear/release/disappear cycling of the orange "mother orb" and at least some of the red orb releases matching the expected visual signature, timing, and approximate flight path of a flare-dispensing aircraft. This is the strongest single piece of the analysis: a real, documented, radar-confirmed military exercise, happening at the right place and time, producing a light pattern genuinely capable of resembling what the witnesses described from the ground.

The witnesses themselves, however, were not simply defaulted around. AARO's memo credits them with "professional knowledge of the visual characteristics of military flares" — an unusual acknowledgment for the agency to make, and one that reflects the specific occupational context of federal agents who guard a national-security site and would reasonably be expected to have seen countermeasure flares before, whether from training exercises, base defense demonstrations, or incidental exposure to nearby military operations. Even crediting that expertise, several agents disputed that flares fully explained what they had watched — particularly the mother-orb "launching" behavior and, above all, the red orb reported holding a stationary position above a ridgeline for hours.

The 60 Percent: What AARO Attributes to Military Flares

AARO's flare explanation is not a vague dismissal — it rests on a documented military exercise, confirmed by flight logs, occurring in the correct place and time window. Standard infrared countermeasure flares, dispensed from military aircraft in sequential bursts as part of routine defensive training, produce exactly the kind of bright, brief, repeatedly-appearing points of light the mother-orb pattern describes: an intense flash lasting a few seconds, followed by darkness, repeating as the aircraft cycles through additional flare releases over the course of a training run. Independent analysts examining the released case — including forum discussion on the skeptical analysis site Metabunk — noted that flare burn-out timing, where a released flare's light output tapers and extinguishes over roughly ten seconds, is broadly consistent with witness descriptions of individual red-orb sightings fading from view relatively quickly after release. On this reading, the orange "mother orb" is the aircraft itself or its flare-dispensing signature, and the red "orbs" are the sequential flares burning as they fall.

This explanation accounts, per AARO's own percentage, for a clear majority of what the six agents reported across both nights. It is also the only candidate explanation in this entire case backed by an actual, documented, radar-and-flight-log-confirmed real-world event rather than inference from witness description alone — a meaningfully different evidentiary category from every other explanation AARO or outside analysts considered.

The 40 Percent: "Unrecognized Technology (Pending)"

For the remaining activity, AARO's radar and ADS-B review found no known aircraft in the estimated line of sight from the witnesses' reported vantage points at the relevant times. Absent a confirmed flight, drone flight plan, or other identifiable platform to attach the sighting to, and having separately assessed the leading alternative explanations as unlikely (addressed below), AARO's memo advances "Unrecognized Technology" as a provisional label for this residual portion — explicitly "by process of elimination," and explicitly flagged as "not supported by technical data or physical evidence." This is a carefully hedged formulation, not a positive finding of anomalous or non-human technology: AARO is documenting that it could not identify a known cause for roughly 40 percent of the reported activity using the analytical tools available to it, while stating plainly that the label itself rests on an absence of a fit to known categories rather than on any positive technical signature pointing toward something genuinely novel.

The single piece of evidence AARO's own memo cites as the strongest basis for this residual classification is the stationary red orb reported holding a fixed position above a ridgeline for several hours. A standard military flare, once dispensed, burns for a limited duration (typically well under a minute) and falls under gravity and residual momentum — it does not hover motionless for hours. If the witness account of duration and stationarity is accurate, no flare-based explanation can account for that specific observation, which is precisely the gap AARO's memo appears to be pointing at when it separates the case into a resolved flare-attributable majority and an unresolved residual minority rather than accepting the flare explanation wholesale.

A caveat on treating AARO's own analysis as the final word: this case's evidentiary strength rests unusually heavily on a single official document, and that document deserves real but not unconditional trust. AARO's radar/ADS-B methodology here is genuinely more rigorous than most UAP investigations get, and its own memo is candid about the limits of what it resolved — both real, checkable strengths that this file weighs seriously throughout. At the same time, government and military bodies investigating UAP have a documented history of incomplete, delayed, or later-revised conclusions, an institutional incentive to close cases with the least alarming available explanation where the evidence allows it, and a classified investigative process that outside researchers cannot independently audit for completeness. None of this is a specific claim that AARO mishandled this particular case; it is a general reason to treat even an unusually rigorous official analysis as one strong input among several rather than as the last word closing the inquiry — exactly the same caution this site applies when an official finding points toward a mundane explanation rather than away from one.

Alternative Explanations Considered and Ruled Out

AARO's memo and subsequent independent analysis both address several candidate explanations beyond flares, each addressed on its own merits rather than treated as a single undifferentiated "unknown" bucket:

• Unmanned aerial systems (drones): Assessed as unlikely to account for the reported pattern. Commercially or militarily available drones do not typically produce the specific appear/release/disappear light-cycling behavior described, and no drone flight authorization or detection was identified for the relevant airspace and times.
• Foreign adversary technology: Assessed as highly unlikely. Analysts found no signals intelligence, geopolitical indicator, or corroborating detection consistent with a foreign intelligence or military platform operating clandestinely near a U.S. national-security site on the dates in question.
• Meteorological or astronomical misidentification: Assessed as more plausible than the drone or foreign-technology theories, though still judged unlikely as a complete explanation — particularly for the stationary, hours-long red orb, which does not match the transient signature of a meteor, bolide, or satellite flare. A meteor or bolide characteristically leaves a visible trail and a very brief flash-to-fade profile; the stationary orb's reported duration is inconsistent with either.
• "Angel hair" / ballooning spider silk: Raised by outside analysts examining the case rather than by AARO's own memo directly, this addresses a separate detail in one witness account describing "thick spider web looking material" floating in the air near the observation point. October is peak season for mass ballooning-spider dispersal across much of the western United States, when airborne strands of silk can catch ambient or artificial light in ways that have historically been mistaken for anomalous material in other UAP reports. This explanation, even if correct, addresses only the spider-silk detail specifically and has no bearing on the separately reported orb-launching behavior.

AARO's memo is also explicit about what the case does not establish, in language echoed across virtually every PURSUE release: neither the Department of War nor AARO concluded that this incident, or any other incident released through PURSUE, constitutes evidence of extraterrestrial life, non-human intelligence, or alien technology.

Key Witnesses

Every witness in this case remains officially anonymous in AARO's declassified release — no name, badge number, or home agency beyond "federal law enforcement" is disclosed for any of the six agents. The entries below summarize what each numbered narrative statement actually describes, using AARO's own internal file numbering; none of these designations correspond to a named individual with a registered key-figures.html profile, and none should be read as identifying anyone.

The Five Observables Assessment

Assessment: This case has no instrumented flight-path data of any kind — no radar track of the red orbs themselves, no FLIR footage, no ADS-B return matched to the objects (as opposed to the ruled-out flare aircraft). Every performance-characteristic observable that would normally be assessed from sensor data must instead be inferred, if at all, from narrative description alone, which is an inherently weaker evidentiary basis. Low Observability is rated speculative only because AARO's own radar/ADS-B correlation found no known aircraft in the line of sight for the unresolved 40 percent — a genuinely ambiguous data point that could indicate an object radar could not detect, or could equally indicate nothing more exotic was actually there to detect, or that the objects were too small, too dim, or too brief for the systems queried to register at all. No sustained hypersonic motion, instant acceleration, or trans-medium transition is reported anywhere in the witness accounts; the red orbs' described motion (line formation, roughly one-second spacing, apparent altitude changes) falls well within the performance envelope of a falling or gliding light source.

Evidence Assessment

Why "Disputed"

The Western United States Event earns a DISPUTED classification because AARO's own investigation produced a genuinely split result rather than either a clean resolution or an unexplained mystery. This is not a case where skeptics and believers are arguing past each other over the same ambiguous testimony — AARO's own analytical process, using flight logs, radar, and ADS-B data rather than witness testimony alone, independently split the reported activity into a documented, radar-confirmed majority (military flares) and a residual minority AARO itself could not close the loop on. Both halves of that split rest on real analytical work, and both deserve to be taken seriously on their own terms.

What elevates this case above a routine misidentification report is the witness profile and the specificity of AARO's own residual finding. Six federal law enforcement agents, deployed specifically to guard a sensitive site and therefore plausibly more familiar with legitimate military activity near it than an average civilian observer, split three ways and still converged on a consistent core description across independently filed statements — and the FBI's own credibility assessment of those witnesses was favorable, not skeptical. AARO's memo does not hand-wave away their objection to the flare explanation; it engages with the single strongest piece of their case (the stationary red orb's incompatible duration) and concedes the point rather than forcing every observation into the flare bucket for administrative tidiness.

What holds the case back from a higher "Credible" rating is the complete absence of instrumented, physical, or photographic evidence of any kind, and the fact that AARO's residual "Unrecognized Technology" label is, by its own explicit wording, not a positive technical finding but an admission of an evidentiary gap. A case resting entirely on narrative testimony — however credible the witnesses, however rigorous the cross-correlation against known flight activity — cannot be independently verified the way a radar track, an isotopic material analysis, or an intact video file can be. The location redaction, while consistent with PURSUE's broader security practices, also means outside researchers cannot independently pull local air-traffic, weather, or astronomical data to check AARO's own analysis against, leaving the public with AARO's conclusions to evaluate rather than the underlying raw data itself.

Sensor & Instrumentation Detection Profile

No dedicated sensor of any kind was pointed at the phenomenon at the time of the sighting. AARO's post-hoc investigation drew on military and commercial flight logs, ground- and air-defense radar returns, and Automatic Dependent Surveillance-Broadcast (ADS-B) transponder records covering the relevant airspace, dates, and time windows — instrumentation used to test the witness accounts retroactively, not to capture the reported orbs themselves in real time. One witness used personally issued night-vision goggles (NVGs) during the observation, the only image-intensification equipment involved anywhere in the case; NVGs amplify ambient and infrared-adjacent light but do not record, meaning even that account produced no retrievable imagery. No FLIR, targeting pod, weather radar, or fixed security-camera footage of the event has been disclosed as existing.

Environmental & Geospatial Context

The declassified record does not disclose specific meteorological conditions, moon phase, or precise geographic coordinates for either night — a deeper redaction than most other PURSUE-released cases, consistent with the sensitivity of the site being protected. What can be established from the witness accounts themselves: observations began at dusk on both nights and continued into full darkness over a multi-hour window; the terrain included at least one ridgeline prominent enough for a witness to reference a stationary light's position against it; and the setting was rural or semi-rural high desert or mountain terrain typical of federal security reservations in the western United States, consistent with (though not confirmed to be) the general landscape of Department of Energy or Department of Defense installations across Nevada, New Mexico, Utah, Idaho, or similar states.

Observer Credibility & Occupational Profile

All six witnesses share the same occupational profile: federal law enforcement special agents assigned to protect a "sensitive national security site," operating in three independent two-person teams. This is a materially different credibility class than a casual civilian sighting. Federal law enforcement agents assigned to guard classified or high-security federal installations undergo background investigation and security clearance processes, receive training in situational awareness and threat assessment as a core job function, and are professionally accustomed to distinguishing routine activity (including nearby military exercises) from genuine anomalies as a matter of operational necessity. The FBI's own subsequent review of these specific witnesses concluded they were highly credible. AARO's memo goes further, crediting them with specific relevant expertise: "professional knowledge of the visual characteristics of military flares," a credential the agency does not appear to have extended casually, given that it directly undercuts AARO's own flare-based explanation for the majority of the case. That AARO both credited the witnesses' expertise and still concluded flares explained roughly 60 percent of the activity reflects an unusually candid, non-defensive treatment of a conflict between expert witness judgment and instrumented cross-correlation data — with AARO ultimately siding with the data where it had it, and conceding the point to the witnesses where it did not.

Physical & Material Assays

No physical material, debris, or trace evidence of any kind was recovered in connection with this case, and none has ever been claimed. The reported "spider web looking material" mentioned in connection with (though not confirmed to be directly linked to) the broader sighting is not described as collected, tested, or retained by any witness or agency; it survives in the record only as a secondary detail flagged by outside analysts as a plausible mundane explanation (seasonal ballooning-spider "angel hair") for one specific sensory detail, not as an assayed sample.

Historical Precedents & Archive Matches

This case sits within a recognizable pattern on this site: security personnel assigned to guard classified U.S. government installations independently reporting unidentified aerial lights near the facility they protect. The closest documented precedent is the August 1980 Kirtland AFB / Manzano sighting, in which Air Force security police guarding the Manzano Weapons Storage Area — then one of the nation's primary nuclear-weapons storage sites, adjoining Kirtland Air Force Base and Sandia Base — reported an unidentified light hovering and, in one account, landing near the restricted weapons-storage area over several nights, a case documented in a declassified AFOSI complaint form. Both cases share the same essential structure: trained federal security personnel, on duty specifically to guard a classified installation against ground and air threats, reporting anomalous aerial activity in the immediate vicinity of the facility they protect — exactly the population one would expect to notice and correctly identify routine military activity, which is part of what makes their departures from a mundane explanation analytically significant in both cases.

A second, more distant precedent is the late-1948 Green Fireballs wave centered on Kirtland Air Force Base, Sandia Base, and Los Alamos — another case in which persistent aerial light phenomena reported in close proximity to the nation's most sensitive nuclear-weapons infrastructure triggered a formal, sustained government investigation (ultimately Project Twinkle) precisely because of the security implications of unidentified objects operating near such sites, independent of whatever the objects actually were. Within this site's own recently published PURSUE-era coverage, the Western United States Event is most directly comparable to the Jake Barber "Skywatcher" claims and the Immaculate Constellation whistleblower report in terms of release timing and institutional context, though it differs sharply from both in evidentiary character: unlike Barber's largely uncorroborated personal claims, this case has multiple independent government witnesses and a documented AARO analytical process; unlike Immaculate Constellation's broad institutional allegations, it is a narrowly scoped, single-incident case file with a specific, falsifiable percentage breakdown attached to it.

Material Analysis

There is, in the strict sense, no material to analyze in this case — no debris, no recovered fragment, no isotopic sample. What functions as this case's "material" evidence is instead the FBI's set of ten digital renderings and reported video recreations: not physical evidence of an object, but a visual reconstruction of testimony, built after the fact from written witness description rather than captured at the time and place of the event. This is a meaningfully different evidentiary category from a sensor-recorded FLIR clip like the Chandelier or a radar-corroborated encounter — those cases, whatever their own interpretive disputes, at least offer an independently verifiable underlying data file that multiple analysts can examine and re-examine. Here, every rendering and every video recreation is itself already an interpretation, filtered once through the witness's memory and language and a second time through the FBI illustrator's or animator's own choices about how to depict "an orange mother orb releasing red orbs like grapes from a basketball" in visual form. Nothing in that chain can be independently re-analyzed the way a raw sensor file can.

The closest thing to physical trace evidence anywhere in the case's periphery is the reported "thick spider web looking material" observed in the air near the sighting — and even that detail was neither collected nor retained by any witness, surviving only as a secondary description in the record. No metallurgical, isotopic, or soil-based assay of any kind has been conducted or claimed in connection with this case.

The Conventional Explanation Candidate: Military Flares (and What They Don't Explain)

Any accounting of this case has to start from AARO's own finding that a real, documented military exercise dispensing infrared countermeasure flares occurred in the correct place and time, and that flight-log, radar, and ADS-B correlation "strongly aligns" with roughly 60 percent of what the six agents reported. This is not a hypothetical or reconstructed conventional explanation of the kind skeptics often have to propose from scratch years after a sighting — it is a confirmed event, on the government's own books, independent of the witness testimony itself. That gives the flare explanation an evidentiary foundation most conventional-explanation candidates on this site simply do not have.

Military Infrared Countermeasure Flares

Standard aircraft-dispensed IR countermeasure flares are designed to be bright, to ignite and burn within a second or two of release, and to be dispensed in short sequential bursts — a profile that maps closely onto witnesses' description of an orange light "launching" clusters of two to four red lights that then fade from view over roughly ten seconds, per the flare burn-out timing independent analysts flagged as consistent with the case. A flare-dispensing aircraft flying a training pattern near (but outside) a restricted facility's airspace, cycling through its flare load over several hours, would from a ground observer's perspective at dusk or after dark plausibly present as a repeating orange light producing smaller red lights at intervals — especially to an observer without aviation training specifically in flare-dispensing tactics, even one professionally familiar with what flares generally look like.

Where this explanation runs out is the single data point AARO's own memo highlights: a red orb reported holding a stationary position above a ridgeline for several hours. Flares do not loiter. They ignite, burn for a fixed and comparatively short duration, and either extinguish in the air or fall to the ground, entirely governed by pyrotechnic chemistry and gravity — there is no version of standard flare technology that produces a multi-hour stationary light. If that specific witness account is accurate as reported, no flare-based reading can close the case, which is exactly the gap AARO's own analysis leaves open rather than papering over.

Meteorological, Astronomical, and Biological Misidentification

AARO's memo and independent analysts both examined celestial and atmospheric misidentification as a candidate for at least part of the unresolved 40 percent, and both rated it more plausible than a foreign-technology or drone explanation while still judging it unlikely as a complete account. A meteor or bolide entering the atmosphere characteristically produces a brief flash with a visible trail, fading within seconds — a profile that could plausibly account for some of the brief, one-to-two-second orange-orb appearances, but cannot explain either the repeated release-and-disappear cycling (meteors do not repeat) or, especially, the hours-long stationary red orb. Separately, the reported "thick spider web looking material" in the air near the observation site plausibly reflects "angel hair" — airborne strands from mass ballooning-spider dispersal, which peaks in the western United States in October, the same month as this sighting — a real, well-documented natural phenomenon that has independently generated its own UFO misidentification reports elsewhere. This explanation, even where correct, addresses a peripheral sensory detail rather than the orb-launching behavior itself.

Foreign Adversary or Undisclosed U.S. Government Technology

AARO specifically tested and rated foreign adversary technology as "highly unlikely" — a meaningful finding given the site's own security sensitivity would make a genuine foreign intrusion attempt a serious concern warranting careful, motivated scrutiny rather than casual dismissal. No signals intelligence, geopolitical indicator, or corroborating detection is cited as supporting a foreign platform. A related but distinct possibility — that the unresolved 40 percent reflects an undisclosed, classified U.S. government or military capability that AARO itself either could not or would not attribute in an unclassified public memo — cannot be ruled out from the released record, but is speculative: AARO's memo does not raise this possibility itself, and no independent evidence beyond the residual "unmatched to known aircraft" finding supports it over the agency's own stated "Unrecognized Technology (Pending)" framing.

The Assessment

Related Cases

Further Reading — Recommended Literature

DISCLOSURE: Some links above are affiliate links. If you purchase through them, OverClassified receives a small commission at no additional cost to you. This helps support independent research.

Essential Viewing

Sources

• All-domain Anomaly Resolution Office / Department of War. "DOW-UAP-D077: Unresolved Case Analysis Update, Western United States Event," June 5, 2026. war.gov/UFO
• Department of War / FBI. "DOW-UAP-D078–D083, FBI-UAP-D014–D023: Western United States Event case files," PURSUE Release 03, June 12, 2026. war.gov/UFO
• Department of War. "Presidential Unsealing and Reporting System for UAP Encounters (PURSUE) — Program Directive," February 19, 2026. war.gov/UFO
• Fox News. "Pentagon files reveal agents' reports of 'orbs launching orbs' near sensitive US security site," June 2026. foxnews.com
• Fox News. "Pentagon UFO files describe 'mother orb' releasing smaller objects in 2023 incident that remains unexplained," June 2026. foxnews.com
• Deschamps, Alban. "Red orbs in the American West," Sentinel News, June 2026. sentinel-news.org
• Metabunk. "War.gov/UFO — Department of War Releases UAP Files — 2026 Release 3," forum thread, June 2026. metabunk.org
• Disclosure Archives. "PURSUE Release 03: 72 more declassified UAP files — including the FBI's own agents' orb sightings," June 2026. disclosurearchives.com
• Disclosure Archives. "AARO releases — every official UAP publication." disclosurearchives.com
• Foreign Policy Journal. "Pentagon And FBI Release New UAP Files Describing 'Orbs Launching Orbs' Near Sensitive National Security Sites," June 16, 2026. foreignpolicyjournal.com
• Yahoo News / Reuters. "Pentagon's latest UFO file drop contains five separate accounts from law enforcement of orbs moving across sky," June 2026. yahoo.com
• AOL / Associated Press. "Feds left baffled by sighting of 'orbs launching other orbs' in western US, new UFO files reveal," June 2026. aol.com
• 1010 WCSI / Fox News Radio. "Pentagon files reveal agents' reports of 'orbs launching orbs' near sensitive US security site," June 2026. 1010wcsi.com
• Loeb, Avi. "UAP Disclosure #3 is the Most Intriguing Release Thus Far!" Medium, June 2026. avi-loeb.medium.com
• Loeb, Avi. "Are UAP Orbs Meteoritic Dust Clouds?" Medium, July 2026. avi-loeb.medium.com
• Loeb, Avi. "A 'Mother Orb' Released Smaller Orbs—and the Pentagon Can't Explain It," video, June 2026. youtube.com
• WION. "Pentagon UFO Files Show 'Mother ORB' Releasing Smaller Objects | World DNA," video, June 2026. youtube.com
• All-domain Anomaly Resolution Office. Congressional testimony and case-resolution record on the Aguadilla, Puerto Rico FLIR case, November 2024–March 2025, for background on Director Kosloski's investigative methodology. aaro.mil
• Air Force Office of Special Investigations. Complaint Form, Manzano Weapons Storage Area sighting, August 1980, referenced for historical-precedent comparison. See this site's own Kirtland AFB / Manzano Sighting case file for full sourcing.
• Wikimedia Commons. "Nevada Test Site (Now Nevada National Security Site), North of Beatty and Las Vegas, Nevada," photograph by Ken Lund, CC BY-SA 2.0, used for this case file's illustrative hero image. commons.wikimedia.org
• Department of War. Homepage and PURSUE portal statistics (release cadence, tranche dates), accessed August 2026. war.gov/UFO
• All-domain Anomaly Resolution Office. "Report on the Historical Record of U.S. Government Involvement with Unidentified Anomalous Phenomena, Volume I," April 2024, referenced for AARO's general investigative history and precedent. aaro.mil
• FOIA.gov. Federal Freedom of Information Act request portal, referenced for records-access context on redacted PURSUE files. foia.gov