Difference between revisions of "Certification FrameWork VTOL"

From beeplane
Jump to navigation Jump to search
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
= VTOL Certification Framework for Mini-Bee / Red VTOL =
+
= VTOL Certification Framework =
  
−
[[File:MiniBee_VTOL_Certification_Framework_Cover.png|thumb|center|900px|'''Figure 1.''' Mini-Bee / Red VTOL certification framework overview. Placeholder for a visual showing the aircraft, the EASA framework, and the High / Medium / Low certification logic.]]
+
'''Mini-Bee / RED VTOL — EASA Certification Framework'''
  
−
The '''VTOL Certification Framework''' is the regulatory and technical structure that defines how a vertical take-off and landing aircraft can be designed, justified, tested, and accepted by the aviation authority.
+
<div style="border:1px solid #d0d7de; border-radius:14px; padding:22px; background:#f8fafc; margin-bottom:25px;">
  
−
For a project such as '''Mini-Bee / Red VTOL''', certification is not a secondary topic. It is a central part of the design logic. The objective is not only to build an innovative hybrid VTOL aircraft, but also to demonstrate that the concept can follow a credible path toward certification, safety, and operational approval.
+
<div style="font-size:150%; font-weight:bold; color:#1f4e79; margin-bottom:8px;">
 +
Mini-Bee / RED VTOL — Certification Pathway
 +
</div>
  
−
In Europe, this framework is based on '''EASA''' — the European Union Aviation Safety Agency. EASA publishes the official certification specifications, special conditions, acceptable means of compliance, guidance material, and rulemaking documents used as the basis for certification demonstration.
+
<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>
  
−
The Mini-Bee / Red VTOL concept is currently positioned as a '''small rotorcraft''' under '''CS-27''', complemented by '''SC-VTOL-02''' for its VTOL-capable characteristics. This combination is essential because the aircraft behaves partly like a rotorcraft, while also introducing specific VTOL features such as distributed lift, hybrid propulsion, high-power electrical architecture, and a complex lift/thrust chain.
+
<br />
  
−
== Objective of the certification framework ==
+
[[File:MiniBee_VTOL_Certification_Framework_Hero.png|center|900px|Mini-Bee / RED VTOL certification framework hero visual]]
  
−
The objective of this certification framework is to:
+
<div style="text-align:center; font-size:90%; color:#555; margin-top:8px;">
 +
'''Figure 1.''' Mini-Bee / RED VTOL certification framework overview.
 +
</div>
  
−
* define the regulatory environment in which the Mini-Bee / Red VTOL concept is included;
+
</div>
−
* identify the main certification texts that orient the aircraft design;
 
−
* anticipate the future certification process;
 
−
* analyse the maturity of the regulation, especially for VTOL-capable aircraft;
 
−
* identify potential gaps, uncertainties, and areas requiring further authority interaction;
 
−
* transform the aircraft concept into a certifiable engineering project.
 
  
−
This framework is also a design enabler. It helps discover associated technologies, technical constraints, and certification orientations that can make the Mini-Bee / Red VTOL concept more coherent with market expectations and aviation safety requirements.
+
__TOC__
  
−
[[File:MiniBee_Certification_Objectives.png|thumb|center|900px|'''Figure 2.''' Certification framework objectives: classification, applicable rules, maturity analysis, and evidence preparation.]]
+
== Main presentation ==
  
−
== High Level Certification Framework ==
+
<div style="border:2px solid #1f4e79; border-radius:12px; padding:18px; background:#eef6ff; margin-bottom:25px;">
  
−
The '''High Level Certification Framework''' corresponds to the strategic level of the certification approach.
+
<div style="font-size:125%; font-weight:bold; color:#1f4e79;">
 +
Download the full PowerPoint presentation
 +
</div>
  
−
At this level, the question is:
+
<br />
  
−
: '''Where should Mini-Bee / Red VTOL be classified within the EASA certification framework?'''
+
'''Red VTOL TRL4 — 2PAX VTOL hybrid multicopter — Ultra light air ambulance — EASA Certification Framework'''
  
−
The answer defines the aircraft category, the main certification basis, the complementary certification references, and the regulatory philosophy that will guide the design.
+
<br /><br />
  
−
For Mini-Bee / Red VTOL, the current logic is:
+
[[File:20260422_RedVTOL_EASA_Certification_01_High_Level_Framework_v2_en.pptx|'''Download the PowerPoint presentation''']]
  
−
* '''CS-27 Small Rotorcraft''' as the main certification basis;
+
<br /><br />
−
* '''SC-VTOL-02 Small-Category VTOL-Capable Aircraft''' as a complementary framework for VTOL-specific features;
 
−
* '''CS-29 Large Rotorcraft''' as a possible reference for design drivers, especially where system complexity or operational use goes beyond CS-27;
 
−
* '''CS-VLR Very Light Rotorcraft''' as a possible reference only if the aircraft design fits its restrictive conditions;
 
−
* selected '''AMC''', '''GM''', '''RMT''', '''NPA''', and consultation documents as supporting material.
 
  
−
[[File:MiniBee_High_Level_Certification_Map.png|thumb|center|900px|'''Figure 3.''' High Level certification map showing CS-27, SC-VTOL-02, CS-29, and CS-VLR around the Mini-Bee concept.]]
+
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.
  
