PLATOON
DRONE INTEGRATION

Team Composition and Roles

The drone team leader receives tasking from the platoon commander: "reconnoiter the route 500 meters east" or "engage vehicle at grid reference." The team leader distributes tasks among pilots, coordinates with Lisa 26 for ISR support from Fischer 26, manages battery rotation, and conducts AAR after each mission. The team leader does not fly — managing three simultaneous pilots and maintaining situational awareness on the Lisa 26 tablet requires full cognitive capacity. A team leader who also flies loses oversight of the other pilots and misses critical COP updates.

Three FPV pilots rotate in pairs: two active, one resting. After 2-3 hours of continuous FPV operation, reaction times measurably increase and target identification accuracy drops below acceptable levels. Ukrainian data from 2023-2025 shows that pilot error rates double after 3 hours without rest. The third pilot ensures 8 hours of continuous drone coverage through rotation. During rest, the third pilot charges batteries, conducts minor repairs, and monitors radio traffic.

The ISR operator controls non-FPV assets: expendable ISR drones for dangerous reconnaissance passes, observation drones for static overwatch, and coordinates with the Fischer 26 operator at company or battalion level for persistent surveillance tasking. In units without a dedicated ISR operator, the team leader absorbs this role — but this degrades both functions.

Positioning and Communication

The drone team positions 200-500 meters behind the forward line of contact. This distance provides physical protection from direct fire while maintaining short cable runs to antenna masts and visual contact with the platoon commander. FPV operational range extends 3-8 km through MANET relay — Fischer 26 at 300 m AGL provides the relay link that extends ground-level FPV range from 1-2 km (direct, obstructed by terrain) to 5-8 km (relayed through airborne node with clear line of sight in all directions).

Position selection criteria: cover from direct fire (building, terrain feature, dug-in position), access to 12V power (vehicle or portable station), direct line of sight to Fischer 26 for relay, and concealment from aerial observation (trees, camouflage net). The team avoids positioning on hilltops — while radio performance is better with elevation, the team becomes visible to enemy observation drones and vulnerable to artillery.

Communication: Lisa 26 tablet shows the brigade COP filtered to display only the platoon's sector and relevant adjacent units. The team leader sees all blue force drone positions, Fischer 26 ISR detections, L2 recommendations, and the electronic warfare picture from SDR stations. Voice communication with the platoon commander via squad radio (encrypted, short range). Data communication via Silvus MANET mesh (encrypted, brigade-wide through relay chain).

The Kill Chain — Detection to Strike

Step 1 — Detection: Fischer 26 at 300 m AGL detects a vehicle at 4 km range using YOLOv8 thermal model. Detection confidence: 78%. Lisa 26 L1 pushes the detection to all COP displays automatically. Orange icon appears on the team leader's tablet. Time: 0 seconds (automated).

Step 2 — Recommendation: Lisa 26 L2 generates a strike recommendation. "Vehicle at PA 2345 6789, class T-72, confidence 78%. Recommend FPV approach from south-southwest (sun behind attacker at current time). Nearest blue force: 800m north. Fratricide check: CLEAR." Recommendation appears on team leader's tablet. Time: +2 seconds (automated).

Step 3 — Approval: Platoon commander reviews recommendation on team leader's tablet or receives verbal briefing. Checks ROE: vehicles in this sector pre-approved for platoon-level engagement. Approves. Time: +30-120 seconds (human decision).

Step 4 — FPV launch and strike: Team leader briefs pilot: "Target vehicle 3.2 km south-southwest, approach from 210 degrees, thermal will show hot engine." Pilot launches FPV, flies approach using Fischer 26 video feed as reference on second screen, acquires target visually at 500m, enters terminal dive. Strike. Time: +60-180 seconds (flight time dependent on range).

Step 5 — BDA: Fischer 26 adjusts orbit to overfly strike location. Camera captures post-strike imagery. Lisa 26 AI compares pre and post frames. Assessment: fire (engine destroyed), broken track (immobilized), or no visible damage (miss — re-attack). Time: +30-60 seconds after strike.

Total cycle: 2-5 minutes from initial detection to confirmed BDA. This is the target. Units that achieve this consistently dominate the close fight. Units where the cycle takes 10-15 minutes (common in early Ukrainian experience before procedural optimization) lose targets to movement before FPV arrives.

Sustainment and Endurance

Battery consumption at moderate intensity (5 sorties per hour): 5 batteries per hour consumed, 4 batteries per hour charged (one Q6 Pro with 4 ports at 25 minutes each). Net deficit: 1 battery per hour. Eight pre-charged batteries at mission start provide 8 hours of moderate operations before the team needs resupply. At high intensity (10 sorties per hour): 10 batteries consumed, 4 charged. Net deficit: 6 per hour. Pre-charged stock lasts 1.3 hours. Solution: second charger (€60) doubles throughput to 8 per hour, extending high-intensity endurance to 4 hours.

Drone attrition: Publicly reported Ukrainian operational data indicates FPV loss rates of 60-80% per sortie (most are expended on target, not recovered). At 5 sorties per hour with 60% loss: 3 drones lost per hour. Starting stock of 4 drones (Case 1) lasts 1.3 hours. Resupply cycle: company logistics delivers replacement drones every 2-4 hours from battalion drone depot. The drone team leader must communicate consumption rate to the company quartermaster proactively — waiting until stock is zero means 2-4 hours without drone capability while resupply arrives.

Try the interactive Decision Engine Simulator →

Try the interactive Link Budget Calculator →

Open the interactive Decision Engine →

Open the interactive Link Budget Calculator →

Open the interactive Coverage Planner →

Platoon Drone Roles and Equipment

Implementation

# Platoon Drone Team Readiness Check — Pre-mission Gate
class DroneTeamReadiness:
    """Automated pre-mission checklist for platoon drone team."""

    REQUIRED_CHECKS = [
        "fpv_drones_charged",
        "fpv_drones_bound_to_tx",
        "fischer26_charged",
        "manet_radios_programmed",
        "lisa26_sync_complete",
        "medical_kit_present",
        "spare_antennas_present",
        "casevac_plan_briefed",
    ]

    def __init__(self):
        self.status = {k: False for k in self.REQUIRED_CHECKS}

    def mark_complete(self, check: str):
        if check in self.status:
            self.status[check] = True

    def is_ready(self) -> tuple[bool, list[str]]:
        """Return (ready, list_of_blockers)."""
        blockers = [k for k, v in self.status.items() if not v]
        return (len(blockers) == 0, blockers)

readiness = DroneTeamReadiness()
for item in ["fpv_drones_charged", "fischer26_charged", "lisa26_sync_complete"]:
    readiness.mark_complete(item)

ready, missing = readiness.is_ready()
print(f"Ready: {ready}")
if not ready:
    print(f"Blockers: {missing}")

Related Chapters

Sources

Ukrainian drone platoon integration practices 2023-2026. Swedish Armed Forces plutonsstridsreglemente. FSG-A field experience. ISDT Q6 Pro specifications. Silvus Technologies MANET range data.