Air Permit Planner

Every flight crosses a sequence of countries. Each one sets its own permit conditions.

Amsterdam to Seoul crosses twenty-two flight information regions in thirteen countries: overflight permits along the way, and a landing permit at the destination. Air Permit Planner reads your schedule, checks every flight against every permit rule, and keeps the permit record in one place as the schedule changes.

For permitting and flight operations teams at cargo, charter and scheduled airlines, and the planning teams whose schedules they cover.

Amsterdam to Seoul

One flight, and the airspace it crosses

TRACK: AMS TO ICN, 24 AUG 2026. FIR BOUNDARIES AS PUBLISHED
A real track from Amsterdam to Incheon, and the flight information regions it enters in order. Each tinted region is an airspace whose authority sets its own permit conditions.

How it fits together

Works from the schedule you already have.

Flights are read on a continuous feed from your data lake, where the schedule and the filed flight plans already arrive. Each flight is matched against the permit rules your permitting team has defined, authority by authority. Click a box to see what it does.

Click a box
Air Permit PlannerPermit rules and the permit record

Every flight, every permit rule, every change. Holds the permit record and runs the checks that keep it current.


One flight, start to finish

Here is a flight into Seoul, from Singapore, with its own permits to hold.

One flight, followed through the permitting process end to end: the schedule comes in, a gap is found, an application goes out, the approval comes back, the schedule changes, and the record is kept current.

  1. The row already carries every airspace the flight crosses, with the state of the permit for each. Nothing is typed in: the airspaces come from the filed flight plan, the permit states from the record.

  2. Six airspaces are covered by permits on file. Vietnam is not, so the flight is not valid yet. The requirement says what the authority asks for, and the application can be drafted from it.

  3. On your template, with the flight details taken from the schedule: registration, dates, times, entry and exit points. Downloaded, sent from your mailbox, and marked as sent.

  4. The reply is dropped into Record. The tool reads the letter and proposes the entry: authority, permit reference, validity window, approved registration and flight numbers.

    Nothing is filed until your permitting team has checked the proposal against the letter and confirmed it. The permit is attached to the flight it covers, and marked as valid.

  5. The change arrives on the same feed. Some permits cover a whole season. Others hold for one registration, one validity window and set entry and exit points, so a delay, a tail swap or a routing change can put a flight outside its permit.

    It is flagged, with the reason, and the permitting team decides: reapply, amend, or override. The team always has the final say.

  6. Every flight, every permit and its current state are visible on one board. It can be filtered and exported, and the permit state can be written back to the data lake, so that the permit record sits next to the schedule it belongs to, for any system that needs it.

Air Permit PlannerScheduleFEED, SYNCED 06:40 UTC
ArrivingICNFlight8789+ filter
Flt numDateDepArrDep tEqpPermitting
5Y 811708SEP26ICNHAN11:40N419MCValid 4 of 4 legs authorised
5Y 878908SEP26SINICN02:00N419MCNot valid 6 of 7, application in progress
DepOverflight, in orderArr
SIN
Singapore
Malaysia
Vietnam
China
Hong Kong
China
South Korea
ICN
5Y 81108SEP26ICNPVG16:10N429MCValid 3 of 3 legs authorised
5Y 557908SEP26AMSICN13:20N856GTValid 23 of 23 legs authorised
5Y 431209SEP26ICNNRT03:30N419MCPending 2 of 3, confirmation in progress
The schedule, filtered to one arrival. The expanded row is the flight's permit journey: every airspace from the filed flight plan, in order, with the state of the permit for each.
Air Permit PlannerSchedule / 5Y 8789 / Dossier08SEP26, SIN to ICN
5Y 8789SIN → ICN, 08SEP26, N419MC, 747-400FNot valid
Permit journey
DepartureOverflight, in orderArrival
SINStation
1SingaporeCovered
2MalaysiaCovered
3VietnamNot covered
4ChinaCovered
5Hong KongCovered
4ChinaCovered
6South KoreaCovered
7ICNLanding
Covered 6Not covered 1
Requirements
1Overflight SingaporeValidok
2Overflight MalaysiaValidok
3Overflight VietnamNot validmissing
Civil Aviation Authority of Vietnam (VN)
Filed planConfirmedAssisted08SEP26

No permit on file covers this leg. Per-flight overflight: one registration, one validity window, entry and exit points as filed. Lead time 3 working days. Applied for directly, on the airline template.

Confirm scopeAttach permitMark not required
7Landing permit ICNValidok, KR-LDG-2026-8789, to 08SEP26
The dossier for one flight: the permit journey across every airspace, and the requirement behind each numbered step. One gap, and the action it calls for.
Air Permit PlannerApplications / VN overflight / 5Y 8789DRAFTED FROM REQUIREMENT
Overflight permit applicationCivil Aviation Authority of VietnamDraft
YOUR TEMPLATE / OVERFLIGHT / VNREF 5Y-VN-8789-260908

