The Role of the Aerodynamicist in Bee Projects and Early Aircraft Design

The Role of the Aerodynamicist in Bee Projects and Early Aircraft Design

Summary

The aerodynamicist is one of the key engineering profiles in any aircraft project. In the Bee ecosystem — Bee-Plane, ISO-Plane, Mini-Bee and related collaborative aircraft concepts — the aerodynamicist is not only the person who “makes the aircraft fly”. Their role is broader: they translate mission needs into shapes, surfaces, loads, performance targets, trade-offs and design decisions that other teams can use.

In early aircraft design, aerodynamics is a bridge between vision and feasibility. It connects market needs, mission profiles, structure, propulsion, certification, energy consumption, safety and environmental impact. A good aerodynamic study does not merely produce a wing profile or a CFD image; it helps the whole project team decide whether an aircraft concept is coherent, scalable and worth pursuing.

This is especially important in Bee projects, where teams work under the Lesser Open Bee License 1.3, a framework built around collaborative innovation, shared technical documentation and multi-participant development.

1. Why aerodynamics matters so early in aircraft design

In a mature aircraft program, aerodynamics is everywhere: cruise performance, take-off distance, stall behaviour, stability, engine integration, noise, fuel burn, certification margins and operating cost. But in an upstream design project, the aerodynamicist has an even more strategic role.

At TRL 1 to TRL 3, the aircraft is still a concept. The team does not yet know whether the fuselage is too wide, whether the wing is large enough, whether the tail is stable, whether the engine placement makes sense, or whether the mission profile is compatible with realistic lift and drag values. The aerodynamicist therefore acts as an early warning system.

Their work answers questions such as:

• Can the aircraft generate enough lift at take-off, cruise and landing?
• Is the wing surface coherent with the mass estimate and required runway performance?
• Is the aspect ratio realistic for structure, manufacturability and fuel efficiency?
• Does the fuselage create excessive drag?
• Is the tail volume sufficient for stability and control?
• Are the engines, rotors or propellers placed in a clean flow region?
• Are the assumptions used by the structure, propulsion and business teams physically consistent?

This is why aerodynamic work should start before the detailed CAD model is frozen. Once the geometry is too detailed, correcting a wrong wing, tail or fuselage choice becomes expensive in time, credibility and engineering effort.

2. The aerodynamicist as a system engineer

A common mistake is to see aerodynamics as a narrow discipline limited to airfoils, CFD and wind-tunnel images. In reality, the aerodynamicist works at system level.

The aerodynamicist must understand the aircraft as a coupled object:

Design domain	Aerodynamic link
Mission	Cruise altitude, speed, range, climb rate, runway constraints
Structure	Lift distribution, pressure loads, bending moments, aeroelastic risks
Propulsion	Engine placement, inlet quality, propeller or rotor interaction, cooling
Stability	Tail sizing, control surfaces, trim, centre-of-gravity range
Operations	Take-off, landing, loading, payload changes, emergency cases
Environment	Fuel burn, noise, induced drag, mission efficiency
Project management	Requirements, assumptions, verification evidence, interface control

This system view is particularly relevant in Bee projects. Bee-Plane, for example, is not a conventional aircraft: it is based on a detachable fuselage architecture, with a “Bee” carrier structure and a “Basket” module. The aerodynamicist must therefore consider not only a wing-body configuration, but also the aerodynamic consequences of modularity, attachment systems, passenger or cargo versions, and ground-operation constraints.

3. The aerodynamicist in Bee-Plane

In Bee-Plane, aerodynamics is closely linked to the detachable fuselage concept. The aircraft is designed around two main elements: the carrier structure, which includes cockpit, wings, landing gear and engines, and the detachable Basket, which carries passengers or cargo. This modular architecture creates a unique aerodynamic challenge: the aircraft must remain efficient, stable and safe while supporting an unconventional load path and fuselage integration logic.

