Benazir assassination case: Mark Siegel refuses to record statement in Pakistan

Citing security reasons, US author says he can record his statement through a video link


Web Desk March 31, 2015
A file photo of former prime minister Benazir Bhutto. PHOTO: EXPRESS

Citing security reasons, US author Mark Siegel refused to appear in person to record a statement against former military ruler Pervez Musharraf in the Benazir Bhutto assassination case, Express News reported Tuesday. 

Former prime minister Benazir was assassinated outside Rawalpindi’s Liaquat Bagh on December 27, 2007 and according to Siegel, Musharraf had threatened Benazir with “dire consequences” if she returned home before the 2008 election.

Along with five other prosecution witnesses, Siegel was summoned on January 5 by an anti-terrorism court to record statements in the high-profile assassination case.

Read: Benazir Bhutto case: Arrest warrants out for six witnesses

Though he refused to record his statement in Pakistan today, Siegel said he can do so via a video link.

Read: Benazir assassination case: ATC summons Mark Siegel on Jan 5

Siegel, a key prosecution witness who had known Benazir since 1984, claims that Benazir had received a telephone call from Musharraf in his (Siegel) presence and told her that he would not be responsible for her security if she returned before the election. He alleges that Musharraf knew of the assassination plot and had personally ordered the destruction of evidence.

COMMENTS (1)

Ahmed Haroon | 9 years ago | Reply The judiciary's reluctance in allowing Mark Siegel's statement through video link when Mansoor Ijaz was given full support for the same leaves little need for the statement or the whole case for that matter. Lets just save public money and close the file when clearly the people committing BB's murder the sameone's who are always in power in this country cannot be touched.
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