According to Romania Insider and Euromaidan Press, a drone crashed near Grindu, Tulcea County, in the early hours of 10 November 2025. Romanian military confirmed that for the first time in Romania's documented airspace-violation series, the Romanian F-16s were not scrambled β weather conditions at the airfields grounded the jets. A RO-Alert emergency SMS notification was sent to mobile phones in the affected area at 00:07. Debris was confirmed at the crash site. AirVeto's wind reconstruction at 900 hPa covers the Tulcea corridor during the November 9β10 overnight window.
Illustrative file photo. This image is not from the incident described β it shows a military-type UAV of the kind found in field recovery operations.
The first Romanian failure to scramble β what the weather produced
Every previous confirmed drone incursion in Romania's Danube corridor had been met with a Romanian Air Force scramble β F-16s launching from CΓ’mpia Turzii (primary) or Borcea, with German Eurofighters joining from their NATO Air Policing detachment. The Grindu event on the night of 9β10 November 2025 broke that record: adverse weather conditions at the relevant airfields made launching unsafe, and the jets remained grounded.
The weather in November over southeastern Romania can include low cloud base, reduced visibility, and precipitation β conditions that, at F-16 operating minima, can ground aircraft even when operational necessity is high. The specific conditions on the night of 9β10 November were not publicly detailed by Romanian Air Force sources, but the outcome β no scramble β was confirmed.
This created a perverse outcome: the drone crossed, crashed, and produced debris, but no Romanian or allied aircraft was in the air to track its trajectory, collect imagery, or shadow it. The only data came from radar and the post-crash debris field.
RO-Alert at 00:07 β the public-warning system
The RO-Alert system β Romania's cell-broadcast emergency notification network β sent a message to mobile phones in the Grindu and surrounding area at 00:07 local time. RO-Alert messages use Cell ID broadcast, reaching all phones in the relevant base-station coverage area regardless of subscriber registration. The 00:07 timestamp suggests radar detected the incursion shortly before midnight and the alert was issued within minutes of confirmation.
The Romanian government had been criticised earlier in 2025 for slow or absent public alerts during drone events; the sub-10-minute RO-Alert at Grindu represented an improvement in the public-warning loop.
Debris confirmed at the crash site
Romanian authorities confirmed the presence of drone debris at the Grindu site after the crash. The debris assessment β establishing that a drone had physically impacted at this location rather than simply being tracked and lost β is what triggers the explosion marker in AirVeto's classification (physical impact with no confirmed airborne warhead detonation, but a crash). The type of drone was not publicly confirmed; the Grindu crash site's proximity to the Danube Delta and the standard flight corridors from Russian-occupied Ukrainian territory is consistent with Shahed-class or Gerbera-class vehicles.
Wind layer β 900 hPa over Tulcea on 9β10 November
AirVeto's wind reconstruction covers the 900 hPa pressure level (approximately 1,000 m) over the Tulcea corridor during the overnight window of 9β10 November 2025. The embed above renders the wind field; methodology is described on the AirVeto methodology page.