beeplane - Recent changes [en]

Minibee TRL1

Wiki.admin — Wed, 06 May 2026 11:27:58 GMT

File:MiniBee TRL1 01 initial sketch.png

Wiki.admin — Wed, 06 May 2026 11:14:24 GMT

Wiki.admin uploaded File:MiniBee TRL1 01 initial sketch.png

New page

File:MiniBee TRL1 01 initial sketch.png

Wiki.admin — Wed, 06 May 2026 11:03:07 GMT

Wiki.admin deleted page File:MiniBee TRL1 01 initial sketch.png

File:MiniBee TRL1 01 initial sketch.png

Wiki.admin — Wed, 06 May 2026 10:54:42 GMT

Wiki.admin uploaded File:MiniBee TRL1 01 initial sketch.png

New page

Minibee TRL1

Wiki.admin — Wed, 06 May 2026 10:52:59 GMT

Show changes

Minibee TRL1

Wiki.admin — Wed, 06 May 2026 10:43:19 GMT

Created page with "{{DISPLAYTITLE:TRL 1 – Mini-Bee}} __TOC__ <div style="border:1px solid #cfd6dd; background:#ffffff; margin-bottom:20px;"> <div style="background:#1f3a5f; color:#ffffff; pa..."

New page

{{DISPLAYTITLE:TRL 1 – Mini-Bee}}

__TOC__

<div style="border:1px solid #cfd6dd; background:#ffffff; margin-bottom:20px;">
<div style="background:#1f3a5f; color:#ffffff; padding:12px 16px; font-weight:bold;">
TRL 1 – Mini-Bee | Basic Principles Observed
</div>
<div style="padding:16px;">
This page documents the '''TRL 1 stage''' of the '''Mini-Bee''' project. It presents the initial rationale, the first principles observed, the original mission intent, and the earliest visual explorations that marked the beginning of the project.
</div>
</div>

{| style="width:100%; border-collapse:separate; border-spacing:12px; margin-bottom:20px;"
|-
| style="width:25%; vertical-align:top; border:1px solid #cfd6dd; background:#f6f8fa; padding:12px;" |
'''Project'''<br />
Mini-Bee

| style="width:25%; vertical-align:top; border:1px solid #cfd6dd; background:#f6f8fa; padding:12px;" |
'''TRL stage documented'''<br />
TRL 1 – Basic Principles Observed

| style="width:25%; vertical-align:top; border:1px solid #cfd6dd; background:#f6f8fa; padding:12px;" |
'''Initial phase'''<br />
2015–2016

| style="width:25%; vertical-align:top; border:1px solid #cfd6dd; background:#f6f8fa; padding:12px;" |
'''Project context today'''<br />
Mini-Bee has since progressed beyond this stage and is now documented separately at higher TRL levels.
|}

== Project overview ==

'''Mini-Bee''' is a hybrid VTOL multicopter project developed within the Collaborative Bee framework.

The project was initiated to explore a new type of compact vertical take-off and landing aircraft capable of serving practical missions with a lighter and potentially more deployable architecture than conventional helicopter solutions.

At '''TRL 1''', Mini-Bee was still at the stage of '''basic principles observed'''. The objective was not yet to validate a final aircraft architecture, but to identify the main technical and operational principles that could justify the project.

== Early project visuals ==

<div style="border:1px solid #cfd6dd; background:#f6f8fa; padding:12px; margin:16px 0;">
'''Note:''' the visuals below should use the official early Mini-Bee images available in the project documentation and wiki library.
</div>

<gallery mode="packed" heights="180">
File:MiniBee_TRL1_2015_BasicMockup.jpg|2015 – Basic mock-up
File:MiniBee_TRL1_2016_DetailedConcept.jpg|2016 – Detailed concept
File:MiniBee_TRL1_2017_ScaleModel.jpg|2017 – Early scale model
</gallery>

== Mission origin ==

The Mini-Bee project emerged from the observation that many humanitarian, emergency and low-infrastructure missions require an aircraft that is:

* compact;
* operational with limited ground support;
* easier to deploy than a conventional helicopter;
* adapted to short-notice missions;
* potentially lower in operating cost;
* designed with safety and redundancy in mind.

From the beginning, the project explored the possibility of combining '''vertical flight capability''' with a lighter and more modular aircraft logic.

== Initial intention at TRL 1 ==

At TRL 1, the Mini-Bee project was driven by an early strategic idea:

<div style="border-left:4px solid #1f3a5f; background:#f6f8fa; padding:12px; margin:16px 0;">
Create the basis for a compact VTOL aircraft concept able to support practical missions such as emergency access, humanitarian support and light air mobility, while benefiting from simplified deployment and a modern distributed propulsion logic.
</div>

The mission set was not yet frozen, and the detailed configuration was not yet defined. However, the project already aimed at addressing real operational constraints rather than developing a purely theoretical concept.

== Basic principles observed ==

At TRL 1, the project focused on identifying the first principles that could support the future Mini-Bee concept.

{| style="width:100%; border-collapse:separate; border-spacing:12px; margin:16px 0;"
|-
| style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff; padding:12px;" |
'''Vertical take-off and landing capability'''

The project started from the observation that VTOL capability is highly valuable for missions in constrained environments where runway access is limited or impossible.

| style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff; padding:12px;" |
'''Distributed propulsion logic'''

An early principle was the interest of distributing lift and propulsion functions rather than relying on the traditional single main rotor helicopter architecture.

| style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff; padding:12px;" |
'''Operational simplicity and deployability'''

From the start, the project considered the importance of transportability, modularity and practical deployment in the field.
|}

{| style="width:100%; border-collapse:separate; border-spacing:12px; margin:0 0 16px 0;"
|-
| style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff; padding:12px;" |
'''Hybrid energy pathway'''

The future possibility of hybridization was identified early as a relevant direction for combining endurance, flexibility and distributed electric propulsion.

| style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff; padding:12px;" |
'''Compact two-person mission logic'''

A compact aircraft size and a limited onboard occupancy concept were already aligned with the intended mission profile.

| style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff; padding:12px;" |
'''Safety through architecture'''

The project explored from the beginning the idea that a modern VTOL concept could improve resilience through redundancy and simplified mission-oriented design.
|}

== What TRL 1 covered ==

At this stage, the Mini-Bee project focused on the following areas:

* identification of the mission need;
* first observations on VTOL operational value;
* first reflection on distributed propulsion;
* early concept sketches and visual exploration;
* first comparison with conventional aircraft logic;
* initial assumptions on compactness, modularity and field usability.

== What was not yet defined ==

TRL 1 did '''not''' yet define the final aircraft configuration.

The following elements were still open or only partially explored:

* final rotor count;
* final propulsion architecture;
* detailed hybrid chain;
* avionics architecture;
* structural sizing;
* certification pathway;
* validated performance figures;
* detailed integration of systems.

<div style="border:1px solid #cfd6dd; background:#f6f8fa; padding:12px; margin:16px 0;">
'''Important:''' this page documents the origin of the project. It does not describe the later validated or current configuration in detail. Those elements belong to higher TRL pages.
</div>

== Early visual development ==

The first project visuals played an important role at TRL 1 because they helped transform an initial intuition into a project that could be discussed, shared and progressively structured.

The early visuals supported:

* communication of the concept;
* exploration of the aircraft overall logic;
* discussion with contributors and partners;
* first reflection on mission relevance;
* comparison with existing aircraft approaches.

== First design direction ==

Even at the earliest stage, Mini-Bee was not approached as a generic futuristic aircraft concept.

The project was oriented toward a '''practical and purposeful aircraft logic''':

* useful missions rather than speculative use cases;
* compact and efficient architecture;
* realistic field constraints;
* simplified deployment philosophy;
* potential fit for humanitarian and emergency-oriented scenarios.

== Early milestones ==

