Common PNR Errors and What They Mean

Every agent runs into PNR errors sooner or later — some are harmless warnings, others mean a booking will fail if not corrected. Here are the most common ones and what to do about each.

Duplicate PNR Warning

Most GDS systems check for duplicate bookings — the same passenger name with similar travel dates already existing in another PNR. This usually appears as a warning rather than a hard block, since duplicates can be triggered by legitimate multi-booking cases too, but it's worth investigating before proceeding, since unresolved duplicates are a common source of double-billing complaints.

Ticketing Time Limit (TTL) Expired

Every PNR carries a ticketing time limit — a deadline by which the ticket must be issued or the airline can automatically cancel the held segments. If this passes without ticketing, the segments typically cancel and need to be resold from scratch. Keeping an eye on TTL fields is one of the most basic but important habits for any agent handling live bookings.

Name Mismatch Errors

Airlines increasingly enforce that the name in the PNR exactly match the passenger's travel document. A mismatch — even a minor one, like a missing middle name matching a passport — can trigger a rejection at check-in even though the PNR itself looked fine. Always verify names against the actual travel document, not just what the client typed in an email.

Invalid Fare Basis / No Fare for Class Booked

This occurs when the booking class sold doesn't have a valid, published fare associated with it for the requested route and dates — often because fare availability changed between the initial search and when the segment was actually sold. Re-pricing or re-shopping the itinerary usually resolves it.

Segment Status UC (Waitlist Closed)

If a waitlisted segment shows UC, the airline has closed that waitlist entirely rather than just declining the request — meaning no further waitlist movement should be expected on that flight. At that point, the realistic options are rebooking on an alternate flight or accepting the itinerary without that segment confirmed.

Codeshare and Operating-Carrier Mismatches

A segment sold under one airline's flight number is often actually flown by a different carrier entirely — a codeshare. American Airlines might sell "AA 6132" on a route it doesn't operate itself, with the actual aircraft, crew, and check-in desk belonging to British Airways. The PNR usually carries an OPERATED BY remark spelling this out, but it's easy to skim past when scanning raw GDS text quickly.

3  AA 6132 H 15JUL 2*LHRJFK HK1 1120A 215P
    OPERATED BY BRITISH AIRWAYS

This isn't a booking error by itself, but missing it causes real problems downstream: the passenger shows up at the American Airlines counter for a flight that's actually departing from a different terminal under British Airways, with a different baggage allowance and check-in cutoff. Always pass the operating carrier along with the marketing flight number when briefing a client on a codeshare segment.

NN Status Left Unconfirmed

NN means the segment was requested but the airline hasn't yet returned a confirmed status — it's neither a hard error nor a guaranteed seat. Left unattended, an NN segment can sit in limbo far longer than it should, and because it doesn't throw the kind of hard error a duplicate or expired TTL does, it's one of the easier things to lose track of in a busy queue.

2  UA 512 Y 18AUG 1*ORDLAX NN1  800A 1015A
// still pending — not the same as HK1 (confirmed)

The fix is diligence: re-queue the PNR periodically until the status flips to HK or a waitlist code, and if it's still showing NN close to the ticketing deadline, follow up directly with the airline rather than assuming it will resolve on its own.

Overnight Segments Mistaken for Scheduling Errors

A flight that departs late in the evening and lands after midnight local time carries a date stamp on the arrival side — something like 1145P 615A/16JUL. Agents new to reading raw PNR text sometimes misread this as a data entry mistake, since the arrival time appears to be earlier than the departure time at first glance.

4  QF 8 H 15JUL 1*LAXSYD HK1 1030P 645A/17JUL

Here the flight departs Los Angeles at 10:30PM on the 15th and arrives Sydney at 6:45AM local time on the 17th — the date suffix on the arrival time is what makes this legitimate rather than an error. Before flagging a segment as broken, always check whether the arrival carries a date rollover before assuming something is wrong.

A Quick Troubleshooting Checklist

1. Check every status code firstConfirm each segment reads HK, KK, TK, or RR — anything else (HL, KL, UN, UC, NN) needs a decision before you move on.
2. Confirm the ticketing deadline is presentNo visible TTL/TAW element means the booking could auto-cancel with no warning.
3. Match names to travel documentsNot just what the client typed in an email or booking form.
4. Look for OPERATED BY remarksA codeshare segment needs the operating carrier communicated, not just the marketing flight number.
5. Re-price before ticketing if anything changedA fare basis that looked fine at search time can go stale by the time you're ready to issue.

Mixed-Cabin Itineraries and Baggage Confusion

Not every multi-segment booking keeps the passenger in the same cabin for the whole trip. A fare rule, an award redemption, or simple seat availability can put a passenger in economy outbound and premium economy or business on the return — and that mismatch is a common source of a very specific kind of "error" that isn't really an error at all: a client assuming their baggage allowance is the same on every leg because it was on the outbound segment.

1  BA 284 Y 15JUL 2*LHRJFK HK1 1120A 215P
2  BA 117 J 22JUL 2*JFKLHR HK1  600P 605A/23JUL

Here the outbound is booked in economy (Y) and the return in business (J) — both legitimate, confirmed segments, but with different baggage allowances, boarding priority, and lounge access attached to each. When converting a PNR like this for a client, it's worth calling out explicitly that the two directions aren't mirror images of each other, rather than letting them assume the whole trip matches whichever segment they remember booking.

Airline-Initiated Schedule Changes

A segment can carry a confirmed HK status and still not reflect the flight the passenger actually thinks they're on. Airlines regularly adjust departure times, swap aircraft, or shift flight numbers months after a booking is made — and rather than changing the confirmed status code, this usually shows up as a separate schedule-change remark elsewhere in the PNR history, easy to miss if you're only reading the segment lines themselves.

This matters most on bookings made far in advance — a ticket issued eight months before departure for a long-haul route has plenty of time to pick up one or more schedule changes before travel. Before finalizing any itinerary for a client, especially one booked well ahead of the trip, it's worth checking the PNR's remarks or history section for schedule-change notices, not just trusting that a confirmed status code means nothing has moved.

Infant and Extra Seat Errors

Bookings involving an infant traveling on an adult's lap carry their own segment-level element, separate from the adult passenger's own segment — and it's easy for this to go missing or fall out of sync when an itinerary is rebooked, changed, or split. If the infant element isn't present on every segment the adult is confirmed on, airlines can refuse boarding for the infant even though the adult's own seat is perfectly confirmed.

The same applies to an extra seat purchased for a passenger's comfort or for oversized equipment — it needs its own confirmed element mirroring the passenger's own segment status, and a mismatch (the passenger shows HK, the extra seat still shows NN or is missing entirely) is one of the easier things to overlook when scanning a PNR quickly, since it doesn't look like a passenger-facing error at first glance. Whenever a booking includes an infant or an extra seat, it's worth explicitly checking that element's status matches the primary passenger's on every single segment, not just the first one.