What is ADT in Airline Ticket Code Reference Guide

ADT in airline ticket represents the IATA passenger type code for adult passenger. ADT (Adult) typically applies to passengers 12 years and older for international flights, though some carriers use 16 or 18 as adult threshold for specific scenarios. Adult fares form the standard fare basis in airline ticketing without age-based fare reduction. ADT passenger type code appears in passenger name records (PNRs), e-tickets, GDS responses, travel agency booking systems, NDC integration responses. Understanding ADT alongside other passenger type codes (CHD for child, INF for infant, CNN for child variant, YTH for youth, STU for student, SEA for senior, MIL for military, GOV for government, VFR for visiting friends and relatives, CRP for corporate, GRP for group) supports accurate flight booking and operational handling. Match passenger type code understanding to specific operational scenarios. The IATA passenger type code framework provides standardized passenger classification across airlines and distribution systems. Standardization enables consistent booking system handling across diverse airline scenarios. ADT as adult passenger type forms baseline; other passenger types receive specific fare rules typically defined as percentage discount off adult fare. Age thresholds and discount percentages vary by carrier; consistent IATA code framework enables booking systems to handle diverse carrier policies through code-based logic rather than per-airline implementation. Match passenger type code framework understanding to booking system implementation. ADT applicability spans diverse scenarios. International flights typically apply 12+ years for ADT. Some domestic flights apply different age thresholds. Age determination typically based on travel date age rather than booking date age, requiring booking systems to calculate age at travel time. Single-passenger scenarios apply ADT regardless of accompanying passenger requirements. Group bookings combine multiple ADT passengers with potential CHD/INF passengers. Match ADT applicability assessment to specific carrier rules and scenario patterns. ADT fare structure forms baseline for fare calculations. Adult fares represent the standard fare basis without age-based reduction. Other passenger types typically receive percentage-based discount off adult fare. CHD typically 75 percent of adult fare. INF typically 10 percent of adult fare or fixed nominal fee. YTH varies. STU varies. Senior fares vary. Each passenger type fare structure defined per airline and per fare class. Understanding ADT base fare alongside other passenger type discount structures supports accurate fare calculation in booking systems. Match passenger type fare structure understanding to specific operational scenarios. ADT handling differs from other passenger types across operational dimensions. ADT receives own seat with full seat assignment options. ADT receives full baggage allowance per fare class rules. ADT requires standard passenger documentation. ADT fare calculation applies full adult fare. CHD shares some operational handling with ADT but with discount fare and potentially additional documentation. INF typically lap-held without own seat, receives minimal baggage, requires accompanying ADT. Match passenger type operational handling to specific operational scenarios. This guide covers ADT passenger type code, passenger type framework, fare structure implications, GDS integration, NDC integration, and booking system handling. Use this article alongside our broader pieces on Best Flight Booking APIs for flight API context, Flight Booking System for flight system context, and Global Distribution System for GDS context.

IATA Passenger Type Codes

