The boarding-pass barcode standard — IATA BCBP and the format choice
Boarding-pass barcodes follow the IATA (International Air Transport Association) Bar Coded Boarding Pass (BCBP) standard, originally published in 2005 and updated through several revisions. BCBP defines the data encoded into the barcode and the acceptable barcode formats.
The BCBP-supported formats:
PDF417. A stacked linear barcode developed by Symbol Technologies (later Motorola, now Zebra) in 1991. Reads horizontally; supports up to ~2,710 alphanumeric characters. PDF417 was the original BCBP format choice because the linear scanners deployed in airports in the late 1990s and early 2000s read PDF417 reliably. PDF417 remains the dominant format on printed and mobile-PDF boarding passes today.
Aztec. A 2D matrix barcode developed in 1995. Reads omnidirectionally; more compact than PDF417 for equivalent data. Aztec is widely used in European boarding passes (especially Lufthansa, Air France-KLM, British Airways) and in some U.S. airline mobile wallet passes.
QR. Quick Response codes, developed by Denso Wave in 1994. Widely supported by modern smartphone cameras. QR is used in some airline mobile-wallet passes and in newer airport scanner deployments, though it's still less common than PDF417 for boarding passes specifically.
DataMatrix. A 2D matrix barcode standardized in the 1990s. Rarely used for boarding passes but supported by BCBP for compatibility.
The format choice depends on the airline's scanner infrastructure. Older airport infrastructure (especially in U.S. domestic operations) was built around PDF417 scanning; replacing those scanners with modern 2D readers takes years. Newer infrastructure (especially in Asian and European hubs) is more often 2D-capable from the start.
For travelers, the format distinction usually doesn't matter — the scanner at the gate reads whatever format the airline issues. But for technology and industry observers, the slow migration from PDF417 to 2D formats (Aztec, QR) is one of the longer-running infrastructure modernizations in aviation.
What the barcode encodes — passenger, PNR, and security flags
The boarding-pass barcode encodes a structured set of data fields specified by IATA BCBP. The data includes:
| Field | Example | Purpose |
|---|---|---|
| Passenger name | SMITH/JOHN MR | Identifies the ticketed passenger |
| PNR (Passenger Name Record) | ABC123 | Links to the airline reservation system |
| Origin airport (IATA) | JFK | Departure airport code |
| Destination airport (IATA) | LHR | Arrival airport code |
| Airline (IATA) | AA | Operating airline code |
| Flight number | 0100 | Specific flight |
| Date of flight | 243 | Day-of-year format (Julian) |
| Compartment code | F | Cabin class (F=First, J=Business, Y=Economy) |
| Seat number | 12A | Assigned seat |
| Sequence number | 0042 | Check-in sequence number |
| Passenger status | 1 | Security or boarding status flags |
Tips
- **The PNR is the most sensitive field** — it links to the airline's full reservation including contact info, payment method, and trip history. Photo-shared boarding passes can be exploited via the PNR.
- **Security flags** include PreCheck (TSA-approved expedited screening), CLEAR, and SSR (Special Service Request) codes. These are read by airport scanners to route the traveler appropriately.
- **The barcode includes a checksum** for error detection — scanners verify data integrity before accepting the boarding pass.
- **International flights add fields** including travel document type (passport vs. visa), nationality, and onward-travel verification flags.
- **Status codes route the traveler** to the appropriate boarding zone, lounge access, or special-handling lane.
- **The boarding pass barcode is NOT encrypted** — anyone with a barcode reader can decode the contents.
- **Security depends on the airline and TSA databases**, not on the barcode being secret. The scanner verifies the barcode contents against the live manifest.
The airport scan workflow — six to twelve scans per trip
A typical international itinerary requires the boarding-pass barcode to be scanned multiple times across the airport journey. Each scan serves a different operational purpose:
Check-in scan. At the check-in counter or kiosk, the agent scans the barcode (or it's generated digitally) to confirm the reservation, assign or confirm seat, and produce the boarding pass.
Bag drop scan. At checked-bag drop, the agent scans the boarding pass to associate the checked bag's tag with the passenger's reservation. The bag tag itself has a separate barcode that tracks it through the baggage handling system.
Lounge access scan. Premium-cabin and elite-status travelers entering airline lounges scan their boarding pass at the lounge entrance. The lounge attendant verifies eligibility and may add additional services (food orders, shower bookings) to the passenger's record.
Security checkpoint scan (1st). Most U.S. airports scan the boarding pass at the TSA podium before queue entry. The scan verifies the document is valid for the day, matches a real reservation, and surfaces any security flags or routing.
Security checkpoint scan (2nd). Some airports (especially international and Asian hubs) scan a second time at the bag screening conveyor — verifying the passenger and their bags are routed together.
Customs/immigration scan (international). At outbound customs (in some countries) and inbound immigration, the boarding pass is scanned alongside the passport to verify the traveler is on the manifest.
Gate boarding scan. At the gate, the boarding pass is the primary verification — the scan reads the barcode, confirms the manifest, and prints a boarding stub. Errors at this stage (wrong gate, wrong flight, ineligible boarding) are surfaced immediately.
Premium-cabin meal scan. Some airlines scan the boarding pass at premium-cabin meal service to confirm dietary preferences and special meal orders.
Lounge re-entry scan. Long layovers often involve multiple lounge entries; each entry is a fresh scan.
For international itineraries with transit stops, the cycle repeats — multiple lounges, multiple security checkpoints, multiple gate scans. Twelve scans per traveler per international itinerary is common.
The scan volume highlights why barcode reliability matters. A boarding pass that fails to scan creates friction at every checkpoint. Mobile wallet passes are particularly reliable because the screen brightness is consistent and the barcode is sharp; printed passes can crinkle and degrade through the journey.
Mobile wallet passes — Apple Wallet, Google Wallet, and the always-fresh ticket
Mobile wallet passes have become dominant in modern aviation. Apple Wallet (iOS), Google Wallet (Android), and airline-specific apps store the boarding pass as a digital ticket that updates automatically.
The wallet pass advantages over PDF or screenshot:
Automatic gate updates. When the gate changes (which happens on a meaningful fraction of flights), the wallet pass updates automatically. Screenshots become stale; wallet passes stay current.
Delay notifications. Wallet passes push delay notifications to the traveler's lock screen. The traveler doesn't need to check the airline app or airport boards manually.
Geo-fenced display. Apple Wallet displays the boarding pass automatically when the traveler arrives at the airport. The pass appears on the lock screen without requiring the traveler to dig through their apps.
Brightness optimization. When the wallet pass is displayed, the phone screen brightness automatically maximizes to ensure barcode scan reliability.
Multiple-trip support. A traveler with multiple itineraries (connecting flights, multi-airline journeys) stores all the boarding passes in the wallet simultaneously, organized by departure time.
Family-sharing. Apple Wallet supports sharing boarding passes across family member iPhones. The parent's wallet has passes for the whole family, with each pass shareable to the family member's device.
The wallet pass mechanism uses standard barcode formats (PDF417 most commonly, Aztec and QR in some cases). The format is determined by the airline's pass template; the wallet displays whatever format the airline issued.
For travelers, the workflow is straightforward: at booking or check-in, the airline app or email confirmation offers an 'Add to Apple Wallet' or 'Add to Google Wallet' button. Tapping the button installs the pass. The pass auto-updates from there through the trip.
For airlines, the wallet pass workflow is operationally meaningful because it reduces gate-agent intervention. Travelers with current wallet passes board faster than travelers with stale screenshots. The major U.S. and international airlines have invested heavily in wallet-pass quality because the throughput improvement is significant at scale.
TSA, security verification, and the database-driven model
TSA (and equivalent international security authorities) use the boarding-pass barcode as one element of a layered security workflow. The barcode is not the security primitive — the database lookup is. The barcode is the index key that retrieves the relevant security data.
The TSA workflow:
At the TSA podium, the agent scans the boarding-pass barcode. The scanner reads the encoded fields (passenger name, flight, PNR, security flags) and queries the Secure Flight database. The database returns the traveler's risk assessment, PreCheck eligibility, no-fly-list status, and special handling requirements.
If the lookup is clean, the agent waves the traveler to the standard or PreCheck lane. If the lookup flags a concern (selectee status, document mismatch, manifest discrepancy), the traveler is routed to enhanced screening.
The barcode itself isn't secret. The security is in the live database lookup. This is why airlines and TSA explicitly warn travelers not to share boarding-pass photos on social media — the PNR encoded in the barcode allows anyone with access to the airline's PNR lookup tools (relatively easy to obtain via website forms with passenger name and PNR) to view trip details, contact information, and sometimes payment information.
For PreCheck-eligible travelers, the security flag is encoded in the barcode and the scanner reads it directly. The PreCheck enrollment process (separate from the boarding pass) creates the eligibility record; the boarding-pass barcode carries the flag indicating the traveler is enrolled.
For international travel, the boarding-pass scan integrates with passport verification at customs. The combined scan confirms the passenger is on the manifest, the passport is valid for the destination country, and any required visas are properly recorded.
For travelers concerned about privacy, the only durable mitigation is to avoid sharing boarding-pass photos. Once shared, the PNR is exposed; an attacker can use the PNR with the airline's website to view and sometimes modify the trip. Real cases of attackers canceling other people's flights have been documented.
Beyond the barcode — QRs in the broader boarding-pass ecosystem
While the boarding-pass barcode itself is typically PDF417, QR codes appear throughout the broader boarding-pass ecosystem.
Tips
- **Lounge entry QRs** — premium lounges sometimes use QR codes for entry rather than reading the boarding-pass PDF417. Faster scanners; cleaner workflow for one-time-entry verification.
- **Boarding-pass companion QRs** — some airlines print a separate QR on the boarding pass routing to in-flight entertainment login, post-flight survey, or status-tracking app downloads.
- **Baggage tracking QRs** — some airlines have moved from barcode-only to QR-coded baggage tags allowing travelers to scan their own bags for tracking.
- **TSA PreCheck enrollment QRs** — airport signage with QRs routing to TSA PreCheck enrollment workflows. Captures travelers in the moment of frustration with standard-lane queues.
- **Airline app download QRs** — airport gate signage with QRs routing to the airline app for travelers who haven't installed it.
- **Loyalty program QRs** — boarding-pass post-trip emails with QRs routing to mileage credit or status review pages.
- **Travel-document verification QRs** — international travel often involves QR-routed verification of vaccination records, COVID test results, or visa documents.
Common mistakes that disrupt the boarding-pass workflow
Ten failure patterns we see repeatedly in boarding-pass workflows:
1. Relying on screenshots instead of wallet passes. Screenshots become stale when gates change. Always download the wallet pass.
2. Sharing boarding-pass photos on social media. The PNR encoded in the barcode exposes the booking. Multiple attacker scenarios are well-documented.
3. Printing low-contrast boarding passes. Cheap printer ink and paper can produce barcodes that fail to scan. If printing, verify the contrast and barcode quality.
4. Forgetting to charge the phone. A dead phone at the gate means no wallet pass. Carry a backup PDF or printed copy for international trips with long layovers.
5. Screen brightness too low. Some phones with auto-brightness in low-light conditions produce dim wallet passes that scanners struggle to read. Manually maximize brightness when scanning.
6. Phone case interfering with the screen. Heavy cases or screen protectors with glare can interfere with scanner reading. Test the wallet pass with the actual case before relying on it.
7. Multiple wallet passes from canceled itineraries. Old wallet passes from prior trips or canceled bookings can confuse the boarding-pass workflow. Delete obsolete passes.
8. Forgetting to update the airline app. Some wallet-pass features depend on the latest airline app version. Update the app before traveling.
9. Manual PDF vs. wallet — choosing PDF. PDFs don't auto-update; wallet passes do. Always prefer wallet passes when offered.
10. International trips without printed backup. Some international airports have less reliable cellular and WiFi. A printed backup pass at the start of the trip prevents recovery friction at remote international airports.
