01
Research organisation
Defining research questions, assumptions, methods, and technical priorities.
Development roadmap
A measured path from concept toward physical validation.
AICA follows a phased engineering programme designed to reduce uncertainty through analysis, simulation, subsystem development, integration, and future representative testing.
The roadmap describes programme direction rather than guaranteed delivery dates. Each phase depends on evidence, resources, technical outcomes, and the successful completion of earlier work.
Current programme stage
Research · Architecture · Validation Preparation
Current focus
Building the engineering basis for progressive validation.
02
System architecture
Developing the relationships between propulsion, energy, control, safety, structures, and software.
03
Simulation planning
Preparing analytical, numerical, and digital models to compare candidate engineering approaches.
04
Validation preparation
Defining subsystem tests, measurement needs, evidence standards, and future decision gates.
Development phases
Engineering progress is conditional and sequential.
Phase 01
2014 — Present
Concept & Research
Develop the core concept, engineering assumptions, candidate architectures, and long-term research direction.
Representative work
- —calculations
- —concept studies
- —architecture exploration
- —research questions
- —documentation
- —feasibility analysis
Phase 02
Simulation & Analysis
Use analytical models and numerical simulation to evaluate engineering assumptions and compare alternative architectures.
Representative work
- —CFD planning and studies
- —structural analysis
- —energy-system modelling
- —control-system simulation
- —trade studies
- —uncertainty analysis
Phase 03
Subsystem Development & Bench Testing
Future programme stage
Develop and physically evaluate individual subsystems before vehicle-level integration.
Representative work
- —component prototypes
- —thermal tests
- —structural tests
- —control hardware testing
- —energy-system tests
- —instrumentation development
Phase 04
Integration & System Validation
Future programme stage
Integrate major subsystems and evaluate interfaces, control behaviour, safety logic, and system-level operation.
Representative work
- —integrated test rigs
- —hardware-in-the-loop
- —interface validation
- —fault-response testing
- —ground-system testing
Phase 05
Flight Demonstrator
Future programme stage
Create a representative demonstrator for controlled ground and later flight testing.
Representative work
- —integrated demonstrator
- —ground testing
- —incremental flight envelope
- —measured performance
- —acoustic measurement
- —handling and control assessment
Phase 06
Pre-production & Certification Preparation
Future programme stage
Translate validated engineering into repeatable manufacturing, formal compliance work, and production preparation.
Representative work
- —design maturation
- —manufacturing planning
- —quality systems
- —compliance evidence
- —certification strategy
- —production readiness
Evidence maturity
Confidence should grow as the programme moves from models to hardware.
01
Conceptual
Supported by
- — assumptions
- — calculations
- — architecture reasoning
- — feasibility studies
02
Simulated
Supported by
- — analytical models
- — numerical simulation
- — digital system models
- — comparative studies
03
Bench validated
Supported by
- — component tests
- — subsystem tests
- — physical measurements
- — repeatable experiments
04
Integrated validation
Supported by
- — system rigs
- — hardware-in-the-loop
- — integrated ground testing
- — interface verification
05
Vehicle measured
Supported by
- — representative prototype testing
- — ground testing
- — flight testing
- — direct performance measurement
Performance targets are not measured vehicle capabilities until supported by representative physical testing.
Decision gates
Each stage must earn the next.
Gate A
Concept coherence
Question
Is the architecture internally consistent and technically worth deeper investigation?
Gate B
Model credibility
Question
Do analytical and simulation results support continued development?
Gate C
Subsystem viability
Question
Do physical subsystem tests support integration?
Gate D
Integrated system readiness
Question
Can the combined system proceed safely toward demonstrator testing?
Gate E
Vehicle evidence
Question
Do measured results support further maturation, compliance work, and production planning?
Roadmap principles
Progress follows evidence, not calendar pressure.
01
No fixed promises
Future dates depend on engineering outcomes, resources, and validation results.
02
Risk reduction
Each phase should reduce a specific class of technical uncertainty.
03
Evidence before claims
Published capability statements should match the maturity of supporting evidence.
04
Revision is expected
The roadmap may change when new engineering evidence changes programme priorities.
Explore the work behind the roadmap.
Research defines the questions, documentation records the reasoning, and the engineering journal preserves the programme history.