{| class="wikitable" style="width:100%;"
|-
! style="width:18%; background:#eef1f4;" | Period
! style="width:28%; background:#eef1f4;" | Milestone
! style="background:#eef1f4;" | Meaning for the project
|-
| '''2015'''
| Basic mock-up
| First physical and visual expression of the project idea.
|-
| '''2016'''
| Detailed concept
| Early refinement of the concept and clearer project direction.
|-
| '''2017'''
| Scale model
| First progression toward a more structured concept representation.
|-
| '''After TRL 1'''
| Further development stages
| The project later moved beyond basic principles toward more defined concept and demonstrator work.
|}

== Initial assumptions ==

At TRL 1, the project could already rely on a first set of assumptions:

{| class="wikitable" style="width:100%;"
|-
! style="width:30%; background:#eef1f4;" | Assumption
! style="background:#eef1f4;" | Initial interpretation
|-
| '''Mission relevance'''
| There is a real use case for a compact VTOL aircraft in emergency and low-infrastructure contexts.
|-
| '''Distributed architecture'''
| A distributed propulsion approach could offer interesting design pathways compared with conventional rotorcraft logic.
|-
| '''Deployability'''
| Field logistics and transportability should be considered from the beginning, not added later.
|-
| '''Compact format'''
| A small aircraft configuration can create a better fit for focused missions and lower system complexity.
|-
| '''Hybrid potential'''
| Hybrid propulsion may provide an interesting balance between mission endurance and electric propulsion flexibility.
|}

== Questions to solve before TRL 2 ==

Before moving from TRL 1 to TRL 2, several questions had to be clarified:

* What precise mission should drive the concept definition?
* What general aircraft architecture should be pursued?
* What level of distributed propulsion is relevant?
* What operational benefit would clearly differentiate Mini-Bee?
* What are the main safety and deployment advantages to target?
* What are the main technical risks that must be considered early?

== Why TRL 1 mattered ==

TRL 1 was a key stage because it established the project’s identity.

It transformed an emerging idea into a documented project foundation.
It allowed the Mini-Bee concept to begin as a structured innovation path rather than as an isolated intuition.

This first level created the basis for the later stages of concept formulation, technical development, academic collaboration and demonstrator preparation.

== Transition to the next stage ==

Once the first principles were identified and the initial concept direction became clearer, the Mini-Bee project could move toward:

<div style="border:1px solid #cfd6dd; background:#f6f8fa; padding:14px; margin-top:16px;">
'''TRL 2 – Technology Concept Formulated'''
</div>

At that stage, the project would no longer only describe the first principles, but start defining a more explicit concept and a clearer technical direction.

== See also ==

* [[Technology Readiness Level 1 – Basic Principles Observed|TRL 1 – General page]]
* [[TRL2 Mini-Bee|TRL 2 – Mini-Bee]]
* [[Mini-Bee|Mini-Bee project]]
* [[Collaborative Bee Projects]]

[[Category:Mini-Bee]]
[[Category:Technology Readiness Levels]]
[[Category:TRL 1]]
[[Category:Collaborative Bee]]

TRL1

Wiki.admin — Wed, 06 May 2026 10:32:54 GMT

Show changes

TRL1

Wiki.admin — Wed, 06 May 2026 10:01:59 GMT

Created page with "{{DISPLAYTITLE:Technology Readiness Level 1 (TRL 1)}} __TOC__ <div style="border:1px solid #b7d4ea; background:#f5fbff; padding:16px; border-radius:10px; margin-bottom:18px;..."

New page

{{DISPLAYTITLE:Technology Readiness Level 1 (TRL 1)}}

__TOC__

<div style="border:1px solid #b7d4ea; background:#f5fbff; padding:16px; border-radius:10px; margin-bottom:18px;">
<span style="font-size:180%; font-weight:bold;">Technology Readiness Level 1 – Basic Principles Observed</span><br />
<span style="font-size:110%;">A common reference page for the first maturity step of the Collaborative Bee projects.</span>
</div>

{| class="wikitable" style="width:100%; border-collapse:collapse; margin-bottom:18px;"
|-
! style="width:25%; background:#e8f3ff;" | TRL Level
| '''TRL 1'''
|-
! style="background:#e8f3ff;" | Name
| '''Basic principles observed'''
|-
! style="background:#e8f3ff;" | Project phase
| Scientific observation, first ideas, early conceptual exploration
|-
! style="background:#e8f3ff;" | Expected output
| Initial concept notes, scientific principles, early assumptions, first technical questions
|-
! style="background:#e8f3ff;" | Not yet expected
| Prototype, detailed design, validated architecture, certification evidence, operational demonstration
|}