The Bee-Plane aerodynamic work package has included objectives such as confirming an airfoil, studying lift generation, confirming MTOW, reviewing wing loading and aspect ratio, and reconsidering wing, tail and engine positioning. Earlier modelling work also raised concerns that the wing size could be too small and that the tailplane could be too high, showing how aerodynamic review can challenge previous assumptions before the project moves further into TRL validation.

For students, this is a powerful lesson: the aerodynamicist is not only a calculator. They are the person who asks, “Does this aircraft still make sense when the air actually flows around it?”

A Bee-Plane aerodynamicist should therefore work on the following topics.

Wing sizing and lift consistency

The first task is to verify that the wing can produce the required lift across the flight envelope. This includes estimating wing loading, stall speed, cruise lift coefficient, take-off performance and landing margin.

For Bee-Plane, this is especially important because the Basket mass, mission configuration and payload distribution may vary. A passenger Basket, a cargo Basket or a special mission Basket will not necessarily produce the same mass distribution or aerodynamic behaviour.

Tailplane and stability review

The tail is not an aesthetic element. It controls trim, stability, pitch authority and safety margins. If the tailplane is too small, too high, too low, too close to disturbed flow, or badly aligned with the wing wake, the whole aircraft concept becomes fragile.

A Bee-Plane aerodynamicist should estimate horizontal and vertical tail volume coefficients, check centre-of-gravity variations between Basket configurations, and document the impact of tail placement.

Engine integration

Engine placement affects drag, noise, intake quality, maintainability and structural load paths. On Bee-Plane, engine position is also linked with the carrier architecture and the modular fuselage. The aerodynamicist must work with propulsion and structure teams to evaluate whether engine placement improves or degrades aircraft performance.

Detachable fuselage effects

The Bee + Basket interface is a major design singularity. It may create local discontinuities, interference drag, junction effects and possible flow separation zones. These effects must be identified early, even with simplified methods, because they can drive the shape of fairings, attachment zones and structural covers.

4. The aerodynamicist in ISO-Plane

ISO-Plane illustrates another type of aerodynamic challenge: designing an aircraft around a demanding cargo mission. The aircraft must carry a 20-foot ISO container, manipulate it without external equipment, and remain compact and efficient enough to make sense compared with existing cargo aircraft.

In this case, the aerodynamicist faces a difficult compromise. A container is not aerodynamically convenient. It drives fuselage volume, frontal area, cargo-bay geometry, floor structure and loading systems. The aerodynamicist must help the team avoid turning a clever logistics idea into an inefficient flying box.

The ISO-Plane TRL2 aerodynamic work included the definition of design parameters such as range, cruise speed, take-off and landing distances, wing area, airfoil selection and nose-shape comparison. This is a good example of upstream aerodynamic work: the goal is not to produce a final certified geometry, but to reduce uncertainty, compare credible options and make the next TRL phase more focused.

5. The aerodynamicist in Mini-Bee and VTOL concepts

Mini-Bee introduces another aerodynamic world: rotor performance, distributed propulsion, vertical lift, transition risks, power-chain integration and emergency behaviour. In VTOL concepts, the aerodynamicist must deal not only with wings and fuselage, but also with rotor wakes, ground effect, crosswind sensitivity, downwash, interaction between rotors and structure, and control authority.

For a student aerodynamicist, Mini-Bee is valuable because it shows that aerodynamics is not limited to fixed-wing aircraft. In rotorcraft and VTOL systems, aerodynamic reasoning becomes strongly coupled with control laws, sensors, power electronics and safety logic.

A Mini-Bee aerodynamicist should ask:

• How much thrust is required in hover, climb and emergency cases?
• How does rotor placement affect stability?
• What happens if one rotor or motor group fails?
• How does downwash interact with the cabin, landing zone or surrounding obstacles?
• What is the acceptable compromise between rotor diameter, noise, structural weight and efficiency?
• How should the aircraft behave during transition, if transition flight exists?

