A helicopter can be an important part of a WEF travel plan, but it should not be the only transport plan.
If an aviation movement cannot operate because of weather, airspace restrictions, operational constraints or another flight-side decision, the critical question is not simply whether a car can be found.
The real question is:
can the road movement take over without rebuilding the entire journey from zero?
For the World Economic Forum Annual Meeting 2027, scheduled in Davos from 18 to 22 January 2027, Executive Assistants, Family Offices, flight departments and delegation coordinators should treat helicopter transport and road transport as two separate but connected operating plans.
A useful WEF helicopter road backup should already define the passenger handover, vehicle requirement, luggage movement, Zurich departure point, Davos destination and the person authorised to activate the alternative.
A Road Backup Is Not a Car Ordered After the Helicopter Cancels
There is a major difference between having a road backup and having the phone number of a chauffeur company.
A true backup plan answers the important questions before the aviation itinerary changes:
- Where is the passenger when the road plan becomes necessary?
- Where should the chauffeur vehicle be positioned?
- Who decides that the helicopter plan is no longer operating?
- Does the principal travel with all luggage?
- Are staff or assistants travelling separately?
- What is the exact destination in Davos?
- Does the final Davos access plan need to change?
Without these decisions, a supposed “Plan B” is really a new transport request being created under time pressure.
Why Helicopter and Road Transport Should Be Planned as Separate Movements
The aviation provider controls the aviation movement.
The chauffeur operator controls the road movement.
These services may connect to one another, but they do not share the same operational permissions, timing or responsibilities.
| Helicopter / Aviation Plan | Road Backup Plan |
|---|---|
| Aircraft availability and operation | Vehicle availability and assignment |
| Aviation weather assessment | Road and winter travel planning |
| Airspace and aviation authorisation | Road access and final destination |
| Passenger aviation handover | Chauffeur pickup point |
| Aircraft baggage constraints | Passenger and luggage vehicle allocation |
| Aviation operator decision | Ground transport activation |
Swiss Transfer Service provides the ground transportation component.
It does not operate helicopters and should not be treated as the aviation decision-maker.
The purpose of a road contingency is to ensure that when the aviation provider changes or cancels the planned movement, the ground transport team already understands what must happen next.
WEF Adds Another Layer: Airspace and Helicopter Traffic Can Be Controlled
Previous WEF Annual Meetings have involved temporary aviation restrictions around Davos.
Official information from the Canton of Graubünden for WEF 2026 stated that civilian aircraft movements through restricted airspace were subject to controls and that helicopter traffic to Davos also had to be managed during the Annual Meeting.
Those historical rules are useful evidence that WEF aviation movements require more than a normal point-to-point assumption.
They should not, however, be copied forward as if the exact same restrictions are already confirmed for 2027.
The detailed 2027 aviation and access rules should be checked against the current official information when the relevant authorities publish them.
Current event information confirms that the World Economic Forum Annual Meeting 2027 is scheduled for 18–22 January 2027 at the Davos Congress Centre.
When Should the Road Backup Be Activated?
One of the most important decisions is not where the car waits.
It is who has authority to tell the chauffeur team that the road plan is now active.
Depending on the itinerary, that person might be:
- the Executive Assistant;
- the Family Office travel coordinator;
- the flight department;
- the aviation operator or handler communicating through the client’s coordinator;
- the head of delegation logistics.
The chauffeur team should not have to interpret aviation information and independently decide that a helicopter will not operate.
The aviation-side decision and the road-side activation should remain clearly separated.
A simple operational instruction is often enough:
“If the aviation plan is cancelled, Person X activates the road movement and confirms the passenger pickup location.”
That single decision rule can remove a surprising amount of confusion.
Where Should the Backup Vehicle Be Positioned?
There is no universal answer.
The correct location depends on the traveller’s actual itinerary.
Scenario 1: The passenger is still at Zurich Airport
If the principal has arrived in Zurich by commercial flight and the planned onward helicopter movement cannot operate, the road backup may begin from the airport.
The chauffeur team needs:
- the correct passenger pickup point;
- current passenger contact information;
- the luggage requirement;
- the exact Davos destination;
- confirmation that the road plan has been activated.
Scenario 2: The passenger arrives through Zurich Airport GAC
A private aviation arrival requires another handover layer.
Zurich Airport officially states that passengers using business aviation are escorted between the aircraft and the General Aviation Center, while the selected FBO or ground handling provider manages the aviation-side organisation.
The road vehicle should therefore be coordinated around the actual authorised passenger handover rather than an assumed aircraft-side pickup.
Our dedicated Zurich Airport GAC to Davos guide for WEF 2027 explains the distinction between FBO handling, passenger release and chauffeur transportation in more detail.
Scenario 3: The passenger has not yet reached Zurich
If the aviation itinerary changes before the traveller reaches Zurich, positioning a vehicle too aggressively can create another problem.
A chauffeur sent toward the wrong arrival location may no longer be useful if the passenger’s aviation plan changes again.
For that reason, vehicle dispatch timing should follow the latest confirmed ground requirement rather than an assumption about what the aircraft will do.
Landing Time Is Not the Same as Road Departure Time
This distinction is particularly important for private aviation.
Aircraft arrival, passenger processing, escorted movement, baggage handling and the final chauffeur handover are separate stages.
A vehicle plan built only around “aircraft lands at 10:30” may therefore create unrealistic expectations.
The ground transport team should instead work with:
- the latest aviation information available to the coordinator;
- the confirmed handover arrangement;
- the passenger’s readiness to move by road;
- the luggage status;
- the person authorised to activate the backup.
Luggage Can Break an Otherwise Good Backup Plan
A road backup may solve the principal’s transport problem while leaving the luggage problem unresolved.
This becomes especially relevant when the original aviation itinerary and the road replacement have different baggage assumptions.
The transport coordinator should establish:
- how many passengers are moving by road;
- how many checked bags are involved;
- whether there are garment bags or presentation cases;
- whether specialist equipment is travelling;
- whether staff luggage is mixed with principal luggage;
- whether all items are available at the same time as the passenger.
The principal and the luggage do not always need the same vehicle plan
For some programmes, the correct solution may be one vehicle for the principal and another movement for assistants, staff or additional luggage.
The point is not to automatically add more vehicles.
It is to avoid discovering after the aviation plan changes that the assigned road vehicle solves only part of the transport requirement.
What If the Principal and Staff Need Different Road Movements?
A WEF arrival often involves more than one traveller with more than one priority.
Consider a simple scenario:
- the principal needs to reach Davos as soon as the road backup is activated;
- an Executive Assistant must remain at Zurich for another arrival;
- staff are following on a separate aircraft;
- part of the luggage is not yet ready.
One vehicle cannot solve all four requirements simply because the original plan involved one helicopter movement.
The transport plan should define whether the programme requires:
- a dedicated principal vehicle;
- a second passenger vehicle;
- a luggage movement;
- a later Zurich-to-Davos transfer for staff.
For programmes involving several executives and simultaneous movements, see our WEF delegation transportation service.
The Road Backup Still Needs an Exact Davos Destination
Activating the road plan does not mean the transport problem is finished.
The road team still needs to know precisely where the principal must be delivered.
Useful information includes:
- hotel or residence name;
- full address;
- office or event location where relevant;
- local host or concierge contact;
- current access instruction supplied to the delegation;
- an alternative handover location if the final vehicle approach is restricted.
Previous WEF editions have included temporary security zones, vehicle controls and restricted-access areas in central Davos.
The exact arrangements can change from one Annual Meeting to another.
That is why the road contingency should not be based on the assumption that a vehicle can automatically reach the same point used in a previous year.
Aviation Backup and Davos Access Are Two Different Problems
This distinction is easy to miss.
A successful road replacement from Zurich does not automatically answer the final-access question in Davos.
Think of the journey as two separate decisions:
- How does the passenger reach Davos when the planned air movement cannot operate?
- How close can the assigned vehicle legally and operationally get to the final destination under the current WEF access arrangements?
The first is the intercity transport problem.
The second is the WEF local-access problem.
Keeping them separate makes it easier to update the plan when official 2027 security or traffic information changes.
What Information Should an EA Send for a WEF Road Backup?
A concise road-backup brief can contain the following information.
Aviation plan
- planned aircraft or helicopter movement;
- arrival or departure location;
- aviation coordinator or operator contact;
- who will confirm that the aviation movement cannot operate.
Passenger plan
- lead passenger;
- passenger count;
- EA or delegation coordinator;
- working mobile contact.
Road plan
- intended pickup location;
- backup vehicle requirement;
- principal versus staff vehicle requirements;
- exact Davos destination.
Luggage plan
- number and type of bags;
- oversized or specialist equipment;
- whether luggage travels with the principal;
- whether another vehicle may be needed.
Activation rule
- who activates Plan B;
- who can approve a changed pickup point;
- who can approve an additional vehicle;
- who receives operational updates.
Common WEF Helicopter Backup Mistakes
Waiting for cancellation before thinking about the road alternative
This turns a contingency plan into a last-minute vehicle search.
Assuming the backup vehicle must sit at one location all day
Positioning should follow the actual itinerary and activation logic rather than an arbitrary waiting point.
Using aircraft arrival time as chauffeur pickup time
Passenger handover and aircraft movement are different operational milestones.
Planning for the principal but not the luggage
The passenger can be ready for road travel before the complete luggage movement has been resolved.
Assuming one vehicle can replace an entire delegation aviation movement
Principal, assistants, staff and equipment may require different road movements.
Not defining who activates the road plan
The chauffeur operator should receive a clear instruction rather than infer an aviation cancellation.
Assuming last year’s Davos access rules still apply
Historical WEF information is useful for planning, but current official restrictions should determine the final 2027 operating plan.
Road Backup Checklist Before WEF 2027
Before travel
- Define Plan A and Plan B as separate transport movements.
- Nominate the person authorised to activate the road backup.
- Share passenger and luggage requirements.
- Confirm the likely road pickup location.
- Provide the exact Davos destination.
- Identify whether staff need independent transport.
When the aviation plan changes
- Confirm that the road backup is active.
- Confirm the passenger’s actual location.
- Confirm whether the luggage is ready.
- Confirm any change to passenger count.
- Reconfirm the Davos destination.
- Send the latest contact information to the chauffeur team.
Before entering Davos
- Check current WEF traffic and access information.
- Confirm any destination-specific instructions.
- Keep the local host or concierge contact available.
- Be prepared for a final handover arrangement if vehicle access is restricted.
Road Backup vs Last-Minute Road Transfer
| Pre-Planned Road Backup | Last-Minute Road Request |
|---|---|
| Passenger details already known | Passenger information still being collected |
| Luggage requirement reviewed | Vehicle suitability unknown |
| Activation authority defined | Several people may be giving instructions |
| Pickup logic understood | Driver position still needs to be decided |
| Davos destination confirmed | Final address may still be unclear |
| Delegation vehicle requirements considered | Additional vehicles requested later |
The difference is not luxury.
It is preparation.
Planning the Full Zurich-to-Davos Road Journey
If the road alternative is activated, the passenger moves into the same wider winter arrival environment faced by other WEF travellers travelling from Zurich toward Davos.
For road planning, luggage considerations, final destination details and current-versus-historical WEF access information, see our WEF 2027 Zurich Airport to Davos arrival guide.
After arrival in Davos, daily movements become a separate operational problem.
Our guide to executive ground transport during WEF 2027
covers changing meeting schedules, vehicle assignment, overlapping executive movements and daily transport planning.
Arrange a WEF 2027 Road Backup with Swiss Transfer Service
If a WEF itinerary includes a planned helicopter movement, Swiss Transfer Service can review the road transportation requirement separately so that the ground plan is understood before it is needed.
Send the passenger count, aviation itinerary, expected pickup location, luggage requirement, exact Davos destination and the contact responsible for activating the road alternative.
If the programme involves several principals, staff vehicles or overlapping movements, include those requirements so the road plan can be assessed as part of the wider delegation transport programme.
WEF 2027 Helicopter Road Backup FAQ
Should I arrange a road backup before the helicopter is cancelled?
If road transport is an important contingency for the itinerary, the passenger, luggage, pickup and destination requirements should be understood in advance. The road movement can then be activated when the authorised coordinator confirms that it is needed.
Does Swiss Transfer Service operate helicopters to Davos?
No. Swiss Transfer Service provides private chauffeur and ground transportation. Aviation operations, flight decisions, aviation permissions and helicopter movements remain the responsibility of the relevant aviation operators and authorities.
Can a chauffeur wait at Zurich Airport in case the helicopter cannot operate?
A backup vehicle can be planned around the itinerary, but the appropriate positioning depends on the passenger’s arrival method, pickup arrangement, expected activation point and wider transport programme. The vehicle should not automatically be positioned on an assumption that may no longer match the aviation plan.
What happens if the passenger arrives by private jet at Zurich GAC?
The aviation-side passenger handover must be considered before the road journey begins. Zurich Airport states that business aviation passengers are escorted between the aircraft and the General Aviation Center, so the actual chauffeur handover should be confirmed for the specific arrival rather than assuming automatic planeside access.
Can the principal and luggage travel in different vehicles?
Where passenger, luggage, staff or equipment requirements justify it, the road plan can be assessed as separate movements. Vehicle assignment should be based on the actual transport requirement rather than an assumed luggage capacity.
Are the WEF 2027 helicopter and Davos access restrictions already confirmed?
The Annual Meeting dates are confirmed for 18–22 January 2027. Previous editions involved controlled helicopter traffic, temporary airspace measures and restricted-access areas in Davos, but the detailed current 2027 rules should be checked against the official information published for the event.
What information should I send when requesting a WEF road backup?
Send the aviation itinerary, passenger count, expected road pickup location, luggage requirements, exact Davos destination, relevant coordinator contact and the person authorised to activate the road movement.
Can the road backup be part of a larger WEF delegation transport programme?
Yes. Where several principals, assistants, staff vehicles or multiple arrival movements are involved, the backup can be considered as one part of the wider ground transport plan rather than as an isolated airport transfer.