The Remotely Piloted Systems Handbook

---

RPS provides ISR, logistical and strike support via remotely piloted systems.

This is a temporary skill block, the skill block is being used to accumulate SP for time spent as UAS until it's role card is completed.

Your role access is determined by your skills, experience with those skills, and the specific roles that utilize them. With over 100 roles in UNITAF, creating detailed skill breakdowns for every role is a substantial undertaking that cannot be completed overnight. 

Estimated Role Cards

To ensure the entire unit can transition to the new system immediately, some roles are tagged as **"Estimated"**. These roles use a transitional approach:

• Temporary skill blocks simulate role-specific experience
• Estimated access levels are calculated based on these placeholder blocks
• Similar to LTS functionality but with improved accuracy and fewer limitations

Current State: Estimated roles provide functional access levels that closely mirror the previous LTS system while addressing many of its shortcomings. As development progresses, estimated role cards will be upgraded to the full FTS3 standard with detailed, role-specific skill requirements.

Important Note: When roles transition from "Estimated" to "Verified" status, your access level may change (either increase or decrease) as the requirements become more precise and role-specific.

This approach allows UNITAF to:

• Maintain operations during the transition period
• Provide immediate access to the improved FTS3 system
• Ensure continuity while detailed role cards are developed
• Gradually improve role accuracy over time

The estimated system serves as a bridge, ensuring no disruption to unit operations while we build toward the comprehensive FTS3 vision.

Leaders balance mission success against force preservation. Risk must be deliberate, not accidental. Risk management is the identification and control of hazards to preserve combat effectiveness while accomplishing the mission.

Risk Process

1. Identify hazards (enemy, terrain, logistics, etc).
2. Assess severity and likelihood.
3. Apply mitigation.
4. Accept or adjust based on mission value.

Example mitigation methods

• Adjust route or formation.
• Increase reconnaissance.
• Reallocate assets.
• Modify tempo.
• Establish reserves.

• Identify hazards affecting each individual before committing them to action.
• Compare expected gain against probability and severity of becoming a casualty.
• Adjust positioning, tasking, or support to reduce individual exposure.
• Avoid assigning disproportionate risk to a single individual without necessity.
• FM/BS-1409 - Disagree with orders where individual loss outweighs tactical value.
• Reassess exposure continuously as the situation changes.

• Assess how an action affects the element’s overall combat effectiveness.
• Weigh mission gain against potential degradation (casualties, supply loss, immobility).
• Modify plans to reduce exposure while maintaining intent.
• Avoid actions that create irreversible degradation without decisive payoff.
• Preserve reserve combat power for follow-on tasks.
• Disengage or reposition when risk exceeds sustainable limits.

Command is the authority to decide and prioritise.
Control is the regulation and direction of forces to implement decisions.

Command

• Establishes intent.
• Allocates resources.
• Sets priorities.

Control

• Issues instructions.
• Synchronises timing.
• Adjusts actions during execution.

Effective leaders command centrally and control selectively to preserve initiative.

Accept responsibility for decisions and outcomes within the element:

• Address errors immediately through constructive feedback and corrections, not public blame.
• Capture faults, causes, and responsibility during AARs for formal follow-up if required.

Maintain control of of the element:

• Issue clear tasks aligned with intent to all subordinate elements.
• Monitor execution and intervene when elements drift off task.
• Maintain continuous two-way information flow up and down the chain.
• Synchronise subordinate actions to prevent isolation or conflict.
• Re-task or re-prioritise elements as the situation changes.

• Maintain calm posture, tone, and decision-making under stress.
• Issue clear, deliberate orders during friction or failure.
• Suppress visible frustration, panic, or emotional reactions.
• Take appropriate measures to stabilise the element during unexpected events.

Commander’s Intent defines the purpose of an operation, the desired end state, and the key effects required to achieve mission success. It provides direction without prescribing detailed execution, enabling subordinate leaders to act independently while remaining aligned with higher objectives.

Commander’s Intent exists at every level of command:

• Fireteam level: intent clarifies the immediate objective and priority of effort (e.g. suppress, secure, clear, hold). It ensures members understand what must be achieved if communication is lost or conditions change.
• Squad level: intent describes the squad’s role within the platoon plan, the decisive action required, and the conditions that define success. It guides manoeuvre, tempo, and risk decisions.
• Platoon level: intent establishes how squads combine to achieve a broader tactical effect. It identifies the main effort, supporting efforts, and the operational end state.
• Company level: intent defines the overall tactical objective, desired battlefield conditions, and acceptable risk. It shapes subordinate planning and ensures unity of effort across multiple platoons.

Commander’s Intent allows initiative within boundaries. When plans break down, leaders act in accordance with intent rather than waiting for orders. Clear intent preserves momentum, cohesion, and operational effectiveness at every level.

Keep your direct subordinates informed with all the needed information for them to function:

• Updates on the tactical situation
• Current tasking and intent

Ensure you give enough information so that another person can take over leadership without needing additional information.

When preparing for a mission, take care of the following:

• Bring the correct equipment, in the right quantities
• Set standard formations, plans for movement and other actions-on
• Ensure succession of command is clear

Make decisive decisions:

• Make a clear decision in a timely manner in line with the commander's intent, even when information is incomplete.
• Communicate the decision clearly to the element.
• Commit to the decision and direct execution without hesitation.
• Avoid repeatedly changing decisions unless the situation has materially changed.
• Maintain confidence and composure to reinforce cohesion and trust within the element.

Evaluate the element’s combat effectiveness, resources, and condition before and during task execution:

• Recognise when assigned tasks exceed current capability or risk becoming unachievable.
• Identify indicators that continued action will result in unnecessary losses or mission failure.
• Decide to pause, withdraw, or disengage when risk outweighs potential gain.
• Communicate limitations and recommended actions clearly up the chain of command.
• Preserve personnel and equipment to enable future tasking and continued operations.

Dominating the battlefield is the ability to control the tempo, positioning, and flow of combat to achieve objectives while limiting enemy freedom of action.

Key methods of achieving dominance:

• Control key terrain: High ground, choke points, avenues of approach.
• Maintain initiative: Force the enemy to react.
• Coordinate forces: Synchronize squads, fire teams, and support.
• Situational awareness: Monitor the battlefield to make informed decisions.

Why It’s Important:

• Reduces risk to friendly forces.
• Limits enemy options and predictability.
• Maintains operational tempo.
• Maximizes combat effectiveness.
• Increases likelihood of mission success.

Follow the CLAP mnemonic to use with every order:

• Clear: issue direct, concise and actionable tasks.
• Loud: ensure you are heard over chatter, comms and combat.
• As an order: assert what you are saying is an order, and not something else like a question.
• with Pauses: Break up the order in to short phrases separated by short pauses to allow the receiver to process the content.

When issuing an order, use the following format:

• Who: who is expected to execute the order
• What: the thing that needs to be done
• When: when to start the execution

When given an order, confirm the order and make a plan and act to implement the intent of the order. When unable to act, make this clear to avoid misunderstandings or timing issues.

When disagreeing with a given order: 

• Communicate your objection
• State the reason and 
• If possible suggest an alternative. 

If despite the disagreement the order is confirmed, execute it to the best of your ability without complaint or argument.

Be mindful to not disagree with every order, keeping in mind that there might be reasons not yet apparent why the order is given.

Wherever possible, delegate tasks to subordinate elements. Trust people to do the task they are assigned, and give them the needed freedom to do so without interfering.

In other words, tell people what you want, not how to do it.

• Moderate and arbitrate the discourse between subordinate elements. In stressful environments, tensions can occasionally rise high, so it is important to nip conflict or negative sentiment in the bud before it infects the entire team.
• Ensure everyone feels like a valued and included part of the team
• Prevent the team from sliding into an overly casual atmosphere, where nobody is taking anything serious anymore. There is a time for laughter, and a time for focus.

