If you are searching for how to translate airport codes, how to translate flight numbers, or how to handle airline names, terminals, gates and route information across languages, the first principle is that aviation identifiers are not ordinary vocabulary. Codes such as IATA airport codes, ICAO location identifiers, airline designators and flight numbers identify real operational entities. A translation can sound natural and still become dangerous or useless if one code, digit, airport name or route endpoint changes.
Aviation translation appears in tickets, boarding passes, airport websites, airline apps, timetables, disruption notices, baggage instructions, travel insurance, visa support, tourism information and passenger-service messages. The translator has to separate immutable identifiers from translatable labels. “Departure”, “arrival”, “gate”, “terminal”, “operated by”, “codeshare”, “connection” and “boarding” are language. SIN, LHR, JFK, SQ12 or another validated identifier is operational data.
This guide gives a practical system for translating airport and flight information without changing identity. It explains when to preserve IATA and ICAO codes, how to handle airports with local and English names, how to translate codeshare information, what to do with terminals and gates, how to keep origin and destination from reversing, and how to verify that the final target text still describes the same journey.
Why aviation identifiers need special handling
Aviation information is a layered system. An airport can have a public-facing IATA code, an ICAO identifier, a local official name, an English marketing name and terminals with separate labels. An airline can have a legal name, brand name, IATA designator, ICAO designator and call sign. A flight can have a marketing flight number and be physically operated by another carrier under a codeshare arrangement. Translation must preserve the distinctions because passengers and systems use them differently.
The second difficulty is route logic. A single line can include origin, destination, departure date, local time, terminal, gate, operator and status. If translation changes the order of locations or attaches the wrong terminal to the wrong airport, the sentence can remain grammatical while the journey becomes wrong. Aviation QA should therefore be relational, not merely lexical.
The third difficulty is that airport names themselves can vary. Cities can have multiple airports. One airport may be named after a person while travelers search by city. Another may use a local-language official name and a conventional English exonym. The translator should preserve the specific airport identity, not simplify every airport to the city name.
A reliable translation method
1. Lock codes and numbers before translating
Copy airport codes, airline designators, flight numbers, booking references, terminal identifiers and gate numbers into a protected list. These strings should not be paraphrased or normalized by language tools. Treat them as identifiers first and typography second.
2. Identify the exact airport, not only the city
If a city has several airports, resolve the code and full airport name. Translating “London airport” where the source names Heathrow, Gatwick or Stansted destroys information. Airport identity must remain specific.
3. Separate marketing carrier from operating carrier
Codeshare travel can list one airline’s flight number while another airline operates the aircraft. Translate “operated by” and similar labels precisely. Do not collapse both carriers into one name because passenger check-in, baggage and service responsibilities can differ.
4. Preserve origin-destination direction
Identify which airport is departure and which is arrival before changing word order. Some target languages naturally reorder phrases; that is fine as long as route direction remains the same. Verify arrows, “from/to” labels and table columns together.
5. Keep local time attached to the correct airport
Flight schedules normally use local time at each airport. Translation should not convert those times unless the task explicitly requires it. If a separate time-zone conversion is added, label it clearly so passengers do not mistake it for the official schedule.
6. Preserve terminal and gate hierarchy
Terminal, concourse, pier, zone and gate labels are distinct. Translate the generic label where appropriate while preserving the identifier, such as Terminal 3 or Gate B12. Do not convert B12 into “12B” unless the airport itself uses that form.
7. Use official names where available
Airports and airlines often publish multilingual names. Prefer the official form used by the operator or airport authority rather than inventing a literal translation. If no official target name exists, retain the recognized proper name and translate only descriptive material around it.
8. Test the journey as a passenger
Read the target as if you were traveling. Can you identify departure airport, destination, airline, flight number, departure time, terminal, gate and connection? This task-based check catches relationship errors that ordinary proofreading misses.
Twenty recurring aviation translation problems
1. IATA airport codes
Three-letter public-facing airport codes such as SIN or LHR are identifiers. Keep them unchanged and attached to the correct airport. Translating or “correcting” a code because it does not resemble the local airport name is an error.
When a translated airport name is unfamiliar, the code can improve recognition. A useful format is the official target-language airport name followed by the unchanged code in parentheses, provided that style matches the publication.
2. ICAO location identifiers
Four-letter ICAO codes appear in operational, technical and aviation contexts. They should remain unchanged. Do not assume the public three-letter code can replace the ICAO identifier; they serve different systems and audiences.
If the source uses both, preserve both labels and explain their role only when the target reader needs that explanation. Substitution is not translation.
3. Airline designators
Airline codes used in schedules and tickets should be treated as identifiers. Translate the airline’s descriptive or legal name only according to official usage, and keep the designator attached to the right carrier.
This matters in alliance, codeshare and interline contexts where several airline names can appear in one itinerary. A designator moved to the wrong name can change which carrier a passenger believes they booked.
4. Flight numbers
A flight number is not a sentence fragment. Preserve its carrier designator and numeric portion exactly as supplied. If typography inserts a space between designator and digits, do so only according to the source or project convention.
Do not translate digits, localize numerals into another numbering system without explicit system support, or infer that two similar flight numbers are interchangeable.
5. Codeshare flights
A passenger may hold a ticket under one marketing flight number while another airline operates the aircraft. Translate “operated by” with precision and preserve both carrier identities. The relationship is operational, not stylistic.
Where several codeshare numbers are listed, do not delete them merely because they appear repetitive. They may matter to different booking systems and passengers.
6. Airport names with personal names
Airports named after people should normally use their recognized official or conventional target-language form. Do not translate the personal name semantically. A person named in an airport title remains a proper name.
If the target market commonly uses a shortened city-airport form, make sure the full airport identity remains clear where confusion with another airport is possible.
7. Multiple airports serving one city
Large metropolitan areas often have several airports. Do not simplify “Paris Charles de Gaulle” to “Paris Airport” or “Tokyo Haneda” to “Tokyo Airport” if the source is specific. The airport, not merely the city, determines the passenger route.
QA should compare city, airport name and code together. If one of the three points to a different airport, stop and resolve the discrepancy.
8. Terminal numbers
Translate the generic word “Terminal” if local style does so, but protect the terminal identifier. Terminal 1, Terminal A and Terminal International may reflect different local systems. Do not regularize them into one pattern.
A terminal can also change after publication. Translation teams should distinguish source-content updates from linguistic corrections and avoid changing live travel data from memory.
9. Gates and boarding zones
Gate B12 and Boarding Zone 3 are different kinds of identifiers. Keep their labels separate and preserve letters and numbers. Avoid typographic reordering in right-to-left environments without testing the actual display.
Because gate assignments are dynamic, a static translated article should not imply that an example gate is current unless the source explicitly gives current operational information.
10. Departure and arrival
Departure and arrival labels look elementary but are high-risk in tables. A swapped column can reverse the journey while every airport name and time remains individually correct. Translate the headers, then validate one complete row as a relation.
For connection itineraries, repeat the check for each leg. The arrival airport of one leg may be the departure airport of the next, but terminals and dates can differ.
11. Local schedule times
Airline timetables usually show local times. Preserve that convention unless the source states otherwise. Translating a schedule does not automatically mean converting every time into the reader’s time zone.
If target content adds UTC or another converted time for clarity, label both values and verify the date, because a time-zone shift can move an event to the previous or next calendar day.
12. Overnight flights
A flight can depart on one local date and arrive on the next even if the elapsed flight time is shorter than the clock difference suggests. Preserve dates, local times and any “+1 day” notation carefully.
Do not rewrite an apparently strange arrival date simply because the numbers look inconsistent. Time zones and International Date Line effects can produce counterintuitive schedules.
13. Connection and transfer terminology
Connection, transfer, transit and stopover can have different practical and legal meanings. Use the target language’s recognized travel terminology and preserve whether the passenger changes aircraft, leaves the airport or continues on the same flight number.
Where visa or baggage consequences depend on the type of connection, avoid casual synonym replacement.
14. Baggage collection and through-checking
Instructions about collecting or through-checking baggage must remain operationally clear. Translate “collect baggage”, “baggage checked through” and “re-check baggage” as different actions.
A passenger who misunderstands this distinction can miss a connection even though the flight information itself is correct.
15. Flight status labels
Scheduled, boarding, final call, delayed, cancelled, diverted and landed are status terms, not stylistic variants. Use concise target-language forms familiar to travelers and keep them attached to the correct flight.
Do not infer a status from surrounding narrative if the live system has not provided it. Translation should not create operational data.
16. Diversions
A diverted flight has a new landing airport while retaining its flight identity. Translate the diversion message so readers understand the original destination and the actual diverted airport. Do not silently replace the destination in the whole itinerary.
The distinction matters for onward travel, immigration, baggage and compensation.
17. Airport rail and terminal links
Large airports may use branded people movers, shuttle trains or terminal buses. Preserve official service names and translate the descriptive instruction. Do not assume a branded internal transport name is an ordinary train category.
Where the service is free, landside, airside or security-controlled, preserve those conditions because they affect passenger access.
18. Boarding groups and zones
Airlines may use groups, zones, priorities or sequence numbers. Translate the generic category but preserve the assigned value. Group 4 should not become Zone 4 unless the airline itself uses both terms equivalently.
Passengers use these labels to decide when to queue, so terminological consistency across app, boarding pass and airport message is important.
19. Booking references and ticket numbers
Booking references, record locators and ticket numbers are protected identifiers. Translate their labels but preserve the strings character for character. Be cautious with O/0, I/1 and hyphens copied from scans.
Do not expose a private booking reference in examples unless the source already treats it as public or it is fictionalized.
20. Historic flight information
Archives can contain airlines, airport names and codes that have changed. Preserve historical identity rather than updating the text to a modern airline or renamed airport unless a note explicitly explains the later change.
Historical translation should make the past legible, not rewrite it into the present.
Common failure modes
Translating identifiers: Airport codes, flight numbers and booking references should remain protected data. Collapsing airport to city: A city can have several airports; preserve the specific airport. Ignoring codeshares: Marketing and operating carriers can differ. Converting schedule times without instruction: Local time is normally part of the official itinerary. Swapping departure and arrival: Validate whole route relationships, not isolated words. Regularizing terminal labels: Keep the airport’s actual terminal system. Modernizing historical names: Archives need period identity. Trusting OCR: Confusing O with 0 or I with 1 can corrupt flight and booking identifiers.
Worked practice
Practice 1: A codeshare itinerary
The passenger books under one airline’s code, while the aircraft is operated by another. Keep the marketing flight number, translate “operated by”, and preserve the operating airline name. The translation should make both relationships visible rather than selecting whichever airline is more familiar.
Practice 2: A city with three airports
The source names one airport plus its IATA code. Keep the specific airport name and code. Do not shorten to the city name if that would make the itinerary ambiguous.
Practice 3: An overnight arrival
The flight departs late at night and arrives the next local day. Preserve both dates and local times, even if the elapsed duration looks surprising. Verify time zones before assuming an error.
Practice 4: A gate change
The source update changes Gate B12 to C4. Translate the update language, preserve the new identifier and make sure cached or repeated target-language references no longer display B12.
Practice 5: A baggage-transfer notice
The passenger must collect luggage and re-check it. Translate both actions explicitly. A vague “transfer baggage” phrase can hide a required landside procedure.
Practice 6: An airport renaming
A historical document uses the airport’s former official name. Preserve the period name and optionally add the modern name in a note when useful. Do not replace the original silently.
Advanced QA for aviation translation
Use a route matrix for complex itineraries. For every leg, record marketing carrier, operating carrier, flight number, origin airport and code, destination airport and code, departure date/time, arrival date/time, terminal and status. Compare the target against that matrix. This converts a visually dense itinerary into a set of checkable relationships.
In right-to-left languages, test codes, digits, hyphens and arrows in the actual interface. A flight code can display on the wrong side of an airport name even when the underlying characters are stored correctly. Avoid manual reversal; use direction-aware layout and validate the rendered result.
In spreadsheets, store flight numbers and booking references as text. Leading zeros, alphabetic prefixes and long ticket numbers can be damaged by automatic numeric formatting. Protect identifiers before translators or editors begin work.
For live travel products, distinguish linguistic QA from operational freshness. A translator can verify that “Gate” and “Delayed” are correct while the actual gate or status has changed since the source export. Dynamic data should come from the operational system, not be manually translated as static prose.
Accessibility also matters. Screen readers should announce airport names, codes and status labels in an understandable sequence. An icon-only gate, terminal or status indicator needs localized accessible text. A target page is not fully translated if a blind traveler receives a different or incomplete itinerary through assistive technology.
Searchability is another reason to retain identifiers. Travelers often search by flight number, IATA code or airport code rather than translated airport names. Keeping validated codes visible can improve both usability and multilingual discoverability without creating a competing SEO page.
How this fits the wider eduKate translation system
Aviation translation shows why meaning must be preserved across language and data at the same time. The broader framework lives in Master Art of Translation | The Complete System for Moving Meaning Between Languages. Vocabulary depth connects to the Vocabulary Learning Hub, while prepositions, event order, reference and information structure connect to How English Works. Aviation adds one strict requirement: all linguistic choices must still describe the same real journey.
FAQ
Should airport codes be translated?
No. IATA and ICAO codes are identifiers and should remain unchanged.
Can airport names be translated?
Use an official or established target-language name where one exists. Otherwise retain the recognized proper name and preserve the code.
Should flight numbers be localized?
No. Preserve the validated carrier designator and digits.
What does “operated by” mean?
It identifies the carrier physically operating the flight when that may differ from the marketing carrier shown on the ticket.
Should flight times be converted for the reader?
Not automatically. Official schedules generally use local airport time. Add converted times only when the project explicitly calls for them.
How should terminals and gates be handled?
Translate the generic label if appropriate and preserve the exact identifier.
Can I shorten an airport to the city name?
Only when no ambiguity is created. In multi-airport cities, keep the specific airport.
What is the simplest aviation-translation rule?
Protect identifiers, then verify the whole journey relation after translating the language around them.
Final checklist
- Are all IATA and ICAO codes unchanged?
- Are flight numbers and booking identifiers protected?
- Does each airport name match its code?
- Are marketing and operating carriers distinguished?
- Are origin and destination still in the correct direction?
- Are local dates and times attached to the right airports?
- Are terminal and gate identifiers unchanged?
- Are codeshare, baggage and connection instructions preserved?
- Have dynamic status values been kept separate from static translation?
- Can a passenger reconstruct the same trip from the target text?
Airport and flight translation succeeds when every passenger-facing sentence still points to the same aircraft service, airport, time and route. Protect codes and numbers, preserve operating relationships, verify origin and destination, keep local schedule logic intact and test the target as a traveler would use it. A good translation does not merely explain the journey; it keeps the journey from changing.