Difference between revisions of "Certification FrameWork VTOL"
Wiki.admin (talk | contribs) |
Wiki.admin (talk | contribs) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= VTOL Certification Framework = | = VTOL Certification Framework = | ||
| − | '''Mini-Bee / | + | '''Mini-Bee / RED VTOL — EASA Certification Framework''' |
| − | + | <div style="border:1px solid #d0d7de; border-radius:14px; padding:22px; background:#f8fafc; margin-bottom:25px;"> | |
| − | + | <div style="font-size:150%; font-weight:bold; color:#1f4e79; margin-bottom:8px;"> | |
| − | + | Mini-Bee / RED VTOL — Certification Pathway | |
| + | </div> | ||
| − | The objective is to | + | <div style="font-size:105%; line-height:1.6;"> |
| + | This page presents the high-level EASA certification framework studied for the Mini-Bee / RED VTOL concept. | ||
| + | The objective is to understand how a 2PAX hybrid VTOL multicopter, designed as an ultra-light air ambulance concept, can be positioned inside the European aviation certification environment. | ||
| + | </div> | ||
| − | + | <br /> | |
| − | + | [[File:MiniBee_VTOL_Certification_Framework_Hero.png|center|900px|Mini-Bee / RED VTOL certification framework hero visual]] | |
| − | {| class="wikitable" | + | <div style="text-align:center; font-size:90%; color:#555; margin-top:8px;"> |
| + | '''Figure 1.''' Mini-Bee / RED VTOL certification framework overview. | ||
| + | </div> | ||
| + | |||
| + | </div> | ||
| + | |||
| + | __TOC__ | ||
| + | |||
| + | == Main presentation == | ||
| + | |||
| + | <div style="border:2px solid #1f4e79; border-radius:12px; padding:18px; background:#eef6ff; margin-bottom:25px;"> | ||
| + | |||
| + | <div style="font-size:125%; font-weight:bold; color:#1f4e79;"> | ||
| + | Download the full PowerPoint presentation | ||
| + | </div> | ||
| + | |||
| + | <br /> | ||
| + | |||
| + | '''Red VTOL TRL4 — 2PAX VTOL hybrid multicopter — Ultra light air ambulance — EASA Certification Framework''' | ||
| + | |||
| + | <br /><br /> | ||
| + | |||
| + | [[File:20260422_RedVTOL_EASA_Certification_01_High_Level_Framework_v2_en.pptx|'''Download the PowerPoint presentation''']] | ||
| + | |||
| + | <br /><br /> | ||
| + | |||
| + | This presentation was prepared in the context of the '''Mini-Bee / RED VTOL''' work, with contributions from '''RED VTOL''', '''TechnoPlane''' as coordinator of the Mini-Bee project, and '''ALTEN Sud-Ouest''' through the '''ALTEN Solidaire''' initiative. | ||
| + | |||
| + | </div> | ||
| + | |||
| + | == Project context == | ||
| + | |||
| + | {| class="wikitable" style="width:100%;" | ||
! Item | ! Item | ||
! Description | ! Description | ||
|- | |- | ||
| '''Project''' | | '''Project''' | ||
| − | | Mini-Bee / | + | | Mini-Bee / RED VTOL |
|- | |- | ||
| − | | '''Aircraft | + | | '''Aircraft concept''' |
| 2PAX hybrid VTOL multicopter | | 2PAX hybrid VTOL multicopter | ||
|- | |- | ||
| Line 27: | Line 63: | ||
| Ultra-light air ambulance / VEMS concept | | Ultra-light air ambulance / VEMS concept | ||
|- | |- | ||
| − | | ''' | + | | '''Main certification authority''' |
| − | | EASA | + | | EASA — European Union Aviation Safety Agency |
|- | |- | ||
| '''Main aircraft basis''' | | '''Main aircraft basis''' | ||
| Line 36: | Line 72: | ||
| SC-VTOL-02 Small-Category VTOL-Capable Aircraft | | SC-VTOL-02 Small-Category VTOL-Capable Aircraft | ||
|- | |- | ||
| − | | ''' | + | | '''Project logic''' |
| − | | | + | | Build a credible path from innovative VTOL concept to certifiable aircraft architecture |
|} | |} | ||
| − | + | The Mini-Bee / RED VTOL concept is not only a flying vehicle study. It is also a certification-oriented design exercise. | |
| + | |||
| + | The central question is simple: | ||
| − | + | : '''How can an innovative hybrid VTOL aircraft be designed from the beginning with certification, safety and operational approval in mind?''' | |
| − | + | This question is essential because a VTOL aircraft cannot be evaluated only through performance. It must also be understandable by the authority, technically justified, testable, and traceable. | |
| − | + | == RED VTOL and ALTEN Solidaire == | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''RED VTOL''' is associated with the humanitarian and emergency medical orientation of the project. | |
| − | + | The RED VTOL vision gives the Mini-Bee concept a concrete use case: a compact VTOL aircraft able to support medical aid, rapid response, local mobility, and potentially emergency transport missions. | |
| − | + | The name RED VTOL is linked to the idea of a '''VTOL vehicle for emergency medical service''', or '''VEMS'''. This mission orientation creates strong design and certification implications: | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | * the aircraft must be safe in degraded modes; | |
| + | * the lift and thrust system must be robust; | ||
| + | * the operational use must be clearly defined; | ||
| + | * the pilot and crew logic must be considered; | ||
| + | * medical or public-service missions may bring additional constraints; | ||
| + | * the aircraft must be credible not only as a prototype, but as a future operational system. | ||
| − | + | '''ALTEN Solidaire''' appears in the presentation as a collaborative support framework. | |
| − | + | It refers to the involvement of ALTEN through a solidarity or skills-based contribution logic, with '''Christophe Marionneau, ALTEN Sud-Ouest for ALTEN Solidaire''', mentioned in the presentation credits. | |
| − | The | + | In this context, ALTEN Solidaire contributes to the technical structuring of the certification analysis. The value is not only to produce a document, but to help transform the project into a more rigorous engineering framework. |
| − | + | This type of collaboration is important for Mini-Bee because certification requires several levels of expertise: | |
| − | |||
| − | + | * aircraft architecture; | |
| + | * systems engineering; | ||
| + | * safety analysis; | ||
| + | * regulatory interpretation; | ||
| + | * electric and hybrid propulsion; | ||
| + | * rotorcraft certification logic; | ||
| + | * documentation and traceability. | ||
| − | + | TechnoPlane is identified as the coordinator of the Mini-Bee project, while RED VTOL and ALTEN Solidaire contribute to the broader collaborative R&D and certification preparation effort. | |
| − | + | == Objective of the certification framework == | |
| − | + | The purpose of the certification framework is to define the regulatory environment in which Mini-Bee / RED VTOL could be positioned. | |
| − | The | + | The presentation has four main objectives: |
| − | {| class="wikitable" | + | {| class="wikitable" style="width:100%;" |
| − | ! | + | ! Objective |
| − | ! | + | ! Meaning for the project |
| + | |- | ||
| + | | '''Classify the aircraft''' | ||
| + | | Understand whether the aircraft is treated as a rotorcraft, a VTOL-capable aircraft, or both. | ||
| + | |- | ||
| + | | '''Identify applicable texts''' | ||
| + | | List the EASA certification specifications and special conditions that influence design choices. | ||
| + | |- | ||
| + | | '''Assess rule maturity''' | ||
| + | | Understand where VTOL-capable aircraft regulation is mature, evolving, or still uncertain. | ||
|- | |- | ||
| − | | ''' | + | | '''Prepare future evidence''' |
| − | | Main | + | | Anticipate the analyses, tests and demonstrations needed to support certification. |
| + | |} | ||
| + | |||
| + | == Certification snapshot == | ||
| + | |||
| + | [[File:MiniBee_Certification_Three_Level_Logic.png|center|900px|Mini-Bee certification three-level logic]] | ||
| + | |||
| + | <div style="text-align:center; font-size:90%; color:#555; margin-top:8px;"> | ||
| + | '''Figure 2.''' Three-level certification logic: aircraft framework, system architecture, and compliance evidence. | ||
| + | </div> | ||
| + | |||
| + | <br /> | ||
| + | |||
| + | {| class="wikitable" style="width:100%; text-align:center;" | ||
| + | ! Level | ||
| + | ! Main question | ||
| + | ! Main output | ||
|- | |- | ||
| − | | ''' | + | | '''High Level''' |
| − | | | + | | Where does Mini-Bee fit in the EASA framework? |
| + | | Aircraft category and certification basis | ||
|- | |- | ||
| − | | ''' | + | | '''Medium Level''' |
| − | | | + | | Which rules apply to each system? |
| + | | System and sub-system certification map | ||
|- | |- | ||
| − | | ''' | + | | '''Low Level''' |
| − | | | + | | Which evidence proves compliance? |
| + | | Analyses, tests, inspections, simulations and reports | ||
|} | |} | ||
| − | + | == High Level — aircraft positioning == | |
| − | + | The high-level framework defines the regulatory positioning of Mini-Bee / RED VTOL. | |
| − | + | The current logic is to consider the aircraft as: | |
| − | + | * a '''small rotorcraft''' under '''CS-27'''; | |
| + | * with '''VTOL-capable characteristics''' under '''SC-VTOL-02'''. | ||
| − | + | This is the main certification idea of the presentation. | |
| − | + | CS-27 provides the small rotorcraft basis. | |
| + | SC-VTOL-02 covers the specific aspects of VTOL-capable aircraft. | ||
| − | + | [[File:MiniBee_CS27_SCVTOL_Positioning.png|center|900px|Mini-Bee CS-27 and SC-VTOL-02 positioning]] | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | <div style="text-align:center; font-size:90%; color:#555; margin-top:8px;"> | |
| + | '''Figure 3.''' Mini-Bee positioned between CS-27 small rotorcraft logic and SC-VTOL-02 VTOL-capable aircraft logic. | ||
| + | </div> | ||
== Main EASA references == | == Main EASA references == | ||
| − | {| class="wikitable" | + | EASA is the official European authority for aviation certification. |
| + | |||
| + | For the Mini-Bee / RED VTOL project, all certification assumptions must be traced back to official EASA documents, with the correct issue date, amendment level and applicability. | ||
| + | |||
| + | {| class="wikitable" style="width:100%;" | ||
! Reference | ! Reference | ||
| − | ! | + | ! Role in the framework |
|- | |- | ||
| '''CS-27''' | | '''CS-27''' | ||
| − | | | + | | Main basis for small rotorcraft certification. |
|- | |- | ||
| '''SC-VTOL-02''' | | '''SC-VTOL-02''' | ||
| − | | VTOL-capable aircraft | + | | Special condition for small-category VTOL-capable aircraft. |
|- | |- | ||
| '''CS-VLR''' | | '''CS-VLR''' | ||
| − | | | + | | Possible reference for very light rotorcraft, only if the design fits its restrictions. |
|- | |- | ||
| '''CS-29''' | | '''CS-29''' | ||
| − | | | + | | Reference for complex rotorcraft aspects or if the aircraft exits CS-27 boundaries. |
|- | |- | ||
| '''CS-E''' | | '''CS-E''' | ||
| − | | | + | | Certification specifications for engines. |
|- | |- | ||
| '''SC E-19''' | | '''SC E-19''' | ||
| − | | | + | | Special condition for electric and hybrid propulsion systems. |
|- | |- | ||
| '''CS-P''' | | '''CS-P''' | ||
| − | | | + | | Certification specifications for propellers. |
|- | |- | ||
| '''CS-26''' | | '''CS-26''' | ||
| Line 156: | Line 223: | ||
|- | |- | ||
| '''AMC-20''' | | '''AMC-20''' | ||
| − | | | + | | Acceptable means of compliance for products, parts and appliances. |
|- | |- | ||
| '''CS-34''' | | '''CS-34''' | ||
| Line 162: | Line 229: | ||
|} | |} | ||
| − | = | + | [[File:MiniBee_EASA_Reference_Map.png|center|900px|Mini-Bee EASA reference map]] |
| + | |||
| + | <div style="text-align:center; font-size:90%; color:#555; margin-top:8px;"> | ||
| + | '''Figure 4.''' EASA reference map for the Mini-Bee / RED VTOL certification framework. | ||
| + | </div> | ||
| − | + | == System and sub-system logic == | |
| − | + | The medium-level framework translates the aircraft-level certification basis into system and sub-system references. | |
| − | * | + | For Mini-Bee / RED VTOL, the main technical domains are: |
| + | |||
| + | * engine; | ||
* electric and hybrid propulsion system; | * electric and hybrid propulsion system; | ||
| − | * propellers | + | * propellers and rotors; |
* high-power electrical architecture; | * high-power electrical architecture; | ||
| − | * | + | * lift / thrust system; |
* operational airworthiness; | * operational airworthiness; | ||
* emissions and fuel venting; | * emissions and fuel venting; | ||
| − | * | + | * environmental constraints. |
| − | + | The important point is that Mini-Bee cannot be certified only as a list of independent components. | |
| − | The | + | The aircraft must be understood as an integrated system. |
| − | + | In particular, the complete '''lift / thrust system''' must be considered as a chain from energy source to thrust production. | |
| − | {| class="wikitable" | + | == Lift / thrust system chain == |
| + | |||
| + | The lift / thrust system is the core technical object of the Mini-Bee / RED VTOL certification study. | ||
| + | |||
| + | It includes: | ||
| + | |||
| + | {| class="wikitable" style="width:100%;" | ||
! Chain element | ! Chain element | ||
! Certification attention point | ! Certification attention point | ||
|- | |- | ||
| − | | Fuel / | + | | '''Fuel / battery''' |
| − | | | + | | Energy availability, storage, safety and endurance. |
|- | |- | ||
| − | | | + | | '''Engine''' |
| − | | | + | | Certified status, installation, operating limits and failure modes. |
|- | |- | ||
| − | | Electrical generation | + | | '''Generator''' |
| − | + | | Electrical generation, reliability and integration with the hybrid chain. | |
|- | |- | ||
| − | | Power electronics | + | | '''Power electronics''' |
| − | | | + | | High-voltage distribution, thermal control, EMC and safety. |
|- | |- | ||
| − | | | + | | '''Motors''' |
| − | | Redundancy, | + | | Redundancy, monitoring, degraded modes and thrust command. |
|- | |- | ||
| − | | | + | | '''Rotors / propellers''' |
| − | | | + | | Loads, vibration, thrust generation, noise and failure behaviour. |
|- | |- | ||
| − | | | + | | '''Lift''' |
| − | | | + | | Aircraft controllability, stability and safety in normal and degraded conditions. |
|} | |} | ||
| − | + | [[File:MiniBee_Lift_Thrust_System_Chain.png|center|900px|Mini-Bee lift thrust system chain]] | |
| − | + | <div style="text-align:center; font-size:90%; color:#555; margin-top:8px;"> | |
| + | '''Figure 5.''' Lift / thrust system chain from energy source to distributed lift. | ||
| + | </div> | ||
| − | + | == Certification risks == | |
| − | + | The presentation highlights several certification risks that must be controlled early. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | {| class="wikitable" style="width:100%;" | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | {| class="wikitable" | ||
! Risk | ! Risk | ||
! Why it matters | ! Why it matters | ||
|- | |- | ||
| − | | ''' | + | | '''CS-27 / SC-VTOL boundary''' |
| Mini-Bee combines rotorcraft behaviour and VTOL-capable characteristics. | | Mini-Bee combines rotorcraft behaviour and VTOL-capable characteristics. | ||
|- | |- | ||
| − | | '''Possible | + | | '''Possible CS-29 drift''' |
| − | | | + | | Mass, occupants, system complexity or operations may increase certification expectations. |
|- | |- | ||
| '''Hybrid propulsion''' | | '''Hybrid propulsion''' | ||
| − | | The propulsion chain may | + | | The complete energy and propulsion chain may become a safety-critical integrated system. |
|- | |- | ||
| '''High electrical power''' | | '''High electrical power''' | ||
| − | | | + | | EWIS, EMC, power electronics and electrical safety must be justified. |
|- | |- | ||
| '''Distributed lift''' | | '''Distributed lift''' | ||
| − | | Failure | + | | Failure cases and degraded modes must be clearly demonstrated. |
|- | |- | ||
| − | | '''VEMS | + | | '''VEMS mission''' |
| − | | | + | | Medical or public-service missions may create additional operational constraints. |
|} | |} | ||
| − | == | + | == Low Level — evidence and demonstration == |
| − | The | + | The low level is the level of concrete proof. |
| − | + | Certification is not based only on design intention. | |
| + | It is based on evidence. | ||
| − | + | Typical evidence includes: | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | * requirement allocation; | |
| + | * safety analyses; | ||
| + | * calculations; | ||
| + | * system schematics; | ||
| + | * bench tests; | ||
| + | * HIL / SIL simulations; | ||
| + | * inspection reports; | ||
| + | * environmental qualification; | ||
| + | * flight test preparation; | ||
| + | * flight test reports; | ||
| + | * compliance documentation. | ||
| − | + | The purpose of this work is to connect each certification requirement to a verifiable means of compliance. | |
| − | + | This can include: | |
| − | {| class="wikitable" | + | {| class="wikitable" style="width:100%; text-align:center;" |
| − | ! | + | ! Analysis |
| − | ! | + | ! Test |
| + | ! Simulation | ||
| + | ! Inspection | ||
| + | ! Demonstration | ||
|- | |- | ||
| − | | | + | | Safety studies |
| − | | | + | | Bench tests |
| − | | | + | | HIL / SIL |
| − | | | + | | Installation checks |
| − | | | + | | Flight evidence |
| − | |- | + | |} |
| − | + | ||
| − | + | == Certification pathway logic == | |
| − | + | ||
| − | + | The certification pathway should be progressive. | |
| − | + | ||
| + | It should move from regulatory positioning to detailed evidence: | ||
| + | |||
| + | {| class="wikitable" style="width:100%; text-align:center;" | ||
| + | ! Step 1 | ||
| + | ! Step 2 | ||
| + | ! Step 3 | ||
| + | ! Step 4 | ||
| + | ! Step 5 | ||
|- | |- | ||
| − | | | + | | Aircraft classification |
| − | | | + | | Applicable rules |
| − | | | + | | System allocation |
| − | | | + | | Evidence production |
| − | | | + | | Testing and approval |
|} | |} | ||
| − | == | + | The presentation therefore supports a structured development logic: |
| + | |||
| + | * first define the aircraft category; | ||
| + | * then identify the applicable EASA texts; | ||
| + | * then allocate requirements to systems and sub-systems; | ||
| + | * then prepare the evidence matrix; | ||
| + | * then organize tests, analyses and demonstrations. | ||
| + | |||
| + | == What this work brings to the project == | ||
| − | + | The RED VTOL / ALTEN Solidaire certification work brings structure to the Mini-Bee project. | |
| − | + | It helps the project move from a conceptual aircraft architecture to a more credible engineering path. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | The main benefits are: | |
| − | + | * better understanding of EASA certification logic; | |
| − | + | * clearer positioning between CS-27 and SC-VTOL-02; | |
| − | + | * identification of system-level certification references; | |
| − | + | * early detection of regulatory risks; | |
| − | + | * preparation of future compliance evidence; | |
| − | + | * improved design discipline; | |
| − | + | * stronger credibility for partners, authorities and future operators. | |
| − | + | ||
| − | + | == Conclusion == | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | Mini-Bee / RED VTOL should currently be considered as a '''small rotorcraft with VTOL-capable characteristics'''. | |
| − | + | The most credible certification logic is based on: | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | * '''CS-27''' as the small rotorcraft basis; | |
| + | * '''SC-VTOL-02''' for VTOL-capable aspects; | ||
| + | * '''SC E-19''' for electric and hybrid propulsion; | ||
| + | * '''CS-E''' for engines; | ||
| + | * '''CS-P''' for propellers; | ||
| + | * additional references such as CS-26, AMC-20, CS-34, CS-VLR and CS-29 when relevant. | ||
| − | The | + | The certification framework is not only a regulatory checklist. |
| + | It is a design management tool. | ||
| − | + | For Mini-Bee / RED VTOL, it helps transform an innovative hybrid VTOL concept into a structured, traceable and progressively certifiable aircraft project. | |
| − | + | == Useful links == | |
| − | [[File: | + | * [[File:20260422_RedVTOL_EASA_Certification_01_High_Level_Framework_v2_en.pptx|Download the PowerPoint presentation]] |
| + | * [[Mini-Bee]] | ||
| + | * [[Minibee_TRL3]] | ||
| + | * [[RED VTOL ONG]] | ||
Latest revision as of 12:49, 19 May 2026
VTOL Certification Framework
Mini-Bee / RED VTOL — EASA Certification Framework
Mini-Bee / RED VTOL — Certification Pathway
This page presents the high-level EASA certification framework studied for the Mini-Bee / RED VTOL concept. The objective is to understand how a 2PAX hybrid VTOL multicopter, designed as an ultra-light air ambulance concept, can be positioned inside the European aviation certification environment.
Figure 1. Mini-Bee / RED VTOL certification framework overview.
Main presentation
Download the full PowerPoint presentation
Red VTOL TRL4 — 2PAX VTOL hybrid multicopter — Ultra light air ambulance — EASA Certification Framework
File:20260422 RedVTOL EASA Certification 01 High Level Framework v2 en.pptx
This presentation was prepared in the context of the Mini-Bee / RED VTOL work, with contributions from RED VTOL, TechnoPlane as coordinator of the Mini-Bee project, and ALTEN Sud-Ouest through the ALTEN Solidaire initiative.
Project context
| Item | Description |
|---|---|
| Project | Mini-Bee / RED VTOL |
| Aircraft concept | 2PAX hybrid VTOL multicopter |
| Mission orientation | Ultra-light air ambulance / VEMS concept |
| Main certification authority | EASA — European Union Aviation Safety Agency |
| Main aircraft basis | CS-27 Small Rotorcraft |
| VTOL-specific basis | SC-VTOL-02 Small-Category VTOL-Capable Aircraft |
| Project logic | Build a credible path from innovative VTOL concept to certifiable aircraft architecture |
The Mini-Bee / RED VTOL concept is not only a flying vehicle study. It is also a certification-oriented design exercise.
The central question is simple:
- How can an innovative hybrid VTOL aircraft be designed from the beginning with certification, safety and operational approval in mind?
This question is essential because a VTOL aircraft cannot be evaluated only through performance. It must also be understandable by the authority, technically justified, testable, and traceable.
RED VTOL and ALTEN Solidaire
RED VTOL is associated with the humanitarian and emergency medical orientation of the project.
The RED VTOL vision gives the Mini-Bee concept a concrete use case: a compact VTOL aircraft able to support medical aid, rapid response, local mobility, and potentially emergency transport missions.
The name RED VTOL is linked to the idea of a VTOL vehicle for emergency medical service, or VEMS. This mission orientation creates strong design and certification implications:
- the aircraft must be safe in degraded modes;
- the lift and thrust system must be robust;
- the operational use must be clearly defined;
- the pilot and crew logic must be considered;
- medical or public-service missions may bring additional constraints;
- the aircraft must be credible not only as a prototype, but as a future operational system.
ALTEN Solidaire appears in the presentation as a collaborative support framework.
It refers to the involvement of ALTEN through a solidarity or skills-based contribution logic, with Christophe Marionneau, ALTEN Sud-Ouest for ALTEN Solidaire, mentioned in the presentation credits.
In this context, ALTEN Solidaire contributes to the technical structuring of the certification analysis. The value is not only to produce a document, but to help transform the project into a more rigorous engineering framework.
This type of collaboration is important for Mini-Bee because certification requires several levels of expertise:
- aircraft architecture;
- systems engineering;
- safety analysis;
- regulatory interpretation;
- electric and hybrid propulsion;
- rotorcraft certification logic;
- documentation and traceability.
TechnoPlane is identified as the coordinator of the Mini-Bee project, while RED VTOL and ALTEN Solidaire contribute to the broader collaborative R&D and certification preparation effort.
Objective of the certification framework
The purpose of the certification framework is to define the regulatory environment in which Mini-Bee / RED VTOL could be positioned.
The presentation has four main objectives:
| Objective | Meaning for the project |
|---|---|
| Classify the aircraft | Understand whether the aircraft is treated as a rotorcraft, a VTOL-capable aircraft, or both. |
| Identify applicable texts | List the EASA certification specifications and special conditions that influence design choices. |
| Assess rule maturity | Understand where VTOL-capable aircraft regulation is mature, evolving, or still uncertain. |
| Prepare future evidence | Anticipate the analyses, tests and demonstrations needed to support certification. |
Certification snapshot
Figure 2. Three-level certification logic: aircraft framework, system architecture, and compliance evidence.
| Level | Main question | Main output |
|---|---|---|
| High Level | Where does Mini-Bee fit in the EASA framework? | Aircraft category and certification basis |
| Medium Level | Which rules apply to each system? | System and sub-system certification map |
| Low Level | Which evidence proves compliance? | Analyses, tests, inspections, simulations and reports |
High Level — aircraft positioning
The high-level framework defines the regulatory positioning of Mini-Bee / RED VTOL.
The current logic is to consider the aircraft as:
- a small rotorcraft under CS-27;
- with VTOL-capable characteristics under SC-VTOL-02.
This is the main certification idea of the presentation.
CS-27 provides the small rotorcraft basis. SC-VTOL-02 covers the specific aspects of VTOL-capable aircraft.
Figure 3. Mini-Bee positioned between CS-27 small rotorcraft logic and SC-VTOL-02 VTOL-capable aircraft logic.
Main EASA references
EASA is the official European authority for aviation certification.
For the Mini-Bee / RED VTOL project, all certification assumptions must be traced back to official EASA documents, with the correct issue date, amendment level and applicability.
| Reference | Role in the framework |
|---|---|
| CS-27 | Main basis for small rotorcraft certification. |
| SC-VTOL-02 | Special condition for small-category VTOL-capable aircraft. |
| CS-VLR | Possible reference for very light rotorcraft, only if the design fits its restrictions. |
| CS-29 | Reference for complex rotorcraft aspects or if the aircraft exits CS-27 boundaries. |
| CS-E | Certification specifications for engines. |
| SC E-19 | Special condition for electric and hybrid propulsion systems. |
| CS-P | Certification specifications for propellers. |
| CS-26 | Additional airworthiness specifications for operations. |
| AMC-20 | Acceptable means of compliance for products, parts and appliances. |
| CS-34 | Aircraft engine emissions and fuel venting. |
Figure 4. EASA reference map for the Mini-Bee / RED VTOL certification framework.
System and sub-system logic
The medium-level framework translates the aircraft-level certification basis into system and sub-system references.
For Mini-Bee / RED VTOL, the main technical domains are:
- engine;
- electric and hybrid propulsion system;
- propellers and rotors;
- high-power electrical architecture;
- lift / thrust system;
- operational airworthiness;
- emissions and fuel venting;
- environmental constraints.
The important point is that Mini-Bee cannot be certified only as a list of independent components.
The aircraft must be understood as an integrated system.
In particular, the complete lift / thrust system must be considered as a chain from energy source to thrust production.
Lift / thrust system chain
The lift / thrust system is the core technical object of the Mini-Bee / RED VTOL certification study.
It includes:
| Chain element | Certification attention point |
|---|---|
| Fuel / battery | Energy availability, storage, safety and endurance. |
| Engine | Certified status, installation, operating limits and failure modes. |
| Generator | Electrical generation, reliability and integration with the hybrid chain. |
| Power electronics | High-voltage distribution, thermal control, EMC and safety. |
| Motors | Redundancy, monitoring, degraded modes and thrust command. |
| Rotors / propellers | Loads, vibration, thrust generation, noise and failure behaviour. |
| Lift | Aircraft controllability, stability and safety in normal and degraded conditions. |
Figure 5. Lift / thrust system chain from energy source to distributed lift.
Certification risks
The presentation highlights several certification risks that must be controlled early.
| Risk | Why it matters |
|---|---|
| CS-27 / SC-VTOL boundary | Mini-Bee combines rotorcraft behaviour and VTOL-capable characteristics. |
| Possible CS-29 drift | Mass, occupants, system complexity or operations may increase certification expectations. |
| Hybrid propulsion | The complete energy and propulsion chain may become a safety-critical integrated system. |
| High electrical power | EWIS, EMC, power electronics and electrical safety must be justified. |
| Distributed lift | Failure cases and degraded modes must be clearly demonstrated. |
| VEMS mission | Medical or public-service missions may create additional operational constraints. |
Low Level — evidence and demonstration
The low level is the level of concrete proof.
Certification is not based only on design intention. It is based on evidence.
Typical evidence includes:
- requirement allocation;
- safety analyses;
- calculations;
- system schematics;
- bench tests;
- HIL / SIL simulations;
- inspection reports;
- environmental qualification;
- flight test preparation;
- flight test reports;
- compliance documentation.
The purpose of this work is to connect each certification requirement to a verifiable means of compliance.
This can include:
| Analysis | Test | Simulation | Inspection | Demonstration |
|---|---|---|---|---|
| Safety studies | Bench tests | HIL / SIL | Installation checks | Flight evidence |
Certification pathway logic
The certification pathway should be progressive.
It should move from regulatory positioning to detailed evidence:
| Step 1 | Step 2 | Step 3 | Step 4 | Step 5 |
|---|---|---|---|---|
| Aircraft classification | Applicable rules | System allocation | Evidence production | Testing and approval |
The presentation therefore supports a structured development logic:
- first define the aircraft category;
- then identify the applicable EASA texts;
- then allocate requirements to systems and sub-systems;
- then prepare the evidence matrix;
- then organize tests, analyses and demonstrations.
What this work brings to the project
The RED VTOL / ALTEN Solidaire certification work brings structure to the Mini-Bee project.
It helps the project move from a conceptual aircraft architecture to a more credible engineering path.
The main benefits are:
- better understanding of EASA certification logic;
- clearer positioning between CS-27 and SC-VTOL-02;
- identification of system-level certification references;
- early detection of regulatory risks;
- preparation of future compliance evidence;
- improved design discipline;
- stronger credibility for partners, authorities and future operators.
Conclusion
Mini-Bee / RED VTOL should currently be considered as a small rotorcraft with VTOL-capable characteristics.
The most credible certification logic is based on:
- CS-27 as the small rotorcraft basis;
- SC-VTOL-02 for VTOL-capable aspects;
- SC E-19 for electric and hybrid propulsion;
- CS-E for engines;
- CS-P for propellers;
- additional references such as CS-26, AMC-20, CS-34, CS-VLR and CS-29 when relevant.
The certification framework is not only a regulatory checklist. It is a design management tool.
For Mini-Bee / RED VTOL, it helps transform an innovative hybrid VTOL concept into a structured, traceable and progressively certifiable aircraft project.