Difference between revisions of "Certification FrameWork VTOL"

From beeplane
Jump to navigation Jump to search
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.]]
+
[[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]]
  
−
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.
+
The '''VTOL Certification Framework''' defines how a vertical take-off and landing aircraft can be designed, justified, tested, and accepted by the aviation authority.
  
−
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.
+
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.
  
−
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.
+
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 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.
+
[[File:MiniBee_VTOL_Certification_Framework_Overview.png|thumb|center|900px|'''Figure 1.''' Overview of the Mini-Bee / Red VTOL certification framework.]]
  
−
== Objective of the certification framework ==
+
== Objective ==
  
−
The objective of this certification framework is to:
+
The objective of this page is to summarize the certification logic presented in the document:
  
−
* define the regulatory environment in which the Mini-Bee / Red VTOL concept is included;
+
'''Red VTOL TRL4 — 2PAX VTOL hybrid multicopter — Ultra light air ambulance — EASA Certification Framework'''
−
* 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.
+
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.
  
−
[[File:MiniBee_Certification_Objectives.png|thumb|center|900px|'''Figure 2.''' Certification framework objectives: classification, applicable rules, maturity analysis, and evidence preparation.]]
+
The main objectives are:
 +
 
 +
* define the certification framework of the concept;
 +
* 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 ==
  
−
The '''High Level Certification Framework''' corresponds to the strategic level of the certification approach.
+
At high level, the main question is:
−
 
 
−
At this level, the question is:
 
−
 
 
−
: '''Where should Mini-Bee / Red VTOL be classified within the 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.
 
−
 
 
−
For Mini-Bee / Red VTOL, the current logic is:
 
−
 
 
−
* '''CS-27 Small Rotorcraft''' as the main certification basis;
 
−
* '''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.]]
 
−
 
 
−
=== EASA as the official reference ===
 
−
 
 
−
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.
 
−
 
 
−
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:
 
−
 
 
−
* official EASA origin;
 
−
* issue number;
 
−
* amendment number;
 
−
* publication date;
 
−
* current validity;
 
−
* associated AMC or GM;
 
−
* relationship with other certification specifications.
 
−
 
 
−
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.
 
  
−
== Main certification positioning of Mini-Bee ==
+
: '''Where does Mini-Bee / Red VTOL fit inside the EASA certification framework?'''
  
−
Mini-Bee / Red VTOL is currently considered as:
+
The current logic is to consider Mini-Bee as:
  
−
: '''a small rotorcraft under CS-27, with VTOL-capable characteristics under SC-VTOL-02.'''
+
* a '''small rotorcraft''' under '''CS-27''';
 +
* with '''VTOL-capable characteristics''' under '''SC-VTOL-02'''.
  
−
This means that the design should comply with both:
+
This means that the design should be oriented around both references:
  
 
* '''CS-27 Small Rotorcraft''';
 
* '''CS-27 Small Rotorcraft''';
 
* '''SC-VTOL-02 Small-Category VTOL-Capable Aircraft'''.
 
* '''SC-VTOL-02 Small-Category VTOL-Capable Aircraft'''.
−
 
−
This dual positioning is one of the key points of the certification strategy.
 
  
 
CS-27 provides the rotorcraft basis.   
 
CS-27 provides the rotorcraft basis.   
−
SC-VTOL-02 provides the additional logic for the VTOL-capable aspects that are not fully covered by conventional rotorcraft rules.
+
SC-VTOL-02 adds the specific requirements linked to VTOL-capable aircraft, distributed lift, hybrid propulsion, high electrical power, and lift/thrust system safety.
  
−
[[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.]]
+
[[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.]]
  
−
== SC-VTOL-02 Small-Category VTOL-Capable Aircraft ==
+
== Main EASA references ==
  
−
'''SC-VTOL-02''' is a special condition for small-category VTOL-capable aircraft.
+
The presentation identifies several EASA references that structure the certification approach.
  
