Paris Orly Airport Code: ORY & LFPO Explained

Paris Orly has two primary airport codes: ORY for commercial and passenger use, and LFPO for pilot, flight planning, and ATC operations. If you're flying there, the code that belongs in your EFB, flight plan, briefing workflow, and cockpit paperwork is LFPO, not ORY.

That distinction trips up a lot of pilots because both codes point to the same physical airport. Your passengers may say they're flying into Orly and show you a booking with ORY on it, while your avionics, charts, and planning tools expect LFPO. For a student pilot preparing for an international cross-country, this isn't trivia. It's part of good cockpit discipline.

When workload rises, small labeling mistakes create avoidable friction. The point of understanding the Paris Orly airport code isn't to memorize two abbreviations. It's to know which code belongs in which task, so you don't add confusion during planning, programming, or radio work.

Planning a Flight to Paris Decoding the Airport Codes

You are loading the destination into the EFB before departure. The chart binder, flight plan form, and avionics want one code. Your passengers, the handling agent, and the itinerary email keep showing another. At Paris Orly, that split can create avoidable confusion if you do not sort it out early in your workflow.

At this airport, ORY and LFPO both refer to Orly, but they serve different jobs. ORY belongs to the commercial and passenger side. LFPO belongs to the operational side that pilots use to file, brief, and verify the correct destination. For a pilot, that is more than trivia. It is basic error prevention.

Orly is one of France's major airports, with heavy airline traffic and tightly managed flows. In that setting, code discipline matters because the wrong identifier can slow down flight planning, chart retrieval, dispatcher coordination, and data entry in the cockpit. If you want more pilot-focused breakdowns of code usage and planning workflow, the PilotGPT aviation blog covers similar operational topics.

A common assumption for student pilots is that the code on the ticket must be the code for everything else. That assumption usually holds until the first international planning session. Then the mismatch shows up. The booking says ORY, while the flight plan software asks for LFPO.

The easiest way to organize it in your head is by task:

• Booking and passenger handling: ORY
• Flight plans, charts, and avionics databases: LFPO
• ATC and operational coordination: LFPO

That split works like using a city nickname in conversation versus a full street address for delivery. One is easy for the public to recognize. The other gets you to the exact place without ambiguity.

Practical cockpit rule: If the task affects routing, performance planning, chart selection, or ATC coordination, verify the ICAO code first.

Build that habit before engine start, and the rest of the Paris planning chain gets cleaner.

The Critical Difference Between IATA and ICAO Codes

Most code confusion disappears once you stop treating airport codes as one category. They aren't. They serve different users and different systems.

IATA codes are designed for commercial travel. They are short, easy to read, and public-facing. ORY fits that role. Passengers see it on bookings, departure boards, and luggage tags.

ICAO codes are operational identifiers. They are built for precision in global aviation workflows. LFPO is the code that belongs in pilot planning and ATC systems.

A simple way to remember it

Think of ORY as the airport's public nameplate. Think of LFPO as its technical street address plus routing information.

If you mailed an important package using only a nickname for the building, someone might eventually figure it out. But official systems don't want "close enough." They want a precise destination. That's what ICAO coding provides.

The code LFPO is the technical identifier embedded in avionics, POH references, and IFR approach material. It ties the airport to precise geolocation at 48°43'34"N, 2°21'51"E and supports runway alignment data, as described in this pilot-focused explanation of the Paris Orly code distinction. That same source notes that ORY lacks the regional identifier L used in routing structure for France.

Why that matters in the cockpit

A passenger can say, "I'm going to ORY," and everyone understands them. A flight management system needs something tighter. It needs the code used by navigation databases, dispatch logic, and ATC-facing workflows.

That difference shows up in practical tasks:

• Flight planning software: It expects LFPO.
• Weather retrieval tied to airport operations: Pilots use the ICAO identifier.
• Approach and chart lookup: ICAO is the standard operational reference.
• ATC and system clarity: Regional coding helps remove guesswork.

For broader pilot training context, the PilotGPT aviation blog has more material on cockpit workflow and operational references.

Use ORY when you're talking like a traveler. Use LFPO when you're acting like a pilot.

That's the distinction in one sentence.

Operational Deep Dive Paris Orly LFPO for Pilots

You are inbound to Paris after a long cross-country, the radios are busy, and the arrival starts tightening up. In that moment, LFPO is more than a label in the flight plan. It is the key that connects your charts, procedures, airport restrictions, and cockpit setup into one consistent picture.

For pilot use, the safest habit is simple. Treat LFPO as the airport's operational name. That is the identifier you use when consulting the French AIP for the airport chart, runway data, instrument procedures, and published restrictions in the official French AIP entry for Paris Orly. Passenger-facing references can tolerate shorthand. Flight planning and approach preparation cannot.

The runway picture pilots need

One common trap for less experienced crews is assuming every published runway is equally likely to be assigned. At Orly, that can lead to a weak arrival brief. A better method is to review the airport layout, then separate normal-use runways from configurations you may see only in less common conditions.

That changes how you brief the arrival in practice:

• Start with the likely operating configuration. Build your first expectation around the runways and procedures most commonly used in airline and ATC flow.
• Keep the full airport diagram in view. If ATC assigns something less common, you want recognition, not surprise.
• Cross-check the box against the clearance. FMS selections, approach charts, and standby notes should all match the runway assigned.
• Slow down when the plan changes. A runway change close in is not hard if the crew catches it early and verifies every related item.