== Purpose of this page ==

This page explains what '''Technology Readiness Levels''' are, with a specific focus on '''TRL 1'''.

It is intended to be used as a common entry point before accessing the project-specific TRL 1 pages for:

* [[TRL1 Mini-Bee|TRL 1 – Mini-Bee]]
* [[TRL1 Bee Plane|TRL 1 – Bee Plane]]
* [[TRL1 Iso-Plane|TRL 1 – Iso-Plane]]

The objective is to keep a shared understanding of maturity levels across the different Collaborative Bee projects.

== What are Technology Readiness Levels? ==

'''Technology Readiness Levels''' — usually called '''TRLs''' — are a scale used to describe the maturity of a technology, from the earliest scientific observation to a fully operational system.

The TRL scale helps project teams, academic partners, industrial contributors and decision-makers answer a simple question:

<div style="border-left:5px solid #2f80c0; background:#f7fbff; padding:12px; margin:14px 0;">
'''How mature is this technology, and what evidence supports this maturity level?'''
</div>

TRLs are not only a planning tool. They also help structure:

* research activities;
* technical documentation;
* prototype development;
* testing strategy;
* risk analysis;
* certification preparation;
* project reviews.

== Overview of the TRL scale ==

{| class="wikitable" style="width:100%; text-align:left;"
|-
! style="width:12%; background:#eef6ff;" | TRL
! style="width:28%; background:#eef6ff;" | Typical meaning
! style="background:#eef6ff;" | General interpretation
|-
| '''TRL 1'''
| Basic principles observed
| Scientific principles are identified. The idea is still at the observation and concept level.
|-
| '''TRL 2'''
| Technology concept formulated
| A possible application is described and a first concept is proposed.
|-
| '''TRL 3'''
| Experimental proof of concept
| First analytical or experimental evidence supports the concept.
|-
| '''TRL 4'''
| Technology validated in laboratory
| Key functions are tested in a controlled environment.
|-
| '''TRL 5'''
| Technology validated in relevant environment
| The technology is tested in conditions closer to real use.
|-
| '''TRL 6'''
| Technology demonstrated in relevant environment
| A representative model or prototype demonstrates the main functions.
|-
| '''TRL 7'''
| System prototype demonstrated in operational environment
| A prototype is tested in realistic operational conditions.
|-
| '''TRL 8'''
| System complete and qualified
| The system is completed, tested and qualified for its intended use.
|-
| '''TRL 9'''
| Actual system proven in operational use
| The technology is fully operational and used in real missions.
|}

== Definition of TRL 1 ==

'''TRL 1 is the first level of technological maturity.'''

At this stage, the project team observes and identifies basic scientific or technical principles that may support a future technology.

TRL 1 does '''not''' mean that a product exists.
It does '''not''' mean that an architecture is frozen.
It does '''not''' mean that the technology is already feasible, safe or certifiable.

TRL 1 means that the first foundations have been identified and that a technical exploration can begin.

== What TRL 1 means in practice ==

At TRL 1, the work is mainly exploratory. The project team may:

* identify a need or mission;
* observe physical, aerodynamic, mechanical, electrical or operational principles;
* collect scientific references;
* compare existing technologies;
* formulate early technical questions;
* identify possible benefits and limitations;
* open the first project documentation page.

At this level, uncertainty is normal. The goal is not to prove the solution, but to define the knowledge base from which the concept can grow.

== Typical TRL 1 deliverables ==

