Air Defence Training Simulator

What you asked for

“Chose “Mass Raid Prioritisation: Jets First, UAVs After, Unknowns Referred” from the list.”

Grade

30 / 100

Poor

Mission failed

Identification discipline held — zero friendlies and zero Unknowns engaged, and the three friendly tracks were allowed to overfly rather than shot at. But the engagement queue was inverted: the first shot went to the nearest UAV at T+006 and no jet was engaged until T+083, 63 seconds after TK-4101 resolved to Enemy. Four hostiles leaked, two of them jets (TK-4101 and TK-4103, the latter never engaged at all), against a pass threshold of one. Eight rounds spent, mean reaction 46.7 s. Criteria not met.

What it was judged on

Nothing hostile reached the defended area4 reached it, 1 allowed
Nothing friendly was engagednone engaged
The engagement was seen throughnothing hostile left in the air
Rounds were spent within the allowance8 spent of 12 allowed

Pass: the three fast closers are engaged at the earliest valid firing solution each offers, the unmanned wave is then serviced as a continuous queue whenever a launcher frees, and no more than one hostile reaches the site. Every Unknown is referred and none is fired upon — engaging an unresolved or friendly track fails the run outright, regardless of how many hostiles were destroyed. Holding fire with two rockets committed is correct behaviour, not inaction; breaking or retargeting a committed engagement is scored as an error even if it works. No more than twelve rounds expended.

The tally

Counted from the run itself. These are not judgements and nothing can argue with them.

Hostiles destroyedShot down before they arrived.: 6
Reached the siteGot through to the defended area.: 4
Still inboundStill closing when the run stopped — neither stopped nor arrived.: 0
Friendlies engagedFired on and it was not a threat. Fails a run on its own.: 0
Rounds spentInterceptors fired, of 12 allowed.: 8
Mean reactionFrom a hostile becoming identifiable to you firing on it.: 47s

What happened

The run was decided in the first six seconds. Your opening launch went to TK-5203, a UAV at 32 km, and your second to TK-5201 at 33 km, while three jets sat at 84-91 km closing on the site. That is the error the record names first: proximity reads as urgency on the display, but closure rate is what determines who must die first. From T+020 the jets were resolving to Enemy one after another and you had a clear long-range window on each — you did not use it until T+083, and by then the launchers and the round count were both being eaten by a UAV wave you were servicing at progressively worse geometry. TK-4103 was classified Enemy at T+035 and never had a round fired at it. It overflew at T+263. The Pk column tells the story cleanly. The two jet shots you did take were 86% at 65 km and 90% at 50 km — the cheapest kills available anywhere in this picture. Against that, your UAV engagements ran 86, 87, 79, 73, 70, 68 as each track was allowed to close before you committed. You inverted the economics: expensive short-range work on the slow threats, nothing on the fast ones until the window had mostly closed. The 'no rounds remaining' refusals from T+153 are not a supply problem, they are the arithmetic of that choice. What you got right matters and should be said plainly: no friendly and no Unknown was engaged. TK-9001, TK-9002 and TK-9003 all overflew the site unmolested, including TK-9002, which never resolved at all. Under this scenario's hierarchy that is the single most important line in the tally, and it is why this run scores above one that killed more and shot an Unknown. The one blemish on that discipline is T+076-077, where you set TK-5206 to unknown and then to enemy yourself. It was already displayed Enemy and it genuinely was, so nothing broke — but self-classifying locally is a habit the record warns against explicitly, and here it delayed the shot to 16 km and Pk 70%. One note the record does not settle: the log carries no interrogation entries and no explicit referral events, only resolutions at T+020, T+025, T+035, T+075 and T+150. Whether a referral was raised on TK-9002, which went unresolved to overflight, is not something the log shows, so I will not score it either way.

The moments that decided it

The turning points of the run, taken from what actually happened. The comments come from the knowledge base — the reasoning the domain expert recorded when this scenario was captured.

cost you
You:
Launched on TK-5203, a UAV at 32 km, as the first shot of the run (T+006), then TK-5201 at T+018
The record says:
Fire the lead jet at the earliest valid firing solution
T+006. This is the documented error verbatim: engaging the nearest UAV first because proximity reads as urgency, when closure rate — not slant range — determines who must die first. The three jets were held at 84-91 km from T+000 and were the tracks consuming the timeline. Both launchers were free and you spent them on the slowest threats in the picture.
cost you
You:
Held all jet engagement until T+083 despite TK-4101 resolving Enemy at T+020, TK-4102 at T+025 and TK-4103 at T+035
The record says:
Fire on each jet at the first valid solution the system offers, without holding for a better picture
T+020 to T+083. Sixty-three seconds of long-range window on TK-4101 went unused while the launchers cycled UAVs. The Pk figures show what that cost: the jet shots you eventually took were 86% at 65 km and 90% at 50 km — the cheapest shots of the whole run — while the UAV shots degraded 86, 87, 79, 73, 70, 68 as the wave closed. You paid short-range prices for UAVs and then had no capacity left for the jets.
cost you
You:
Set TK-5206 to unknown at T+076, then set it back to enemy at T+077, and launched at T+090
The record says:
Leave classification to the referral chain; act on the answer, do not set it locally
T+076-077. Local self-classification is a documented error even when the answer happens to be right — and here TK-5206 had been displayed as Enemy since detection at T+050, so the round trip through 'unknown' bought nothing and cost time. The engagement finally went out at 16 km for Pk 70% on a track first held at 21 km.
cost you
You:
Attempted a third launch at T+135 with both rockets committed (TK-4101 and TK-4102)
The record says:
Hold and wait for a fire status to resolve
T+135. The two-in-flight limit is a hard property of the system, and trying to force a third launch achieves nothing except lost seconds. The refusal is evidence about the queue, not the system — the reason this moment felt unwinnable is upstream, in the eighty seconds of launcher time spent on UAVs.
cost you
You:
Never engaged TK-4103; TK-4101 missed at T+140 with no capacity to re-engage; from T+153 every attempt returned no rounds remaining
The record says:
Keep both launchers continuously employed against confirmed hostiles by earliest valid solution, having cleared the fast closers first
T+140 onward. TK-4103 resolved Enemy at T+035 and was never fired on once. The string of 'no rounds remaining' refusals from T+153 to T+234 is the end state of a queue that was run backwards: capacity was gone while two jets and two UAVs were still inbound, and TK-4103 and TK-4101 reached the site at T+263 and T+284.

Practise next

Open the run by committing both launchers to the two leading jets at the first valid solution the system offers — do not let a UAV inside 35 km take your first round while a jet is held at 85 km.
Treat the classification resolution timestamp as your trigger: TK-4101 resolved Enemy at T+020, so the shot should be seconds later, not at T+083. Practise firing on resolution rather than on a tidier picture.
Stop editing classifications at the console. TK-5206 was already Enemy; leave the referral chain to answer and spend those seconds on the launch.
When both rockets are committed, sit on your hands rather than probing for a third launch as you did at T+135 — log the next target and fire the instant a status resolves.
Rehearse the UAV mop-up as a throughput problem: take the next available valid solution rather than letting each track close to 15-16 km, where your Pk fell to 68-70% and your round count ran out.

Run it again Done