Salalah Aircraft Ground Handling
Salalah aircraft ground handling is planned for OOSA/SLL in Dhofar, Oman. LFS coordinates the movement with local providers and reviews the applicable permissions. Salalah is not Muscat OOMS/MCT; keep the correct airport code on every request.
Request Ground Handling Support
Salalah and Muscat are different operating locations
Salalah Airport serves Dhofar in southern Oman. Oman’s Civil Aviation Authority identifies Salalah separately from Muscat, and Oman Airports lists both airports in its network. OOSA/SLL belongs to Salalah; OOMS/MCT belongs to Muscat. The distinction matters in handling orders, permission applications, fuel releases and crew transport.
This guide addresses Salalah rather than transferring Muscat service assumptions to a different airport. Airport infrastructure is not proof of specific equipment or aircraft acceptance. Use current Oman AIP data, NOTAMs and the operator’s performance documentation for the movement.
Notice periods depend on what is being approved
A handling request, landing permission and any special clearance are different processes. An earlier 24–48-hour handling estimate should not be read as overriding an authority’s filing requirement. Nor should a generic country-level working-day estimate be treated as a current airport rule for every flight.
Send the itinerary as soon as it is known and ask which permission applies to the operator, registration and private, commercial, state or medical status. The landing permits desk checks the current requirement and identifies conditions or missing documents. No fixed notice period guarantees acceptance, and short-notice urgency does not waive approval.
Ground services and an aircraft-specific scope
Provide exact model, registration, operating weight and configuration. For power, cooling, towing, stairs and servicing, give the aircraft’s required interfaces rather than an unspecified full handling order. The station provider must confirm availability, capacity and the requested service time.
LFS coordination is distinct from airport ownership and licensed ramp delivery. If a terminal, cargo load or engineering request is involved, identify the responsible provider and the agreed scope in the briefing. Do not assume equipment visible in an illustrative image is available at Salalah for your movement.
Arrival, parking and passenger processing
Reconcile UTC arrival and departure, origin, onward sector, crew and passenger data before dispatch. Request airport acceptance and the complete parking period separately from permits and fuel. If overnight parking needs towing, security or repositioning, obtain those terms before accepting the plan.
Border and customs arrangements depend on the flight and occupants. Ask where passengers and crew will be processed and how the ground transfer will meet them. Missing database hours are unverified, not proof of unavailable service or unrestricted access.
Khareef and weather-aware planning
Salalah’s Khareef season is a distinctive local planning context: cloud, moisture and visibility can differ from the dry-desert conditions operators associate with other Gulf airports. Review the actual forecast, METAR, NOTAMs and approach requirements rather than assuming the airport shares Muscat’s weather.
Agree a suitable alternate and diversion communication plan under the operator’s procedures. A delay can change parking, crew accommodation and catering requirements. Use flight watch to keep the desk and station provider working from the latest aircraft progress, without promising operation despite weather or restrictions.
Fuel and technical-stop sequencing
For fuel coordination, provide grade, anticipated uplift, units and release or payment details. The supplier confirms acceptance and delivery arrangements. A commercial release is not evidence that the aircraft can depart at a particular weight or that ground time will be fixed.
For a technical stop, state whether passengers remain aboard, crew change and what formalities apply. Sequence fuelling, documentation and any required services before quoting a turn. A medical or urgent flight still requires authority and provider acceptance; identifying urgency early lets the desk review the correct process.
Crew logistics and departure handover
Request crew rooms and transfers against the planned duty and rest period. Tourism demand around Salalah can affect preferred accommodation, but no availability or transfer-time promise is made. Agree check-in, check-out and transport capacity with the actual provider.
Before departure, ask for a consolidated status: correct OOSA identifiers, permissions, handling contact, parking, fuel, passenger process and unresolved conditions. A revised route or schedule may require amendment of several items, so request explicit reconfirmation. After the flight, reconcile actual services and uplift against the agreed order.
A Salalah mission brief for different operators
A corporate or charter visit should identify the destination around Salalah, passenger count and intended aircraft stay. A seasonal visit may require different hotel and parking dates from the original proposal. Separate the passenger itinerary from an aircraft repositioning plan and obtain acceptance for both.
For a cargo or special-load movement, provide commodity, dimensions, weights and dangerous-goods status where applicable. Loading equipment, customs responsibility and storage conditions need a specific provider review. A passenger handling acceptance does not establish the ability to support a freighter or temperature-sensitive shipment.
For a medical movement, identify the responsible clinical liaison, aircraft configuration and required ground-transfer interfaces. The desk coordinates the aviation request and contacts; it does not guarantee medical access or decide clinical suitability. Send the relevant urgency and documentation early so the actual approval process can be reviewed.
Frequently asked questions
What is the airport code for Salalah?
Salalah is OOSA/SLL. Muscat is OOMS/MCT and is a different airport.
Does a 24–48-hour estimate replace permit requirements?
No. Handling preparation and authority approval have different timelines. The applicable current requirement must be checked for the actual operation.
Can Salalah be used for a technical stop?
Submit the route and service requirements for a feasibility review. Airport acceptance, permissions, fuel and formalities need confirmation.
Does Khareef mean the airport cannot be used?
No blanket conclusion applies. Current weather, procedures, aircraft capability and authority restrictions govern each flight.
Official and reference sources
Reviewed 2 November 2026. Current AIP, NOTAMs, authority requirements and written provider confirmations govern each flight.
Send your flight details
Share your route, aircraft, UTC schedule and the services you need. The LFS desk will review the request and confirm documentation, availability and terms. Permits and access remain subject to approval by the relevant authority.
Request Flight SupportAircraft length reference at OOSA
Wide-body cargo
Narrow-body cargo
Wide-body passenger
Narrow-body passenger
Request Ground Handling Support
Send registration, aircraft type, route and dates. You get one reply with the ramp plan, permit lead time, slot position and a fuel price for Salalah International Airport.
