Force-on-Force LVC

A demanding force-on-force large force employment day: a few live jets, dense synthetic opposition, live takeover of constructive tracks, per-side datalink.

Four jets in the air. A fourteen-aircraft fight on the picture.

A squadron needs a demanding force-on-force fight — a credible adversary package, radar and threat-warning cues, and a tactical datalink picture for each side — but it can only put a handful of jets in the air on the day. The Arena runs the training day with a small number of live airframes backed by a dense synthetic opposition, and makes the whole engagement hold together as one coherent, reviewable mission.

Plan

The mission director opens a saved scenario and the team builds the day together — the adversary lead shapes the hostile package and its commit timing, the controller lays in the datalink plan, and the briefing lead prepares the picture. Every entity is pre-assigned as live, virtual, or constructive across both sides. Before anyone briefs, the team scrubs the scenario timer forward to watch the fight develop, so if the hostile package commits too early they fix it while it is still cheap to fix.

Brief

The team briefs from the very same mission picture they will fly, not a separate slide deck. Push times, the threat laydown, the communications plan, and the datalink plan are all confirmed against that shared picture. A late change to a commit time is captured against the mission timeline itself, rather than left to be remembered as a verbal exception.

Execute

The mission runs under one authoritative clock, so every control-cell station sees the same elapsed time and the same picture. The adversary liaison holds the live aggressor jets off the friendly datalink while constructive aircraft present the threat package as one coherent formation; on the controller's call, each live jet merges onto the constructive track it joined — inheriting that track's number, identity, and position — so a contact crews were already working is suddenly backed by a radar return and threat-warning cues, with nothing flickering. Each side works its own independent datalink picture with correct friend/foe symbology translated automatically per side — no shared God's-eye view. When a pilot fires, the Arena detects the launch off the datalink, spawns the weapon into the simulation, and guides it so every participant sees the same shot, with the outcome assessed against geometry and the kill model and recorded.

Debrief

The team reconstructs the mission from recorded evidence: track history, the datalink picture each side actually saw, every shot and kill, and the merge and split events laid out on the timeline. The debrief follows each visible object across its handoffs, so a contact that was constructive, then live, then constructive again is told as one continuous story rather than three disconnected tracks. The squadron walks away with proof of what was trained, not an argument about what happened.

• Live takeover of constructive tracks — live jets merge onto synthetic contacts inheriting number, identity, and position
• Independent datalink picture per side, with friend/foe symbology translated automatically and no shared God's-eye view
• Live shots in the shared picture — launches detected off the datalink, spawned into the sim, and guided so everyone sees the same weapon
• A coordinated control cell working from one authoritative clock and one common picture
• Split-back and regeneration under exercise rules to keep the problem alive
• Evidence-based debrief that follows every object across its handoffs

AIR COMBAT ARENA / MISSION PROFILE

The capabilities behind the fight

Bring us the fight you need to rehearse, and we will walk you through how the Arena runs it — plan to debrief, on one coherent picture.

Related pages

• Contact ArenaLogic
• Air Combat Arena