§ 01Global Flight Track Map
All 18 sorties from the last 30 days plotted on a single map. Colour gradient maps to date (earliest = blue, latest = pink). Click any track to see the date and duration. The May 10 West Alton overflight is highlighted in gold.
§ 02Day-by-Day Flight Log
| Date (UTC) | Start | End | Duration | Origin → Destination (inferred) | Notes |
|---|
§ 03Key Findings
60% operational tempo
18 flying days in 30. Significantly higher than typical for an E-4B, which usually flies test or alert sorties only. Pattern indicates active mission window.
Trans-Pacific deployment
May 12-13 trans-Pacific transit: Offutt → BC Canada → Anchorage → Kadena AB Okinawa. 12 hr 33 min Anchorage to Kadena. Lands ~24 hr before US President's arrival in Beijing for the 13 May 2026 summit.
West Alton overflight
10 May, 1h 43m mid-route transit from Wright-Patterson AFB → Offutt AFB, passing 2.13 nautical miles overhead a West Alton civilian observer at 15:07:36 UTC. MLAT-only, no callsign, squawk 6726.
Pentagon UAP file day
8 May 2026: 6h 27m sortie on the same day Department of War launched war.gov/ufo and released the largest tranche of declassified UAP files in US history (162 documents). No direct linkage claimed.
15-hour endurance test
15 Apr 2026: longest single sortie of the window — 14 h 56 m airborne. Consistent with a fuel-endurance training mission or shadow-the-president exercise.
MLAT-only signature
Across nearly every sortie, no ADS-B Out callsign or squawk broadcast. Position derived from ground-station multilateration only. Standard low-observable operating mode for NAOC.
§ 04UAP Sighting Cross-Reference (Strict Criteria)
Every Enigma Labs and Reddit r/UFOs sighting from the 30-day window was geocoded and compared against every trace point of each of the 18 sorties. A sighting is flagged STRICT MATCH only if the aircraft was within 30 nautical miles of the witness's location within ±2 hours of when the sighting was filed. PROXIMITY is the next ring out (≤100 nm / ≤6 hr). Everything else is rejected.
The only confirmed strict spatial-temporal coincidence between this aircraft and any public UAP sighting in the 30-day window is the filer's own sighting at West Alton, MO on 10 May 2026. Every other sighting in the same regional corridor was off in time by hours to weeks, or off in space by more than 30 nautical miles, or both.
| Sighting | Source | Filed | Closest sortie | Min dist | Δ time | Verdict |
|---|---|---|---|---|---|---|
| West Alton, MO | Enigma #331938 | 10 May 15:07 UTC | 2026-05-10 | 2.1 nm | 0.0 hr | STRICT MATCH |
| Millersville, MO | Enigma #331905 | 11 May 04:27 UTC | 2026-04-15 | 1.7 nm | 624 hr | REJECTED (time) |
| Effingham, IL | Enigma #332025 | 12 May 22:12 UTC | 2026-05-10 | 11.7 nm | 55 hr | REJECTED (time) |
| Edmonds, WA | Enigma #331953 | 11 May 15:20 UTC | 2026-05-12 | 20.1 nm | 31 hr | REJECTED (time) |
| Antioch, IL | Enigma #331963 | 11 May 21:00 UTC | 2026-04-30 | 20.4 nm | 284 hr | REJECTED (time) |
| Galena, MO | Enigma #332082 | 14 May 04:22 UTC | 2026-04-15 | 17.9 nm | 697 hr | REJECTED (time) |
| Poulsbo, WA | Enigma #331904 | 11 May 04:18 UTC | 2026-05-12 | 30.4 nm | 42 hr | REJECTED (both) |
| Gallipolis, OH | Enigma #332024 | 12 May 01:00 UTC | 2026-04-29 | 30.4 nm | 301 hr | REJECTED (time) |
| Blue Hill, NE | Enigma #332084 | 14 May 04:30 UTC | 2026-04-16 | 30.8 nm | 657 hr | REJECTED (both) |
| Rocky River, OH | Enigma #331895 | 10 May 01:30 UTC | 2026-04-21 | 48.8 nm | 437 hr | REJECTED (both) |
| Missoula, MT | Enigma #331851 | 9 May 23:40 UTC | 2026-05-12 | 67.4 nm | 70 hr | REJECTED (both) |
| + 28 r/UFOs sighting posts from the same window (state-level geocoded). All rejected on either spatial or temporal criteria. Closest was a "Virginia fiery orb" post at 3.1 nm from the 8 May track, but 23 hr delta. Raw data: /data/sighting_matches_30day.json | ||||||
What this means
This is the opposite of what most UAP-adjacent reports claim. When you constrain to strict spatial-temporal coincidence, the 30-day window for 75-0125 contains exactly one confirmed UAP report inside that window: the filer's own.
What this does NOT mean
It does not mean no other sightings happened in the corridor. It means none of the other 39 evaluated sightings line up with 75-0125's actual position to within 30 nm and 2 hours. The aircraft and the sightings share a region, not a specific moment.
The remaining question
Why did the filer's footage capture 22 independent moving objects in clear sky 2.13 nm from a NAOC E-4B that was making no evasive maneuver? The aircraft-sighting coincidence at West Alton remains the open question, not the broader corridor pattern.
§ 05Methodology
All trace data sourced from ADS-B Exchange historical archive at globe.adsbexchange.com/globe_history/YYYY/MM/DD/traces/b6/trace_full_adfeb6.json (requires Referer: https://globe.adsbexchange.com/ header). Combined dataset publicly accessible (CORS-open) at /data/750125_30day.json for independent verification. Total dataset: 18 active sorties, ~20,000 trace points, ~50 cumulative flight hours.