United States Palm Beach Airport Begins a 40-Day Dual-Code Migration as Federal Aviation Systems Replace PBI and KPBI with DJT and KDJT Before Airline Reservations and Baggage Platforms Complete Their Passenger-Facing Transition

Written By: Antara Mitra

Antara Mitra

I am a content writing professional with an academic background in Journalism and Mass Communication. My professional journey began with academic research and content writing, where I developed strong research, analytical, and documentation skills. As I progressed in my career, I gained experience in creating website content, blogs, articles, and other forms of web content across diverse industries. I later expanded my experience into marketing copywriting, creating content for social media posts, reels, static creatives, website copy, and brand communication.

See Full Bio

July 11, 2026 14:18 GMT+5:30

Image generated with Ai

President Donald J. Trump International Airport has entered a 40-day dual-identity period after the Federal Aviation Administration completed its chart and database changes on 9 July. FAA operational systems now use DJT and the ICAO identifier KDJT. However, passengers must continue using PBI for airline bookings, boarding passes and baggage tags until the IATA code changes on 18 August. Flights, routes, schedules, ownership and airport services remain unchanged during the phased migration.

Palm Beach Airport Begins a Rare Split-Code Transition

Palm Beach Airport in the United States is now operating under two separate identification timelines.

The FAA completed the required aeronautical updates associated with the airport’s new name on 9 July 2026. Its three-letter FAA location identifier changed from PBI to DJT. Its four-letter International Civil Aviation Organization identifier moved from KPBI to KDJT.

Yet the commercial aviation system used by most travellers has not changed.

The International Air Transport Association code remains PBI until 18 August. Passengers should therefore continue searching for PBI when booking flights, checking reservations, reviewing boarding passes or tracking baggage during the transition.

The airport expects DJT to appear in airline reservation systems, ticketing tools, baggage tags and related travel platforms after the IATA implementation date. The change follows a request made to IATA by several airlines serving the airport.

This creates a 40-day period in which pilots, aviation operators and federal systems may use DJT or KDJT while passengers continue seeing PBI.

How DJT, KDJT and PBI Identify the Same United States Airport

The simultaneous use of three codes does not represent three airports. Each identifier serves a different part of the aviation ecosystem.

The FAA has clarified that it does not approve airport names. Its responsibility is to update charts, databases and associated federal aviation records after the relevant naming process has been completed.

That distinction is important. The state and county controlled the legal and licensing process. The FAA managed the technical aviation-system transition. IATA is handling the separate commercial code migration.

Passengers Must Keep Using PBI Until 18 August

Travellers should not manually replace PBI with DJT when searching for flights before the IATA cutover.

The FAA says PBI will continue appearing on booking confirmations, boarding passes and luggage tags until 18 August. The airport also confirms that airline routes, schedules and customer services remain unaffected.

There is no airport relocation. The terminal remains at 1000 James L. Turnage Boulevard in West Palm Beach. Palm Beach County retains ownership, governance and operating control.

No additional check-in procedure has been introduced. No passenger document needs to be amended solely because of the airport’s renaming. Existing tickets remain valid when they display PBI.

Traveller-facing systems most likely to retain PBI

The safest approach is to follow the identifier generated by the operating airline rather than editing an active booking.

Why the Code Split Matters to Airlines and Travel Technology

The immediate issue is data synchronisation, not flight disruption.

An airline operations department may already see KDJT in flight-planning data while the same carrier’s passenger reservation environment still produces PBI. A travel management company may receive PBI from a booking channel but DJT from an operational flight feed.

This can create temporary mismatches across global distribution systems, agency mid-office platforms, customer relationship databases, expense systems and destination-content tools.

The greatest risk is duplicate airport creation. A platform that treats PBI and DJT as unrelated locations could divide bookings, expenditure reports or traveller profiles between two records. It could also break automated rules connected to airport transfers, hotel searches, corporate travel policies or disruption alerts.

The stronger technical response is to preserve PBI as a historical alias while mapping it to DJT as the same physical airport. Companies should avoid deleting the former code because older tickets, archived records and future schedule changes may continue referencing it.

This analysis follows from the separate FAA and IATA implementation dates. The official notices do not report a service failure, but they establish the conditions that require careful data governance across the travel distribution chain.

FAA Compliance Work Continues Beyond the Passenger Cutover

The passenger transition ends on 18 August, but some regulated aviation work continues for longer.

FAA Information for Operators notice 26011 advises affected operators and air agencies to assess whether they need to amend certificates, authorising documents and airport data held in federal systems.

The notice applies across multiple parts of the United States aviation regulations. It covers air carriers, charter operators, air agencies, maintenance organisations, flight schools and other regulated aviation businesses.

Potential changes include Air Carrier Certificates, Operating Certificates, Air Agency Certificates, operations specifications, management specifications and letters of authorisation.

Operators may also need to update the Safety Assurance System and other FAA repositories. Relevant records can include an organisation’s principal place of business, main operating base, maintenance base, address or assigned airport data.