−
=== EASA as the official reference ===
+
</div>
  
−
EASA is the official European authority for aviation safety and certification. Any certification basis used for Mini-Bee / Red VTOL must be traced to an official EASA source.
+
== Project context ==
  
−
This point is important because certification cannot be built on informal interpretations or outdated documents. Each text used as a reference should be checked for:
+
{| class="wikitable" style="width:100%;"
−
 
+
! Item
−
* official EASA origin;
+
! Description
−
* issue number;
+
|-
−
* amendment number;
+
| '''Project'''
−
* publication date;
+
| Mini-Bee / RED VTOL
−
* current validity;
+
|-
−
* associated AMC or GM;
+
| '''Aircraft concept'''
−
* relationship with other certification specifications.
+
| 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
 +
|}
  
−
For Mini-Bee / Red VTOL, the EASA Pro environment is the main access point for official certification material, including certification specifications, special conditions, rulemaking tasks, easy access rules, and consultation documents.
+
The Mini-Bee / RED VTOL concept is not only a flying vehicle study. It is also a certification-oriented design exercise.
  
−
== Main certification positioning of Mini-Bee ==
+
The central question is simple:
  
−
Mini-Bee / Red VTOL is currently considered as:
+
: '''How can an innovative hybrid VTOL aircraft be designed from the beginning with certification, safety and operational approval in mind?'''
  
−
: '''a small rotorcraft under CS-27, with VTOL-capable characteristics under SC-VTOL-02.'''
+
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.
  
−
This means that the design should comply with both:
+
== RED VTOL and ALTEN Solidaire ==
  
−
* '''CS-27 Small Rotorcraft''';
+
'''RED VTOL''' is associated with the humanitarian and emergency medical orientation of the project.
−
* '''SC-VTOL-02 Small-Category VTOL-Capable Aircraft'''.
 
  
−
This dual positioning is one of the key points of the certification strategy.
+
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.
  
−
CS-27 provides the rotorcraft basis. 
+
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:
−
SC-VTOL-02 provides the additional logic for the VTOL-capable aspects that are not fully covered by conventional rotorcraft rules.
 
  
−
[[File:MiniBee_CS27_SCVTOL_Positioning.png|thumb|right|450px|'''Figure 4.''' Proposed visual: Mini-Bee positioned between small rotorcraft logic and VTOL-capable aircraft logic.]]
+
* 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.
  
−
== SC-VTOL-02 Small-Category VTOL-Capable Aircraft ==
+
'''ALTEN Solidaire''' appears in the presentation as a collaborative support framework.
  
−
'''SC-VTOL-02''' is a special condition for small-category VTOL-capable aircraft.
+
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.
  
−
It addresses aircraft that are able to take off and land vertically but differ from conventional rotorcraft or fixed-wing aircraft. This point is central for Mini-Bee / Red VTOL because the aircraft uses a non-conventional architecture, with distributed propulsion and a hybrid lift/thrust chain.
+
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.
  
−
The main SC-VTOL-02 topics relevant to Mini-Bee include:
+
This type of collaboration is important for Mini-Bee because certification requires several levels of expertise:
  
−
* VTOL-capable aircraft classification;
+
* aircraft architecture;
 +
* systems engineering;
 
* safety analysis;
 
* safety analysis;
−
* single failure prevention;
+
* regulatory interpretation;
−
* weight and occupant limits;
+
* electric and hybrid propulsion;
−
* lift/thrust system definition;
+
* rotorcraft certification logic;
−
* flight and safety recorders;
+
* documentation and traceability.
−
* high electrical power;
 
−
* EWIS considerations;
 
−
* interaction between propulsion, lift, thrust, and control systems.
 
  
−
For Mini-Bee, the complete hybrid chain must be considered as part of the '''lift/thrust system'''. This means that the certification logic must not only cover the propellers or rotors, but the full chain from energy storage and generation to the final thrust-producing elements.
+
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.
  
−
This includes, for example:
+
== Objective of the certification framework ==
  
−
* fuel reservoir;
+
The purpose of the certification framework is to define the regulatory environment in which Mini-Bee / RED VTOL could be positioned.
−
* thermal engine;
 
−
* generator or alternator;
 
−
* power electronics;
 
−
* electrical distribution;
 
−
* electric motors;
 
−
* rotors or propellers;
 
−
* control logic;
 
−
* degraded modes;
 
−
* safety monitoring.
 
  
−
[[File:MiniBee_Lift_Thrust_System_Chain.png|thumb|center|900px|'''Figure 5.''' Placeholder for a visual showing the complete Mini-Bee lift/thrust chain from energy source to distributed propellers.]]
+
The presentation has four main objectives:
  
