Trainee A — Ops Console 1

Session history

• 6Mass Raid Prioritisation: Jets First, UAVs After, Unknowns ReferredEuro_ADmedium9/9/2026, 8:43:37 PM

  Requested

  “Everything arrives at once and I have to decide what to engage first. Make Iff dilemas”

  Decisions

  1. missedAttempted short-range engagements on the nearest UAVs at 29, 26 and 25 km (T+014, T+020, T+027), then committed both launchers to TRK-3303 and TRK-3301 at T+033 and T+037, leaving TRK-2101 and TRK-2102 untouchedpreferred: Fire the lead jet at the earliest valid firing solution
  2. missedAttempted a third launch at T+070 while both rockets were committedpreferred: Hold and wait for a fire status to resolve
  3. missedSet TRK-4472 to enemy locally at T+151 after an interrogation returned no reply at T+043, then launched a medium round at it at T+168 (Pk 58%)preferred: Refer to the commander and withhold fire until the track is classified Enemy
  4. missedFired the entire long-range rail at the three jets from T+198, at 24, 24 and 22 km, each at Pk 0%; all three missedpreferred: Engage the jets at the earliest valid solution at long range, keeping the launchers free for the UAV wave
  5. missedNever engaged TRK-3302, detected at 30 km at T+000 and interrogated at T+158; it reached the defended area at T+213preferred: Mop up the UAVs by earliest available valid solution inside the shorter rings, keeping both rockets continuously employed

  Debrief

  You asked for a picture where everything arrives at once and you have to choose what to engage first, with IFF dilemmas in it. You got exactly that, and the run turned on both halves of the request going the wrong way. Start with the one that failed it outright: at T+151 you set TRK-4472 — an Unknown that had never been resolved — to enemy yourself, and at T+168 you launched on it. At T+183 you destroyed a friendly helicopter. You had already watched the referral chain work twice in this same run: TRK-4471 came back Friendly at T+070 and TRK-4470 came back Our Forces at T+118, and you correctly let that one overfly the site rather than shoot it. So you knew the commander answers, and you knew roughly what it costs. The interrogation at T+043 returned 'no reply', and you appear to have read that as confirmation. It is not, and it never was — the brief told you interrogation returns nothing on any mode here, and the record says plainly that a track behaving aggressively is not a classification. In this scenario all three Unknowns were friendly and the threatening flight profile was the bait. The sequencing failed independently. TRK-2101 and TRK-2102 were displayed Enemy at second zero at 92 and 89 km, and you did not fire at a jet until T+198. In the opening 37 seconds you made three attempts to reach UAVs at 29, 26 and 25 km with a 20 km weapon, then put both launchers onto UAVs. That is the documented error of proximity reading as urgency on the display when closure rate, not slant range, decides who must die first. Everything downstream follows from it: the short rail was empty by T+122, the two-in-flight limit was occupied by UAV engagements when you tried to force a third round at T+070, and when you finally turned to the jets they were at the ragged edge of the long round's minimum range. Three long rounds went out at Pk 0% and all three missed, followed by three refusals for firing inside 20 km. The jets did not leak because the weapon failed; they leaked because they were engaged two hundred seconds late, and a leaking fast mover is the most expensive category of leaker in this record. What went right is narrow but real: you did not fire on TRK-4470 or TRK-4471 once they resolved, and the four UAV kills at Pk 90%, 89%, 77% and 83% were competently taken shots at reasonable geometry. But the mean reaction of 95.9 seconds is not a side note here — it is the mechanism by which three jets crossed the site. And TRK-3302 sat in the picture as Enemy from T+000, got interrogated at T+158 for information the system could not give you, and leaked at T+213. The habit to break is treating identification as something you can resolve at the console under time pressure. Refer it, keep shooting the tracks already marked Enemy, and act on the answer when it lands. The habit to build is committing to the fast closers at the first valid long-range solution, before proximity on the display starts making decisions for you.

  Recommended next

  • Never set an Unknown to enemy at the console. Refer TRK-4470/4471/4472-class tracks the moment they appear and leave the classification field alone — in this run the commander answered in about 40 seconds on 4471 and 88 on 4470, and both answers would have saved you the friendly kill.
  • Treat 'no reply' from the interrogator as no information. You interrogated eight tracks in this run and every one returned no reply, including TRK-2102 at T+210 which was already classified Enemy. Stop spending seconds on an interrogator that this theatre has told you is mute.
  • Commit the long rail to the fast movers inside the first 30 seconds, at 70 km, before touching anything inside the medium ring — not at T+198 when TRK-2101/2102/2103 were at 22–24 km and the solution had already collapsed to Pk 0%.
  • When both rockets are in the air and something crosses the short ring, hold and let a fire status resolve rather than attempting a third launch as you did at T+070. If that moment feels unwinnable, the fault is in the order you built the queue, not in the limit.

  Open the debrief as the trainee saw it