{| class="wikitable" style="width:100%;"
|-
! style="width:30%; background:#eef6ff;" | Deliverable
! style="background:#eef6ff;" | Description
|-
| Mission statement
| First description of the need, use case or problem to solve.
|-
| Basic principles note
| Identification of the physical, technical or scientific principles that may support the idea.
|-
| Initial bibliography
| First list of references, comparable projects, existing technologies or scientific sources.
|-
| Concept assumptions
| Early assumptions about mass, energy, structure, flight mode, deployment or operation.
|-
| Open questions list
| Main unknowns that must be studied before moving to TRL 2.
|-
| First risk list
| Early identification of technical, operational, safety or regulatory risks.
|}

== What is not required at TRL 1 ==

At TRL 1, the following elements are usually '''not yet required''':

* detailed engineering drawings;
* complete system architecture;
* prototype;
* simulation model;
* laboratory validation;
* supplier selection;
* certification compliance matrix;
* operational procedure;
* costed industrial plan.

These elements usually appear at later TRL stages.

== TRL 1 exit criteria ==

A project may be considered ready to move from '''TRL 1''' to '''TRL 2''' when:

{| class="wikitable" style="width:100%;"
|-
! style="width:8%; background:#eef6ff;" | #
! style="background:#eef6ff;" | Exit criterion
! style="width:20%; background:#eef6ff;" | Status
|-
| 1
| The basic scientific or technical principles have been identified.
| To be assessed
|-
| 2
| A potential application has been described.
| To be assessed
|-
| 3
| The main assumptions and uncertainties have been listed.
| To be assessed
|-
| 4
| Comparable existing technologies or references have been identified.
| To be assessed
|-
| 5
| A first concept direction can be formulated.
| To be assessed
|}

== Project-specific TRL 1 pages ==

The following pages apply the TRL 1 logic to each project.

{| class="wikitable" style="width:100%;"
|-
! style="width:25%; background:#e8f3ff;" | Project
! style="width:25%; background:#e8f3ff;" | TRL 1 page
! style="background:#e8f3ff;" | Purpose
|-
| '''Mini-Bee'''
| [[TRL1 Mini-Bee|Open TRL 1 – Mini-Bee]]
| Early principles behind a hybrid VTOL multicopter for humanitarian and medical missions.
|-
| '''Bee Plane'''
| [[TRL1 Bee Plane|Open TRL 1 – Bee Plane]]
| Early principles behind the Bee Plane concept and its possible mission applications.
|-
| '''Iso-Plane'''
| [[TRL1 Iso-Plane|Open TRL 1 – Iso-Plane]]
| Early principles behind the Iso-Plane concept and its initial technical assumptions.
|}

== Recommended structure for each TRL 1 project page ==

Each project-specific TRL 1 page should preferably follow the same structure:

# Mission or need
# Basic principles observed
# Early technical assumptions
# Comparable technologies or references
# Main opportunities
# Main uncertainties
# First risks
# Questions to solve before TRL 2
# Contributors and references

== Summary ==

TRL 1 is the starting point of a technology project.

It is the moment where the idea is still at the level of scientific observation and early reasoning.
The purpose is to create a clear foundation before formulating a structured technology concept at TRL 2.

<div style="border:1px solid #d8d8d8; background:#fafafa; padding:12px; border-radius:8px; margin-top:18px;">
'''Next step:''' once the basic principles are documented, each project can move toward '''TRL 2 – Technology concept formulated'''.
</div>

== See also ==

* [[TRL1 Mini-Bee|TRL 1 – Mini-Bee]]
* [[TRL1 Bee Plane|TRL 1 – Bee Plane]]
* [[TRL1 Iso-Plane|TRL 1 – Iso-Plane]]
* [[Technology Readiness Levels]]
* [[Collaborative Bee Projects]]

== Categories ==

[[Category:Technology Readiness Levels]]
[[Category:Project Management]]
[[Category:Collaborative Bee]]
[[Category:TRL 1]]

File:Minibee official 1.png

Wiki.admin — Mon, 04 May 2026 09:53:04 GMT

Wiki.admin deleted page File:Minibee official 1.png Deleted old revision 20260504095128!Minibee_official_1.png

File:Minibee official 1.png

Wiki.admin — Mon, 04 May 2026 09:51:29 GMT

Wiki.admin uploaded a new version of File:Minibee official 1.png

New page

RED VTOL ONG