IATA passenger type codes provide standardized passenger classification framework. ADT (Adult). Adult passenger type, typically 12+ years for international flights. Standard fare basis without age-based reduction. Most common passenger type. Strong baseline for fare calculations. CHD (Child). Child passenger type, typically 2-11 years. Discount fare typically 75 percent of adult fare. Requires accompanying adult typically. Match CHD code to child passenger scenarios. INF (Infant). Infant passenger type, typically under 2 years without seat. Discount fare typically 10 percent of adult fare or fixed nominal fee. Lap-held by accompanying adult. Requires accompanying adult (1:1 ratio typically). Match INF code to infant passenger scenarios. CNN (Child variant). Alternative child passenger code in some scenarios. Match CNN code to specific carrier requirements. YTH (Youth). Youth passenger type. Age threshold varies by carrier (typically 12-25 years). Match YTH code to youth-specific fare scenarios. STU (Student). Student passenger type. Requires student documentation. Match STU code to student-specific fare scenarios. SEA (Senior). Senior passenger type. Age threshold varies by carrier (typically 60+ or 65+). Match SEA code to senior-specific fare scenarios. MIL (Military). Military passenger type. Requires military documentation. Match MIL code to military-specific fare scenarios. GOV (Government). Government passenger type. Requires government documentation. Match GOV code to government-specific fare scenarios. VFR (Visiting Friends and Relatives). VFR passenger type for specific scenarios. Match VFR code to VFR-specific fare scenarios where applicable. CRP (Corporate). Corporate passenger type. Triggers corporate negotiated rates. Match CRP code to corporate scenarios with corporate fare agreements. GRP (Group). Group passenger type. Triggers group fare rules. Match GRP code to group booking scenarios. SC (Sea/Sailor). Sailor/sea passenger type. Match SC code to specific maritime scenarios. UNN (Unaccompanied Minor). Unaccompanied minor scenarios. Requires special handling. Match UNN code to unaccompanied minor scenarios. LAB (Labor). Labor passenger type for specific scenarios. RM (Religious Minister). Religious minister passenger type. VFR variants. Various VFR-related codes per carrier requirements. Custom passenger types. Some carriers define custom passenger types beyond IATA standard. Match custom passenger type handling to specific carrier requirements. Code variations across GDS. Different GDS may use slightly different syntax but IATA codes apply consistently. Match code variations to specific GDS implementation. Passenger type combinations. Single booking may include multiple passenger types (multiple ADT with CHD and INF). Booking systems handle combinations through passenger type selection. Match combination handling to operational scenarios. Age threshold variations. Adult age threshold varies by carrier (12, 16, 18). Child age threshold varies by carrier. Senior age threshold varies. Match age threshold understanding to specific carrier rules. Discount percentage variations. CHD discount varies (typically 75 percent but can vary). INF discount varies (typically 10 percent or fixed fee). Match discount percentage understanding to specific carrier rules. Documentation requirements. Different passenger types require different documentation. CHD may require parental consent for unaccompanied scenarios. STU requires student ID. MIL requires military ID. Match documentation requirements to specific passenger type handling. Booking system implementation. Booking systems handle passenger types through dropdown selection or per-passenger type counters. Strong booking system implementation supports diverse passenger combinations. The IATA passenger type code framework provides comprehensive coverage of passenger classification scenarios. Match passenger type code usage to specific operational scenarios.

To help Google and AI tools place this page correctly, here are the most relevant guides for ADT and passenger type code reference.

ADT in Booking Systems

