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 =
  
[[File:20260422_RedVTOL_EASA_Certification_01_High_Level_Framework_v2_en.pptx|thumb|center|900px|'''Download the full presentation''' — Red VTOL / Mini-Bee EASA Certification Framework]]
+
'''Mini-Bee / Red VTOL — EASA Certification Framework'''
  
The '''VTOL Certification Framework''' defines how a vertical take-off and landing aircraft can be designed, justified, tested, and accepted by the aviation authority.
+
The '''VTOL Certification Framework''' defines how a vertical take-off and landing aircraft can be designed, justified, tested and progressively accepted by the aviation authority.
  
For a project such as '''Mini-Bee / Red VTOL''', certification is not only a regulatory topic. It is a design driver. The aircraft must not only fly. It must also follow a credible path toward safety demonstration, technical compliance, and operational approval.
+
For '''Mini-Bee / Red VTOL''', certification is not only a regulatory constraint.
 +
It is a design driver.
  
In Europe, this framework is based on '''EASA''' — the European Union Aviation Safety Agency. EASA provides the official certification specifications, special conditions, acceptable means of compliance, guidance material, and rulemaking documents used for aircraft certification.
+
The objective is to position the aircraft inside the EASA certification environment and to identify the main rules that will guide the future technical demonstration.
  
[[File:MiniBee_VTOL_Certification_Framework_Overview.png|thumb|center|900px|'''Figure 1.''' Overview of the Mini-Bee / Red VTOL certification framework.]]
+
[[File:MiniBee_VTOL_Certification_Framework_Overview.png|thumb|center|900px|'''Mini-Bee / Red VTOL certification framework overview'''<br />Placeholder visual showing the aircraft, EASA, CS-27, SC-VTOL-02 and the certification pathway.]]
  
== Objective ==
+
== Quick project summary ==
  
The objective of this page is to summarize the certification logic presented in the document:
+
{| class="wikitable"
 +
! Item
 +
! Description
 +
|-
 +
| '''Project'''
 +
| Mini-Bee / Red VTOL
 +
|-
 +
| '''Aircraft type'''
 +
| 2PAX hybrid VTOL multicopter
 +
|-
 +
| '''Mission orientation'''
 +
| Ultra-light air ambulance / VEMS concept
 +
|-
 +
| '''Certification topic'''
 +
| EASA VTOL Certification Framework
 +
|-
 +
| '''Main aircraft basis'''
 +
| CS-27 Small Rotorcraft
 +
|-
 +
| '''VTOL-specific basis'''
 +
| SC-VTOL-02 Small-Category VTOL-Capable Aircraft
 +
|-
 +
| '''Key challenge'''
 +
| Demonstrate that the aircraft can follow a credible path toward certification, safety and operational approval
 +
|}
 +
 
 +
== Main presentation ==
 +
 
 +
The main document supporting this page is the PowerPoint presentation:
 +
 
 +
: '''Red VTOL TRL4 — 2PAX VTOL hybrid multicopter — Ultra light air ambulance — EASA Certification Framework'''
 +
 
 +
{| class="wikitable"
 +
! Document
 +
! Description
 +
|-
 +
| [[File:20260422_RedVTOL_EASA_Certification_01_High_Level_Framework_v2_en.pptx|Download the PowerPoint presentation]]
 +
| High level certification framework for Mini-Bee / Red VTOL, including EASA references, CS-27, SC-VTOL-02, CS-VLR, CS-29, system and sub-system certification references, environmental topics, official links and glossary.
 +
|}
 +
 
 +
[[File:MiniBee_EASA_Presentation_Extract.png|thumb|center|900px|'''Presentation overview'''<br />Placeholder visual to be created from the first slide or from a graphical synthesis of the PowerPoint.]]
 +
 
 +
== Visual introduction ==
 +
 
 +
<gallery mode="packed" heights="220px">
 +
File:MiniBee_High_Level_Certification_Map.png|'''High level framework'''<br />CS-27, SC-VTOL-02, CS-29 and CS-VLR positioning.
 +
File:MiniBee_Lift_Thrust_System_Chain.png|'''Lift / thrust system'''<br />Hybrid chain from energy source to distributed propellers.
 +
File:MiniBee_Low_Level_Evidence_Matrix.png|'''Compliance evidence'''<br />Requirements, analyses, tests, inspections and demonstrations.
 +