−
== CS-27 Small Rotorcraft ==
+
{| 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'''
 +
| Anticipate the analyses, tests and demonstrations needed to support certification.
 +
|}
  
−
'''CS-27''' is the Certification Specification for Small Rotorcraft.
+
== Certification snapshot ==
  
−
For Mini-Bee / Red VTOL, CS-27 is used because the aircraft behaves, from a certification standpoint, like a small rotorcraft. The presence of multiple propellers or rotors does not automatically remove the aircraft from rotorcraft logic. Instead, the general behaviour, flight control logic, lift generation, and operational philosophy remain close to rotorcraft certification principles.
+
[[File:MiniBee_Certification_Three_Level_Logic.png|center|900px|Mini-Bee certification three-level logic]]
  
−
CS-27 provides requirements and acceptable means of compliance for small rotorcraft, including topics such as:
+
<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>
  
−
* structural design;
+
<br />
−
* flight characteristics;
 
−
* controllability;
 
−
* performance;
 
−
* powerplant installation;
 
−
* equipment;
 
−
* operating limitations;
 
−
* safety and airworthiness.
 
  
−
For Mini-Bee, CS-27 is therefore the baseline certification frame. However, because Mini-Bee includes VTOL-capable and hybrid propulsion features, CS-27 must be complemented by additional references.
+
{| 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
 +
|}
  
−
== CS-VLR Very Light Rotorcraft ==
+
== High Level — aircraft positioning ==
  
−
'''CS-VLR''' applies to very light rotorcraft.
+
The high-level framework defines the regulatory positioning of Mini-Bee / RED VTOL.
  
−
It may be useful as a reference only if the design enters its restrictive frame. Typical CS-VLR logic is associated with simple rotorcraft, very limited occupancy, and restricted operations.
+
The current logic is to consider the aircraft as:
  
−
For Mini-Bee / Red VTOL, CS-VLR may provide useful insights, but it should not be assumed as the main basis unless the aircraft fully matches its constraints.
+
* a '''small rotorcraft''' under '''CS-27''';
 +
* with '''VTOL-capable characteristics''' under '''SC-VTOL-02'''.
  
−
CS-VLR is relevant mainly as a comparison tool for:
+
This is the main certification idea of the presentation.
  
−
* simplicity of design;
+
CS-27 provides the small rotorcraft basis. 
−
* very light rotorcraft logic;
+
SC-VTOL-02 covers the specific aspects of VTOL-capable aircraft.
−
* low occupant count;
 
−
* restricted operations;
 
−
* possible design simplification.
 
  
−
== CS-29 Large Rotorcraft ==
+
[[File:MiniBee_CS27_SCVTOL_Positioning.png|center|900px|Mini-Bee CS-27 and SC-VTOL-02 positioning]]
  
−
'''CS-29''' applies to large rotorcraft.
+
<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>
  
−
Mini-Bee is not primarily positioned as a CS-29 aircraft. However, CS-29 remains important as a reference because some design characteristics can push a project toward higher certification expectations.
+
== Main EASA references ==
  
−
This may happen if the aircraft design includes:
+
EASA is the official European authority for aviation certification.
  
−
* higher weight;
+
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.
−
* higher occupant capacity;
 
−
* complex systems;
 
−
* multi-engine or complex power architecture;
 
−
* public transport operations;
 
−
* night operations;
 
−
* operations over water;
 
−
* advanced equipment;
 
−
* human factors requirements;
 
−
* safety requirements beyond the CS-27 baseline.
 
  
−
A candidate design under CS-27 may be required to comply with selected CS-29 specifications if some features exceed the boundaries of CS-27.
+
{| class="wikitable" style="width:100%;"
 +
! 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.
 +
|}
  
−
This is a major risk to be considered early in the design.
+
[[File:MiniBee_EASA_Reference_Map.png|center|900px|Mini-Bee EASA reference map]]
  
−
[[File:MiniBee_CS27_CS29_Boundary_Risk.png|thumb|center|900px|'''Figure 6.''' Placeholder for a visual showing the risk of moving from CS-27 logic toward CS-29 expectations when design complexity increases.]]
+
<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>
  
−
== Conclusion of the High Level framework ==
+
== System and sub-system logic ==
  
−
At High Level, Mini-Bee / Red VTOL should be treated as:
+
The medium-level framework translates the aircraft-level certification basis into system and sub-system references.
  
−
* a '''small rotorcraft''' under CS-27;
+
For Mini-Bee / RED VTOL, the main technical domains are:
−
* a '''VTOL-capable aircraft''' under SC-VTOL-02;
 
−
* a concept that may need selected CS-29 considerations if complexity, operations, or configuration exceed CS-27 expectations;
 
−
* a design that should only rely on CS-VLR if it fully fits the very light rotorcraft frame.
 
  
−
The main conclusion is that Mini-Bee must be designed with certification boundaries in mind from the beginning.
+
* engine;
 +
* electric and hybrid propulsion system;
 +
* propellers and rotors;
 +
* high-power electrical architecture;
 +
* lift / thrust system;
 +
* operational airworthiness;
 +
* emissions and fuel venting;
 +
* environmental constraints.
  
−
Only one non-compliant characteristic may be enough to move the aircraft into a higher or more demanding category. This may relate to mass, number of occupants, propulsion complexity, electrical architecture, operational use, or safety assumptions.
+
The important point is that Mini-Bee cannot be certified only as a list of independent components.
  
−
== Medium Level Certification Framework ==
+
The aircraft must be understood as an integrated system.
  
−
The '''Medium Level Certification Framework''' corresponds to the system and sub-system certification architecture.
+
In particular, the complete '''lift / thrust system''' must be considered as a chain from energy source to thrust production.
  
−
At this level, the question changes:
+
== Lift / thrust system chain ==
  
−
: '''Which certification texts apply to each technical domain of the aircraft?'''
+
The lift / thrust system is the core technical object of the Mini-Bee / RED VTOL certification study.
  
−
The aircraft-level framework must be translated into system-level references. This is where the broad certification strategy becomes a practical engineering map.
+
It includes:
  
−
For Mini-Bee / Red VTOL, the main system and sub-system references include:
+
{| class="wikitable" style="width:100%;"
−
 
+
! Chain element
−
* '''CS-E''' for engines;
+
! Certification attention point
−
* '''SC E-19''' for electric and hybrid propulsion systems;
+
|-
−
* '''CS-P''' for propellers;
+
| '''Fuel / battery'''
−
* '''CS-26''' for additional airworthiness specifications for operations;
+
| Energy availability, storage, safety and endurance.
−
* '''AMC-20''' for products, parts, and appliances;
+
|-
−
* '''CS-34''' for aircraft engine emissions and fuel venting;
+
| '''Engine'''
−
* '''CS-36''' for aircraft noise where applicable;
+
| Certified status, installation, operating limits and failure modes.
−
* '''CS-CO2''' for CO2 aspects where applicable;
+
|-
−
* selected EASA Certification Memoranda and consultation material.
+
| '''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.
 +
|}
  