• 8Mass Raid Prioritisation: Jets First, UAVs After, Unknowns ReferredEuro_ADmedium9/7/2026, 6:45:13 PM

  Requested

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

  Decisions

  1. missedLaunched long range at TK-202, a UAV at 30 km, as the first shot of the run while TK-101 (90 km) and TK-102 (84 km) sat unengaged.preferred: Fire the lead jet at the earliest valid firing solution.
  2. missedInterrogated TK-301 at T+026, got no reply, and set it to enemy yourself at T+035.preferred: Refer to the commander and withhold fire until the track is classified Enemy.
  3. missedLaunched short range at TK-302 at T+043, then set TK-302 to enemy at T+046 — the classification came three seconds after the missile.preferred: Refer to the commander and withhold fire until the track is classified Enemy.
  4. missedInterrogated TK-303 at T+053, got no reply, self-classified at T+063 and fired at T+066.preferred: Refer to the commander and withhold fire until the track is classified Enemy.
  5. missedSpent the medium ring on TK-301 at T+097 (Pk 75%) while TK-101, TK-102 and TK-103 were all still inbound and unengaged.preferred: Keep both launchers continuously employed against confirmed Enemy tracks by earliest valid solution.
  6. missedFirst jet engagement of the run came at T+130 against TK-103; TK-102 and TK-101 not committed until T+204 and T+211, at 23 km and 25 km on the medium ring.preferred: Fire the jets at the earliest valid firing solution the system offers, at long range.
  7. missedInterrogated TK-101 at T+218, seven seconds after firing on it.preferred: Identification work belongs before commitment, not after.

  Debrief

  You engaged three friendly tracks and destroyed all three. TK-302 was a friendly helicopter, TK-303 a friendly UAV, TK-301 our own forces. That fails the run outright and nothing else in it changes that. The mechanism was the same each time: TK-301 and TK-303 you interrogated, got "no reply", and set to enemy yourself; TK-302 you never interrogated at all and fired on at T+043, three seconds before you got round to classifying it. The record is unambiguous — an Unknown is a question, not a permission, and classification goes to the commander, who answers in about fifteen seconds. No reply is not proof of hostility and never was. All three Unknowns in this scenario were friendly, and the aggressive-looking profile was the bait. The sequencing was inverted as well. Your first commitment of the run at T+009 went to TK-202, a UAV at 30 km, while TK-101 at 90 km and TK-102 at 84 km sat untouched. That is the documented error of reading slant range as urgency when closure rate is what decides who must die first. It cascaded: the first jet was not engaged until T+130, and TK-102 and TK-101 were not committed until T+204 and T+211, taken at 23 and 25 km on the medium ring at 75-76% when the long-range window had been available from the opening seconds. They died, but because the timeline was generous, not because you sequenced them. The medium-ring shot at TK-301 at T+097 is the clearest single example of what the record calls letting the Unknown pull launchers off the jets — thirty-two seconds of launcher capacity spent killing our own aircraft while three fast closers ran in unengaged. The numbers you will point to are ten hostiles destroyed and zero leakers, and those are real. They came from a picture that gave you time, not from a queue you managed. Thirteen interceptors against a ceiling of twelve, three of them fired at friendlies, is the arithmetic of that: the rounds you spent on TK-301, TK-302 and TK-303 are exactly the margin you overran by. Mean reaction of 109 seconds tells the same story from the other end — the jets were left to close for over three minutes. The habit to break is not tactical, it is procedural. You did the identification work on two of the three Unknowns and then overrode your own result. Fifteen seconds of referral would have cost you nothing against this timeline and would have turned a failed run into a passable one.

  Recommended next

  • Make the referral to the commander on every Unknown and wait for the answer before any launcher is assigned — TK-301, TK-302 and TK-303 all had fifteen seconds of slack available and none were referred.
  • Treat a "no reply" interrogation as unresolved, not as hostile. TK-301 at T+026 and TK-303 at T+053 both returned no reply and both were friendly.
  • Commit the fastest closer first: with TK-101 at 90 km and TK-102 at 84 km on the board at T+000, the first long-range round goes to a jet, not to TK-202 at 30 km.
  • Take jets in the long-range window rather than letting them run to the medium ring — TK-102 and TK-101 were engaged at 23 and 25 km when a 70 km solution had been available for over three minutes.
  • Never fire before classification is set, as happened with TK-302 at T+043. If the classification is not already resolved, the launcher waits.

  Open the debrief as the trainee saw it