The FAA notice describes itself as guidance rather than a separate legally binding enforcement instrument. However, it states that certificates, authorising documents or information systems still referring to PBI after 90 days may be considered non-compliant with applicable regulations.

Florida Law Created the Airport Renaming Framework

The airport name change followed Florida legislation signed on 30 March 2026.

The law transferred authority over the naming of major commercial service airports to the state. It codified the names of seven Florida airports classified by the FAA as large or medium hubs.

Palm Beach was the only airport whose existing name changed under the legislation. The law also established that the naming designation did not create a new legal entity or automatically require the replacement of every existing document.

Palm Beach County subsequently entered a naming-rights and licence agreement on 5 May. The agreement addressed the authorised commercial use of the new airport name and protected the county against potential trademark or publicity-right claims.

The formal airport name and FAA identifier changes became effective on 9 July. Signage, branding and public-facing materials are being updated in phases.

Renaming Programme Carries an Estimated US$5.5 Million Cost

Palm Beach County Department of Airports estimates that the full transition will cost approximately US$5.5 million.

The programme includes terminal and roadway signs, wayfinding, branding, technology systems, printed material and other operational assets.

Florida has appropriated US$2.75 million. The remaining cost will come from the Department of Airports operating budget and capital improvement programme.

The airport does not use local property-tax revenue for its operations. Passengers will not face a separate renaming charge. The name change also does not guarantee new federal or state infrastructure funding.

Code Change Reaches an Airport Handling 8.7 Million Travellers

The transition affects a substantial South Florida aviation gateway.

Official figures show that the airport handled 8,707,371 passengers during the 12 months ending May 2026. This represented annual growth of 1.6 per cent.

Estimated seat capacity increased by 7.5 per cent to more than 11.2 million seats. Air-carrier movements rose by 5.9 per cent to 68,486.

However, the estimated rolling load factor fell from 82 per cent to 77.5 per cent. Capacity therefore expanded faster than passenger volume.

JetBlue held the largest rolling 12-month share of departing passengers at 25.65 per cent. Delta followed with 24.90 per cent, American Airlines with 20.04 per cent, United Airlines with 13.14 per cent and Southwest Airlines with 7.69 per cent.

Route Network and MICE Access Raise the Commercial Stakes

The airport’s official fact sheet lists more than 40 nonstop destinations and over 200 scheduled commercial arrivals and departures each day.

Its network includes major United States business and leisure markets, alongside international links to The Bahamas and Canada. Future services displayed by the airport include additional flights to Atlantic City, Columbus, Denver and Los Angeles, subject to airline schedules and seasonal operating plans.

The airport is also positioned approximately three miles from downtown West Palm Beach, the convention centre, hotels, resorts, beaches and cultural venues. That proximity gives the code migration relevance for MICE organisers, destination management companies and ground-transport providers.

The airport estimates that it contributes more than US$4.6 billion directly and indirectly to the South Florida economy.

Infrastructure Expansion Continues Behind the Rebranding

The identity transition is occurring alongside significant airport investment.

Palm Beach County’s federal agenda identifies a 46,300-square-foot expansion and modernisation of Concourse B. The project adds circulation space, passenger seating, a sensory room, concessions, support facilities and two gates.

The county is also pursuing runway rehabilitation, terminal security improvements and investment in nearby reliever-airport capacity.

These projects matter more to long-term capacity than the code change itself. However, the rebranding programme competes for management attention, technology resources and capital at a time when passenger facilities are already being expanded.

Critical Actions for Travel Agents and Tour Operators

• Continue searching and booking the airport under PBI until 18 August 2026.
• Do not alter an active ticket merely because operational systems now display DJT or KDJT.
• Explain that PBI, DJT and KDJT identify the same West Palm Beach airport during the transition.
• Preserve PBI as an alias in agency, accounting and customer databases.
• Map future DJT records to existing PBI traveller histories and expenditure reports.
• Check airport-transfer, hotel, cruise and car-hire reservations for code-dependent automation.
• Review destination pages, pre-trip emails, invoices and emergency alerts after the IATA cutover.
• Warn corporate clients that older documents may retain PBI even after new bookings begin displaying DJT.
• Verify flight details through the operating airline when third-party systems show conflicting identifiers.
• Ensure aviation clients assess FAA certificates, authorisations and system records before the 90-day compliance period ends.

Palm Beach Code Migration Will Test Travel-System Coordination

The long-term significance of the change extends beyond airport branding.

It demonstrates how one airport identity is distributed across federal aeronautical systems, international codes, airline reservations, baggage platforms, travel agencies, expense tools and traveller communications.

The operational migration has already taken place. The passenger migration follows on 18 August. Historical PBI records will remain in circulation well beyond that date.

Successful implementation will depend on systems recognising PBI and DJT as the same destination. Airlines and travel technology companies that maintain strong alias mapping should complete the transition with limited passenger impact.

For the wider international travel industry, Palm Beach provides a live case study in managing airport-code changes without interrupting routes or services. The decisive measures will be accurate data mapping, consistent traveller communication and disciplined operational compliance across the distribution chain.