Referred to the Committee on Armed Services, and in addition to the Committee on Veterans' Affairs, for a period to be subsequently determined by the Speaker, in each case for con…
The Flight 293 Remembrance Act requires the Secretary of Defense, with VA consultation, to identify non‑combat military plane crashes categorized as Operational Loss/Non‑War Loss (starting with 1984 records, earlier crashes via other sources), create a public database of service members who died in those crashes, provide targeted assistance and a designated DoD point of contact for affected families, consult outside experts, and report to Congress within two years. The bill also applies certain federal nondiscrimination requirements to programs funded under the Act and directs agencies to issue implementing regulations.
Liberals emphasize strong funding, inclusivity, and privacy safeguards
Relative to its intended legislative type, this bill establishes clear administrative obligations for the Department of Defense (in consultation with VA) to identify non‑combat military plane crashes, create a public database, provide family assistance, appoint a designated point of contact, and report to Congress.
The Flight 293 Remembrance Act requires the Secretary of Defense, with VA consultation, to identify non‑combat military plane crashes categorized as Operational Loss/Non‑War Loss (starting with 1984 records, earlier crashes via other sources), create a public database of service members who died in those crashes, provide targeted assistance and a designated DoD point of contact for affected families, consult outside experts, and report to Congress within two years.
The bill also applies certain federal nondiscrimination requirements to programs funded under the Act and directs agencies to issue implementing regulations.
Substantively modest and bipartisan-leaning, but administrative costs, privacy or legal technicalities and legislative calendar compete with priorities.
Relative to its intended legislative type, this bill establishes clear administrative obligations for the Department of Defense (in consultation with VA) to identify non‑combat military plane crashes, create a public database, provide family assistance, appoint a designated point of contact, and report to Congress. It sets reasonable timelines for initial deliverables and specifies report contents and nondiscrimination applicability.
Liberals emphasize strong funding, inclusivity, and privacy safeguards
These are examples from the analysis, not a ranked list of the most-affected groups.
Liberals emphasize strong funding, inclusivity, and privacy safeguards
Generally supportive.
Sees the bill as acknowledging families of non‑combat losses, improving benefits access, and increasing transparency.
Would push for strong implementation, funding, privacy protections, and inclusive outreach.
Cautiously supportive.
Approves objectives—supporting families and transparency—but wants clear cost estimates, timelines, and legal clarity about the nondiscrimination enforcement approach.
Generally favorable to honoring fallen service members but wary of expanded federal bureaucracy, regulatory implications, and new ongoing costs.
May seek limits on scope and clearer protections for privacy and state roles.
Reached or meaningfully advanced
Reached or meaningfully advanced
Still ahead
Still ahead
Still ahead
Substantively modest and bipartisan-leaning, but administrative costs, privacy or legal technicalities and legislative calendar compete with priorities.
The bill has not accumulated any surfaced votes yet.
Liberals emphasize strong funding, inclusivity, and privacy safeguards
Substantively modest and bipartisan-leaning, but administrative costs, privacy or legal technicalities and legislative calendar compete wit…
Relative to its intended legislative type, this bill establishes clear administrative obligations for the Department of Defense (in consultation with VA) to identify non‑combat military plane crashes, create a public da…
Go beyond the headline summary with full stakeholder mapping, legislative design analysis, passage barriers, and lens-by-lens tradeoff breakdowns.