A captain asks why his aircraft, which rolled off the production line three years ago, lacks a protection that the same manufacturer fits as standard on a smaller, older model. The answer is neither commercial nor technical: it comes down to a date, the filing date of the type certificate application, which froze the applicable body of requirements that day — sometimes two decades earlier. The freeze, and the few mechanisms that reopen it, explain much of what surprises people in service.
What a certification basis really covers
The term is commonly taken to mean, roughly, “the rules under which the aircraft was designed.” Its administrative reality is narrower: a dated list, negotiated point by point, that brings together four families of elements.
- The applicable airworthiness code — large aeroplanes, small aeroplanes, rotorcraft, engines or propellers — taken at a specific amendment level. Not today’s code: the code as it stood on a given day.
- The special conditions, added when a design feature is novel or unusual and the code, written before it existed, has nothing useful to say about it.
- The equivalent levels of safety and accepted deviations: the points where the applicant did not meet the letter of a requirement but demonstrated by other means that it achieved its intent.
- The environmental protection requirements, noise and emissions, which follow their own timetable of applicability.
To these are added the operational suitability data, brought within the scope of the type certificate: the master minimum equipment list, flight crew training data, simulator qualification data, and data intended for cabin crew and certifying maintenance staff. These are handled constantly without always being recognised as revised under design procedures, not operational ones.
During the investigation, every point discussed is carried on a certification review item until it is resolved: a special condition to be drafted, a requirement to be interpreted, an unusual means of compliance to be accepted. The outcome is condensed into the type certificate data sheet, a public document that few people open once the aircraft is in service.
Why the application date freezes the body of requirements
The principle can be stated in one sentence: the applicable specifications are those in force on the date of the application. The code may be amended several times during development; the target no longer moves.
This is not a favour granted to industry, it is a constraint of demonstration. Compliance is not written, it is established: calculation, a structural test taken to destruction, a flight test campaign, a systems safety analysis. A requirement that changes along the way does not cost a line of text — it costs an already-destroyed test article, an electrical architecture to be redone, months of flying to be repeated. Without a fixed point, no long programme could converge, and the authority would lose the stable reference that lets it process a file spread over years.
The freeze is not eternal, though, and that is the point people forget. An application has a limited period of validity, on the order of a few years — longer for large aeroplanes and heavy rotorcraft than for other products, depending on the applicable text. Once that period elapses without issuance, the applicant has two options. Refile, with today’s date and therefore today’s amendments. Or request an extension of the application by proposing a new effective date, which cannot be early enough to empty the time limit of its purpose. Either way the clock is reset and the basis climbs one notch or several: a programme delay is also paid for in requirements.
The certification basis is frozen at the time of application to give manufacturers a stable set of rules to work with. Changing requirements mid-development would mean redoing expensive tests and redesigns, which would make aircraft development impossible. If the application expires, the manufacturer must either restart with new rules or extend the application, which moves the basis to a newer set of requirements.
An Airbus A350 first applied for certification in 2011. If the programme had faced delays and the application expired in 2015, the manufacturer would have had to either refile with 2015 rules (requiring additional compliance work) or extend the application with a new effective date, moving the basis to a later amendment level.
The date you read is not the one that counts. A data sheet carries several dates — initial issuance, successive revisions, sometimes a purely formal reissue — and none of them is the one that froze the basis. Only the application date, stated in the section devoted to the certification basis, fixes the amendment level; a data sheet revised last month can describe a code that was settled two decades earlier. The corollary holds for the programme itself: a development slippage is not merely an industrial cost, it can shift part of the file onto a more recent amendment, with additional tests and design choices to be redone.
What the freeze does not protect against
The frozen basis does not shield against everything, nor forever. Four entries remain open, and three of them open even before the certificate is issued.
Special conditions. When a design feature is novel or unusual, when the intended use is out of the ordinary, or when experience gained on comparable types shows the code does not reach the intended level, the authority prescribes requirements that did not exist at filing. This is the relief valve that keeps the freeze from enshrining a known gap.
Interpretation. The text is frozen; the way of demonstrating it is not. Acceptable means of compliance, guidance material and review practice evolve. A literally identical requirement may today be demonstrated through an analysis the authority would not have accepted at the time of filing, and may elsewhere demand a level of proof that was not then required.
Environmental requirements. Noise and emissions fall under the annex to the Chicago Convention devoted to environmental protection, and their applicability rules are their own: depending on the topic, they attach to the application, the issuance, or the manufacture of the individual aircraft. An operator can therefore see the same type produced under two different noise chapters, with the knock-on effects on charges and access to certain airports.
Operational suitability data. These live on: a revision of the master minimum equipment list or of the training data does not reopen the airworthiness code, but it changes what the operator must do, often within short deadlines.
| Family of requirements | Usual reference date | What moves it |
|---|---|---|
| Airworthiness code | Date of the type certificate application | Refiling, extension with a new effective date, significant change |
| Special conditions and interpretations | None: settled during the review | New design feature, unusual use, experience feedback from comparable types |
| Environmental protection | Depending on the topic: application, issuance, or manufacture of the individual aircraft | Adoption of a new noise or emissions chapter |
| Additional specifications for operations | Deadline set by the text, independent of the age of the type | Decision to make a requirement retroactive |
Modifying a type: the rule for the changed product
The second door is wider, and it is the one people cross without realising it when flying a recent variant of an old type. Every modification made to a type design is classified, and the class determines the basis that is retained.

