The Complete Guide to PNR Conversion: Decoding Airline Booking Data Like a Pro
A Passenger Name Record is the backbone of every airline ticket and travel booking — a dense, coded snapshot of an entire journey. This guide explains what PNRs are, how GDS formats work, and why converting them to structured data is essential for the modern travel industry.
What Is a PNR — and Why Is It So Hard to Read?
A Passenger Name Record (PNR) is a standardized data record created in a Global Distribution System (GDS) whenever a travel booking is made. It serves as the master file for an entire trip — containing passenger identities, flight segments, fare codes, seat assignments, special service requests, ticketing deadlines, contact information, and operational remarks, all crammed into a compact, cryptic text format originally designed for speed over readability.
The PNR format traces its origins to the 1960s, when airline reservation systems were first computerized. Systems like SABRE (Semi-Automatic Business Research Environment) — developed by IBM and American Airlines in 1960 — needed a highly efficient encoding scheme to store booking data on the limited hardware of the era. That efficiency came at a cost: the resulting format is deeply opaque to anyone not trained as a travel agent or GDS operator. Line identifiers, airline codes, fare basis codes, seat designators, and operational SSR elements are all compressed into terse, capital-letter strings that look like noise to the untrained eye.
Our PNR Converter bridges this readability gap — taking raw GDS-format PNR text and transforming it into clean, structured data that developers, analysts, and travel professionals can actually use without a GDS terminal or specialist training.
How the PNR Converter Works — Step by Step
Our tool uses a multi-stage parsing pipeline to interpret raw PNR text, classify each line by segment type, extract structured fields, and render the data in your chosen output format. Here's what happens when you paste a PNR and click Convert:
Step 1: GDS Format Detection
The parser analyzes the first few lines of the input to identify the originating GDS system — Amadeus, Sabre, Galileo/Travelport, or Worldspan — based on characteristic line prefixes, date formats, and field separators. You can also manually select your GDS in the settings for maximum accuracy.
Step 2: Segment Classification
Each line of the PNR is classified into one of the standard segment types: Name (NE), Air Segment (SI), Phone (AP), Ticketing (TK), Special Service Request (SSR), OSI Remarks, Free-form Remarks (RM), or General Facts (GF). This classification drives how each line is subsequently parsed.
Step 3: Field Extraction
Within each classified segment, individual fields are extracted using pattern-matching rules tailored to the detected GDS format. Passenger names are split into surname and given name. Flight segments yield airline code, flight number, booking class, dates, routes, status codes, and times. SSR elements reveal document numbers, nationalities, and dietary preferences.
Step 4: Structured Output
The extracted, structured data object is serialized into your chosen format — a nested JSON document with arrays for each segment type, a flat CSV with one row per segment, or a readable plain-text itinerary. The table view renders all segments in a scannable, color-coded grid. All output is instantly copyable and downloadable.
The Four Major GDS Formats: Similarities and Differences
The global travel industry operates through four dominant GDS platforms, each with its own PNR syntax, line formatting conventions, and field delimiter schemes. Understanding these differences is critical for accurate parsing.
Amadeus
The European market leader, Amadeus uses a consistent line-number prefix with a distinct name format (SURNAME/GIVENNAME TITLE) and a slash-delimited SSR structure. Amadeus PNRs frequently include IATA office ID suffixes and use specific codes like HK (holding confirmed), HL (waitlisted), and TK (ticketing time limit) in standardized positions.
Sabre
Sabre, dominant in North America, has a more verbose structure with explicit field tags and a different name element format. Sabre PNRs use a hyphen-based name separator, distinct phonetic coding for names, and a different address-element format. Sabre's CRS date format also differs from Amadeus, using 01JAN style versus Amadeus's 01JAN25 with two-digit year.
Galileo / Travelport
Galileo (now part of Travelport) uses a name format more similar to Amadeus but has its own numbering scheme for itinerary elements and a distinct passive segment syntax. Galileo PNRs are common in the UK, Europe, and Asia-Pacific markets and frequently include hotel and car rental segments alongside air segments.
Worldspan
Worldspan (also Travelport) is the oldest of the four systems and has the most archaic syntax. Its PNRs use a different line element numbering convention, a unique status code scheme, and a compressed date format. Despite its age, Worldspan remains in active use in many US and Latin American markets and is still frequently encountered in legacy data conversion projects.
Understanding PNR Segment Types: The Building Blocks
Every PNR is composed of a set of standardized segment types, each identified by a two or three-letter prefix. Knowing what each segment type contains is essential for extracting meaning from raw PNR data.
Passenger name elements — surname, given name, title, and infant/child associations. The first segment of every PNR.
Flight segments — airline, flight number, booking class, date, route, status, departure/arrival times, and number of passengers.
Contact phone numbers — city of origin and phone number for the booking party. Essential for operational contact.
Ticketing time limits and ticket number references. Indicates the deadline by which the booking must be ticketed or it will auto-cancel.
Special Service Requests — DOCS (travel document info), MEAL (meal preference), WCHR (wheelchair), CHLD (child age), and dozens more IATA-coded requests.
Other Service Information and free-form remarks — contains email addresses, frequent flyer numbers, agency notes, and operational comments.
Who Benefits from a PNR Converter?
Whether you are migrating legacy booking data, building a travel API, auditing reservations for compliance, or simply trying to read an incomprehensible itinerary printout, structured PNR data is dramatically more useful than raw GDS text. This tool serves a wide spectrum of professional users.
✔ Travel Technology Developers
Building or maintaining travel booking engines, APIs, or data pipelines? Converting PNRs to JSON gives you clean, structured objects that slot directly into your application logic without wrestling with GDS terminal syntax. Parse once, consume everywhere — your REST API, mobile app, and database all speak JSON.
✔ Travel Agents & TMCs
Travel Management Companies handling high volumes of corporate bookings need to regularly audit, report on, and reconcile PNR data. Converting raw GDS PNRs to CSV enables bulk analysis in Excel or Google Sheets, simplifying expense reporting, compliance audits, and traveler profiling without specialized GDS training.
✔ Data Analysts & BI Teams
Airline revenue management analysts, route performance teams, and BI developers working with booking data need structured fields to build dashboards, run queries, and generate reports. Structured PNR data eliminates the regex-heavy pre-processing step that typically consumes hours of analyst time before the actual analysis can even begin.
✔ Airlines & Airport Operations
Ground handlers, check-in staff, and airport IT teams frequently need to quickly parse PNR data to extract passenger counts, special service requirements, and travel document information. A fast, browser-based converter provides instant access to structured data without requiring GDS terminal access or specialist operator skills.
JSON vs CSV vs Plain Text: Choosing Your Output Format
The right output format depends entirely on what you need to do with the data next. Our converter supports all three common formats, and understanding their respective strengths will help you choose correctly.
JSON — Best for Developers
JSON is the ideal format when the structured PNR data needs to be consumed by an application, API, or database. The nested object structure preserves the natural hierarchy of PNR data — a booking object containing arrays of passenger names, flight segments, and service requests. Configurable indentation supports both human-readable (2 or 4 spaces) and minified (0 spaces) output for production use.
CSV — Best for Analysis
CSV is the go-to format when the data needs to be analyzed in spreadsheet software (Excel, Google Sheets, LibreOffice Calc), imported into a SQL database, or processed by a data pipeline. Our CSV output flattens the PNR hierarchy into one row per segment with configurable column headers and delimiter characters, maximizing compatibility with analysis tools.
Plain Text — Best for Readability
Plain text output reformats the cryptic PNR into a clean, human-readable itinerary — similar to what passengers see on their booking confirmation emails. This format is ideal for quickly communicating itinerary details to non-technical staff, printing for file retention, or including in email confirmations without any post-processing.
Table Preview — Best for Quick Review
The table view renders all PNR segments as an interactive, color-coded HTML table — perfect for quickly reviewing a booking's completeness, spotting missing elements (like a missing AP or TK segment), or presenting PNR data in a clean format during client calls or screen-sharing sessions without exposing raw GDS syntax.
Why Converting PNR Data Is Critical for the Modern Travel Industry
The travel technology landscape has changed dramatically since PNR formats were designed. ✈️ Modern travel platforms operate through REST APIs, microservices, cloud databases, and real-time data streams — none of which speak raw GDS syntax natively. The gap between legacy PNR formats and modern data infrastructure creates real costs.
Who Needs This Tool?
- ➤ OTAs (Online Travel Agencies): Systems that aggregate bookings from multiple GDS sources need to normalize PNR data into a single internal format. A conversion layer that handles all four major GDS formats is foundational to any OTA's data architecture.
- ➤ Corporate Travel Managers: CTMs auditing travel policy compliance need to query booking data across hundreds or thousands of PNRs simultaneously. Structured data enables queries like "show all bookings where cabin class is Business and fare class is not the lowest available" — impossible with raw PNR text.
- ➤ Travel Software Vendors: ISVs building check-in apps, duty-of-care platforms, expense management systems, or itinerary management apps all need clean, structured booking data. PNR conversion is the unglamorous but essential first step in any travel data pipeline.
- ➤ Airport & Ground Handling IT Teams: Passenger manifest generation, APIS (Advance Passenger Information System) submission, and DCS (Departure Control System) integration all require structured passenger and flight data extracted from PNRs in real time.
The Data Efficiency Advantage
Converting a 30-line raw PNR to structured JSON reduces parsing time at the application layer from potentially hundreds of milliseconds (with complex regex chains) to zero — the structure is already there. For high-volume booking platforms processing thousands of PNRs per minute, this efficiency compounds rapidly.
This is why airline PSS (Passenger Service Systems) providers increasingly use structured internal data formats rather than raw GDS strings — and why conversion tooling is a permanent fixture in any travel technology stack.
Key Features of Our Advanced PNR Converter
Professional-grade PNR parsing across all four major GDS formats, with four output modes, batch file support, instant download, and complete in-browser privacy.
4-Format GDS Support
Auto-detects and correctly parses PNRs from all four major Global Distribution Systems — Amadeus, Sabre, Galileo/Travelport, and Worldspan — handling their individual syntax variations, name formats, date conventions, and field delimiters without any manual configuration required.
4 Output Formats
Convert any PNR to nested JSON (configurable indentation), flat CSV (configurable delimiter and headers), human-readable plain text itinerary, or an interactive HTML table preview — switching between formats with a single click without re-running the conversion. Download all formats simultaneously as a ZIP archive.
100% Private & Secure
PNR data contains sensitive passenger information — names, passport numbers, contact details, and travel documents. Our converter processes all data exclusively within your browser using JavaScript. Nothing is ever transmitted to any server, stored in any database, or logged in any way. Optional PNR locator masking adds an additional layer of protection.
Batch File Processing
Upload multiple PNR files simultaneously via the file upload mode — supporting .TXT, .PNR, .CSV, .LOG, .DAT, and .APO formats. Each file is parsed independently, with results concatenated into a single output or packaged into a ZIP archive for bulk download. Ideal for migration projects and batch data processing pipelines.
Pro Tips for Using the PNR Converter Effectively
While the auto-detect engine handles the vast majority of real-world PNRs correctly, ambiguous or truncated PNRs can occasionally be misclassified. If your output looks incorrect — misaligned fields, missing segments, or garbled dates — switch to manual GDS selection in the settings panel and re-run the conversion.
Before downloading a converted PNR for use in a production system, switch to the Table Preview tab for a quick visual scan. Missing required elements — a phone element (AP), ticketing deadline (TK), or passenger name — are immediately obvious in tabular view. This 10-second check can prevent downstream system errors caused by incomplete booking data.
The 6-character PNR locator (booking reference) is a sensitive identifier — anyone with this code can access and potentially modify a booking through most airline direct channels. Enable the "Mask PNR Locator" option in settings before capturing screenshots, sharing output with external parties, or using converted data in documentation or training materials.
If a PNR needs to be delivered to multiple stakeholders — a JSON feed for developers, a CSV for the finance team, and a plain text version for the traveler — convert once and download the ZIP archive containing all three formats simultaneously. This single-action workflow eliminates the need to run three separate conversions and ensures all formats are synchronized from the same source parse.
Frequently Asked Questions
Conclusion
Raw PNR data is the lifeblood of the global travel industry — but its cryptic, GDS-specific format has historically been a significant barrier to developers, analysts, and non-specialist professionals who need to work with booking data. Our free PNR Converter eliminates that barrier, providing instant, accurate conversion from any of the four major GDS formats to clean, structured JSON, CSV, plain text, or interactive table output — all within the privacy of your own browser. Whether you're building a travel API, auditing bookings, migrating legacy data, or simply trying to understand a complex itinerary, structured PNR data is where your work starts.
Ready to Convert Your PNR Data?
Use our advanced PNR Converter now — paste your GDS data and get clean, structured JSON, CSV, or readable text in seconds!