• Use operational situations as teaching opportunities when time permits.
• Explain the reasoning behind decisions and actions.
• Guide individuals to arrive at conclusions rather than simply issuing correction.
• Issue immediate corrective commands when required by tempo or risk.
• Conduct follow-up explanation during AAR if correction was time-critical.
• Maintain professional tone; avoid belittling or ego-driven instruction.

• Prevent people or elements from wandering off
• Actively steer people when needed
• Allow for looser formations when in low risk areas, as maintaining strict cohesion takes energy that is better used when in combat

When taking a casualty, focus on winning the engagement as the primary priority:

• If stationary, ensure the minimally needed amount of people are working on the casualty, and only if those people are not needed for the engagement
• If moving, ensure the movement continues, taking the casualty along deferring treatment to after the movement is complete

When the situation allows, transfer the casualty to higher levels of care, unburdening the element.

• Ensure people have access to enough supplies to sustain the current pace of combat, taking into account the speed at which new supplies can be delivered.
• Proactively request resupply as soon as a need can be anticipated, allowing for the maximum amount of time for the supply chain to work. 
• Share supplies to maintain all-around fighting ability
• Limit the usage of supplies when running short

An element can only move as fast as the heaviest person. This means that, to the greatest extent possible, all equipment should be distributed among the members of the element, to equalise weight.

A couple of examples:

• Have people carry their own PAK and other medical supplies
• Distribute ammo between members, instead of having the dedicated roles carry everything. This includes ammo that might not be usable by the person carrying it

Fixed-wing aircrew support ground forces and are often a small part of the ORBAT. Missions are built around infantry, not aircraft. Seeing enemy units early (such as game master-spawned threats) doesn’t mean they should be engaged. Only act if the threat is imminent to ground forces or on instruction. Early action can disrupt mission pacing.

If an AO isn’t populated, simulate using radio communications with mission support. Ask what would realistically be seen, then report accordingly. This preserves immersion and supports the scenario. Good pilots enhance the mission by staying in sync with the bigger picture, not exposing technical boundaries.

Game masters may divert aircraft to other areas to maintain mission flow or populate areas without interference. This is due to Arma’s performance limits. Pilots should avoid unprompted engagement and work with mission staff to simulate realistic behaviour instead of acting on everything they see.

Takeoff from a runway using the following method:

1. Line up along the centre line of the runway
2. Lower the flaps to the halfway position; if the aircraft has capability.
3. Smoothly throttle up to 100%
4. After reaching the aircraft specific rotation speed, smoothly pull the nose up to achieve 10 degrees of climb.
5. Retract the landing gear after achieving a positive rate of climb.
6. Retract the flaps.

• Maintain assigned holding altitude within ±50 meters.
• Apply smooth, minimal control inputs to prevent oscillation or overcorrection.
• Anticipate aircraft pitch and power changes to stabilize climb/descent trends early.
• Utilize onboard Altitude Hold systems when available to maintain consistent altitude.
• Continuously cross-check altitude instruments while in holding patterns.

• Maintain assigned heading within ±2 degrees during CAS runs, cargo drops, and paradrop operations.
• Establish heading prior to run-in and minimize lateral corrections once stabilized.
• Use available heading references (DUI, MFD, or compass display) to confirm alignment.
• Apply smooth roll inputs to prevent overcorrection and heading oscillation.
• Utilize onboard Heading Hold systems when available to maintain directional stability.

• Climb or descend to assigned orbit altitude prior to entering orbit pattern.
• Navigate to the assigned focal point and establish the required orbit radius.
• Maintain assigned orbit direction (clockwise or counterclockwise) without reversing unless directed.
• Apply small, smooth control inputs to preserve stable turn rate and altitude.
• Continuously monitor altitude, radius distance, and ground reference point during orbit.
• Anticipate aircraft drift and correct early rather than applying large corrections.

Land on a runway using the following method:

1. Visually align with the runway centerline when possible.
2. Reduce throttle and use air brakes to reach approach speed while remaining above stall speed.
3. Lower flaps fully and extend landing gear prior to final approach.
4. When crossing the runway threshold, reduce throttle to 0% and slightly raise the nose to reduce descent rate.
5. Slowly lower the nose to allow the nose wheel to make contact with the runway.
6. Apply wheel brakes and air brakes to slow the aircraft (if available).
7. Maintain runway alignment while decelerating to taxi speed.
8. Follow Air Traffic Control instructions and exit the runway using the directed taxiway.

