Launch when the mission requires it.
Developing the propulsion, flight-control, and vehicle technologies required for responsive European access to orbit. Our current program is focused on an integrated reusable VTVL demonstrator — the first step toward a dedicated launch system for small payloads.
Explore the development program
Discuss a partnership
EU / 50–200 KG CLASS
The Operational Constraint
A payload can be ready long before its launch opportunity is.
Small satellites can be designed and manufactured on increasingly short development cycles, but access to orbit remains constrained by fixed manifests, shared missions, integration schedules, and limited destination flexibility. Launch timing, target orbit, deployment conditions, and operational independence can determine whether a mission is commercially or strategically useful.
01 — Schedule dependency
Payload operators often have to adapt their mission to an available launch rather than selecting a launch around their mission.
02 — Orbital compromise
Rideshare missions may require compromises in inclination, altitude, deployment timing, or transfer requirements.
03 — Long integration cycles
Launch availability, payload qualification, interface coordination, and manifest planning can extend the period between payload completion and orbital deployment.
The System Concept
Dedicated launch, designed around mission requirements.
Akkoyun Aerospace is developing toward a vertically integrated launch platform for small payloads requiring greater control over schedule, destination, and deployment conditions. Target payload class: approximately 50–200 kg — a long-term system objective, not a service currently available for booking.
Dedicated missions
Responsive preparation
Orbital flexibility
European capability
Development Phase 01
Building the vehicle from the inside out.
The current phase is structured around bringing the vehicle’s critical systems to a level where they can be integrated, operated together, and progressively exposed to real flight conditions. The objective is not to develop isolated technology demonstrations. It is to establish a complete experimental vehicle architecture in which propulsion, control, structures, avionics, software, and ground systems function as one coordinated platform.
INTEGRATED VEHICLE DEVELOPMENT SEQUENCE
01
DEFINE THE VEHICLE REQUIREMENTS — Translate the flight objective into system-level requirements for thrust, control authority, operating time, mass, structural loads, sensing, recovery, and ground operations.
02
DEVELOP THE CRITICAL SUBSYSTEMS — Design propulsion, propellant management, thrust-vector control, avionics, structures, software, and ground-support systems around one shared vehicle architecture.
03
VALIDATE THE INTERFACES — Test the mechanical, electrical, fluid, software, and control interfaces that connect the individual systems before full vehicle integration.
04
INTEGRATE THE GROUND VEHICLE — Operate propulsion, actuation, sensing, flight electronics, software, and structural hardware together under controlled ground-test conditions.
05
PROGRESS TOWARD FLIGHT — Advance through staged vehicle testing, from integrated ground operation to restrained vertical testing and eventually autonomous free flight.
PROGRAM ARCHITECTURE
INTEGRATED VEHICLE OVER ISOLATED DEMONSTRATIONS — The program is organized around a complete experimental vehicle so that subsystem interactions are discovered early.
PROGRESSIVE EXPOSURE TO RISK — Hardware moves from component testing to subsystem testing, integrated ground operation, restrained flight, and free flight.
FLIGHT-RELEVANT ARCHITECTURE FROM THE BEGINNING — Early systems are developed around the interfaces, loads, control requirements, and operating conditions expected in the vehicle.
MODULAR AND SERVICEABLE CONSTRUCTION — Components are designed to be inspected, modified, and replaced between development cycles.
Each development step exists to remove a specific integration risk before the vehicle progresses to the next operating environment.
Technology Demonstrator
A complete vehicle reveals what isolated component tests cannot.
An orbital launch system is not created by developing a high-performance engine in isolation. Propulsion, guidance, structures, actuation, software, thermal management, and ground operations must function as a coordinated system. The VTVL demonstrator provides a controlled platform for validating these interactions before progressing toward larger and more demanding vehicles.
Integrated propulsion control
Validate ignition, throttling, shutdown, and relight within the complete vehicle architecture.
Dynamic thrust-vector control
Measure actuator response, control authority, structural interaction, and vehicle stability during powered flight.
Autonomous flight control
Develop state estimation, guidance logic, control algorithms, sensor fusion, and fault handling using real flight data.
Reusable operations
Study landing, inspection, servicing, turnaround procedures, and repeated vehicle use.
SRS VCTR-04 / FLIGHT-ORIENTED ELECTROMECHANICAL TVC ACTUATOR
Featured Subsystem / Thrust Vector Control
SRS VCTR-04
A compact electromechanical actuator developed for precise thrust-vector control under high dynamic loads.
SRS VCTR-04 is the fourth iteration of Akkoyun Aerospace’s internally developed thrust-vector-control actuator. The system combines high load capacity, low mass, closed-loop position feedback, and minimal mechanical play in a compact flight-oriented architecture. Manufactured from carbon-fiber-reinforced PA12, aerospace-grade aluminum alloys, and PTFE bearing elements, the current configuration is intended for integration into upcoming VTVL flight vehicles.
ITERATION
04
CONTROL
Closed-loop encoded feedback
STRUCTURE
PA12-CF / 6061-T6 / EN AW-2027 / PTFE
APPLICATION
Thrust-vector control
BENCH-TESTED LOAD-TO-MASS RATIO — UP TO 285:1
DOCUMENTATION AREA / PROPULSION, OXIDIZER, AVIONICS, STRUCTURES, TESTING, AND VEHICLE INTEGRATION
Hardware Development
Physical progress is documented system by system.
The program continues through manufactured hardware, integration fixtures, instrumentation, and ground-support equipment. This area is prepared for future documentation of propulsion hardware, oxidizer systems, avionics, structures, testing, and vehicle integration as those physical development stages are recorded.
Engineering Approach
Designed, manufactured, and tested in-house.
01
Vertical integration
Critical systems are developed internally to accelerate iteration and retain technical control.
02
Physical validation — Design decisions are evaluated through real hardware, testing, and measurable results.
03
Rapid iteration — Compact development cycles move systems quickly from individual components to integrated flight testing.
Development Roadmap
A staged path from demonstrator to orbit.
01 — INTEGRATED TECHNOLOGY DEMONSTRATOR
Validation of propulsion, thrust-vector control, avionics, guidance, relight, and vertical landing.
02 — SUBORBITAL VEHICLE
Testing under increasingly representative flight and operational conditions.
03 — RESPONSIVE ORBITAL LAUNCH SYSTEM
Dedicated access to orbit for European small-satellite missions.
Why Responsive Launch Matters
The value of launch is determined by more than price per kilogram.
Conventional launch economics are optimized around vehicle utilization and aggregated payload demand. Responsive dedicated launch addresses a different requirement: missions for which timing, destination, deployment conditions, or operational independence justify a dedicated service.
TIME-SENSITIVE COMMERCIAL MISSIONS / REPLACEMENT AND REPLENISHMENT SPACECRAFT
TECHNOLOGY DEMONSTRATION / EARTH-OBSERVATION / NON-STANDARD ORBITAL PARAMETERS
INSTITUTIONAL AND EUROPEAN STRATEGIC MISSIONS / CONSTELLATION DEPLOYMENT AND MAINTENANCE
The Company
An engineering-first aerospace company.
Akkoyun Aerospace was founded by Yasin Akkoyun to develop vertically integrated flight and propulsion technologies through rapid iteration and physical validation.
EDITORIAL PLACEHOLDER — FOUNDER / ASSEMBLY / TESTING
Contact
Building responsive launch capability requires the right partners.
We are open to conversations with investors, technical partners, suppliers, future payload customers, and media.
Start a conversation
Investment · Technical partnerships · Suppliers · Future payload missions · Media