The core challenge of any multi-aircraft scenario is holding several aircraft in your head while you compute, rank, and decide simultaneously. Train that load directly: drill a fixed decision sequence — read, rank, act, update — on paper scenarios until it runs without conscious effort, and set up every math problem in words before you touch numbers. This guide works through both skills with two detailed scenarios, a self-check rubric, and a six-week sequence you can adapt to your own calendar.
Why Multi-Aircraft Scenarios Strain Working Memory
A scenario item asks you to track several aircraft — positions, altitudes, headings, and rates — while new instructions keep arriving. The strain comes less from the content than from rebuilding your mental picture every time attention breaks.
Air traffic practitioners talk about a mental picture: a continuously updated model of who is where, at what altitude, at what speed, and doing what. On paper that model is stable; in a timed scenario it decays within seconds whenever you look away to compute or re-read an instruction. Holding five data streams while doing arithmetic on top of them is exactly what makes the scenario format demanding, and no amount of vocabulary review alone builds that holding capacity.
The remedy is rehearsing method, not memorizing content. If you decide mid-scenario what to check first, which aircraft matters most, and how to record positions, those meta-decisions consume the same working memory you need for the traffic itself. Decide them once, in advance, and drill them until they are automatic. After that, the scenario only supplies data, and your limited attention stays on the aircraft rather than on what you are supposed to be doing next.
Read, Rank, Act, Update: A Decision Sequence to Drill
Use one fixed sequence for every paper scenario: read the situation, rank who needs action first, act with the smallest safe change, then update the picture. Consistency, not speed, is what you rehearse first.
Define each step concretely. Read means noting every aircraft's altitude, heading, and speed before responding to anything. Rank means ordering the traffic by urgency: first, pairs already losing separation; next, aircraft with the least room to maneuver or the least altitude margin; last, everyone else. Ranking is where an untrained approach drifts, because the most recent instruction on the screen is not necessarily the most urgent item in the picture.
Act and Update close the loop. Act with the smallest change that solves the immediate problem, because large corrections create new interactions you must then manage. Update means restating the picture immediately after acting — new altitude, new heading, new rate — so the next decision starts from current reality rather than from your pre-action sketch. Skipping the update is precisely how a correct first decision turns into a wrong second one two minutes later.
Applied Math: Set Up the Problem Before You Compute
Rate, time, and distance problems reward a set-up-first habit: state the endpoint and the units in words before touching numbers. The costly errors are usually wrong endpoints or mixed units, not the arithmetic itself.
Convert every speed to nautical miles per minute by dividing by sixty: 240 knots becomes 4 NM per minute. That single conversion turns closing-rate problems into mental arithmetic instead of long division. Then write the endpoint before computing — 'overtake to within 5 NM,' 'descend 3,000 feet at 1,500 feet per minute' — because the endpoint, not the multiplication, is where a rushed answer goes wrong.
Worked example: aircraft A cruises at 180 knots; aircraft B trails 30 NM behind at 240 knots on the same route. How long until B is within 5 NM? The rushed answer computes a 60-knot closing rate, divides 30 by it, and reports 30 minutes. The better answer states the endpoint first: B must close 25 NM, not 30. At 1 NM per minute, the answer is 25 minutes. The mistake matters because the wrong-endpoint figure is exactly the kind of plausible number a hurried reader grabs.
Conflict Detection and Resolution Are Two Different Skills
Detection means projecting future positions to find where separation will fail; resolution means choosing a change that fixes it without harming anyone else. Drill them separately, then together, in paper scenarios.
For detection practice, extend a mental or pencil line forward from each aircraft's position, heading, and speed, and mark where it crosses another aircraft's line at the same or a crossing altitude. Name the pair and the failure point out loud or in writing: 'one and two, same altitude, converging near the fix.' Naming forces a definite projection instead of a vague unease, and it gives you something concrete to re-check after any change to the picture.
Worked example, using self-defined practice rules — keep two grid squares apart laterally or 1,000 feet apart vertically; these are drill values, not official minima: aircraft 1 eastbound at 5,000 feet, aircraft 2 southeastbound also at 5,000, aircraft 3 level at 6,000 just ahead of 1's track. The rushed fix climbs aircraft 1 to 6,000 — clean separation from 2, immediate conflict with 3. The better decision tests the proposed action against every other aircraft first and climbs 1 to 4,000 instead. It matters because a resolution that creates a second conflict costs more corrective work than the original problem did.
| Skill | What you produce | Drill focus | Typical misstep |
|---|---|---|---|
| Detection | A named pair and the point where separation fails | Projecting tracks and altitudes forward | Vague worry instead of a definite projection |
| Resolution | An action that holds separation for all traffic | Testing the proposed change against every aircraft | Fixing one pair and creating another conflict |
| Update | A current picture after each action | Restating all positions and altitudes post-change | Deciding from a stale pre-action sketch |
A Paper Scenario Drill With a Self-Check Rubric
Run one ten-minute paper scenario daily: sketch three aircraft, speak your sequence aloud, pause mid-scenario for thirty seconds, then rebuild the picture from memory. Score yourself against the rubric below.
Draw a simple grid, place three aircraft with headings, altitudes, and speeds you invent, and define your own separation rule for the drill — for example, one grid square laterally or 500 feet vertically, clearly labeled in your notes as practice values. Introduce one change roughly every minute: a heading change here, a climb there. Your job is to maintain the picture, rank the traffic, and resolve the first conflict using the check-against-everyone habit from the last section.
Expected observations in early sessions: your rebuilt picture misses an altitude more often than any other fact; your first resolution sometimes fixes the named pair but disturbs a bystander aircraft; and after the pause, ranking takes longer than detection did. All three fade within a couple of weeks of daily drills. Track them explicitly, because they are the specific capacities that a multi-aircraft, fast-moving scenario format pressures hardest.
- 5 — Rebuilt picture complete; resolution checked against all aircraft before acting; update stated immediately after each action
- 4 — Picture complete but needed one re-peek; resolution checked; update occasionally late
- 3 — One altitude or heading wrong after the pause; one resolution left unchecked
- 2 — Picture lost two or more facts; ranking restarted mid-scenario
- 1 — Sequence abandoned; worked ad hoc from the most recent item on the page
- Note: rubric scores are learning milestones for your drills, not predictions of any test outcome
An Adaptable Six-Week Preparation Sequence
Sequence the work: two weeks on domain vocabulary and math fluency, two weeks on single- and then multi-aircraft paper scenarios, and a final two weeks on timed mixed sets scored with the rubric.
Weeks one and two: learn the vocabulary of the domain — headings, altitudes, rates, levels, vectors — until reading a scenario card takes a single pass, and drill the knots-to-NM-per-minute conversion plus rate problems daily. Weeks three and four: run the paper scenario drill with one aircraft, then three, keeping untimed accuracy as the only goal. Timing enters only once the sequence is automatic, because premature timing teaches rushing rather than method.
Weeks five and six: alternate timed mixed sets — a math block, a scenario block — with a review pass that logs every error by type: wrong endpoint, unchecked resolution, stale picture. Adapt the plan to your calendar by shrinking or stretching each phase, not by skipping the ordering; the ordering exists because automatic method must precede time pressure. Lean toward an extra scenario week if your rubric scores stall at three for several consecutive sessions.
Readiness Checks to Pass Before Test Day
Treat readiness as demonstrated behavior, not a feeling: rebuild a picture cold, set up ten math problems correctly in a row, and hold a rubric score of four across a full timed mixed session.
Run three checks. First, the cold rebuild: start a scenario, pause for thirty seconds, then redraw every position, altitude, and heading with nothing missed. Second, the setup streak: on ten straight rate problems, write the endpoint and units before computing, with no skipped steps. Third, the timed hold: complete a mixed session while keeping the drill rubric at four or better, including immediately after an intentional mid-scenario interruption.
If any check fails, return to the matching phase of the sequence instead of adding more hours of the same drilling — a failed rebuild points to more single-aircraft tracking, and a failed setup streak points to slower, untimed math work. One administrative note: for current application steps, scheduling, and eligibility, rely on the FAA's careers page at faa.gov/jobs rather than secondhand summaries, since logistics change and this guide stays deliberately out of them.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.