ADT handling in booking systems requires comprehensive integration patterns. Passenger type selection. Booking flow includes passenger type selection (typically default ADT). Per-passenger type counter allowing 1+ ADT, 0+ CHD, 0+ INF combinations. Strong passenger type selection supports diverse passenger combinations. ADT-specific fare calculation. ADT fare calculation applies full adult fare. Fare class application. Tax calculation. Fee calculation. Strong ADT fare calculation supports accurate pricing display. Age verification. Age verification at booking time using travel date age calculation. ADT applicability verification. Match age verification to specific carrier rules. Passenger information collection. ADT passenger information collection (full passenger details including name, date of birth, document information). Strong passenger information collection supports operational booking. Document verification. ADT typically requires standard passenger documentation. Document verification at check-in. Match document verification to operational compliance. Seat assignment. ADT receives own seat with seat assignment options. Strong seat assignment supports user experience. Baggage allowance. ADT receives full baggage allowance per fare class rules. Match baggage allowance to fare class rules. Special service requests. ADT-specific special service request handling (meal preferences, mobility assistance, etc.). Match special service request handling to operational service requirements. Booking confirmation. Per-passenger booking confirmation including ADT passenger details. Match booking confirmation to communication strategy. E-ticket generation. E-ticket per ADT passenger with passenger details. Strong e-ticket generation supports operational ticketing. PNR creation. PNR creation including ADT passenger data. ADT passenger count tracking. Strong PNR creation supports GDS operational requirements. Multi-passenger booking. Multi-passenger booking supporting multiple ADT and other passenger types. Combined fare calculation. Match multi-passenger booking to family and group scenarios. Group booking handling. Group booking with multiple ADT passengers. Group fare application where applicable. Match group booking handling to group operational requirements. Corporate booking handling. Corporate booking with ADT passengers. Corporate negotiated fare application. Match corporate booking handling to corporate scenarios. B2B agent booking. B2B agent booking with multiple ADT passengers. Agent booking workflows. Match B2B agent booking to agent operational scenarios. B2C consumer booking. B2C consumer booking with ADT passengers. Consumer booking workflows. Match B2C consumer booking to consumer operational scenarios. Mobile booking handling. Mobile-optimized passenger type selection. Mobile-friendly passenger information collection. Strong mobile booking handling captures mobile traffic. Multi-language passenger type display. Translated passenger type labels. Translated age threshold information. Match multi-language to international scenarios. Multi-currency fare display. ADT fare display in customer preferred currency. Currency conversion. Match multi-currency to international scenarios. Reporting on ADT bookings. Per-passenger-type booking reports. ADT-specific revenue reports. Match reporting to operational analytical requirements. Cancellation handling. Per-passenger cancellation handling. ADT-specific refund calculation per fare rules. Match cancellation handling to specific cancellation policy. Modification handling. Per-passenger modification handling. ADT-specific modification fee calculation. Match modification handling to specific modification policy. Schedule change handling. Per-passenger schedule change notification. ADT-specific rebooking offers. Match schedule change handling to operational requirements. BSP integration for IATA agencies. BSP records include ADT passenger counts and fare information. BSP reconciliation. Match BSP integration to IATA agency requirements. The ADT booking system handling compounds significantly over operations. Strong ADT handling produces foundation for sustained flight booking operations.

ADT in GDS and NDC

ADT handling in GDS and NDC integrations requires comprehensive integration patterns. Amadeus GDS ADT handling. Amadeus GDS responses include ADT passenger type indicators. Amadeus booking commands specify ADT passenger count. Amadeus PNR data includes per-passenger ADT type indicator. Match Amadeus ADT handling to Amadeus integration scenarios. Sabre GDS ADT handling. Sabre GDS responses include ADT passenger type indicators. Sabre booking commands specify ADT passenger count. Match Sabre ADT handling to Sabre integration scenarios. Travelport GDS ADT handling. Travelport Universal API responses include ADT passenger type indicators. Travelport booking specifies ADT passenger count. Match Travelport ADT handling to Travelport integration scenarios. Modern aggregator ADT handling. Duffel, Kiwi.com responses include ADT passenger type indicators in modern API patterns. Match modern aggregator ADT handling to modern API integration scenarios. NDC ADT handling. NDC schema includes passenger type field accepting ADT. NDC implementation respects ADT-specific fare rules. NDC booking creation specifies ADT passenger count. Match NDC ADT handling to NDC integration scenarios. Cross-GDS ADT consistency. ADT code applies consistently across major GDS enabling cross-GDS operational consistency. Different GDS use slightly different command syntax but ADT code applies consistently. Match cross-GDS ADT consistency to multi-GDS integration scenarios. Fare quote with ADT. GDS fare quote responses include ADT passenger type and fare. Per-passenger fare components. Total fare calculation. Match fare quote handling to operational fare presentation. Booking creation with ADT. GDS booking creation specifies ADT passenger count and per-passenger details. Booking confirmation includes ADT passenger data. Match booking creation handling to operational booking workflows. Ticketing with ADT. GDS ticketing creates e-ticket per ADT passenger. ADT-specific ticketing data. Match ticketing handling to operational ticketing requirements. PNR retrieval with ADT. PNR retrieval responses include ADT passenger data. Per-passenger details accessible. Match PNR retrieval handling to operational PNR access scenarios. BSP records with ADT. BSP settlement records include ADT passenger counts and fare information for IATA agencies. BSP reconciliation against booking records. Match BSP records handling to BSP reconciliation operational requirements. Fare rules with ADT. ADT-specific fare rules through GDS responses. Cancellation rules. Modification rules. Match fare rules handling to operational fare rule application. Tax handling with ADT. Per-ADT tax calculation. Tax rules vary by jurisdiction. Match tax handling to specific tax requirements. Fee handling with ADT. Per-ADT fee calculation (carrier fees, payment fees, service fees). Match fee handling to operational fee structure. Mileage accrual with ADT. Frequent flyer mileage accrual per ADT passenger. Loyalty program integration. Match mileage accrual to loyalty operational scenarios. Special service requests with ADT. ADT-specific special service request handling through GDS. Meal preferences. Seat preferences. Match special service requests to operational service standards. Codeshare handling with ADT. ADT handling across codeshare flights. Multi-carrier booking. Match codeshare handling to operational scenarios. Stopover handling with ADT. ADT handling across stopovers. Multi-segment booking. Match stopover handling to operational scenarios. Open jaw handling with ADT. ADT handling across open jaw bookings. Different origin and destination on outbound versus return. Match open jaw handling to operational scenarios. Round-the-world handling with ADT. ADT handling across complex multi-segment bookings. Match round-the-world handling to operational scenarios. The ADT GDS and NDC handling compounds significantly over integration lifetime. Strong handling produces foundation for sustained flight booking operations across GDS and NDC distribution channels.

