Al-Jazeera says news crew kidnapped in Yemen freed

The news crew went missing while covering conflict between rebels and Gulf-backed forces loyal to President Hadi


Afp January 28, 2016
Yemeni tribesmen from the Popular Resistance Committees, supporting forces loyal to Yemen's Saudi-backed President Abedrabbo Mansour Hadi, hold a position on the outskirts of Taez, on January 26, 2016 PHOTO: AFP

DOHA: Al-Jazeera said on Thursday that a three-man news crew for the Qatar-based channel has been freed more than 10 days after being kidnapped in the flashpoint Yemeni city of Taez.

Reporter Hamdi al-Bokari, cameraman Abdulaziz al-Sabri and driver Munir al-Subaie went missing on January 18 while covering the conflict between rebels and Gulf-backed forces loyal to President Abedrabbo Mansour Hadi.

In world's most dangerous country for journalists, female reporters try guns for a change

The pan-Arab news channel said on its website early on Thursday morning that the three had been freed "a short while ago" after having been kidnapped by "unknown gunmen".

In a message posted on his Facebook page, Bokari said he had been held by the Iran-backed Shia Huthi rebels, under fire since March from a Saudi-led coalition, of which Qatar is a member.

"We heard them repeat 'Death to America'," a slogan the Huthis and Iranian protesters commonly chant, he wrote, adding that he would release more details about the kidnapping in the coming days.

The city of Taez is held by loyalists of Yemen's internationally recognised government, but it has been besieged by the Iran-backed rebels for months.

Pakistani among 14 fallen journalists honoured by US museum

The Huthis overran Sanaa more than a year ago, forcing Hadi's government to flee the Yemeni capital.

Hadi loyalists backed by a Saudi-led coalition have fought back and have been trying to retake Taez province and pave the way towards the rebel-held capital.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