Skip to content

Should F1 rethink Jeddah in 2027 after Formula E postpones Saudi race?

1 Comments
Formula E has postponed its planned season-opening double-header in Jeddah, putting Saudi Arabia’s place on the international motorsport calendar back under scrutiny. With Formula 1 scheduled to return to the same venue in March 2027, should the championship be reconsidering its plans?
Jeddah had been due to launch Formula E’s Gen4 era on 18-19 December 2026. Instead, the Saudi Arabian double-header has been moved to 16-17 April 2027, leaving Mexico City to open the championship on 16 January.
The reshuffle comes against the backdrop of conflict in the Middle East and concerns surrounding travel to the region and while the decision does not mean Formula 1’s Saudi Arabian Grand Prix has been postponed or cancelled, it raises a clear question on how confidently can F1 plan its own return when another world championship has pushed back its visit?

Formula E explains its Jeddah decision

In its official announcement, Formula E said the revised dates followed discussions with its Saudi partners, the FIA and local stakeholders. The championship cited “recent developments in the region and the logistical considerations involved”, while stressing that Jeddah would retain both races.
ADVERTISEMENT
Sanya’s E-Prix has consequently been brought forward to 3 April, allowing Formula E to preserve its planned race count. It means that Formula E has not abandoned Saudi Arabia; it has given itself more time before returning.

Nevertheless, moving the competitive debut of a new generation of cars is a significant adjustment, rather than a routine calendar change.
For Formula 1, the timing is particularly relevant. As GPblog previously reported when the 2027 calendar was announced, Jeddah is scheduled to host the Saudi Arabian Grand Prix on 19-21 March. F1’s visit would therefore take place before Formula E’s rearranged event.

Previous disruption gives F1 reason to prepare

There is already a recent precedent for disruption. GPblog’s Saudi Arabian Grand Prix coverage details how the 2026 race was cancelled amid the escalating regional situation, with safety concerns and transport difficulties contributing to the decision.
ADVERTISEMENT
The race was also cast into doubt in 2022 when a local oil refinery was hit in a drone attack, with drivers at the time holding a meeting with F1 and the FIA about whether it was safe to race.
That history makes contingency planning more than a theoretical exercise. GPblog has also previously examined the practical consequences of uncertainty for the paddock.
In its report on teams seeking earlier clarity over Middle Eastern races, the financial and operational difficulties of waiting for decisions were highlighted. The same issue applies to preparations for 2027.
Teams, suppliers, broadcasters and travelling supporters need to make arrangements well before a race weekend begins. A place on the published calendar cannot, by itself, remove the uncertainty surrounding those plans.
ADVERTISEMENT

Should Formula 1 reconsider Jeddah?

Formula E’s postponement is not proof that racing in Jeddah will be impossible in March because conditions could change, and the two championships have different schedules and logistical requirements.
Equally, Formula E’s decision to retain an April date should not be treated as a guarantee that the situation will have stabilised by then.
The sensible question for F1 is therefore not whether it should immediately cancel the Saudi Arabian Grand Prix, but whether it has a credible alternative and a clear timetable for deciding and this could lead to a shuffling of the schedule again.
Jeddah remains on the 2027 schedule. Yet after losing its Formula E season opener, the venue warrants renewed scrutiny. Formula 1 should be prepared to explain what would allow its March race to proceed, and ready to act if those conditions are not met.
ADVERTISEMENT

Don’t miss GPblog in Google

Mark us as a preferred source and our articles will appear more often at the top of Top Stories.

Add as a preferred / source on Google
loading

Loading