• 4Mass Raid Prioritisation: Jets First, UAVs After, Unknowns ReferredEuro_ADmedium9/7/2026, 1:54:14 PM

  Requested

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

  Decisions

  1. missedFired the first rocket of the run at UAV TK-202 at 30 km (T+011), leaving lead jet TK-101 unengaged until T+037 and TK-102 unengaged for nearly three minutespreferred: Fire the lead jet at the earliest valid firing solution; jets are prioritised because they consume the timeline, not because they are closest
  2. missedInterrogated TK-302 at T+076, read 'no reply', and launched short range at 8 km (T+079); TK-302 destroyed, it was Friendlypreferred: Refer the Unknown to the commander and withhold fire until it is classified Enemy
  3. missedLaunched short range at TK-303 at 9 km (T+101) with no interrogation entry in the log at all; destroyed, it was Friendlypreferred: Refer and withhold — nothing may be fired on unless classified Enemy
  4. missedLaunched medium range at TK-301 at 15 km, Pk 66% (T+123); destroyed, it was Our Forcespreferred: Refer and withhold; keep the launchers on confirmed Enemy tracks
  5. missedEngaged TK-102 at 33 km (T+171) and TK-103 at 18 km (T+214), after clearing six UAVs and three friendliespreferred: Take the jets at first valid long-range solution, then mop up the UAVs inside the shorter rings
  6. missedHeld TK-205 until 3 km and took a Pk 58% shot at T+206; it leaked four seconds laterpreferred: Take the next available valid solution rather than holding for a short-range shot, keeping both rockets continuously employed

  Debrief

  You destroyed three friendly aircraft in this run — TK-302 at T+101, TK-303 at T+123 and TK-301 at T+147. That fails the run on its own terms, and nothing else in the log changes it. The most instructive of the three is TK-302: you interrogated it at T+076, got 'no reply', and fired eight seconds later. The record is unambiguous that no reply is not proof of hostility, and that all three Unknowns in this scenario were friendly with a flight profile designed to read as aggressive. TK-303 you engaged with no interrogation entry in the log at all, and TK-301 you took at 15 km on a 66% solution. None of the three was ever classified Enemy, and the rule was that nothing may be fired on unless it is. You asked to practise jets first, UAVs after, unknowns referred. The exercise put you in that position exactly and the run inverted all three legs of it. Your first rocket of the day went to UAV TK-202 at T+011 while TK-101 and TK-102 sat on the scope at 90 and 84 km — the documented error of reading slant range as urgency when closure rate is what matters. TK-102 was not engaged until 33 km at T+171 and TK-103 not until 18 km at T+214, after you had spent launcher capacity on six UAVs and three friendlies. TK-103's 18 km shot missed at 67%, the reshoot at 6 km was a 61% shot, and it reached the site. That is the most expensive leaker in the scoring hierarchy and it was decided in the first thirty seconds, not at the end. The rest follows from the same cause. TK-205 leaked at T+210 after you held it from 23 km at T+055 down to a 3 km, 58% shot — the mop-up error of holding for a stronger short-range solution and running out of timeline. Fifteen rounds against a ceiling of twelve is the arithmetic of shooting everything late: a jet at 79 km cost one long-range round, the same class of target at 6 km cost two and still leaked. Three refusals at T+018, T+028 and T+031 were wrong-ring selections against tracks well beyond that launcher's reach, and three more later were the two-in-flight limit — capacity you had spent on friendlies. Holding while both rockets were committed would have been correct behaviour; you never had a moment where holding was the problem. The mean reaction figure of 137 seconds is not a separate fault, it is the same fault measured differently. Tracks you saw at first detection were serviced two to four minutes later, inside the short ring, at Pk figures in the fifties and sixties, when the same targets were available at long range at high confidence.

  Recommended next

  • Treat a 'no reply' interrogation as unresolved, not as hostile. On TK-302 you had the answer and overrode it — make the commander's referral and hold until a track comes back classified Enemy before any launch authority is considered.
  • Commit the jets first, at the first valid long-range solution the system offers. TK-101 was taken at 79 km for one round at 87%; TK-102 and TK-103 were available on the same terms from the first minute and you took them at 33 and 18 km instead.
  • Refer every Unknown the moment it appears and then go back to the confirmed hostiles. In this run the three Unknowns consumed five launches and roughly seventy seconds of launcher capacity that the jets needed.
  • Stop holding UAVs for short-range solutions. TK-205 was on the scope at 23 km from T+055 and you shot it at 3 km on a 58% solution; take the next valid shot as launcher capacity frees rather than waiting for the ring to close.

  Open the debrief as the trainee saw it
