How to Write a Market Study for Upstream Aerospace Projects

How to Write a Market Study for Upstream Aerospace Projects

Summary

This page provides a practical method for writing a market study for early-stage aerospace projects, especially during TRL 1 to TRL 3 phases. It is inspired by Bee ecosystem projects such as Bee-Plane, ISO-Plane, Mini-Bee and GPS 4D, and by the 2022 ESTACA Architecture Bee-Plane presentation, which included an early market study, a competitive watch, price assumptions, sales scenarios and positioning arguments for the detachable-fuselage aircraft concept.

Reference case: 10052022 Soutenance ESTACA Architecture – Bee-Plane Architecture – ESTACA – 10 May 2022.

File:10052022 Soutenance ESTACA Architecture.pdf

A market study for an upstream aerospace project is not a commercial brochure. It is a structured decision-making document. Its purpose is to answer a simple but difficult question:

Does this aircraft, system or technology solve a real problem for identifiable users, in a market where technical feasibility, economic value and operational adoption can realistically converge?

For Bee projects, this question is essential because the concepts are often ambitious and unconventional: detachable fuselages, ISO-container aircraft, hybrid VTOLs, 4D navigation systems or collaborative data architectures. The market study must therefore connect engineering choices with real users, real missions, real budgets and real operational constraints.

1. Why a market study matters in upstream aerospace design

In early aerospace design, teams naturally focus on technical feasibility: wings, structures, propulsion, mass, aerodynamics, CAD models, simulations and control systems. These are essential. However, an aircraft concept does not become useful only because it can theoretically fly. It becomes valuable when it solves a problem better than existing solutions.

A market study helps the team understand:

• who may use the aircraft or system;
• what mission the product is designed to perform;
• what current solutions already exist;
• why those solutions are insufficient;
• how much users may be willing to pay;
• what operational savings or performance gains can be expected;
• what barriers may prevent adoption;
• what technical requirements are market-driven rather than purely engineering-driven;
• which configuration should be prioritized for the next TRL phase.

In upstream projects, the market study is not expected to be perfectly accurate. It is expected to be transparent, traceable and useful for design decisions.

2. The market analyst as a system thinker

The person preparing the market study should not work separately from the engineering team. Like the aerodynamicist or the systems engineer, the market analyst connects several dimensions of the project.

Market-study dimension	Link with aircraft design
Customer need	Defines the mission profile, payload, autonomy, cabin or cargo configuration
Competitor analysis	Identifies what must be better, cheaper, faster, cleaner or more flexible
Pricing	Influences cost targets, production assumptions and business model
Operations	Affects maintenance, turnaround time, airports, ground equipment and crew
Regulation	Shapes certification path, market access and deployment timeline
Environment	Impacts fuel strategy, emissions, noise and public acceptance
Risk	Helps identify technical, financial, industrial and adoption barriers
TRL planning	Helps decide which proof is needed next

A good market study transforms a broad idea into a set of design priorities. It tells the technical team which performance characteristics matter most and which features are secondary.

3. Starting point: the Bee-Plane ESTACA Architecture example

The 2022 ESTACA Architecture Bee-Plane presentation is a useful reference because it does not treat the market study as an isolated appendix. It links market positioning with architecture, fuselage structure, landing gear, propulsion and the detachable Basket concept.

The presentation introduced Bee-Plane as an innovative project aiming to reduce air-transport costs and compete with low-cost airlines. It positioned the aircraft as a short- and medium-haul aircraft with dimensions close to an A321, but with a detachable architecture composed of:

• the Bee: the carrier structure including cockpit, engines and wings;
• the Basket: the passenger and/or cargo module.

The market-study section then addressed several key questions:

• Where does Bee-Plane stand compared with competitors?
• Which detachable-fuselage or modular-aircraft concepts already exist?
• What are their advantages and disadvantages?
• Which markets could be relevant?
• What could be the selling price of the Bee and the Basket?
• What 10-year sales objectives could be imagined?
• How could maintenance costs compare with conventional aircraft?

