ASTB-E study materials
ASTB-E study resources

Multi-Task Prioritization Under a Hard-Deadline Battery

ASTB-E · Put your knowledge to work in context.

All case studies

Multi-Task Prioritization Under a Hard-Deadline Battery

You are 12 minutes into a multi-task simulator sortie with three concurrent tasks. (1) Target tracking: you hold a crosshair on a target that is drifting right at 4 m/s; an error above 30 m held for more than 3 s ends the run. (2) Dichotic listening: your call sign 'Viper 2' may arrive in the left ear followed by a heading you must read back; numbers arriving in the right ear are distractors. (3) Fuel panel: a caution must be reset within 4 s of appearing or the engine model degrades for 10 s, which is uncomfortable but recoverable. At t = 0 the tracking error is 10 m and growing at 4 m/s. At t = 4 s the fuel caution appears. At t = 5 s 'Viper 2, zero-nine-zero' arrives in the left ear. At t = 6 s the tracking error crosses 30 m.

1. Give your action sequence from t = 4 s to t = 9 s, and state the priority rule you are using rather than an ad hoc order.

Read the worked answer

Priority rule (not urgency alone): order by consequence × irreversibility, then by deadline.

  1. Tracking failure ends the run - irreversible, highest consequence.
  2. Missing your own call sign is a discrete, scored communication failure and, in the real aircraft, a safety-of-flight item. Delayed by a second is acceptable; dropped is not.
  3. Fuel panel degrade is 10 s and recoverable - lowest consequence, despite having the loudest deadline.

Sequence:

  • t = 4 s: error is 10 + 4(4) = 26 m - still under 30. Take a short joystick correction (~0.5 s) to flatten the drift, then immediately reset the fuel panel (1–2 s). Doing the panel now, not at t = 7.9, is deliberate: it burns the deadline before the radio call arrives.
  • t = 5 s: acknowledge and read back "Viper 2, zero-nine-zero" (~2 s). Hold the stick steady during the readback; sub-threshold jitter is cheaper than a garbled readback.
  • t = 6 s: error crosses 30 m. Apply a larger corrective input and hold it. The 3 s clock starts now, so the error must be back under 30 by t = 9 s - roughly a 10 m/s correction rate, well inside the target's 4 m/s drift.
  • t = 7–9 s: re-center and re-trim, then resume the normal scan. Never let the panel reset push you past t = 8; never let the readback push you past t = 9 on the tracking clock.

What not to do: do not reset the panel at t = 7.9 simply because it is the loudest task, and do not answer the radio before the panel - that ordering stacks two deadlines into the same two seconds.

2. If two tasks collide and you must drop one, which do you drop and which do you protect? Justify with the consequence of each failure, not the noise of each cue.

Read the worked answer

Protect, in order:

  1. Tracking - a single 3 s excursion ends the run. There is no recovery path, so no other task can be allowed to buy time from it.
  2. Own call sign - a missed or wrong readback is an unrecoverable discrete error in the record and, in the aircraft, a real breakdown of crew coordination. Delaying it by 1–2 s is fine; skipping it is not.

Drop:

  • The fuel-panel reset, if and only if it truly collides. The penalty is a 10 s degraded engine model - annoying, recoverable, and self-clearing. Absorbing that is far cheaper than either alternative.

The general principle: urgency (how loud, how soon) is not priority. A 4 s deadline with a recoverable outcome loses to a 3 s deadline with an unrecoverable one. Watchstanders who sort by loudness fail the battery; watchstanders who sort by what cannot be undone pass it.

Caveat that changes the answer: if the panel reset were a real fuel imbalance with a hard limit rather than a 10 s model degrade, the consequence ordering flips and the panel moves to the top. The rule is consequence-based; the ranking only holds while the numbers hold.

3. At t = 8 s the radio issues a control instruction that, if complied with immediately, will drive the tracking error well past 30 m. How do you resolve the conflict, and what do you never do?

Read the worked answer

Resolution order - aviate, navigate, communicate, in that sense:

  1. Comply with the control instruction. In live flight, an ATC clearance is a directive with separation consequences; the simulator score is not. Ignoring or delaying a clearance to protect a tracking number is the exact inversion of airmanship the battery is looking for.
  2. Absorb the tracking penalty within the limit. A single excursion past 30 m is survivable if corrected inside 3 s. Comply, then apply a large corrective input and expect the error to peak and recover - do not fight the instruction with the stick.
  3. If the maneuver genuinely makes the tracking task unachievable, say so on the radio and request relief - "unable at this time, standby" - rather than silently non-complying. The correct failure mode is a declared deviation, not an undeclared one.

Never do:

  • Never let an automated score override an external directive. The battery is measuring whether your priorities survive pressure, and the answer it wants is the one that keeps the aircraft safe.
  • Never drop the readback as a way of buying tracking time - that is the same error in a quieter form.
  • Never make two corrections at once (stick plus panel plus radio). Sequence them; simultaneous inputs are how a small tracking error becomes a lost target and a missed call.