6. Core technical responsibilities of the aerodynamicist

6.1 Build the aerodynamic requirements

Before drawing wings, the aerodynamicist must help formalize the requirements. These include:

• design mass and MTOW;
• payload and payload variation;
• cruise speed and altitude;
• stall speed;
• take-off and landing distance;
• climb performance;
• range and endurance;
• operational environment;
• regulatory constraints;
• safety margins;
• noise and environmental targets.

This step should be done with the project manager, structure team, propulsion team and mission-analysis team. It should produce a clear set of assumptions, because every later calculation depends on them.

6.2 Select first-order models

At early TRL, simple models are often more useful than complex simulations. The aerodynamicist should begin with:

• lift equation;
• drag polar estimation;
• wing loading analysis;
• aspect ratio comparison;
• tail volume coefficient;
• Reynolds and Mach number checks;
• airfoil database comparison;
• empirical performance formulas;
• sensitivity analysis.

The goal is to detect major inconsistencies quickly. A beautiful CFD simulation is not useful if the wing area, mass estimate or flight condition is wrong.

6.3 Choose and justify airfoils

Airfoil selection is a classic aerodynamic task, but it should not be isolated from the rest of the aircraft. The aerodynamicist must justify the airfoil according to:

• lift coefficient;
• stall behaviour;
• pitching moment;
• thickness ratio;
• structural depth for spars;
• low-speed performance;
• cruise drag;
• manufacturability;
• compatibility with flaps or high-lift systems.

Bee-Plane studies have investigated NACA-type profiles, while ISO-Plane work also used simplified NACA profiles in first approximation. These choices are not final certification answers; they are traceable design hypotheses that future teams can test, improve or replace.

6.4 Size wings and control surfaces

Wing sizing is one of the most important upstream tasks. It determines lift, stall speed, induced drag, structural bending moment, fuel burn and airport compatibility.

The aerodynamicist should produce:

• wing surface estimate;
• span and aspect ratio;
• taper ratio;
• sweep angle;
• dihedral angle;
• twist assumptions;
• flap concept;
• aileron sizing assumptions;
• horizontal tail surface;
• vertical tail surface;
• control authority assumptions.

For each value, the team should document the source, formula, assumptions and limitations.

6.5 Evaluate drag and performance

Aerodynamic performance should be expressed in a way that other teams can use. The aerodynamicist should estimate:

• parasite drag;
• induced drag;
• interference drag;
• fuselage drag;
• landing gear drag;
• cooling drag;
• propulsion installation losses;
• lift-to-drag ratio;
• fuel-burn sensitivity;
• climb and descent performance.

A good aerodynamicist does not only say, “The drag is high.” They explain where it comes from, how it affects mission cost, and which design actions could reduce it.

6.6 Support structure through aerodynamic loads

The structure team needs aerodynamic loads. The aerodynamicist should provide pressure distributions, lift distributions and load cases for:

• cruise;
• manoeuvre;
• gust;
• take-off;
• landing;
• emergency descent;
• asymmetric conditions;
• maximum lift cases;
• control surface deflection.

This requires a close interface with structural engineers. In Bee projects, where student teams often divide work into poles such as structure, aerodynamic, power chain, cockpit or configuration, this interface must be explicit in the WBS and reviewed regularly.

7. The aerodynamicist and project management

Aerodynamics is an engineering discipline, but it is also a project-management function. A technically correct aerodynamic study is not enough if it cannot be reused, challenged and continued by another team.

Good aerodynamic work should therefore follow core engineering project-management practices: clear objectives, structured WBS, realistic planning, iterative reviews, risk tracking, documentation, version control and retrospectives.

For an aerodynamicist, this means the following.

Define deliverables

Examples of aerodynamic deliverables:

• aerodynamic assumptions sheet;
• flight-envelope definition;
• airfoil comparison table;
• wing sizing note;
• tail sizing note;
• drag polar model;
• CFD setup report;
• mesh-quality report;
• simulation result file;
• sensitivity analysis;
• aerodynamic risk register;
• interface note for structure and propulsion;
• recommendations for next TRL.

