The mental arithmetic test is selection at its most honest: a problem, a timer, a keypad, and nowhere to hide. No options to eliminate, no partial credit for method, just the exact number before the clock empties. This guide covers the format, the precedence rule that catches careless candidates, and the head-math techniques that separate trained speed from native talent.
What is the Mental Arithmetic Test?
The test measures exact computation under time pressure, and aviation insists on it for good reason. Fuel checks, crossing restrictions, descent gradients and separation math all happen verbally, in the head, while flying or controlling continues. The abbreviation KRN traces back to the German Kopfrechnen, head calculation, a fixture of DLR style screening for decades.
Two features distinguish it from school arithmetic. First, entry is typed, not chosen: an answer of 67 when the truth is 68 scores exactly zero, so estimation habits die here. Second, chained problems enforce operator precedence: multiplication and division resolve before addition and subtraction. In a problem like 6 x 7 + 13, the product comes first, then the sum, giving 55. Candidates who read left to right produce 120 and lose the point. Its numerical sibling, the number series test, probes pattern finding; this one probes raw, precise throughput.

Which Exams Include the Mental Arithmetic Test?
Timed head math appears in nearly every aviation battery. Candidates commonly report this test type in:
- DLR screenings, where the Kopfrechnen stage gave the format its name
- COMPASS and Advanced COMPASS by EPST, in the math sections
- PACE, in airline and cadet programme assessments
- ADAPT, within its numerical tasks
- Aon / cut-e batteries, in applied numeracy items
- FEAST and related ATC selection, where mental math supports several stages
Providers revise their content without notice and publish no official syllabus, so treat this as candidate-reported guidance.
How the Test Works: Format and Rules
The mechanics are minimal by design:
- One arithmetic problem appears: addition, subtraction, multiplication, or a chain mixing them.
- A per-question timer bar drains; when it empties, the question counts as a miss.
- You type the exact answer on a keypad, with a minus toggle for negatives and a backspace to fix a digit, then submit.
- Standard precedence applies on chains: resolve products before sums and differences.
Take 17 x 4. Split it as 17 x 2 x 2: doubling twice gives 34, then 68, typed and submitted with seconds to spare. This is exactly how it looks in the test:
Levels trade time against problem complexity:
- Level 1: 10 problems, 18 seconds each, single operations
- Level 2: 20 seconds, harder operands
- Level 3: 25 seconds, chains appear
- Level 4: 28 seconds, longer chains
- Level 5: 30 seconds, full mixed chains
Note the inversion: time per question grows because the problems grow faster. Thirty seconds for a Level 5 chain is tighter than eighteen for a Level 1 sum.
Exact or nothing. The keypad does not grade effort.
Scoring: What a Good Result Looks Like
One point per exact answer, response time logged. Assessors weigh the error pattern: timeouts suggest slow technique, which trains out quickly, while wrong submitted answers suggest broken checking habits, which is the more serious signal. A strong result submits ninety percent exact with steady times, and never bleeds points on precedence, the single most preventable error class in the format.
How to Prepare: Strategies That Actually Work
- Scan for products first on every chain. Before computing anything, mark the multiplications, resolve them, then sweep the additions left to right. Make precedence a visual habit, not a remembered rule.
- Build a decomposition toolkit. Multiply by 4 as double-double, by 5 as times ten halved, by 9 as times ten minus one, by 11 as times ten plus one. Every two digit multiplication should have a route that avoids grinding.
- Add left to right. For 384 + 267, do 500, then 140, then 11: 651. Left to right matches how numbers are spoken and halves the carrying load.
- Say intermediate results once. On chains, voice the resolved product in your head before continuing; it anchors the value against the timer's pressure.
- Estimate as a safety net, then compute exactly. A one-second estimate of 17 x 4 as near 70 will catch a typo like 86 before submission.
- Train daily in short bursts. Head math compounds fast: ten minutes a day rebuilds school-era speed within weeks. Pair sessions with the coordinate system test, whose heading arithmetic runs on the same muscle.
Common Mistakes to Avoid
- Computing chains left to right, the precedence trap in its purest form.
- Grinding multiplications digit by digit instead of decomposing.
- Submitting without the one-second sanity glance at magnitude.
- Freezing on a hard problem and donating the timer; give your best exact attempt and move on.
Practice This Skill
Head math is the most trainable score in the entire battery, and it decays without reps. Train with the Mental Arithmetic module, which reproduces the timer bar, the keypad entry and the precedence chains exactly as described here. Level 1 is free, and the guided tutorial walks you through the format before your first attempt.