• Position cargo close to the aircraft loading point, typically the rear cargo access area.
• Load cargo using one of the available interaction methods:
• Use the cargo interaction menu to select Load and then select the aircraft as the target.
  • Use the interaction scroll menu on the aircraft, select cargo, then select Load/Unload as required.
• For unloading cargo:
  • Interact with the aircraft, select the cargo inventory, then select Deploy/Unload.

Paradrop troops/cargo using the following method:

1. Identify and confirm the designated LZ prior to approach.
2. Calculate drop alignment point above the LZ, accounting for wind strength and direction. Flying into the wind is preferred to improve drop accuracy.
3. Establish level flight at low, stable airspeed during approach to the drop point.
4. Perform the drop
   1. For cargo drops: initiate drop sequence approximately 7 seconds before reaching the drop point using the cargo interaction menu
   2. For troop drops: announce drop status over comms:
      1. Communicate “RED LIGHT” to the Jump Master 20 seconds before reaching the LZ.
      2. Communicate  “GREEN LIGHT” to the Jump Master 10 seconds before reaching the LZ.
5. Maintain steady flight path through drop execution.
6. After release, immediately egress from the drop zone and resume mission flight profile.

Used when anti-air threats are possible. The aircraft approaches, fires ordnance (typically rockets), then immediately turns away before crossing over the target. The distance of the break depends on enemy threat range, reducing exposure to return fire.

Used when enemy anti-air threats are minimal or absent. The aircraft flies directly at the target, fires forward-facing weapons like rockets or cannons, and exits by flying over or near the target. Other ordnance such as bombs may be dropped using this method.

Dive attacks improve accuracy for rockets, bombs, and cannon fire by tightening the impact pattern and reducing timing errors.

Two primary dive attack profiles are used:

• A high-altitude dive begins with a run-in at altitude, followed by a nose-down dive onto the target.
• A pop-up attack uses a low-altitude terrain-following approach to mask the aircraft, then a sharp pull-up into a steep climb and immediate dive onto the target.

Steeper dives increase accuracy but reduce reaction time. Balance dive angle, speed, and weapon type for safe, effective strikes. Laser-guided bombs benefit from altitude; cannon fire spreads more at longer ranges.

The RPV terminal provides command, control, and situational awareness for unmanned platforms. The interface displays map-based platform locations and allows selection via map icons or callsigns. Platform feeds and controls may vary based on vehicle capabilities.

Telemetry data provides operational indicators but should not be treated as absolute system health data.

Common telemetry fields include:

• STAT - General platform condition.
• FUEL - Remaining fuel.
• WPN - Weapons and ammunition status.
• POS - Grid location.
• AZT - Bearing.
• SPD - Speed.
• ALT - Altitude.

Operators should use telemetry to support, not replace, tactical judgment.

• Access the UAV terminal through the interaction menu.
• Identify the desired RPV using map icons or callsign selection.
• Connect terminal control to the selected RPV.
• Select available pilot or weapon operator seats when applicable.
• Confirm sensor and telemetry feeds are functioning after connection.

The TYPE setting determines what an RPV will do upon reaching a waypoint. Selecting the appropriate type allows operators to control movement behaviour, engagement posture, and loiter patterns.

• MOVE
  • The RPV will move to the waypoint location and attempt to remain stationary.
  • If it cannot remain stationary, it will orbit the waypoint.
• DESTROY
  • The RPV will attempt to destroy the targeted entity.
    • This method is not highly reliable since UAV terminals cannot directly target entities with high precision.
• SEEK AND DESTROY
  • The RPV will attempt to visually detect enemies near the waypoint and engage according to its WCS.
  • This method is not consistently reliable due to detection limitations.
• HOLD
  • The RPV will move to the waypoint and remain in position, orbiting if necessary.
    • Useful for staging operations since additional waypoints can be prepared without forcing immediate movement.
  • To release HOLD, delete or change the waypoint type to MOVE.