Use TRL logic

At TRL 1, the aerodynamicist explores principles and identifies feasible concepts.

At TRL 2, they compare configurations, calculate first-order performance and define credible geometry ranges.

At TRL 3, they validate key assumptions through simulation, scaled models or structured numerical testing.

Collaborative engineering best practices for Bee projects recommend identifying the TRL level in deliverables, attaching evidence of progress, documenting input data and constraints, exporting open formats, and ensuring that future teams can reproduce or extend the work.

Make assumptions visible

An aerodynamic result without assumptions is almost useless. Each calculation should state:

• mass used;
• altitude;
• speed;
• air density;
• Reynolds number;
• Mach number;
• configuration;
• flap setting;
• CG assumption;
• solver or formula;
• safety factor;
• limitations.

This is what allows peer review. It also prevents future teams from repeating work without understanding why earlier decisions were made.

8. Tools used by aerodynamicists in Bee projects

The tool is not the engineering. It is only a means to test an assumption. Still, tool selection matters.

CAD and geometry tools

Tools such as Onshape or Blender can support geometry creation, collaborative design and model sharing. The aerodynamicist should ensure that geometry is clean, simplified where necessary, and suitable for simulation.

CFD and simulation tools

CFD tools can help visualize pressure fields, velocity vectors, separation zones and drag tendencies. However, CFD must be used carefully. The aerodynamicist must document:

• geometry simplifications;
• mesh strategy;
• boundary conditions;
• turbulence model;
• convergence criteria;
• reference values;
• result interpretation.

A CFD image without setup documentation should not be treated as proof.

Data and visualization tools

For projects such as GPS 4D, the aerodynamicist may also interact with trajectory, weather and mission-optimization data. GPS 4D-type projects show that future aerodynamicists will increasingly work with data engineers, software developers and simulation architects.

9. Typical aerodynamic workflow for a Bee student team

A recommended workflow for a Bee aerodynamic team is as follows.

Step 1 — Understand the mission

Read the project history, previous reports, CAD models and wiki pages. Identify the aircraft mission, payload, target range, expected speed and operational constraints.

Step 2 — Rebuild the assumptions

Create a one-page aerodynamic assumptions sheet. Do not accept inherited values blindly. Verify mass, wing area, speed, altitude and airfoil choices.

Step 3 — Perform first-order calculations

Estimate lift, drag, stall speed, wing loading, aspect ratio and tail volume. Compare results with similar aircraft or previous Bee studies.

Step 4 — Identify contradictions

Look for inconsistencies: wing too small, tail too large, unrealistic cruise speed, excessive drag, centre-of-gravity issue, engine placement problem or structural incompatibility.

Step 5 — Propose configuration options

Do not present only one solution. Compare at least two or three credible alternatives, with advantages, drawbacks and next tests.

Step 6 — Simulate selectively

Use CFD or numerical tools only after first-order calculations are coherent. Simulate the most important uncertainties first.

Step 7 — Transfer data to other teams

Give structure teams load cases, propulsion teams installation constraints, project managers risk items, and documentation teams clear figures and captions.

Step 8 — Publish and prepare continuity

Store files in open formats, write a README, add a CHANGELOG, include version numbers and publish validated results on the CollaborativeBee Wiki or shared repository.

10. What makes a good aerodynamicist?

A good aerodynamicist combines physics, curiosity and humility.

They know that early calculations are approximate, but they also know that approximate does not mean careless. They can explain why a model is useful, where it fails, and what evidence is needed next.

A good aerodynamicist:

• questions inherited assumptions;
• writes down every hypothesis;
• works with structure and propulsion teams;
• compares alternatives instead of defending one idea too early;
• understands that stability is as important as lift;
• cares about manufacturability and maintenance;
• transforms simulations into decisions;
• communicates clearly with non-specialists;
• keeps the project reusable for future teams.

