About Us

IMRA
IMRA
IMRA

 

Subscribe

Search


...................................................................................................................................................


Monday, June 16, 2025
There's a Plan For Fordo And It's Not "Yihyeh Bseder"

There's a Plan For Fordo And It's Not "Yihyeh Bseder"
Dr. Aaron Lerner 16 June 2025

When Prime Minister Binyamin Netanyahu held his first top-secret meeting of
his "Iran War Team," the neutralization of the Fordow Fuel Enrichment Plant
(FFEP) was most certainly identified as a necessary condition for success.

Netanyahu didn't fill the room with a bunch of yes-men.

So even if he wanted to (and I genuinely don't think Netanyahu wanted to)
engage in wishful thinking, the independent members of the team wouldn't
abide by assuming that somehow Fordow would work out.

That somehow America would ultimately bomb Fordow with their most powerful
bunker busters.

And that the optimistic estimates that American bunker busters are
sufficient to do the job are correct.

To be clear:

Israel isn't picking targets from a target bank in some kind of tit-for-tat
with Iran.

We are following a schedule.

And somehow that plan does indeed address Fordow.

So it's time for all the retired generals and former intelligence heads now
sharing their wisdom on television panels to have a modicum of modesty.

They are clueless about what the plan is.

So they should think twice before proclaiming that we have no solution for
Fordow and should immediately abandon the operation.

________________________________________
IMRA - Independent Media Review and Analysis

Since 1992 providing news and analysis on the Middle East with a focus on
Arab-Israeli relations

Website: www.imra.org.il

Search For An Article

....................................................................................................

Contact Us

POB 982 Kfar Sava
Tel 972-9-7604719
Fax 972-3-7255730
email:imra@netvision.net.il IMRA is now also on Twitter
http://twitter.com/IMRA_UPDATES

image004.jpg (8687 bytes)