−
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.
+
{| class="wikitable"
 +
! Reference
 +
! Role for Mini-Bee / Red VTOL
 +
|-
 +
| '''CS-27'''
 +
| Main basis for small rotorcraft certification.
 +
|-
 +
| '''SC-VTOL-02'''
 +
| Special condition for small VTOL-capable aircraft.
 +
|-
 +
| '''CS-VLR'''
 +
| Possible reference for very light rotorcraft, only if the design fits its restrictions.
 +
|-
 +
| '''CS-29'''
 +
| Reference for large rotorcraft and complex design aspects.
 +
|-
 +
| '''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.
 +
|}
 +
 
 +
== System and Sub-System Certification Framework ==
 +
 
 +
The medium level of the framework concerns the main systems and sub-systems of the aircraft.
  
−
The main SC-VTOL-02 topics relevant to Mini-Bee include:
+
For Mini-Bee / Red VTOL, this includes:
  
−
* VTOL-capable aircraft classification;
+
* the engine;
−
* safety analysis;
+
* the electric or hybrid propulsion system;
−
* single failure prevention;
+
* the propellers or rotors;
−
* weight and occupant limits;
+
* the high-power electrical architecture;
−
* lift/thrust system definition;
+
* the lift/thrust chain;
−
* flight and safety recorders;
+
* operational airworthiness topics;
−
* high electrical power;
+
* emissions and environmental constraints.
−
* 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.
+
The key point is that Mini-Bee cannot be certified only as a set of separate components. 
 +
The complete '''lift/thrust system''' must be considered as an integrated chain.
  
−
This includes, for example:
+
This chain includes:
  
−
* fuel reservoir;
+
* energy source;
 
* thermal engine;
 
* thermal engine;
−
* generator or alternator;
+
* electrical generation;
 
* power electronics;
 
* power electronics;
−
* electrical distribution;
 
 
* electric motors;
 
* electric motors;
−
* rotors or propellers;
+
* distributed propellers or rotors;
 
* control logic;
 
* control logic;
−
* degraded modes;
+
* failure modes and degraded operation.
−
* 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.]]
 
−
 
 
−
== CS-27 Small Rotorcraft ==
 
−
 
 
−
'''CS-27''' is the Certification Specification for Small Rotorcraft.
 
−
 
 
−
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.
 
−
 
 
−
CS-27 provides requirements and acceptable means of compliance for small rotorcraft, including topics such as:
 
−
 
 
−
* structural design;
 
−
* 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.
 
−
 
 
−
== CS-VLR Very Light Rotorcraft ==
 
−
 
 
−
'''CS-VLR''' applies to very light rotorcraft.
 
−
 
 
−
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.
 
−
 
 
−
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.
 
−
 
 
−
CS-VLR is relevant mainly as a comparison tool for:
 
−
 
 
−
* simplicity of design;
 
−
* very light rotorcraft logic;
 
−
* low occupant count;
 
−
* restricted operations;
 
−
* possible design simplification.
 
−
 
 
−
== CS-29 Large Rotorcraft ==
 
−
 
 
−
'''CS-29''' applies to large rotorcraft.
 
−
 
 
−
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.
 
−
 
 
−
This may happen if the aircraft design includes:
 
−
 
 
−
* higher weight;
 
−
* 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.
 
−
 
 
−
This is a major risk to be considered early in the design.
 
−
 
 
−
[[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.]]
 
−
 
 
−
== Conclusion of the High Level framework ==
 
−
 
 
−
At High Level, Mini-Bee / Red VTOL should be treated as:
 
−
 
 
−
* a '''small rotorcraft''' under CS-27;
 
−
* 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.
 
−
 
 
−
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.
 
−
 
 
−
== Medium Level Certification Framework ==
 
−
 
 
−
The '''Medium Level Certification Framework''' corresponds to the system and sub-system certification architecture.
 
−
 
 
−
At this level, the question changes:
 
−
 
 
−
: '''Which certification texts apply to each technical domain of the aircraft?'''
 
−
 
 
−
The aircraft-level framework must be translated into system-level references. This is where the broad certification strategy becomes a practical engineering map.
 
−
 
 
−
For Mini-Bee / Red VTOL, the main system and sub-system references include:
 
−
 
 
−
* '''CS-E''' for engines;
 
−
* '''SC E-19''' for electric and hybrid propulsion systems;
 
−
* '''CS-P''' for propellers;
 
−
* '''CS-26''' for additional airworthiness specifications for operations;
 
−
* '''AMC-20''' for products, parts, and appliances;
 
−
* '''CS-34''' for aircraft engine emissions and fuel venting;
 
−
* '''CS-36''' for aircraft noise where applicable;
 
−
* '''CS-CO2''' for CO2 aspects where applicable;
 
−
* selected EASA Certification Memoranda and consultation material.
 
−
 
 
−
[[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.]]
 
−
 
 
−
== CS-E Engines ==
 
−
 
 
−
'''CS-E''' defines certification specifications and acceptable means of compliance for engines.
 
−
 
 
−
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.
 
−
 
 
−
A certified aeronautical engine may reduce certification effort, provided that:
 
−
 
 
−
* the engine is used within its certified operating envelope;
 
−
* installation effects are properly justified;
 
−
* cooling, fuel, vibration, and control interfaces are demonstrated;
 
−
* the integration with the hybrid chain does not create unaddressed risks.
 
−
 
 
−
If a non-certified or significantly modified engine is used, the certification burden becomes much higher.
 
−
 
 
−
For Mini-Bee, the engine must be analysed in relation with:
 
−
 
 
−
* CS-E;
 
−
* SC E-19;
 
−
* SC-VTOL-02;
 
−
* CS-34;
 
−
* the full lift/thrust system logic.
 
  
−
== SC E-19 Electric / Hybrid Propulsion System ==
+
[[File:MiniBee_Lift_Thrust_System_Chain.png|thumb|center|900px|'''Figure 3.''' Placeholder visual: complete Mini-Bee lift/thrust chain.]]
  
−
'''SC E-19''' is the special condition addressing electric and hybrid propulsion systems.
+
== Low Level Demonstration ==
  
−
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 low level corresponds to the concrete demonstration of compliance.
  
−
The key point is that the certification approach may consider the hybrid propulsion either as:
+
At this stage, the project must produce technical evidence. Each requirement must be linked to a means of compliance.
  
−
* an aircraft-level integrated system;
+
Typical evidence may include:
−
* 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:
+
* analyses;
−
 
+
* calculations;
−
: '''Should the hybrid propulsion system be treated as a set of components, or as one integrated lift/thrust system?'''
+
* safety studies;
−
 
+
* system schematics;
−
From a safety perspective, the integrated-system approach appears more coherent because failures may propagate through electrical, mechanical, thermal, and control interfaces.
+
* simulations;
−
 
 
−
[[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.
 
−
 
 
−
At this level, the question becomes:
 
−
 
 
−
: '''Which evidence proves that each requirement is satisfied?'''
 
−
 
 
−
This is where the project moves from regulatory interpretation to engineering proof.
 
−
 
 
−
For Mini-Bee / Red VTOL, Low Level certification work should include:
 
−
 
 
−
* requirement allocation;
 
−
* requirement traceability;
 
−
* design assumptions;
 
−
* safety analyses;
 
−
* functional hazard assessment;
 
−
* system safety assessment;
 
−
* architecture justification;
 
−
* schematics;
 
−
* material files;
 
−
* control logic description;
 
 
* bench tests;
 
* bench tests;
−
* simulation reports;
+
* HIL / SIL tests;
−
* HIL and SIL validation;
 
−
* electrical safety evidence;
 
−
* EWIS analysis;
 
−
* electromagnetic compatibility assessment;
 
−
* mechanical tests;
 
−
* environmental tests;
 
 
* inspection procedures;
 
* inspection procedures;
 
* flight test preparation;
 
* flight test preparation;
−
* flight test reports;
+
* test reports.
−
* degraded mode demonstrations.
 
−
 
 
−
[[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 Low Level is essential because certification is not granted on the basis of concept quality alone. It requires traceable and verifiable evidence.
 
−
 
 
−
Each requirement must be connected to a means of compliance, such as:
 
−
 
 
−
* analysis;
 
−
* calculation;
 
−
* test;
 
−
* inspection;
 
−
* demonstration;
 
−
* similarity;
 
−
* simulation;
 
−
* qualification;
 
−
* operational limitation.
 
−
 
 
−
== 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;
 
−
* 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.
 
−
 
 
−
== Parachute and recovery systems ==
 
−
 
 
−
The presentation also highlights the question of parachutes and recovery systems.
 
−
 
 
−
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.
 
−
 
 
−
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.
 
−
 
 
−
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.
+
This level is essential because certification is not based only on a concept. It is based on traceable proof.
  
−
[[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.]]
+
[[File:MiniBee_Low_Level_Evidence_Matrix.png|thumb|center|900px|'''Figure 4.''' Placeholder visual: requirements linked to analyses, tests, inspections and demonstrations.]]
  
−
== Rulemaking maturity and VTOL evolution ==
+
== Key certification risks ==
  
−
The certification framework for VTOL-capable aircraft is still evolving.
+
The main risks identified for Mini-Bee / Red VTOL are:
−
 
 
−
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'''
 
−
| Produce compliance evidence
 
−
| Which proof demonstrates compliance?
 
−
| AMC, GM, tests, analysis, simulations, inspections
 
−
| Traceable evidence files
 
−
|}
 
