Switch Challenge shows you a row of four symbols, then the same four symbols in a different order underneath, with one or more numbered operators sitting between the two rows. Each operator is a four-digit code — 2 4 1 3 means 'take the 2nd symbol, then the 4th, then the 1st, then the 3rd' — and you must work out which offered operator, or chain of operators applied top to bottom, produces exactly the reordering shown. Rule Application works the other way round: you are handed a short, priority-ordered rule-set first — colour, shape and dot-count combinations that each map to a response key — and then a stream of symbols arrives one at a time, fast, and you press whichever key the first matching rule dictates before the response window closes. One test asks you to infer a hidden operator from its effect; the other asks you to hold explicit rules in memory and fire them off under time pressure.
Why airlines test it
Both are deductive reasoning, but of a stricter kind than the pattern-spotting in the previous lesson: here the rules are given or discoverable, and your job is to apply or infer them without drift. Switch Challenge checks that you can reconstruct a formal transformation from cause and effect alone, accepting only what the evidence logically forces. Rule Application checks something airlines care about just as much — whether a rule-set survives contact with speed and fatigue, since the rules refresh mid-test and a wrong keypress costs a point exactly as a wrong deduction would.
In the cockpit
Cockpit procedures are rule-sets, not instincts. Checklists, FMS logic, and conditional ATC clearances are all if-this-then-that structures that must be applied precisely, in priority order, without hesitation — exactly the skill Rule Application drills. Switch Challenge drills the companion skill: troubleshooting, where you know the input state and the output state and must deduce which system behaviour — which 'operator' — turned one into the other.
For example: on a go-around, the flap load relief system automatically retracts your flaps a stage the moment airspeed passes its limit — the flap position changed, but you never touched the lever. Recognising that this is the load-relief logic firing, and not a fault, is the same deduction Switch Challenge trains: a known input, an observed output, and the system behaviour that explains the transformation — reasoned out rather than reaching for a non-normal checklist you don't need.
How to practise
For Switch Challenge, don't scan the offered operators at random — pick one symbol in the top row, trace where it lands in the bottom row, and check which operator's digit sequence accounts for that single move before testing the rest; on two- or three-operator chains, apply them one stage at a time and hold the intermediate row in mind rather than trying to compress the whole chain in one leap. For Rule Application, re-read the rule-set the instant a block refreshes instead of coasting on the old one, and always check rules in the stated priority order — most errors come from applying a rule that would have matched further down the list, not from misreading the symbol itself.