5 kN-Class Liquid Engine Demonstrator

Published by APEX

Demonstrator architecture

These entries are taken from APEX's own Hardware page, with their status. They describe the architecture of the demonstrator, not tested performance.

Thrust classBuilt
5 kN class
Engine cycleBuilt
Single-shaft gas-generator cycle
CoolingBuilt
Regenerative cooling
IgnitionBuilt
Spark-augmented ignition
Engine controlBuilt
Integrated electronic control unit (ECU)
Development statusBuilt
Prototype / technology demonstrator
Active throttle controlPlanned
Active throttle control is planned future development.

Performance figures are not repeated here until APEX confirms whether each is a measured value or a design target. APEX’s own Hardware page lists further specifications. APEX Hardware page (opens in a new tab)

How APEX builds

Manufacturing-led development

In APEX's own words, from its Development & Testing page.

Machined and fabricated metal components laid out on a dark bench, including flanged plates, bearings and small fittings. — Fig. 09APEX engineering hardware: components during build.

Rapid development

Design to hardware, quickly enough to learn from it.

APEX states that it moves from engineering design to physical hardware in as little as two months.

Manufacturing independence

Conventional, accessible processes.

APEX's published approach relies on conventional, accessible manufacturing processes, including CNC tube bending, orbital TIG welding and induction brazing.

APEX deliberately avoids dependence on metal additive manufacturing, imported metal powders and proprietary production infrastructure.

Built for iteration

Speed, iteration and control.

APEX describes a manufacturing-led development process built around speed, iteration and greater control over how its hardware is designed and produced.

Source: apexrocketsystems.com — Development & Testing

Engine development story

From requirement to verified engine

The engineering lifecycle an engine passes through. It describes what happens and what evidence it leaves — not how to build propulsion hardware.

Mission needEngineer · The job the engine must do for the vehicle.
Engine requirementsEngineer · Verifiable statements of thrust class, operation, interfaces and safety.
ArchitectureEngineer · The cycle and functional blocks chosen to meet them.
Subsystem definitionEngineer · Each block's requirements and interfaces.
AnalysisEngineer · First-order performance, thermal and structural margins.
SimulationEngineer · Behaviour explored across operating scenarios.
Detailed designBuild · Drawings, models and bills of material under configuration control.
ManufacturingBuild · Parts made with recorded processes.
InspectionProve · Parts shown to match their drawings.
AssemblyBuild · Built to a recorded configuration.
InstrumentationBuild · Sensors fitted, calibrated and mapped to channels.
Component testProve · Individual parts and assemblies tested on their own.
Engine testProve · The integrated engine tested to a written objective.
Data correlationImprove · Measured results compared with prediction.
Engineering decisionImprove · Accept, investigate or change — decided by APEX.
IterationImprove · A new baseline, and the next test.