Powered-lift certification: FAA, EASA and UK evidence review
Organise powered-lift certification research by authority, document status, agreed basis and evidence—without assuming automatic equivalence.
About this article: This information illustrates the potential benefits of Aviation.Bot’s upcoming regulatory library and desktop/web document-review features. It is not compliance guidance, legal advice or a basis for a regulatory, certification or operational decision. Examples demonstrate the workflow; verify applicable official sources and use qualified professional judgement for actual work.
Workflow at a glance
Original workflow illustration. Candidate findings remain subject to qualified human review; the diagram does not establish an approval or compliance decision.
A shared aircraft concept does not create a shared approval record
A powered-lift programme may consider several markets while developing one aircraft. Its engineers still need to distinguish each authority’s certification framework, the project’s agreed basis, the means of showing compliance and the evidence produced for that purpose. A search result describing “global eVTOL certification” can conceal these separate objects.
The useful research question is narrower: which source supports this proposed requirement or evidence activity, in which jurisdiction, at which revision, and with what status? An answer becomes much more valuable when the team can attach it to an actual programme record rather than a general comparison of regulators.
This article proposes a research register. It does not establish a certification basis, prescribe a test programme or assess any manufacturer’s likelihood of certification.
Separate aircraft certification from pilot and operating rules
The FAA’s active AC 21.17-4, issued 18 July 2025, addresses powered-lift type, production and airworthiness certification and describes an acceptable means for certain aircraft under 14 CFR 21.17(b). That document belongs in an aircraft-certification research set.
The FAA’s Part 194 FAQ concerns a different layer: pilot and instructor certification and operating rules. A programme may need both layers, but a new pilot-training rule should not be mistaken for proof that a particular aircraft design has obtained type certification.
For EASA, the small-category VCA publication consolidates SC-VTOL and means-of-compliance material. The VTOL publication page separately records publications and consultation activity. A consultation item and final material must retain different status labels in the register.
Keep the UK programme context dated
The UK CAA’s 6 November 2025 VTOL policy article described a consultation spanning airworthiness, pilots, landing sites and operations. It identified Vertical Aerospace’s VX4 test activity at that time. The article is a dated authority statement, not evidence of the company’s present certification status or a guarantee about future commercial service.
The UK 21.B.80 provision explains the CAA’s establishment of a type-certification basis. For a specific programme, public framework research must be connected to the project’s actual authority communications and controlled basis. Similar public material does not establish automatic acceptance of another authority’s findings.
A synthetic evidence row for an electric-propulsion change
Take a fictional supplier delivering an updated electric-propulsion subsystem to a manufacturer considering UK, EU and US markets. No technical requirement or certification finding is assumed. The supplier needs to identify which existing evidence records the change may affect.
One proposed register row could contain:
- Change: subsystem revision and affected aircraft configuration, with an internal change identifier.
- Authority context: FAA, EASA or UK CAA; project and application reference; agreed-basis document reference where available.
- Source candidate: exact document, paragraph, issue, publication status and official URL.
- Compliance activity: proposed analysis or test reference, its purpose and the programme person responsible for determining suitability.
- Evidence relationship: existing report, configuration it covers, assumptions that may have changed, and reuse questions requiring review.
- Authority disposition: proposed, submitted, queried, accepted or superseded, backed by the corresponding controlled communication.
The register should have separate rows where jurisdictions differ. “Equivalent” should require an explicit basis and review, not merely similar wording or a common technical standard. A linked report can appear in several rows without implying that every authority has accepted it.
Track proposals without promoting them into requirements
A new consultation, draft advisory circular or proposed means of compliance may be relevant to programme planning. Store it in a watchlist with its status, closing date where relevant, topic and affected internal review. Keep it distinct from the agreed certification basis and from adopted material.
When final material appears, compare the actual text and revision history. Record whether the team proposes a programme change, needs authority clarification or determines no action for the present basis. A publication date alone does not decide that outcome. This is where a disciplined review record can prevent a new search result from becoming an undocumented engineering instruction.
Ask an assistant for evidence, then review the mapping
A useful AI prompt is: “Find the official sources for this certification topic, label their status and revisions, distinguish design certification from operational rules, and identify questions that require project-specific authority evidence.” Require direct citations and an explicit list of missing programme facts.
Aviation.Bot’s upcoming regulatory library and desktop/web features are designed to support powered-lift certification research like this. The starting libraries cover EASA, FAA, UK CAA, CAAC and Dutch IL&T across multiple document categories. The workflow lets a reviewer search the selected authority material beside certification plans, test reports and open-issue registers, then map candidate evidence to each authority’s recorded basis. Desktop users work with selected local folders and files; browser users upload selected documents to their workspace. Available sources and editions remain visible parts of the review rather than an assumed complete collection.
The practical difference from a typical ChatGPT upload session is the aviation-specific source collection and repeatable document-review workflow: selected regulatory material sits alongside the organisation’s manuals, procedures and evidence, with references the reviewer can reopen. ChatGPT also supports file analysis; Aviation.Bot’s differentiation is how the source set and review task are organised, rather than a claim that general assistants cannot read documents.
Complex tables and forms deserve the same inspection as prose. The workflow is being developed to retain table relationships, headings, footnotes and form context, and to let the reviewer check the original page when extraction is uncertain. Reliable review depends on seeing that structure—not merely receiving a confident summary. Better accuracy, complete table fidelity and time savings require task-specific validation; they are not established by having a curated database.
Start with one changed subsystem and one register. The result should make the next technical review easier to follow while preserving who decides the certification consequence.
Prepared with AI assistance and editorial checks against linked official sources. Illustrative examples do not represent authority or independent expert approval.