</gallery>
 +
 
 +
== Project overview ==
 +
 
 +
The Mini-Bee / Red VTOL concept is a hybrid VTOL aircraft project based on a distributed lift architecture.
  
'''Red VTOL TRL4 — 2PAX VTOL hybrid multicopter — Ultra light air ambulance — EASA Certification Framework'''
+
From a certification point of view, the aircraft must be treated carefully because it is not a conventional helicopter and not a conventional aeroplane. It combines rotorcraft behaviour with VTOL-capable characteristics.
  
The presentation identifies the main regulatory references that may apply to Mini-Bee / Red VTOL and explains how the project can be positioned inside the EASA certification environment.
+
The current certification logic is therefore based on two main references:
  
The main objectives are:
+
* '''CS-27 Small Rotorcraft''' for the rotorcraft basis;
 +
* '''SC-VTOL-02''' for VTOL-capable specific aspects.
  
* define the certification framework of the concept;
+
This dual approach helps structure the project without ignoring the innovative features of the aircraft.
* identify the main texts that orient the design;
 
* anticipate the certification process;
 
* analyse the maturity of the VTOL-capable aircraft regulation;
 
* prepare future technical demonstration and compliance activities.
 
  
 
== High Level Certification Framework ==
 
== High Level Certification Framework ==
  
At high level, the main question is:
+
The high level framework answers one main question:
  
: '''Where does Mini-Bee / Red VTOL fit inside the EASA certification framework?'''
+
: '''Where does Mini-Bee / Red VTOL fit inside the EASA certification environment?'''
  
The current logic is to consider Mini-Bee as:
+
The current positioning is:
  
* a '''small rotorcraft''' under '''CS-27''';
+
{| class="wikitable"
* with '''VTOL-capable characteristics''' under '''SC-VTOL-02'''.
+
! Reference
 +
! Role
 +
|-
 +
| '''CS-27'''
 +
| Main basis for small rotorcraft certification.
 +
|-
 +
| '''SC-VTOL-02'''
 +
| Complementary framework for VTOL-capable characteristics.
 +
|-
 +
| '''CS-VLR'''
 +
| Possible reference only if the aircraft fits very light rotorcraft restrictions.
 +
|-
 +
| '''CS-29'''
 +
| Reference for complex rotorcraft aspects or if the design exits CS-27 boundaries.
 +
|}
 +
 
 +
[[File:MiniBee_CS27_SCVTOL_Positioning.png|thumb|right|420px|'''Certification positioning'''<br />Mini-Bee between small rotorcraft logic and VTOL-capable aircraft logic.]]
 +
 
 +
At this level, the key point is to avoid a late reclassification risk.
 +
 
 +
A design initially considered under CS-27 may be pushed toward more demanding expectations if it exceeds boundaries related to mass, occupants, complexity, power architecture, operating mode or public transport use.
 +
 
 +
== EASA as official source ==
  
This means that the design should be oriented around both references:
+
EASA is the official European authority for aviation safety and certification.
  
* '''CS-27 Small Rotorcraft''';
+
For Mini-Bee / Red VTOL, every certification reference must be checked from official EASA sources:
* '''SC-VTOL-02 Small-Category VTOL-Capable Aircraft'''.
 
  
CS-27 provides the rotorcraft basis. 
+
* certification specifications;
SC-VTOL-02 adds the specific requirements linked to VTOL-capable aircraft, distributed lift, hybrid propulsion, high electrical power, and lift/thrust system safety.
+
* special conditions;
 +
* acceptable means of compliance;
 +
* guidance material;
 +
* rulemaking tasks;
 +
* consultation documents;
 +
* easy access rules;
 +
* official FAQs and product lists.
  
[[File:MiniBee_High_Level_Certification_Map.png|thumb|center|900px|'''Figure 2.''' High level certification positioning: CS-27, SC-VTOL-02, CS-29 and CS-VLR.]]
+
This is important because certification work must rely on validated texts, with clear issue dates and amendment levels.
  
 
== Main EASA references ==
 
== Main EASA references ==
 
The presentation identifies several EASA references that structure the certification approach.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
 
! Reference
 
! Reference
! Role for Mini-Bee / Red VTOL
+
! Main use for Mini-Bee / Red VTOL
 
|-
 
|-
 
| '''CS-27'''
 
| '''CS-27'''
| Main basis for small rotorcraft certification.
+
| Small rotorcraft certification basis.
 
