Crydon Defense Systems Inc. · St. Petersburg, FL UEI ER13XF6JSQ64 · CAGE 15L43 · U.S.-owned · No FOCI
Contact
cumulative flight hours across platforms
100,000+
release altitude of the record HiDRON flight
111,434 ft
platforms flight-demonstrated, compact UAS to HAPS
8
to months per integration, not a platform-specific build
Weeks

Most unmanned programs still mean months of platform-specific autopilot development, integration and test for every new airframe. APX takes the other path: one trusted control architecture adapted to radically different vehicles, so a new integration is measured in weeks to months.

APX integrates with existing command-and-control systems, sensors, communication links and customer-owned payloads rather than replacing a customer’s ecosystem. Crydon supports platform assessment, structured demonstration, integration, verification and lifecycle sustainment — through Other Transaction agreements under 10 U.S.C. §4022 and direct contracts.

Overview

Autonomy Integration for Complex Platforms

How APX brings one autonomy core to fixed-wing, rotary-wing and stratospheric platforms. 6 min.
01 Architecture

Built to be trusted on any airframe

A hardened, reduced-SWaP architecture designed for complex unmanned platforms — and for the integration and security discipline defense programs require.

  • Distributed architecture

    Dedicated microcontrollers across the vehicle with layered mission, guidance and stabilization tiers — fault isolation, lower central processing load and safe degraded states.

  • Controlled firmware baseline

    Proprietary firmware — not open-source and not Pixhawk-derived — for controlled security updates, configuration accountability and a smaller public attack surface.

  • Resilient navigation

    Multi-constellation GNSS, a tactical-grade IMU with sensor fusion and an AHRS independent of GNSS, for GPS-degraded, denied and spoofed conditions.

  • Secure communications

    AES-256 encrypted command and telemetry with frequency-hopping spread spectrum across LOS, LTE and satellite links — including third-party datalinks such as pMDDL.

  • Isolated mission scripting

    An onboard virtual machine runs custom mission logic without modifying flight-critical firmware.

  • Open payload integration

    Open payload buses and SDK-based extensions for EO/IR, SAR, SIGINT, EW, communications relay and customer-owned payloads.

02 Specification

Architecture at a glance

The capability baseline APX brings to an integration.

Architecture
Distributed microcontrollers; mission, guidance and stabilization tiers; fault isolation; safe degraded states
Firmware
Proprietary, controlled baseline — not open-source, not Pixhawk-derived
Hardware
R4 generation; compact, modular, reduced SWaP; dual IMUs; power redundancy; onboard watchdogs; sealed, anodized enclosures for high-altitude and extreme environments
Flight functions
Autonomous taxi, takeoff, landing, navigation and mission execution; diagnostics; mission planning
Navigation
Multi-constellation GNSS; tactical-grade IMU with sensor fusion; AHRS independent of GNSS; GNSS-degraded, denied and anti-spoofing operation
Communications
AES-256 encrypted command and telemetry; frequency-hopping spread spectrum; LOS, 4G/LTE and satellite datalinks; third-party datalink integration (pMDDL, SATCOM)
Mission scripting
Onboard virtual machine — custom mission logic isolated from flight-critical firmware
Payloads
Open payload buses and SDK-based extensions; EO/IR, SAR, SIGINT, EW, communications relay, customer-owned payloads; modular bay for rapid swap
Energy management
Solar-harvesting and battery-control logic for persistent day–night stratospheric missions
Development process
Aligned with the DO-178C (software) and DO-254 (hardware) frameworks for safety-critical airborne systems
Ground control
GCS software for mission planning, real-time telemetry and command links across LOS, LTE and satellite
Airframe classes
Fixed-wing, rotary-wing and hybrid VTOL, from about 11 lb to 8,800 lb MTOW; also demonstrated on an uncrewed surface vessel
Maturity
100,000+ cumulative flight hours across platforms; SITL and HITL validated; 5G connectivity demonstrated on a HAPS
03 Flight-demonstrated

One core, radically different vehicles

APX has flown on platforms from compact UAS to stratospheric aircraft and heavy-lift helicopters converted from piloted airframes.

  1. 01

    HiDRON stratospheric glider

    Autonomous control above 111,000 ft in near-space conditions

    Stratospheric
  2. 02

    ApusDuo / ApusNeo solar HAPS

    Continuous stratospheric operation, day–night solar energy management, 5G connectivity demonstration

    Stratospheric
  3. 03

    UVH-500 heavy-lift helicopter

    Manned-to-unmanned conversion — autonomous takeoff and landing, networked remote control, autorotation

    Rotary-wing
  4. 04

    S1-V300 MALE UAS

    Fully autonomous taxi, takeoff and landing under SATCOM with redundant avionics

    Fixed-wing
  5. 05

    ALBATROSS 2.2

    Distributed avionics with triple redundancy

    Fixed-wing
  6. 06

    UVH-25EL compact VTOL

    Compact autopilot with advanced vibration management

  7. 07

    Borey UAS swarm

    Coordinated autonomy and swarm flight control

  8. 08

    High-dynamic flight demonstrator

    Precision control in demanding flight regimes, including GNSS-denied and spoofed conditions

Platforms shown are UAVOS engineering heritage, not Crydon products. About our heritage

04 Engagement

From assessment to sustainment

Crydon is the U.S. contracting, integration, verification and lifecycle-sustainment interface for APX.

Missions

  • Persistent ISR
  • Communications relay
  • GNSS-degraded and denied operations
  • Manned-to-unmanned conversion
  • Multi-payload missions
  • Rapid deployment with minimal ground support
  • Swarm operations
  1. 01

    Assess

    Platform assessment against mission requirements, interfaces and constraints — what APX must integrate with, and what it should leave in place.

  2. 02

    Integrate

    Interface definition through installation — flight controls, C2, sensors, datalinks and payloads brought onto one autonomy core.

  3. 03

    Verify

    SITL and HITL validation, then structured flight demonstration, with evidence captured against the agreed requirements.

  4. 04

    Sustain

    Lifecycle support — maintenance, configuration-controlled updates, diagnostics and field support.

Next step

Assess APX for your platform

Tell us about the airframe, the C2 environment and the mission. We'll come back with an integration and demonstration approach.