Sri Lanka ad-hoc charter approval documents should be assembled for the actual commercial operation. CAASL publishes a dedicated checklist for revenue ad-hoc passenger and cargo flights, alongside separate aviation-security requirements. That process should not be treated as a universal document list for private, non-revenue or overflight-only movements.
This article explains the published commercial checklist and its coordination implications. Use the Sri Lanka overflight and landing permit guide for permission types and the crew and passenger entry guide for personal entry formalities.
For a recurring programme, read our permit and FAOC guide. CAASL’s register lists IS 110 effective 3 August 2026; confirm the current approval route rather than relying on the older FAQ threshold alone.
Identify the operation before selecting the checklist
CAASL’s 2024 ad-hoc guidance addresses revenue passenger/cargo operations and directs non-revenue enquiries to its flight-permission channel. Its aircraft-operations FAQ also identifies a certification route for operators proposing six or more non-scheduled commercial flights in a six-month season. Confirm the route applicable to the intended programme; an ad-hoc application is not automatically sufficient for repeated commercial operations.
Tell the permit coordinator the operator, flight purpose, commercial status, itinerary and planned frequency. Do not classify a flight solely by aircraft size or the fact that it is carrying only a few passengers.
What the published revenue ad-hoc checklist requests
The 2024 CAASL checklist identifies the following records and confirmations:
- AOC or equivalent, with Operations Specifications.
- Valid insurance and aircraft registration certificates.
- Airworthiness certificate or current Airworthiness Review Certificate.
- Radio licence.
- Landing-airport technical certification arrangements, including relevant engineer or pilot licence and authorisation evidence.
- General Declaration and local handling-agent contact details.
- Dangerous-goods authorisation when such goods are carried.
- Slot-allocation SCR message.
- Control-tower parking allocation for a CMB operation.
Check the latest authority instructions before submitting. This summary explains an identified published document; it does not certify that the list is exhaustive or unchanged for the intended flight date.
Resolve technical certification before completing the pack
The technical-certification entry is more specific than a generic request for “handling”. Ask which appropriately authorised person or organisation will provide the required support at the landing airport and what evidence the authority needs. A routine ramp-service confirmation cannot establish engineering approval.
Keep this workstream separate from ground handling. Identify the aircraft type and planned technical arrangements so that a provider can confirm its actual scope rather than relying on a general airport facility description.
Treat slots and CMB parking as supporting records
The published checklist separately requests a slot message and, for CMB, a parking allocation. This is a useful reason to organise the approval pack around confirmed arrangements rather than a provisional flight schedule alone.
For Bandaranaike / CMB / VCBI, ask the coordinator to check what parking evidence is currently required and how it is obtained. A preferred arrival time is not proof that a stand is accepted for the complete stay. See the parking guide for the stay-planning questions.
Include the applicable aviation-security evidence
CAASL’s separate commercial charter/ad-hoc security guidance covers aircraft checks, access control, protection while out of service and departure-related security arrangements. It requests evidence of the operator’s arrangements or confirmation from a local aviation-security provider, according to the approach selected.
Identify the responsible party and obtain the required evidence through the appropriate operational channel. This public article does not reproduce restricted programmes or detailed security procedures.
Allow adequate time without promising an approval deadline
The 2024 ad-hoc guidance requests a complete submission at least three working days before operation. This is a dated requirement for that published process, not a guaranteed processing time. Confirm the current submission period, working-day implications and additional requirements with CAASL or the responsible coordinator.
Send a complete pack early enough to resolve questions about certification, slots, parking and security. Avoid publishing a universal “24-hour approval” or applying the commercial checklist’s timing to every non-revenue movement.
Carry the approval into the dispatch handover
The retrieved June 2026 ENR 1.10 directs non-scheduled/private operations into and across Sri Lankan territory to quote the flight-clearance or re-clearance number in Item 18 of the filed flight plan. Dispatch should verify the effective instruction and applicable format before filing.
Reconcile the approved aircraft, itinerary and dates with the final handling brief. If they change, use the schedule-change guide and check which approval and service records require revision.
Frequently asked questions
Does this checklist apply unchanged to a private non-revenue flight?
No. Establish the applicable permission route and documents for that operation separately.
Does submitting three working days ahead guarantee approval?
No. The published submission period is not a service guarantee and needs checking against current instructions.
Are handling, technical certification and parking the same confirmation?
No. Keep each required supporting record identifiable in the pack.
Official sources and scope
- CAASL: 2024 documents/requirements for ad-hoc flight operations
- CAASL: published commercial charter/ad-hoc aviation-security requirements
- CAASL: aircraft-operations FAQ and commercial certification routes
- Retrieved June 2026 eAIP: ENR 1.10 flight planning
- AIM Sri Lanka: current publication access
Send SEAS your commercial charter coordination enquiry with the flight purpose, aircraft, operator, itinerary and planned frequency. Agree the channel for supporting documents with the operations team.
Updated 8 October 2026. This article explains planning and coordination. Use the effective AIP, applicable amendments, supplements and NOTAMs for the flight date. The operator and pilot remain responsible for operational decisions and compliance.
Flying Into Sri Lanka? Start With the Operations Desk
Ground handling, overflight and landing permits, Jet A-1 uplift, airport slots, PPR and parking, and complete trip support — the whole Sri Lanka segment coordinated by one team. Send your aircraft details, routing and dates.

