The request
A private client needed a three-city itinerary over four days: two business stops and one leisure stop, with fixed meeting times at the first two destinations and a hard return deadline. The routing crossed three jurisdictions, each with its own landing permit process, handling arrangements and operating hours.
- Routing: three cities, three jurisdictions, four days
- Aircraft: light jet, third-party charter operator
- Constraint: fixed meeting windows at stops one and two, hard return deadline
- Scope: charter sourcing, permits, handling, crew duty planning, ground transport
How it was worked
The itinerary was decomposed into three independent operations. Permit lead times were mapped for each jurisdiction, and the schedule was built backwards from the fixed meetings rather than forwards from departure. Crew duty analysis showed the original day-three plan would have exceeded legal limits — the schedule was re-sequenced to insert an overnight, which the client accepted because it was presented before booking, not after.
A single duty officer held the full itinerary. When a handling delay at the first stop threatened a 40-minute slip, the second stop's slots and ground transport were re-confirmed in advance, and the meeting window held.
The result
All three legs operated on the re-planned schedule. Total slip against the confirmed itinerary: 25 minutes, absorbed at the second stop without touching any meeting. The client returned on the required date.
The pattern this case illustrates: in multi-stop work, the itinerary is a chain of dependencies, and the value of a coordinator is measured at the handovers — permits between jurisdictions, duty limits between days, and re-planning between legs.