ETH Zurich Focus Project · 2026/27

Autonomytakes flight.

Mission-defined drones, generated through a parametric design pipeline with minimal manual iteration.

Scroll to enter

Specify the mission.

Generate the aircraft.

BOREAS is building a design-automation pipeline that translates mission requirements into a purpose-built drone. Parameters replace repeated manual redesign, allowing the system to explore, evaluate and refine aircraft concepts with minimal human effort.

Mission in.

An aircraft emerges.

The interceptor is the first proof of the method: one demanding mission translated into a traceable aircraft. It is not the end state—it is the first visible point in a design space that can open toward many future configurations.

Development pipeline / 2026–27 Measured results remain TBD until validated
Design variablesTBDGeometry · propulsion · structures
Candidates / runTBDGenerated and screened
Evaluation stackTBDCFD · FEA · controls · mission
Validation statusTBDSimulation → bench → flight
Human authority

People define the mission, constraints and acceptance criteria. Automation carries the repetitive exploration while decisions remain reviewable.

Mission to geometry.

The first proof. Not the final form.

The visualizer below generates interceptor concepts only. The interceptor is BOREAS’s proof of concept: a focused aircraft used to prove that mission requirements can drive geometry through the automated pipeline.

Once that method is validated, the interceptor becomes a doorway—not a limitation. Change the mission and the same parametric foundation can continuously modify range, payload, endurance, propulsion and geometry, opening a family of purpose-built aircraft without restarting from zero.

BOREAS / INTERCEPTOR POC-01Ready for mission input
Mockup onlyINTERCEPTORProof of concept · doorway to mission-defined variants
Parametric previewEngineering validity: TBD
BOREAS autonomous interceptor drone rendering

One aircraft.
Endless directions.

01 / First use case

The interceptor proves the method.

BOREAS begins with an interceptor as a focused proof of concept: a demanding mission with clear performance requirements against which the automated workflow can be tested.

02 / Parametric foundation

Not one fixed airframe.

The interceptor is one point in a wider design space. Connected parameters allow its geometry, propulsion and subsystems to evolve as the mission changes.

03 / Future configurations

A door to continuous modification.

Once the pipeline is validated, new requirements can lead toward new variants—different range, payload, endurance or operating environments—without starting the design process from zero.

Aircraft programme / mission profiles

One pipeline.
More than one drone.

The interceptor is the physical proof of concept. Further aircraft shown here are design-space directions, not validated products.

BOREAS interceptor proof-of-concept rendering
POC-01 · Active

Interceptor

Rapid-response configuration used to prove the automated workflow from mission input to engineering output.

Validation status · TBD
Direction 02 · TBD

Endurance

A future long-duration mission profile derived from the same connected parameter space.

Concept only · no performance claims
Direction 03 · TBD

Payload

A future payload-biased profile illustrating how a new mission can redirect geometry and propulsion.

Concept only · no performance claims

Capability needs

a compass.

BOREAS treats responsible system design, information security and publication practice as part of the engineering work. Our preliminary Ethics Statement sets out how we approach dual-use technology, human responsibility and responsible collaboration.

Read the Ethics Statement ↗

Built by students.

Driven by curiosity.

A multidisciplinary ETH Zurich team turning theory into a flying system.

The BOREAS team in the ETH Zurich workshop
BOREAS team · ETH Zurich
BOREAS team member portrait01

Team member

Role to be confirmed

“Personal saying goes here.”
BOREAS team member portrait02

Team member

Role to be confirmed

“Personal saying goes here.”
BOREAS team member portrait03

Team member

Role to be confirmed

“Personal saying goes here.”
BOREAS team member portrait04

Team member

Role to be confirmed

“Personal saying goes here.”
BOREAS team member portrait05

Team member

Role to be confirmed

“Personal saying goes here.”
BOREAS team member portrait06

Team member

Role to be confirmed

“Personal saying goes here.”
BOREAS team member portrait07

Team member

Role to be confirmed

“Personal saying goes here.”
BOREAS team member portrait08

Team member

Role to be confirmed

“Personal saying goes here.”

Names, roles and personal sayings can be added as soon as the final team list is confirmed.

There is no fixed playbook.

Build what comes next.

BOREAS brings together people who want to turn modelling, hardware and flight testing into one working system. Roles and application dates are still being defined; expressions of interest are welcome now.

Interest list openFormal roles / dates · TBD
01 / Software

Design automation

Parametric CAD, optimization, data pipelines and engineering tooling.

02 / Hardware

Airframe + propulsion

Structures, aerodynamics, manufacturing and propulsion integration.

03 / Autonomy

Embedded systems

Controls, sensing, avionics, simulation and safety-oriented autonomy.

04 / Operations

Flight test

Test planning, instrumentation, validation, documentation and field operations.

Students · collaborators · future membersTell us where you want to contribute and what you want to learn.

Register your interest ↗

Open the process.

Learn how it flies.

Manuals, project context and selected video resources for anyone who wants to understand the reasoning behind a mission-defined aircraft.

BOREAS-specific YouTube links are prepared as replaceable slots until the official uploads are available.

From the workshop

Field notes.

Progress is shared.

Our ecosystem.

Operational partner

Police

Domain exchange for responsible protective applications.

Critical infrastructure

AKW

Application context for resilient infrastructure protection.

Future partner

Your organisation

Technology, expertise, equipment or financial support.

Supporting partners

TechnologyManufacturingSoftwareTestingMaterials
01 / 05