AFCAT 02/2012 written exam was conducted by India air-force on 26 Aug 2012, the standard of AFCAT written test has improved considerably since last 3 years. But still there is a question, whether or not AFCAT has fixed cut off marks.
Also Read
Also Check: AFCAT New Results 2012
AFCAT started in 2011 for the recruitment of officers in Indian air force for flying , technical and GDOC. Since then there is 30%-40% increment in the number of candidates applying AFCAT every year. Also the difficulty level and quality of questions have changed, it is clear that IAF making AFCAT more and more secure and top level like CDSE and NDA. This year IAF has allowed the online and offline submission for AFCAT application submission, making the whole process convenient for the aspirants.
AFCAT written test is divided into four basic sections viz. general awareness , verbal ability, numerical ability and reasoning and military aptitude. Both sections are getting more and more difficult with time and you may need good practice for all sections if you are an average student.
In AFCAT 02/2012 the level of questions were better and higher than last AFCAT 01/2012 held in Feb 2012. Surprisingly the level of reasoning and military aptitude was difficult this time, as usual verbal ability, numerical ability was tough and it wouldn’t be wrong if we say it was almost like CDSE level or more than that.
If we consider the difficulty level of questions this time, in 02/2012 AFCAT , cut off marks might fall near 140, or 45-55 correct questions might be a safer side for you, hope you have avoided the more of guessing in questions and kept the negative marking in mind. But again its all depends on the IAF, how much intake they want from this AFCAT, though they have also announced the additional list in last AFCAT 01/2012 results lately and considered few more candidates those who were failed earlier.
Lets hope for the best, do write your number of questions you have done in AFCAT 02/2012 and how many correct answers your are expecting this time.
Also Check:
