What Did Kelleher Actually Do For AAWSAP?

Introduction

Colm Kelleher’s strongest institutional claim in the UAP world is not that he was a Pentagon official, a military witness, or a government whistleblower. It is that he helped run the contractor side of a real Defense Intelligence Agency-funded programme: AAWSAP, executed by Bigelow Aerospace Advanced Space Studies, usually shortened to BAASS. That distinction matters. Kelleher’s role gives him credible proximity to a government-funded UAP-adjacent research effort, but it does not automatically make every claim associated with AAWSAP, Skinwalker Ranch, or BAASS publicly proven. The most careful reading is that Kelleher was a senior BAASS operator managing work for a DIA contract, while the government authority, requirements, classification decisions and programme accountability sat with DIA and Department of Defense officials. Rice University’s Archives of the Impossible profile says Kelleher became BAASS deputy administrator in 2008 and led day-to-day execution of the AAWSAP contract with DIA. [Title of Site | Rice University]impossiblearchives.rice.eduSource details in endnotes.

BAASS and the DIA contract

AAWSAP stands for Advanced Aerospace Weapon System Applications Program. In public discussion it is often merged with AATIP, the Advanced Aerospace Threat Identification Program, but the records are messier than the shorthand. A 2009 Under Secretary of Defense memorandum says Senator Harry Reid referred to “AAITP”, but that the programme was officially the AAWSAP contract managed by DIA. The same memo describes its stated purpose as investigating revolutionary future aerospace technologies, especially unconventional and revolutionary technologies, and says the sole bid came from Bigelow Aerospace Advanced Space Studies in Las Vegas. [Defense Intelligence Agency]dia.milDefense Intelligence Agency

The public solicitation is important because it shows what the contract formally asked for. The Statement of Objectives framed the work as technical studies of future aerospace threats out to around 2050, focused on breakthrough technologies rather than simple extrapolations of existing aerospace trends. The solicitation called for studies in areas such as lift, propulsion, control, power generation, spatial translation, materials, signature reduction, human interface, human effects and armament, with PhD-level expertise expected on analytical teams. It also required finished assessments and presentations suitable for senior federal government audiences, including non-technical executive summaries. [The Black Vault]documents2.theblackvault.comThe Black Vault

That is the official frame: advanced aerospace threat analysis, not an openly advertised “alien investigation” contract. Yet the later public controversy exists because BAASS’s actual activities, as described by AARO and supporters of the programme, extended into UFO case review, witness interviews, biological and physiological effects, and Skinwalker Ranch-related anomalous phenomena. AARO’s 2024 historical report says UAP investigation was not specifically outlined in the contract statement of work, but that the selected private sector organisation nevertheless conducted UFO research with the support of the DIA programme manager. [AARO]aaro.milUnclassified Final DSD AARO Historical ReportAAROUnclassified Final DSD AARO Historical Report…

For Kelleher, this creates a credibility profile with two sides. On one side, his BAASS role is not imaginary or merely self-promotional; it sits inside a documented contractor structure attached to a DIA-managed contract. On the other side, the most contentious work was not all plainly visible in the original contract language, which means readers should not treat “DIA-funded” as a blanket endorsement of every BAASS investigative direction.

What Kelleher actually did inside BAASS

The clearest public description of Kelleher’s role is contractor-side operational leadership. Rice University’s profile describes him as BAASS deputy administrator from 2008, leading day-to-day operations in executing the AAWSAP contract with DIA. That is a managerial and programme-execution role: organising work, personnel, reporting and field or analytical activity for the private company hired by DIA, rather than acting as a DIA official himself. [Title of Site | Rice University]impossiblearchives.rice.eduSource details in endnotes.

This distinction is often lost in popular accounts. Kelleher was not the government programme manager. That role is generally associated with DIA personnel, most notably James Lacatski in insider accounts and later public discussion. Kelleher’s position was on the BAASS side of the line: the contractor that performed the work, hired or coordinated specialists, gathered material and produced deliverables. A later Journal of Scientific Exploration review of the authors’ follow-up book identifies Lacatski as the programme’s director and Kelleher as its deputy director, but this is a programme-insider framing rather than proof that Kelleher held a government post. [Journal of Scientific Exploration]journalofscientificexploration.orgJournal of Scientific Exploration Inside the US Government Covert UFO ProgramJournal of Scientific Exploration Inside the US Government Covert UFO Program

