Introduced in Senate · Cruz · read twice and referred to the Committee on Armed Services on June 12, 2025
Future Long Range Assault Aircraft Medical Evacuation and Special Operations Procurement Act of 2025 (S. 2075)
Provisions
Section 2 — FLRAA medical-evacuation and special-operations variants
§2: Discretionary acceleration authority, conditional program objectives, funding limitation, and 180-day report
Section 2 — FLRAA medical-evacuation and special-operations variants
§2: Discretionary acceleration authority, conditional program objectives, funding limitation, and 180-day report
Section 1 supplies only the short title. Section 2(a) would expressly permit, but not require, the Secretary of the Army to accelerate research, development, test, evaluation, and initial procurement for a medical-evacuation configuration and a special-operations configuration of the Future Long Range Assault Aircraft. If the Secretary exercises that authority, subsection (b) requires coordination with relevant stakeholders, alignment of the development timeline for rapid prototyping, user evaluation, and risk reduction before full-rate production, and pursuit of component and system commonality to the maximum extent practicable. Subsection (c) authorizes no additional appropriations and makes development and procurement subject to appropriations provided in advance. Subsection (d) requires the Secretary, within 180 days after enactment, to report to the congressional defense committees on development and testing status, estimated milestone, operational-testing, and fielding timelines, and anticipated future funding needs. The bill sets no appropriation amount, procurement quantity, performance threshold, required fielding date, public-reporting duty, or recurring data release.
Quoted from the bill ▸
“The Secretary of the Army may accelerate the research, development, test, evaluation, and initial procurement” … “No additional appropriations are authorized under this section.” … “Not later than 180 days after the date of the enactment of this Act, the Secretary of the Army shall submit to the congressional defense committees a report”
Countersignable goals
Likely effects — shown regardless of the goals
Permissive acceleration authority
If enacted, subsection (a) would expressly allow the Secretary to accelerate the listed acquisition activities for the two variants, but ‘may’ would not require the Secretary to exercise that authority or complete any development, testing, or procurement action.
Variant capability scope without thresholds
The medical-evacuation configuration is described in terms of telemedicine integration, patient capacity, operational reach, patient-care capability, and survivability, while the special-operations configuration is described in terms of sensors, weapons systems, launched effects, and mission modules. Those descriptions set direction but no minimum performance level, acceptance test, procurement quantity, or delivery date.
Duties nested inside discretionary action
The stakeholder, development-timeline, and commonality objectives would bind the Secretary only when exercising the subsection (a) authority. ‘Aligned,’ ‘rapid,’ and ‘to the maximum extent practicable’ leave substantial implementation judgment and do not create quantitative completion criteria.
Commonality and specialization tradeoff
Greater component and system commonality can reduce integration, logistics, acquisition, and sustainment burdens, while the two mission-specific configurations can require divergent equipment and design choices. The bill directs pursuit of commonality but does not prescribe how the Army must resolve that tradeoff.
Authorization–appropriation boundary
The section would authorize activity without authorizing additional appropriations, and any development or procurement under it would depend on money provided in advance by an appropriations Act. Enactment alone would therefore establish neither a funded program increment nor an expenditure, contract, or fielding result.
One-time congressional reporting
The Secretary would have to send the congressional defense committees a report within 180 days after enactment covering the listed status, estimated-timeline, and anticipated-funding subjects. The text does not require publication, a standard format, a later update, or proof of committee receipt.
Implementation barriers
Congressional appropriators and Army acquisition officials
The authority cannot itself fund development or procurement; implementation would require suitable advance appropriations, but the bill specifies no amount, fiscal-year allocation, procurement quantity, or priority against other FLRAA work.
Army program managers, contractors, and the test community
They would have to integrate medical systems, sensors, weapons, launched effects, and mission modules while managing airworthiness, payload, range, cybersecurity, test, and baseline-aircraft constraints that the bill does not resolve.
Army Medical Department, United States Special Operations Command, and the FLRAA program office
The participants would have to reconcile distinct mission requirements with the commonality and cost objective. The text supplies no decision rule for when specialized capability should prevail over common components or what level of commonality is practicable.
Congressional and public evaluators
The report would contain estimates rather than binding milestones or funding commitments, and the bill requires delivery only to congressional defense committees. Without a publication requirement, standard fields, or recurring update, the text supplies no guaranteed public record for verifying report delivery or later program outcomes.
Candidate outcome metrics
Department of the Army annual RDT&E Budget Item Justification for PE 0605241A, project DG5, using the separately listed ‘FLRAA MEDEVAC Development and Integration’ planned-program dollars and activity descriptions, together with clearly identified published FLRAA schedule milestones. This is an official public execution proxy, not proof of bill attribution, delivered capability, or cost reduction; overall milestones are not variant-specific, more dollars can reflect cost growth rather than progress, and no equivalent separately itemized special-operations-variant row was established.
If the bill is enacted, official confirmation that the Army submitted the §2(d) report by enactment plus 180 days, together with the report's stated variant status, estimated milestone, operational-testing, and fielding timelines, and anticipated future-year funding needs. This is a one-time administrative record rather than a recurring series, and the bill does not require publication or public confirmation of receipt.
No recurring public official series was established for variant-specific patient-care capability, survivability, patient capacity, operational reach, special-operations mission effectiveness, component commonality, or life-cycle acquisition and sustainment savings attributable to this authority. Overall FLRAA funding and milestones must not be relabeled as those outcomes.
Conditional forecast sketches
P(Army PE 0605241A/DG5 planned-program dollars and stated development stage for the separately itemized FLRAA MEDEVAC activity in the President's Budget for FY 2028 | S. 2075 enacted by December 31, 2026 versus not enacted by that date). Resolve both arms from the first-print FY 2028 Army RDT&E justification. This is a public execution proxy, not a direct measure of acceleration, either variant's delivered capability, or causal effect.
P(Army submits the §2(d) report by the enactment date plus 180 days | enactment). Public resolution is possible only if the Army or a congressional defense committee confirms submission or receipt; the bill does not require publication.