This is a good model for student teams because it shows that even a preliminary market study can already support engineering choices. For example, if the value proposition is faster turnaround and lower operating cost, then the structure, attachment system, maintenance strategy and airport compatibility become market-driven requirements.

4. What is a market study in TRL 1–3?

At TRL 1 to TRL 3, the market study is not a final business plan. It is a structured exploration of the project’s economic and operational relevance.

TRL 1 — Opportunity exploration

At TRL 1, the market study should identify the problem and the potential users. The goal is to understand whether the concept addresses a real need.

Typical questions:

• What problem are we trying to solve?
• Who experiences this problem?
• What existing solutions are used today?
• Why are these solutions insufficient?
• What mission scenarios justify the concept?
• What early indicators suggest that a market may exist?

TRL 2 — Concept positioning

At TRL 2, the market study should compare concepts, refine target segments and connect market needs with technical requirements.

Typical questions:

• Which customer segments are most promising?
• Which competitors or substitutes should be monitored?
• What technical parameters matter most to users?
• What price range may be acceptable?
• What operational gains could justify adoption?
• Which configuration should be selected for deeper study?

TRL 3 — Evidence and validation

At TRL 3, the market study should support a more robust value proposition and define what evidence is needed for industrial partners.

Typical questions:

• Which use case should be demonstrated first?
• What quantitative evidence is required?
• What are the main adoption barriers?
• What industrial partnerships are needed?
• What certification and deployment path is realistic?
• What is the minimum viable aircraft, system or demonstrator?

5. Recommended structure of a market study

A clear market study should follow a logical structure. The following structure can be reused by Bee project teams.

Section	Purpose
Executive summary	Give the key conclusions in one page
Project description	Explain the concept, mission and technical singularity
Problem statement	Identify the need addressed by the project
Target users	Define who could use or buy the solution
Market segmentation	Separate civil, military, cargo, medical, emergency or data markets
Competitive watch	Compare existing aircraft, systems or concepts
Substitutes	Identify non-aircraft alternatives or indirect competition
Value proposition	Explain why the project is useful and different
Market size	Estimate demand with transparent assumptions
Pricing assumptions	Propose early price ranges and cost logic
Operating economics	Compare operating cost, maintenance, fuel, turnaround or productivity
Regulatory constraints	Identify certification and market-access barriers
Environmental impact	Evaluate emissions, noise and sustainability drivers
SWOT analysis	Summarize strengths, weaknesses, opportunities and threats
Porter analysis	Evaluate competitive forces and ecosystem constraints
Risks and uncertainties	List what may invalidate the market hypothesis
Recommendations	Provide design and TRL guidance for the next team

6. Step 1 — Define the project and its mission

A market study must begin with a precise description of the project. Avoid vague sentences such as “an innovative aircraft for the future”. Instead, define the aircraft or system through its mission.

For example:

• Bee-Plane: medium-range aircraft with detachable fuselage, aiming to reduce turnaround time and improve operational flexibility.
• ISO-Plane: cargo aircraft designed to transport a 20-foot ISO container and load or unload it autonomously.
• Mini-Bee: two-seat hybrid VTOL designed for rapid access to difficult areas, medical missions or emergency transport.
• GPS 4D: collaborative navigation and trajectory-optimization system for drones, VTOLs, aircraft and aerial vehicles.

A good project description includes:

• mission type;
• payload;
• range or autonomy;
• target speed;
• operating environment;
• user type;
• infrastructure needs;
• main technical innovation;
• expected economic advantage.

7. Step 2 — Identify the real problem

A market study should not start from the solution. It should start from the problem.

For aerospace projects, problems may include:

• airport turnaround time;
• high operating cost;
• poor cargo flexibility;
• lack of access to remote areas;
• medical emergency delays;
• high fuel consumption;
• dependence on ground infrastructure;
• insufficient airspace coordination;
• inefficient maintenance;
• difficulty integrating new mobility systems into existing regulation.