Operating ADT Booking Systems

Beyond initial deployment, ongoing operations involving ADT and passenger type handling require sustained discipline. Booking system maintenance. ADT handling code maintenance. Passenger type framework updates as IATA evolves. Strong booking system maintenance prevents operational issues. Carrier rule monitoring. Per-carrier ADT rule monitoring (age thresholds, fare structures). Rule updates as carriers evolve. Match carrier rule monitoring to multi-carrier scenarios. Age threshold maintenance. Age threshold configuration per carrier. Travel date age calculation maintenance. Strong age threshold maintenance prevents booking errors. Discount percentage maintenance. CHD/INF discount percentage configuration per carrier. Discount calculation accuracy. Match discount percentage maintenance to specific carrier rules. Documentation requirement maintenance. Per-passenger-type documentation requirement tracking. Documentation requirement updates as policies evolve. Match documentation requirement maintenance to compliance requirements. Multi-carrier ADT handling. Cross-carrier ADT consistency monitoring. Per-carrier ADT-specific rule application. Match multi-carrier ADT handling to multi-carrier operational scenarios. Multi-GDS ADT handling. Cross-GDS ADT consistency. Per-GDS ADT-specific syntax. Match multi-GDS ADT handling to multi-GDS integration scenarios. NDC ADT handling evolution. NDC schema evolution affecting ADT handling. NDC implementation updates. Match NDC ADT handling evolution to NDC integration scenarios. Booking flow optimization with ADT. Booking flow A/B testing for passenger type selection. Conversion optimization. Continuous improvement is mandatory for competitive booking systems. Customer support operations. ADT-specific customer support inquiries. Passenger type clarification. Match customer support operations to operational support requirements. Reporting on passenger types. Per-passenger-type booking reports. ADT-specific revenue reports. Match reporting to operational analytical requirements. BSP reconciliation operations. BSP records reconciliation including ADT passenger fare data. Match BSP reconciliation to IATA agency operational requirements. Fare reconciliation operations. Per-passenger-type fare reconciliation. Discrepancy investigation. Match fare reconciliation to financial operational requirements. Compliance management. Passenger type-specific compliance requirements. Documentation compliance. Strong compliance management prevents legal issues. Vendor relationship management. GDS provider relationships affecting ADT handling. NDC aggregator relationships. Match vendor relationship management to commercial relationship strategy. Strategic evolution. Periodically reviewing ADT handling strategy. Evaluating multi-passenger-type optimization opportunities. Match strategic evolution to operational priorities. Innovation adoption. AI-assisted passenger type recommendation. Personalization for repeat passengers. Match innovation adoption to operational differentiation. Customer feedback integration. Customer feedback on passenger type selection UX. User research. Match customer feedback integration to operational improvement strategy. Engineering capability evolution. Booking system engineering capability. GDS integration expertise. NDC integration expertise. Strong engineering capability supports operational evolution. The flight booking systems that handle ADT effectively combine careful initial implementation, disciplined operational management, sustained carrier rule monitoring, ongoing GDS/NDC integration maintenance, and strategic discipline. The compounding benefits over multi-year operations significantly exceed transactional benefits including substantial booking accuracy, customer satisfaction, and operational compliance. For travel platforms handling ADT in flight booking today, the strategic guidance includes evaluating ADT handling capability for specific operational scope, building sustained engineering capability supporting passenger type framework, treating ADT and passenger type handling as foundation of accurate flight booking operations.

