Luis Elizondo’s Exit from the Pentagon: What the Paperwork Says and What It Leaves Out
A public resignation letter, a program the Pentagon acknowledged and later downplayed, and a book that cleared its own prepublication review. Six years of official versions that do not fit together.
Luis Elizondo worked for the U.S. Department of Defense in counterintelligence, posted to the Office of the Under Secretary of Defense for Intelligence, and resigned in October 2017 with a public letter to the Secretary of Defense. In December of that year he appeared in the press as the head of a Pentagon program on unidentified aerial phenomena. The department confirmed the program's existence in 2019 and, in the same period, other spokespeople denied that Elizondo had assigned responsibilities in it. The historical report published in March 2024 by the Pentagon's specialized office maintains that the program was not assigned that mission.
Executive summary of the case file. Everything essential before you dig deeper.
Fact sheet
OSINT - Traceability
There is one kind of case file that interests me more than any other, and it is this one: the kind where there is no need to argue about whether something flew. Nothing flies here. Here there is a man who worked in a building in Virginia, a resignation letter, spokespeople who contradict one another over six years, a report from an inspector general, another from an office created for the purpose, and a book that went through the prepublication review office of the department itself. Paper against story. My favorite terrain.
Because the Luis Elizondo case has one feature that sets it apart from everything else in this sector. The other witnesses claim to have seen something. He claims to have managed something. And that, unlike a light in the sky, leaves a bureaucratic trace by definition: organizational charts, emails, authorizations, budget lines, signatures. A program is an administrative structure, and administrative structures can be audited.
So let’s look at the paperwork. Without enthusiasm and without ill will, since in this affair both are overvalued and neither is of any use.
What can be verified, first
Let’s start with the solid ground, which is more than is usually acknowledged. Luis Elizondo worked for the U.S. Department of Defense in counterintelligence and security, and was posted to the Office of the Under Secretary of Defense for Intelligence. He resigned in October 2017 with a letter addressed to the then Secretary of Defense, a document that was made public and can be read. In it he set out his frustration at the lack of attention that, in his view, was being paid to an aerial security matter.
A few days later he joined a private company founded by a musician, a physicist and several former administration officials, which was presented publicly that same October. And in December 2017 the article that changed everything appeared in a New York newspaper: the revelation of a Pentagon program devoted to unidentified aerial phenomena, accompanied by video material from military sensors. Elizondo appeared in that report as the man who had run the program.
It is verifiable, finally, that the Department of Defense acknowledged the program’s existence in December 2017, and that in 2019 an official spokesperson told the press that it had looked into unidentified aerial phenomena. A named official spokesperson said that to the press. It is not a leak or an inference.
And now the uncomfortable part, which is just as verifiable. That same department, through other spokespeople and in successive years, maintained that Elizondo had no assigned responsibilities in relation to that program. Both positions come from the same department, were issued a few months apart, and have never been reconciled publicly.
The resignation
Elizondo submits his resignation by letter to the Secretary of Defense, a document that will be made public. That same month he joins a private company devoted to the subject.
The article that changes everything
A New York newspaper reveals the existence of a Pentagon program on unidentified aerial phenomena and publishes military sensor material. Elizondo appears as its head.
The department confirms the program
An official spokesperson publicly acknowledges that the program existed and that it investigated unidentified aerial phenomena.
The department contradicts itself
Other spokespeople maintain that Elizondo had no assigned responsibilities in that program. The two positions are never reconciled.
The inspector general
The Department of Defense inspector general publishes the unclassified summary of its evaluation of the department's handling of anomalous phenomena. It criticizes the lack of a coherent approach.
The historical report
The office the Pentagon created for these matters publishes the first volume of its historical report, which maintains that the program was not officially tasked with investigating these phenomena.
The book clears prepublication review
Elizondo publishes a memoir that has passed the department's own security prepublication review.
Before the House
He appears at a hearing of the House of Representatives oversight subcommittee alongside other former federal officials.
What is said to have happened
Elizondo’s version, maintained since late 2017, amounts to this: he led an effort within the Department of Defense devoted to analyzing incursions by unidentified objects into military airspace; that effort lacked institutional support and adequate funding; he met internal resistance and stigma; and he resigned in order to warn the public about the problem from outside, understanding it to be a national security matter that was being neglected.
The administration’s version is harder to summarize because it is not a single one. At one point it acknowledges the program. At another it denies Elizondo’s connection to it. At another, through its specialized office, it maintains that the program was not assigned the mission attributed to it. And meanwhile, through the security prepublication review, it authorizes the publication of a book written by the person whose connection it denies.
When a department says three different things about the same official in six years, the problem stops being the official.
That last point is the one that interests me most and the one least discussed. Security prepublication review is a real procedure, with its own office, and everything that a former official with access to classified information wants to publish must pass through it. Its function is to strike out what cannot be released. A manuscript clearing that procedure does not mean the department endorses its content (it needs saying plainly, because it is constantly misunderstood), but it does mean the department has read the text and decided what stayed in. That is an administrative relationship, not a fantasy.
What it could be, with no need for Martians
The difference between running and handling
This is probably the most economical explanation of the whole contradiction, and it requires nobody to lie. In a huge organization, a matter can have a formal owner and a person who in practice carries it. The program could have a budget assignment in one place, a nominal head in another, and an official handling the day-to-day in a third. Asked whether that person “ran the program,” the literal answer according to the organizational chart may perfectly well be no, while the practical answer is yes.
Add that the program itself changed form, name and chain of command over the years, taking on and shedding tasks. Asking “did such a program exist and who ran it?” of a bureaucracy that size guarantees different answers depending on which office you ask and in which year.
A department protecting itself
Hypothesis number two, just as earthly. When the matter became uncomfortable in the media, the predictable institutional reaction is to minimize, not to lie. You answer the narrowest possible question, avoid any wording that could be read as validation, and shift the answer onto the person rather than the program, because denying the relevance of an individual is far cheaper than explaining a budget line.
We are all paying for that strategy, and the price is high: when a department gives three different versions of the same matter, it ceases to be a usable source. And in the vacuum it leaves, exactly what it said it wanted to avoid grows.
And what the historical report says, plainly
The first volume of the historical report published in March 2024 by the Pentagon’s specialized office is the document least favorable to Elizondo’s version, and that has to be said without evasions. It maintains that the program was not officially tasked with investigating these phenomena and states that it found no evidence of programs for the recovery or reverse engineering of non-human technology. We analyze it in detail in its own case file and in the document profile.
Now, it has to be read with the same coolness with which we read everything else. It is a report produced by a body of the Department of Defense about the conduct of the Department of Defense. That does not invalidate it, but it does oblige us to record who signs it. And it is worth remembering that the department’s own inspector general, the year before, had concluded that the handling of this matter lacked a coherent approach. A department that evaluates itself after its own inspector has scolded it for the disorder is not the definitive source on its own disorder.
What you can ask for and what you can’t
A practical note for anyone who wants to check this on their own, because the case allows it better than it seems. The organizational charts of the Under Secretary’s office, the associated budget lines and the resulting contracts are, in principle, open to requests under access-to-information rules. So are internal emails, with redactions. What can never be obtained is a person’s security clearance or the content of a classified program, and anyone who promises otherwise is selling smoke.
That means the checkable question is “does his name appear in the program’s administrative trail?”, since “did he have access to such a thing?” has no possible public answer. It is a smaller question and far more useful. As far as this site can tell, nobody has yet answered it with the complete documentation on the table. Until that happens, the case file stays exactly where it is.
Why this case won’t die
Because it is the hinge of everything modern. Before December 2017, this subject was folklore in public conversation. Afterward, it is a matter handled by congressional committees, offices are created and laws are written. Whatever one thinks of Elizondo, that border exists and he stands right on top of it. Without that article and without the Navy videos that accompanied it, there is no 2023 law, no specialized office and no hearings.
It doesn’t die, besides, because the institutional contradiction remains unresolved and nobody is going to resolve it now. There will be no statement reconciling the 2019 and 2021 versions. There will be no clarification of the organizational chart. Those things stay as they are, and the researcher who comes along in twenty years will find the same mess we found, except that by then half the protagonists will be dead.
And it doesn’t die because it raises the question of method that runs through this whole sector, already posed in the Clifford Stone case: how do you verify what someone says they did inside an institution. With Elizondo the result is intermediate and honest. The frame is verified: he existed, he worked there, he resigned, the program was real, his book went through prepublication review. The content is not: what exactly he did, with what mandate and with what results remains unestablished, and the most recent official report points against him.
One last thing, a matter of mental hygiene. There are two cages in this affair and both are comfortable. The cage of “everything the Pentagon says is a lie, so Elizondo is right.” And the cage of “a spokesperson denied it, so he is a fraud.” Both spare you the work of reading the documents, which is exactly why they are so popular. We are not going into either one here, though it is much cozier inside.
A resignation letter, two spokespeople who do not agree, an inspector general who says it was a mess, and an in-house report that evaluates itself. All of that is state paper, and all of it contradicts itself. In the end, the lesson of this case file has nothing to do with the sky; it concerns how little can be built on top of a department that has not decided which version is its own.
OSINT – Source traceability
Neither the resignation letter nor the statements of the Department of Defense spokespeople are quoted verbatim, because no verified transcripts are available; their content is described and attributed. The individual spokespeople are not named. The exact day of the resignation and of the private company's presentation is not given because it cannot be pinned down with certainty; the month is stated. The content of the 2024 historical report is described in its main lines without citing specific sections.