Plan a Shanghai Pudong arrival or departure around confirmed responsibilities, not an assumed aircraft-side pickup or a single airport ETA.
Confirm Shanghai Pudong (PVG), the operating carrier, flight number, local date and whether the request concerns an international arrival or a departure. Do not substitute a general “Shanghai airport” instruction. Request the assigned terminal and any change from the carrier or airport information for that flight. A ground plan needs the release or acceptance interface as well as the published flight time.
Airline or handler: who manages the passenger from the aircraft-related service to the agreed airport handover, and what assistance is accepted? Escort: who remains responsible for clinical support while waiting? Ground provider: what meeting point, vehicle, staff and equipment can it confirm? Receiving destination: who accepts the person and within what window? Case owner: who resolves a missed connection, changed ETA or new destination? Record a named contact and confirmed/pending status for each answer.
Airside access involves permissions and operational arrangements beyond booking a road vehicle. A request for tarmac or aircraft-side handover must be assessed with the parties responsible for that flight and airport interface; this page does not promise access. If the handover is landside, agree the exact terminal meeting location and who accompanies the patient to it. Do not assume the road team can enter every area needed to retrieve a passenger.
For an international arrival, clarify who accompanies the traveller through the applicable immigration, baggage and customs processes before the agreed handover. Those processes and their timing are controlled by the responsible authorities and service parties. Record how delays are reported and how the receiving team is informed. Do not quote a fixed landing-to-vehicle interval or promise expedited clearance. The road team’s waiting and any commercial implications should be agreed separately.
Send the actual hospital, care facility or home destination and its receiving status. If the destination is outside Shanghai, assess the onward road commitment and receiving window rather than ending the plan at PVG. If the receiving side cannot take over at the revised time, the case owner needs an agreed revision; airport assistance is not a substitute for continuing clinical care or an accepted hospital bed.
The airport’s published accessibility information distinguishes Terminal 1, Terminal 2 and satellite-hall facilities and describes shared wheelchairs for short-distance mobility. These facilities do not establish medical staffing, patient transfer capability or restricted-area access. Check the current official airport information and the exact carrier arrangement. Source reviewed 6 October 2026. Send flight, local date, requested support, proposed handover and receiving status to begin a case-specific confirmation.
| Interface | Confirmation parties | Answer to obtain |
|---|---|---|
| Aircraft / airport service → agreed meeting point | Carrier or handler and accompanying team | Confirm assistance boundary and permitted handover location |
| Meeting point → road vehicle | Local provider and handing-over team | Confirm transfer assistance and continuing support |
| Road vehicle → receiver | Road team and named receiving party | Confirm acceptance, location and revised ETA if delayed |
| Changed flight or receiver | Case owner and relevant decision holders | Reconcile revised scope before assuming the old plan still works |
Ningbo / Fenghua: check support continuity, escort handover and a late receiving window. PVG to Ningbo / Fenghua medical transfer: support continuity after arrival →
Wenzhou: define the stretcher journey, accompanying team and whether companions or baggage need a separate vehicle. PVG to Wenzhou medical transfer: escort, vehicle and receiving scope →
For an arriving passenger using equipment, attach the confirmed flight configuration and remaining ground dependencies to the receiving brief. Medical equipment on China flights: a device-by-device approval pathway →
Send the route, local date, required support, receiving status and payer contact. Exchange detailed records through an agreed authorised follow-up channel; sending an email does not confirm a booking.