A business jet is due into Dubai at 18:10 with a two-hour turn before it continues to Riyadh. In that window the handling agent must park, fuel and clean the aircraft, the caterer must deliver a meal for the next sector against a passenger list that changed at 15:30, two vehicles must take four passengers to the city and a crew of three to a hotel, and that crew must be back airside at 05:45.
Four services, four suppliers, four briefs and, at the end of the month, four invoices arriving at one finance desk. Each supplier is competent at its own job. None has the picture of the flight as a whole, and that is where time, money and the occasional safety margin leak away.
Private and business aviation is now consolidating the services around the aircraft. Accommodation, ground transport, catering and the handling a fixed base operator (FBO) coordinates on the apron are being pulled together because they share the same operator, the same flight, the same window on the ground, and the same team paying for all four.
Why the four services are converging
Commercial airlines separated these services decades ago, with different departments, contracts and systems for each, and at scale that made sense. A business aviation operator running a dozen aircraft across Europe and the Gulf has no department for each: it has a flight operations team, a few dispatchers, and a finance function that would rather not receive forty invoices for one trip.
The forcing function is the ground window. On a two-hour turn, catering that arrives after the crew has left for the hotel is wasted. A car that arrives before the handling agent has cleared the passengers through the FBO is a driver waiting on a meter. A hotel that cannot confirm a late check-in means a dispatcher on the phone at 20:00 instead of planning the morning.
Every one of those failures is a handover failure between services planned separately. The fix is not to make each supplier faster but to plan all four against the same timeline from the start.
One brief, one record, one invoice
In practice, integration means three things, simpler to describe than to build.
One brief. The operator describes the flight once: aircraft, arrival and departure times, passengers and their needs, crew and their rest requirements, special instructions. Every supplier receives the portion relevant to them, from the same source, rather than a separately typed email that may already be out of date.
One record. As the turn unfolds, each supplier writes back to the same record: aircraft on stand at 18:14, passengers departed the FBO at 18:40, catering delivered at 19:05, crew checked in at 19:35. When the departure moves to 21:00 because of a slot, the change goes to the record and from there to the caterer, the hotel and the car. The dispatcher sees one timeline, not four inboxes.
On a two-hour turn, the service that does not know what the other three are doing is the one that will be late.
One invoice. The operator receives a single statement for the flight, with handling, catering, accommodation and transport as lines against the same trip reference. Finance reconciles once. Suppliers are paid from one ledger on one cycle, and disputes are about specific lines rather than whole invoices.
Why the Gulf is the natural proving ground
The Gulf is an unusually good place to prove this model. Business aviation activity is dense and concentrated on a few hubs in the United Arab Emirates, Saudi Arabia and Qatar. Many flights are short regional sectors with quick turns, precisely where the ground window is tightest and a handover failure costs most.
The supplier landscape is also younger than in Europe. Hotels, transport operators and caterers serving business aviation in the Gulf are often newer businesses with modern systems and fewer legacy contracts to unwind, and more open to a shared platform because they have less invested in the old way.
There is also a commercial appetite for standards. Operators in the region work to demanding expectations from their principals and increasingly formal duty of care expectations for crews, and want one accountable party for the ground experience rather than a chain of subcontractors. A model that works in Dubai at 18:10 on a Thursday will work in Geneva and Nice.
The kind of organisation that can lead it
The obvious temptation is for one company to do everything: run the FBO, own the hotels, operate the cars, cook the food. It almost never works. Each is a specialist business with its own economics, licences, staff and local relationships, and whoever tries to own all four ends up mediocre at three.
The organisation positioned to lead looks different. It owns the platform and the standard: the journey record, the brief format, the data trail each supplier must produce, the settlement ledger. It works with specialists for each service, selected and held to that standard, in each location it serves. The platform owner answers to the operator for the whole experience; the specialists answer to the platform owner for their part.
This pattern has worked elsewhere in transport, and it has a few conditions:
- The standard has to be specific enough that a new supplier in a new city can be onboarded quickly and measured fairly.
- The platform has to work for suppliers too, with faster payment and fewer disputes as the reason to join.
- The platform owner has to employ people who have done handling, dispatch and crew logistics, because a standard written by people who have never stood on an apron at 02:14 will not survive contact with one.
What has to be true for it to work
Convergence is not inevitable, and what it depends on is mostly unglamorous. Supplier onboarding has to be fast and honest about maturity: a caterer with a portal and a transport operator with a dispatch API should both be able to join and produce the same facts. The data trail has to be good enough for an insurer or a crew representative to rely on: timestamps and identities, not just confirmations. And the dispatcher has to trust the platform at 20:00 when the slot moves, a reliability test rather than a feature test.
We think the operators that solve this will not be the ones with the biggest fleets. They will be the ones that stop buying four services and start buying one turn.
Key takeaways
- Accommodation, ground transport, catering and handling share the same operator, flight, ground window and payer, which is why they are converging.
- Integration means one brief for all suppliers, one record that each writes back to, and one invoice per flight.
- The Gulf's dense regional flying, quick turns and younger supplier base make it the natural proving ground before the model travels to Europe.
- The leader will own the platform and the standard and work with specialists for each service, rather than run all four itself.
- Reliability on the night, not features in the demo, is what earns the dispatcher's trust.