−
[[File:MiniBee_Medium_Level_System_Map.png|thumb|center|900px|'''Figure 7.''' Medium Level certification map: engine, hybrid propulsion, propellers, electrical system, operations, emissions, and environmental references.]]
+
[[File:MiniBee_Lift_Thrust_System_Chain.png|center|900px|Mini-Bee lift thrust system chain]]
  
−
== CS-E Engines ==
+
<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>
  
−
'''CS-E''' defines certification specifications and acceptable means of compliance for engines.
+
== Certification risks ==
  
−
For Mini-Bee / Red VTOL, the thermal engine is part of the complete lift/thrust chain. It is therefore not only an isolated component. Its certification status, integration, operating limitations, failure modes, and interaction with the hybrid electrical system must be considered.
+
The presentation highlights several certification risks that must be controlled early.
  
−
A certified aeronautical engine may reduce certification effort, provided that:
+
{| class="wikitable" style="width:100%;"
−
 
+
! Risk
−
* the engine is used within its certified operating envelope;
+
! Why it matters
−
* installation effects are properly justified;
+
|-
−
* cooling, fuel, vibration, and control interfaces are demonstrated;
+
| '''CS-27 / SC-VTOL boundary'''
−
* the integration with the hybrid chain does not create unaddressed risks.
+
| Mini-Bee combines rotorcraft behaviour and VTOL-capable characteristics.
−
 
+
|-
−
If a non-certified or significantly modified engine is used, the certification burden becomes much higher.
+
| '''Possible CS-29 drift'''
−
 
+
| Mass, occupants, system complexity or operations may increase certification expectations.
−
For Mini-Bee, the engine must be analysed in relation with:
+
|-
−
 
+
| '''Hybrid propulsion'''
−
* CS-E;
+
| The complete energy and propulsion chain may become a safety-critical integrated system.
−
* SC E-19;
+
|-
−
* SC-VTOL-02;
+
| '''High electrical power'''
−
* CS-34;
+
| EWIS, EMC, power electronics and electrical safety must be justified.
−
* the full lift/thrust system logic.
+
|-
−
 
+
| '''Distributed lift'''
−
== SC E-19 Electric / Hybrid Propulsion System ==
+
| Failure cases and degraded modes must be clearly demonstrated.
−
 
+
|-
−
'''SC E-19''' is the special condition addressing electric and hybrid propulsion systems.
+
| '''VEMS mission'''
−
 
+
| Medical or public-service missions may create additional operational constraints.
−
It is highly relevant for Mini-Bee / Red VTOL because the aircraft concept includes a hybrid propulsion architecture. SC E-19 provides a structured certification reference for systems that combine energy conversion, electrical power, control, and propulsion functions.
+
|}
−
 
 
−
The key point is that the certification approach may consider the hybrid propulsion either as:
 
−
 
 
−
* an aircraft-level integrated system;
 
−
* an engine-like certification object;
 
−
* a set of interacting certified and non-certified components;
 
−
* or a dedicated system requiring its own means of compliance.
 
−
 
 
−
For Mini-Bee, this creates a major design question:
 
−
 
 
−
: '''Should the hybrid propulsion system be treated as a set of components, or as one integrated lift/thrust system?'''
 
−
 
 
−
From a safety perspective, the integrated-system approach appears more coherent because failures may propagate through electrical, mechanical, thermal, and control interfaces.
 
−
 
 
−
[[File:MiniBee_Electric_Hybrid_Propulsion_Certification.png|thumb|center|900px|'''Figure 8.''' Placeholder for a visual showing SC E-19 applied to the Mini-Bee hybrid propulsion architecture.]]
 
−
 
 
−
== CS-P Propellers ==
 
−
 
 
−
'''CS-P''' defines certification specifications and acceptable means of compliance for propellers.
 
−
 
 
−
For Mini-Bee / Red VTOL, propellers or rotors are part of the lift/thrust system. Their certification cannot be isolated from the aircraft architecture because they interact with:
 
−
 
 
−
* distributed lift;
 
−
* propulsion control;
 
−
* structural loads;
 
−
* vibration;
 
−
* redundancy;
 
−
* failure modes;
 
−
* noise;
 
−
* safety around rotating elements;
 
−
* energy management.
 
−
 
 
−
If certified propellers are available and compatible with the Mini-Bee design, their use may reduce certification uncertainty. If custom propellers are required, additional design justification and testing will be necessary.
 
−
 
 
−
== CS-26 Additional airworthiness specifications for operations ==
 
−
 
 
−
'''CS-26''' provides additional airworthiness specifications linked to certain operational conditions.
 
−
 
 
−
For Mini-Bee / Red VTOL, CS-26 may become relevant depending on the intended operational use, especially for:
 
−
 
 
−
* public transport;
 
−
* emergency medical service;
 
−
* water impact and ditching considerations;
 
−
* emergency equipment;
 
−
* fire extinguishers;
 
−
* operational safety requirements.
 
−
 
 
−
This is important because Mini-Bee / Red VTOL is associated with an ultra-light air ambulance concept. If the aircraft is intended for medical aid or public service missions, the operational certification expectations may become more demanding than a basic demonstrator configuration.
 
−
 
 
−
== AMC-20 Products, Parts and Appliances ==
 
−
 
 
−
'''AMC-20''' provides general acceptable means of compliance for airworthiness of products, parts, and appliances.
 
−
 
 
−
For Mini-Bee, AMC-20 is useful because it creates bridges between certification references. It helps connect product-level airworthiness with system-level and equipment-level certification expectations.
 
−
 
 
−
AMC-20 should be used as a supporting reference, especially for:
 
−
 
 
−
* equipment qualification;
 
−
* system installation;
 
−
* environmental qualification;
 
−
* electrical and electronic equipment;
 
−
* interfaces between certification domains;
 
−
* means of compliance selection.
 
−
 
 
−
== CS-34, CS-36 and CS-CO2 environmental references ==
 
−
 
 
−
'''CS-34''' relates to aircraft engine emissions and fuel venting.
 
−
'''CS-36''' relates to aircraft noise. 
 
−
'''CS-CO2''' relates to aircraft CO2 emissions where applicable.
 
−
 
 
−
For Mini-Bee / Red VTOL, environmental certification cannot be ignored. Even if the aircraft is small and hybrid, the use of a thermal engine, fuel system, and propulsive elements creates environmental compliance questions.
 
−
 
 
−
The key topics include:
 
−
 
 
−
* fuel venting;
 
−
* engine emissions;
 
−
* noise;
 
−
* environmental protection;
 
−
* possible future evolution of CO2-related requirements;
 
−
* alignment with ICAO Annex 16 principles.
 
−
 
 
−
Mini-Bee should therefore monitor future evolutions of these requirements, especially because hybrid aircraft and new air mobility vehicles may be subject to evolving environmental expectations.
 
−
 
 
−
[[File:MiniBee_Environmental_Certification_Map.png|thumb|right|450px|'''Figure 9.''' Placeholder for a visual showing environmental certification links: CS-34, CS-36, CS-CO2, fuel, emissions, and noise.]]
 
−
 
 
−
== Low Level Certification Framework ==
 
  
−
The '''Low Level Certification Framework''' is the level of concrete demonstration.
+
== Low Level — evidence and demonstration ==
  
−
At this level, the question becomes:
+
The low level is the level of concrete proof.
  
−
: '''Which evidence proves that each requirement is satisfied?'''
+
Certification is not based only on design intention. 
 +
It is based on evidence.
  
−
This is where the project moves from regulatory interpretation to engineering proof.
+
Typical evidence includes:
−
 
 
−
For Mini-Bee / Red VTOL, Low Level certification work should include:
 
  
 
* requirement allocation;
 
* requirement allocation;
−
* requirement traceability;
 
−
* design assumptions;
 
 
* safety analyses;
 
* safety analyses;
−
* functional hazard assessment;
+
* calculations;
−
* system safety assessment;
+
* system schematics;
−
* architecture justification;
 
−
* schematics;
 
−
* material files;
 
−
* control logic description;
 
 
* bench tests;
 
* bench tests;
−
* simulation reports;
+
* HIL / SIL simulations;
−
* HIL and SIL validation;
+
* inspection reports;
−
* electrical safety evidence;
+
* environmental qualification;
−
* EWIS analysis;
 
−
* electromagnetic compatibility assessment;
 
−
* mechanical tests;
 
−
* environmental tests;
 
−
* inspection procedures;
 
 
* flight test preparation;
 
* flight test preparation;
 
* flight test reports;
 
* flight test reports;
−
* degraded mode demonstrations.
+
* compliance documentation.
  
−
[[File:MiniBee_Low_Level_Evidence_Matrix.png|thumb|center|900px|'''Figure 10.''' Placeholder for a Low Level evidence matrix linking requirements to analysis, test, inspection, simulation, and demonstration.]]
+
The purpose of this work is to connect each certification requirement to a verifiable means of compliance.
  
−
The Low Level is essential because certification is not granted on the basis of concept quality alone. It requires traceable and verifiable evidence.
+
This can include:
  
−
Each requirement must be connected to a means of compliance, such as:
+
{| class="wikitable" style="width:100%; text-align:center;"
−
 
+
! Analysis
−
* analysis;
+
! Test
−
* calculation;
+
! Simulation
−
* test;
+
! Inspection
−
* inspection;
+
! Demonstration
−
* demonstration;
+
|-
−
* similarity;
+
| Safety studies
−
* simulation;
+
| Bench tests
−
* qualification;
+
| HIL / SIL
−
* operational limitation.
+
| Installation checks
−
 
+
| Flight evidence
−
== Flight test and DOARI considerations ==
+
|}
−
 
 
−
The presentation refers to '''DOARI 2021-01 Consultation''' regarding the competence of flight test crew involved in VTOL flight test activities.
 
−
 
 
−
This document is no longer valid and should only be considered for its principles. However, it remains useful to understand the type of questions raised by VTOL flight testing.
 
−
 
 
−
The main principles retained for Mini-Bee / Red VTOL are:
 
  
−
* flight test operations must be prepared early;
+
== Certification pathway logic ==
−
* the aircraft should be designed to fit the certification frame as much as possible;
 
−
* VTOL-capable aircraft may be assimilated to CS-27 rotorcraft for technical specifications;
 
−
* handling qualities, controls, and performances should remain coherent with rotorcraft expectations;
 
−
* pilot licensing and training considerations must influence design philosophy;
 
−
* the project should avoid creating unnecessary gaps with existing flight crew categories.
 
  
−
This means that certification thinking must influence not only the aircraft hardware, but also the way the aircraft is controlled, tested, trained, and operated.
+
The certification pathway should be progressive.
  
−
== Parachute and recovery systems ==
+
It should move from regulatory positioning to detailed evidence:
  
−
The presentation also highlights the question of parachutes and recovery systems.
+
{| class="wikitable" style="width:100%; text-align:center;"
−
 
+
! Step 1
−
EASA FAQ material indicates that personnel parachutes within the scope of EASA are mainly emergency parachutes for glider and aerobatic pilots, while other parachute types may fall under Member State responsibility.
+
! Step 2
−
 
+
! Step 3
−
For Mini-Bee / Red VTOL, this means that a parachute or ballistic recovery system should not automatically be assumed as an accepted means of compliance for a lift/thrust failure.
+
! Step 4
−
 
+
! Step 5
−
This point requires further analysis.
 
−
 
 
−
A recovery system may be useful from a safety perspective, but it must be demonstrated within the applicable certification framework. It cannot replace the need to show robustness of the lift/thrust system, degraded modes, redundancy, and controllability.
 
−
 
 
−
[[File:MiniBee_Recovery_System_Certification_Question.png|thumb|center|900px|'''Figure 11.''' Placeholder for a visual showing the certification question around parachute or recovery systems for VTOL aircraft.]]
 
−
 
 
−
== Rulemaking maturity and VTOL evolution ==
 
−
 
 
−
The certification framework for VTOL-capable aircraft is still evolving.
 
−
 
 
−
EASA symposiums, rulemaking tasks, notices of proposed amendment, and consultation documents show that the authority is progressively building the certification approach for new air mobility and VTOL-capable aircraft.
 
−
 
 
−
Important evolution topics include:
 
−
 
 
−
* VTOL means of compliance;
 
−
* human factors;
 
−
* flight envelopes;
 
−
* energy reserve;
 
−
* ditching and emergency flotation;
 
−
* doors and landing gear;
 
−
* design loads;
 
−
* structural durability;
 
−
* fire protection;
 
−
* U-space;
 
−
* artificial intelligence;
 
−
* pilot training;
 
−
* licensing;
 
−
* integration into air transport operations.
 
−
 
 
−
For Mini-Bee / Red VTOL, this means that the certification framework should be treated as a living reference. The design should remain adaptable to future updates of SC-VTOL, AMC, GM, and related EASA material.
 
−
 
 
−
== Air transport and VEMS use case ==
 
−
 
 
−
Mini-Bee / Red VTOL is linked to the concept of an ultra-light air ambulance.
 
−
 
 
−
The EASA material on air transport by VTOL-capable aircraft identifies several possible use cases, including:
 
−
 
 
−
* urban passenger services;
 
−
* regional passenger services;
 
−
* VEMS services;
 
−
* sightseeing flights.
 
−
 
 
−
For Mini-Bee, the VEMS angle is particularly relevant. However, medical aid missions can introduce additional constraints because they may involve:
 
−
 
 
−
* public service operations;
 
−
* patient transport;
 
−
* specific equipment;
 
−
* reliability requirements;
 
−
* mission availability;
 
−
* emergency landing considerations;
 
−
* operational approval;
 
−
* crew training;
 
−
* safety procedures.
 
−
 
 
−
The certification framework must therefore remain connected to the intended mission of the aircraft.
 
−
 
 
−
[[File:MiniBee_VEMS_Mission_Certification.png|thumb|center|900px|'''Figure 12.''' Placeholder for a visual showing Mini-Bee as a VTOL emergency medical service concept within certification constraints.]]
 
−
 
 
−
== Summary table ==
 
−
 
 
−
{| class="wikitable"
 
−
! Level
 
−
! Purpose
 
−
! Main question
 
−
! Main references
 
−
! Output
 
−
|-
 
−
| '''High Level'''
 
−
| Define the certification positioning
 
−
| Which aircraft category and framework apply?
 
−
| CS-27, SC-VTOL-02, CS-29, CS-VLR
 
−
| Certification basis and philosophy
 
−
|-
 
−
| '''Medium Level'''
 
−
| Map system and sub-system requirements
 
−
| Which rules apply to each technical domain?
 
−
| CS-E, SC E-19, CS-P, CS-26, AMC-20, CS-34
 
−
| System certification architecture
 
 
|-
 
|-
−
| '''Low Level'''
+
| Aircraft classification
−
| Produce compliance evidence
+
| Applicable rules
−
| Which proof demonstrates compliance?
+
| System allocation
−
| AMC, GM, tests, analysis, simulations, inspections
+
| Evidence production
−
| Traceable evidence files
+
| Testing and approval
 
|}
 
|}
  
