Endurance is the wrong first question

The first question in almost every airborne intelligence conversation is how long the aircraft can stay up. It is an understandable question and a bad starting point, because endurance is the specification most easily met by an aircraft that is wrong in every other respect.

An aircraft that can orbit for eleven hours and cannot land where the mission is has an endurance of zero.

Start with the runway, not the orbit

The binding constraint on most partner-nation programs is not time on station. It is field access: which strips are usable, in what condition, in what weather, with what fuel.

This is a question with a hard answer. Somebody can go and look. And the answer frequently eliminates half the candidate aircraft before performance is discussed at all — because a type that needs four thousand feet of prepared surface is simply not an option in a country where the relevant strips are eighteen hundred feet of dirt.

Field length also has a second-order effect that rarely gets modeled. An aircraft that can only operate from the capital has to transit to the operating area and back on every sortie. Two hours of transit against an eight-hour sortie is a twenty-five percent tax on the whole program, paid in fuel and airframe hours forever. A shorter-legged aircraft based forward can easily deliver more time on station than a longer-legged one that cannot get close.

Then ask what the sensor obliges you to buy

Sensor selection is usually treated as a separate, later conversation. It is not separate. The sensor determines the downlink bandwidth, the downlink determines the ground segment, and the ground segment determines how many people have to be sitting in a room at three in the morning.

Wide-area motion imagery is the clearest example. A wide-area payload genuinely covers more ground than a single turret, and it generates an exploitation workload that most partner nations cannot staff. Buying it without also building the analytic capacity to use it produces expensive recorded video that nobody watches.

The honest version of this conversation sounds like: this sensor will require four more analysts per shift than that one, and you do not currently have four analysts. That is a sensor decision, and it is also a personnel decision, a facility decision and a recurring budget decision.

Then ask what you can keep flying

Availability beats performance over a program’s life, and availability is a function of how ordinary the aircraft is.

A single-engine turboprop with wide global parts availability, a large operator base and technicians who can be trained locally will fly more sorties in year three than a more capable aircraft with a thin support network. This is not an argument for buying the cheapest thing. It is an argument for weighting sustainment as heavily as performance in the selection, which almost nobody does at the point when it matters.

If a country already operates a type, has the maintenance line for it and has crews current on it, putting a mission system on that airframe is usually cheaper and always faster to sustain than introducing a new type alongside it. That remains true even when the existing type is, on paper, the inferior aircraft.

The order that actually works

1. Where must it operate from? Field length, surface, elevation, temperature, weather.
2. What must it see, and who will look at it? Sensor class, and the analytic headcount that class obliges you to fund.
3. What can you keep flying? Parts, technicians, fuel, and whether the type already exists in your inventory.
4. Then endurance. By this point the question is narrow and answerable: given the basing you actually have, how much time on station does each surviving candidate deliver?

Run in that order, the endurance conversation takes ten minutes and produces a defensible answer. Run in the usual order, it takes six months and produces an aircraft in a hangar.