A practical way to understand the role is to separate authority from execution. DIA controlled the contract and government-side acceptance of deliverables. BAASS executed the work. Kelleher, as BAASS deputy administrator, appears to have been one of the people responsible for making that execution happen. His credibility therefore rests more on access to reports, cases and contractor operations than on formal government command authority.

The “programme manager” label can be especially confusing. In ordinary language, someone running day-to-day work may fairly be called a programme manager. In government-contracting language, however, programme manager, contracting officer, contracting officer’s representative, contractor lead and deputy administrator are different roles with different authorities. The AAWSAP records support Kelleher’s proximity and contractor leadership; they do not by themselves turn him into a Pentagon decision-maker.

Contractor role versus Pentagon official status

Kelleher’s BAASS position should be read as institutional proximity, not official government status. He was close to a government-funded programme, but through a private company owned by Robert Bigelow. That makes his public claims more substantial than those of an outside commentator, while also creating a built-in caution: he was part of the organisation performing the work, not a neutral government auditor of that work.

The AAWSAP solicitation reinforces this division. It refers to contractor facilities, contractor-provided personnel, contractor-acquired property, government-furnished data and deliverables to a Government Project Lead. It also says responsibility for collecting information and data necessary for the work remained with the contractor, while classified data supplied by the government remained government property. In other words, BAASS had room to gather, organise and analyse material, but did so under a contract structure that separated contractor activity from government ownership and oversight. [The Black Vault]documents2.theblackvault.comThe Black Vault

This matters for evaluating Kelleher’s later public authority. When he discusses BAASS databases, physiological effects, Skinwalker Ranch, or the breadth of AAWSAP’s investigations, he is speaking as someone who helped run the contractor effort. That gives him relevant experience. It does not mean the Department of Defense has publicly validated each case, database entry, interpretation or anomalous conclusion.

AARO’s 2024 account is sharply relevant here. It says the private sector organisation reviewed new and older Project Blue Book cases, operated debriefing and investigatory teams, and proposed laboratories to examine recovered UFO materials. But AARO also says DIA did not seek or specifically authorise that work, even though a DIA employee set up and managed the contract with the private organisation. This is one of the core governance tensions in the Kelleher story: the work may have happened inside a real contract environment, but not all of it appears to have sat cleanly inside the contract’s stated official purpose. [AARO]aaro.milUnclassified Final DSD AARO Historical ReportAAROUnclassified Final DSD AARO Historical Report…

Supporters tend to interpret that tension as evidence that AAWSAP was more ambitious than the public record shows. Sceptics tend to interpret it as mission drift: a contractor and sympathetic officials pushing UFO and paranormal interests through a loosely framed aerospace-threat contract. Both readings are plausible enough to require careful wording. What is established is Kelleher’s contractor-side role; what remains debated is how much evidential weight should be placed on the more extraordinary conclusions associated with that work.

Deliverables, reports and public records

The strongest public evidence for BAASS’s performance is not a dramatic UAP case. It is ordinary contract paperwork. A DIA “Aerospace Contract Status” slide says BAASS was in full compliance with contract HHM402-08-C-0072, had submitted extensive monthly status reports, had 12 project management plans received and executed, and had delivered 26 detailed research reports by 30 June 2009, twice the minimum requirement. The same slide says reviews of the reports had been overwhelmingly positive and recommended that DIA go forward with option year one, subject to funding. [Defense Intelligence Agency]dia.milDefense Intelligence Agency

That document is highly valuable for Kelleher’s credibility because it confirms that BAASS was not merely a rumour or a retroactive story. A contractor existed, a contract existed, and DIA contemporaneously assessed the contractor’s early performance positively. It also supports the claim that Kelleher’s work environment was structured around real deliverables, not just informal UFO networking.

The deliverables named in the solicitation were conventional in contracting form even when the topics were unconventional. They included status reports, project management plans, research reports, briefings, executive summaries, resumes for key personnel and an integrated threat assessment. The contract also anticipated travel and required personnel and facilities capable of moving towards high-level security clearance requirements. [The Black Vault]documents2.theblackvault.comThe Black Vault

The public record also shows why confusion persists about numbers. Some documents refer to 26 detailed research reports by mid-2009, while public lists and later FOIA releases discuss 38 Defense Intelligence Reference Documents, often called DIRDs. The Black Vault’s AAWSAP archive notes that the DIA released contract-related and programme-related documents, while a separate public index of DIRDs says 37 of 38 requested reports were released in 2022. These records do not all describe the same thing in the same way, which is why neat public summaries can mislead. [The Black Vault]documents2.theblackvault.comThe Black Vault