|-
 
|-
 
| '''SC-VTOL-02'''
 
| '''SC-VTOL-02'''
| Special condition for small VTOL-capable aircraft.
+
| VTOL-capable aircraft specific requirements.
 
|-
 
|-
 
| '''CS-VLR'''
 
| '''CS-VLR'''
| Possible reference for very light rotorcraft, only if the design fits its restrictions.
+
| Very light rotorcraft reference, under strict limitations.
 
|-
 
|-
 
| '''CS-29'''
 
| '''CS-29'''
| Reference for large rotorcraft and complex design aspects.
+
| Large rotorcraft reference for complex or higher-category aspects.
 
|-
 
|-
 
| '''CS-E'''
 
| '''CS-E'''
| Certification specifications for engines.
+
| Engine certification.
 
|-
 
|-
 
| '''SC E-19'''
 
| '''SC E-19'''
| Special condition for electric and hybrid propulsion systems.
+
| Electric and hybrid propulsion system certification.
 
|-
 
|-
 
| '''CS-P'''
 
| '''CS-P'''
| Certification specifications for propellers.
+
| Propeller certification.
 
|-
 
|-
 
| '''CS-26'''
 
| '''CS-26'''
Line 81: Line 156:
 
|-
 
|-
 
| '''AMC-20'''
 
| '''AMC-20'''
| Acceptable means of compliance for products, parts and appliances.
+
| Products, parts and appliances.
 
|-
 
|-
 
| '''CS-34'''
 
| '''CS-34'''
Line 87: Line 162:
 
|}
 
|}
  
== System and Sub-System Certification Framework ==
+
== System and sub-system framework ==
  
The medium level of the framework concerns the main systems and sub-systems of the aircraft.
+
The medium level framework links the aircraft-level certification basis to each major technical domain.
  
For Mini-Bee / Red VTOL, this includes:
+
For Mini-Bee / Red VTOL, the most important domains are:
  
* the engine;
+
* thermal engine;
* the electric or hybrid propulsion system;
+
* electric and hybrid propulsion system;
* the propellers or rotors;
+
* propellers or rotors;
* the high-power electrical architecture;
+
* high-power electrical architecture;
* the lift/thrust chain;
+
* distributed lift system;
* operational airworthiness topics;
+
* operational airworthiness;
* emissions and environmental constraints.
+
* emissions and fuel venting;
 +
* noise and environmental constraints.
  
The key point is that Mini-Bee cannot be certified only as a set of separate components.
+
[[File:MiniBee_Medium_Level_System_Map.png|thumb|center|900px|'''System and sub-system certification map'''<br />Placeholder visual showing CS-E, SC E-19, CS-P, CS-26, AMC-20 and CS-34 around the Mini-Bee architecture.]]
The complete '''lift/thrust system''' must be considered as an integrated chain.
 
  
This chain includes:
+
The main technical point is the definition of the complete '''lift / thrust system'''.
  
* energy source;
+
For Mini-Bee, this system should include the complete chain:
* thermal engine;
 
* electrical generation;
 
* power electronics;
 
* electric motors;
 
* distributed propellers or rotors;
 
* control logic;
 
* failure modes and degraded operation.
 
  
[[File:MiniBee_Lift_Thrust_System_Chain.png|thumb|center|900px|'''Figure 3.''' Placeholder visual: complete Mini-Bee lift/thrust chain.]]
+
{| class="wikitable"
 +
! Chain element
 +
! Certification attention point
 +
|-
 +
| Fuel / energy source
 +
| Safety, storage, venting, endurance and environmental constraints.
 +
|-
 +
| Thermal engine
 +
| CS-E, installation, operating limits and integration.
 +
|-
 +
| Electrical generation
 +
| Power conversion, reliability and degraded modes.
 +
|-
 +
| Power electronics
 +
| Thermal control, electrical safety and EMC.
 +
|-
 +
| Electric motors
 +
| Redundancy, failure cases and thrust control.
 +
|-
 +
| Propellers / rotors
 +
| CS-P, loads, vibration, safety and noise.
 +
|-
 +
| Flight control logic
 +
| Command, monitoring, degraded modes and safety analysis.
 +
|}
  
== Low Level Demonstration ==
+
== Low Level demonstration ==
  
The low level corresponds to the concrete demonstration of compliance.
+
The low level framework is the level of evidence.
  
