The request
A charter operator needed to move a 12-passenger business jet into Lagos on a non-scheduled basis, with a 72-hour window between first contact and the planned departure. The scope covered the landing permit, ground handling, fuel coordination, crew accommodation and secure airside transport for the passengers.
The constraint was not any single task — it was that every task depended on the permit, and the permit depended on a complete, consistent document set. The schedule had no slack for a review restart.
- Aircraft: mid-size business jet, foreign-registered
- Passengers: 12, mixed nationality
- Window: 72 hours from request to planned departure
- Scope: landing permit, handling, fuel, crew logistics, passenger transport
How it was worked
The operations desk assembled the full filing pack — air operator certificate, registration, insurance, crew licences, passenger manifest and purpose-of-flight statement — and cross-checked every field for consistency before submission. The permit was filed as one complete set rather than in sequence, so the review clock started once and was not reset.
In parallel, handling and fuel were provisionally confirmed against the filed schedule, and crew accommodation was held on a cancellable basis. When a crew nationality question arose on day two, it was escalated through a monitored channel and resolved the same day rather than entering an email queue.
The result
The landing permit was approved inside the planned window, the aircraft arrived on schedule, and turnaround services were in position on arrival. The return leg departed without revision to the filed plan. Total elapsed time from first call to wheels-up: 68 hours against a 72-hour target.
The lesson this case illustrates is consistent across our desk: on compressed timelines, parallel confirmation beats sequential confirmation, and a permit filed once correctly beats a permit filed early and amended twice.