−
 
 
−
== Main certification risks ==
 
−
 
 
−
The main certification risks for Mini-Bee / Red VTOL are:
 
  
 
* unclear boundary between rotorcraft and VTOL-capable aircraft;
 
* unclear boundary between rotorcraft and VTOL-capable aircraft;
−
* design moving outside CS-27 assumptions;
+
* possible movement from CS-27 toward CS-29 if the design becomes too complex;
−
* hybrid propulsion treated as an integrated safety-critical system;
+
* certification of the hybrid propulsion system;
−
* high-power electrical architecture requiring specific evidence;
+
* high electrical power requirements;
−
* distributed lift creating complex failure cases;
+
* distributed lift safety demonstration;
−
* lack of accepted means of compliance for some innovative features;
+
* lack of mature means of compliance for some VTOL technologies;
−
* operational use leading to additional requirements;
+
* operational requirements linked to air ambulance or public service missions.
−
* 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.
+
These risks do not block the project. They define the topics that must be treated early in the design process.
  
 
== Conclusion ==
 
== Conclusion ==
Line 507: Line 158:
 
Mini-Bee / Red VTOL should currently be considered as a '''small rotorcraft with VTOL-capable characteristics'''.
 
Mini-Bee / Red VTOL should currently be considered as a '''small rotorcraft with VTOL-capable characteristics'''.
  
