Haqqani commander 'killed in Afghan strike': NATO

ISAF identifies the militant as Dilawar, a lieutenant of Haji Mali Khan.


Afp October 05, 2011
Haqqani commander 'killed in Afghan strike': NATO

KABUL: The NATO-led force in Afghanistan said Wednesday it had killed another senior member of the al Qaeda-linked Haqqani network in an air strike near the Pakistani border.

The International Security Assistance Force (ISAF) identified the militant as Dilawar, a lieutenant of Haji Mali Khan, said to be the senior leader in Afghanistan and whose capture the military announced last week.

Dilawar, who like many Afghans goes by one name, "was a principal subordinate to Haji Mali Khan... Dilawar was killed exactly one week following Khan's capture," ISAF said in a statement.

His death was "another significant loss for the insurgent group," it added.

The military accused Dilawar of coordinating attacks against Afghan forces and moving weapons along the Afghan-Pakistani border.

The feared Haqqani network has its main powerbase in eastern Afghanistan but its leadership is based across the border in Pakistan's tribal belt.

Afghan and US officials accuse the network over a string of high-profile attacks in heavily-guarded Kabul, including last month's 19-hour siege which targeted the US embassy and ISAF headquarters.

Dilawar was killed in the eastern province of Khost on Tuesday, ISAF said, stressing no civilians were injured in the operation.

COMMENTS (15)

Freeman | 13 years ago | Reply

@Nirmit: American Double Standards.

US officials met Haqqani network leaders: Report http://tribune.com.pk/story/267353/us-officials-met-haqqani-network-leaders-report/

Diggvijay Singh | 13 years ago | Reply

@Mirza:

Dear friend, Thank you for your kind words. I am doing my bit to restore some sanity and equilibrium in this mad, topsy-turvy world by spreading the message of love, peace and kindness.

VIEW MORE 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