01
Concept development
Early ideas, design evolution, assumptions, and architecture exploration.
Engineering journal
A public record of how the AICA programme develops.
The AICA Engineering Journal records design evolution, architecture decisions, research observations, documentation milestones, and preparation for future validation.
Entries describe the state of the programme at the time they are published. Later engineering evidence may refine or replace earlier assumptions.
Programme record
Active · Continuously updated
Featured engineering records
Selected records from the programme.
Concept development
Version 1.0Concept Evolution
A look at how the AICA air mobility concept has evolved through research, architecture studies, simulation, and iterative engineering development.
Read engineering record →
Engineering architecture
Version 1.0Engineering Architecture
An overview of the integrated architecture connecting propulsion, energy, control, safety, structure, and software across the AICA platform.
Read engineering record →
Energy systems
Version 1.0Energy System Development
A closer look at the architecture, thermal management, power electronics, safety strategy, and modular development path of the AICA energy system.
Read engineering record →
Programme history
An engineering effort with a long development horizon.
- 01
2014
Confirmed programme origin
Concept and Research Begins
Initial concept development, calculations, architecture exploration, and long-term investigation of a new approach to vertical mobility.
- 02
Recent programme stage
Programme record
Structured Engineering Documentation
The programme moved toward a more formal documentation system covering research questions, architecture, development methods, roadmap, and evidence maturity.
- 03
Current
In preparation
Simulation, Architecture, and Validation Preparation
Current work focuses on research organisation, system architecture, simulation planning, technical documentation, and preparation for progressive subsystem validation.
- 04
Future
Future programme stage · Planned
Progressive Physical Validation
Planned work includes subsystem testing, integration, demonstrator development, ground testing, and later representative vehicle testing.
Journal categories
Different records serve different engineering purposes.
02
System architecture
Relationships between vehicle subsystems and major engineering decisions.
03
Research notes
Questions, methods, simulation observations, and technical trade studies.
04
Programme updates
Documentation milestones, development progress, and roadmap changes.
05
Validation records
Future subsystem, bench, integration, and prototype test records.
Future programme categoryWhy the journal exists
Engineering history should not disappear when assumptions change.
01
Context
Each entry should describe the programme state and available evidence at the time.
02
Traceability
Major decisions and changes should remain connected to their engineering reasoning.
03
Revision
New evidence may refine earlier conclusions without erasing the development history.
04
Limitations
Uncertainty, assumptions, and validation gaps should be stated where relevant.
Journal entries are engineering records, not proof of validated vehicle performance.
Follow the programme through its engineering record.
Research defines the questions, documentation records the reasoning, and future testing will determine the measured capabilities of the platform.