At this stage, the project must produce technical evidence. Each requirement must be linked to a means of compliance.
+
At this stage, the project must demonstrate that each requirement is satisfied through traceable proof.
  
Typical evidence may include:
+
Typical evidence includes:
  
 
* analyses;
 
* analyses;
 
* calculations;
 
* calculations;
* safety studies;
+
* simulations;
 +
* safety assessments;
 
* system schematics;
 
* system schematics;
* simulations;
 
 
* bench tests;
 
* bench tests;
 
* HIL / SIL tests;
 
* HIL / SIL tests;
* inspection procedures;
+
* inspections;
 +
* qualification reports;
 
* flight test preparation;
 
* flight test preparation;
* test reports.
+
* flight test reports.
  
This level is essential because certification is not based only on a concept. It is based on traceable proof.
+
[[File:MiniBee_Low_Level_Evidence_Matrix.png|thumb|center|900px|'''Low level evidence matrix'''<br />Placeholder visual showing the link between requirements, means of compliance and project deliverables.]]
  
[[File:MiniBee_Low_Level_Evidence_Matrix.png|thumb|center|900px|'''Figure 4.''' Placeholder visual: requirements linked to analyses, tests, inspections and demonstrations.]]
+
This level is essential because certification is not based on intention.
 +
It is based on documented, verifiable and reviewable evidence.
  
== Key certification risks ==
+
== Main certification risks ==
  
The main risks identified for Mini-Bee / Red VTOL are:
+
{| class="wikitable"
 +
! Risk
 +
! Why it matters
 +
|-
 +
| '''Boundary between CS-27 and SC-VTOL'''
 +
| Mini-Bee combines rotorcraft behaviour and VTOL-capable characteristics.
 +
|-
 +
| '''Possible move toward CS-29 expectations'''
 +
| Complexity, mass, occupants or operations may increase the certification burden.
 +
|-
 +
| '''Hybrid propulsion'''
 +
| The propulsion chain may need to be treated as an integrated safety-critical system.
 +
|-
 +
| '''High electrical power'''
 +
| Electrical architecture, EWIS and EMC require specific attention.
 +
|-
 +
| '''Distributed lift'''
 +
| Failure modes and degraded operation must be clearly demonstrated.
 +
|-
 +
| '''VEMS / medical mission'''
 +
| Emergency medical use may introduce additional operational constraints.
 +
|}
  
* unclear boundary between rotorcraft and VTOL-capable aircraft;
+
== Certification maturity logic ==
* possible movement from CS-27 toward CS-29 if the design becomes too complex;
 
* certification of the hybrid propulsion system;
 
* high electrical power requirements;
 
* distributed lift safety demonstration;
 
* lack of mature means of compliance for some VTOL technologies;
 
* operational requirements linked to air ambulance or public service missions.
 
  
These risks do not block the project. They define the topics that must be treated early in the design process.
+
The certification framework for VTOL-capable aircraft is still evolving.
  
== Conclusion ==
+
Mini-Bee / Red VTOL should therefore keep a living certification watch on:
  
Mini-Bee / Red VTOL should currently be considered as a '''small rotorcraft with VTOL-capable characteristics'''.
+
* SC-VTOL updates;
 +
* new means of compliance;
 +
* EASA Rotorcraft and VTOL Safety Symposium outputs;
 +
* electric and hybrid propulsion guidance;
 +
* environmental rules;
 +
* operational rules for VTOL-capable aircraft;
 +
* pilot training and licensing evolutions.
  
The most credible certification logic is therefore based on:
+
This point is important for the transition toward a stronger demonstrator phase.
  
* '''CS-27''' as the small rotorcraft basis;
+
== What the presentation clarified ==
* '''SC-VTOL-02''' for the VTOL-capable specific aspects;
+
 
* '''SC E-19''' for hybrid propulsion;
+
The PowerPoint presentation clarified several key points:
* additional references such as CS-E, CS-P, CS-26, AMC-20, CS-34, CS-VLR and CS-29 when relevant.
+
 
 +
{| class="wikitable"
 +
! Topic
 +
! Clarification
 +
|-
 +
| '''Aircraft classification'''
 +
| Mini-Bee can be considered as a small rotorcraft with VTOL-capable characteristics.
 +
|-
 +
| '''Main certification basis'''
 +
| CS-27 should be used as the main rotorcraft basis.
 +
|-
 +
| '''VTOL complement'''
 +
| SC-VTOL-02 is needed for specific VTOL-capable features.
 +
|-
 +
| '''System certification'''
 +
| Engine, hybrid propulsion, propellers and electrical systems require dedicated references.
 +
|-
 +
| '''Design risk'''
 +
| The project must avoid unintentionally exiting the CS-27 frame.
 +
|-
 +
| '''Future work'''
 +
| Each certification text must be analysed in detail to deduce constraints and design options.
 +
|}
  
