The rejection email runs to three lines and says nothing about the reason. A few months later, the same operator reposts the position, and the question arises in the same terms for a captain, a cabin manager, or certifying staff: can you reapply, what will the recruiter see of the first attempt, and what in the file has a real chance of having changed? The answer depends less on the operator’s stated policy than on the nature of what was actually measured the first time.
What a selection process produces, and what remains of it
A selection process does not manufacture a verdict, it manufactures a stack of traces. The declarative file first: total hours, types flown, start and end dates, validities. The supporting documents next: licence, medical certificate, language proficiency certificate, work authorisation. Then the outputs of the campaign: aptitude battery results, raw and scaled against a norm, often sub-test by sub-test; structured-interview notes filed by competency; simulator session grading sheet; group-exercise observations; reference checks.
Yet none of this is what will be read first on a second application. What will be read first is a decision code entered in the tracking tool: rejected for prerequisites, rejected on assessment, hold, talent pool. This code is short, it survives reorganisations, and it drives automatic sorting. The details only surface if someone opens the file — that is, if the file passes the sort.
The retention period is not left to chance. An operator that processes applications is a data controller: it must state, in a notice addressed to candidates, the purpose pursued, the length of time it keeps the file, and the fate reserved for test results. This notice is the only document that says, for that particular operator, what “retained” means — and the first one almost nobody reads before reapplying.
The waiting period is not a punishment, it is a property of the test
An aptitude battery targets quantities held to be stable: working memory, processing speed, coordination, spatial reasoning, attention sharing. It measures them through items, and items can be learned. On the second attempt, the candidate knows the instructions, the logic of the timer, and the strategy that pays off. The score rises; the targeted quantity has not moved.
Tests measure things like memory or coordination, but you can get better at the test itself by practicing. The waiting period makes sure your second score is fair by letting the “practice effect” wear off. It’s not a punishment, it’s to keep the test accurate.
A candidate takes an aptitude test for Airline X on January 1st, scoring 70. They retake it on February 1st, scoring 85. The second score is likely inflated by familiarity, not real improvement. Airline X’s policy requires a 6-month wait before retesting, ensuring the next score reflects true ability, not just practice.
Two constant consequences follow: item banks are rotated and the norm is redone; a minimum interval separates two attempts, otherwise the second score is no longer interpretable against the norm on which the threshold was set. The waiting period protects the measurement above all else. Incidentally, it also protects the candidate from a false conclusion: a narrow failure is as much measurement noise as a lack of capacity, and replaying it three weeks later does not resolve the ambiguity, it merely moves it.
The reason drives what comes next, disappointment drives nothing
Campaigns fail for very different kinds of reasons, and the common reflex — wait, then reapply unchanged — only addresses one of them. The useful question is not “when can I reapply”, but “which variable was judged insufficient, and how long does it take for it to change”.
| Reason for rejection | What stays on file | What changes the outcome | Useful window |
|---|---|---|---|
| Prerequisite not met (hours, qualification, language level, right to work) | Declarations and dated documents | Documented acquisition of the missing element | As soon as obtained, independent of any waiting period |
| Position not open, promotion already filled | File in the talent pool, often with no unfavourable assessment | Nothing on your side: the next campaign | At the next posting, with an updated file |
| Non-technical skills insufficiently supported by evidence | Competency grading sheet, evaluator’s wording | New operational exposure that produces tellable situations | The time to live them and then consolidate them |
| Simulator session below standard | Session grading sheet, identified areas of deviation | Retraining aimed at the specific gap, not a repeat of the profile | After the targeted work, whatever the waiting period |
| Aptitude battery below threshold | Raw and scaled scores, date of attempt | Little in the short term; sometimes a different assessment scheme elsewhere | The announced waiting period, and not before |
What you can obtain from your file, and what will be refused
The right of access to personal data is often presented as the key that unlocks the reason for rejection. It unlocks less than that, and it unlocks something else: your answers, your scores, the written assessments concerning you, the existence of an automated decision and the logic underlying it. In observed practice, it does not extend to the items, the scoring keys, or the blank grading sheet: these are not your data, and the test designer will invoke trade secrecy. Nor does it cover a third party’s data: what concerns another candidate in a group exercise, or what would identify an evaluator, may be redacted.
| Item requested | Regime | What this tells you in practice |
|---|---|---|
| Your answers and your scores, raw and scaled | Personal data, disclosable | Your relative standing, never the cause of the gap |
| Written assessments concerning you | Personal data, disclosable with third parties redacted | The wording used: often the only usable information |
| Items, scoring keys, blank grading sheet | Evaluator’s tool, generally not disclosable | Nothing, and asking for it damages the relationship |
| Thresholds and weightings used for the campaign | Internal policy, rarely disclosed | Nothing directly useful for a second application |
| Existence of automated filtering and its logic | Information owed to the candidate | Whether a criterion excluded the file before any human review |
The right reflex. First ask, in writing, for operational feedback from your contact in the recruitment department, without contesting the decision and without citing any legal text: some operators then grant a short debrief, which is worth more than any communication of scores. The formal data-access request comes next, if that feedback stayed empty. The reverse order almost always closes the door to the informal debrief.
The only variable that really moves: the evidence base
A structured interview does not measure your opinion on crew resource management. It collects evidence of past behaviour in situations with certain properties: ambiguity, a time constraint, a decision made on incomplete information, a colleague’s error, a deviation from procedures noticed and dealt with, a disagreement with someone more senior. The evaluator scores what you did, what you said at the time, and what resulted from it. When this part of the campaign ends in rejection, the cause is rarely eloquence: it is a lack of material.
Hence the central, uncomfortable point: replaying the exercise with the same material gives the same result. The same three stories, better told, sound rehearsed — a visibly polished account carries less weight than an imperfect but dated and verifiable one. What changes the game is of a different nature: a different exposure. An instructor or line-training mentor role, a function within the safety management system, a fleet transition, a real diversion flown and debriefed. Then the material exists, and the interview becomes an exercise in recounting rather than reconstructing.
It still has to be recorded. A personal log kept as events unfold — date, context, decision made, outcome, what one would do differently — costs a few minutes per event and forms the only usable stock a year or two later. It must stay consistent with the logbook, which is also its limit: only what actually happened goes into it.
Your two applications will be read side by side
Tracking tools automatically match files belonging to the same individual: name, date of birth, licence number. The recruiter therefore opens, in the same window, what you declared the first time and what you declare today. The comparison is silent and systematic.
The trap. It is almost never a lie that sinks a second application, it is a rounded figure redone from memory: a total of hours that has not progressed plausibly with the declared activity, a reason for leaving rephrased more elegantly, a previously empty period suddenly filled, a qualification dated a month too early. Read alongside the first file, the discrepancy does not read as imprecision but as a flaw of integrity — and integrity is the one assessment dimension that offers no path to recovery. Reconstruct your figures from the logbook and the licence, never from memory.
The same logic governs how to mention the first attempt: a neutral sentence with its date. Staying silent about it when the tool displays it anyway is a misjudgement; arguing against the previous decision amounts to asking the operator to rule against its own evaluator, which it will not do.
The useful timeline does not coincide with the waiting period
The waiting period is an administrative floor. It states from when the file becomes admissible again; it says nothing about the moment when it becomes different. For a missing prerequisite, the two dates often coincide, because the element is obtained and proven. For everything relating to behavioural evidence, they diverge, and it is the second one that matters.
Reapplying within the interval has a real cost: the file goes back through the same measurement chain, produces the same result, and uses up the current campaign, whereas some operators reopen only once per cycle. When a talent pool exists, the economical route is different: you do not reapply, you update the new document as soon as it is obtained, which puts the file back into the flow without triggering a new decision.
Simulator: retraining is not resitting
An assessment session observes a small number of observable things: parameter control in manual flight, visual scan under degraded instrumentation, attention sharing, task prioritisation, automation management and monitoring, quality of the briefing and of calling out deviations. A failure almost always concerns one or two of these axes, not “the simulator” as a whole. Yet the spontaneous preparation consists of resitting the whole profile, which trains the profile and leaves the gap untouched.
The approach that works isolates the axis, attacks it alone, and then recomposes the whole. A raw-data instrument approach with flight director off, if it was parameter control that failed. A visual scan forced onto an unavailable instrument, if it was attention sharing. Repeated rejected-takeoff decisions, if it was reaction time to a failure. This requires knowing the axis, which brings us back to the value of a debrief requested at the right time. The FL330 training programmes, like any other resource, are only worthwhile when aimed at a named gap; bought blind, they simply reproduce profile training.
A counter-intuitive point: some operators deliberately assess on a generic machine, or on an aircraft the candidate does not fly, precisely so as not to reward familiarity with the type. Expensive preparation on the targeted airline’s aircraft may therefore have no effect at all on the grade, while reassuring greatly the person paying for it.
Three checks before reapplying
The first concerns the operator’s candidate information notice: announced retention period, existence of a talent pool and its update mechanism, any mention of a reapplication waiting period, existence of automated sorting. It is a short document, often in the footer of the recruitment portal, and on its own it answers half the questions asked on forums.