Subject: Request for overflight permission, 5Y 8789, 08 September 2026

We kindly request overflight permission for the following cargo flight through Ho Chi Minh FIR:

Operator5YAircraftB747-400F, N419MC
Flight5Y 8789Date08 SEP 2026
RoutingSIN 0200Z to ICN 0825ZEntry / exitas filed, VVTS
PurposeScheduled cargoDocumentsAOC, insurance, noise cert.

Please find attached the supporting documents. We would be grateful for your confirmation.

FLIGHT DETAILS FROM THE SCHEDULE, NOTHING RE-KEYED
The application, drafted from the requirement on your template. Flight details come from the schedule row, so the letter and the flight cannot disagree.
Air Permit PlannerRecord / Inbound1 DOCUMENT, 1 PROPOSAL
vn_8789_airspace_approval.eml
Read by the model6 fields found in the letter
From: AuthorityCivil Aviation Authority of Viet Nam, Flight Operations Department

Dear Sir/Madam, further to your request dated 05 Sep 2026, overflight permission is granted under reference Permit referenceVN-OVF-2026-8789 for aircraft RegistrationN419MC, operating flight Flight number5Y8789 from Singapore to Incheon, Validityvalid from 08 September to 10 September 2026, routing Entry and exitvia VVTS as filed. This permission is subject to the conditions stated in the annex, and to the payment of the applicable overflight charges.

Proposed from correspondenceHigh confidence
AuthorityCAA Viet Nam (VN)
Permit referenceVN-OVF-2026-8789
RegistrationN419MC
Flight numbers5Y 8789
Validity08SEP26 to 10SEP26
Entry and exitVVTS, as filed
Schedule cross-check
A PROPOSAL, NOT A WRITE. NOTHING IS FILED UNTIL CONFIRMED
The approval letter as it arrived, with the passages the model read marked and named, and the entry it proposes from them. The permitting team checks each field against the letter and confirms. If nothing matches the schedule, the tool says so.
Air Permit PlannerSchedule / 5Y 8789 / DossierSCHEDULE CHANGE, SYNC 14:05 UTC
5Y 8789SIN → ICN, 09SEP26, N419MCNot validchange invalidated cover
SINStation
1SingaporeCovered
2MalaysiaCovered
3VietnamCovered
4ChinaCovered
5Hong KongCovered
4ChinaCovered
6South KoreaCovered
7ICNNot covered
1 permit needs review after this schedule change. The leg arrives on 09SEP26 local time at the station, outside permit KR-LDG-2026-8789's validity (12AUG26 to 08SEP26). The Vietnam permit, valid to 10SEP26, still covers it.
Schedule, as it arrived
Arrival 08SEP 17:25 09SEP 13:25 local
Registration N419MC
Routing as filed
Permit on record
KR-LDG-2026-8789
Validity 12AUG26 to 08SEP26
Registration N419MC
DECISION AND REASON, TIMESTAMPED
A delay puts the flight outside its landing permit. The flag says which permit, and why. The decision stays with the permitting team, which can always override, and it is recorded with its reason. The original permit stays on record.
Air Permit PlannerScheduleALL FLIGHTS, SEP 2026
PermittingNot valid+ filterExport to Excel
FlightDateRouteRegistrationReasonPermitting
5Y 878909 SEPSIN ICNN419MCLanding, outside validityNot valid 6/7
5Y 58611 SEPGYD ZAZN856GTOverflight, tail swapNot valid 7/8
5Y 86212 SEPHSV LUXN429MCOverflight, missingNot valid 5/6
5Y 431214 SEPNRT NGON419MCLanding, expiring 13 SEPExpiring 3/3
PERMIT STATE WRITTEN BACK TO THE DATA LAKE, 14:06 UTC
One board for every flight and every permit: filter it, export it, write the state back.

What stays with the tool, what stays with you

Checking every change against every rule sits with the tool, so that your permitting team's time goes to the decisions.

Rules

Your permitting team sets them, authority by authority.

Seasonal or per flight. Direct or through an intermediary. Lead times, documents, what a permit fixes: registration, validity window, entry and exit points. The tool applies them; it does not invent them.

Record

One authoritative place for every permit and its state.

Required, drafted, sent, pending, valid, expiring, not valid. Attached to the flights it covers, with the letter behind it. Written back to your data lake for any system that needs it.

Decisions

Nothing is filed without a person's confirmation, and the permitting team can always override.

Proposals from inbound letters are confirmed by a person. Flags from schedule changes are decided by a person. The tool does the reading and the checking, and keeps the trail.

Bring one route and its permits.

A useful first session starts with one schedule feed, one authority's rules and one flight that crosses several. We will show the dossier, the application, the inbound letter, and what happens when the schedule moves.

info@leitmotif.systems