The certification framework is not only a compliance checklist. 
+
== Questions to solve before a future certification phase ==
It is a design management tool.
 
  
It helps structure the project, identify design constraints, prepare evidence, and build a credible path toward future certification.
+
Before moving toward a more advanced certification phase, several questions must be clarified:
  
[[File:MiniBee_Certification_Pathway.png|thumb|center|900px|'''Figure 5.''' Placeholder visual: Mini-Bee certification pathway from concept to compliance demonstration.]]
+
* What is the final certified mass target?
 +
* What is the final occupant configuration?
 +
* Which parts of the hybrid propulsion chain can rely on certified components?
 +
* How should the integrated lift / thrust system be demonstrated?
 +
* Which degraded modes must be demonstrated?
 +
* What operational category should be targeted?
 +
* How far should the VEMS mission be included in the first certification logic?
 +
* Which EASA discussions or consultations should the project enter?
  
== Download ==
+
== Suggested visuals to create ==
  
* [[File:20260422_RedVTOL_EASA_Certification_01_High_Level_Framework_v2_en.pptx|Download the full PowerPoint presentation]]
+
{| class="wikitable"
 +
! Visual
 +
! Purpose
 +
|-
 +
| '''MiniBee_VTOL_Certification_Framework_Overview.png'''
 +
| Global cover visual for the page.
 +
|-
 +
| '''MiniBee_High_Level_Certification_Map.png'''
 +
| Show CS-27, SC-VTOL-02, CS-29 and CS-VLR around Mini-Bee.
 +
|-
 +
| '''MiniBee_CS27_SCVTOL_Positioning.png'''
 +
| Explain the dual positioning: rotorcraft basis + VTOL-capable complement.
 +
|-
 +
| '''MiniBee_Lift_Thrust_System_Chain.png'''
 +
| Show the complete hybrid chain from fuel to propellers.
 +
|-
 +
| '''MiniBee_Medium_Level_System_Map.png'''
 +
| Map systems and sub-systems to certification references.
 +
|-
 +
| '''MiniBee_Low_Level_Evidence_Matrix.png'''
 +
| Show requirements linked to evidence and means of compliance.
 +
|-
 +
| '''MiniBee_Certification_Pathway.png'''
 +
| Final synthesis visual: concept → framework → compliance → tests → approval.
 +
|}
  
== 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 ONG]]
+
* [[RED VTOL]]
 +
* [[CS-27]]
 +
* [[SC-VTOL-02]]
 +
* [[Hybrid Propulsion]]
 +
 
 +
== Why this framework matters ==
 +
 
 +
The VTOL Certification Framework is essential because Mini-Bee / Red VTOL cannot be assessed only through performance or innovation.
 +
 
 +
The aircraft must also be understandable, justifiable and demonstrable from a certification point of view.
 +
 
 +
This framework helps the project move from an innovative VTOL concept toward a structured, traceable and credible aircraft development path.
 +
 
 +
[[File:MiniBee_Certification_Pathway.png|thumb|center|900px|'''Mini-Bee certification pathway'''<br />Placeholder visual showing the progression from concept definition to certification evidence and operational approval.]]

Revision as of 10:14, 19 May 2026

VTOL Certification Framework

Mini-Bee / Red VTOL — EASA Certification Framework

The VTOL Certification Framework defines how a vertical take-off and landing aircraft can be designed, justified, tested and progressively accepted by the aviation authority.

For Mini-Bee / Red VTOL, certification is not only a regulatory constraint. It is a design driver.

The objective is to position the aircraft inside the EASA certification environment and to identify the main rules that will guide the future technical demonstration.

File:MiniBee VTOL Certification Framework Overview.png
Mini-Bee / Red VTOL certification framework overview
Placeholder visual showing the aircraft, EASA, CS-27, SC-VTOL-02 and the certification pathway.

Quick project summary