• SENTRY
  • The RPV will move to the waypoint and hold position.
  • The RPV will attempt to detect and identify unknown units, then determine friendly or hostile status before continuing.
  • May engage hostile units while moving to the next waypoint.
• GUARD
  • Not usable in most cases, as it requires editor-set triggers to function.
• SUPPORT
  • The RPV will move to the waypoint and loiter until a unit requests support through the in-game support system.
  • Use is generally limited.
• CYCLE
  • The RPV will move to the nearest MOVE waypoint associated with the CYCLE waypoint and repeat the waypoint loop.
  • Useful for establishing patrol routes with multiple waypoints.
  • The cycle continues until the CYCLE waypoint is removed or modified.
• LOITER
  • The RPV will orbit the waypoint location.
  • Loiter radius can be adjusted through the context menu after selection.
• LAND
  • The RPV will attempt to land at the selected location.
  • Fixed-wing RPVs require a recognized airstrip.
  • Rotary-wing RPVs can land in open areas but are more reliable when using designated landing zones or helipads.

The BEHAVIOR setting controls the RPV’s Weapons Control State (WCS) and determines how it will respond to potential targets. It is recommended to set RPV WCS to NEVER FIRE to ensure all weapons employment is controlled by a human operator. 

WCS Options

• NEVER FIRE
  • The RPV will not fire weapons under any circumstances.
  • Requires human authorization for all weapon employment.
• HOLD FIRE
  • The RPV will not engage targets unless explicitly ordered.
  • Provides strict control over weapon release.
• HOLD FIRE, ENGAGE AT WILL
  • The RPV may only engage targets that directly threaten it or friendly forces.
  • Provides limited autonomous defence capability.
• OPEN FIRE
  • The RPV may engage targets without waiting for additional authorization.
  • Increases responsiveness but reduces operator control.
• OPEN FIRE, ENGAGE AT WILL
  • The RPV may freely engage targets within WCS and threat parameters.
  • Provides maximum autonomy but carries the highest risk of misidentification or unintended engagement.

The ALTITUDE setting determines the height a UAV will attempt to maintain while moving toward a waypoint. Altitude cannot typically be adjusted at the current location, so altitude changes usually require setting a new waypoint or manually controlling the UAV.

Selecting appropriate altitude improves survivability and mission effectiveness. Higher altitudes are generally sufficient to reduce the effectiveness of small arms fire against small UAVs (sUAVs), while still allowing for effective surveillance and navigation.

Altitude selection should balance:

• Threat exposure
• Sensor effectiveness
• Mission requirements
• Airspace deconfliction with friendly assets

• Create waypoints using map controls.
• Modify waypoint behaviour using the waypoint context menu.
• Use waypoint tasking to direct RPV movement and mission behaviour.
• Adjust waypoint parameters as mission conditions change.

RPV sensor systems provide situational awareness for ISR and targeting support. Operators should focus on interpreting sensor information rather than platform-specific interface layouts.

Displays typically present:

• Left side: Speed, altitude, camera angle, grid location, and time.
• Centre: Bearing, camera direction, target range, crosshair alignment, and magnification.
• Right side: Target grid and range data.

Common imaging modes include visual, night vision, and thermal (white-hot or black-hot).

Auxiliary sensors or AI-assisted detection systems may display contact markers within the sensor field of view. Detection reliability may vary based on platform capability and environmental conditions.

Map and navigation overlays may be used to maintain spatial awareness and confirm platform orientation.

• Adjust zoom using platform zoom controls.
• Switch imaging modes using platform imaging controls.
• Lock or unlock targets using targeting controls.
• Slew turret to map or grid locations using map or grid input functions.
• Place map markers to report contacts using appropriate communication channels.
• Measure distance and azimuth using two-point measurement tools.
• Maintain visual tracking of targets when conducting ISR or fire support observation.

