Turbojet vs. Piston for Target Drones

Propulsion is the first decision in a target drone program, and the one that constrains everything after it. Below roughly 1,000 kg MTOW, the realistic choice is between a small turbojet and a piston engine, and the right answer depends almost entirely on what the target is supposed to represent. This is a walkthrough of the trade-offs, in the terms a procurement or test-and-evaluation team will actually meet them.

Start with the threat you are simulating

A target drone exists to be flown against. Its job is to reproduce some part of a threat's flight envelope convincingly enough that the test means something: for a seeker, for a fire-control system, for a pilot in training. Everything else follows from that.

Piston-powered targets top out at modest speeds and altitudes. That is entirely adequate when the mission is slow-mover work: cruise-missile profiles at low level, ISR-looking tracks, gunnery training, or cheap volume for operator hours. A large fraction of real target requirements sit exactly here, and buying jet performance for them is money spent on realism nobody requested.

A turbojet changes the envelope, not the concept. It buys high subsonic speed and the altitude that comes with it, the part of the map where manned fighters, fast cruise missiles and strike aircraft actually live. If the system under test has to detect, track or engage something in that regime, a piston target cannot stand in for it, no matter how many you fly. The physics of closure rate, radar cross-section presentation at speed, and intercept geometry do not grade on effort.

The blunt version: choose the engine that matches the threat's speed-altitude corner, not the one that fits the budget line most comfortably.

Throttle response and profile fidelity

Real threat profiles are not steady-state. Weaves, pop-ups, dashes and egress segments ask the propulsion system to move thrust quickly and repeatedly.

Piston engines respond essentially immediately: the propeller is a direct load, and power follows the throttle. Turbojets spool: thrust lags the lever while the rotor accelerates, and small single-spool engines have their own particular transient character. Neither is a defect; both are behavior the autopilot and the mission profile must be designed around. What matters is that the transient is understood, modelled and repeatable. A target whose dash segment arrives two seconds late on every run is at least consistently late, and consistency is what makes test data comparable across sorties.

Mass and installation

A piston engine is heavy for its power and wants volume: cylinders, cooling airflow, exhaust routing, vibration isolation. A small turbojet is compact for its thrust and concentrates its demands elsewhere: inlet ducting, hot-end clearance, fuel and control systems, and heat management around the exhaust path.

The installation question that decides layouts is where the engine can live. A pusher or tractor propeller puts the engine at an extremity and simplifies the fuselage. A turbojet typically buries in the aft fuselage, which buys a clean external shape and frees the nose for payloads, at the price of an inlet duct that has to deliver air around bends without starving or distorting the compressor face. Duct design is real engineering, not plumbing, and it belongs in the trade study, not the risk register.

Fuel logistics

This is the unglamorous argument that often decides fleet decisions. Piston engines in this class traditionally mean avgas or automotive gasoline; turbojets mean kerosene: Jet A or the heavy fuels military logistics already move in bulk. If your operation is expeditionary, ship-based, or integrated with military supply chains, a heavy-fuel target burns what the logistics system already carries. If you operate from a small civilian strip, avgas may be the fuel that is actually there. Check the supply line before the spec sheet.

Cost per flight hour

Be honest about both directions. Piston targets are cheaper to buy and cheaper to feed. Small turbojets burn more fuel per hour and carry overhaul economics that punish casual fleet planning. Against that, a jet target can compress a test program: fewer sorties to reach the required profile realism, one airframe covering envelopes that would otherwise need two different target types, and no surrogate-fudging in the data set. The metric that matters is cost per valid test point, not cost per hour on the ramp.

Recoverability

If the target is meant to come back (parachute recovery rather than expendable), propulsion choice shapes the recovery design. A piston airframe recovered under canopy has done it for decades; the practices are settled. A turbojet airframe recovers fine too, but the hot end, the duct and the fuel system all have to survive the landing attitude and the occasional rough field. Design for recovery from the first layout, not as a retrofit.

A worked example: Orion-T1

One data point from the jet side of the argument, since it is ours and the numbers are public. The Orion-T1 is a Block 2 concept target drone at 696.5 kg MTOW, built around the Orion 13.34 kN turbojet, air-launched with parachute recovery. In its scripted 6-DoF flight-test program, the max-level-speed test stabilized at Mach 0.967 at 5 km (high-subsonic, the regime a piston target cannot reach), while launch separation, climb, sustained turn and fuel-anchor tests all closed against their declared expectations.

That is what the turbojet choice buys in concrete terms: a target that flies where the threat flies, with a verified mass budget and a flight model anchored to the engine's own cycle deck. Whether your program needs that corner of the envelope is the question only your threat set can answer, but if it does, this is the class of machine that answers it.

See the full configuration, mass breakdown and flight-test receipt on the Orion-T1 page.