−
== Main certification risks ==
+
The presentation therefore supports a structured development logic:
  
−
The main certification risks for Mini-Bee / Red VTOL are:
+
* 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.
  
−
* unclear boundary between rotorcraft and VTOL-capable aircraft;
+
== What this work brings to the project ==
−
* design moving outside CS-27 assumptions;
 
−
* hybrid propulsion treated as an integrated safety-critical system;
 
−
* high-power electrical architecture requiring specific evidence;
 
−
* distributed lift creating complex failure cases;
 
−
* lack of accepted means of compliance for some innovative features;
 
−
* operational use leading to additional requirements;
 
−
* environmental and noise requirements evolving before certification;
 
−
* flight test and licensing assumptions not aligned with existing categories.
 
  
−
These risks do not block the project. They define the areas where early engineering discipline is required.
+
The RED VTOL / ALTEN Solidaire certification work brings structure to the Mini-Bee project.
  
−
== Conclusion ==
+
It helps the project move from a conceptual aircraft architecture to a more credible engineering path.
  
−
Mini-Bee / Red VTOL should currently be considered as a '''small rotorcraft with VTOL-capable characteristics'''.
+
The main benefits are:
  
−
Its design should therefore comply with '''CS-27''' as the main rotorcraft basis and '''SC-VTOL-02''' for the specific VTOL-capable aspects. Additional references such as CS-29, CS-VLR, CS-E, SC E-19, CS-P, CS-26, AMC-20, and CS-34 must be used to structure the system-level and sub-system-level certification approach.
+
* 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.
  
−
The most important point is that certification must be integrated into the design process from the beginning.
+
== Conclusion ==
  
−
For Mini-Bee / Red VTOL, the certification framework is not only a regulatory checklist. It is a design management tool. It helps define the aircraft category, orient technical decisions, identify missing evidence, manage risks, prepare authority discussions, and progressively transform an innovative VTOL concept into a certifiable aircraft project.
+
Mini-Bee / RED VTOL should currently be considered as a '''small rotorcraft with VTOL-capable characteristics'''.
  
−
[[File:MiniBee_Certification_Pathway.png|thumb|center|900px|'''Figure 13.''' Placeholder for a final pathway visual: from concept to certification basis, system compliance map, evidence matrix, testing, and operational approval.]]
+
The most credible certification logic is based on:
  
−
== Glossary ==
+
* '''CS-27''' as the small rotorcraft basis;
−
 
