Why international filing is harder than it looks
A domestic flight plan is a routine form. An international one is a negotiation with every airspace the route crosses: each FIR has its own entry and exit points, some routes are mandatory, some are forbidden at certain hours, and the equipment codes in the plan determine which routes and levels the aircraft will be offered. A plan that is technically valid can still produce a bad route, a fuel penalty or a refusal if it does not match what the airspace actually allows.
The 2012 ICAO flight plan format made precision mandatory: navigation specifications, surveillance equipment and performance-based navigation codes all have to be declared correctly, because the route and level you are cleared on depend on them. An aircraft coded wrongly can find itself routed off an RNAV airway it needed, or offered a level it cannot accept. Getting the codes right is not bureaucracy — it determines the flight you actually fly.
What LFS checks before a plan is filed
Every filing starts with the route. The desk validates the proposed routing against current airspace restrictions, published route availability and known flow measures, using the controlling aeronautical publications rather than a previous trip's plan. Routing that worked last month may be closed, restructured or subject to new restrictions — the FAA's international flying guidance and the relevant national AIPs are the references that govern, not habit.
The aircraft's equipment and capability codes are confirmed with the operator before filing, because only the operator knows the aircraft's actual approved configuration. The schedule is checked against slot requirements, airport curfews and permit validity windows, so the filed plan matches the permissions the flight actually holds. A plan filed for a time outside the permit window can be refused or, worse, accepted and then create a compliance problem on arrival.
Filing with the right units, in the right order
International plans are filed with the ATS units responsible for each part of the route — in Europe through the centralised IFPS, elsewhere with individual national units, each with its own lead times and addressing. A plan that crosses ten FIRs has to be acceptable to all of them, and a rejection from one can require re-routing that affects the rest. The desk files with the correct addresses and monitors for acknowledgements and rejections until the plan is accepted along the whole route.
Rejection handling is where filing support earns its keep. A rejected plan comes back with a reason — an invalid point, a closed route, a timing conflict — and each rejection costs time against the departure. The desk reads the rejection, corrects or re-routes, and refiles, keeping the operator informed. The aim is that the crew arrives at the aircraft with an accepted plan, not a puzzle.
Amendments, delays and cancellations
Plans change. A departure that slips past its tolerance needs a delay message; a route change needs an amendment; a cancelled flight needs a cancellation so the slot and the airspace are released. Unmanaged amendments are a common source of operational friction: a flight that departs significantly outside its filed time without a delay message can lose its place in the traffic sequence or attract attention from flow management.
The desk manages the message traffic around the plan — delay, amendment and cancellation messages — as the schedule moves, and coordinates the downstream effects: a new departure time may need a revised slot, an updated handling time and a check that the permit window still covers the movement. Because the same desk handles dispatch and permits, the plan, the permissions and the ground arrangements stay consistent with each other.
Flight plans and permits are not the same thing
A filed and accepted ATS flight plan means the air traffic system expects the flight. It does not mean the flight has permission to operate. Overflight and landing permits, diplomatic clearances, slots and airport approvals are separate requirements, granted by separate authorities, and an accepted flight plan satisfies none of them. Equally, holding a permit does not remove the need to file.
This distinction matters operationally: a crew can depart on an accepted plan and still arrive to a compliance problem if a required permit was missing, and an operator can hold every permit and still not depart because no plan was filed. The desk tracks both tracks in parallel for each trip and reports their status separately, so nothing is assumed from one to the other.
Filing support for your operation
Filing support is included in every trip LFS dispatches, and is available as a standalone service for operators who plan their own routes but want a specialist desk handling the filing, monitoring and amendment workload. It suits operators flying unfamiliar regions, ad hoc charter with short notice periods, and flight departments without a 24/7 filing capability.
Send your aircraft details, route and schedule through the request form and the desk will confirm the filing requirements for the route, the lead times involved and what it needs from you. For the wider planning picture around the filing — fuel, alternates, briefing — see international flight planning.
Common filing errors and how they are avoided
Most rejected plans fail on a small set of avoidable errors: a waypoint name that does not match the current AIRAC cycle, an equipment code inconsistent with the route requested, a departure time in the wrong format or outside the filing window, and addressing that misses a unit which expected a copy. Each error is minor in isolation and expensive in aggregate, because every rejection-and-refile cycle consumes the margin before departure.
The desk's defence is process rather than brilliance: current navigation data, a checklist for the plan's fields, and a human reading the acknowledgement messages instead of assuming acceptance. Where a route is new to the operation, the plan is built and checked earlier than usual, leaving time for the rejection cycle that new routes tend to attract. Experience matters here mostly as pattern recognition — knowing which FIRs query which kinds of plans, and pre-empting the query in the filing itself.
Filing support across regions
Filing mechanics differ by region. Within Europe, a single IFPS submission covers the participating states and centralises validation. Elsewhere — much of the Middle East, Asia, Africa and the Americas — plans are addressed to individual national units, each with its own lead time, format expectations and reliability of acknowledgement. Oceanic crossings add their own clearances and position reporting requirements on top.
The desk files according to the region's actual practice, not a single global assumption, and monitors each unit's response separately. A plan accepted in Europe but unacknowledged by a unit further along the route is treated as unfinished, and the follow-up happens before the crew is at the aircraft asking. This regional detail is the part of filing support that is hardest to replicate with software alone.
What the crew receives
Filing support ends at the aircraft, not at the ATS unit. The crew's briefing package shows the filed route as accepted, the planned times, and any constraints that shaped the plan — a slot, a curfew, a permit window — so the crew understands not just what was filed but why. Where the plan filed differs from the plan the operator requested, the difference is stated plainly with its reason.
If anything changes after the package is issued, the crew receives the revision with a clear version reference, and superseded versions are withdrawn from the active set. A crew that has to guess which of two similar plans is current is a risk that good document control removes entirely. The desk's standard is that the latest version is unambiguous at a glance, even at 04:00 on a dark ramp.
Operational planning questions
Does an accepted flight plan mean the flight is approved?
No. ATS acceptance means the air traffic system has processed the plan. Overflight and landing permits, slots and airport approvals are separate requirements granted by separate authorities. LFS tracks both and reports them separately.
Who provides the aircraft equipment codes?
The operator. Only the operator knows the aircraft's approved navigation and surveillance configuration. LFS files what the operator confirms and flags codes that affect routing or levels, but does not certify aircraft capability.
What happens if a plan is rejected?
The desk reads the rejection reason, corrects the error or re-routes, and refiles, keeping the operator informed. Rejections are worked until the plan is accepted along the whole route or the operator decides to change the plan.
How much notice does international filing need?
Plans can be filed up to 120 hours before departure and, in many regions, quite close to departure — but short-notice filing leaves no time to fix rejections. For new or complex routes, earlier is safer. The desk advises per route.
Can LFS file for flights it did not plan?
Yes. Standalone filing support covers routes planned by your own team. The desk needs the route, aircraft details, schedule and equipment codes, and will flag anything that looks unworkable before filing.
Operational references
Reviewed 23 October 2026. Current AIPs, NOTAMs, authority decisions and written provider acceptance govern the actual flight.
Send your operational requirements
Provide your route, aircraft details, UTC schedule and required services. LFS will review the request and confirm the proposed coordination scope, documentation and commercial terms. Acceptance remains with the relevant authority, airport and service provider.
Request a Quote
