Ukrainian air monitoring reported a single Russian jet-powered Shahed (Geran-3) drone transiting through Ternopil Oblast in western Ukraine on October 15 at 01:53 UTC, heading west. The report, posted by the Ukrainian Air Force command (@kpszsu), placed the aircraft near Melnytsia-Podilska. No interception or strike outcome was noted in the observation.
Ternopil Oblast lies in Ukraine's western corridor and frequently appears in transit routes for Russian strike drones heading toward targets in central and western Ukraine. The westbound trajectory aligns with a pattern of multiple Geran-3 sightings across adjacent regions on the same night—including simultaneous or near-simultaneous reports in Ivano-Frankivsk, Rivne, and Krasyliv. Such concentrated drone activity often indicates a coordinated strike package, though individual transit reports do not confirm intended targets. The Geran-3 is a jet-powered variant with extended range relative to earlier Shahed models, capable of deep strikes into Ukrainian territory.
Single source: Ukrainian Air Force command (@kpszsu) on Telegram. Related events corroborate regional drone activity on October 14–15. Confidence score of 8.0 reflects reliable source credibility but single-channel reporting and regional (not point-specific) location precision. Cross-confirmation from independent air defense or radar sources would raise confidence; absence of strike reports from the affected region may lower assessed significance.
Ternopil Oblast, western Ukraine, near Melnytsia-Podilska settlement. Located approximately 280 km west of Kyiv, the oblast forms part of Ukraine's western defensive belt. Regional precision indicates the drone's position was tracked by air monitoring systems but not pinpointed to a specific facility or coordinate.
▶ View this event on the live map
Intel Mapper aggregates open-source reports from monitored Telegram and X channels, geolocates them, cross-checks duplicates across sources and assigns a confidence score. Entries are updated as new confirmations arrive. Read how we verify events.