TCP

TCP stands for "to complete party" and appears in airline reservation systems as a modifier code that signals the presence of additional passengers traveling together as a unit but booked under separate reservations. When an agent enters TCP followed by a number, such as TCP/4, it tells the system that this booking is part of a group of four people who are flying together despite having four individual PNRs (passenger name records). This is critical information for crew scheduling, gate assignments, and passenger communication because the airline must treat them as a coordinated unit rather than as four independent travelers.

The notation TCP/n (where n is the total party size) appears in the OSI field of the PNR, typically visible only to airline staff and GDS operators. Unlike group bookings or corporate arrangements with a single contract, TCP bookings arise when families, small teams, or tour groups each have their own ticket number but need to be seated together or handled as one entity for operational purposes. The code ensures that when one passenger changes a flight or makes a special request, the system flags that three other people are involved in the same travel event.

Ground handlers and flight crew use TCP information to coordinate boarding, seat blocking, and special handling. If passenger TCP/3 books a wheelchair, the airline knows two other passengers in that TCP group may need assistance locating the passenger or boarding gate. Similarly, when overbooking forces a voluntary denied boarding, airlines will not separate TCP parties, treating them as a single unit for compensation and rebooking purposes. This prevents the operationally dangerous and customer relations nightmare of separating a parent from children or breaking up a work crew.

TCP differs from both group bookings (which consolidate multiple passengers under one PNR and one contract) and from casual coppa ssengers. It is strictly a notation flag rather than a structural change to how the bookings themselves are made. A travel agent might manually input TCP during reservation; some systems auto-detect it when passengers with the same contact information book multiple separate fares on the same flight, but this is not universal.

The term reflects older airline reservation terminology and remains embedded in IATA messaging standards and most major GDS platforms (Amadeus, Sabre, Galileo). It is less commonly discussed in modern consumer-facing travel than in back-office crew planning, gate management, and customer service protocols. Misuse or omission of TCP can lead to miscommunication about group intent, particularly in European and international markets where tour groups and family travel are common and booking rules differ from domestic North American patterns.