The problem must be written in operational terms. A good problem statement describes what happens today, who is affected, and why current solutions are not sufficient.

Example:

Regional cargo operators can transport standard containers by sea, road or large aircraft, but they lack a compact aircraft capable of carrying an ISO 20-foot container directly to smaller airports while reducing external ground-handling requirements.

This type of statement immediately creates a bridge between market need and technical design.

8. Step 3 — Define customer segments

The word “market” is too broad. The team must identify specific user groups.

Possible aerospace customer segments include:

Segment	Possible needs
Airlines	Lower operating cost, faster turnaround, modular cabins, higher utilization
Cargo operators	Payload flexibility, container compatibility, fast loading, route profitability
Humanitarian organizations	Access to remote zones, medical evacuation, emergency logistics
Military operators	Tactical transport, modular payloads, autonomous loading, rugged operations
Regional airports	More routes, lower infrastructure requirements, improved logistics
Emergency services	Rapid intervention, VTOL access, medical equipment transport
Industrial operators	Transport of high-value goods, spare parts, urgent maintenance logistics
Urban air mobility operators	Route optimization, safety, noise management, digital coordination
Public authorities	Safety, regulation, environmental acceptability, territorial connectivity

Each segment should be evaluated separately. A project may be attractive for military logistics but not for commercial airlines. Another may work for emergency medical services but not for mass passenger transport.

9. Step 4 — Map the use cases

A use case is a concrete mission scenario. It should describe how the aircraft or system would be used.

A good use case includes:

• departure point;
• destination;
• payload;
• user;
• mission frequency;
• time constraint;
• infrastructure constraint;
• weather or regulatory constraint;
• expected benefit.

Example use cases:

• Bee-Plane: passenger Basket prepared while the Bee is flying another mission, reducing ground immobilization time.
• ISO-Plane: direct delivery of an ISO container to a small regional airport without heavy external loading equipment.
• Mini-Bee: rapid medical intervention in a difficult-access area after a natural disaster.
• GPS 4D: dynamic rerouting of drones and VTOLs around weather, airspace restrictions and traffic conflicts.

Use cases are essential because they prevent the market study from becoming too abstract.

10. Step 5 — Conduct a competitive watch

The competitive watch identifies projects, aircraft, companies or technologies that address similar needs.

In the 2022 Bee-Plane ESTACA Architecture presentation, the competitive watch compared detachable or modular aircraft concepts from Airbus, AKKA, EPFL and other sources. It listed advantages such as proven aircraft bases, simple Basket installation, flexible modules or limited ground handling, and disadvantages such as baggage limitations, pressurization questions, airport adaptation needs, loading time or inability to fly without the fuselage.

This method can be reused for any upstream aerospace project.

Competitor or reference	Advantages	Disadvantages	Lessons for our project
Competitor A	Proven aircraft base, known technology	Limited modularity	Our concept must prove flexibility without adding excessive complexity
Competitor B	High payload or large lifting surface	Requires major airport infrastructure	Infrastructure compatibility may be a differentiator
Competitor C	Strong digital platform	Limited certification maturity	Certification strategy must be addressed early
Conventional solution	Reliable and already certified	Less optimized for the target mission	The new concept must quantify its operational gain

The goal is not to prove that competitors are bad. The goal is to understand what they teach us.

11. Step 6 — Identify substitutes, not only direct competitors

In aerospace, the strongest competitor is not always another aircraft. It may be a truck, a ship, a train, a helicopter, a drone, a software platform or a change in logistics organization.

For example:

• ISO-Plane competes not only with cargo aircraft, but also with road, rail and maritime container transport.
• Mini-Bee competes not only with helicopters, but also with ambulances, drones, emergency vehicles and local medical infrastructure.
• GPS 4D competes not only with aviation navigation systems, but also with air-traffic-management platforms, drone UTM systems and existing GIS tools.
• Bee-Plane competes not only with aircraft manufacturers, but also with airline operational improvements, airport automation and low-cost airline business models.