• 5Mass Raid Prioritisation: Jets First, UAVs After, Unknowns ReferredEuro_ADmedium9/7/2026, 9:56:10 AM

  Requested

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

  Decisions

  1. missedAttempted a short-range engagement on a UAV at 31 km (refused), then launched medium range at TK-202 at T+011 — the first shot of the run went to a UAV while TK-101 (90 km) and TK-102 (84 km) sat unengaged.preferred: Fire the lead jet at the earliest valid firing solution.
  2. correctLaunched long range at TK-103 at T+018, 78 km, Pk 87%.
  3. missedLaunched short range at TK-302 at 9 km, Pk 83%; destroyed at T+092. It was Friendly.preferred: Refer to the commander and withhold fire until the track is classified Enemy.
  4. missedLaunched short range at TK-303 (T+093, missed), re-attacked at T+144 at 4 km Pk 62% and destroyed it; launched at TK-301 at T+119 and destroyed it at T+149.preferred: Refer, withhold fire on all three Unknowns, and keep working the confirmed hostiles.
  5. missedHeld short-range capacity on friendly re-attacks and short-range UAV shots; TK-207 was engaged at T+153 at 7 km, Pk 74%, missed, and no second shot was available.preferred: Keep both rockets continuously employed against valid solutions inside the shorter rings so no UAV reaches a point where no launcher can be brought to bear.
  6. missedLaunched long range at TK-103 (T+185, Pk 0%) and at TK-102 (T+207, Pk 0%), then re-engaged both with medium range at Pk 58% and 60%.preferred: Fire when the system offers a valid solution within system capability — not shots the system prices at zero.
  7. missedTK-101, detected at 90 km at T+000, was not engaged until T+253 at 12 km, Pk 78%; TK-102 not until T+207. Both were interrogated only after commitment (T+259, T+260, 'no reply').preferred: Fire the jets at first valid solution at long range, when they are cheapest to kill.

  Debrief

  You asked to practise mass-raid prioritisation — jets first, UAVs after, Unknowns referred. The scenario handed you exactly that, and you inverted all three legs of it. The run is failed on identification. You put four interceptors into TK-302, TK-303 (twice) and TK-301, and destroyed all three. Every one was friendly. The log carries no referral for any of them and no interrogation of any of them; the only interrogations in the whole run were of TK-101 at T+259 and T+260, after you had already launched at it, on a track the system had shown as Enemy from second zero. The record is unambiguous here: an Unknown is a question, not a permission, the commander answers in about fifteen seconds, and in this scenario the aggressive-looking flight profile of TK-301 is the bait. You took the bait, and when the first shot at TK-303 missed at T+116 you came back and took it again at 4 km for a 62% Pk. That is the documented worst outcome in this entry and it caps the score regardless of the nine hostiles you did kill. The sequencing failed independently. Your first shot of the run — after a refused short-range attempt on a UAV at 31 km — was a medium-range round at TK-202 at T+011, while TK-101 sat at 90 km and TK-102 at 84 km with the entire long-range ring available. That is the classic nearest-UAV error: proximity reads as urgency on the display, but the record says closure rate decides the queue because the jets consume the timeline. TK-103 at T+018 was the one shot you got right. TK-102 was not engaged until T+207 and TK-101 not until T+253, both inside 25 km, both after zero-Pk long-range launches at T+185 and T+207 that were pure waste. You killed all three jets in the end, but you killed them the expensive way — 17 rounds against a ceiling of 12, with the tail of the run reduced to 58–78% short-range shots. TK-207 leaked at T+189 after a 74% shot at 7 km missed and no launcher was free to re-attack. That leaker is not a bad-luck event; it is the arithmetic of having spent four rounds and two launcher slots on friendlies and two more on zero-Pk geometry. The record notes that the moment when a UAV crosses the short ring with both rockets committed is decided upstream — and yours was decided at T+011.

  Recommended next

  • Before any launch, check the track's classification field: if it reads Unknown, refer it and do nothing else with it. Do not fire on TK-301/302/303-type tracks, and do not re-attack one after a miss — the fifteen-second referral is cheap and the log shows you never paid it once.
  • Take the jets at the outer ring. TK-101 was on the display at 90 km at T+000 and you did not shoot it until 12 km at T+253 — commit each jet at the first valid long-range solution before touching any UAV, even one at 30 km.
  • Stop launching at Pk 0%. The rounds at T+185 and T+207 bought nothing and occupied launcher slots you needed for the UAV wave; wait the few seconds for a priced solution rather than firing to feel busy.
  • Treat transponder work as pre-engagement, not post-engagement. Interrogating TK-101 at T+259, after launch and on an already-Enemy track, was effort spent in the wrong place — and remember that 'no reply' is not evidence of hostility.

  Open the debrief as the trainee saw it