For readers assessing Kelleher, the key point is not simply “many reports existed”. It is that most of the public evidence consists of contract status documents, technical paper titles, released research reports and later official reviews. Those sources verify programme activity and contractor output. They do not, on their own, verify that the most extraordinary cases collected by BAASS were accurately interpreted.

Why AAWSAP and BAASS get collapsed in UFO discourse

AAWSAP and BAASS are often spoken of as though they were the same thing because their public histories are tightly interwoven. AAWSAP was the DIA-managed programme or contract vehicle; BAASS was the private contractor executing much of the work. The confusion is intensified by the overlapping use of AAWSAP, AATIP and AAITP in official and public documents. AARO states that AAWSAP and AATIP have been used interchangeably in official documentation, while also saying AATIP was never an official DoD programme in the same way after AAWSAP ended and later became a name used by an informal UAP community of interest. [Marcello Catalano]marcellocatalano.comMarcello Catalano UFOsMarcello Catalano UFOs

This matters because Kelleher’s role is sometimes inflated by the ambiguity. Saying “Kelleher worked for AAWSAP” is broadly understandable but imprecise. Saying “Kelleher was deputy administrator at BAASS, the contractor executing the DIA AAWSAP contract” is more accurate. It places him inside the work without blurring him into the Pentagon chain of command.

The same collapse affects public understanding of programme purpose. Media and UFO-community shorthand often presents AAWSAP/AATIP as “the Pentagon UFO programme”. That is partly understandable because BAASS did collect and review UFO-related material, and because the programme became famous through UFO reporting after 2017. But the formal solicitation’s language was about advanced aerospace threat studies, while AARO later emphasised that UFO/UAP investigation was not specifically outlined in the contract statement of work. [The Black Vault]documents2.theblackvault.comThe Black Vault

A fair account therefore has to hold two truths together. It is misleading to pretend AAWSAP had no UAP dimension, because later official review acknowledges that UFO case review, interviews and Skinwalker Ranch-related work occurred. It is also misleading to imply that the public contract straightforwardly authorised every UFO, paranormal or “hitchhiker” line of inquiry later associated with BAASS.

Skinwalker Ranch and the boundary problem

Kelleher’s earlier work at Skinwalker Ranch is relevant because it helps explain why BAASS’s AAWSAP work became associated with more than aerospace theory. Before BAASS, Kelleher had been involved with Robert Bigelow’s National Institute for Discovery Science and co-authored Hunt for the Skinwalker with George Knapp. Rice University’s profile links his later AAWSAP talk to UAPs, human effects, physiological effects, psychological effects and paranormal effects being entered into a large UAP database. [Title of Site | Rice University]impossiblearchives.rice.eduSource details in endnotes.

AARO’s report takes a more sceptical view of that expansion. It says AAWSAP/AATIP investigated an alleged hotspot of UAP and paranormal activity at a Utah property owned by the head of the private organisation, including reports of “shadow figures”, “creatures”, remote viewing and human consciousness anomalies. It then states that AARO had not uncovered other substantive UAP case work conducted by AAWSAP/AATIP beyond reviews of Project Blue Book and private cases, interviews of UAP observers, and unrelated work on alleged paranormal activity at the private sector organisation’s Utah property. [AARO]aaro.milUnclassified Final DSD AARO Historical ReportAAROUnclassified Final DSD AARO Historical Report…

That is a serious challenge to how supporters sometimes frame the programme. If one accepts AARO’s account, BAASS’s most distinctive UAP/paranormal work may have been less a cleanly authorised government UAP investigation and more a contractor-driven expansion into areas already central to Bigelow and Kelleher’s earlier research interests. If one accepts the insider-supporter account, by contrast, the human-effects and paranormal-adjacent material was not a distraction but part of what made AAWSAP unusually broad.

Either way, this is where Kelleher’s credibility becomes hardest to score. His role is verifiable. The existence of BAASS deliverables is verifiable. The fact that UAP and paranormal-adjacent work occurred is now acknowledged in official review. But the quality, chain of custody and interpretive strength of many underlying cases remain much less publicly testable.

The Special Access Programme request