Wiki.admin — Mon, 04 May 2026 09:35:24 GMT

Alten Solidaire

Wiki.admin — Mon, 04 May 2026 09:08:28 GMT

References

File:10 tarmac assembly minibee.png

Wiki.admin — Thu, 30 Apr 2026 12:08:24 GMT

Wiki.admin uploaded File:10 tarmac assembly minibee.png

New page

File:08 logistique ld3 minibee.png

Wiki.admin — Thu, 30 Apr 2026 12:04:40 GMT

Wiki.admin uploaded File:08 logistique ld3 minibee.png

New page

File:09 cockpit hmi avionics minibee.png

Wiki.admin — Thu, 30 Apr 2026 11:56:49 GMT

Wiki.admin uploaded File:09 cockpit hmi avionics minibee.png

New page

File:03 architecture technique minibee.png

Wiki.admin — Thu, 30 Apr 2026 11:49:44 GMT

Wiki.admin uploaded File:03 architecture technique minibee.png

New page

File:11 certification roadmap minibee.png

Wiki.admin — Thu, 30 Apr 2026 11:40:06 GMT

Wiki.admin uploaded File:11 certification roadmap minibee.png

New page

File:07 mission emergency energy minibee.png

Wiki.admin — Thu, 30 Apr 2026 11:32:27 GMT

Wiki.admin uploaded File:07 mission emergency energy minibee.png

New page

File:06 mission remote access minibee.png

Wiki.admin — Thu, 30 Apr 2026 11:22:10 GMT

Wiki.admin uploaded File:06 mission remote access minibee.png

New page

File:05 mission disaster relief minibee.png

Wiki.admin — Thu, 30 Apr 2026 11:14:01 GMT

Wiki.admin uploaded File:05 mission disaster relief minibee.png

New page

File:04 mission air ambulance minibee.png

Wiki.admin — Thu, 30 Apr 2026 11:08:25 GMT

Wiki.admin uploaded File:04 mission air ambulance minibee.png

New page

File:02 vue produit studio minibee.png

Wiki.admin — Thu, 30 Apr 2026 10:43:12 GMT

Wiki.admin uploaded File:02 vue produit studio minibee.png

New page

Mini-Bee

Wiki.admin — Thu, 30 Apr 2026 08:44:44 GMT

File:01 hero principal minibee.png

Wiki.admin — Thu, 30 Apr 2026 08:27:07 GMT

Wiki.admin uploaded File:01 hero principal minibee.png

New page

Mini-Bee

Wiki.admin — Thu, 30 Apr 2026 08:25:22 GMT

Visual Overview

Show changes

RED VTOL ONG

Wiki.admin — Thu, 30 Apr 2026 07:49:45 GMT

Mission logic first

Technoplane

Wiki.admin — Thu, 30 Apr 2026 07:47:40 GMT

ISO-Plane

Iso-Plane

Wiki.admin — Tue, 28 Apr 2026 14:48:26 GMT

Show changes

File:Minibee official 6.png

Wiki.admin — Tue, 28 Apr 2026 10:41:15 GMT

Wiki.admin deleted page File:Minibee official 6.png Deleted old revision 20260428103843!Minibee_official_6.png

File:Minibee official 6.png

Wiki.admin — Tue, 28 Apr 2026 10:38:43 GMT

Wiki.admin uploaded a new version of File:Minibee official 6.png

New page

File:Minibee official 5.png

Wiki.admin — Tue, 28 Apr 2026 09:50:26 GMT

Wiki.admin deleted page File:Minibee official 5.png Deleted old revision 20260428094917!Minibee_official_5.png

File:Minibee official 5.png

Wiki.admin — Tue, 28 Apr 2026 09:49:18 GMT

Wiki.admin uploaded a new version of File:Minibee official 5.png

New page

File:Isoplane main.png

Wiki.admin — Tue, 28 Apr 2026 09:40:45 GMT

Wiki.admin deleted page File:Isoplane main.png Deleted old revision 20260428093538!Isoplane_main.png

File:Isoplane main.png

Wiki.admin — Tue, 28 Apr 2026 09:35:39 GMT

