Difference between revisions of "Certification FrameWork VTOL"

From beeplane
Jump to navigation Jump to search
Line 1: Line 1:
 
= VTOL Certification Framework =
 
= VTOL Certification Framework =
 +
 +
'''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="border:1px solid #d0d7de; border-radius:14px; padding:22px; background:#f8fafc; margin-bottom:25px;">
  
<div style="font-size:150%; font-weight:bold; margin-bottom:8px;">
+
<div style="font-size:150%; font-weight:bold; color:#1f4e79; margin-bottom:8px;">
Mini-Bee / Red VTOL — EASA Certification Framework
+
Mini-Bee / RED VTOL — Certification Pathway
 
</div>
 
</div>
  
 
<div style="font-size:105%; line-height:1.6;">
 
<div style="font-size:105%; line-height:1.6;">
A high-level certification map for a 2PAX hybrid VTOL multicopter designed as an ultra-light air ambulance concept.
+
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>
 
</div>
  
 
<br />
 
<br />
  
[[File:20260422 RedVTOL EASA Certification 01 High Level Framework v2 en.pptx|center|900px|Mini-Bee / Red VTOL EASA Certification Framework]]
+
[[File:MiniBee_VTOL_Certification_Framework_Hero.png|center|900px|Mini-Bee / RED VTOL certification framework hero visual]]
  
 
<div style="text-align:center; font-size:90%; color:#555; margin-top:8px;">
 
<div style="text-align:center; font-size:90%; color:#555; margin-top:8px;">
'''Hero visual placeholder''' Mini-Bee aircraft, EASA certification path, CS-27, SC-VTOL-02 and system demonstration.
+
'''Figure 1.''' Mini-Bee / RED VTOL certification framework overview.
 
</div>
 
</div>
  
Line 23: Line 26:
 
__TOC__
 
__TOC__
  
== Main document ==
+
== Main presentation ==
  
 
<div style="border:2px solid #1f4e79; border-radius:12px; padding:18px; background:#eef6ff; margin-bottom:25px;">
 
<div style="border:2px solid #1f4e79; border-radius:12px; padding:18px; background:#eef6ff; margin-bottom:25px;">
Line 41: Line 44:
 
<br /><br />
 
<br /><br />
  
This presentation defines the high-level EASA certification logic for Mini-Bee / Red VTOL
+
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.
It identifies the main aircraft classification, the applicable certification texts, the system references, and the next certification risks to analyse.
 
  
 
</div>
 
</div>
  
== Certification snapshot ==
+
== Project context ==
  
{| class="wikitable" style="width:100%; text-align:center;"
+
{| class="wikitable" style="width:100%;"
! Project
+
! Item
! Aircraft logic
+
! Description
! Main basis
+
|-
! VTOL complement
+
| '''Project'''
! Key issue
+
| Mini-Bee / RED VTOL
 
|-
 
|-
| '''Mini-Bee / Red VTOL'''
+
| '''Aircraft concept'''
 
| 2PAX hybrid VTOL multicopter
 
| 2PAX hybrid VTOL multicopter
| '''CS-27'''
+
|-
| '''SC-VTOL-02'''
+
| '''Mission orientation'''
| Certifiable lift/thrust system
+
| 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
 
|}
 
|}
  
<gallery mode="packed" heights="210px">
+
The Mini-Bee / RED VTOL concept is not only a flying vehicle study. It is also a certification-oriented design exercise.
File:MiniBee_High_Level_Certification_Map.png|'''High Level'''<br />Aircraft classification and regulatory basis.
+
 
File:MiniBee_System_Certification_Map.png|'''Medium Level'''<br />System and sub-system certification references.
+
The central question is simple:
File:MiniBee_Evidence_Demonstration_Map.png|'''Low Level'''<br />Evidence, tests and means of compliance.
+
 
</gallery>
+
: '''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 ==
  