RPVs are manually controlled using methods similar to their manned platform counterparts. Refer to applicable flight ( FM/G204 - Take off and landing and FM/G122 - Fixed wing flight basics) and vehicle operation guides for detailed manoeuvring principles.

All RPV weapon releases must be directly authorized and controlled by a human operator unless explicitly authorized otherwise through an OPORD or Field Leader (FL).

This policy is mandatory and applies to all RPV combat operations. Autonomous or AI-directed weapon releases are prohibited unless specifically approved through formal operational orders or command authorization channels.

• Identify a change in situation
• Cancel the attack run

• Select appropriate loitering munition variant for the target and use case
• Use turret camera to observe and track the target
• Point turret at target and press vehicle target lock
• Select airburst mode when engaging infantry or exposed targets if required

• Place launcher tube in a suitable and safe position
• Deploy the munition from the launcher
• Take control of the munition using the UAV terminal

The Switchblade is a loitering munition used by many NATO and allied forces and available in two variants. It is a disposable UAV designed to loiter over an area and strike designated targets with precision.

• Switchblade 300 is small and lightweight, allowing multiple units to be carried by a single operator. It has short range and endurance with VIS, NV, and TI imaging and a payload comparable to a 40 mm HEDP grenade, making it suitable for infantry and light vehicles. It can detonate on impact or airburst.
• Switchblade 600 is a larger variant with longer range and endurance and a payload comparable to a Javelin ATGM, making it suitable for armoured vehicles and heavier targets.

Switchblade munitions are launched from a disposable tube at an elevated angle and typically deployed from covered or rear positions. After launch, the munition loiters over the area and is controlled through a UAV terminal.

Target designation can be performed using automated waypoints or manual targeting. Automated targeting is generally discouraged due to unpredictability and policy restrictions, while manual designation using the turret camera and target lock provides better control and visual confirmation. Once a target is locked, the munition conducts a top down attack and can be cancelled or self destructed if required.

Known issue: Direct targeting through GMs remote control may not function correctly; a UAV terminal should be used for manual designation.

Loitering munitions are a type of UAV designed to loiter around an AO until a target is spotted and designated, allowing faster response than systems that must launch and transit after target acquisition.

They are distinct from other UAS in several ways. Conventional UAVs such as the MQ-9 Reaper are aircraft that deploy munitions, whereas loitering munitions are themselves the weapon. Unlike FPV kamikaze drones which are piloted directly, loitering munitions are generally more independent and guide themselves onto a designated target. They are also not recoverable once launched, making them a single-use strike asset.

Loitering munitions are most useful as a rapid response capability against HVTs or targets of opportunity, where speed and precision are more important than persistence or recovery.

Organisation

• UAS Operators MUST be organised as a distinct and separate element from the Ground Combat Element (GCE).
• The UAS Operator element MUST consist exclusively of qualified UAS Operators. No non-UAS personnel are permitted within this element.
• The UAS Operator element MUST be directly subordinate to Force Leadership (FL).
• Tasking and coordination MAY be conducted through FAC/JTAC elements where operationally required.

Deployment Restrictions

• UAS Operators MUST NOT deploy into the field alongside the Ground Combat Element under any circumstances.
• UAS Operators MUST REMAIN at STARTEX for the duration of operations.

Operational Rationale

• This policy reflects the requirement to simulate the logistical and physical constraints of UAS control systems, including:
  • Fixed, seated control terminals
  • Increased equipment footprint
• UAS systems  ARE NOT to be treated as lightweight or handheld (e.g. sUAS-style) platforms.

UAS Definition

• A UAS (Unmanned Aircraft System) is defined as the complete system required to operate an unmanned aerial vehicle.
• A UAS MUST INCLUDE all of the following components:
  • The operator
  • The control terminal
  • The aircraft (UAV)
  • Any supporting logistical infrastructure

Classification

UAS are categorised into two distinct types:

• UAS
  • Systems that REQUIRE dedicated infrastructure to operate.
  • Systems that are NOT man-portable.
•  sUAS (small UAS)
  • Systems that are fully man-portable.
  • Systems that DO NOT REQUIRE additional infrastructure beyond what can be carried by an operator.