Wiki.admin uploaded a new version of File:Isoplane main.png

New page

@@ Line 18: / Line 18: @@
 | style="width:52%; vertical-align:middle; text-align:center;" |
-[[File:MiniBee_TRL1_01_initial_sketch.png|frameless|620px|Initial Mini-Bee concept sketch]]
+[[File:MiniBee_TRL1_01_initial_sketch.png|frameless|420px|Initial Mini-Bee concept sketch]]
 <div style="color:#4b5563; margin-top:6px;">Initial concept sketch – early Mini-Bee visual exploration</div>
 |}
@@ Line 50: / Line 50: @@
 |-
 | style="width:33%; vertical-align:top; border:1px solid #cfd6dd; background:#ffffff; padding:10px; text-align:center;" |
-[[File:MiniBee_TRL1_01_initial_sketch.png|frameless|300px|Initial sketch]]
+[[File:MiniBee_TRL1_01_initial_sketch.png|frameless|280px|Initial sketch]]
 <div style="margin-top:8px;">'''Initial sketch'''</div>
 <div style="color:#4b5563;">First visual expression of the compact VTOL idea.</div>

@@ Line 150: / Line 150: @@
 == Three mission families ==
-=== Medical missions ===
+=== Research ===
-The medical field is one of the clearest applications for a humanitarian VTOL platform. In this context, Mini-Bee Hybrid may contribute to:
+Research is the first mission family supported by RED VTOL ONG. Its objective is to study how VTOL aircraft can respond to humanitarian, medical and solidarity needs in real operating conditions.
-* transporting medical supplies;
+In this context, Mini-Bee Hybrid may contribute to research on:
-=== Educational missions ===
+* medical access in isolated or degraded areas;
-In remote or difficult-to-access regions, humanitarian missions may also include educational support. A VTOL platform can help transport:
+This research work helps define what a useful humanitarian VTOL platform should really do before focusing only on technical performance.
-* teachers or trainers;
+=== Experimentation ===
-=== Solidarity worksites and field support ===
+Experimentation is the second mission family supported by RED VTOL ONG. Its purpose is to test, compare and validate practical mission scenarios before any large-scale deployment.
-Humanitarian field activity is not limited to medical support. VTOL systems may also support solidarity missions and field worksites by transporting:
+Humanitarian experimentation may include:
-* one passenger in addition to the pilot;
+* simulated medical evacuation missions;
-* tools, materials and equipment;
+* transport of emergency medical kits;
-* a doctor if required;
+* field tests for access to isolated villages or temporary humanitarian sites;
-* support resources for temporary teams operating in difficult areas.
+* evaluation of loading, unloading and mission preparation procedures;
-They can also help evacuate an injured volunteer or locate teams and people in the field.
+The objective is to verify whether a light hybrid VTOL platform can be useful, safe, deployable and maintainable in realistic humanitarian conditions.
 [[File:minibee_official_4.png|thumb|center|720px|Mini-Bee – official visual]]

← Older revision		Revision as of 09:08, 4 May 2026
Line 188:		Line 188:

	== References ==		== References ==