A serious market study must include substitutes because customers compare solutions based on mission value, not engineering categories.

12. Step 7 — Build the value proposition

The value proposition explains why the concept matters.

A weak value proposition says:

This aircraft is innovative and modular.

A stronger value proposition says:

This aircraft reduces ground turnaround time by separating the flying carrier from the passenger or cargo module, allowing operators to prepare the next mission while the carrier is already in operation.

The value proposition should answer:

• What pain point is reduced?
• What cost is reduced?
• What revenue opportunity is created?
• What operational delay is avoided?
• What infrastructure constraint is removed?
• What mission becomes possible?
• What environmental or safety benefit is gained?

For Bee projects, value propositions often rely on one or more of the following:

• modularity;
• faster turnaround;
• lower operating cost;
• mission flexibility;
• reduced dependence on infrastructure;
• improved emergency access;
• lower environmental impact per useful mission;
• open-source collaborative development;
• continuity between student cohorts and industrial partners.

13. Step 8 — Estimate the market size carefully

Market sizing is difficult in early aerospace projects. It should be done with humility and transparent assumptions.

There are three useful levels:

Total Addressable Market — TAM

The largest possible market if the concept could serve all relevant users.

Example: global regional cargo aircraft demand, global emergency VTOL demand, global urban air mobility software market.

Serviceable Available Market — SAM

The portion of the market realistically compatible with the concept.

Example: cargo operators using small airports and needing container-compatible aircraft.

Serviceable Obtainable Market — SOM

The portion the project could realistically target in an early deployment scenario.

Example: a small number of pilot customers, regional operators or public-service missions.

A student team should avoid exaggerated market claims. Instead, it should show assumptions:

• number of potential operators;
• fleet size;
• renewal rate;
• target regions;
• mission frequency;
• adoption rate;
• price range;
• regulatory timeline.

14. Step 9 — Define pricing assumptions

At upstream stage, pricing is approximate. Still, a market study must propose early assumptions because price strongly affects feasibility.

The 2022 Bee-Plane market section included separate price assumptions for the Bee and the Basket, then derived scenario values for different configurations. This is a useful approach for modular aircraft because the business model may not be based on a single aircraft price.

Pricing assumptions may include:

• aircraft sale price;
• module or Basket sale price;
• leasing model;
• maintenance contract;
• software subscription;
• mission-based pricing;
• retrofit or upgrade cost;
• training and support cost.

For modular concepts, the study should ask:

• Is the carrier sold separately from the module?
• Can one carrier serve several modules?
• Who owns the modules?
• Does the operator buy, lease or share them?
• How does modularity affect maintenance cost?
• How does modularity affect fleet utilization?

15. Step 10 — Analyze operating economics

A market study must go beyond purchase price. Aerospace customers care about total cost of ownership and mission economics.

Important operating-cost elements include:

• fuel or energy cost;
• maintenance cost;
• crew cost;
• airport fees;
• ground-handling cost;
• insurance;
• spare parts;
• training;
• downtime;
• utilization rate;
• turnaround time;
• payload revenue;
• residual value.

For Bee-type concepts, the following indicators are useful:

Indicator	Why it matters
Cost per flight hour	Measures operational competitiveness
Cost per passenger-kilometre	Useful for passenger concepts
Cost per tonne-kilometre	Useful for cargo concepts
Turnaround time	Key for modular or detachable concepts
Fleet utilization	Shows how often the expensive flying asset is used
Maintenance downtime	Impacts availability and revenue
Infrastructure cost	Determines airport compatibility
Fuel burn per mission	Links market, aerodynamics and environmental impact

A good market study should clearly state which costs are estimated, which are unknown, and which require future technical work.

16. Step 11 — Link market study with technical requirements

The most useful market studies directly influence engineering.