+
* '''SC-VTOL-02''' for VTOL-capable aspects;
−
{| class="wikitable"
+
* '''SC E-19''' for electric and hybrid propulsion;
−
! Acronym
+
* '''CS-E''' for engines;
−
! Meaning
+
* '''CS-P''' for propellers;
−
|-
+
* additional references such as CS-26, AMC-20, CS-34, CS-VLR and CS-29 when relevant.
−
| AC
 
−
| Advisory Circular
 
−
|-
 
−
| AMC
 
−
| Acceptable Means of Compliance
 
−
|-
 
−
| ATS
 
−
| Air Traffic Service
 
−
|-
 
−
| CAEP
 
−
| Committee on Aviation Environmental Protection
 
−
|-
 
−
| CM
 
−
| Certification Memorandum
 
−
|-
 
−
| CS
 
−
| Certification Specifications
 
−
|-
 
−
| DOA
 
−
| Design Organisation Approval
 
−
|-
 
−
| DOARI
 
−
| DOA Review Item
 
−
|-
 
−
| EASA
 
−
| European Union Aviation Safety Agency
 
−
|-
 
−
| ED
 
−
| EASA Decision
 
−
|-
 
−
| EHPS
 
−
| Electric / Hybrid Propulsion System
 
−
|-
 
−
| ETSO
 
−
| European Technical Standard Order
 
−
|-
 
−
| EWIS
 
−
| Electrical Wiring Interconnection System
 
−
|-
 
−
| FAA
 
−
| Federal Aviation Administration
 
−
|-
 
−
| GM
 
−
| Guidance Material
 
−
|-
 
−
| ICAO
 
−
| International Civil Aviation Organization
 
−
|-
 
−
| MoC
 
−
| Means of Compliance
 
−
|-
 
−
| NAM
 
−
| New Air Mobility
 
−
|-
 
−
| NPA
 
−
| Notice of Proposed Amendment
 
−
|-
 
−
| PAX
 
−
| Passenger
 
−
|-
 
−
| RMT
 
−
| Rulemaking Task
 
−
|-
 
−
| SARP
 
−
| Standards and Recommended Practices
 
−
|-
 
−
| SC
 
−
| Special Condition
 
−
|-
 
−
| TCDS
 
−
| Type Certificate Data Sheet
 
−
|-
 
−
| TLD
 
−
| Time Limited Dispatch
 
−
|-
 
−
| ToR
 
−
| Terms of Reference
 
−
|-
 
−
| TRL
 
−
| Technology Readiness Level
 
−
|-
 
−
| VEMS
 
−
| VTOL Emergency Medical Service
 
−
|-
 
−
| VLR
 
−
| Very Light Rotorcraft
 
−
|-
 
−
| VTOL
 
−
| Vertical Take-Off and Landing
 
−
|-
 
−
| WG
 
−
| Working Group
 
−
|}
 
  
−
== Suggested visuals to create ==
+
The certification framework is not only a regulatory checklist. 
 +
It is a design management tool.
  
−
The following visuals can be created later and inserted into the page:
+
For Mini-Bee / RED VTOL, it helps transform an innovative hybrid VTOL concept into a structured, traceable and progressively certifiable aircraft project.
−
 
 
−
{| class="wikitable"
 
−
! File name
 
−
! Purpose
 
−
! Suggested content
 
−
|-
 
−
| MiniBee_VTOL_Certification_Framework_Cover.png
 
−
| Cover visual
 
−
| Mini-Bee aircraft, EASA framework, certification pathway
 
−
|-
 
−
| MiniBee_Certification_Objectives.png
 
−
| Explain the page objective
 
−
| Classification, rules, maturity, evidence
 
−
|-
 
−
| MiniBee_High_Level_Certification_Map.png
 
−
| High Level view
 
−
| CS-27, SC-VTOL-02, CS-29, CS-VLR around Mini-Bee
 
−
|-
 
−
| MiniBee_CS27_SCVTOL_Positioning.png
 
−
| Aircraft positioning
 
−
| Mini-Bee between rotorcraft and VTOL-capable categories
 
−
|-
 
−
| MiniBee_Lift_Thrust_System_Chain.png
 
−
| Technical chain
 
−
| Fuel, engine, generator, power electronics, motors, propellers
 
−
|-
 
−
| MiniBee_CS27_CS29_Boundary_Risk.png
 
−
| Certification risk
 
−
| Design features that may push toward CS-29
 
−
|-
 
−
| MiniBee_Medium_Level_System_Map.png
 
−
| Medium Level view
 
−
| System/sub-system certification map
 
−
|-
 
−
| MiniBee_Electric_Hybrid_Propulsion_Certification.png
 
−
| Hybrid propulsion
 
−
| SC E-19 applied to Mini-Bee
 
−
|-
 
−
| MiniBee_Environmental_Certification_Map.png
 
−
| Environmental references
 
−
| CS-34, CS-36, CS-CO2
 
−
|-
 
−
| MiniBee_Low_Level_Evidence_Matrix.png
 
−
| Low Level view
 
−
| Requirements linked to tests, analysis, inspection, simulation
 
−
|-
 
−
| MiniBee_Recovery_System_Certification_Question.png
 
−
| Safety recovery question
 
−
| Parachute / recovery system versus certification evidence
 
−
|-
 
−
| MiniBee_VEMS_Mission_Certification.png
 
−
| Mission use case
 
−
| Mini-Bee as VTOL emergency medical service aircraft
 
−
|-
 
−
| MiniBee_Certification_Pathway.png
 
−
| Final synthesis
 
−
| Concept → certification basis → compliance map → evidence → testing
 
−
|}
 
  
−
== See also ==
+
== Useful links ==
  
 +
* [[File:20260422_RedVTOL_EASA_Certification_01_High_Level_Framework_v2_en.pptx|Download the PowerPoint presentation]]
 
* [[Mini-Bee]]
 
* [[Mini-Bee]]
 
* [[Minibee_TRL3]]
 
* [[Minibee_TRL3]]
−
* [[RED VTOL]]
+
* [[RED VTOL ONG]]
−
* [[EASA]]
 
−
* [[CS-27]]
 
−
* [[SC-VTOL-02]]
 
−
* [[Hybrid Propulsion]]
 
−
* [[VTOL Emergency Medical Service]]
 

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.


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.

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.

Useful links

Retrieved from "https://wiki.collaborativebee.com//index.php?title=Certification_FrameWork_VTOL&oldid=1999"