Definition
The cabin crew attestation, usually written CCA, is the document that says a person meets the European standard to serve as cabin crew. It is created by Part-CC — Annex V to Commission Regulation (EU) No 1178/2011 — and the rules that govern it sit in Subpart CCA: issue (CC.CCA.100), validity (CC.CCA.105), and suspension and revocation (CC.CCA.110).
The route to it is set out in Subpart TRA. An applicant completes an approved initial training course and passes the examination that closes it (CC.TRA.220), with the content of both prescribed in Appendix 1 to Part-CC. Subpart GEN adds the surrounding conditions: the application itself (CC.GEN.015), a minimum age (CC.GEN.020), the privileges the attestation confers and the conditions attached to them (CC.GEN.025), and the documents and record-keeping the holder must maintain (CC.GEN.030).
What the attestation does not do is qualify the holder to work a particular aircraft or for a particular airline. It is the general credential. Before a cabin crew member can be assigned to duty, the operator must add its own layer under Part-ORO Subpart CC: aircraft type specific training and operator conversion training (ORO.CC.125), differences training where a variant demands it (ORO.CC.130), familiarisation (ORO.CC.135), and then recurrent training (ORO.CC.140) for as long as the person keeps flying, with refresher training (ORO.CC.145) where currency has lapsed. Aircraft type or variant qualifications are also recognised in Part-CC itself at CC.TRA.225.
The practical consequence is that the attestation is portable and the operator layer is not. A cabin crew member who changes airline carries the CCA across, then completes conversion training for the new operator and type qualifications for its fleet. For the receiving operator this makes the joining record a verification exercise — confirming the attestation is valid and not suspended — followed by a training programme of its own, and both halves have to be evidenced separately.
Two further details shape how the credential behaves in practice. Who issues it varies: member states differ in whether the competent authority issues attestations directly or whether approved organisations do so on the authority's behalf, so a crew member's attestation may look different depending on where it was obtained while conferring the same privileges. And the attestation can be suspended or revoked under CC.CCA.110, which means a valid-looking document is not by itself proof of entitlement — an operator's verification has to establish current standing, not merely that a document exists. Both points push in the same direction: the attestation is one input to assignability, not the whole answer.
Why It Matters for Flight Schools
An attestation is the kind of credential that matters most at the moment somebody is rostered. It is held by the individual, but the operator is the party that has to be able to show, per crew member and per flight, that the person assigned was entitled to be there.
That creates a verification burden at joining and a monitoring burden thereafter. At joining, the operator confirms the attestation exists and is valid. Thereafter, the operator's own type qualifications, conversion records and recurrent cycles determine assignability, and those expire on their own schedules. An airline with several types and a few hundred cabin crew is tracking thousands of individually dated items whose only visible symptom of failure is a crew member being rostered who should not have been.
For a training organisation delivering the initial course, the same record is the product: the candidate's attestation depends on the organisation being able to evidence that the approved course was delivered and the examination passed.
How Aviatize Handles This
Aviatize holds the attestation as a document on the crew member's record with its own validity, alongside the operator-side qualifications and checks that determine assignability. Expiry alerts are configurable, so a lapsing item surfaces while there is still time to schedule the training rather than at the roster.
Because the syllabus engine handles non-flight events, the initial course behind the attestation is structured and evidenced the same way any other course is — theory events, practical elements, examination results, all recorded against the candidate and retrievable later.
The Validation Engine's document preconditions are the piece that turns this from filing into control: a required document that is missing or expired can warn or block rather than simply sitting incorrect in a file.