Examples:

Market finding	Technical consequence
Operators need short turnaround	Design detachable modules, fast attachment, easy inspection
Cargo market needs ISO compatibility	Define cargo-bay dimensions, floor strength, loading system
Emergency medical users need remote access	Prioritize VTOL capability, compact landing footprint, medical equipment layout
Airlines need low maintenance cost	Reduce part count, improve accessibility, modularize systems
Military users need rugged operations	Consider rough-field landing, autonomous loading, redundancy
Urban operators face noise constraints	Study rotor noise, flight paths and acceptable operating zones
Regulators require safety evidence	Plan certification logic and traceable verification

This is the main difference between a market study and a generic business presentation. The market study must create engineering requirements.

17. Step 12 — Study regulation and certification constraints

Aerospace markets are shaped by regulation. Even if a project has strong technical and economic potential, certification barriers may delay or prevent adoption.

The market study should identify:

• aircraft category;
• certification authority;
• expected certification basis;
• pilot requirements;
• maintenance requirements;
• airspace constraints;
• airport or vertiport constraints;
• noise regulation;
• environmental regulation;
• export-control issues;
• military or dual-use considerations;
• data and cybersecurity constraints for software systems.

For early-stage projects, the goal is not to solve certification, but to identify the certification path and its market impact.

18. Step 13 — Include environmental and social factors

Modern aerospace market studies must include environmental and social acceptability.

Key questions:

• What are the expected CO2 emissions per mission?
• Does the concept reduce or increase fuel consumption compared with alternatives?
• What is the noise impact?
• Does the aircraft require new infrastructure?
• Does it serve useful social missions such as medical access, disaster response or territorial connectivity?
• Does it create rebound effects, such as encouraging unnecessary air transport?
• Can the concept support lower-emission operations in the long term?

For upstream studies, the environmental section can be approximate, but it must be honest. If the aircraft is less efficient than competitors, the study should say so and recommend technical improvements.

19. Step 14 — Perform a SWOT analysis

A SWOT analysis summarizes internal and external factors.

Strengths	Weaknesses
Innovative architecture	Low technical maturity
Mission flexibility	Uncertain certification path
Potential operating-cost gain	Limited data at early TRL
Collaborative open-source documentation	Dependence on future industrial partners

Opportunities	Threats
Growing need for regional logistics	Strong existing aircraft manufacturers
Emergency and humanitarian applications	Regulatory delays
Modular operations and new business models	High development and certification cost
Cross-school and industrial collaboration	Market adoption uncertainty

A SWOT is useful only if it leads to decisions. Each weakness and threat should be connected to a mitigation action.

20. Step 15 — Use Porter’s Five Forces

Porter’s Five Forces can help structure the competitive environment.

Force	Aerospace interpretation
Competitive rivalry	Existing manufacturers, startups, alternative technologies
Threat of new entrants	Barriers from certification, capital, industrial capability
Bargaining power of suppliers	Engines, avionics, batteries, composite materials, software platforms
Bargaining power of customers	Airlines, public authorities, militaries and logistics operators often negotiate strongly
Threat of substitutes	Road, rail, maritime transport, helicopters, drones, digital optimization

For student teams, Porter’s analysis is useful because it highlights that technology alone is not enough. Industrial ecosystem, supply chain, customer power and substitutes can determine whether a project can survive.

21. Step 16 — Define risks and uncertainties

Every market study should include a risk table.

Risk	Probability	Impact	Mitigation
Market demand overestimated	Medium	High	Validate use cases with real operators and public data
Purchase price too high	Medium	High	Compare with existing aircraft and refine cost model
Operating cost not competitive	Medium	High	Improve fuel burn, maintenance assumptions and utilization model
Certification path unclear	High	High	Identify certification category and consult standards early
Infrastructure requirements too heavy	Medium	Medium	Prioritize compatibility with existing airports or logistics systems
Competitors mature faster	Medium	Medium	Focus on unique value proposition and niche entry market
Technical performance not achieved	Medium	High	Link market assumptions to aerodynamic, structural and propulsion validation
Environmental performance insufficient	Medium	High	Run lifecycle and mission-emission comparisons

