Mellon’s “narrowed ask,” challenged — the Gerb critique and Mellon’s reply (June 2026)
Source: X/Twitter exchange around Christopher Mellon’s 15 June 2026 UAP-release-priorities tweet. Mellon’s original (the three sensor-data priorities) is captured separately: mellon-uap-data-release-priorities-2026-06-15 (https://x.com/ChrisKMellon/status/2066336684850180394). Captured: 2026-06-19 via fxtwitter. Verbatim. What this is: (1) Gerb (@UAPGERB)‘s 15 June 2026 public critique quote-replying to Mellon’s priorities tweet, and (2) Mellon’s 19 June 2026 follow-up laying out his step-by-step rationale. Together they bear directly on the co-option-versus-tactical-sequencing question flagged on the Mellon page. Analysis: mellon-career-and-advocacy.
Gerb (@UAPGERB), 15 June 2026 — quote-reply to Mellon’s priorities tweet
URL: https://x.com/UAPGERB/status/2066531534719586695 (23,430 followers; 185,984 views; 327 RT; 1,736 likes)
Mr. Mellon,
While many, including myself, appreciate your tenacity here, this is a perplexing tweet…
You are calling for the release of UAP space data, satellite data, and detection from the Ballistic Missile Early Warning System; however, you yourself have commented on several occasions on the existence of both the legacy programs and recovered materials/biological samples.
The number one example that comes to mind is this redacted Signal messaging screenshot you released in 2024 in response to Sean Kirkpatrick voluntarily offering Signal exchanges between you and him for a FOIA release.
This redacted exchange with an unknown individual not only confirms you know the management structure, security control systems, and ownership of the crash retrieval portfolio, but that you are also aware of a highly classified memo by SecAF in the 1950s that is still in effect to maintain cover for the legacy programs.
Indeed, you also in this exchange confirm you are aware of the Air Force legacy SES-2 gatekeeper (likely Russel E. Wyler) and state the 1953 Kingman, Arizona UFO crash was indeed real and recovered.
So why exactly is this memo by a former SecAF or the release of the Kingman wreckage and biologics not a priority for you? These have lower precedence than your listed IMINT/SIGINT data?…
You have said similar things on several occasions regarding UFO retrieval and exploitation, including a 2023 NewsNation appearance with Chris Cuomo where you stated: “I’ve been told that we have recovered technology that did not originate on this Earth, by officials in the Department of Defense and by former intelligence officials.”
https://www.newsnationnow.com/cuomo-show/ufo-hearing-congress-christopher-mellon/
This feels like a bizarre pivot back to your and Mr. Elizondo’s ~ 2017-2023 narrative of discussing an amorphous non-human presence on this planet without breaking into the fine details of recovered technical vehicles or biologics.
At the same time, I find it bizarre that your list is excluding maritime UFO sensor data encounters. We know, all the way back to the days of Project Blue Book, USO/maritime UFO encounters are often strikingly anomalous and occur almost more frequently than any space-based UFO monitoring and tracking.
Others and I share the concern that within the Age of Disclosure documentary, Jay Stratton, who retired as a Defense Intelligence Senior Executive (DISES) from the Office of Naval Intelligence (ONI), purposefully excluded Navy elements from the film’s “Legacy Program” outline to protect his Naval interest or prior exposure to Naval Legacy Elements. Mr. Mellon, are you doing the same? Admiral Gallaudet has advocated for the study of UFO/USO in maritime environments tirelessly. Why do you not also advocate for release of such data?
An additional worthy pursuit, as I have publicly requested, is for you to comment on your former SSCI coworker, Mary K. Sturtevant. As I have stated, I am aware that whilst Sturtevant was Lockheed Martin VP of Government Affairs and VP for Intelligence, Joint and Science & Technology Progams, she aided in the blocking of the Kona Blue PSAP UFO materials transfer between Lockheed Martin and the AAWSAP. My public request to you can be found here:
https://x.com/UAPGERB/status/1971960633504813519
Why is UFO retrieval, exploitation, and reverse engineering, for which you have advocated transparency in the past, taking a backseat to a handful of specific sensor data?
Christopher K. Mellon (@ChrisKMellon), 19 June 2026
URL: https://x.com/ChrisKMellon/status/2068089975187382462 (162,036 followers; 14,332 views; 54 RT; 319 likes)
Congress has repeatedly asked about crash debris etc. and the answer is always the same, “We don’t know what you are talking about.” Repeatedly asking the same question and getting the same answer is not helpful. We need a strategy to build a wider, broader base of support to press further and eventually get to the bottom of this. My premise is that to get to the holy grail of recovered ET materials, if indeed we have any, first requires a greater public consensus and demand for the truth and support from key committees. One of the best ways to get there is to show UAP entering and leaving the atmosphere; or exceeding all known science and aeronautic principles regarding acceleration etc. We’ve established there are strange and mysterious objects out there but we are a long way from demonstrating to the satisfaction of most people that UAP are so advanced they are definitely of non-human origin. If we can get this other data out, our prospects for successfully obtaining the release of recovered materials will be far, far greater and the public will be better prepared to accept this. This is a step by step process unless Congress is able to leapfrog to the alleged recovered materials which isn’t looking likely at the moment. So if we can get there directly that would be great, but we still have a lot of convincing to do and the data I propose seeking offers a logical and reliable step towards the common objective of getting to the truth with genuine highly compelling data that exists but has not yet been released. Meanwhile we continue to look for and support whistleblowers.