Skyryse and the FlightOS software turning ordinary helicopters into fly-by-wire autonomous machines

Skyryse, a company based in El Segundo, California, is taking a fundamentally different approach to the future of flight. Instead of building a new aircraft from scratch, Skyryse developed FlightOS, a full fly-by-wire operating system designed to be retrofitted into existing certified helicopters — starting with the Robinson R66. The result is military-grade automation and envelope protection in a four-seat turbine helicopter that’s already flying worldwide.

Why Software Instead of a New Airframe?

The eVTOL industry — Joby, Archer, and others — is trying to solve three problems simultaneously: new airframe certification, new propulsion technology, and new automation systems. Skyryse made a strategic decision to solve only one of those problems, but to solve it for aircraft that already exist.

That’s a fundamentally different risk profile. Skyryse doesn’t need to build a factory or certify a new airframe. Their product is a retrofit kit and software stack that installs into an existing aircraft. The capital requirements and deployment timeline are dramatically compressed compared to clean-sheet designs.

What Is FlightOS and How Does It Work?

FlightOS wraps the Robinson R66 in what amounts to a digital nervous system. The system replaces the helicopter’s mechanical control linkages with fly-by-wire actuators and interposes triple-redundant flight computers between the pilot’s inputs and the rotor system. The software interprets, smooths, and when necessary, overrides pilot inputs.

This is exactly how modern military helicopters like the Black Hawk, Apache, and Chinook operate. The critical difference is that those systems were designed into the aircraft from day one. Skyryse is retrofitting the capability into an airframe originally built with cables and pushrods.

The redundancy architecture mirrors the design philosophy of the Airbus A320’s flight control computers. FlightOS runs three independent flight computers with dissimilar software — three different implementations solving the same control problem independently. Their outputs are compared in real time. If one computer disagrees, it gets voted out. If two disagree, the system falls back to a degraded but still safe mode.

Why Helicopter Safety Needs a Software Solution

The overwhelming majority of fatal helicopter crashes are not caused by mechanical failure. They’re caused by loss of control — spatial disorientation, over-controlling in gusty conditions, startle responses after unexpected encounters. The NTSB has documented this pattern for decades. The machine is usually fine. The human operating it runs out of capacity.

FlightOS attacks this problem directly through escalating levels of autonomy:

• Level 1 — Enhanced stability augmentation. Release the controls, and the helicopter holds its attitude, altitude, and position. GPS-coupled. Wind-compensated. No drift, no slow roll into a bank.
• Level 2 — Automated maneuvers. Automated takeoff, landing, approach to a point, and go-arounds.
• Level 3 — Full autonomous flight from point A to point B with a pilot monitoring but not actively flying.

For any helicopter pilot who has spent an hour hovering in a crosswind, the significance of Level 1 alone is immediately clear.

The Simplified Pilot Interface

Skyryse has designed what they call a simplified vehicle interface. Instead of the traditional collective, cyclic, and anti-torque pedals, a FlightOS-equipped helicopter can be flown with a single inceptor — essentially a sidestick. Push it in the direction you want to go, and the computer translates that into rotor inputs.

This raises a legitimate philosophical debate that the aviation community has grappled with for decades in the airline world: does simplifying the control interface make aviation safer, or does it create operators who don’t understand the machine they’re flying? When automation works, it’s spectacular. When it fails, you need a pilot who understands the raw machine underneath.

Skyryse’s counterargument is that their triple-redundant architecture makes total system failure so unlikely that the greater risk is leaving pilots to hand-fly complex machines in demanding conditions. Statistically, the loss-of-control accident data supports that position — but it’s a point that deserves ongoing scrutiny as the technology matures.

Certification Path and Timeline

The engineering challenge of retrofitting fly-by-wire into a mechanically controlled helicopter is substantial. Every actuator, wire, and computer must be integrated without compromising the existing type certificate. The FAA doesn’t have a neat category for this kind of modification.

Certification is being pursued through supplemental type certificates (STCs), the standard pathway for aircraft modifications. However, the scope of this particular STC is unlike anything the certification branch has previously evaluated. The FAA is working through means of compliance for software-intensive fly-by-wire systems retrofitted to Part 27 helicopters, and there isn’t a clear precedent.

Skyryse has flown their modified R66 extensively and demonstrated automated takeoffs, landings, and stability augmentation in real conditions. But full STC certification is still in progress, and no certified product has yet been delivered to a paying customer. That distinction matters.

Target Market and Business Case

Skyryse’s initial business target is the air tour market — specifically high-volume operations in places like Hawaii and the Grand Canyon corridor, where helicopter accident rates have drawn Congressional attention. If FlightOS can demonstrate a dramatically lower risk of loss-of-control accidents, the regulatory case becomes compelling.

The Robinson R66 fleet numbers in the thousands worldwide, flying tours, utility missions, pilot training, and law enforcement. Making every one of those aircraft dramatically safer without replacing the airframe is something no eVTOL company can match in deployment speed.

On the funding side, Skyryse has raised over $200 million from investors including Fidelity and Venrock. That’s an order of magnitude less than major eVTOL players have raised, but the capital requirements are fundamentally different when you’re not building a factory or certifying a new airframe.

Implications for General Aviation

If FlightOS achieves full certification and demonstrates its safety improvement in the field, the same approach could extend to fixed-wing aircraft. Consider a Cessna 182 with full envelope protection — not a stick shaker and a warning horn, but a computer that simply won’t let the wing exceed its critical angle of attack. Automated go-arounds in single-engine pistons.

Loss-of-control accidents are the number one killer in general aviation. A software system that prevents them, installed in aircraft already on the ramp, could save more lives than any new aircraft design — and on a timeline measured in years, not decades.

Key Takeaways

• Skyryse’s FlightOS retrofits military-grade fly-by-wire automation into existing helicopters, starting with the Robinson R66, rather than building a new aircraft from scratch.
• The system uses triple-redundant, dissimilar flight computers — the same architecture proven in the Airbus A320 — to address the loss-of-control accidents that cause the majority of fatal helicopter crashes.
• Certification via STC is in progress but not yet complete; no certified product has been delivered to a paying customer.
• With over $200 million in funding, Skyryse is targeting the air tour market first, where high-volume operations and Congressional scrutiny create strong regulatory incentive.
• If successful, the same software-first approach could bring envelope protection to fixed-wing general aviation aircraft already flying today.