The Secret Service has denied multiple Freedom of Information Act (FOIA) requests seeking records related to the July 13, 2024, assassination attempt on former President Donald Trump. The attack occurred during a rally in Butler, Pennsylvania, where 20-year-old Thomas Crooks managed to evade security, climb onto a roof, and fire eight shots at the former president.
President Trump narrowly escaped serious injury when a bullet grazed his ear after he turned his head to read a chart on illegal immigration. The incident raised significant concerns about security measures at the event.
Conservative watchdog group Judicial Watch filed three FOIA requests shortly after the incident, seeking emails, videos, and advance security assessments related to the attempt on Trump’s life. The Secret Service, however, refused to release any documents, citing Title 5 U.S.C. § 552(B)(7)(A), which exempts records that could potentially interfere with enforcement proceedings.
Judicial Watch, known for its legal efforts to obtain government transparency, expressed frustration with the Secret Service’s refusal to provide the requested records. The organization’s president, Tom Fitton, criticized the agency for what he described as a “cover-up,” accusing it of failing to protect the former president and hiding information from the public.
“The Biden Secret Service is in cover-up mode on its inexcusable and epic failure to protect former President Trump and other innocents,” Fitton said. “For Secret Service leaders to promise transparency to Congress while hiding every possible FOIA record from the American people is yet another indictment of this corrupt and failing agency.”
Judicial Watch has indicated that it is preparing for litigation to compel the release of the documents.
The Secret Service’s decision to withhold records has only fueled controversy surrounding the assassination attempt and the agency’s handling of the situation, further igniting conspiracy theories and raising questions about transparency.
SOURCE: JUDICIAL WATCH
You must be logged in to post a comment Login