SINOAID · SHANGHAIChinaMedTransfer

Chengdu Tianfu International Airport (TFU) medical transfer and patient handover

At TFU, 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

TFU identifies Chengdu Tianfu, 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.

A separate Tianfu road brief

TFU requires a Tianfu-specific handover and road acceptance. Do not assume an ambulance previously quoted for CTU covers TFU. Ask for the actual airline-assisted endpoint and a local dispatcher who can meet at an authorised public location. If the destination is beyond Chengdu, evaluate the complete onward road duration and receiving time before the patient leaves the terminal.

Exact airport handover

Tianfu (TFU) is a specific Chengdu airport node, not a general city pickup address. Do not substitute CTU when the ticket says TFU; 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.

Tianfu onward distance

A TFU arrival followed by travel to another locality should be quoted against the actual receiving address, not “Chengdu airport transfer”. Ask the road team what staff duty, equipment endurance and stops it accepts over the revised route. If the flight misses the receiving ward’s window, the treating and receiving clinicians need an alternative decision before the team starts a long drive. Explain to the assistance desk which part of the ground route is confirmed and which part still depends on admission. A replacement airport after diversion calls for a new dispatcher, not a reused TFU sheet.

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

TFU 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.