The 2009 request to put the programme under special access protection is one of the clearest examples of how institutional seriousness and evidential uncertainty sit side by side. Senator Harry Reid’s June 2009 letter argued that the programme had made progress in identifying sensitive, unconventional aerospace-related findings and requested a Restricted Special Access Program with a limited access list for parts of AATIP. The released KONA BLUE packet reproduces the letter and describes a small cadre of DoD and private-sector individuals as necessary for advanced sciences, sensors, intelligence, counterintelligence and aerospace engineering. [The Black Vault]documents2.theblackvault.comThe Black Vault

The official response was not acceptance. The November 2009 Under Secretary of Defense memorandum recommended against establishing a Special Access Program at that time. It says the programme manager and leadership saw no justification for special access protection based on the FY09 deliverables or anticipated FY10 work, and James Clapper recommended against creating the SAP. [Defense Intelligence Agency]dia.milDefense Intelligence Agency

For Kelleher’s role, this episode is useful because it shows that BAASS-linked work did reach a level where special-access protection was formally considered. That supports the idea that the programme was not trivial. But the refusal also shows that senior defence leadership did not accept that the submitted material justified the higher compartment. This weakens any simple claim that AAWSAP’s findings were officially recognised as so extraordinary that they demanded special secrecy.

A later AARO document on KONA BLUE adds another cautionary layer. It says KONA BLUE originated from AAWSAP/AATIP, was proposed as a Department of Homeland Security prospective special access programme, but was never approved or formally established, received no materials or funding, and had no data or material transferred under its auspices. It also says DIA terminated AAWSAP/AATIP because of a cited lack of merit and lack of utility in Bigelow’s products for DIA’s mission. [The Black Vault]documents2.theblackvault.comThe Black Vault

That does not erase Kelleher’s contractor experience. It does, however, undercut any argument that later proposed successor efforts prove the existence of recovered non-human technology, hidden materials or validated extraordinary claims. The available official record points to proposals, archived materials and disputed assessments, not publicly confirmed possession of exotic hardware.

What the contractor role supports — and what it does not

Kelleher’s AAWSAP/BAASS role supports several grounded claims. He had real access to a privately executed, government-funded research apparatus. He was involved in organising or managing contractor work that produced formal deliverables to DIA. He operated within a network that included government personnel, contractors, scientists, investigators and UFO-related case material. Those facts make him a meaningful figure in modern UAP history, not merely a commentator after the fact.

The role does not support stronger claims without additional evidence. It does not prove that every BAASS case was accurately investigated. It does not prove that anomalous biological effects were caused by non-human intelligence. It does not prove that Skinwalker Ranch phenomena were real in the extraordinary sense. It does not prove that the Pentagon accepted BAASS’s broadest conclusions. AARO’s public position is that the AAWSAP/AATIP technical papers were exploratory and not thoroughly peer reviewed, and that the programme ended after deliverables were completed amid DIA and DoD concerns. [AARO]aaro.milUnclassified Final DSD AARO Historical ReportAAROUnclassified Final DSD AARO Historical Report…

The fairest credibility assessment is therefore layered. Kelleher is credible as a witness to what BAASS tried to do, how it was organised, and what kinds of data and cases it sought to collect. He is less independently confirmable as a source for the ultimate truth of the most extraordinary interpretations attached to that material, because much of the underlying evidence remains unreleased, privately held, classified, anecdotal, or filtered through later insider books and interviews.

Why this distinction matters for Colm Kelleher

Kelleher’s public standing depends heavily on whether readers understand the contractor-side nature of his AAWSAP role. If he is treated as a Pentagon official, his authority is overstated. If he is treated as an outsider paranormal author with no institutional role, his authority is understated. The accurate middle ground is more interesting: he was a scientist and Bigelow-linked investigator who became a senior operator inside the private company delivering work under a DIA aerospace-threat contract.

That middle ground also explains why he remains influential. Kelleher sits at the junction between formal records and unofficial claims. The formal records show BAASS compliance, deliverables, DIA contract status, technical studies and a real governance trail. The unofficial or less publicly testable side includes large UAP databases, alleged physiological effects, Skinwalker Ranch reports, witness accounts and claims about broader government interest. His credibility cannot be assessed by accepting only one side of that divide.

