> For the complete documentation index, see [llms.txt](https://resources.atriptech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.atriptech.com/capability/atlas-news/9-air-aq-terminal-change-at-guangzhou-baiyun-airport-can.md). # 9 Air (AQ) Terminal Change at Guangzhou Baiyun Airport (CAN) **Guangzhou Baiyun International Airport (CAN)** is commencing comprehensive upgrade and renovation work on **Terminal 1 (T1)**. As a result, all **9 Air (AQ)** flights will relocate from **Terminal 1 to Terminal 2** at Guangzhou Baiyun International Airport. **Effective Date:** 15 January 2026 **New Bookings (from 31 December 2025):** All 9 Air (AQ) flights departing from or arriving at Guangzhou automatically display Terminal 2 (T2) in booking confirmations. No action is required. **Existing Bookings (made on and before 30 December 2025):** \ Previous ticket confirmations and SMS notifications show Terminal 1 (T1). These passengers must be notified of the terminal change to avoid confusion or missed flights. Thank you for promptly notifying your passengers and ensuring smooth travel experiences. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://resources.atriptech.com/capability/atlas-news/9-air-aq-terminal-change-at-guangzhou-baiyun-airport-can.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.