The first sort is on the nature of the change: is it substantial? If the design or the operating principles change to the point that the original demonstration is no longer relevant, one does not amend a certificate, one applies for a new one. The basis is then entirely today’s.
Failing that, is the change significant? The question concerns the general configuration, the construction principles and the assumptions that underpinned compliance. If the answer is yes, the areas, systems, parts and appliances affected are reassessed against the specifications in force on the date of the modification application; the rest of the aircraft keeps its original basis. Two escape routes are commonly used: when the authority judges that compliance with the latest amendment would not bring a significant safety improvement, or would be impractical, an earlier amendment may be retained. Never, however, less demanding than the existing basis: a product’s basis never moves downward.
If the change is not significant, the existing basis applies as it stands. This is the regime for the vast majority of modifications, including many that are classified as major — major and significant are not synonyms, and confusing them skews the reading of an entire file.
| Class of change | What characterises it | Basis retained | Administrative route |
|---|---|---|---|
| Substantial | Design or operating principles modified to the point of making the original demonstration moot | Today’s specifications, on the whole product | New type certificate |
| Significant | General configuration, construction principles or compliance assumptions affected | Specifications in force on the date of the modification application, for the affected areas only; an earlier amendment admitted if the upgrade brings nothing significant or proves impractical | Amendment of the certificate or supplemental type certificate |
| Not significant | Everything else, including many modifications classified as major | Existing basis, unchanged | Amendment of the certificate or supplemental type certificate |
The cumulative effect is what throws people off: an aircraft delivered this year on an old type carries, depending on the area, requirements from three different eras. Primary structure judged against an original amendment, modernised controls against a recent amendment, cabin fit-out against a third. None of this is anomalous — it is the mechanism working normally.
Reopening a basis without touching the certificate
What remains is the case that matters most in service: a new requirement judged necessary for a fleet already certified and already in operation. The lawmaker does not reopen the certification basis; it acts alongside it, through three distinct routes best not confused when writing a report or investigating a discrepancy.
The airworthiness directive addresses an unsafe condition identified on a product in service. It imposes an inspection, a limitation or a modification, with a compliance deadline. It does not modify the basis: it corrects the gap between what the design was meant to do and what it actually does.
The additional airworthiness specifications applicable to aircraft used in operations form the deliberately retroactive mechanism. This is the route through which the large fleet upgrade campaigns have passed: fuel tank safety, integrity and maintenance of electrical interconnection wiring, damage tolerance of ageing structures. These requirements target types certified well before them, and the operator must demonstrate compliance, at its own expense and on an imposed schedule.
Operating rules, finally, impose equipment and capabilities independently of the basis: ground proximity warning, airborne collision avoidance system, recorders, communication, surveillance and navigation means required in certain airspaces. The requirement arises from operations, the demonstration falls back on the design, hence the supplemental type certificates for compliance upgrades that arrive in waves on older fleets.
Reading the basis where it is written
All of this can be checked in a few minutes. The type certificate data sheet states the code retained and its amendment, lists the special conditions, the equivalent levels of safety and the deviations, specifies the environmental requirements and refers to the operational suitability data. For a safety manager investigating an event, a certifying staff member building a file, or an instructor who must explain a difference between variants, this is the primary source, and it is public.
The right reflex. Before any discussion of compliance, open the data sheet for the type concerned and read its basis: code, amendment, special conditions, equivalent levels of safety. Then check whether the area in question was affected by a significant change or by an embedded supplemental type certificate. A few minutes of reading avoids weeks of misdirected debate.
The most common trap. Confusing the age of the individual aircraft with the age of the basis. An aircraft that rolled off the line this year on an old type remains judged, in the areas not affected, against old requirements: it is perfectly compliant, and a report concluding non-compliance has the wrong frame of reference. The symmetrical confusion is just as costly: believing that a cockpit modernisation brings the aircraft up to the latest standard, when it only shifts the basis on the affected systems.
What is left to check, and what remains debated
Three checks are usefully made on one’s own fleet. The list of embedded supplemental type certificates, aircraft by aircraft, since two registrations from the same fleet do not always carry the same ones. The status of the operational suitability data and the difference lists, which govern training and the minimum equipment list and change more often than the basis. Finally, when a type has been validated by an authority other than the one that certified it, the conditions added during that validation, which explain equipment differences between two identical aircraft registered on either side.
The grey area, for its part, never closes. The boundary between significant and not significant remains a reasoned judgement, not a calculation: it is argued, and two neighbouring cases can receive different answers. Resorting to retroactivity through additional specifications is also a trade-off, between the cost imposed on operators and the expected benefit for a fleet that will fly for a long time yet. For anyone preparing a type rating, the stakes are very concrete: much of the difference in behaviour, alerting and procedure between two variants of the same family reads in the basis, not in the operating manual. That is what is worth digging into while preparing a type rating, and one of the topics that comes up most often in exchanges between crews who have moved from one version to another.
On any point of detail, the applicable regulatory text, the type certificate data sheet of the aircraft concerned and the operator’s approved documentation prevail over this article, whose sole purpose is to lay out the mechanism.
Questions fréquentes
How do I find out which amendment my type was certified against?
The type certificate data sheet, published by the certifying authority, opens with the certification basis: the applicable airworthiness code, the amendment level retained, special conditions, equivalent levels of safety and deviations. It also states the environmental requirements and refers to the operational suitability data. It is a public document, and the only authoritative source on this point.
Does a recent modernisation bring the aircraft up to the latest regulatory standard?
No, unless the change was classified as substantial, in which case a new type certificate is issued. A significant change shifts the basis only for the areas, systems, parts and appliances affected, and a change that is not significant leaves it untouched. A modernised aircraft therefore carries requirements from several eras at once, depending on the area.
Does an airworthiness directive modify the certification basis?
No. An airworthiness directive addresses an unsafe condition found on a product in service and imposes an inspection, a limitation or a modification with a compliance deadline. It corrects a gap between the design’s expected behaviour and its actual behaviour. The certification basis remains the one stated on the type’s data sheet.
Why don't two aircraft of the same type carry the same equipment?
Three causes combine. Embedded supplemental type certificates differ from one aircraft to another. The requirements imposed by operating rules depend on the operator’s state and the airspaces frequented. Finally, when a type is validated by an authority other than the one that certified it, that authority can add its own conditions.
Can a programme delay make the applicable requirements stricter?
Yes, and this effect is routinely underestimated. A type certificate application has a limited period of validity. If the certificate is not issued within that period, the applicant must refile or obtain an extension by proposing a new effective date for the application. Either way, the basis is reset against more recent amendments.
Does the certification basis explain training differences between variants?
Largely, yes. Operational suitability data fall within the scope of the type certificate and feed the flight crew training data, the simulator qualification data and the master minimum equipment list. When two variants of the same family require differences training, the root cause is most often found in their respective bases.

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