- Federal agenciesCreates a consistent federal practice to honor American hostages and wrongfully detained individuals, increasing public…
- Potential benefitRaises awareness of hostage and wrongful-detention issues at high-visibility sites (embassies, passport offices, airpor…
- Potential benefitImposes little substantive regulatory change beyond flag-display requirements, so supporters may contend implementation…
Remembering American Hostages Act of 2025
Referred to the House Committee on the Judiciary.
This bill (Remembering American Hostages Act of 2025) amends Title 36 to expand and specify when and where the Hostage and Wrongful Detainee flag should be displayed. It adds certain key historical dates (including dates tied to the Iranian hostage crisis, the death of journalist James Foley, and the October 7, 2023 Hamas attack) to the list of occasions for flying the flag, and requires the flag be flown at specified federal locations (additional Cabinet-level officials, Department of State offices and embassies/consulates, Department of Justice offices, and passport-issuing locations) whenever the U.S. flag is displayed.
Whether the bill’s specific language (e.g., calling October 7 an "unprovoked" attack and singling out particular incidents) politicizes what otherwise is a symbolic recognition.
Relative to its intended legislative type, this bill is an administrative/operational amendment to title 36 that is clear in purpose and specific about dates, locations, and responsible officials, but it lacks fiscal acknowledgment and accountability mechanisms.
This bill (Remembering American Hostages Act of 2025) amends Title 36 to expand and specify when and where the Hostage and Wrongful Detainee flag should be displayed.
It adds certain key historical dates (including dates tied to the Iranian hostage crisis, the death of journalist James Foley, and the October 7, 2023 Hamas attack) to the list of occasions for flying the flag, and requires the flag be flown at specified federal locations (additional Cabinet-level officials, Department of State offices and embassies/consulates, Department of Justice offices, and passport-issuing locations) whenever the U.S. flag is displayed.
The bill also contains a Sense of Congress encouraging state and local governments and airports (in coordination with FAA) to fly the flag on those days and recommends an Executive Order to direct flag-raising on days a hostage returns or is confirmed to have died in captivity.
Because the bill is narrow, administrative, low-cost, and focused on symbolic observance, it aligns with many past measures that have become law with modest debate. The primary risks are political/diplomatic sensitivities tied to naming and characterizing specific events and potential Senate procedural delays; absent strong opposition those risks are unlikely to block enactment, but they introduce uncertainty.
Relative to its intended legislative type, this bill is an administrative/operational amendment to title 36 that is clear in purpose and specific about dates, locations, and responsible officials, but it lacks fiscal acknowledgment and accountability mechanisms.
Whether the bill’s specific language (e.g., calling October 7 an "unprovoked" attack and singling out particular incidents) politicizes what otherwise is a symbolic recognition.
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 burdenBy naming specific incidents and describing one attack as 'unprovoked,' the bill could be criticized for taking a polit…
- Federal agenciesRequiring the flag 'any day on which the United States Flag is displayed' at many additional federal locations may incr…
- Potential burdenMandating display at embassies, consulates, and passport offices could raise protocol, security, or operational concern…
Why the argument around this bill splits.
Whether the bill’s specific language (e.g., calling October 7 an "unprovoked" attack and singling out particular incidents) politicizes what otherwise is a symbolic recognition.
A mainstream liberal would likely support the goal of honoring hostages and recognizing wrongful detention but be cautious about aspects of the bill that appear to politicize particular events or use charged language.
They would welcome measures that provide symbolic recognition for victims and their families but may question the emphasis on select incidents (for example the explicit naming of October 7 as an "unprovoked" attack) and whether symbolism is substituted for substantive policy to help hostages and detainees.
They may also want assurances that flag displays won’t be used as political signaling or to justify unrelated policy actions.
A centrist/ moderate would likely view this bill as a low-cost, broadly reasonable symbolic recognition measure that standardizes practice across federal locations while encouraging non-federal participation.
They would appreciate the bipartisan-appeal of honoring hostages but want clarity on implementation details, minimal administrative burden, and guardrails to avoid creating unnecessary bureaucracy or cultural flashpoints.
Overall they'd lean supportive if the bill stays primarily symbolic and implementation is straightforward.
A mainstream conservative is likely to strongly support the bill’s aims to honor American hostages and signal national solidarity, and will especially approve of explicit recognition of incidents tied to national security (including the October 7 attack).
They will view flag-raising as an appropriate, low-cost federal expression of support for victims and might welcome the expansion to embassies, passport offices, DOJ and other federal locations.
Some conservatives may, however, prefer that symbolic measures be accompanied by robust policy on hostage recovery and national security.
The path through Congress.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
Because the bill is narrow, administrative, low-cost, and focused on symbolic observance, it aligns with many past measures that have become law with modest debate. The primary risks are political/diplomatic sensitivities tied to naming and characterizing specific events and potential Senate procedural delays; absent strong opposition those risks are unlikely to block enactment, but they introduce uncertainty.
- Potential political or diplomatic objections to singling out and characterizing particular incidents (e.g., language describing an event as 'unprovoked' or naming a present-day hostile actor) could prompt amendments or resistance not visible in the text alone.
- No congressional budget office (CBO) cost estimate is included in the bill text; while direct costs appear minimal, agencies may identify modest implementation expenses (flags, installation, signage) that could shape negotiations.
Recent votes on the bill.
No vote history yet
The bill has not accumulated any surfaced votes yet.
Go deeper than the headline read.
Whether the bill’s specific language (e.g., calling October 7 an "unprovoked" attack and singling out particular incidents) politicizes wha…
Because the bill is narrow, administrative, low-cost, and focused on symbolic observance, it aligns with many past measures that have becom…
Relative to its intended legislative type, this bill is an administrative/operational amendment to title 36 that is clear in purpose and specific about dates, locations, and responsible officials, but it lacks fiscal ac…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.