Item Description
Project Mini-Bee / Red VTOL
Aircraft type 2PAX hybrid VTOL multicopter
Mission orientation Ultra-light air ambulance / VEMS concept
Certification topic EASA VTOL Certification Framework
Main aircraft basis CS-27 Small Rotorcraft
VTOL-specific basis SC-VTOL-02 Small-Category VTOL-Capable Aircraft
Key challenge Demonstrate that the aircraft can follow a credible path toward certification, safety and operational approval

Main presentation

The main document supporting this page is the PowerPoint presentation:

Red VTOL TRL4 — 2PAX VTOL hybrid multicopter — Ultra light air ambulance — EASA Certification Framework
Document Description
File:20260422 RedVTOL EASA Certification 01 High Level Framework v2 en.pptx High level certification framework for Mini-Bee / Red VTOL, including EASA references, CS-27, SC-VTOL-02, CS-VLR, CS-29, system and sub-system certification references, environmental topics, official links and glossary.
File:MiniBee EASA Presentation Extract.png
Presentation overview
Placeholder visual to be created from the first slide or from a graphical synthesis of the PowerPoint.

Visual introduction

Project overview

The Mini-Bee / Red VTOL concept is a hybrid VTOL aircraft project based on a distributed lift architecture.

From a certification point of view, the aircraft must be treated carefully because it is not a conventional helicopter and not a conventional aeroplane. It combines rotorcraft behaviour with VTOL-capable characteristics.

The current certification logic is therefore based on two main references:

  • CS-27 Small Rotorcraft for the rotorcraft basis;
  • SC-VTOL-02 for VTOL-capable specific aspects.

This dual approach helps structure the project without ignoring the innovative features of the aircraft.

High Level Certification Framework

The high level framework answers one main question:

Where does Mini-Bee / Red VTOL fit inside the EASA certification environment?

The current positioning is:

Reference Role
CS-27 Main basis for small rotorcraft certification.
SC-VTOL-02 Complementary framework for VTOL-capable characteristics.
CS-VLR Possible reference only if the aircraft fits very light rotorcraft restrictions.
CS-29 Reference for complex rotorcraft aspects or if the design exits CS-27 boundaries.
Certification positioning
Mini-Bee between small rotorcraft logic and VTOL-capable aircraft logic.

At this level, the key point is to avoid a late reclassification risk.

A design initially considered under CS-27 may be pushed toward more demanding expectations if it exceeds boundaries related to mass, occupants, complexity, power architecture, operating mode or public transport use.

EASA as official source

EASA is the official European authority for aviation safety and certification.

For Mini-Bee / Red VTOL, every certification reference must be checked from official EASA sources:

  • certification specifications;
  • special conditions;
  • acceptable means of compliance;
  • guidance material;
  • rulemaking tasks;
  • consultation documents;
  • easy access rules;
  • official FAQs and product lists.

This is important because certification work must rely on validated texts, with clear issue dates and amendment levels.

Main EASA references

Reference Main use for Mini-Bee / Red VTOL
CS-27 Small rotorcraft certification basis.
SC-VTOL-02 VTOL-capable aircraft specific requirements.
CS-VLR Very light rotorcraft reference, under strict limitations.
CS-29 Large rotorcraft reference for complex or higher-category aspects.
CS-E Engine certification.
SC E-19 Electric and hybrid propulsion system certification.
CS-P Propeller certification.
CS-26 Additional airworthiness specifications for operations.
AMC-20 Products, parts and appliances.
CS-34 Aircraft engine emissions and fuel venting.

System and sub-system framework

The medium level framework links the aircraft-level certification basis to each major technical domain.

For Mini-Bee / Red VTOL, the most important domains are:

  • thermal engine;
  • electric and hybrid propulsion system;
  • propellers or rotors;
  • high-power electrical architecture;
  • distributed lift system;
  • operational airworthiness;
  • emissions and fuel venting;
  • noise and environmental constraints.
File:MiniBee Medium Level System Map.png
System and sub-system certification map
Placeholder visual showing CS-E, SC E-19, CS-P, CS-26, AMC-20 and CS-34 around the Mini-Bee architecture.

The main technical point is the definition of the complete lift / thrust system.

For Mini-Bee, this system should include the complete chain:

