2021-06-12 - DoD IG Interview Summary
Source Link: https://documents2.theblackvault.com/documents/dod/DODOIG-2023-001013.pdf
(U) Purpose
1. (U) The purpose of this work paper is to document our interview with Major David Grusch on July 12, 2021.
2. (U) We interviewed Major Grusch to determine whether he could provide background information that might be relevant to our evaluation.
3. (U) The Overall classification of this meeting was at the TOP SECRET//TK//NOFORN level due to the vulnerabilities, subject matter discussed, and potential compilation of information.
(U) Sources:
1. (U) The interview was conducted on June 12, 2021. 2. (U) Attending the interview:
A. (U) [Air Force] Major David Grusch B. (U) on behalf of the DoD OIG:
[(b)(6) Redaction] ; DoD OIG Evaluations, (b)(6) Missile, and Nuclear Division (EVAL/SMN)
[(b)(6) Redaction] ; DoD OIG Evaluations, (b)(6) and Engineering Division (EVAL/R&E)
of the Space,
of the Research
-
[(b)(6) Redaction] ; DoD OIG Evaluations (EVAL/SMN), [(b)(6) Redaction]
-
[(b)(6) Redaction] ; DoD OIG Evaluations (EVAL/Intelligence);
Evaluator
[(b)(6) Redaction] ; DoD OIG Evaluations (EVAL/R&E); [(b)(6) Redaction]
(U) Scope:
1. (U) The stated objective of the project is to determine what actions the DoD has taken in regard to UAP reporting and policies. The scope of this interview is to determine what efforts DARPA has published, developed, received, and implemented that is associated with UAP sightings and events.
(U) Methodology:
1. (U) The interview was accomplished to gain testimonial evidence from a member of the UAP task force to gain a better understanding into what the DoD has done and should be doing regarding the UAP problem set.
2. (U) The team prepared a list of questions to guide the discussion with Major Grusch regarding the DoD’s actions taken in response to unidentified aerial phenomena (UAP); however, the interview was conducted in a less structured manner, allowing Major Grusch to provide any information he believed was relevant to our evaluation.
A. Summary of Interview:
1. (U) On July 12, 2021, we met with Major David Grusch to obtain information he had regarding our evaluation of the DoD’s actions taken in response to unidentified aerial phenomena (UAP). [(b)(6) Redaction] recommended that we speak to Major Grusch regarding the topic of our evaluation. (Refer to the "Source" tab of this work paper for a specific list of the meeting attendees.) The Overall classification of this meeting was at the TOP SECRET//TK//NOFORN level due to the vulnerabilities, subject matter discussed, and potential compilation of information. The remainder of this work paper summarizes the discussion that occurred during the meeting and the statements that were attributed to Major David Grusch. Major Grusch provided us with general background information on the DoD's actions regarding UAP (to his knowledge).
2. (U) Major Grusch stated that
. He stated that he “has been studying UAPs for 15 years” and that he serves as the NRO liaison to the UAP
Task Force.
3. (U) Major Grusch stated that there was no formal reporting mechanism for reporting UAP observations and initiating investigations. However, he stated that there were “some forms” that should be e-mailed to [(b)(6) Redaction] .
4. (U) Major Grusch stated that [in his opinion] the analysis done for the Director of National Intelligence (DNI) UAP report “was not very in-depth.”
5. (U) Major Grusch stated that we should speak with [(b)(6) Redaction] , an Air Force point of contact, regarding potential recovered UAP materials.
[(b)(6) Redaction]
6. (U) Major Grusch stated that he recommended the DoD fund and conduct “red and blue assessments” [of UAP], in addition to establishing a permanent office to investigate what he called “strategic anomalies.” Additionally, Major Grusch provided us with a copy of a briefing regarding a proposed permanent office to handle such strategic anomalies (including UAP).
(U) Conclusion
1. (U) Major Grusch provided us with general background information on the DoD's actions regarding UAP (to his knowledge).
(U) Update by [(b)(6) Redaction] 1/6/2023:
[(b)(5) Redaction]
No Comments