Representative aviation imagery, including illustrations; not evidence of LFS facilities or personnel in this region.
Start with the mission, not a regional service assumption
An executive visit to Nairobi, a charter into Tanzania and a humanitarian cargo rotation can all require East Africa flight support, but they do not require the same ground plan. The arrival airport, flight purpose, aircraft, people on board and intended onward sector determine what needs to be checked. Describe the mission clearly, including any positioning or technical legs. It is particularly important to distinguish a passenger visit from a cargo delivery when the schedule includes several destinations.
LFS brings the coordination work into one trip file: authority requests, provider contacts, requested fuel, handling acceptance and crew or passenger logistics. Local licensed providers carry out the agreed airport services. The regional desk’s availability does not mean every airport is continuously open or every service can be delivered without notice. The operator keeps operational control, and the pilot in command remains responsible for the decision to operate.
Kenya, Tanzania and the wider route
Use the existing Kenya flight-support briefing and Tanzania flight-support briefing for country-level context. Airport enquiries can start with Nairobi Jomo Kenyatta HKJK or Dar es Salaam HTDA. An airport’s presence in the directory identifies a place to investigate; it is not confirmation of a parking stand, fuel uplift or handling acceptance for your flight.
For a route continuing beyond those destinations, submit every country and intended stop rather than extending one country’s assumptions across the region. A commercial charter, a private flight and a government movement may follow different approval processes. If a destination is not in your existing trip file, ask the desk to establish the local coordination scope before committing it to the schedule. No LFS-owned Kenyan or Tanzanian station is asserted on this regional page.
Permits and documentation for the whole flight chain
Separate overflight requirements from landing requirements and record which approvals relate to which sector. Entry and exit points, UTC times and aircraft details need to remain consistent across the applications. LFS coordinates overflight requests and landing requests, follows up on authority questions and reports the status. Lead times, supporting documents and validity are country- and mission-specific; the desk confirms them for the actual request.
Humanitarian or time-sensitive work should not be presented as automatically exempt from aviation or border approvals. Explain the purpose, the requesting organisation and the required timing, and supply any supporting documents the authority asks for. Where an approval is outstanding, that status needs to be explicit. A submitted application is not a clearance to depart, and an urgent handling request does not guarantee an airport can accept the aircraft.
Airport suitability and the difference between a runway and a workable stop
Runway data alone does not establish that an airport can support the intended operation. The operator must assess aircraft performance, current runway conditions, approach availability and operational limitations using authoritative information. The ground coordination review asks a separate set of questions: can the provider receive the aircraft at that time, are the required services confirmed, can international formalities be completed and is the planned parking duration accepted?
These checks matter when a main gateway connects to a smaller destination. Do not assume that services at the international arrival airport are also available at the next airfield. Identify the essential items and distinguish them from preferences. If towing, stairs, ground power or a particular passenger arrangement is essential, request confirmation for the aircraft type. A directory entry or an indicative specification is not evidence of a currently available handler.
Fuel uplift and technical-stop decisions
A technical stop is only useful if the operational route and the ground arrangements work together. The operator defines the fuel requirement and performance plan; LFS requests confirmation of the uplift, supplier acceptance, timing and payment terms. Include expected quantities and any flexibility in the proposed stop. A general statement that an airport offers fuel is not enough to rely on a particular uplift at a particular hour.
Use aircraft fuel coordination and technical-stop support when comparing options. Ask what is confirmed in writing and what still needs a provider response. If the schedule changes substantially, reconfirm fuel and handling together. A refuelling delay can affect crew duty, the validity of later approvals and the reception plan at the final destination, so those consequences belong in the same update rather than separate messages.
Cargo and humanitarian movements need a specific ground brief
For cargo, send the commodity description, dimensions, weights and handling requirements early. Indicate whether the load includes regulated or temperature-sensitive goods, and identify the shipper, consignee and local customs contact. The operator remains responsible for its carriage approvals and load-control procedures. LFS can coordinate the requested local support, but acceptance of the consignment and the availability of suitable equipment must be established for the actual airport.
For humanitarian work, distinguish the aviation movement from the distribution activity after arrival. A handler’s ability to receive an aircraft does not establish that an onward delivery or a special customs process has been agreed. Include unloading priorities, expected ground duration and the receiving organisation’s contact. The cargo charter service and humanitarian operations page explain the existing LFS support scope without implying automatic clearances or guaranteed airport access.
Crew logistics and a credible onward schedule
An overnight stay needs a hotel and transport plan that fits the operator’s duty and rest arrangements. Give the desk the crew count, expected arrival and next departure, entry-document considerations and any planned crew change. Ground travel time and airport access should be discussed before treating a short rest interval as practical. Duty compliance remains with the operator; a hotel booking does not itself establish a legal rest opportunity.
Passenger logistics require the same precision. State whether passengers enter the country, continue on a domestic leg or remain with the aircraft for a technical stop. Border requirements depend on nationality and the actual movement. LFS coordinates crew logistics and requested ground arrangements with local providers. Where a timing or access condition is unresolved, it should be flagged before the crew receives a final trip brief.
Keep contingency decisions grounded in current information
Kenya’s aeronautical information services and the relevant national AIPs and NOTAMs provide operational information for the dates of flight. Weather, airspace notices and airport conditions can change a plan that was workable when first requested. The operator reviews those sources for release and safety decisions. The LFS desk uses the revised itinerary to check what changes in the requested approvals and ground services.
If an alternate becomes the destination, identify the actual airport and intended ground duration immediately. Recheck reception, fuel, border arrangements and onward logistics rather than assuming the original provider booking transfers. The existing diversion support page is relevant to that coordination. A conservative contingency brief states what has been checked, which contacts are available and what remains unconfirmed; it should not promise access to every airfield in the region.
Send a request that can be scoped and priced
Include the complete route, UTC schedule, aircraft type and registration, flight purpose, passengers, crew and any cargo. List the support required at each stop and mark time-critical requirements. Ask for the commercial scope, exclusions, payment conditions and cancellation or schedule-change terms alongside the operational status. For multi-leg work, nominate one contact who can confirm the current itinerary when different teams are involved.
Submit through the existing LFS enquiry page. The desk can then review the route, identify the authorities and providers that need to respond, and tell you what further documents are needed. Clear information supports a useful enquiry; it does not create a guarantee of permit approval or service availability. Final acceptance should be visible in the trip brief before the operator relies on the arrangement.
Regional flight-support questions
Can LFS coordinate handling in Nairobi and Dar es Salaam?
LFS can review handling requests for HKJK and HTDA with local providers. Include aircraft details, flight purpose and UTC times; airport acceptance and requested equipment must be confirmed for the movement. Discuss your trip with LFS.
Can LFS coordinate fuel for an East Africa technical stop?
LFS requests fuel supplier acceptance, uplift timing and payment terms alongside handling. Send the proposed airport and quantity; live fuel availability is not guaranteed, and operational suitability remains the operator’s decision. Discuss your trip with LFS.
Does LFS operate its own stations throughout East Africa?
This regional service is described as coordination through vetted local providers. Do not infer an LFS-owned station from an airport directory link. The desk will confirm the delivery arrangement for the airport and services requested. Discuss your trip with LFS.
Can you coordinate humanitarian and cargo flights?
You can submit those missions for review. Include flight purpose, consignment details, receiving contacts and timing. Aviation approval, customs acceptance and suitable ground support must each be confirmed; none is automatic because a flight is humanitarian. Discuss your trip with LFS.
How early should an East Africa permit request be sent?
As soon as the route and mission details are available. There is no universal regional lead time. The relevant authority, type of operation and supporting documents determine the application process and expected response. Discuss your trip with LFS.
Can a smaller airport be used as a fuel stop?
Only after the operator assesses operational suitability and the required fuel, handling, airport acceptance and formalities are confirmed. A runway listing does not establish those services. Send the aircraft and proposed stop for a specific review. Discuss your trip with LFS.
Where do I submit a multi-country trip?
Use the existing LFS request page with the complete itinerary, UTC times, aircraft details and support needed at every stop. Include any approvals or provider arrangements you already hold to avoid duplicate requests. Discuss your trip with LFS.
Operational references
Reviewed 3 November 2026. Current AIPs, NOTAMs, authority decisions and written provider acceptance govern the actual flight. References support planning checks, not a claim of LFS station ownership.
Send the complete itinerary
Provide the aircraft, route, UTC schedule, flight purpose and services required at each stop. The LFS desk will review the coordination scope, supporting documents and commercial terms.
Request flight support