Chain element Certification attention point
Fuel / energy source Safety, storage, venting, endurance and environmental constraints.
Thermal engine CS-E, installation, operating limits and integration.
Electrical generation Power conversion, reliability and degraded modes.
Power electronics Thermal control, electrical safety and EMC.
Electric motors Redundancy, failure cases and thrust control.
Propellers / rotors CS-P, loads, vibration, safety and noise.
Flight control logic Command, monitoring, degraded modes and safety analysis.

Low Level demonstration

The low level framework is the level of evidence.

At this stage, the project must demonstrate that each requirement is satisfied through traceable proof.

Typical evidence includes:

  • analyses;
  • calculations;
  • simulations;
  • safety assessments;
  • system schematics;
  • bench tests;
  • HIL / SIL tests;
  • inspections;
  • qualification reports;
  • flight test preparation;
  • flight test reports.
File:MiniBee Low Level Evidence Matrix.png
Low level evidence matrix
Placeholder visual showing the link between requirements, means of compliance and project deliverables.

This level is essential because certification is not based on intention. It is based on documented, verifiable and reviewable evidence.

Main certification risks

Risk Why it matters
Boundary between CS-27 and SC-VTOL Mini-Bee combines rotorcraft behaviour and VTOL-capable characteristics.
Possible move toward CS-29 expectations Complexity, mass, occupants or operations may increase the certification burden.
Hybrid propulsion The propulsion chain may need to be treated as an integrated safety-critical system.
High electrical power Electrical architecture, EWIS and EMC require specific attention.
Distributed lift Failure modes and degraded operation must be clearly demonstrated.
VEMS / medical mission Emergency medical use may introduce additional operational constraints.

Certification maturity logic

The certification framework for VTOL-capable aircraft is still evolving.

Mini-Bee / Red VTOL should therefore keep a living certification watch on:

  • SC-VTOL updates;
  • new means of compliance;
  • EASA Rotorcraft and VTOL Safety Symposium outputs;
  • electric and hybrid propulsion guidance;
  • environmental rules;
  • operational rules for VTOL-capable aircraft;
  • pilot training and licensing evolutions.

This point is important for the transition toward a stronger demonstrator phase.

What the presentation clarified

The PowerPoint presentation clarified several key points:

Topic Clarification
Aircraft classification Mini-Bee can be considered as a small rotorcraft with VTOL-capable characteristics.
Main certification basis CS-27 should be used as the main rotorcraft basis.
VTOL complement SC-VTOL-02 is needed for specific VTOL-capable features.
System certification Engine, hybrid propulsion, propellers and electrical systems require dedicated references.
Design risk The project must avoid unintentionally exiting the CS-27 frame.
Future work Each certification text must be analysed in detail to deduce constraints and design options.

Questions to solve before a future certification phase

Before moving toward a more advanced certification phase, several questions must be clarified:

  • What is the final certified mass target?
  • What is the final occupant configuration?
  • Which parts of the hybrid propulsion chain can rely on certified components?
  • How should the integrated lift / thrust system be demonstrated?
  • Which degraded modes must be demonstrated?
  • What operational category should be targeted?
  • How far should the VEMS mission be included in the first certification logic?
  • Which EASA discussions or consultations should the project enter?

Suggested visuals to create

Visual Purpose
MiniBee_VTOL_Certification_Framework_Overview.png Global cover visual for the page.
MiniBee_High_Level_Certification_Map.png Show CS-27, SC-VTOL-02, CS-29 and CS-VLR around Mini-Bee.
MiniBee_CS27_SCVTOL_Positioning.png Explain the dual positioning: rotorcraft basis + VTOL-capable complement.
MiniBee_Lift_Thrust_System_Chain.png Show the complete hybrid chain from fuel to propellers.
MiniBee_Medium_Level_System_Map.png Map systems and sub-systems to certification references.
MiniBee_Low_Level_Evidence_Matrix.png Show requirements linked to evidence and means of compliance.
MiniBee_Certification_Pathway.png Final synthesis visual: concept → framework → compliance → tests → approval.

Useful links

Why this framework matters

The VTOL Certification Framework is essential because Mini-Bee / Red VTOL cannot be assessed only through performance or innovation.

The aircraft must also be understandable, justifiable and demonstrable from a certification point of view.

This framework helps the project move from an innovative VTOL concept toward a structured, traceable and credible aircraft development path.

File:MiniBee Certification Pathway.png
Mini-Bee certification pathway
Placeholder visual showing the progression from concept definition to certification evidence and operational approval.