Two Fadron engineers assembling a fixed-wing UAV on a workbench

Defence & Government

Complete systems, from design to flight in weeks, not years.

Bring us a mission nobody sells an aircraft for yet. The airframe, the autonomy and the ground software are one company's work, and the system is flight-tested before delivery. Built in Bulgaria, an EU and NATO member state, on 12+ years of R&D and manufacturing.

The capability

One engineering authority over the whole aircraft.

Manufacturing is ours: carbon fibre layup, CNC machining, 3D printing and final assembly, with several models running in parallel. A change to a wing, a mount or a control law is decided, cut and flown by the same people, and nothing waits on another company to agree an interface. Most of a custom aircraft's schedule is that waiting.

The same team runs a civil inspection business, where every flight ends in a number an engineer signs.

Software

Three layers of software, all written in house.

A programme buys the path from sensor to decision.

01 / ONBOARD

Detection and tracking

Detection and tracking run on the aircraft, trained on what a given programme has to find. A classification made in the air survives losing the link. GNSS-denied navigation on request.

02 / GROUND

The record a decision rests on

The flight comes back as a record somebody has to act on. Detections are located, timed and delivered into the system where the decision already gets made.

03 / MISSION

Several aircraft, one task

Mission control for several aircraft flying one task: who searches where, what happens when one finds something, and what an operator approves. Written first for autonomous wildfire response.

Evidence

Nimbus, the aircraft that came out of it.

Nimbus is a long-range VTOL for mapping, survey and ISR, designed here and flown through 3,000+ hours of flight testing. Recon is available in an NDAA-compliant configuration. Where a programme needs a different aircraft, we design and build that aircraft.

Specifications and flight permissions are on the Nimbus page.

Where this goes

Why the build time changes the requirement.

A requirement is written against the threat that exists the day it is written. When procurement takes years, the aircraft arrives against a different one.

When the build takes weeks, the requirement can stay open. A planner can specify narrowly, because a narrow aircraft is no longer a decade-long commitment. A prime can put a flying airframe in front of an evaluator during the bid.

Ways to work with us

The four ways a programme starts.

Primes, integrators, ministries, and manufacturers.

A system built to your requirement

Design to flight test.

Tell us the mission, the payload and the environment. We return an airframe sized to it and a flight-test programme. Where something we already build fits, we say so.

Consortium partnerships

Aircraft and autonomy inside a programme team.

We join national and European programme consortia as the aircraft and autonomy partner, where sovereign capability is the point. Bring us in while the work packages are still being drawn.

Industry and integration partnerships

Radar, sensors, and mission systems.

They integrate onto our aircraft and co-develop with us. The flight stack is PX4 with MAVLink, so the integration is documented, portable, and yours to maintain.

Contract manufacturing and OEM

Carbon structures and assembly, to your drawings.

The line is open to partners: contract manufacturing, subsystem supply, and OEM platform work alongside our own aircraft. Volumes and lead times are confirmed in writing against a specific programme.

Compliance and provenance

Export control and provenance.

Fadron operates under EU dual-use export control. What can be supplied in a given configuration depends on destination and end use, confirmed before a proposal goes out.

Component provenance is documented through the supply chain, and the site where the aircraft are built can be visited.

For operations under state or military authority we support the acquiring organisation's certification and documentation requirements.

Contact

The first conversation.

Send the requirement, or the outline of one. Conversations are technical and confidential, and working under NDA is normal. We reply within one business day.

Prefer email? Write to [email protected].

Digits or words both work.

Request a demo