That last point matters. At a busy airport, a runway change is rarely just a runway change. It can also mean a different transition, different missed approach, different taxi expectation, and a different mental picture out the window.

Restrictions and local rules affect the whole plan

Orly is also the kind of airport where local operating limits can shape the flight long before descent. Noise procedures, access limits, slot coordination, and time-based restrictions are not side notes. They influence whether the trip is practical, what alternate makes sense, and how much delay margin you should carry.

For a student pilot, the easiest way to understand this is to treat airport restrictions like weather minima. They are part of go or no-go thinking, not trivia to skim after engine start.

Use LFPO as the thread that ties those details together during preflight. Pull the airport entry, read the remarks, review current NOTAMs, then confirm that your route, ETA, fuel, alternate, and arrival briefing still work as a set.

Why LFPO belongs in cockpit workflow

The code matters because your operational tools are built around it. Procedure lookup, airport chart selection, weather products used in dispatch and IFR planning, and many avionics database entries all expect the ICAO identifier. Using the correct code reduces the chance of loading the wrong airport data or briefing from the wrong reference set.

A practical cockpit flow looks like this:

1. Enter LFPO in planning software and avionics.
2. Pull the airport diagram and instrument procedures for LFPO.
3. Review NOTAMs and operating remarks tied to LFPO.
4. Brief the likely runway and one realistic alternate scenario.
5. Recheck the clearance against what is loaded before descent and again before the approach.

That is disciplined workflow, not bureaucracy. It keeps the airplane, the charts, and the crew on the same page.

For safety-minded flight prep, the PilotGPT safety resources for reducing cockpit workload are aimed at planning, briefing, and cross-checking tasks before arrival.

A quick field video can help you build a visual picture before arrival:

Comparing Paris Airports From the Cockpit

If you're choosing a Paris-area airport, code knowledge alone won't make the decision for you. Mission type matters. So does how much complexity you're willing to absorb in busy airspace.

A pilot comparing Paris airports usually cares about access, handling friction, and how well the airport fits the flight. That lens is different from a traveler comparing convenience or terminal shops.

Pilot's Comparison of Paris Airports

How to think through the choice

For a general aviation pilot, Le Bourget often makes the most sense when the goal is easier compatibility with private flying. Orly and Charles de Gaulle are major airline environments first. That doesn't make them unusable. It means you should expect more procedural and coordination overhead.

Here are the decision criteria I'd teach a student to use:

• Mission fit: If you need Orly specifically because of passenger logistics or destination needs, plan for LFPO carefully and early.
• Workload tolerance: If you're newer to international ops, a GA-oriented field may be the smarter first choice.
• Handling complexity: Big commercial airports can increase coordination demands on the ground as well as in the air.
• Traffic mix: Airline-heavy fields can push your pace faster than a lower-time pilot would prefer.

In busy international airspace, the best airport isn't always the biggest or closest. It's the one that matches your airplane, your experience, and your margin.

If you're reviewing airport options more broadly, the PilotGPT airport resources are organized around pilot decision-making rather than tourist convenience.

Using ORY and LFPO in Practice

The Paris Orly airport code question becomes easy. Stop asking which code is "correct." Ask which system you're talking to.

What goes where

If you're filling out a route in ForeFlight, Garmin Pilot, or another EFB, enter LFPO in the destination field. If you're programming an FMS, looking up procedures, or briefing weather and operational data tied to the airport, use LFPO again.

If your passenger sends you an itinerary, the airport will likely appear as ORY. That's normal. Booking systems and passenger-facing tools are built around the IATA code.

A practical split looks like this:

• Use ORY for: airline bookings, boarding passes, baggage tags, public-facing schedule references
• Use LFPO for: flight plan filing, ATC-related workflow, chart lookup, pilot briefings, navigation system entry

The cockpit rule to memorize

When pilots get busy, memory aids should be short. Here's the one I recommend:

If it happens in the cabin, think ORY. If it happens in the cockpit, think LFPO.

That rule won't cover every edge case in global aviation, but it works very well for Orly and prevents the most common mistake. If you're ever unsure, ask yourself whether the task is commercial-facing or operationally safety-critical. That usually answers it immediately.

Frequently Asked Questions About Paris Airport Codes

What happens if I file with ORY instead of LFPO

You're creating avoidable confusion. Operational systems expect the ICAO identifier for pilot and ATC workflows, so LFPO is the correct code to use in flight planning and related cockpit tasks.

Does this matter for VFR flights too

Yes. The code distinction isn't only for airline or IFR operations. If the task involves pilot planning, airport operational references, or communication workflow, using the operational identifier keeps your process clean.

What code will my passengers recognize

Usually ORY. That's the public label travelers see in booking engines, ticketing systems, and baggage workflows.

What about the other major Paris airports

Pilots will commonly encounter LFPG for Paris Charles de Gaulle and LFPB for Paris-Le Bourget. Travelers usually know those same airports by their passenger-facing codes, but in the cockpit you should keep thinking in ICAO identifiers.

What's the safest habit to build

Don't translate codes mentally at the last minute. Build the habit early. Passenger conversation can stay in IATA. Flight planning, charts, avionics, and ATC prep should stay in ICAO.

---

If you want a tool built around that exact kind of cockpit discipline, PilotGPT is worth a look. It's designed for real-world flying, helps reduce workload in high-task phases, and gives pilots fast access to the operational information that matters when you need the right answer, not another guess.