The risk table should be reviewed during each project milestone.

22. Step 17 — Build scenarios

Aerospace projects are uncertain. Instead of presenting one forecast, the market study should build scenarios.

Conservative scenario

The project is adopted slowly, by a small number of specialized users. The first market is a niche: humanitarian logistics, military support, emergency services or regional cargo.

Central scenario

The project reaches a limited but credible commercial deployment. It serves several operators and demonstrates clear economic value in selected routes or missions.

Ambitious scenario

The project becomes a reference architecture or platform. It expands to multiple configurations, regions or mission types.

Each scenario should include:

• number of aircraft or systems;
• number of modules, if applicable;
• target customers;
• timeline;
• expected revenue;
• key assumptions;
• trigger conditions;
• risks.

23. Step 18 — Connect the study to TRL recommendations

The market study should end with recommendations for the next TRL.

Examples:

Market conclusion	TRL recommendation
The strongest market is regional cargo	Prioritize payload, loading system and cost per tonne-kilometre
The strongest market is emergency response	Prioritize availability, VTOL capability, medical layout and reliability
The main value is turnaround reduction	Demonstrate attachment, detachment and ground-operation time
The main risk is fuel burn	Prioritize aerodynamic and mass optimization
The main barrier is regulation	Build an early certification roadmap
The main uncertainty is customer willingness to pay	Prepare interviews and partner outreach

This is where the market study becomes useful for project management.

24. Common mistakes in student market studies

Mistake 1 — Starting with the solution instead of the problem

A market study should not begin by saying that the project is innovative. It should begin by explaining which problem exists and why current solutions are insufficient.

Mistake 2 — Confusing market size with reachable market

A large global aerospace market does not mean the project can capture it. Always distinguish TAM, SAM and SOM.

Mistake 3 — Ignoring substitutes

A cargo aircraft may compete with trucks and ships. A VTOL medical aircraft may compete with helicopters or improved ground response. A software tool may compete with existing operational procedures.

Mistake 4 — Using old figures without context

Old market forecasts can be useful, but they must be identified, dated and treated carefully. If a forecast comes from 2011 or 2022, the team must explain why it is still relevant or what has changed.

Mistake 5 — Presenting optimistic sales without assumptions

A sales objective is useful only if the assumptions are visible: customer type, fleet renewal, adoption rate, price, production capacity and timeline.

Mistake 6 — Separating market and engineering

If the market study does not influence the aircraft configuration, it is incomplete.

25. Recommended workflow for Bee project teams

Step 1 — Read previous work

Start with previous wiki pages, reports, presentations, CAD files and project notes. Identify what has already been studied and what assumptions were used.

Step 2 — Write the mission statement

Define the aircraft or system in one paragraph: user, mission, payload, range, operating environment and innovation.

Step 3 — List use cases

Write three to five concrete scenarios. Include one conservative use case and one ambitious use case.

Step 4 — Build the competitor table

Compare direct competitors, indirect competitors and substitutes.

Step 5 — Identify target users

Separate buyers, operators, passengers, regulators, maintainers and beneficiaries.

Step 6 — Estimate market size

Use transparent assumptions. Do not hide uncertainty.

Step 7 — Estimate price and operating economics

Build simple cost models. Make assumptions visible.

Step 8 — Link findings to technical requirements

Translate market findings into aircraft requirements.

Step 9 — Run SWOT and Porter analyses

Use them to identify risks and strategy, not just to fill pages.

Step 10 — Publish and prepare continuity

Write a clean wiki page, upload spreadsheets, include sources, document assumptions and recommend next actions.

26. Recommended deliverables for a market-study work package

