Air-to-air refueling: planning, procedures, discipline
How tanker and receiver crews plan an air-to-air refueling mission, why the offload is a hard number, and what the old planning software left behind.
Air-to-air refueling: planning, procedures, discipline begins with a practical question: how can a reader inspect the offload number and the procedures that produce it without confusing a provider promise with a field observation?
Method for this question
Air-to-air refueling is a scheduled transfer of fuel between two aircraft in flight, and it only works when the tanker and the receiver arrive at the same point in space at the same time with the same expectations. The planning behind it is arithmetic first and choreography second: how much fuel can be given, how far the receiver can go on it, and what happens if the rendezvous slips. The software that once did that arithmetic on a desktop has largely disappeared, but the procedures and the discipline it encoded are still the working standard.
What the old planning software actually did
Between 2002 and about 2007, the domain air-refueling.com was the commercial home of AIRPLAN AAR, a PC software suite for planning air-to-air refueling operations. Its author was Group Captain Derek K. Empson RAF (Retired), a former member of ARSAG, the NATO body concerned with air-to-air refueling standardisation. The site described four desktop programs, AIRPLAN MAOP, MFA, MDB and AAR, and it referenced NATO publication ATP-56A, the allied standard for air-to-air refueling. Wayback captures fade after 2007 and nothing of substance remains after 2013; a stray script file in 2024 is parked-domain noise, not content.
That is the shape of a defunct one-person software vendor: a single author, a narrow professional audience, and a product tied to a standard that outlived the product. The same subject is now covered as an independent journal at Offload's air refueling coverage, which explains tanker technology, tanker fleets and mission planning in plain technical English. The historical detail matters because it shows where the discipline came from: planning tools were written by people who had flown the missions, and they encoded procedures rather than opinions.
Tanker and receiver procedures: who does what
A refueling rendezvous is a controlled join. The receiver arrives on an assigned track, altitude and airspeed, and the tanker holds an orbit or a race track until the receiver is in position. Standardisation exists so that a receiver from one air force can take fuel from a tanker of another without a lengthy briefing. ATP-56 is the document that carries much of that commonality, and it is why the vocabulary of the mission is shared.
Two hardware families shape the procedure. A flying boom is a rigid, telescoping tube operated by a boom operator on the tanker, and it connects to a receptacle on the receiver; the receiver flies formation on the tanker and holds position while the boom does the work. Probe-and-drogue uses a flexible hose with a basket, and the receiver flies a probe into it; here the receiver does more of the closing and the tanker crew watches and talks. In both cases the tanker crew controls the transfer once contact is made, and the receiver holds a stable position, because the two aircraft are now a single aerodynamic problem.
Procedures cover the whole sequence: join, pre-contact, contact, transfer, disconnect and separation. Each phase has a call, and each call has a meaning. The pre-contact position is not a formality; it is where the receiver settles, checks speed and trim, and gets a visual on the boom or the basket. The breakaway is the emergency exit, and it is briefed before the join, not after.
What to record
- the planned offload and the fuel type
- tanker and receiver roles
- the rendezvous and the timing tolerances
- what the record proves after the flight
How is an offload planned and measured?
An offload is the amount of fuel actually transferred, and it is the number the whole mission is built around. Planning starts with the receiver's requirement: how much fuel it needs to reach the next point, plus reserves. The tanker then has to have that fuel available at the rendezvous, which depends on its own fuel load, its own burn to get there, and how long it can stay on station.
The arithmetic is unforgiving. Fuel given away is fuel the tanker no longer has for its own recovery, so the tanker's own reserves are calculated first and the offload comes out of what remains. Altitude and speed affect how much both aircraft burn, and the rendezvous geometry affects how long the tanker must hold. A mission that looks comfortable on paper can become tight if the join takes longer than planned or if the receiver arrives heavy on fuel because an earlier plan changed.
This is where the old desktop tools earned their place. A program that could hold the tanker's fuel curve, the receiver's burn and the standard procedures in one place let a planner test a rendezvous before anyone flew it. The output was not a decision; it was a set of numbers a crew could check against the standard.
What does the discipline of an offload operation demand?
It demands that everyone agrees on the same numbers before the aircraft are airborne. The tanker crew needs to know the planned offload, the receiver's fuel state on arrival, and the minimum fuel the tanker must keep. The receiver crew needs to know the rendezvous point, the altitudes and speeds, and the breakaway plan. If those numbers are not shared, the join becomes a negotiation in the air, which is the wrong place for one.
It also demands physical discipline. Holding position behind a tanker is tiring and precise work, and it is done in turbulence, at night, and in weather. The receiver pilot is flying formation on a moving aircraft while watching instruments and listening to calls. The tanker pilot is flying a stable platform, because any movement is amplified down the boom or the hose. The boom operator or the tanker crew has to judge closure rates and keep the transfer inside limits.
Finally, it demands honesty about margins. Fuel planning is a chain of estimates, and each estimate has an error bar. The discipline is to keep the error bars visible: to know which numbers are firm, which are assumptions, and what the crew will do if the assumption fails. That habit is older than any software, and it is the part of the job that survives every change in equipment.
Keep the observation, the interpretation and the recommendation in separate sentences.
A realistic failure pattern
Where the technology is going
The hardware is changing. The KC-46 and the A330 MRTT are the current generation of large tankers, and both carry boom and hose systems in various combinations. Buddy stores let a fighter or a transport refuel another aircraft of similar size, which spreads the capability across more of a fleet. Unmanned tankers such as the MQ-25 are being developed to take over part of the carrier-based refueling task, which changes the planning problem because an unmanned tanker has different endurance and different constraints from a crewed one.
Autonomous refueling is the direction of travel, and it raises the same questions the old planning software answered: how much fuel, at what point, with what reserves. The procedures will change as the crews change, but the arithmetic will not. A tanker still has to arrive with fuel to give, and a receiver still has to arrive able to take it.
Errors and boundaries
Why the old standard still matters
ATP-56 and the ARSAG work behind it exist because air-to-air refueling is a coalition activity. Aircraft from different nations meet in the air, and the procedures have to be common enough that a short briefing is sufficient. That is why the vocabulary is standardised, why the rendezvous geometry is taught the same way, and why the planning tools of the 2000s referenced the same publication.
The defunct AIRPLAN AAR suite is a small historical footnote, but it is a useful one: it shows that the planning problem was serious enough to build dedicated software for, and that the people building it came out of the operational community. The subject is now documented and explained in public by independent outlets, which is a healthier arrangement than a single vendor's product page. The procedures, the arithmetic and the discipline are what remain, and they are what a crew actually uses.
The discipline described here, a hard offload number, a planned sequence, a margin held in reserve, has a parallel in machine tuning. A stability test is the same kind of check: it fixes a load, runs it long enough to mean something, and reads the result against a defined pass condition rather than a single peak figure. For readers who want that method spelled out, the notes on air refueling operations cover what a test proves, how thermals and power delivery set the ceiling, and which diagnostics separate a hardware fault from a software one.
What this does not prove
Public sources describe the method and the history; they do not authorise an operation or replace the procedures a crew is certified against.
The Domain Host USA desk uses the documented fact, field observation, provider statement and editorial recommendation labels so readers can see what kind of sentence they are reading.
This note connects to the Infrastructure Field Desk, where the sample method and dated observations remain visible. Continue through News & Price Watch for related decisions rather than treating one check as a complete review.