• abandonedMass Raid Prioritisation: Jets First, UAVs After, Unknowns ReferredEuro_ADmedium9/7/2026, 9:54:00 AM

  Requested

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

  Decisions

  0 answered before the run was abandoned; never evaluated.

• abandonedMass Raid Prioritisation: Jets First, UAVs After, Unknowns ReferredEuro_ADmedium9/7/2026, 7:29:41 AM

  Requested

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

  Decisions

  0 answered before the run was abandoned; never evaluated.

• 30Mass Raid Prioritisation: Jets First, UAVs After, Unknowns ReferredEuro_ADhard9/3/2026, 7:17:45 PM

  Requested

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

  Decisions

  1. missedLaunched on TK-5203, a UAV at 32 km, as the first shot of the run (T+006), then TK-5201 at T+018preferred: Fire the lead jet at the earliest valid firing solution
  2. missedHeld all jet engagement until T+083 despite TK-4101 resolving Enemy at T+020, TK-4102 at T+025 and TK-4103 at T+035preferred: Fire on each jet at the first valid solution the system offers, without holding for a better picture
  3. missedSet TK-5206 to unknown at T+076, then set it back to enemy at T+077, and launched at T+090preferred: Leave classification to the referral chain; act on the answer, do not set it locally
  4. missedAttempted a third launch at T+135 with both rockets committed (TK-4101 and TK-4102)preferred: Hold and wait for a fire status to resolve
  5. missedNever engaged TK-4103; TK-4101 missed at T+140 with no capacity to re-engage; from T+153 every attempt returned no rounds remainingpreferred: Keep both launchers continuously employed against confirmed hostiles by earliest valid solution, having cleared the fast closers first

  Debrief

  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.

  Recommended 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.

  Open the debrief as the trainee saw it