For a reader trying to judge him, the most useful test is not whether AAWSAP was “real”. It was. Nor is it whether BAASS did UAP-related work. It did. The better question is narrower: when Kelleher moves from describing contractor activity to interpreting anomalous events, does he provide evidence that can be checked outside the BAASS/Bigelow/insider circle? On the public record, the answer varies by claim. The contract role is well supported. The extraordinary conclusions remain much more uneven.

Amazon book picks

Further Reading

Books and field guides related to What Did Kelleher Actually Do For AAWSAP?. Use these as the next step if you want deeper reading beyond the article.

Book

Hunt for the Skinwalker

By Colm A. Kelleher, George Knapp

Provides background on Kelleher's investigative work and the network that later fed into AAWSAP-era discussions.

See on Amazon

Book

UFOs

By Leslie Kean

Offers context for evaluating government-linked UFO claims and official involvement.

See on Amazon

Book

In Plain Sight: an Investigation Into UFOs and Impossible Sci...

By Ross Coulthart

Examines contemporary UAP controversies, including government and contractor narratives.

See on Amazon

Book

Skinwalkers at the Pentagon

By James T Lacatski D.Eng., James T. Lacatski et al.

Covers AAWSAP, BAASS, government contracting, and insider claims surrounding Kelleher's work.

See on Amazon

Browse more on Amazon: Hunt for the Skinwalker UFOs In Plain Sight: an Investigation Into UFOs and Impossible Science

As an Amazon Associate I earn from qualifying purchases.

Endnotes

1. Source: impossiblearchives.rice.edu
   Link: https://impossiblearchives.rice.edu/flash-talk-speakers/colm-a-kelleher

2. Source: dia.mil
   Title: Defense Intelligence Agency
   Link: https://www.dia.mil/FOIA/FOIA-Electronic-Reading-Room/FileId/170015/

3. Source: documents2.theblackvault.com
   Title: The Black Vault
   Link: https://documents2.theblackvault.com/documents/dia/AAWSAP/SOW_Aerospace.pdf

4. Source: aaro.mil
   Title: Unclassified Final DSD AARO Historical Report
   Link: https://www.aaro.mil/Portals/136/PDFs/AARO_Historical_Record_Report_Vol_1_2024.pdf
   Source snippet

   AAROUnclassified Final DSD AARO Historical Report...

5. Source: dia.mil
   Title: Defense Intelligence Agency
   Link: https://www.dia.mil/FOIA/FOIA-Electronic-Reading-Room/FileId/170019/

6. Source: documents2.theblackvault.com
   Title: The Black Vault
   Link: https://documents2.theblackvault.com/documents/osd/konablue-release1.pdf

7. Source: journalofscientificexploration.org
   Title: Journal of Scientific Exploration Inside the US Government Covert UFO Program
   Link: https://journalofscientificexploration.org/index.php/jse/article/view/3541/2229

8. Source: theblackvault.com
   Link: https://www.theblackvault.com/documentarchive/the-advanced-aerospace-weapon-system-applications-program-aawsap-documentation/

9. Source: marcellocatalano.com
   Title: Marcello Catalano UFOs
   Link: https://www.marcellocatalano.com/aaro.htm

Additional References

1. Source: youtube.com
   Title: Examining the DIA’s AAWSAP Program and Objectives
   Link: https://www.youtube.com/watch?v=9QJ-FfG24eQ
   Source snippet

   Colm Kelleher and the BAASS Operational Framework...

2. Source: youtube.com
   Title: Understanding the AAWSAP and BAASS UAP Contract
   Link: https://www.youtube.com/watch?v=F6QjK6H7j68
   Source snippet

   George Knapp on the History and Scope of AAWSAP...

3. Source: youtube.com
   Title: The Role of Bigelow Aerospace in UAP Research
   Link: https://www.youtube.com/watch?v=S2S7sR-b364
   Source snippet

   Examining the DIA's AAWSAP Program and Objectives...

4. Source: youtube.com
   Title: George Knapp on the History and Scope of AAWSAP
   Link: https://www.youtube.com/watch?v=l_a-S3Z45vI
   Source snippet

   The Role of Bigelow Aerospace in UAP Research...

5. Source: locationsunknown.org
   Title: Locations Unknown Defense Intelligence Reference Documents (DRIDs)On
   Link: https://locationsunknown.org/foia-reading-room/the-deep-end/ufos-aliens/defense-intelligence-reference-documents

6. Source: youtube.com
   Title: Colm Kelleher and the BAASS Operational Framework
   Link: https://www.youtube.com/watch?v=1K1sWpWfH44