The FCDO added new guidance to its Romania travel advice on 18 September, covering drones crossing into Romanian airspace and territorial waters. Its own change note reads: "New information about drones crossing into Romanian airspace ('Safety and security' page)."
The new text is short and worth reading in full: "There have been cases of drones crossing into Romanian airspace and territorial waters, and occasionally, drones carrying explosives have landed or washed ashore in Romania. If you encounter drone activity follow guidance from local authorities, including the RO-Alert mobile phone alert system, and do not approach any military debris."
It sits in the safety and security section, alongside the FCDO's standing note that there is widespread military activity in neighbouring Ukraine.
Be clear about what this is not. It is not a change to where the FCDO says you can travel. The Romania advice has no regional risks section at all, and the FCDO advises against travel to no part of the country. The advice is in five parts: warnings and insurance, entry requirements, safety and security, health, and getting help. A team planning Romanian work has not been handed a new no-go area. It has been handed a named physical hazard that the advice did not previously spell out.
Two things follow for planning. RO-Alert is Romania's public warning system, sent to mobile phones, and the FCDO now names it as the channel to follow during drone activity. Anyone running Black Sea coast or Danube delta movements should have it briefed and understood before arrival rather than discovered during an incident. Second, the instruction not to approach military debris belongs in vehicle and ground SOPs rather than in an aviation annex, because the realistic encounter is a driver or a team member finding something on a beach or a field margin.
One limit on this, stated plainly. We cannot point you to a primary source for a specific incident behind the change. The FCDO marks the entry as new information rather than an update, which is its own marker for an addition rather than a revision, and the previous change to the page was on 11 August on an unrelated entry requirements point. Beyond that, the trigger is not something we can evidence, so we are not going to assert one.
