Partner-nation programs fail at transfer, not in the air. The handover has to be designed from the first day as milestones with competency criteria attached, not scheduled as a date near the end. Aircrew convert fastest, sensor operators take longer, and maintenance depth and an exploitation cell take longest of all.
Ask anyone who has stood up an airborne intelligence capability for a partner nation what went wrong, and you will almost never hear about the aircraft. The aircraft usually flew. The sensor usually worked. What failed was the part nobody drew: the moment the contractor was supposed to stop being necessary.
That moment gets called transition, or handover, or sustainment — and in most programs it is a line item near the end of a schedule rather than the thing the schedule was built around. By the time anyone takes it seriously, the decisions that made it impossible were taken three years earlier.
Four decisions that decide the handover before it starts
Who holds the type certificate and the maintenance data. If the mission fit is proprietary to the integrator and the data package does not transfer, the customer cannot maintain the aircraft without the integrator, forever. This is not a technicality. It is the single most common reason a capability reverts to contractor dependence after transition.
Whether the crews were trained or merely observed. There is a real difference between a partner-nation operator who has flown two hundred sorties in the right seat and one who has run the mission as aircraft commander with a contractor sitting quietly behind them. Only the second one can run the capability on their own, and only the second one takes three times as long to produce.
Whether the ground segment is sustainable on local power, local bandwidth and local budget. A ground station specified against what is technically best rather than what the customer can actually keep running is a handover failure with a delay fuse in it. Generators fail, bandwidth contracts lapse, and air conditioning in a server room is a recurring cost somebody has to defend in a ministry budget every year.
Whether the spares pipeline survives the end of the contract. If parts flow because the integrator has a relationship with a distributor, that flow stops when the contract does. The customer needs their own supply arrangement, and it needs to exist before transition rather than after.
What a handover-first program looks like instead
It looks slower at the start and faster at the end.
The training pipeline is built before the aircraft arrive, not after. The maintenance data package is a contract deliverable with a date on it, not an afterthought. The ground segment is specified against the customer’s actual power and communications reality, which usually means it is less capable than the one a vendor would prefer to sell and considerably more likely to be running in year five.
Most importantly, the contract contains a defined end state with criteria attached. Not “transition to be discussed in year three”, but a written definition of what the customer must be able to do unaided for the capability to be considered transferred — how many qualified aircraft commanders, how many certified maintainers, what mission-capable rate sustained over what period.
The commercial objection, and the answer to it
The obvious objection is that this is a bad business. A contractor who designs their own obsolescence earns less than one who does not.
That is true over a single program and false over a decade. A customer whose first capability actually transferred comes back for the second one. A ministry that owns a working ISR capability starts asking what else it could own. And the reference that a partner nation gives about a contractor who left when they said they would is worth more in that region than any amount of marketing.
The alternative — the program that never ends because it was never designed to — produces a customer who resents the dependency and a contractor who has to defend the same support budget every year against a government that increasingly wishes it had bought differently.
A capability that cannot survive the contractor leaving was never a capability. It was a subscription with aircraft attached.