- Potential benefitMay increase transparency and public understanding about the 1967 attack and government responses.
- Potential benefitCould provide closure and recognition for surviving crew members and families through released records.
- Potential benefitWould strengthen the documentary record available to historians, scholars, and journalists.
Honor USS Liberty Crew and Urge Declassification
Referred to the Committee on Armed Services, and in addition to the Committees on Foreign Affairs, and Intelligence (Permanent Select), for a period to be subsequently determined…
This resolution is a nonbinding statement by the House that honors the crew of the USS Liberty, lists those who died, and urges the President and U.S. agencies to declassify and release all records about the June 8, 1967 attack. It specifically asks for records from the Department of Defense, the Central Intelligence Agency, the National Security Agency, and any other relevant federal offices. It also affirms that the safety of U.S. citizens and servicemembers should be paramount in U.S. foreign policy. Because it is a simple House resolution, it does not create law or compel the President or agencies to act.
This House resolution honors the crew and casualties of the USS Liberty attack on June 8, 1967, urges the President to declassify all U.S. government records related to that attack, and affirms that the lives and safety of U.S. citizens and servicemembers must be paramount in U.S. foreign policy.
The text recounts the attack, cites sworn affidavits and statements questioning official explanations, lists the crew members who died, and calls for full public release of Department of Defense, CIA, NSA, and other agency records about the incident.
As a House sense resolution it is nonbinding and cannot itself become law; passage in both chambers as binding statute is unlikely given scope and diplomatic sensitivity.
Relative to its intended legislative type, this resolution is clear and effective as a commemorative and declaratory instrument but offers limited construction for the operational request it contains (broad declassification). It specifies who should act and what categories of records are sought, yet omits timelines, interaction with classification law, resourcing acknowledgement, safeguards, and accountability mechanisms.
Scope of declassification versus protection of intelligence
Who stands to gain, and who may push back.
These are examples from the analysis, not a ranked list of the most-affected groups.
- Potential burdenCould strain diplomatic relations with an allied country by renewing attention to contested historical allegations.
- Potential burdenDeclassification carries risk of revealing intelligence sources, methods, or sensitive operational details.
- Potential burdenAgencies would likely incur staff time and costs to review, redact, and process voluminous classified records.
Why the argument around this bill splits.
Scope of declassification versus protection of intelligence
Likely strongly supportive of honoring the crew and pushing for full transparency to establish a public historical record.
Views declassification as a necessary accountability and veterans’ justice measure, while acknowledging possible diplomatic fallout that should be managed.
May insist on protections for intelligence sources where strictly necessary.
Generally supportive of honoring the crew and increasing transparency, but cautious about blanket declassification.
Prefers a measured, interagency review to protect sources, limit harm to intelligence, and avoid unnecessary diplomatic damage.
Likely supportive of honoring the crew and affirming servicemembers’ primacy, but skeptical of sweeping declassification that could harm national security or U.S.–Israel relations.
Concerned about language implying deliberate wrongdoing by an ally without full vetted evidence.
The path through Congress.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
As a House sense resolution it is nonbinding and cannot itself become law; passage in both chambers as binding statute is unlikely given scope and diplomatic sensitivity.
- Executive branch willingness to declassify records
- Committee action and floor scheduling
Recent votes on the bill.
No vote history yet
The bill has not accumulated any surfaced votes yet.
Go deeper than the headline read.
Scope of declassification versus protection of intelligence
As a House sense resolution it is nonbinding and cannot itself become law; passage in both chambers as binding statute is unlikely given sc…
Relative to its intended legislative type, this resolution is clear and effective as a commemorative and declaratory instrument but offers limited construction for the operational request it contains (broad declassifica…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.