Eos-0

Single-prop UAV with active fin control

  • Preliminary design since October 2026
  • Flies the Kari flight computer first
  • Nothing built or flown yet
Eos-0 placeholder: photos and CAD coming
[KADEN: hero photos or CAD renders]

Goal and maneuvers

What Eos-0 is for

Eos-0 is the first vehicle in my Eos program: a single-prop UAV with active fin control, designed for testing. A 4 in body carries one lift motor with a 16 to 20 in propeller and four fins in the prop wash that steer it. It is also the first vehicle to fly Kari, the flight computer I am designing for Eos.

[KADEN: the goal in your words, and the maneuvers Eos-0 should perform]

Timeline and process

Preliminary design

  1. Oct to Dec 2026

    Eos-0

    Single-prop test UAV with active fins: linkage, mechanical, Kari, propulsion and the controls model, designed together, then static tests.

  2. Jan to Feb 2027

    Eos-1

    L1 high-power rocket (planned).

  3. Feb to Mar 2027

    Eos-2

    L2 rocket with active fins (planned).

The design is one loop: thrust, mass properties and fin forces go into the controls model, the model shows whether the vehicle can perform the maneuvers, and I change the design until it can.

[KADEN: the steps and dates inside Eos-0]

Linkage design

The main driver

Each fin needs ±20° of deflection, and there is very little space for the linkage that drives it. That space limit shapes the design more than anything else on the vehicle. I size the parts with straightforward load calculations.

[KADEN: the linkage layout, the fin load case and the margin]

Mechanical design

Apart from the linkage, the mechanical design is straightforward.

[KADEN: structure, fin station, couplers and landing legs, with CAD]

Electrical design

Developing Kari

The electronics are built around Kari, a PCB flight computer I am designing for the Eos vehicles. Its sensors are set by what the controls model reasonably needs.

[KADEN: wiring overview and the power path from the battery]

Controls design

Brief, because of ITAR

Because of ITAR I can't go into specifics here. The general approach: I model the vehicle in MATLAB (Simulink with the Aerospace and Control toolboxes), put in its numbers (CG, inertias, thrust, and fin forces from CFD) and check whether it can perform the maneuvers I am attempting. Then I change the design, update the numbers and run it again.

The model will later become a pure controls model for the flight computer. For now it is a sanity check on the design.

Propulsion design

Thrust
A first estimate of the requirement, iterated with the controls model.
Propeller
16 to 20 in, with an airfoil that is published online.
ESC
Rated for the current the motor draws.
Battery
6S.
Motor
Chosen on kV and price.
[KADEN: the thrust requirement and the chosen motor, propeller, ESC and battery]

CFD and aero analysis

CFD gives me three things: the drag, the size of the vanes, and the fin forces that go into the controls model.

[KADEN: method, cases and results]

Testing

Planned

Static tests are planned for:

  • Thrust
  • Motor time constants
  • Possibly fin forces
[KADEN: the test stand, instruments and what each test decides]

Ground station telemetry

Planned

I will build the ground station in Cosmic, my C++ engine, where SF_Telem for Shear Force already runs.

[KADEN: what the ground station will show and record]