== Page objective ==
+
'''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 objective of this page is to summarize the certification logic of Mini-Bee / Red VTOL.
+
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:
  
It answers three practical questions:
+
* 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:
  
 
{| class="wikitable" style="width:100%;"
 
{| class="wikitable" style="width:100%;"
! Question
+
! Objective
! Certification answer
+
! Meaning for the project
 
|-
 
|-
| '''What is the aircraft category?'''
+
| '''Classify the aircraft'''
| Small rotorcraft with VTOL-capable characteristics.
+
| Understand whether the aircraft is treated as a rotorcraft, a VTOL-capable aircraft, or both.
 
|-
 
|-
| '''Which rules apply?'''
+
| '''Identify applicable texts'''
| CS-27, SC-VTOL-02 and associated system references.
+
| List the EASA certification specifications and special conditions that influence design choices.
 
|-
 
|-
| '''What must be demonstrated?'''
+
| '''Assess rule maturity'''
| Safety, compliance, lift/thrust system robustness and technical evidence.
+
| 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.
 
|}
 
|}
  
== Visual certification logic ==
+
== Certification snapshot ==
  
 
[[File:MiniBee_Certification_Three_Level_Logic.png|center|900px|Mini-Bee certification three-level logic]]
 
[[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;">
 
<div style="text-align:center; font-size:90%; color:#555; margin-top:8px;">
'''Figure placeholder''' Three-level certification logic: High Level, Medium Level, Low Level.
+
'''Figure 2.''' Three-level certification logic: aircraft framework, system architecture, and compliance evidence.
 
</div>
 
</div>
  
 
<br />
 
<br />
  
{| class="wikitable" style="width:100%;"
+
{| class="wikitable" style="width:100%; text-align:center;"
 
! Level
 
! Level
! Meaning
+
! Main question
 
! Main output
 
! Main output
 
|-
 
|-
 
| '''High Level'''
 
| '''High Level'''
| Aircraft classification and certification basis.
+
| Where does Mini-Bee fit in the EASA framework?
| CS-27 + SC-VTOL-02 positioning.
+
| Aircraft category and certification basis
 
|-
 
|-
 
| '''Medium Level'''
 
| '''Medium Level'''
| System and sub-system rules.
+
| Which rules apply to each system?
| CS-E, SC E-19, CS-P, CS-26, AMC-20, CS-34.
+
| System and sub-system certification map
 
|-
 
|-
 
| '''Low Level'''
 
| '''Low Level'''
| Compliance demonstration.
+
| Which evidence proves compliance?
| Analyses, tests, simulations, inspections and reports.
+
| Analyses, tests, inspections, simulations and reports
 
|}
 
|}
  
 
== High Level — aircraft positioning ==
 
== High Level — aircraft positioning ==
  
<div style="display:flex; gap:22px; align-items:flex-start; flex-wrap:wrap;">
+
The high-level framework defines the regulatory positioning of Mini-Bee / RED VTOL.
 
 
<div style="flex:1; min-width:320px;">
 
  
The current certification logic is to position Mini-Bee / Red VTOL as:
+
The current logic is to consider the aircraft as:
  
 
* a '''small rotorcraft''' under '''CS-27''';
 
* a '''small rotorcraft''' under '''CS-27''';
 
* with '''VTOL-capable characteristics''' under '''SC-VTOL-02'''.
 
* with '''VTOL-capable characteristics''' under '''SC-VTOL-02'''.
  
This is the central regulatory positioning of the project.
+
This is the main certification idea of the presentation.
  
CS-27 gives the rotorcraft basis.   
+
CS-27 provides the small rotorcraft basis.   
SC-VTOL-02 covers the specific VTOL-capable aspects.
+
SC-VTOL-02 covers the specific aspects of VTOL-capable aircraft.
  
</div>
+
[[File:MiniBee_CS27_SCVTOL_Positioning.png|center|900px|Mini-Bee CS-27 and SC-VTOL-02 positioning]]
  
<div style="flex:1; min-width:320px;">
+
<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.
[[File:MiniBee_CS27_SCVTOL_Positioning.png|center|430px|Mini-Bee CS-27 and SC-VTOL-02 positioning]]
 
 
 
<div style="text-align:center; font-size:90%; color:#555;">
 
'''Visual placeholder''' Mini-Bee positioned between CS-27 and SC-VTOL-02.
 
 
</div>
 
</div>
  
</div>
+
== Main EASA references ==
  
</div>
+
EASA is the official European authority for aviation certification.
  
== Main EASA references ==
+
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%;"
 
{| class="wikitable" style="width:100%;"
 
! Reference
 
! Reference
 
! Role in the framework
 
! Role in the framework
|-
 
| '''EASA'''
 
| Official European authority for aviation certification.
 
 
|-
 
|-
 
| '''CS-27'''
 
| '''CS-27'''
| Main basis for small rotorcraft.
+
| Main basis for small rotorcraft certification.
 
|-
 
|-
 
| '''SC-VTOL-02'''
 
| '''SC-VTOL-02'''
Line 162: Line 203:
 
|-
 
|-
 
| '''CS-VLR'''
 
| '''CS-VLR'''
| Possible reference for very light rotorcraft, if the design fits.
+
| Possible reference for very light rotorcraft, only if the design fits its restrictions.
 
|-
 
|-
 
| '''CS-29'''
 
| '''CS-29'''
| Reference for more complex rotorcraft aspects.
+
| Reference for complex rotorcraft aspects or if the aircraft exits CS-27 boundaries.
|}
 
 
 
[[File:MiniBee_EASA_Reference_Map.png|center|900px|Mini-Bee EASA reference map]]
 
 
 
<div style="text-align:center; font-size:90%; color:#555;">
 
'''Visual placeholder''' — EASA reference map: CS-27, SC-VTOL-02, CS-VLR and CS-29.
 
</div>
 
 
 
== Medium Level — system certification map ==
 
 
 
The aircraft-level certification basis must be translated into system and sub-system references.
 
 
 
{| class="wikitable" style="width:100%;"
 
! Aircraft domain
 
! Main certification reference
 
 
|-
 
|-
| Engine
 
 
| '''CS-E'''
 
| '''CS-E'''
 +
| Certification specifications for engines.
 
|-
 
|-
| Electric / hybrid propulsion
 
 
| '''SC E-19'''
 
| '''SC E-19'''
 +
| Special condition for electric and hybrid propulsion systems.
 
|-
 
|-
| Propellers
 
 
| '''CS-P'''
 
| '''CS-P'''
 +
| Certification specifications for propellers.
 
|-
 
|-
| Operational airworthiness
 
 
| '''CS-26'''
 
| '''CS-26'''
 +
| Additional airworthiness specifications for operations.
 
|-
 
|-
| Products, parts and appliances
 
 
| '''AMC-20'''
 
| '''AMC-20'''
 +
| Acceptable means of compliance for products, parts and appliances.
 
|-
 
|-
| Emissions and fuel venting
 
 
| '''CS-34'''
 
| '''CS-34'''
 +
| Aircraft engine emissions and fuel venting.
 
|}
 
|}
  
[[File:MiniBee_Medium_Level_System_Certification_Map.png|center|900px|Mini-Bee medium level certification map]]
+
[[File:MiniBee_EASA_Reference_Map.png|center|900px|Mini-Bee EASA reference map]]
  
<div style="text-align:center; font-size:90%; color:#555;">
+
<div style="text-align:center; font-size:90%; color:#555; margin-top:8px;">
'''Visual placeholder''' — System map linking each aircraft domain to its certification reference.
+
'''Figure 4.''' EASA reference map for the Mini-Bee / RED VTOL certification framework.
 
</div>
 
</div>
  
== Lift / thrust system ==
+
== 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.
  
For Mini-Bee / Red VTOL, the key technical object is the complete '''lift / thrust system'''.
+
The aircraft must be understood as an integrated system.
  
It must be considered as an integrated chain.
+
In particular, the complete '''lift / thrust system''' must be considered as a chain from energy source to thrust production.
  
[[File:MiniBee_Lift_Thrust_System_Chain.png|center|900px|Mini-Bee lift thrust system chain]]
+
== Lift / thrust system chain ==
  
<div style="text-align:center; font-size:90%; color:#555;">
+
The lift / thrust system is the core technical object of the Mini-Bee / RED VTOL certification study.
'''Visual placeholder''' — Fuel source → engine → generator → power electronics → motors → propellers → thrust.
 
</div>
 
  
<br />
+
It includes:
  
 
{| class="wikitable" style="width:100%;"
 
{| class="wikitable" style="width:100%;"
 
! Chain element
 
! Chain element
! Certification attention
+
! Certification attention point
 
|-
 
|-
| Energy source
+
| '''Fuel / battery'''
| Safety, endurance, fuel venting.
+
| Energy availability, storage, safety and endurance.
 
|-
 
|-
| Thermal engine
+
| '''Engine'''
| CS-E and installation.
+
| Certified status, installation, operating limits and failure modes.
 
|-
 
|-
| Electrical generation
+
| '''Generator'''
| Reliability and degraded modes.
+
| Electrical generation, reliability and integration with the hybrid chain.
 
|-
 
|-
| Power electronics
+
| '''Power electronics'''
| Electrical safety and EMC.
+
| High-voltage distribution, thermal control, EMC and safety.
 
|-
 
|-
| Electric motors
+
| '''Motors'''
| Redundancy and failure cases.
+
| Redundancy, monitoring, degraded modes and thrust command.
 
|-
 
|-
| Propellers / rotors
+
| '''Rotors / propellers'''
| Loads, vibration, noise and safety.
+
| Loads, vibration, thrust generation, noise and failure behaviour.
 
|-
 
|-
| Control logic
+
| '''Lift'''
| Monitoring, command and degraded operation.
+
| Aircraft controllability, stability and safety in normal and degraded conditions.
 
|}
 
|}
  
== Low Level — evidence and demonstration ==
+
[[File:MiniBee_Lift_Thrust_System_Chain.png|center|900px|Mini-Bee lift thrust system chain]]
  
Certification is not based on intention. 
+
<div style="text-align:center; font-size:90%; color:#555; margin-top:8px;">
It is based on documented evidence.
+
'''Figure 5.''' Lift / thrust system chain from energy source to distributed lift.
 
 
[[File:MiniBee_Low_Level_Evidence_Matrix.png|center|900px|Mini-Bee evidence matrix]]
 
 
 
<div style="text-align:center; font-size:90%; color:#555;">
 
'''Visual placeholder''' — Requirements linked to analyses, tests, inspections, simulations and demonstrations.
 
 
</div>
 
</div>
  
<br />
+
== Certification risks ==
 
 
{| class="wikitable" style="width:100%; text-align:center;"
 
! Analysis
 
! Test
 
! Simulation
 
! Inspection
 
! Demonstration
 
|-
 
| Safety studies
 
| Bench tests
 
| HIL / SIL
 
| Installation checks
 
| Flight evidence
 
|}
 
  
== Certification risks ==
+
The presentation highlights several certification risks that must be controlled early.
  
 
{| class="wikitable" style="width:100%;"
 
{| class="wikitable" style="width:100%;"
 
! Risk
 
! Risk
! Design impact
+
! Why it matters
 
|-
 
|-
 
| '''CS-27 / SC-VTOL boundary'''
 
| '''CS-27 / SC-VTOL boundary'''
| The aircraft must remain clearly classifiable.
+
| Mini-Bee combines rotorcraft behaviour and VTOL-capable characteristics.
 
|-
 
|-
| '''CS-29 drift'''
+
| '''Possible CS-29 drift'''
| Complexity may increase certification burden.
+
| Mass, occupants, system complexity or operations may increase certification expectations.
 
|-
 
|-
 
| '''Hybrid propulsion'''
 
| '''Hybrid propulsion'''
| The full chain may be safety-critical.
+
| The complete energy and propulsion chain may become a safety-critical integrated system.
 
|-
 
|-
 
| '''High electrical power'''
 
| '''High electrical power'''
| EWIS, EMC and power distribution must be justified.
+
| EWIS, EMC, power electronics and electrical safety must be justified.
 
|-
 
|-
 
| '''Distributed lift'''
 
| '''Distributed lift'''
| Failure cases and degraded modes must be demonstrated.
+
| Failure cases and degraded modes must be clearly demonstrated.
 
|-
 
|-
 
| '''VEMS mission'''
 
| '''VEMS mission'''
| Medical or public service use may add operational constraints.
+
| 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.
 +
 +
[[File:MiniBee_Low_Level_Evidence_Matrix.png|center|900px|Mini-Bee low level evidence matrix]]
 +
 +
<div style="text-align:center; font-size:90%; color:#555; margin-top:8px;">
 +
'''Figure 6.''' Low-level evidence matrix linking requirements to analyses, tests, inspections and demonstrations.
 +
</div>
  
 
== Certification pathway ==
 
== Certification pathway ==
 +
 +
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
 +
|}
  
 
[[File:MiniBee_Certification_Pathway.png|center|900px|Mini-Bee certification pathway]]
 
[[File:MiniBee_Certification_Pathway.png|center|900px|Mini-Bee certification pathway]]
  
<div style="text-align:center; font-size:90%; color:#555;">
+
<div style="text-align:center; font-size:90%; color:#555; margin-top:8px;">
'''Visual placeholder''' — Concept → classification → system map → evidence → tests → operational approval.
+
'''Figure 7.''' Certification pathway from concept definition to compliance demonstration.
 
</div>
 
</div>
  
== Key conclusions from the presentation ==
+
== What this work brings to the project ==
  
<div style="border-left:5px solid #1f4e79; padding:14px 18px; background:#f6f8fa; margin:18px 0;">
+
The RED VTOL / ALTEN Solidaire certification work brings structure to the Mini-Bee project.
  
Mini-Bee / Red VTOL should currently be considered as a '''small rotorcraft with VTOL-capable characteristics'''.
+
It helps the project move from a conceptual aircraft architecture to a more credible engineering path.
  
The most credible certification logic is:
+
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;
 
* '''CS-27''' as the small rotorcraft basis;
 
* '''SC-VTOL-02''' for VTOL-capable aspects;
 
* '''SC-VTOL-02''' for VTOL-capable aspects;
* '''SC E-19''' for hybrid propulsion;
+
* '''SC E-19''' for electric and hybrid propulsion;
* '''CS-E''' and '''CS-P''' for engine and propulsive elements;
+
* '''CS-E''' for engines;
* additional references when operations, complexity or environmental aspects require them.
+
* '''CS-P''' for propellers;
 
+
* additional references such as CS-26, AMC-20, CS-34, CS-VLR and CS-29 when relevant.
</div>
 
  
== Visuals to create ==
+
The certification framework is not only a regulatory checklist. 
 +
It is a design management tool.
  
{| class="wikitable" style="width:100%;"
+
For Mini-Bee / RED VTOL, it helps transform an innovative hybrid VTOL concept into a structured, traceable and progressively certifiable aircraft project.
! File name
 
! Role
 
|-
 
| '''MiniBee_VTOL_Certification_Framework_Hero.png'''
 
| Hero image for the top of the page.
 
|-
 
| '''MiniBee_Certification_Three_Level_Logic.png'''
 
| Explain High / Medium / Low certification levels.
 
|-
 
| '''MiniBee_CS27_SCVTOL_Positioning.png'''
 
| Show the dual positioning of Mini-Bee.
 
|-
 
| '''MiniBee_EASA_Reference_Map.png'''
 
| Show the main EASA references.
 
|-
 
| '''MiniBee_Medium_Level_System_Certification_Map.png'''
 
| Link systems to certification references.
 
|-
 
| '''MiniBee_Lift_Thrust_System_Chain.png'''
 
| Show the full lift/thrust chain.
 
|-
 
| '''MiniBee_Low_Level_Evidence_Matrix.png'''
 
| Show compliance evidence.
 
|-
 
| '''MiniBee_Certification_Pathway.png'''
 
| Final certification roadmap visual.
 
|}
 
  
 
== Useful links ==
 
== Useful links ==
Line 363: Line 415:
 
* [[SC-VTOL-02]]
 
* [[SC-VTOL-02]]
 
* [[Hybrid Propulsion]]
 
* [[Hybrid Propulsion]]
 
+
* [[TRL]]
== See also ==
 
 
 
* [[Mini-Bee]]
 
* [[Bee-Plane]]
 
* [[Iso-Plane]]
 
* [[RED VTOL ONG]]
 

Revision as of 12:29, 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.


Mini-Bee / RED VTOL certification framework hero visual

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

Mini-Bee certification three-level logic

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.

Mini-Bee CS-27 and SC-VTOL-02 positioning

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.
Mini-Bee EASA reference map

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.
Mini-Bee lift thrust system chain

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.

Figure 6. Low-level evidence matrix linking requirements to analyses, tests, inspections and demonstrations.

Certification pathway

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

Figure 7. Certification pathway from concept definition to compliance demonstration.

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.

Useful links