−
−
−	* [https://www.jobyaviation.com/technology Joby Aviation – Technology]
−	* [https://www.ehang.com/ehang216s/airworthiness/ EHang EH216-S – Airworthiness]
−	* [https://www.zapata.com/airscooter/ Zapata AirScooter]
−	* [https://www.flyrotax.com/products/916-is-c Rotax 916 iS]
−	* [https://www.reuters.com/business/aerospace-defense/german-air-taxi-start-up-volocopter-files-insolvency-2024-12-30/ Reuters – Volocopter insolvency]
−	* [https://www.flightglobal.com/aerospace/2026/04/lilium-jets-journey-ends-on-scrapheap-as-prototypes-fail-to-sell/ FlightGlobal – Lilium insolvency context]

@@ Line 16: / Line 16: @@
 <div style="position:relative; overflow:hidden; border-radius:28px; background:linear-gradient(135deg,#10263b 0%,#1f4058 52%,#49677a 100%); color:white; padding:42px 42px 34px 42px; margin:0 0 28px 0; box-shadow:0 18px 44px rgba(15,23,42,0.18);">
    <div style="max-width:1180px; margin:auto;">
-     <div style="display:inline-block; padding:7px 13px; border:1px solid rgba(255,255,255,0.24); border-radius:999px; background:rgba(255,255,255,0.09); font-size:13px; letter-spacing:0.08em; text-transform:uppercase; color:#edf3f8;">
+     <p style="margin:0 0 10px 0; padding:0; border:0; background:transparent; font-size:13px; letter-spacing:0.08em; text-transform:uppercase; color:#ffffff; font-weight:600; box-shadow:none;">
        TRL4 demonstrator · Hybrid VTOL · Humanitarian aviation
-     </div>
+     </p>
      <h1 style="font-size:50px; line-height:1.02; margin:22px 0 14px 0; max-width:900px; font-weight:800; letter-spacing:-0.04em; color:#ffffff;">
@@ Line 162: / Line 162: @@
 <!-- ===================================================== -->
 <!-- VISUAL OVERVIEW -->
 <!-- ===================================================== -->

← Older revision		Revision as of 07:49, 30 April 2026
(One intermediate revision by the same user not shown)
Line 97:		Line 97:

	The common operational need is clear: transport equipment, carry one additional person besides the pilot, observe or locate, and remain quickly deployable in the field. Humanitarian VTOL platforms must also be easy to maintain, resistant to crash conditions, financially accessible and capable of operating in constrained environments.		The common operational need is clear: transport equipment, carry one additional person besides the pilot, observe or locate, and remain quickly deployable in the field. Humanitarian VTOL platforms must also be easy to maintain, resistant to crash conditions, financially accessible and capable of operating in constrained environments.
		+	<BR>
		+	<BR>
		+	<BR>
		+	<BR>
		+	<BR>

	== Support for the Mini-Bee Hybrid project ==		== Support for the Mini-Bee Hybrid project ==

@@ Line 9: / Line 9: @@
 | style="width:35%; vertical-align:top; text-align:center;" |
-[[File:technoplane_minibee_intro.png|300px|Mini-Bee – projet coordonné par Technoplane]]
+[[File:technoplane_minibee_intro.png|420px|Mini-Bee – projet coordonné par Technoplane]]
 <div style="font-size:95%; color:#555; margin-top:6px;">
@@ Line 20: / Line 20: @@
 {| style="width:100%; border-collapse:collapse; margin-bottom:25px;"
 | style="width:35%; vertical-align:top; text-align:center; padding-right:25px;" |
-[[File:technoplane_coordination.png|280px|Technoplane – coordination de l’écosystème Bee]]
+[[File:technoplane_coordination.png|360px|Technoplane – coordination de l’écosystème Bee]]
 <div style="font-size:95%; color:#555; margin-top:6px;">
@@ Line 43: / Line 43: @@
 | style="width:35%; vertical-align:top; text-align:center;" |
-[[File:technoplane_minibee_main.png|300px|Mini-Bee – VTOL hybride léger]]
+[[File:technoplane_minibee_main.png|340px|Mini-Bee – VTOL hybride léger]]
 <div style="font-size:95%; color:#555; margin-top:6px;">
@@ Line 54: / Line 54: @@
 {| style="width:100%; border-collapse:collapse; margin-bottom:25px;"
 | style="width:35%; vertical-align:top; text-align:center; padding-right:25px;" |
-[[File:beeplane_main.png|300px|Bee-Plane – avion à fuselage détachable]]
+[[File:beeplane_main.png|340px|Bee-Plane – avion à fuselage détachable]]
 <div style="font-size:95%; color:#555; margin-top:6px;">
@@ Line 79: / Line 79: @@
 | style="width:35%; vertical-align:top; text-align:center;" |
-[[File:isoplane_main.png|290px|ISO-Plane – transport direct d’un conteneur ISO]]
+[[File:isoplane_main.png|340px|ISO-Plane – transport direct d’un conteneur ISO]]
 <div style="font-size:95%; color:#555; margin-top:6px;">