Vehicles & Programs

Aegis configurations are named for their engine count or capability tier:

Note: Configuration designations describe relative capability within the Aegis family. Precise performance specifications vary by test and mission profile. All configurations have demonstrated autonomous landing capability.

Aegis boosters use AutoLand autonomous guidance for reliable recovery:

• Descent Prediction: AutoLand calculates whether current trajectory can achieve vertical descent with available thrust.
• Throttle Control: Smooth throttle adjustments maintain controlled descent rate and landing envelope.
• Landing Accuracy: Guidance targets designated landing zones. Typical landing errors range from on-target to several kilometers depending on conditions.
• Touchdown Management: Final-approach phase aims for gentle vertical descent and manageable touchdown velocity.
• Proven Performance: 47+ successful recoveries across varied landing sites, environmental conditions, and payload scenarios.

See the AutoLand Engineering page for detailed guidance system documentation.

WSA is exploring advanced multi-booster recovery architectures:

Aegis development involved failures that drove important engineering improvements:

• Early Recovery Challenges: Initial tests showed that surviving descent and landing required more than structural design—active control and prediction were essential.
• Guidance Refinement: Early landing guidance produced inconsistent results. Throttle smoothing, descent prediction tuning, and altitude-management algorithms required iteration.
• Post-Landing Stability: Boosters occasionally tipped over after landing, damaging fins or engines. This drove development of better landing-gear design and touchdown-velocity management.
• Scaling Challenges: Moving from smaller to larger configurations revealed issues with fuel reserves, thrust-to-weight ratios, and guidance system margins.
• Environmental Factors: Water landings, rough terrain, and variable wind conditions required more robust guidance and better sensor reliability.

Each failure led to documented improvements. The 47+ successful recoveries represent learning accumulated through test flights and operational missions.

Operational Status: Aegis family is mature and operationally ready for regular missions.

• Recovery Capability: High reliability demonstrated across all tested configurations. Ready for frequent-flight operations.
• Crewed Certification: Preparing for certification testing to support crewed missions to KGOSS and beyond.
• Legacy Role: Aegis continues to serve existing mission requirements while Lyra development progresses for future high-capacity needs.
• Research Platform: AutoLand development and advanced recovery concepts use Aegis as the test bed for new guidance and control algorithms.

Lyra P-1E: Prototype 1 Experimental—the current development vehicle for the Lyra family.

• Status: Integration of primary systems underway. First flight testing planned.
• Configuration: Experimental prototype with flexible payload bay for various test loads.
• Role: Validation of Lyra booster architecture, staging separation, landing guidance, and autonomous-recovery procedures.
• Expected Outcome: Successful first flight will clear path for Lyra Selene production and scaling.

Development Timeline: P-1E first flight is the critical path item for Lyra program. Completion allows qualification testing and transition to operational Selene, Sol, and Astra variants.

Lyra development has explored various engine arrangements to optimize thrust, cost, and performance:

• Main Stage: Multi-engine arrangement (up to 21 engines on main stage in some concepts) to achieve target thrust and provide redundancy.
• Side Stages (Proposed): Additional booster segments for heavy-lift configurations. Concepts include up to 39 total engines across all stages.
• Engine Commonality: All variants designed to use the same engine type to simplify manufacturing, logistics, and spare parts management.
• Thrust Redundancy: Multi-engine design allows throttling or shutdown of individual engines if needed, improving robustness.

Note: Engine arrangements are design concepts undergoing validation. Final configurations will be determined through testing and operational requirements.

Lyra is essential to several WSA strategic goals:

• KGOSS Construction: Higher payload capacity supports station modules, fuel tanks, and expansion capabilities beyond current assembly limits.
• Deep-Space Missions: Enables ambitious FAMMOK-3 rescue and exploration missions requiring larger launch vehicles.
• Crewed Spaceflight: Supports crewed missions to distant destinations and transport of heavy payloads requiring human supervision.
• Next-Generation Infrastructure: Enables future orbital refueling stations, larger habitats, and advanced mission architectures requiring high-capacity launch.
• Autonomous Flight Research: Lyra serves as a platform for advancing AutoLand and autonomous operations on more powerful, faster-flying vehicles.

WSA has developed several spaceplane concepts for crew transport and return:

Detailed specifications for these configurations are still being documented. Additional information will be added as crew-transport programs progress.

WSA maintains several experimental aircraft and spaceplane development lines:

• FX Series (FX-1, FX-2, FX-3): Experimental aircraft designs exploring various aerodynamic and structural concepts.
• FAX Series (FAX-1, FAX-2, FAX-3, FAX-3E, FAX-3C, FAX-3S): Advanced experimental spacecraft with variations for specific mission roles.
• SRX-1: Special research experimental craft designation. Purpose and specifications under evaluation.

Most of these experimental designations have limited operational history. Detailed records will be added as projects mature and documented results become available.

Single-stage-to-orbit (SSTO) development explores whether a spaceplane can reach orbit without staging:

Development Challenges:

• Fuel Depletion: Early atmospheric-to-orbital transition was difficult. Early designs exhausted liquid fuel near 25 km altitude, requiring incomplete ascent or staged recovery.
• Orbital Achievement: Later designs using NERV engines reached approximately 200 km orbit, but without sufficient RCS propellant for docking maneuvers.
• Docking Problem: Achieving orbit proved insufficient for mission success. The SSTO reached orbit but lacked RCS capability needed for rendezvous with KGOSS.

Key Lesson: Reaching orbit is not the same as completing a mission. Systems must be designed not just to achieve altitude, but to perform the full mission profile including rendezvous, docking, and return. SSTO designers must balance fuel for ascent, orbital maneuvers, and return—a difficult trade on a single stage.

Current Status: SSTO development continues as an experimental program. The fundamental trade-offs between atmospheric efficiency, orbital capability, and mission flexibility remain active research areas.