−
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.
+
The most credible certification logic is therefore based on:
  
−
The most important point is that certification must be integrated into the design process from the beginning.
+
* '''CS-27''' as the small rotorcraft basis;
 +
* '''SC-VTOL-02''' for the VTOL-capable specific aspects;
 +
* '''SC E-19''' for hybrid propulsion;
 +
* additional references such as CS-E, CS-P, CS-26, AMC-20, CS-34, CS-VLR and CS-29 when relevant.
  
−
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.
+
The certification framework is not only a compliance checklist.
 +
It is a design management tool.
  
−
[[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.]]
+
It helps structure the project, identify design constraints, prepare evidence, and build a credible path toward future certification.
  
−
== Glossary ==
+
[[File:MiniBee_Certification_Pathway.png|thumb|center|900px|'''Figure 5.''' Placeholder visual: Mini-Bee certification pathway from concept to compliance demonstration.]]
  
−
{| class="wikitable"
+
== Download ==
−
! Acronym
 
−
! Meaning
 
−
|-
 
−
| 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 following visuals can be created later and inserted into the page:
+
* [[File:20260422_RedVTOL_EASA_Certification_01_High_Level_Framework_v2_en.pptx|Download the full PowerPoint presentation]]
−
 
 
−
{| 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 ==
 
== See also ==
Line 681: Line 180:
 
* [[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]]
 

Revision as of 10:12, 19 May 2026

VTOL Certification Framework

File:20260422 RedVTOL EASA Certification 01 High Level Framework v2 en.pptx

The VTOL Certification Framework defines how a vertical take-off and landing aircraft can be designed, justified, tested, and 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.

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.

File:MiniBee VTOL Certification Framework Overview.png
Figure 1. Overview of the Mini-Bee / Red VTOL certification framework.

Objective

The objective of this page is to summarize the certification logic presented in the document:

Red VTOL TRL4 — 2PAX VTOL hybrid multicopter — Ultra light air ambulance — EASA Certification Framework

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 main objectives are:

  • define the certification framework of the concept;
  • 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

At high level, the main question is:

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

The current logic is to consider Mini-Bee as:

  • a small rotorcraft under CS-27;
  • with VTOL-capable characteristics under SC-VTOL-02.

This means that the design should be oriented around both references:

  • CS-27 Small Rotorcraft;
  • SC-VTOL-02 Small-Category VTOL-Capable Aircraft.

CS-27 provides the rotorcraft basis. SC-VTOL-02 adds the specific requirements linked to VTOL-capable aircraft, distributed lift, hybrid propulsion, high electrical power, and lift/thrust system safety.

File:MiniBee High Level Certification Map.png
Figure 2. High level certification positioning: CS-27, SC-VTOL-02, CS-29 and CS-VLR.

Main EASA references

The presentation identifies several EASA references that structure the certification approach.

Reference Role for Mini-Bee / Red VTOL
CS-27 Main basis for small rotorcraft certification.
SC-VTOL-02 Special condition for small VTOL-capable aircraft.
CS-VLR Possible reference for very light rotorcraft, only if the design fits its restrictions.
CS-29 Reference for large rotorcraft and complex design aspects.
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.

System and Sub-System Certification Framework

The medium level of the framework concerns the main systems and sub-systems of the aircraft.

For Mini-Bee / Red VTOL, this includes:

  • the engine;
  • the electric or hybrid propulsion system;
  • the propellers or rotors;
  • the high-power electrical architecture;
  • the lift/thrust chain;
  • operational airworthiness topics;
  • emissions and environmental constraints.

The key point is that Mini-Bee cannot be certified only as a set of separate components. The complete lift/thrust system must be considered as an integrated chain.

This chain includes:

  • energy source;
  • thermal engine;
  • electrical generation;
  • power electronics;
  • electric motors;
  • distributed propellers or rotors;
  • control logic;
  • failure modes and degraded operation.
Figure 3. Placeholder visual: complete Mini-Bee lift/thrust chain.

Low Level Demonstration

The low level corresponds to the concrete demonstration of compliance.

At this stage, the project must produce technical evidence. Each requirement must be linked to a means of compliance.

Typical evidence may include:

  • analyses;
  • calculations;
  • safety studies;
  • system schematics;
  • simulations;
  • bench tests;
  • HIL / SIL tests;
  • inspection procedures;
  • flight test preparation;
  • 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
Figure 4. Placeholder visual: requirements linked to analyses, tests, inspections and demonstrations.

Key certification risks

The main risks identified for Mini-Bee / Red VTOL are:

  • unclear boundary between rotorcraft and VTOL-capable aircraft;
  • 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.

Conclusion

Mini-Bee / Red VTOL should currently be considered as a small rotorcraft with VTOL-capable characteristics.

The most credible certification logic is therefore based on:

  • CS-27 as the small rotorcraft basis;
  • SC-VTOL-02 for the VTOL-capable specific aspects;
  • SC E-19 for hybrid propulsion;
  • additional references such as CS-E, CS-P, CS-26, AMC-20, CS-34, CS-VLR and CS-29 when relevant.

The certification framework is not only a compliance checklist. It is a design management tool.

It helps structure the project, identify design constraints, prepare evidence, and build a credible path toward future certification.

File:MiniBee Certification Pathway.png
Figure 5. Placeholder visual: Mini-Bee certification pathway from concept to compliance demonstration.

Download

See also

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