• abandonedMass Raid Prioritisation: Jets First, UAVs After, Unknowns ReferredEuro_ADhard9/3/2026, 7:07:21 PM

  Requested

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

  Decisions

  0 answered before the run was abandoned; never evaluated.

• abandonedMass Raid Prioritisation: Jets First, UAVs After, Unknowns ReferredEuro_ADmedium9/3/2026, 7:04:24 PM

  Requested

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

  Decisions

  0 answered before the run was abandoned; never evaluated.

• abandonedMass Raid Prioritisation: Jets First, UAVs After, Unknowns ReferredEuro_ADhard9/3/2026, 12:32:34 PM

  Requested

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

  Decisions

  0 answered before the run was abandoned; never evaluated.

• 5Mass Raid Prioritisation: Jets First, UAVs After, Unknowns ReferredEuro_ADmedium8/30/2026, 12:46:05 PM

  Requested

  “any task will do”

  • What kind of pressure do you want to practise under — deciding which of several inbound threats to engage first, or something else? — yes
  • When you say yes — do you want several threats arriving at once and too few missiles to cover them all? — yes

  Decisions

  1. missedHeld the first launch until T+046, then put both available rounds onto TRK-4102 (T+046 and T+061), leaving TRK-4101 unengaged until T+125preferred: Fire the lead jet at the earliest valid firing solution, then the next jet, keeping the two-in-flight limit spread across separate fast closers
  2. missedAttempted a launch at 73 km (refused, beyond 70 km reach)preferred: Fire when the system permits it — target within system capability and a solution exists
  3. correctHeld while both rockets were committed against jets and UAVs crossed the short ring (refusals at T+069, T+087, T+151)
  4. missedLet UAVs close inside 5 km before committing — four refusals for minimum range at T+176, 180, 184, 188, then a launch at 5 km with Pk 0% at T+195preferred: Mop up by earliest available valid solution inside the shorter rings, keeping both rockets continuously employed
  5. missedLaunched on TRK-7024 at T+203 and T+215; it had been resolved to Friendly at T+130preferred: Withhold fire on anything not standing as Enemy; act on the commander's answer when it arrives
  6. missedBroke off the engagement against TRK-7024 at T+212, wasting one round, then re-launched at T+215preferred: Do not break or switch a committed engagement under time pressure

  Debrief

  The run was decided at T+203. You launched on TRK-7024 and, after breaking that engagement and wasting a round, launched on it again at T+215 and destroyed it at T+290. The commander had answered on that track at T+130 — resolved to Friendly. This is not the near-miss the record warns about, where an Unknown's aggressive profile tempts a self-classification; the answer was already on your display and you fired anyway. Two friendly engagements fail the run outright, whatever the kill count, and they also consumed your last rounds: the refusal at T+218 for no rounds remaining came with four hostile UAVs still inbound. Underneath that, the sequencing failed in the way the record predicts. Both lead jets were inside the 70 km ring well before your first launch at T+046, and when you did commit you put both available rounds onto TRK-4102 while TRK-4101 sat unengaged until T+125. That is the documented error of delaying jet commitment for a better picture, made worse by spending the second launcher on a target already covered. The out-of-range attempt at T+051 cost more seconds. You did kill all three jets — 4102 at T+120, 4103 at T+163, 4101 at T+173 — but two minutes later than the timeline allowed, so the two-in-flight limit was still occupied straight through the UAV wave's arrival inside the short ring. Your holds at T+069, T+087 and T+151 were correct and I am not marking them as inaction; the record treats holding with both rockets committed as right behaviour. The problem is that by the time a launcher freed up, the wave was at the inner limit. Four consecutive refusals for minimum range between T+176 and T+188, then a launch at 5 km with a stated Pk of 0% at T+195, are the arithmetic of a queue that was already broken. Six UAVs reached the defended area. Some UAV leakage is tolerable in a run that took the jets first and kept identification discipline; this run did neither. One thing the record does not speak to is the two friendly overflights, TRK-7038 at T+168 and TRK-7011 at T+191. Those are counted as leakers in your tally and I will not argue with the count, but the doctrine entry only requires that Unknowns be referred and left alone until classified Enemy — it says nothing about preventing friendly tracks transiting the site, so I have no basis to call that a handling error either way.

  Recommended next

  • Treat a resolved classification as binding the moment it appears. TRK-7024 stood as Friendly from T+130; build the habit of re-reading the track's current standing on the display immediately before every launch commit, not the impression you formed of it earlier.
  • Commit the lead jet at the first valid solution inside 70 km — in this run that was well before T+046 — and put the second round on a different fast closer, not a second shot at the same one. Practise runs where the only measure is time-to-first-launch on each jet.
  • Never break a committed engagement to re-aim. The cease at T+212 cost a round and left you at zero by T+218 with four hostiles inbound. Let the fire status resolve, then re-plan.
  • Stop letting UAVs run inside 5 km. You had four minimum-range refusals and a Pk 0% launch; work drills that take the next available valid solution in the medium and short rings rather than waiting for the nearest track to present a stronger one.

  Open the debrief as the trainee saw it