The second concerns your own archive: the exact file submitted the first time, with its figures and dates; if it no longer exists, it is reconstructed from verifiable sources, never from memory. The third concerns the test provider, and this is the grey area of the subject: several operators use the same battery supplier, and depending on the contracts, a result may be reused, or held against you, beyond the company where it was obtained. This portability is a matter for the provider and does not always appear in the operator’s notice; the question should therefore be put to both, before burning an attempt at a secondary employer just to “practise”. Practitioner feedback on the FL330 forum gives a fairly accurate picture of the schemes used.
For anyone preparing a qualification in parallel, the sequence follows from this: the verifiable element first, the application afterwards. Applying while announcing a qualification in progress amounts to having an intention assessed, and an intention is coded “rejected for prerequisites” just as surely as an absence.
In the event of any discrepancy between the above and an applicable text, the regulations in force, the operator’s candidate information notice, and its approved documentation prevail under all circumstances: this article describes mechanisms, not the procedure of any specific operator.
Questions fréquentes
How long does an operator retain the file of a failed selection?
The duration is not fixed by a single legal text: it is decided by the operator, justified by the purpose of the processing, and announced in the candidate information notice. In practice, two durations often coexist, a short one for the application file and a longer one for the aptitude battery result, which serves precisely to enforce the waiting period. The operator’s notice is the only authoritative document on this point, and it generally appears on the recruitment portal or in its footer.
Can you obtain your scores and the exact reason for rejection?
You can obtain the personal data concerning you: your answers, your raw and scaled scores, the written assessments concerning you, and information on the existence of automated sorting. You will not obtain the items, the scoring keys, or the blank grading sheet, which are not your data and fall under trade secrecy. The exact reason, in the sense of an explanation, is therefore not guaranteed: the wording of the assessments is often the only truly usable information.
Does the reapplication waiting period also apply when the failure was due to a missing prerequisite?
Most often not, because the waiting period protects the interpretability of a measurement, and a prerequisite is not a measurement: it is a documentary finding. An operator that rejected a file for insufficient hours or a missing qualification generally reopens as soon as the document exists. This still needs to be checked in the notice or with the recruitment department, as some operators apply a single waiting period to all reasons for administrative simplicity.
Does retaking an aptitude battery at another operator erase the first result?
No, and it can even make the situation worse. Several operators use the same test provider, and depending on the contract binding them, a result may be reused or held against you beyond the company where it was obtained. Before sitting a battery “to practise”, ask the question of the provider as much as of the operator: a burnt attempt at a secondary employer can close a campaign at the one you really have in mind.
Should the previous application be mentioned in the new file?
Yes, in one neutral sentence stating the date and the position applied for, without commenting on the decision. The tracking tool links the two files anyway, and the recruiter reads them side by side: staying silent about the first attempt does not hide it, it only creates an impression of concealment. Contesting the previous assessment, on the other hand, is counterproductive, since it would amount to asking the operator to rule against its own evaluator.
Can a simulator session judged unsatisfactory be made up for with training?
Yes, provided the gap is trained rather than the profile. An assessment covers a small number of observable axes — parameter control in manual flight, visual scan under degraded instrumentation, attention sharing, automation management, calling out deviations — and a failure generally targets one or two of them. Resitting the full profile trains the profile and leaves the gap untouched; the axis therefore needs to be obtained at the debrief, worked on in isolation, and then a full session recomposed.

Leave a Reply
You must be logged in to post a comment.