SINOAID · SHANGHAIChinaMedTransfer

Chengdu Shuangliu International Airport (CTU) medical transfer and patient handover

At CTU, verify the operating flight and terminal, the permitted public-side meeting point and the receiving destination; do not assume airside access.

The airport-code decision

CTU identifies Chengdu Shuangliu, not a generic city pickup. Confirm terminal and flight on the current itinerary, the point where the carrier or airport assistance releases the traveller, and the authorised public-area pickup position. The road provider needs the receiving address and a delay contact. Chengdu has another airport, so do not substitute CTU and TFU.

Separate Chengdu city and onward care

A hospital in Chengdu city and a receiving facility in another locality create different road duty and handover arrangements. Name the final ward or responsible family contact, not merely the city where the aircraft lands. Ask the actual provider to assess the full road duration, patient position and equipment. A delayed flight can move arrival outside the receiving window; someone must reopen that decision before dispatch.

Shuangliu is not Tianfu

A flight coded CTU arrives at Shuangliu, not Chengdu Tianfu (TFU). If a connection or rebooking changes the airport, ask the new ground provider to accept the revised pickup rather than routing a crew from the old instruction. Hospital staff should know which airport the patient has actually landed at and whether the ETA remains within their receiving window.

Exact airport handover

Shuangliu (CTU) is a specific Chengdu airport node, not a general city pickup address. Do not substitute TFU when the ticket says CTU; the airports are different road and handover assignments. Obtain the actual operating flight, date and terminal before asking a supplier to confirm its meeting point. The airline’s mobility service has its own endpoint, and a local road team can only meet where authorised. The final hospital or home address and named receiver determine the onward scope. An airport name by itself cannot establish who helps during the terminal-to-vehicle gap.

Direction and changed arrival

An inbound patient may need airport-to-hospital transport; an outbound patient needs hospital release, road pickup and the airline handover before departure. These are opposite directions and different decision times. Ask whether a wheelchair, stretcher, oxygen or staff is needed during unloading and the public-side wait. A flight delay or change of terminal can cancel the ground meeting plan; the dispatcher should reaccept the new point. If the receiver cannot take the patient at the revised arrival, the responsible clinicians need a new destination decision, not a driver’s improvisation.

Shuangliu release to a Chengdu receiver

For a patient leaving a CTU flight, name the person who has custody of medication and mobility equipment until the ground clinician or driver accepts. If rehabilitation rather than acute admission is intended, the rehabilitation provider must agree to the hour of arrival and support level; the airport cannot decide this. Ask the supplier whether it can assist from its public meeting point into the vehicle and all the way to the receiving doorway. A family companion may take luggage separately. Recheck the plan if the airline assistance ends before the personal wheelchair is returned.

Decision pathway

Confirm airport code, operating flight and the permitted assistance endpoint; secure actual road-provider and receiving acceptance. If terminal, support or arrival time changes, revise and acknowledge one current instruction.

Information for a useful first enquiry

CTU operating flight and date; terminal if known; inbound or outbound direction; mobility/oxygen/stretcher support; public meeting point; destination and receiving contact; payer.

For detailed clinical records, use a direct authorised exchange rather than this public page.

Official sources

Last reviewed: 2026-09-29. Requirements can change; confirm with the responsible organisation.

Initial enquiry

Tell us where, when and what support is needed

A short description of the route and support required is enough to start. Send any case details directly by email, not through a public webpage.