In collaborative engineering, this last point is essential. Under the Lesser Open Bee License 1.3, technical documentation and project work are part of a shared engineering continuity.

11. Why students should join aerodynamic and aircraft design projects

Aerodynamics is one of the most exciting ways to enter aerospace engineering because it brings together theory, design and reality.

Students who join an aerodynamic work package learn how to:

• transform equations into aircraft geometry;
• connect physics with mission requirements;
• use CAD and simulation tools responsibly;
• understand why aircraft look the way they do;
• work with structural, propulsion and software teams;
• present technical results to project stakeholders;
• contribute to open-source engineering documentation;
• build a portfolio of real aerospace design work.

Bee projects are especially valuable because they expose students to long-term, multi-school, multi-generation engineering. A student does not simply complete an isolated assignment; they contribute to a technical lineage. Their work can be reviewed, reused, challenged and improved by future teams.

This is close to how real aerospace companies and research programs work. Aircraft design is not a solo activity. It is a negotiation between disciplines, constraints and evidence.

12. Recommended wiki deliverables for an aerodynamic work package

Each aerodynamic team should publish the following items:

Deliverable	Purpose
Aerodynamic assumptions sheet	Shared baseline for all calculations
Airfoil comparison	Justifies profile selection
Wing sizing note	Explains surface, span, aspect ratio and taper
Tail sizing note	Documents stability assumptions
Drag polar estimate	Supports performance and fuel-burn studies
CFD setup report	Ensures simulation reproducibility
Load-case summary	Transfers useful data to structure team
Interface note	Links aero with propulsion, structure and operations
Risk register	Tracks uncertain aerodynamic assumptions
Next-TRL recommendations	Helps future teams continue efficiently

Each file should include a title, project name, TRL level, date, version, assumptions, tools used, source files, output files and known limitations.

13. Practical checklist for aerodynamic deliverables

Before publishing an aerodynamic deliverable, the team should verify that it includes:

• project name;
• TRL level;
• version number;
• date of publication;
• authorship by team or institution, without unnecessary personal attribution on public pages;
• aircraft configuration studied;
• mission assumptions;
• mass assumptions;
• speed and altitude assumptions;
• aerodynamic model used;
• tool used;
• source files;
• open export format;
• key results;
• limits of validity;
• interface consequences for structure, propulsion and project management;
• recommendations for future teams;
• license reference.

14. Conclusion

The aerodynamicist is not a decorative role added after the aircraft has been drawn. They are one of the first engineers who must challenge the concept.

In Bee projects, this role is even more important because the aircraft concepts are unconventional: detachable fuselage aircraft, container-carrying cargo aircraft, hybrid VTOLs and 4D navigation systems. These projects require engineers who can think across disciplines, communicate clearly and document their work for future teams.

For students, becoming an aerodynamicist in a Bee project is an opportunity to experience real upstream aircraft design: uncertain data, evolving requirements, imperfect models, interdisciplinary trade-offs and the satisfaction of turning a bold idea into a more credible aircraft.

Aerodynamics is where imagination meets the atmosphere. It is where a concept begins to prove whether it deserves to fly.

Internal references

• Bee-Plane collaborative project documentation and aerodynamic work package notes.
• ISO-Plane TRL2 final documentation and aerodynamic study notes.
• Mini-Bee technical documentation on VTOL architecture, rotor performance, power chain and stabilization.
• GPS 4D collaborative project documentation on trajectory optimization, 3D visualization and airspace constraints.
• Lesser Open Bee License 1.3.
• Best Practices for Lesser Open Bee License 1.3 Users.
• Best Practices for Engineers on Project Management.
• Best Practices for Collaborative Engineering Deliverables, Bee Projects TRL 1–3.

License reference

Task achieved under the Lesser Open Bee License 1.3 Chapter 2 Open source – © Coordinator Technoplane SAS.