Operational notes — Jordan
## Jordan flight clearance — what to expect
LFS files Jordan overflight and landing permits as a daily core service. The Civil Aviation Regulatory Commission (CARC), Amman processes through a small, professional permits desk; their workflow rewards complete, correctly-formatted filings and quietly punishes ambiguity. Our ops controllers maintain the working relationships and the document templates that keep clearance times predictable.
### Lead times in practice
The published lead time for an overflight permit in Jordan is **24 hours**, and for a landing permit **48 hours**. In practice, LFS files most non-routine missions earlier than that. The reason is operational, not procedural: when the permits desk reviews a file in the last hour of validity, errors get amplified — typos in passport numbers, an insurance certificate that doesn't explicitly name the territory, a missing operator letter — and there's no buffer to fix them. We file early, hold the slot, and use the buffer to absorb late changes from the operator side: a tail swap, a crew change, a pax addition.
### What the file actually contains
A complete Jordan permit file is built from the airworthiness pack (AOC, COA, COR, CON), the insurance pack (COI with the right limits and territorial cover), the operational pack (crew list, pax manifest, itinerary in UTC, purpose of flight), and the operator letter on company letterhead addressed to the named authority section. For state, royal, military, dignitary, or medevac flights, a diplomatic clearance number from the originating country's MFA is added to the file before submission.
### Common failure modes
Most rejections in Jordan are not policy disputes — they are document discipline. Insurance certificates issued by US or EU underwriters frequently lack explicit territorial cover for the region; a one-line endorsement from the underwriter resolves it, but only if you catch it before filing. Crew lists and pax manifests often disagree on spelling between the captain's declaration and the operator's record system; we treat the captain's signed list as the single source of truth and re-issue from there. Operator letters signed by a dispatcher rather than a director or chief pilot get returned without comment; we keep templates with the correct signatory authority on file for repeat operators.
### Diplomatic, VIP, and state aircraft
Diplomatic clearance in Jordan runs through the MFA channel separately from the civil permit. The civil authority will not process a state or dignitary flight until the dip clearance number is issued and embedded in the operator letter. LFS coordinates the dip clearance request through the appropriate embassy channel for repeat principals, and we maintain the protocol pack — fast-track, security escort, separate immigration channel, motorcade access — that VIP and state ops require.
### Working hours and out-of-hours coverage
The Civil Aviation Regulatory Commission (CARC), Amman permits desk operates sun–thu 08:00–15:30 eet · after-hours via carc duty officer through lfs. Outside those hours, LFS holds 24/7 access to the duty controller for genuine ops emergencies — diversions, medevac, missions with already-approved permits requiring an ETA shift. We do not use the duty channel for routine filings. Plan your first-time filings inside working hours; subsequent revisions can ride on the existing file.
### What the operator gets from LFS
For Jordan, our deliverable is the issued permit number, the validity window, and any conditions attached — back to the operator within minutes of issuance, by email and on the trip sheet. We monitor the file for revisions throughout the validity window. If the authority adds conditions late (a slot change, a routing constraint, a diplomatic note), we surface it immediately and rebrief the crew and dispatcher before it becomes an in-flight problem.
### When to involve us
If you are filing for Jordan for the first time, file through us. If you are filing for a state, royal, or medevac mission, file through us. If your mission has a mixed crew nationality, dual-itinerary stops, or a sensitive principal, file through us. Routine repeat ops with stable documentation can be filed direct, but the failure cost when something slips — a turn cancelled, a principal stranded, a fuel uplift wasted — is high enough that most operators we work with file every Jordan mission through one channel for consistency.
LFS does not publish CAA phone numbers on this page by policy. Direct calls from operators outside the established workflow create noise the permits desk cannot absorb. Channel inquiries through ops@lfs.aero or the LFS ops desk and we route them appropriately.