The Yemeni Government forces released video footage on September 15 documenting a first-person-view (FPV) kamikaze drone strike against a Houthi combatant in the Sanaa region. The footage shows a precision strike targeting an Ansar Allah fighter. The report was shared via X by conflict monitoring account ConflictTR, citing the original Turkish-language source describing the strike as conducted by Yemen's military.
Sanaa, Yemen's capital, has been under Houthi control since 2015 and remains a focal point of Yemen's ongoing civil conflict. The release of strike footage by Government forces suggests an effort to demonstrate operational capability and battlefield activity in contested territory around the capital. FPV drone strikes have become increasingly common in Yemen's conflict, used by multiple factions to conduct targeted strikes with minimal collateral risk. The public documentation of such operations often serves both tactical and strategic messaging purposes within the broader information environment of the conflict.
The event was reported by conflict monitoring account ConflictTR on X. Source count is one, indicating limited cross-confirmation at present. Confidence score of 6.0 reflects the single-source nature of the report. Confidence would increase with corroboration from additional independent channels or Yemeni Government official statements, or decrease if the location or actor attribution were contradicted by rival sources.
The strike was reported in the Sanaa region (geo_precision: region), Yemen's capital city located in the northwestern highlands. Sanaa has been a control flashpoint throughout Yemen's civil war and remains under Houthi administration. The specific coordinates (15.35°N, 44.21°E) place the report within the greater Sanaa urban area.
▶ 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.