WHO Chief suffers hearing problems after Israeli airstrike in Yemen

"I’m okay, but I developed tinnitus from the loud explosion. I hope it will be temporary," wrote Tedros on X.


News Desk January 01, 2025
World Health Organization (WHO) Director-General Tedros Adhanom Ghebreyesus attends a news conference in Geneva Switzerland July 3, 2020. PHOTO: REUTERS

Listen to article

World Health Organization (WHO) head Tedros Adhanom Ghebreyesus has been suffering from tinnitus after he and his WHO team were caught up in an Israeli airstrike in Yemen.

“I am okay but I have developed tinnitus [ringing in my ears] from the loud explosion. I hope it will be temporary,” Tedros, 59, wrote on X after his return to Geneva.

In his New Year message, the UN chief called peace the best medicine, stressing that war brings only death, destruction, and displacement, and urging a focus on finding a political solution for lasting peace for future generations.

The Israeli airstrike targeted the airport in Yemen’s capital, Sanaa, last Thursday, just as Tedros and his team were about to board their flight following talks in the city.

According to Tedros, one of his team members was injured in the attack, and significant damage was done to the control tower, departure hall, and runway of the airport.

Israel’s military stated that the strike targeted Houthi militia infrastructure, including several facilities at the international airport.

Following the airstrike, the UN Secretary-General issued a statement underscoring the importance of adhering to international law, particularly humanitarian law.

He emphasized that civilians and civilian infrastructure must be protected and that humanitarian workers should never be targeted.

The Secretary-General also expressed deep concern about the risk of further escalation in the region and called for all parties to cease military actions and exercise maximum restraint.

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