Deliverable	Purpose
Market-study wiki page	Main public synthesis
Competitor benchmark table	Traceable comparison with existing solutions
Use-case catalogue	Concrete mission scenarios
TAM/SAM/SOM assumptions sheet	Transparent market-size logic
Pricing model	Early price and revenue assumptions
Operating-cost comparison	Total cost of ownership and mission economics
SWOT analysis	Strategic summary
Porter analysis	Competitive environment
Risk register	Market and adoption risks
TRL recommendation note	Design and validation priorities for future teams
Source list	Traceability and peer review

27. Practical checklist before publishing

Before publishing a market study, verify that it includes:

• project name;
• TRL level;
• date;
• version number;
• team or institution attribution;
• mission statement;
• target users;
• use cases;
• competitor table;
• substitutes;
• market segmentation;
• market-size assumptions;
• pricing assumptions;
• operating-cost assumptions;
• regulatory constraints;
• environmental considerations;
• SWOT analysis;
• Porter analysis;
• risks and uncertainties;
• technical consequences;
• recommendations for next TRL;
• source list;
• license reference.

28. Suggested page template

The following structure can be reused directly for a Bee project market-study page.

= Market Study – Project Name – TRL Level =

== Executive Summary ==
Short synthesis of the opportunity, target market and key recommendations.

== Project and Mission Description ==
What is the concept? What mission does it serve?

== Problem Statement ==
Which operational, economic or environmental problem is addressed?

== Target Users and Stakeholders ==
Who buys, operates, regulates, maintains or benefits from the system?

== Use Cases ==
Detailed mission scenarios.

== Market Segmentation ==
Civil, military, cargo, medical, emergency, software, data, etc.

== Competitive Watch ==
Direct competitors, indirect competitors and substitutes.

== Value Proposition ==
Why is the project useful, different and potentially adoptable?

== Market Size and Demand Assumptions ==
TAM, SAM, SOM and transparent assumptions.

== Pricing and Business Model ==
Sale price, leasing, maintenance, subscription or mission-based pricing.

== Operating Economics ==
Cost per mission, cost per hour, maintenance, energy, turnaround and utilization.

== Regulation and Certification ==
Market-access constraints and certification roadmap.

== Environmental and Social Impact ==
Emissions, noise, infrastructure, public acceptance and useful missions.

== SWOT Analysis ==
Strengths, weaknesses, opportunities and threats.

== Porter’s Five Forces ==
Competitive structure of the ecosystem.

== Risks and Uncertainties ==
What could invalidate the market hypothesis?

== Technical Consequences ==
How the market study changes the aircraft or system requirements.

== Recommendations for Next TRL ==
What should future teams test, model, validate or document?

== Sources ==
List of reports, presentations, datasets and public sources.

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

29. Conclusion

A market study is not a secondary task performed after the technical work. In upstream aerospace projects, it is one of the main tools for choosing the right technical direction.

For Bee projects, the market study helps teams avoid designing an elegant but irrelevant aircraft. It connects engineering effort with operational value. It explains why a detachable fuselage, a container-carrying aircraft, a hybrid VTOL or a 4D navigation system may deserve further development.

A strong market study does not need to predict the future perfectly. It must make assumptions visible, compare alternatives honestly, identify users precisely and translate market needs into technical priorities.

For students, writing a market study is a powerful way to understand the aerospace industry. It shows that aircraft design is not only about lift, mass and propulsion. It is also about customers, operations, infrastructure, regulation, cost, maintenance, environmental responsibility and long-term adoption.

The best aerospace projects are not only those that can fly. They are those that are useful enough to be built, operated, maintained, improved and trusted.

Internal references

• 10052022 Soutenance ESTACA Architecture – Bee-Plane Architecture – ESTACA – 10 May 2022.
• Bee-Plane collaborative project documentation.
• ISO-Plane TRL2 final documentation and market-study work.
• Mini-Bee technical and project-management documentation.
• GPS 4D collaborative project documentation.
• 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.