Mock tests and previous papers for AFCAT

Most AFCAT candidates know the syllabus reasonably well by the last month. What separates them is how they perform for two hours on a computer screen: how quickly they move, how well they judge which questions to leave, and how few careless errors they make. Mock tests are where those skills are built.

But a mock by itself teaches very little. The score tells you where you are. The analysis afterwards tells you how to move. This guide covers both, with a worked example.

Three kinds of practice

Start with the official online practice test on the AFCAT website. It shows you the real interface: the question palette, how to mark questions for review, and how the timer is displayed. Do it early, so the interface is never a surprise.

Previous papers

Previous papers show the level of maths and reasoning, the kind of English passages and the mix of GA topics the Air Force sets. Solve the recent ones under timed conditions, like mocks.

Be careful about sources. Many papers in circulation are memory-based reconstructions put together after the exam, and their details, and sometimes their answers, can be wrong. Use them for the level and the types of questions, and check any answer that looks doubtful.

Simulate the exam

• Two hours, no breaks, phone in another room.
• The same time of day as your exam slot, so your mind is sharp at that hour.
• On a computer screen, not on paper. Reading figures and passages on a screen is slower until you are used to it.
• Rough paper and a pen only; no calculator.
• The real marking scheme: +3, −1, 0.

How to analyse a mock: four steps

Set aside at least as much time for analysis as for the mock itself, ideally on the same day.

1. Score. Record total score, correct, wrong and unattempted, overall and for each section.
2. Wrong answers. Classify every one as a concept gap, a calculation slip, a misread question or a bad guess.
3. Unattempted questions. Solve each one untimed. Could you have done it in the paper? If yes, was the problem time, nerves or order?
4. Time. Note how long each section took. Find the two or three questions that took the longest and ask whether they were worth it.

Then write down one change for the next mock. Just one, so you can tell if it worked.

A worked example

Suppose an aspirant takes a mock and gets these results (made-up figures):

Score: 64 × 3 = 192, and 192 − 18 = 174. Accuracy is 64 ÷ 82 = 78%.

Classifying the 18 wrong answers: 7 careless (misread or calculation slip), 5 concept gaps, 6 bad guesses.

What that is worth:

• If the 7 careless errors had been right, the score would rise by 7 × 4 = 28, to 202.
• If the 6 bad guesses had been left blank, the score would rise by 6 × 1 = 6.
• The 5 concept gaps point to topics to revise this week.

The one change: slow down slightly in Numerical Ability and re-read the question before selecting an option. Numerical took 40 minutes for only 14 attempts, so the problem is not speed alone. The aspirant should check the error log for which chapters caused the slips.

Keep an error log

A notebook or spreadsheet with one row per mistake. Review it every Sunday and again in the last week.

After a few weeks, patterns appear: the same chapter, the same trap, the same time of the paper. Those patterns are your fastest source of marks.

How many mocks?

The quality of analysis matters more than the number. Fifteen to twenty full mocks, each carefully analysed, is a reasonable target over the last six to eight weeks, alongside sectional tests. Taking a mock every day without analysis tends to repeat the same mistakes at greater speed.

If time is short, take fewer mocks and analyse them properly rather than taking more and skimming.

Tracking progress

A simple table shows whether your changes are working. Again, these are made-up figures:

Notice that attempts rose by only 6 while the score rose by 58. Almost all the gain came from accuracy.

When scores plateau

Most candidates hit a plateau at some point. Common causes and fixes:

• Same wrong answers in the same topics: go back to the concept for those two or three topics; more mocks will not fix a concept gap.
• Running out of time: check the time table. Usually one section is taking ten minutes too long.
• Scores swinging widely: often guessing. Check your guess accuracy by type, as described in our guide to negative marking.
• Tired in the second hour: take mocks at exam time and keep your sleep regular.

Your mock routine checklist

• Take the official practice test on the AFCAT website this week.
• Book fixed mock slots in your calendar, the same time each week.
• Set up the error log before your next mock.
• After every mock, do the four-step analysis and write one change.
• Review the error log every Sunday and again in your last month.