The Combat Action Recognition and Evaluation (CARE) for Remotely Piloted Aircraft (RPA) Crews Act of 2025 would require the Secretaries of the military departments to establish a status identifier that is equivalent in merit to a combat status for RPA crews who conduct combat operations. The designation must be created not later than 180 days after enactment.
This creates a formal recognition pathway for remote operations and aligns RPA duties with traditional combat roles in personnel records and career milestones. The bill does not spell out funding or the detailed implementation steps, leaving those specifics to DoD policy and existing award and promotion frameworks.
At a Glance
What It Does
Not later than 180 days after enactment, the Secretaries of the military departments must establish a status identifier for RPA crews that is equivalent in merit to a combat status.
Who It Affects
RPA crews engaged in combat operations and DoD personnel management and awards offices that would implement and administer the status.
Why It Matters
Creates formal recognition for remote combat operations, potentially influencing promotions, awards, and career trajectories within the armed services.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The CARE for RPA Crews Act of 2025 creates a new combat-status-like recognition for remotely piloted aircraft crews who conduct combat operations. The bill requires the Secretaries of the military departments to establish a status identifier within 180 days of enactment that is equivalent in merit to traditional combat status.
This brings remote warfare duties into the same recognition framework as manned combat roles, enabling upcoming decisions about awards, promotions, and career progression to consider RPA combat operations in a similar light. The act does not provide funding or a detailed roadmap for implementation, leaving DoD to integrate the new status into existing personnel systems and policies.
In short, it formalizes a pathway for recognizing the risk, responsibility, and contribution of RPA crews in combat zones within the service-wide talent management ecosystem. Implementation details—such as how the status will be documented, audited, and used in eligibility determinations—will depend on DoD policy and the surrounding personnel infrastructure.
The bill aims to ensure that remote combat duties are not overlooked in formal recognition, creating parity with traditional combat roles over time.
The Five Things You Need to Know
The bill requires the Secretaries of the military departments to establish a combat-status-equivalent identifier for RPA crews within 180 days of enactment.
The identifier must bear merit-equivalence to traditional combat status.
It applies specifically to remotely piloted aircraft crews conducting combat operations.
The act codifies a formal recognition mechanism for remote combat duties within DoD personnel processes.
No funding or implementation funding is specified in the bill; DoD would determine resource needs and budgeting.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
This section designates the official citation of the act as the Combat Action Recognition and Evaluation (CARE) for Remotely Piloted Aircraft Crews Act of 2025. It clarifies how the bill should be cited in legal and policy references.
Combat status identifier requirement
Not later than 180 days after enactment, the Secretaries of the military departments shall establish a status identifier that is equivalent in merit to combat status for remotely piloted aircraft crews who conduct combat operations. This creates a formal mechanism to recognize and document remote-combat service within personnel records and related award or progression processes.
This bill is one of many.
Codify tracks hundreds of bills on Defense across all five countries.
Explore Defense in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- RPA pilots and sensor operators who conduct combat operations gain formal recognition aligning their duties with traditional combat roles.
- DoD personnel records and awards offices gain a clear framework for documenting and awarding combat-equivalent recognition.
- Unit commanders and leaders can reference a standardized status in planning, assignments, and performance assessments.
- Policy and HR teams within the services gain a structured basis for integrating remote combat roles into existing career pathways.
Who Bears the Cost
- DoD HR and IT systems will need updates to incorporate the new status in personnel records and award rules.
- Units may require training for supervisors to apply and interpret the new status consistently.
- Administrative overhead in processing, auditing, and maintaining the status could increase short-term workload for personnel offices.
- Potential adjustments to existing eligibility criteria for awards and benefits may be needed as implementation unfolds.
Key Issues
The Core Tension
Balancing formal recognition for remote combat with practical implementation across diverse DoD personnel systems and traditions—while ensuring uniform eligibility and avoiding unintended consequences or inequities.
The bill creates a recognition mechanism without specifying funding or the exact administrative architecture for implementation. Real-world adoption will require DoD policy development, integration with existing award and promotion criteria, and updates to personnel IT systems to track and verify the new status.
Potential implementation challenges include ensuring parity across service branches, preventing gaming of the status, and aligning it with current veteran and transition programs. A key question is whether the combat-status-equivalent identifier will be treated the same as traditional combat status for all purposes or retain service-specific distinctions.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.