July 24, 2026
Pentagon UAP Report and Burchett's Disclosure Demand — July 24, 2026
Congressional pressure grows after Tim Burchett accuses the Pentagon of shielding UAP files and a new Pentagon report plus a Virginia Beach sighting raise calls for disclosure; listen for details and implications.
This program uses AI to hide our identites and to gather information from sources the government would prefer we didn't contact.
WEBVTT
1
00:00:00.120 --> 00:00:03.560
This is UFO sightings. Today, Tim Burchett walked out of
2
00:00:03.600 --> 00:00:06.360
a two hour meeting at the Pentagon and accused what
3
00:00:06.480 --> 00:00:10.759
he called a deep state effort to keep UAP information
4
00:00:10.839 --> 00:00:16.079
from Congress and the public. Fox News reports Birchett, who
5
00:00:16.160 --> 00:00:19.640
has long pressed for aggressive oversight and has said we
6
00:00:19.800 --> 00:00:23.480
have sworn testimony that there are recovered alien bodies, demanded
7
00:00:23.519 --> 00:00:28.320
documents and answers. His remarks come against a tense political backdrop,
8
00:00:29.280 --> 00:00:32.079
and after the April death of Air Force Officer Matthew
9
00:00:32.200 --> 00:00:36.240
James Sullivan, who had agreed to testify to Congress. The
10
00:00:36.280 --> 00:00:41.159
timing has only sharpened calls for transparency. A separate item
11
00:00:41.159 --> 00:00:45.640
in the Pentagon's latest reporting touched the coastline. Wavy dot
12
00:00:45.679 --> 00:00:49.560
Com notes the Pentagon's Anomaly Resolution Office included a siding
13
00:00:49.600 --> 00:00:53.960
off the Virginia Beach Coast. Local authorities and regional reporters
14
00:00:54.039 --> 00:00:56.640
say the incident is now part of the official file.
15
00:00:57.240 --> 00:01:00.479
One more unexplained entry in a dossier that law lawmakers
16
00:01:00.520 --> 00:01:04.799
are fighting over. In our Disclosure Watch segment, the Debrief reports,
17
00:01:04.840 --> 00:01:09.000
the Pentagon's Anomaly Resolution Office released a new consolidated report
18
00:01:09.400 --> 00:01:14.239
finding no evidence of exotic technology, but acknowledging. Many mysteries persist.
19
00:01:15.200 --> 00:01:18.319
The office calls for improved sensor networks and broader inner
20
00:01:18.319 --> 00:01:21.640
agency data sharing to resolve cases the current record cannot
21
00:01:21.640 --> 00:01:25.599
explain online. The community is talking about a Reddit post
22
00:01:25.760 --> 00:01:31.000
that recounts a cylindrical UAP during US Navy exercises. Jets
23
00:01:31.040 --> 00:01:36.000
scrambled the object, reportedly toyed with fighters, made impossible maneuvers,
24
00:01:36.599 --> 00:01:41.640
then departed as mysterious. Personnel removed logs. Other posts urge
25
00:01:41.640 --> 00:01:44.599
public pressure to keep a UAP disclosure framework in the
26
00:01:44.599 --> 00:01:50.439
Defense Bill. Official investigators emphasize caution. Most incidents, when resolved,
27
00:01:50.680 --> 00:01:55.799
trace to aircraft, balloons, satellites, or censor error. The Pentagon's
28
00:01:55.840 --> 00:01:59.079
Office says better data and clearer records are the path
29
00:01:59.159 --> 00:02:03.840
to fewer mystories. We'll keep watching the skies. UFO sightings
30
00:02:03.840 --> 00:02:08.120
today is for informational purposes only. Stories are drawn from
31
00:02:08.199 --> 00:02:12.479
publicly available sources. All claims are attributed to their original
32
00:02:12.520 --> 00:02:15.319
sources and have not been independently verified
1
00:00:00.120 --> 00:00:03.560
2
00:00:03.600 --> 00:00:06.360
3
00:00:06.480 --> 00:00:10.759
4
00:00:10.839 --> 00:00:16.079
5
00:00:16.160 --> 00:00:19.640
6
00:00:19.800 --> 00:00:23.480
7
00:00:23.519 --> 00:00:28.320
8
00:00:29.280 --> 00:00:32.079
9
00:00:32.200 --> 00:00:36.240
10
00:00:36.280 --> 00:00:41.159
11
00:00:41.159 --> 00:00:45.640
12
00:00:45.679 --> 00:00:49.560
13
00:00:49.600 --> 00:00:53.960
14
00:00:54.039 --> 00:00:56.640
15
00:00:57.240 --> 00:01:00.479
16
00:01:00.520 --> 00:01:04.799
17
00:01:04.840 --> 00:01:09.000
18
00:01:09.400 --> 00:01:14.239
19
00:01:15.200 --> 00:01:18.319
20
00:01:18.319 --> 00:01:21.640
21
00:01:21.640 --> 00:01:25.599
22
00:01:25.760 --> 00:01:31.000
23
00:01:31.040 --> 00:01:36.000
24
00:01:36.599 --> 00:01:41.640
25
00:01:41.640 --> 00:01:44.599
26
00:01:44.599 --> 00:01:50.439
27
00:01:50.680 --> 00:01:55.799
28
00:01:55.840 --> 00:01:59.079
29
00:01:59.159 --> 00:02:03.840
30
00:02:03.840 --> 00:02:08.120
31
00:02:08.199 --> 00:02:12.479
32
00:02:12.520 --> 00:02:15.319