• 12Mass Raid Prioritisation: Jets First, UAVs After, Unknowns ReferredEuro_ADmedium8/29/2026, 7:10:30 PM

  Requested

  “train dealing a lot of targets”

  Decisions

  1. missedEngage the nearest UAV first, then turn to the jetspreferred: Fire the lead jet at the earliest valid firing solution
  2. correctHold and wait for a fire status to resolve
  3. missedEngage the Unknown on the basis of its aggressive behaviourpreferred: Refer to the commander and withhold fire until the track is classified Enemy
  4. missedHold fire until UAVs enter the innermost part of the envelope to maximise kill probabilitypreferred: Mop up the UAVs by earliest available valid solution inside the shorter rings

  Debrief

  The run was decided at T+96. You fired on TRK 4401 while it was still held Unknown, on the strength of its behaviour — descending, altering heading, steadying on the protected area. That is the single worst outcome this scenario scores, and the record is blunt about why: all three Unknowns are friendly, and the threatening-looking profile is the bait. An Unknown is a question, not a permission. Classification is referred to the commander, who answers in about fifteen seconds, and nothing may be fired on unless it is classified Enemy. You took zero seconds on that call. Fifteen seconds of referral cost almost nothing against a properly sequenced queue; being wrong costs the run. The sequencing was already off before that. At T+0 you took the nearest UAV first. That is the classic error the entry names: proximity reads as urgency on the display, but closure rate is what determines who must die first. Jets are prioritised because they consume the timeline, not because they are close. Committing the lead jet at the first valid solution — TTI 74 s, PK 82%, a shot the system was already offering you — is what frees the launchers by the time the UAV wave crosses the short ring. Twenty-four seconds spent arriving at the wrong target compounded it. The hold at T+79 was your one clean decision, and it was clean for the right reasons: both rockets committed, no cease-fire on a developing jet engagement, no panic-switch, no attempt to force a third launch past a hard system limit. But note what the rationale says about that moment — it is not where the run is won. It felt survivable only because the jets happened to resolve; the entry's point is that when this moment feels unwinnable, the fault is upstream in the queue. At T+152, with both launchers free, seven UAVs and about 90 s of window, you held for maximum kill probability at short range. That is the documented error of compressing the remaining timeline and producing leakers at the end of a run. Once the fast closers are gone the UAV wave is a throughput problem: take the next available valid solution and keep both rockets continuously employed.

  Recommended next

  • Rehearse the identification gate as a reflex: any track held Unknown gets referred to the commander immediately and is off limits until it comes back Enemy — regardless of how its flight profile reads. Run the T+96 picture again and make the referral inside five seconds while continuing to work TRK 2203.
  • Drill target selection by closure rate rather than slant range. Replay T+0 and practise committing the lead jet at the first valid solution the console offers, with a target decision time well under ten seconds.
  • Practise the UAV mop-up as a throughput exercise: with both launchers free, take the next valid solution rather than waiting for the nearest track or for a higher PK. Aim to have no launcher idle at any point in the final 90 s.
  • Keep the T+79 behaviour and understand why it worked — write out, in your own words, why holding on two committed rockets is correct and why a UAV crossing the short ring is the expected consequence of a jet-first sequence, not evidence the plan failed.

  Open the debrief as the trainee saw it