FAQs

Q1. What is ADT in airline ticket?

ADT in airline ticket represents the IATA passenger type code for adult passenger. ADT (Adult) typically applies to passengers 12 years and older for international flights. Adult fares are the standard fare basis without age-based fare reduction. ADT passenger type code appears in PNRs, e-tickets, GDS responses, travel agency systems.

Q2. What other passenger codes exist?

ADT (Adult, 12+ years typically), CHD (Child, typically 2-11 years), INF (Infant, typically under 2 years without seat), CNN (Child variant), YTH (Youth), STU (Student), SEA (Senior), MIL (Military), GOV (Government), VFR (Visiting Friends and Relatives), CRP (Corporate), GRP (Group).

Q3. How does ADT affect fares?

ADT (Adult) passenger type triggers standard adult fare rules without age-based fare reduction. Adult fares form the base fare basis. Other passenger types (CHD, INF, etc.) typically receive percentage-based discount off adult fare (e.g., 75 percent for CHD, 10 percent for INF).

Q4. When does ADT apply?

ADT typically applies to passengers 12 years and older for international flights and most domestic flights. Some carriers use different adult thresholds (16 for some, 18 for others). Age threshold typically based on travel date age, not booking date age.

Q5. What's the difference between ADT and CHD?

ADT typically applies 12+ years; CHD typically applies 2-11 years. ADT pays full adult fare; CHD typically pays 75 percent of adult fare. ADT requires standard passenger documentation; CHD may require additional documentation. ADT seats independently; CHD typically seats with accompanying ADT.

Q6. What's ADT versus INF?

ADT typically applies 12+ years; INF typically applies under 2 years. ADT pays full adult fare; INF typically pays 10 percent of adult fare or fixed nominal fee. ADT receives own seat; INF typically lap-held by accompanying ADT without seat.

Q7. How does ADT appear in GDS?

ADT appears in GDS (Amadeus, Sabre, Travelport) responses as passenger type indicator in PNR data, fare quotes, ticketing data, e-ticket records. GDS booking commands specify passenger type as ADT for adult passengers. Different GDS use slightly different command syntax but ADT code applies consistently.

Q8. What about ADT in NDC?

ADT in NDC integration follows IATA passenger type code standard with ADT representing adult passenger. NDC schema includes passenger type field accepting ADT alongside other passenger type codes. NDC implementation should respect passenger type-specific fare rules and pricing.

Q9. How does ADT affect booking systems?

ADT in booking systems affects passenger type selection in booking flow (typically default), fare calculation (full adult fare without discount), ticketing (e-ticket per ADT passenger), seat assignment (own seat per ADT), baggage allowance (full per ADT), passenger information collection.

Q10. What about ADT for travel agency systems?

Travel agency systems handle ADT through passenger type selection in booking workflows, ADT-specific fare calculation, ADT passenger information collection, ADT-specific reporting. B2B travel platforms supporting agent-mediated booking typically default to ADT with override capability for non-adult passenger types.