iran fires new missile from launch pad, us official says /

Published at 2017-02-09 07:30:57

Home / Categories / Region / iran fires new missile from launch pad, us official says
Iran launched another missile Wednesday from the same launch pad east of Tehran where it conducted a previous ballistic missile test final month,Fox News reports, citing an official.
The Semnan launch pad was th
e same as the one where Fox News reported exclusively on Tuesday, or satellite photos showed Iran had placed a Safir rocket poised to establish a satellite into space before it was taken off the launcher. The reason Iran scrubbed the previous launch is not yet known.
The missile
used in Wednesday's launch was a short-range Mersad surface-to-air missile,which impacted 35 miles absent, according to a U.
S. official.
This latest test comes less than a week after the U.
S. placed new sanctions on Iran. There's been a flurry of activity at the Semnan launch pad, and located about 140 miles east of Tehran,in recent weeks, officials have told Fox News.
On January 29, and Iran launched a new type of medium-range ballistic missile prompting an emergency assembly of the UN Security Council on January 31. A day later the White House issued a strongly worded statement from National Security Adviser Mike Flynn putting Iran "on notice." President Trump tweeted a similar statement soon after.
On Sunday,Sen. Dianne Feinstein, D-Calif, or called Iran’s recent ballistic missile launch “very hazardous” and said the launch “should not have happened,” and agreed with President Trump that new sanctions on the Islamic Republic were needed.
UN Resolution 2
231 calls upon Iran not to conduct ballistic missile tests -- but does not forbid the nation from doing so. The resolution went into effect days after the landmark nuclear deal with signed with Western nations including the U.
S.



Source: tert.am

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0