28.08.2013 Views

Adherence to and Compliance with Arms Control, Nonproliferation ...

Adherence to and Compliance with Arms Control, Nonproliferation ...

Adherence to and Compliance with Arms Control, Nonproliferation ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ADHERENCE TO AND COMPLIANCE<br />

WITH<br />

ARMS CONTROL, NONPROLIFERATION<br />

AND<br />

DISARMAMENT AGREEMENTS<br />

AND COMMITMENTS<br />

August 2005<br />

Prepared by the U.S. Department of State


TABLE OF CONTENTS<br />

I. PURPOSE 1<br />

II. SCOPE OF THE REPORT 2<br />

III. OVERVIEW 2<br />

Libyan Renunciation of Weapons of Mass Destruction 3<br />

Nuclear Non-Proliferation Treaty (NPT) 3<br />

Expansion of START <strong>Compliance</strong> Section 4<br />

Chemical Weapons Convention (CWC) 5<br />

Open Skies Treaty 5<br />

IV. ADHERENCE TO AGREEMENTS 5<br />

A. Policy 5<br />

B. U.S.Organizations <strong>and</strong> Programs <strong>to</strong> Evaluate <strong>and</strong> Ensure<br />

Treaty <strong>Compliance</strong> 6<br />

C. Importance of Treaty <strong>and</strong> Commitment Enforcement 6<br />

1. Noncompliance Challenges <strong>and</strong> Required Responses 7<br />

2. Enforcing <strong>Compliance</strong> 8<br />

D. U.S. <strong>Compliance</strong> <strong>with</strong> <strong>Arms</strong> <strong>Control</strong>, <strong>Nonproliferation</strong>, <strong>and</strong><br />

Disarmament Agreements <strong>and</strong> Commitments 8<br />

1. U.S. Institutional <strong>and</strong> Procedural Organization<br />

for Ensuring <strong>Compliance</strong> 8<br />

2. Treaty <strong>Compliance</strong> 9<br />

3. Issues Raised by Other Treaty Parties Concerning U.S. <strong>Compliance</strong><br />

a. The Intermediate-Range Nuclear Forces (INF) Treaty 9<br />

b. The Strategic <strong>Arms</strong> Reduction Treaty (START) 9<br />

V. COMPLIANCE BY SUCCESSORS TO TREATIES AND AGREEMENTS<br />

CONCLUDED BILATERALLY WITH THE SOVIET UNION 10<br />

A. The Intermediate-Range Nuclear Forces (INF) Treaty 10<br />

B. The Strategic <strong>Arms</strong> Reduction Treaty (START) 11<br />

VI. COMPLIANCE OF OTHER NATIONS (INCLUDING SUCCESSORS TO<br />

THE SOVIET UNION) WITH MULTILATERAL AGREEMENTS 15<br />

A. The 1972 Biological <strong>and</strong> Toxin Weapons Convention (BWC) 15<br />

Country Assessments 17<br />

China 17<br />

Cuba 19<br />

Iran 20<br />

Iraq 21<br />

Libya 24<br />

North Korea 26<br />

Russia 27<br />

Syria 31<br />

i


B. The Treaty on Conventional Armed Forces in Europe (CFE) 32<br />

Country Assessments 34<br />

Armenia 34<br />

Azerbaijan 37<br />

Belarus 38<br />

Russia 38<br />

Ukraine 48<br />

Collective Obligations 48<br />

C. The Vienna Documents of 1992, 1994, <strong>and</strong> 1999 49<br />

D. The Chemical Weapons Convention (CWC) 50<br />

Country Assessments 54<br />

China 54<br />

Iran 55<br />

Libya 56<br />

Russia 58<br />

Sudan 61<br />

E. The Nuclear Non-Proliferation Treaty (NPT) 62<br />

Agreement Provisions 63<br />

Country Assessments 70<br />

China 70<br />

Iran 72<br />

Iraq 80<br />

Libya 84<br />

North Korea 87<br />

F. The Treaty on Open Skies 92<br />

Country Assessments 94<br />

Russia 94<br />

Ukraine 97<br />

VII. COMPLIANCE OF OTHER NATIONS (INCLUDING SUCCESSORS<br />

TO THE SOVIET UNION) WITH THEIR INTERNATIONAL COMMITMENTS 99<br />

A. Missile <strong>Nonproliferation</strong> Commitments 99<br />

Missile Technology <strong>Control</strong> Regime 99<br />

Hague Code of Conduct against Ballistic Missile Proliferation 102<br />

Chinese <strong>Nonproliferation</strong> Commitments 103<br />

Other <strong>Nonproliferation</strong> Commitments 105<br />

Country Assessments 105<br />

China 105<br />

Russia 106<br />

ii


ADHERENCE TO AND COMPLIANCE WITH<br />

ARMS CONTROL, NONPROLIFERATION, AND<br />

DISARMAMENT AGREEMENTS AND COMMITMENTS<br />

I. PURPOSE<br />

This Noncompliance Report (NCR) is submitted pursuant <strong>to</strong> Section 403 of the<br />

<strong>Arms</strong> <strong>Control</strong> <strong>and</strong> Disarmament Act, as amended (22 U.S.C. 2593) which requires a<br />

Report by the President on <strong>Adherence</strong> <strong>to</strong> <strong>and</strong> <strong>Compliance</strong> <strong>with</strong> <strong>Arms</strong> <strong>Control</strong>,<br />

<strong>Nonproliferation</strong>, <strong>and</strong> Disarmament Agreements <strong>and</strong> Commitments.<br />

This Report – the August 2005 edition of this Congressionally-m<strong>and</strong>ated report –<br />

reflects the importance the Administration <strong>and</strong> the U.S. Congress place upon compliance<br />

<strong>with</strong> arms control, nonproliferation, <strong>and</strong> disarmament agreements <strong>and</strong> commitments.<br />

Such agreements <strong>and</strong> commitments only serve the national security interests of the<br />

United States if they are fully complied <strong>with</strong>. Other states’ violations of such obligations<br />

can present grave threats <strong>to</strong> our security. For this reason, the United States places a very<br />

high priority upon verifying compliance <strong>with</strong>, <strong>and</strong> detecting violations of, such<br />

agreements <strong>and</strong> commitments – as well as upon ensuring that viola<strong>to</strong>rs promptly return <strong>to</strong><br />

compliance <strong>and</strong> that other would-be viola<strong>to</strong>rs are deterred from breaking their own<br />

promises.<br />

The United States has had some success in helping bring noncompliant countries<br />

back in<strong>to</strong> compliance <strong>with</strong> their agreements <strong>and</strong> commitments, <strong>and</strong> in demonstrating that<br />

their return <strong>to</strong> compliance leads <strong>to</strong> improved relations <strong>with</strong> the United States. However,<br />

other countries have presented significant compliance problems, which are detailed<br />

herein, <strong>and</strong> of which U.S. decision-makers need <strong>to</strong> be aware. Particularly in a post-9/11<br />

world in which there exists a very real threat of weapons of mass destruction (WMD)<br />

being used as weapons of terror, it is vital that the international community take all steps<br />

necessary <strong>to</strong> end noncompliance <strong>with</strong> arms control, nonproliferation, <strong>and</strong> disarmament<br />

agreements <strong>and</strong> commitments <strong>and</strong> ensure that would-be future viola<strong>to</strong>rs are deterred from<br />

taking such a provocative <strong>and</strong> dangerous course. The urgency of these tasks highlights<br />

the importance of the various initiatives President Bush has put forward <strong>to</strong> enhance<br />

compliance enforcement efforts, prevent WMD terrorism, <strong>and</strong> reduce proliferation risks.<br />

This Report contributes <strong>to</strong>ward these goals by highlighting cases of noncompliance or of<br />

compliance concern so that policymakers can focus their attention upon returning<br />

viola<strong>to</strong>rs <strong>to</strong> full compliance as rapidly as possible.<br />

Another key objective of this Report is <strong>to</strong> make it very clear that the United States<br />

takes compliance assessment very seriously, <strong>and</strong> applies only the highest st<strong>and</strong>ards of<br />

analytical rigor in making its compliance findings. This point is not always well<br />

unders<strong>to</strong>od, particularly among countries that themselves may apply less rigorous<br />

approaches, or which may even make “compliance” judgments simply on the basis of<br />

policy likes or dislikes. Now more than ever, it is important that everyone underst<strong>and</strong> the


effort, seriousness, <strong>and</strong> rigor that go in<strong>to</strong> U.S. compliance assessments. The<br />

unprecedented clarity <strong>and</strong> detail provided in this Report are designed <strong>to</strong> set the global<br />

st<strong>and</strong>ard for such work.<br />

II. SCOPE OF THE REPORT<br />

This Report provides an assessment of U.S. adherence <strong>to</strong> obligations undertaken<br />

in arms control, nonproliferation, <strong>and</strong> disarmament agreements as well as an assessment<br />

of the adherence of other nations <strong>to</strong> obligations undertaken in arms control,<br />

nonproliferation, <strong>and</strong> disarmament agreements or commitments, including the Missile<br />

Technology <strong>Control</strong> Regime, <strong>to</strong> which the United States is a participating state.<br />

Pursuant <strong>to</strong> Section 403(a)(6), this version of the Report identifies questions, <strong>to</strong><br />

the maximum extent practicable, that exist <strong>with</strong> respect <strong>to</strong> compliance by other countries<br />

<strong>with</strong> their arms control, nonproliferation, <strong>and</strong> disarmament agreements <strong>and</strong> commitments.<br />

To fulfill this statu<strong>to</strong>ry requirement while at the same time safeguarding sensitive or<br />

special reporting, the unclassified version of the Report may contain less detailed<br />

information about U.S. compliance assessments <strong>and</strong> findings’ judgments. As a result,<br />

this version of the Report presents a relatively brief account of findings <strong>and</strong> the<br />

unclassified information that underlies them. In setting out the United States’ findings in<br />

this version of the Report, we wish <strong>to</strong> emphasize that the findings are based on all<br />

available information, including information that may only be discussed in classified<br />

versions of the Report.<br />

Although the Report primarily reflects activities that occurred from January 1,<br />

2002, through January 1, 2004, every effort has been made <strong>to</strong> include significant<br />

developments that have occurred more recently. Unless otherwise noted, compliance<br />

issues that first came <strong>to</strong> light after that period will be addressed in the NCR due <strong>to</strong><br />

Congress on April 15, 2006.<br />

III. OVERVIEW<br />

The United States has long recognized the importance of reaching the most<br />

rigorous judgments possible as <strong>to</strong> whether parties <strong>to</strong> arms control, nonproliferation, <strong>and</strong><br />

disarmament agreements or commitments are complying <strong>with</strong> the obligations or<br />

commitments they have made. This Report represents the most recent in a series of<br />

Noncompliance Reports issued <strong>to</strong> alert policymakers, Congress, <strong>and</strong> – <strong>with</strong> the<br />

unclassified version of the Noncompliance Report – the public, <strong>to</strong> questions of arms<br />

control, nonproliferation, <strong>and</strong> disarmament noncompliance. All governments that give<br />

their word in this vital area should be held <strong>to</strong> it, <strong>and</strong> the United States is committed not<br />

only <strong>to</strong> holding others <strong>to</strong> a high st<strong>and</strong>ard of compliance but also <strong>to</strong> adhering <strong>to</strong> such a<br />

high st<strong>and</strong>ard itself.<br />

2


The Report, in turn, addresses U.S. compliance, compliance by Russia <strong>and</strong> other<br />

successor states of the Soviet Union <strong>with</strong> treaties <strong>and</strong> agreements concluded bilaterally<br />

<strong>with</strong> the Soviet Union, compliance by other countries that are parties <strong>to</strong> multilateral<br />

agreements <strong>with</strong> the United States, <strong>and</strong> compliance <strong>with</strong> commitments made less<br />

formally but that bear directly upon arms control, nonproliferation, <strong>and</strong>/or disarmament<br />

issues.<br />

Several items of particular importance that have arisen since the last edition of the<br />

Report merit mention.<br />

Libyan Renunciation of Weapons of Mass Destruction<br />

Perhaps the most significant event since the submission of the last<br />

Noncompliance Report in June 2003 is Libya’s his<strong>to</strong>ric undertaking, on December 19,<br />

2003, <strong>to</strong> renounce its pursuit of WMD <strong>and</strong> long-range missiles <strong>and</strong> <strong>to</strong> come back in<strong>to</strong><br />

compliance <strong>with</strong> its obligations under the Nuclear <strong>Nonproliferation</strong> Treaty, as well as <strong>to</strong><br />

join <strong>and</strong> comply <strong>with</strong> the Chemical Weapons Convention <strong>and</strong> begin <strong>to</strong> eliminate its longrange<br />

missiles. In the next Report, the United States will publish a detailed analysis<br />

regarding our efforts <strong>to</strong> assist in Libya fulfill its commitments, <strong>with</strong> specific emphasis<br />

upon our degree of confidence that such WMD programs no longer remain in Libya <strong>and</strong><br />

that its Missile Technology <strong>Control</strong> Regime (MTCR)-class ballistic missiles have been,<br />

or will be, eliminated.<br />

This Report addresses Libya’s previous noncompliance <strong>with</strong> arms control,<br />

nonproliferation, <strong>and</strong> disarmament agreements – e.g., <strong>with</strong> Articles II <strong>and</strong> III of the<br />

Nuclear Non-Proliferation Treaty (NPT) – before Libya renounced its WMD <strong>and</strong> MTCRclass<br />

missile programs <strong>and</strong> provides updates on the unprecedented cooperative WMD<br />

elimination <strong>and</strong> verification effort undertaken by Libya in 2004. Libya’s return <strong>to</strong><br />

compliance will be discussed in more detail in the next edition of the Noncompliance<br />

Report.<br />

Nuclear Non-Proliferation Treaty (NPT)<br />

Another important development – albeit a less salutary one – during the period<br />

since the submission of the last Noncompliance Report has been North Korea’s<br />

<strong>with</strong>drawal from the NPT <strong>and</strong> the large volume of new information available about the<br />

challenge <strong>to</strong> the NPT regime presented by Iran’s long his<strong>to</strong>ry of cl<strong>and</strong>estine nuclear<br />

activity.<br />

The United States has warned publicly for more than ten years that Iran was<br />

engaged in a covert effort <strong>to</strong> develop nuclear weapons, but it was only in 2002 that much<br />

information began <strong>to</strong> appear in public about the Iranian nuclear program. Since that time,<br />

the International A<strong>to</strong>mic Energy Agency (IAEA) has extensively documented much of<br />

the Iranian program, making detailed information available about Iran’s long his<strong>to</strong>ry of<br />

undeclared activity <strong>and</strong> lies <strong>to</strong> the IAEA <strong>and</strong> the rest of the international community.<br />

3


This Report marks the first time that U.S. noncompliance findings have specified<br />

violations of the NPT on an article-by-article basis. Such distinctions are particularly<br />

important in cases such as Iran’s, because of the potentially quite different implications of<br />

Article II <strong>and</strong> Article III noncompliance. A violation of Article III – e.g., a country’s<br />

noncompliance <strong>with</strong> its IAEA Safeguards Agreement – might occur for a variety of<br />

reasons, not all of which are sinister (e.g., simple error). An Article II violation, however<br />

– that is, an effort <strong>to</strong> manufacture or otherwise acquire a nuclear weapon or other nuclear<br />

explosive device, or seeking or receiving any assistance in such manufacture –<br />

necessarily represents a willful subversion of the NPT’s core nonproliferation principles.<br />

For this reason, <strong>and</strong> in keeping <strong>with</strong> the United States’ emphatic commitment <strong>to</strong> rigor <strong>and</strong><br />

clarity in all compliance assessments, this Report sets forth NPT noncompliance findings<br />

<strong>with</strong> greater specificity than in previous reports.<br />

This Report also contains much new information on North Korea’s nuclear<br />

weapons program, <strong>and</strong> its longst<strong>and</strong>ing violation of the NPT prior <strong>to</strong> its <strong>with</strong>drawal from<br />

that Treaty becoming effective in 2003. Recent developments in North Korea have been<br />

particularly significant because of Pyongyang’s admission <strong>to</strong> a U.S. delegation in<br />

Oc<strong>to</strong>ber 2002 that it had been pursuing a cl<strong>and</strong>estine uranium enrichment program, its<br />

resumption of activities at the Yongbyon facility, its announcement of the resumption of<br />

plu<strong>to</strong>nium reprocessing, <strong>and</strong> its shifting admissions <strong>and</strong> denials <strong>with</strong> respect <strong>to</strong> the<br />

plu<strong>to</strong>nium weapons it has already produced. This Report details North Korea’s violations<br />

– through the pursuit of both uranium- <strong>and</strong> additional plu<strong>to</strong>nium-based nuclear weapons –<br />

of its IAEA Safeguards Agreements, Articles II <strong>and</strong> III of the NPT, the 1994 Agreed<br />

Framework, <strong>and</strong> the Joint North-South Declaration on the Denuclearization of the Korean<br />

Peninsula.<br />

Expansion of START <strong>Compliance</strong> Section<br />

Section 403 of the <strong>Arms</strong> <strong>Control</strong> <strong>and</strong> Disarmament Act – the legislative basis for<br />

the submission <strong>to</strong> Congress of this series of Noncompliance Reports – requires that the<br />

Report provide greater specificity about compliance concerns. To wit, the law requires<br />

the Report <strong>to</strong> include “a specific identification, <strong>to</strong> the maximum extent practicable in an<br />

unclassified form, of each <strong>and</strong> every question that exists <strong>with</strong> respect <strong>to</strong> compliance by<br />

other countries <strong>with</strong> arms control, nonproliferation, <strong>and</strong> disarmament agreements <strong>with</strong> the<br />

United States.” To comply <strong>with</strong> this requirement, this edition of the Report has included<br />

more information than ever before on, among other things, Russia’s implementation of<br />

the Strategic <strong>Arms</strong> Reduction Treaty (START).<br />

To facilitate this effort, in 2003 the United States conducted consultations <strong>with</strong><br />

the Russian Government regarding a number of longst<strong>and</strong>ing, unresolved U.S. concerns<br />

about Russian compliance <strong>with</strong> the START Treaty – some of which actually date back <strong>to</strong><br />

the first year of START implementation. These included Russia preventing U.S.<br />

inspec<strong>to</strong>rs from measuring the launch canisters of certain Intercontinental Ballistic<br />

Missiles (ICBMs) or verifying that certain ICBMs do not contain more warheads than<br />

attributed under the Treaty. The U.S. concerns also included Russia failing <strong>to</strong> provide all<br />

4


equired telemetry materials for some START-accountable flight tests, failing properly <strong>to</strong><br />

declare certain ICBM road-mobile launchers accountable under the Treaty, <strong>and</strong> locating<br />

some deployed SS-25 ICBM launchers outside their declared restricted areas. With<br />

respect <strong>to</strong> this last issue, however, it should be noted that Russia has taken steps that have<br />

resolved U.S. compliance concerns.<br />

Chemical Weapons Convention (CWC)<br />

During this reporting period, the United States increased its efforts <strong>to</strong> engage in<br />

compliance-related dialogue <strong>with</strong> States Parties <strong>with</strong> which we continue <strong>to</strong> have<br />

concerns. The bilateral discussions underpin the United States’ effort <strong>to</strong> pursue strict<br />

compliance <strong>with</strong> the CWC <strong>and</strong> resolve questions regarding a State Party’s compliance.<br />

These actions have been taken under the Article IX provisions of the CWC for<br />

Consultations, Cooperation, <strong>and</strong> Fact-Finding. Article IX provides a role for every State<br />

Party <strong>to</strong> participate actively in resolving questions of concern which may cause doubt<br />

about compliance <strong>with</strong> the Convention. For its part, the United States has successfully<br />

used bilateral consultations under Article IX <strong>to</strong> resolve numerous compliance concerns.<br />

The CWC section of this Report addresses our concerns <strong>with</strong> China, Iran, Russia<br />

<strong>and</strong> Sudan, as well as the results of our interactions <strong>with</strong> Libya <strong>to</strong> assist it <strong>with</strong> declaring<br />

<strong>and</strong> eliminating its chemical weapons (CW) program. However, the United States also<br />

has conducted bilateral discussions <strong>with</strong> other States Parties during this reporting period.<br />

These bilateral efforts have been well received <strong>and</strong> useful in laying the groundwork for<br />

judging compliance; as a result, the United States has resolved a number of its CWC<br />

compliance concerns. In this regard, the United States welcomes the actions undertaken<br />

by Albania <strong>to</strong> declare newly discovered chemical weapons, obtain an extension <strong>to</strong> its CW<br />

destruction deadlines, <strong>and</strong> work transparently <strong>and</strong> cooperatively <strong>to</strong> ensure the security<br />

<strong>and</strong> elimination of these chemical weapons s<strong>to</strong>cks. Such actions set a positive precedent<br />

for CWC compliance <strong>and</strong> deserve <strong>to</strong> be commended.<br />

Open Skies Treaty<br />

Finally, it is worth noting that the Open Skies Treaty came in<strong>to</strong> force in January<br />

2002, making this Report the first <strong>to</strong> discuss compliance <strong>with</strong> that Treaty.<br />

IV. ADHERENCE TO AGREEMENTS<br />

A. POLICY<br />

Effective progress by the international community in achieving key arms control,<br />

nonproliferation, <strong>and</strong> disarmament goals requires parties <strong>to</strong> comply fully <strong>with</strong> the<br />

obligations <strong>and</strong> commitments they have undertaken. <strong>Compliance</strong> <strong>with</strong> agreements or<br />

commitments freely negotiated or undertaken by parties is a fundamental corners<strong>to</strong>ne of<br />

U.S. national security policy <strong>and</strong> a bedrock norm of international relations. The rigorous<br />

U.S. approach <strong>to</strong> compliance is deeply rooted in our own legal system <strong>and</strong> fundamental<br />

5


principles <strong>and</strong> values. To that end, the United States is committed <strong>to</strong> adhering <strong>to</strong> the<br />

same high st<strong>and</strong>ard of compliance that it requires of others. In order <strong>to</strong> provide<br />

policymakers <strong>with</strong> information they need <strong>to</strong> fulfill their responsibilities, this Report<br />

identifies not only countries that we assess <strong>to</strong> be violating their obligations or<br />

commitments, but also those about which the United States has developed concerns about<br />

potential noncompliance. Every effort is made clearly <strong>to</strong> distinguish such cases, but it is<br />

important <strong>to</strong> raise both types of issues for attention.<br />

B. U.S. ORGANIZATIONS AND PROGRAMS TO EVALUATE AND<br />

ENSURE TREATY COMPLIANCE<br />

Our deep-seated legal tradition, a commitment <strong>to</strong> U.S. agreements that enhance<br />

our security <strong>and</strong> that of our allies <strong>and</strong> friends, <strong>and</strong> the transparency <strong>and</strong> accountability<br />

that result from our open <strong>and</strong> democratic society, create powerful incentives <strong>to</strong> comply<br />

<strong>with</strong> agreements <strong>to</strong> control nuclear weapons, other weapons of mass destruction, <strong>and</strong><br />

other dangerous technologies. Legal <strong>and</strong> institutional procedures <strong>to</strong> ensure compliance<br />

have been established, <strong>and</strong> specialized compliance-related organs set up <strong>with</strong>in the U.S.<br />

Government by law <strong>and</strong> by longst<strong>and</strong>ing policy; they reflect the seriousness <strong>with</strong> which<br />

these obligations are taken <strong>and</strong> they reinforce these underlying policies <strong>and</strong> principles.<br />

Department of Defense (DoD) compliance review groups, for instance, oversee <strong>and</strong><br />

manage DoD compliance <strong>with</strong> arms control, nonproliferation, <strong>and</strong> disarmament<br />

agreements <strong>and</strong> related commitments. The Verification <strong>and</strong> <strong>Compliance</strong> Analysis<br />

Working Group (VCAWG), an interagency organization, oversees <strong>and</strong> manages analysis<br />

of compliance of other nations <strong>with</strong> arms control, nonproliferation, <strong>and</strong> disarmament<br />

agreements <strong>and</strong> related commitments. In addition, the VCAWG participates actively in<br />

the preparation of this annual report detailing the assessment of both the United States’<br />

<strong>and</strong> other nations’ adherence <strong>to</strong> obligations undertaken in arms control, nonproliferation,<br />

<strong>and</strong> disarmament agreements, <strong>and</strong> related commitments. Moreover, an interagency<br />

review is conducted in appropriate cases, including when other Treaty Parties officially<br />

raise questions regarding U.S. implementation of its obligations. In addition, federal law<br />

m<strong>and</strong>ates the existence, <strong>with</strong>in the U.S. State Department, of the Bureau of Verification<br />

<strong>and</strong> <strong>Compliance</strong>; this bureau is devoted by law <strong>to</strong> detecting <strong>and</strong> assessing noncompliance<br />

<strong>with</strong> such agreements <strong>and</strong> commitments. U.S. law also m<strong>and</strong>ates the production of this<br />

report on compliance <strong>with</strong> arms control, nonproliferation, <strong>and</strong> disarmament agreements<br />

<strong>and</strong> commitments, the compliance findings of which are discussed <strong>and</strong> debated<br />

extensively <strong>with</strong>in the U.S. interagency community <strong>and</strong> then forwarded <strong>to</strong> Congress by<br />

the Secretary of State on behalf of the President. Finally, Congress – which has long<br />

shown a keen interest in compliance matters – performs oversight functions through<br />

committee hearings, budget allocations, <strong>and</strong> a variety of formal <strong>and</strong> informal<br />

investigative means pursuant <strong>to</strong> its powers as a coordinate branch of the U.S. federal<br />

system.<br />

C. IMPORTANCE OF TREATY AND COMMITMENT ENFORCEMENT<br />

The United States uses its assessments of a country’s compliance <strong>with</strong> arms<br />

control, nonproliferation, <strong>and</strong> disarmament agreements <strong>and</strong> commitments as guides <strong>to</strong><br />

6


policymaking. Such agreements <strong>and</strong> commitments cannot serve their purpose of<br />

increasing U.S. <strong>and</strong> international security if countries do not fulfill their obligations or<br />

pledges. Verification, compliance assessment, <strong>and</strong> enforcement are sometimes seen as<br />

separate <strong>and</strong> separable activities, but they are not: all three elements are interrelated, <strong>and</strong><br />

none can have real value <strong>with</strong>out the others. <strong>Compliance</strong> enforcement is an essential<br />

component of the process. Only by making viola<strong>to</strong>rs face consequences for their<br />

violations can they be expected <strong>to</strong> take compliance seriously, <strong>and</strong> only by making<br />

viola<strong>to</strong>rs face such consequences will other would-be viola<strong>to</strong>rs be deterred. Indeed,<br />

<strong>with</strong>out taking steps <strong>to</strong> bring such compliance pressure <strong>to</strong> bear, or <strong>to</strong> counter the threats<br />

posed by noncompliance, there would be little point in trying <strong>to</strong> detect noncompliance in<br />

the first place. The United States works vigorously not just <strong>to</strong> detect noncompliance but<br />

also <strong>to</strong> induce viola<strong>to</strong>rs <strong>to</strong> return <strong>to</strong> compliance. Because all participating states have a<br />

similar security interest in ensuring compliance, we urge other countries <strong>to</strong> do the same.<br />

Though the most immediate responsibilities for compliance enforcement will vary<br />

depending upon the nature of the agreement or commitment in question, all responsible<br />

members of the international community share a common security interest in ensuring<br />

that parties <strong>to</strong> arms control, nonproliferation, <strong>and</strong> disarmament agreements <strong>and</strong><br />

commitments comply <strong>with</strong> their undertakings. A wide range of <strong>to</strong>ols is available for<br />

compliance enforcement purposes, including diplomatic pressure <strong>and</strong> economic<br />

sanctions. The United States supports effective compliance enforcement, <strong>and</strong>, in<br />

furtherance of this goal, seeks <strong>to</strong> build international coalitions <strong>to</strong> exert effective<br />

compliance pressures upon viola<strong>to</strong>rs – either <strong>to</strong> induce a return <strong>to</strong> compliance or <strong>to</strong> thwart<br />

or degrade the advantages the viola<strong>to</strong>r may seek <strong>to</strong> obtain from its noncompliance. The<br />

United States also is prepared <strong>to</strong> employ unilateral measures when necessary <strong>and</strong><br />

appropriate <strong>to</strong> address such noncompliance.<br />

1. NONCOMPLIANCE CHALLENGES AND REQUIRED RESPONSES<br />

Two themes emerged over the past two years as this Report was prepared <strong>and</strong><br />

updated – first, that serious compliance challenges exist, but also that countries can make<br />

the strategic decision <strong>to</strong> come in<strong>to</strong> compliance, particularly if other parties work <strong>to</strong> seek<br />

such a strategic commitment.<br />

There has been a serious failure by two NPT Parties <strong>to</strong> comply <strong>with</strong> the core<br />

nonproliferation undertakings of Articles II <strong>and</strong> III of the Treaty. The United States <strong>and</strong><br />

other like-minded states have been struggling <strong>with</strong> one such case for more than a decade.<br />

North Korea has violated these Articles by its continued development of plu<strong>to</strong>nium<br />

weapons <strong>and</strong> pursuit of uranium ones, <strong>and</strong> it has refused thus far <strong>to</strong> make the strategic<br />

decision <strong>to</strong> accept the complete, verifiable, <strong>and</strong> irreversible dismantlement of its nuclear<br />

program. Another case of Article II <strong>and</strong> III violations has thrust itself upon the attention<br />

of the international community as more <strong>and</strong> more of Iran’s secret nuclear weapons<br />

programs have been exposed <strong>to</strong> public view. Such cases illustrate the challenge of<br />

persuading committed viola<strong>to</strong>rs <strong>to</strong> reverse their violations <strong>and</strong> enforcing full adherence <strong>to</strong><br />

<strong>and</strong> compliance <strong>with</strong> the NPT’s core nonproliferation obligations. Other international<br />

7


arms control <strong>and</strong> nonproliferation regimes or commitments face their own sets of<br />

compliance challenges.<br />

On the other h<strong>and</strong>, the world has observed the emergence of a few remarkable<br />

compliance success s<strong>to</strong>ries. Most significant is Libya’s his<strong>to</strong>ric announcement, on<br />

December 19, 2003, <strong>to</strong> renounce its pursuit of WMD <strong>and</strong> long-range missiles <strong>and</strong> its<br />

implementation of that commitment. Similarly, Albania’s actions <strong>to</strong> declare newly<br />

discovered chemical weapons, obtain an extension <strong>to</strong> its CW destruction deadlines, <strong>and</strong><br />

work transparently <strong>and</strong> cooperatively <strong>to</strong> ensure the security <strong>and</strong> elimination of these<br />

chemical weapons s<strong>to</strong>cks set a positive precedent for CWC compliance <strong>and</strong> deserve <strong>to</strong> be<br />

commended.<br />

2. ENFORCING COMPLIANCE<br />

Even if violations are detected early <strong>and</strong> are quickly unders<strong>to</strong>od as such, an arms<br />

control, nonproliferation or disarmament regime can still be in peril if its members are<br />

unable or unwilling <strong>to</strong> address them as compliance challenges. Detection is only part of<br />

what is needed: violations must have consequences. National governments play a critical<br />

role both in deterring <strong>and</strong> detecting violations, <strong>and</strong> in taking resolute action – individually<br />

<strong>and</strong> collectively – <strong>to</strong> enforce compliance <strong>and</strong> hold viola<strong>to</strong>rs accountable for their actions.<br />

Verification only works when these elements act <strong>to</strong>gether <strong>to</strong> deter, detect, <strong>and</strong> remedy<br />

noncompliance.<br />

D. U.S. COMPLIANCE WITH ARMS CONTROL, NONPROLIFERATION,<br />

AND DISARMAMENT ARGREEMENTS AND COMMITMENTS<br />

1. U.S. INSTITUTIONAL AND PROCEDURAL ORGANIZATION FOR<br />

ENSURING COMPLIANCE<br />

There are three major programs <strong>with</strong>in the U.S. executive branch that operate <strong>to</strong><br />

ensure that U.S. plans <strong>and</strong> programs remain consistent <strong>with</strong> U.S. international obligations.<br />

These procedures include internal Department of Defense (DoD) controls, Department of<br />

Energy (DOE) procedures <strong>and</strong> controls, <strong>and</strong> separate evaluations produced by the<br />

Department of State. These procedures operate in parallel, <strong>and</strong> in addition, <strong>to</strong><br />

congressional oversight.<br />

In 1972, by direction of the President, the DoD established a process <strong>to</strong> ensure<br />

that all DoD programs comply <strong>with</strong> U.S. international obligations. Under this<br />

compliance process (established <strong>with</strong> the SALT I agreements), key offices in DoD are<br />

responsible for overseeing DoD compliance <strong>with</strong> all U.S. arms control, nonproliferation,<br />

<strong>and</strong> disarmament commitments. DoD components ensure that their implementing<br />

program offices adhere <strong>to</strong> DoD compliance directives <strong>and</strong> seek guidance from the offices<br />

charged <strong>with</strong> oversight responsibility. Interagency reviews are also conducted in<br />

appropriate cases, such as when other Treaty Parties formally raise questions regarding<br />

U.S. implementation of its arms control obligations.<br />

8


2. TREATY COMPLIANCE<br />

The United States is in compliance <strong>with</strong> all its obligations under arms control,<br />

nonproliferation, <strong>and</strong> disarmament agreements, <strong>and</strong> continues <strong>to</strong> make every effort <strong>to</strong><br />

comply scrupulously. Because of the breadth <strong>and</strong> intrusiveness of most arms control,<br />

nonproliferation, <strong>and</strong> disarmament regimes <strong>and</strong> their extensive notification <strong>and</strong> data<br />

exchange requirements, the United States has on occasion committed some errors in<br />

meeting our treaty obligations. When our Treaty Partners have raised compliance<br />

questions regarding U.S. implementation activities, the United States has carefully<br />

reviewed the matter <strong>to</strong> determine whether its actions were in compliance <strong>with</strong> its treaty<br />

obligations. When an error has been made, the United States has acknowledged this fact<br />

<strong>to</strong> our Treaty Partners <strong>and</strong> taken steps <strong>to</strong> correct the problem.<br />

3. ISSUES RAISED BY OTHER TREATY PARTIES CONCERNING U.S.<br />

COMPLIANCE<br />

a. THE INTERMEDIATE-RANGE NUCLEAR FORCES (INF) TREATY<br />

The Treaty between the United States of America <strong>and</strong> the Union of Soviet<br />

Socialist Republics on the Elimination of Their Intermediate-Range <strong>and</strong> Shorter-Range<br />

Missiles (INF Treaty) required the elimination of all U.S. <strong>and</strong> Soviet ground-launched<br />

ballistic <strong>and</strong> cruise missiles <strong>with</strong> ranges of between 500 <strong>and</strong> 5,500 kilometers, their<br />

launchers <strong>and</strong> associated support equipment <strong>and</strong> permanently banned the possession,<br />

production, <strong>and</strong> flight-testing of such missiles. The United States <strong>and</strong> the Soviet Union<br />

completed the elimination of all declared INF-prohibited systems in 1991. Inspection<br />

rights under the Treaty ceased at midnight on May 31, 2001.<br />

With the dissolution of the Soviet Union, all 12 former Soviet republics became<br />

Parties <strong>to</strong> the Treaty. The United States, Belarus, Kazakhstan, Russia, <strong>and</strong> Ukraine are<br />

the active participants in the Special Verification Commission (SVC), the implementing<br />

body for the INF Treaty.<br />

Russia has expressed INF compliance concerns related <strong>to</strong> certain procedures used<br />

during past inspections in the United States, <strong>and</strong> <strong>to</strong> the treaty status of specific missiles<br />

<strong>and</strong> a silo test launcher. With regard <strong>to</strong> each of these concerns, the United States has<br />

determined that it is in full compliance <strong>with</strong> the INF Treaty. U.S. officials have<br />

addressed these concerns in great detail in the SVC, through diplomatic channels, <strong>and</strong><br />

meetings at the political level, explaining why U.S. actions are fully consistent <strong>with</strong> the<br />

Treaty.<br />

b. THE STRATEGIC ARMS REDUCTION TREATY (START)<br />

The entry in<strong>to</strong> force of the START Treaty on December 5, 1994, ushered in a<br />

verification regime of unprecedented complexity <strong>and</strong> intrusiveness. In addition <strong>to</strong><br />

verification by national technical means, data notifications, missile flight test telemetry<br />

9


exchanges, <strong>and</strong> other cooperative measures, the Treaty provides for 12 types of on-site<br />

inspections <strong>and</strong> exhibitions, as well as continuous on-site moni<strong>to</strong>ring activities at<br />

specified facilities. As required, the Parties have exchanged updated START<br />

Memor<strong>and</strong>um of Underst<strong>and</strong>ing (MOU) data on a semiannual basis <strong>and</strong> continued <strong>to</strong><br />

exercise their right <strong>to</strong> conduct on-site inspections. During 2002 <strong>and</strong> 2003, the United<br />

States hosted 30 such on-site inspections each year at U.S. facilities.<br />

As might be expected under a verification regime <strong>with</strong> the breadth <strong>and</strong><br />

intrusiveness of START, a number of compliance questions have been raised by our<br />

Treaty Partners. These questions primarily concern procedural issues related <strong>to</strong><br />

inspections, flight tests of submarine-launched ballistic missiles (SLBMs) <strong>and</strong> telemetry,<br />

as well as a few substantive disagreements <strong>with</strong> U.S. equipping <strong>and</strong> positioning of its<br />

heavy bombers <strong>and</strong> the nature of certain intercontinental ballistic missile (ICBM)<br />

launchers. A number of these issues have been resolved in the Joint <strong>Compliance</strong> <strong>and</strong><br />

Inspection Commission (JCIC) <strong>and</strong> through diplomatic channels, while others have been<br />

under active discussion since 1995.<br />

With regard <strong>to</strong> each of these concerns, the United States has determined that it is<br />

in full compliance <strong>with</strong> the START Treaty. U.S. officials have addressed these concerns<br />

in great detail in the JCIC, through diplomatic channels, <strong>and</strong> meetings at the political<br />

level, explaining why U.S. actions are fully consistent <strong>with</strong> the Treaty.<br />

V. COMPLIANCE BY SUCCESSORS TO TREATIES AND<br />

AGREEMENTS CONCLUDED BILATERALLY WITH THE<br />

SOVIET UNION<br />

A. THE INTERMEDIATE-RANGE NUCLEAR FORCES (INF) TREATY<br />

The Treaty between the United States of America <strong>and</strong> the Union of Soviet<br />

Socialist Republics on the Elimination of Their Intermediate-Range <strong>and</strong> Shorter-Range<br />

Missiles (INF Treaty) was signed by U.S. President Ronald Reagan <strong>and</strong> Soviet General<br />

Secretary Mikhail Gorbachev on December 8, 1987, <strong>and</strong> entered in<strong>to</strong> force on June 1,<br />

1988. Elimination of all declared missiles <strong>and</strong> launchers under the Treaty was completed<br />

in 1991.<br />

The Treaty is of unlimited duration, <strong>and</strong> bans the possession, production, <strong>and</strong><br />

flight testing of intermediate- <strong>and</strong> shorter-range missile systems. The Treaty required the<br />

complete elimination of all the approximately 800 U.S. <strong>and</strong> approximately 1,800 former<br />

Soviet ground-launched missiles <strong>with</strong> ranges between 500 <strong>and</strong> 5,500 kilometers, as well<br />

as their launchers <strong>and</strong> associated support equipment <strong>and</strong> structures. All such items were<br />

eliminated by May 28, 1991.<br />

The Treaty established a verification regime using national technical means<br />

(NTM), notifications, <strong>and</strong> an on-site inspection system <strong>to</strong> detect <strong>and</strong> thus help deter<br />

10


violations of Treaty obligations. This inspection regime concluded on May 31, 2001, at<br />

the end of 13 years following the Treaty’s entry in<strong>to</strong> force. All Treaty-related on-site<br />

inspection activities have now ceased. The remainder of the verification regime,<br />

however, continues for the life of the Treaty (i.e., indefinitely).<br />

The United States has identified no INF Treaty compliance issues <strong>with</strong> its Treaty<br />

Partners as of this report. The United States will continue <strong>to</strong> verify compliance <strong>with</strong> the<br />

INF Treaty through NTM for the duration of the Treaty.<br />

UPDATE ON SS-23 MISSILES<br />

In 1990, the United States discovered that the Soviet Union had transferred a<br />

number of SS-23 shorter-range missiles <strong>to</strong> the former German Democratic Republic,<br />

Czechoslovakia, <strong>and</strong> Bulgaria. While this transfer did not violate the INF Treaty since it<br />

occurred prior <strong>to</strong> Treaty signature, the United States had serious compliance concerns<br />

regarding this issue. The nations whose military forces held the SS-23 missiles were not<br />

INF Parties, <strong>and</strong> thus were never legally obligated under the Treaty. As a matter of<br />

policy, the United States has sought the destruction of these missiles in order <strong>to</strong> fulfill the<br />

objectives of the INF Treaty.<br />

Germany <strong>and</strong> the Czech Republic destroyed their SS-23 missiles <strong>and</strong> associated<br />

support equipment during the 1990s.<br />

The Slovak Republic, which gained possession of a number of SS-23 missiles<br />

following the “Velvet Divorce” <strong>with</strong> Czechoslovakia, agreed <strong>to</strong> destroy its missiles <strong>with</strong><br />

financial assistance provided by the Department of State’s <strong>Nonproliferation</strong> <strong>and</strong><br />

Disarmament Fund (NDF). On Oc<strong>to</strong>ber 27, 2000, a team of U.S. observers confirmed<br />

that the Slovak Republic had completed the destruction of its SS-23 missiles <strong>and</strong><br />

associated support equipment.<br />

Bulgaria announced its intention in December 2001 <strong>to</strong> destroy its SS-23 missiles<br />

by Oc<strong>to</strong>ber 2002. The United States offered <strong>to</strong> provide technical <strong>and</strong> financial assistance<br />

under the NDF, which Bulgaria accepted. The destruction of Bulgaria’s SS-23 missiles<br />

began in July 2002. On January 16, 2004, a team of U.S. observers confirmed that<br />

Bulgaria had completed the destruction of its SS-23 missiles <strong>and</strong> associated support<br />

equipment. This issue has now been resolved.<br />

B. THE STRATEGIC ARMS REDUCTION TREATY (START)<br />

Belarus, Kazakhstan, Russia, <strong>and</strong> Ukraine are in compliance <strong>with</strong> the START<br />

strategic offensive arms (SOA) central limits. Both the United States <strong>and</strong> Russia met the<br />

START seven-year reduction final ceilings of 1,600 delivery vehicles <strong>and</strong> 6,000<br />

attributed warheads by the December 4, 2001, deadline. By December 2001, these four<br />

Former Soviet Union (FSU) successor states had reduced their aggregate forces <strong>to</strong> 1,136<br />

deployed launchers, 5,518 deployed warheads, <strong>and</strong> 4,894 deployed ballistic missile<br />

11


warheads, as defined by Article II of the Treaty, <strong>and</strong> all strategic weapons had been<br />

removed or eliminated from the terri<strong>to</strong>ries of Ukraine, Belarus, <strong>and</strong> Kazakhstan.<br />

Additionally, START required the four FSU successor states <strong>to</strong> eliminate at least 154<br />

heavy ICBM (SS-18) silo launchers by December 2001. In the original MOU, dated<br />

September 1, 1990, the Soviet Union declared 308 SS-18 heavy ICBM silo launchers. As<br />

of November 30, 2001, a <strong>to</strong>tal of 158 SS-18 silo launchers had been eliminated – 104 in<br />

Kazakhstan <strong>and</strong> 54 in Russia – leaving a <strong>to</strong>tal of 150 deployed heavy ICBMs.<br />

Not<strong>with</strong>st<strong>and</strong>ing the overall success of START implementation, a significant<br />

number of longst<strong>and</strong>ing compliance issues that have been raised in the START Treaty’s<br />

Joint <strong>Compliance</strong> <strong>and</strong> Inspection Commission (JCIC) remain unresolved. The Parties<br />

continue <strong>to</strong> work through diplomatic channels <strong>and</strong> in the JCIC <strong>to</strong> ensure smooth<br />

implementation of the Treaty <strong>and</strong> effective resolution of compliance issues <strong>and</strong> questions.<br />

The United States raised six new compliance issues during the period of this<br />

report. The United States considers four of these <strong>to</strong> have been closed. However, several<br />

previous – often long-st<strong>and</strong>ing – compliance issues remain unresolved. A number of<br />

these issues, some of which originated as early as the first year of Treaty implementation,<br />

highlight the different interpretations of the Parties about how <strong>to</strong> implement the complex<br />

inspection <strong>and</strong> verification provisions of the START Treaty.<br />

ICBM ISSUES<br />

Inability <strong>to</strong> Confirm during Reentry Vehicle Inspections (RVOSIs) that the<br />

Number of Attributed ICBM Warheads Has Not Been Exceeded. During RVOSIs of<br />

deployed Russian ICBMs, U.S. inspec<strong>to</strong>rs have been hampered, in some cases, from<br />

ascertaining whether the missile had a front section, or that the front section contained no<br />

more reentry vehicles (RVs) than the number of warheads attributed <strong>to</strong> a missile of the<br />

declared type under the Treaty.<br />

The purpose of an RVOSI, as set forth in paragraph 6 of Article XI of the Treaty,<br />

is <strong>to</strong> confirm that a ballistic missile contains no more RVs than the number of warheads<br />

attributed <strong>to</strong> a missile of that type. The RVOSI procedures are referenced in paragraph<br />

16 of Section IX of the Inspection Pro<strong>to</strong>col <strong>and</strong> contained in Annex 3 <strong>to</strong> the Inspection<br />

Pro<strong>to</strong>col. Paragraph 11 of Annex 3 allows the inspected Party <strong>to</strong> cover RVs. Inspec<strong>to</strong>rs<br />

have a right <strong>to</strong> view these covers <strong>and</strong> <strong>to</strong> measure hard covers prior <strong>to</strong> their placement on<br />

the RVs. The covers are then installed on the RVs before the inspec<strong>to</strong>rs view the front<br />

section. Under the Treaty, such covers must not hamper inspec<strong>to</strong>rs in ascertaining that<br />

the front section contains no more RVs than the number of warheads attributed <strong>to</strong> a<br />

missile of that type. Russian RV covers, in some instances, are <strong>to</strong>o large; consequently,<br />

they fail <strong>to</strong> meet this requirement.<br />

During certain RVOSIs, Russia did not demonstrate <strong>to</strong> the satisfaction of the U.S.<br />

inspection team that additional covered objects located on the front section, <strong>and</strong> declared<br />

by Russia not <strong>to</strong> be RVs, were not RVs. Although START does not differentiate between<br />

12


nuclear <strong>and</strong> non-nuclear RVs, Russia’s willingness <strong>to</strong> use radiation detection equipment<br />

(RDE) during such RVOSIs <strong>to</strong> establish that the extra objects were not nuclear has been<br />

useful for resolving some, but not all, U.S. concerns.<br />

FINDING. Russian RV covers, <strong>and</strong> their method of emplacement, have in some<br />

cases hampered U.S. inspec<strong>to</strong>rs from ascertaining that the front section of the missiles<br />

contains no more RVs than the number of warheads attributed <strong>to</strong> a missile of that type<br />

under the Treaty. Russian cooperation in the use of RDE <strong>and</strong> other measures has been<br />

helpful in addressing some, but not all, of the difficulties encountered by U.S. inspec<strong>to</strong>rs.<br />

Russian Road-Mobile Launchers’ “Break-in.” Russia has failed <strong>to</strong> declare<br />

certain road-mobile launchers of ICBMs when they first leave their production facility, as<br />

required by the Treaty. Russia has moved some of these launchers <strong>to</strong> an undeclared<br />

“break-in” area located over 60 miles from the production facility <strong>with</strong>out declaring that<br />

they have left the production facility <strong>and</strong> are accountable under the Treaty.<br />

Pursuant <strong>to</strong> paragraph 6(b) of Article III of the Treaty, a mobile launcher of<br />

ICBMs becomes subject <strong>to</strong> the Treaty limitations when it first leaves a production<br />

facility. Not later than five days following the first exit of such a newly produced nondeployed<br />

road-mobile launcher, <strong>and</strong> its entry in<strong>to</strong> Treaty accountability, Section I of the<br />

Notification Pro<strong>to</strong>col requires the Party producing the new Treaty-accountable item <strong>to</strong><br />

provide a notification of this change in data. Except for transits, Parties are proscribed<br />

from locating non-deployed mobile launchers outside the boundaries of the STARTdeclared<br />

facilities identified in sub-paragraph 9(b) of Article IV of the Treaty.<br />

FINDING. Russia continues <strong>to</strong> violate START provisions relevant <strong>to</strong> these<br />

obligations.<br />

Deployed SS-25 Road-Mobile Launchers Based Outside Their Designated<br />

Restricted Areas. Russia based some deployed SS-25 road-mobile launchers outside<br />

their declared restricted areas (RAs) at two road-mobile ICBM bases while these RAs<br />

were under construction. The United States <strong>and</strong> Russia concluded a temporary, interim<br />

policy arrangement regarding the conduct of inspections <strong>and</strong> cooperative measures at the<br />

facilities where the launchers were housed during the period of construction. This<br />

arrangement permitted U.S. inspec<strong>to</strong>rs <strong>to</strong> conduct data update inspections <strong>and</strong> RVOSIs<br />

that they had not previously been able <strong>to</strong> perform, <strong>and</strong> allowed Russia <strong>to</strong> cooperate fully<br />

<strong>with</strong> providing cooperative measures access for the launchers that were previously<br />

unavailable. All of these road-mobile ICBMs <strong>and</strong> their launchers have since been<br />

transferred from their bases, <strong>and</strong> their declared RAs have been eliminated as START<br />

facilities.<br />

FINDING. Not<strong>with</strong>st<strong>and</strong>ing the interim policy arrangement, Russia’s practice of<br />

locating deployed SS-25 road-mobile launchers outside their declared RAs for long<br />

periods of time constituted basing in a manner that violated the provisions of paragraphs<br />

13


1 <strong>and</strong> 9 of Article VI of the Treaty. This practice has ceased <strong>and</strong> the United States<br />

considers this issue closed.<br />

Denial of the Right <strong>to</strong> Measure Certain Deployed ICBM Launch Canisters<br />

on Mobile Launchers. U.S. inspec<strong>to</strong>rs have been prevented from exercising the Treaty<br />

right <strong>to</strong> measure certain ICBM launch canisters on mobile launchers, both deployed <strong>and</strong><br />

non-deployed, that are encountered during data update inspections <strong>to</strong> confirm data<br />

regarding the type of item of inspection. Russia, for instance, has prevented U.S.<br />

inspec<strong>to</strong>rs from measuring launch canisters for SS-24 ICBMs contained in rail-mobile<br />

launchers that are located <strong>with</strong>in the boundaries of an inspection site. Similar concerns<br />

have arisen <strong>with</strong> regard <strong>to</strong> launch canisters for SS-25 <strong>and</strong> SS-27 mobile ICBMs located<br />

on road-mobile launchers. With regard <strong>to</strong> launch canisters for these latter types, Russia<br />

<strong>and</strong> the United States have agreed upon a policy arrangement <strong>to</strong> address this issue,<br />

though it has not yet been implemented for the SS-27 ICBM.<br />

Subparagraph 20(a) of Section VI of the Inspection Pro<strong>to</strong>col identifies ICBM<br />

launch canisters as one of the items of inspection for data update inspections. In<br />

accordance <strong>with</strong> the procedures in Annex 1 <strong>to</strong> the Inspection Pro<strong>to</strong>col, inspec<strong>to</strong>rs have<br />

the right <strong>to</strong> confirm the number <strong>and</strong>, if applicable, the types of items of inspection that are<br />

specified for the facility <strong>to</strong> be inspected <strong>and</strong> declared for the inspection site, <strong>and</strong> the right<br />

<strong>to</strong> confirm the absence of any other item of inspection at the inspection site. Pursuant <strong>to</strong><br />

paragraph 6 of Annex 1, inspec<strong>to</strong>rs may view <strong>and</strong> measure the dimensions of a launch<br />

canister declared <strong>to</strong> contain an item of inspection <strong>to</strong> confirm it is of the declared type.<br />

FINDING. Russia prevented U.S. inspec<strong>to</strong>rs from exercising their Treaty right <strong>to</strong><br />

measure launch canisters for SS-24 ICBMs contained in rail-mobile launchers that are<br />

located <strong>with</strong>in the boundaries of an inspection site, in contravention of paragraphs 1 <strong>and</strong><br />

6 of Annex 1 <strong>to</strong> the Inspection Pro<strong>to</strong>col. With regard <strong>to</strong> launch canisters for SS-25 <strong>and</strong><br />

SS-27 ICBMs located on road-mobile launchers, the Parties have agreed upon a policy<br />

arrangement <strong>to</strong> address this issue, but it has not yet been implemented for the SS-27<br />

ICBM.<br />

TELEMETRY ISSUES<br />

As part of the START verification regime, the Parties are obligated <strong>to</strong> notify each<br />

other of missile flight tests <strong>and</strong> <strong>to</strong> exchange telemetry tapes, tape summaries, interpretive<br />

data, <strong>and</strong> acceleration profiles for each flight test of a START-accountable ICBM or<br />

SLBM. The United States has raised several concerns regarding Russia’s failure <strong>to</strong><br />

provide all Treaty-required telemetry materials for some START-accountable flight tests<br />

in violation of paragraphs 4 <strong>and</strong> 5 of Article X of the Treaty, <strong>and</strong> paragraph 1 of Section I<br />

<strong>and</strong> paragraphs 1 <strong>and</strong> 2 of Section II of the Telemetry Pro<strong>to</strong>col.<br />

FINDING. Russia has in some instances failed <strong>to</strong> comply <strong>with</strong> Treaty<br />

requirements regarding the provision of telemetry information on missile flight testing<br />

pursuant <strong>to</strong> Article X of the START Treaty <strong>and</strong> Sections I <strong>and</strong> II of the Telemetry<br />

Pro<strong>to</strong>col.<br />

14


VI. COMPLIANCE OF OTHER NATIONS (INCLUDING<br />

SUCCESSORS TO THE SOVIET UNION) WITH<br />

MULTILATERAL AGREEMENTS<br />

A. THE 1972 BIOLOGICAL AND TOXIN WEAPONS CONVENTION (BWC)<br />

As of December 2003, there were 151 States Parties <strong>to</strong> the 1972 Biological <strong>and</strong><br />

Toxin Weapons Convention. An additional 16 countries have signed but have not yet<br />

ratified the agreement, including Syria. This Report addresses the activities of China,<br />

Cuba, Iran, Iraq, Libya, North Korea, Russia (<strong>and</strong> the former Soviet Union) <strong>and</strong> Syria.<br />

This Report examines whether these States Parties are complying <strong>with</strong> the obligations<br />

assumed under the BWC <strong>and</strong> are providing accurate data under agreed BWC Confidence<br />

Building Measures (CBMs). It also addresses the BW-related activities of Syria, which is<br />

a signa<strong>to</strong>ry <strong>to</strong> the Convention. While the United States has concerns regarding the<br />

activities of other countries, the specific cases addressed here are those that have assumed<br />

obligations relevant <strong>to</strong> the BWC <strong>and</strong> for which the most evidence exists of actual or<br />

potential noncompliance.<br />

At the 1986 BWC Review Conference, the States Parties adopted a set of non-<br />

binding CBMs; these were exp<strong>and</strong>ed at the 1991 Review Conference. The States Parties<br />

also agreed that the data called for in these CBMs should be submitted <strong>to</strong> the United<br />

Nations annually (by April 15).<br />

Since adoption of the non-binding CBMs in 1987, some 85 of the 151 BWC<br />

States Parties have submitted at least one declaration. Of those, a small number of States<br />

Parties have made only an initial declaration, instead of annual declarations. Still others<br />

submitted declarations at one time but have not done so recently. Some have simply<br />

submitted a statement that they have nothing <strong>to</strong> declare, or that they are in compliance<br />

<strong>with</strong> the BWC. The lack of participation in the CBMs is a concern <strong>to</strong> the United States.<br />

Data provided by the CBMs has some limited utility for enhancing U.S. underst<strong>and</strong>ing of<br />

foreign biotechnical activities <strong>and</strong> capabilities, <strong>and</strong> CBMs clearly poorly serve their<br />

intended confidence-building purposes when States Parties implement them <strong>with</strong> such<br />

inconsistency <strong>and</strong> lack of transparency.<br />

The Fifth BWC Review Conference suspended its 2001 session <strong>with</strong>out<br />

agreement, <strong>and</strong> resumed in November 2002. At that time, it made a consensus decision<br />

<strong>to</strong> hold a series of annual meetings of States Parties in 2003, 2004, <strong>and</strong> 2005, leading up<br />

<strong>to</strong> the Sixth Review Conference in 2006. Each meeting was <strong>to</strong> be prepared by a meeting<br />

of relevant Experts. Setting aside previous failed attempts <strong>to</strong> use traditional arms control<br />

measures <strong>to</strong> enhance the transparency of biotechnical activities, the States Parties agreed<br />

<strong>to</strong> discuss, <strong>and</strong> promote common underst<strong>and</strong>ing <strong>and</strong> effective action on, a specified set of<br />

<strong>to</strong>pics that – if implemented nationally or through relevant international organizations –<br />

could have practical utility in helping counter the BW threat. This approach is<br />

particularly important in an era in which the capability <strong>to</strong> create <strong>and</strong> employ biological<br />

weapons is spreading beyond state ac<strong>to</strong>rs <strong>to</strong> terrorist groups <strong>and</strong> even individuals. These<br />

15


<strong>to</strong>pics are:<br />

• the adoption of necessary national measures <strong>to</strong> implement the prohibitions set<br />

forth in the Convention, including enactment of penal legislation (2003);<br />

• national mechanisms <strong>to</strong> establish <strong>and</strong> maintain the security <strong>and</strong> oversight of<br />

pathogenic microorganisms <strong>and</strong> <strong>to</strong>xins (2003);<br />

• enhancing international capabilities for responding <strong>to</strong>, investigating, <strong>and</strong><br />

mitigating the effects of cases of alleged use of biological or <strong>to</strong>xin weapons or<br />

suspicious outbreaks of disease (2004);<br />

• strengthening <strong>and</strong> broadening national <strong>and</strong> international institutional efforts <strong>and</strong><br />

existing mechanisms for the surveillance, detection, diagnosis, <strong>and</strong> combating of<br />

infectious disease affecting humans, animals, <strong>and</strong> plants (2004); <strong>and</strong><br />

• the content, promulgation, <strong>and</strong> adoption of codes of conduct for scientists (2005).<br />

The meetings held in 2003 brought experts <strong>to</strong>gether <strong>to</strong> share experiences <strong>and</strong> views, <strong>and</strong><br />

resulted in recommendations for national actions that – if taken – will reinforce the BWC<br />

<strong>and</strong> contribute <strong>to</strong> stemming the BW threat. The United States continues <strong>to</strong> encourage<br />

States Parties <strong>to</strong> follow through on their work program commitments.<br />

There are significant challenges in moni<strong>to</strong>ring <strong>and</strong> verifying compliance <strong>with</strong> the<br />

BWC. Article I, paragraph 1 of the Convention prohibits development, production,<br />

s<strong>to</strong>ckpiling, acquisition, or retention of microbial or other biological agents or <strong>to</strong>xins, of<br />

types <strong>and</strong> in quantities that have no justification for prophylactic, protective, or other<br />

peaceful purposes. Article I, paragraph 2 also prohibits the development, production, or<br />

s<strong>to</strong>ckpiling of weapons, equipment, or means of delivery designed <strong>to</strong> use such agents or<br />

<strong>to</strong>xins for hostile purposes or in armed conflict. The emphasis in Article I upon whether<br />

or not the purposes for which materials or items are possessed are “peaceful” or “hostile”<br />

makes clear that not only the existence, but also the intent of any country’s biological<br />

program, must be part of any compliance determination. Making a judgment about<br />

intent is challenging given the dual-use nature of most biotechnology equipment,<br />

facilities, <strong>and</strong> activities. As <strong>with</strong> other agreements – particularly those involving dual-use<br />

technologies that may be used in a variety of legitimate or illegitimate ways – intent is a<br />

critical element, <strong>and</strong> it may have <strong>to</strong> be inferred from the circumstances, in light of all<br />

available information, if direct evidence is not available.<br />

16


COUNTRY ASSESSMENTS<br />

CHINA<br />

UISSUEU. The United States believes that China continues <strong>to</strong> maintain some<br />

elements of an offensive BW capability. The issue is whether this capability constitutes a<br />

violation of the BWC.<br />

UHISTORY OF COMPLIANCE EVALUATION. U The United States has assessed<br />

the People’s Republic of China’s compliance <strong>with</strong> the BWC as early as June 1992. At<br />

that time, the United States concluded that it was highly probable that China had not<br />

eliminated its BW program since becoming a State Party <strong>to</strong> the BWC in 1984. In the<br />

1994 Report, we indicated that China’s CBM-m<strong>and</strong>ated declarations had not resolved<br />

U.S. concerns about this probable BW program, <strong>and</strong> reported that there were strong<br />

indications that China “probably maintains its offensive program.” In the unclassified<br />

version of the June 2003 Report, the United States concluded more specifically that:<br />

The United States believes that in the years after its accession <strong>to</strong> the BWC,<br />

China was not in compliance <strong>with</strong> its BWC obligations. China continues<br />

<strong>to</strong> maintain some elements of an offensive biological warfare program it is<br />

believed <strong>to</strong> have started in the 1950s.<br />

UDISCUSSION OF OBLIGATIONS. U China deposited its instrument of accession,<br />

<strong>and</strong> thereby became a State Party <strong>to</strong> the BWC on November 15, 1984. Since that point,<br />

China has been obligated <strong>to</strong> comply fully <strong>with</strong> the provisions of the Convention.<br />

UACTIONS.U The United States believes that China began its offensive BW<br />

program in the 1950s <strong>and</strong> continued its program throughout the Cold War, even after<br />

China acceded <strong>to</strong> the BWC in 1984. Undoubtedly China perceived a threat from the BW<br />

programs of its neighbor, the Soviet Union. There are some reports that China may still<br />

retain elements of its biological warfare program. Such reports support the United States’<br />

continued belief that China has not ab<strong>and</strong>oned its offensive BW program.<br />

China has a number of civilian <strong>and</strong> military facilities that could be associated <strong>with</strong><br />

an offensive BW program. For example:<br />

• The Chinese Ministry of Defense’s Academy of Military Medical Sciences<br />

(AMMS) Institute of Microbiology <strong>and</strong> Epidemiology (IME) in Beijing is<br />

acknowledged as a biodefense research facility.<br />

• The Lanzhou Institute of Biological Products (LIBP) has been identified as a<br />

vaccine producer. We believe that LIBP has several BL-3 labora<strong>to</strong>ries <strong>and</strong> dual<br />

use capabilities.<br />

17


From 1993 <strong>to</strong> the present, military scientists have published in open literature the<br />

results of studies of aerosol stability of bacteria, models of infectious virus aerosols, <strong>and</strong><br />

detection of aerosolized viruses using polymerase chain reaction technology. Such<br />

advanced biotechnology techniques could be applicable <strong>to</strong> the development of offensive<br />

BW agents <strong>and</strong> weapons.<br />

Facilities in China that may have legitimate public health <strong>and</strong> commercial uses<br />

could also offer access <strong>to</strong> additional BW-enabling capabilities.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. U.S. concerns<br />

regarding China’s BWC compliance are based on a number of indica<strong>to</strong>rs over a number<br />

of years. First, the United States believes that China possessed an offensive BW program<br />

prior <strong>to</strong> its accession <strong>to</strong> the BWC in 1984. Upon accession, China was obliged <strong>to</strong><br />

eliminate its offensive program, but China never admitted this program <strong>and</strong> the United<br />

States believes that it maintained the program throughout most of the 1980s, at the very<br />

least.<br />

Although China has submitted its voluntary annual BWC CBM data declarations<br />

every year – <strong>and</strong> did so again in 2002 <strong>and</strong> 2003 – we assess that the information<br />

submitted therein continues <strong>to</strong> be inaccurate <strong>and</strong> misleading. BWC CBMs since 1991<br />

have called on the States Parties <strong>to</strong> declare, among other things, their past offensive<br />

activities, which China has not done. On the contrary, China insists it never had such a<br />

program at all. In its Oc<strong>to</strong>ber 17, 2002, announcement on the promulgation of<br />

“Regulations on Export <strong>Control</strong> of Dual-use Biological Agents <strong>and</strong> related Equipment<br />

<strong>and</strong> Technologies,” for instance, China stated that it “has always fulfilled earnestly its<br />

obligations under the Convention” <strong>and</strong> “has never developed, produced or s<strong>to</strong>ckpiled any<br />

biological weapons, <strong>and</strong> never assisted any country <strong>to</strong> acquire or develop these weapons.”<br />

These claims, we believe, are inaccurate.<br />

China’s current research activities <strong>and</strong> dual-use capabilities raise the possibility<br />

that sophisticated BW work could be underway. For example, because of the possible<br />

offensive applications of aerosolization techniques, the United States’ concerns are<br />

underscored by publications indicating military involvement in such research.<br />

FINDING. The United States reaffirms its judgment that China maintains some<br />

elements of an offensive BW capability in violation of its BWC obligations. Despite<br />

China’s BWC CBM declarations <strong>to</strong> the contrary, indications suggest that China<br />

maintained an offensive BW program prior <strong>to</strong> acceding <strong>to</strong> the Convention in 1984.<br />

18


CUBA<br />

ISSUE. Cuba has the technical capability <strong>to</strong> conduct limited offensive BW<br />

research <strong>and</strong> development.<br />

HISTORY OF COMPLIANCE EVALUATION. Prior <strong>to</strong> the June 2003 NCR,<br />

there were no specific discussions of Cuban noncompliance in this Report. The June<br />

2003 NCR finding on Cuba concluded that:<br />

The United States believes that Cuba has at least a limited, developmental<br />

offensive biological warfare research <strong>and</strong> development effort. Such<br />

efforts are prohibited by the BWC.<br />

DISCUSSION OF OBLIGATIONS. Cuba became a party <strong>to</strong> the BWC in 1976.<br />

Since 1991, Cuba has submitted annual declarations pursuant <strong>to</strong> the agreed BWC CBMs.<br />

ACTIONS. Cuba has a highly sophisticated biotechnology industry<br />

encompassing the pharmaceutical, biomedical, vaccine, veterinary, <strong>and</strong> agricultural<br />

sec<strong>to</strong>rs. Cuba has well qualified scientists skilled in microbiology, virology, <strong>and</strong><br />

biochemistry, who collaborate extensively <strong>with</strong> scientists around the world, including<br />

other countries of concern.<br />

Reflecting a very large capital investment, Cuba’s biotechnology industry<br />

includes a full range of modern dual-use facilities for R & D, large-scale production,<br />

down-stream processing, <strong>and</strong> product finishing. Its product inven<strong>to</strong>ry includes vaccines,<br />

research reagents, medical diagnostic supplies, transgenic animals <strong>and</strong> plants, agricultural<br />

materials, <strong>and</strong> various pharmaceuticals supplying over 40 countries. Many of these<br />

products were developed using state-of-the-art recombinant DNA technology <strong>and</strong> reflect<br />

a sophisticated technical capability.<br />

Although Cuba has had a long his<strong>to</strong>ry of medical research, much of the current<br />

infrastructure was developed <strong>with</strong>in the past 20 years such that the Cuban biotechnology<br />

sec<strong>to</strong>r offers low-cost products <strong>and</strong> services throughout the world. Reflecting a very<br />

large capital investment, the biotechnology program owes its genesis <strong>and</strong> ongoing<br />

support <strong>to</strong> Fidel Castro, largely <strong>to</strong> generate revenue <strong>and</strong> as a matter of national prestige.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. As noted above,<br />

the June 2003 NCR finding stated that Cuba likely had “at least a limited, developmental<br />

offensive biological warfare research <strong>and</strong> development effort.”<br />

While it is clear that Cuba’s biotechnology industry could be put <strong>to</strong> offensive BW<br />

uses – <strong>and</strong> that this industry’s extensive international contacts could be a focus of BWrelated<br />

proliferation – the key factual issue is whether or not Cuba has in fact applied its<br />

biotechnology skills <strong>to</strong> offensive BW work.<br />

19


Based on the same body of reporting, there is a split view over whether Cuba<br />

maintains a BW effort. This arises because the body of information available on Cuba is<br />

inconclusive, supporting hypotheses both for <strong>and</strong> against Cuba having an offensive effort.<br />

In a recent National Intelligence Estimate, the Intelligence Community unanimously held<br />

that it was unclear whether Cuba has an active offensive biological warfare effort now, or<br />

even had one in the past. On the basis of the same reporting, the policy community<br />

believes that the compliance judgment of the June 2003 NCR that Cuba has “at least a<br />

limited, developmental offensive BW research <strong>and</strong> development effort” remains correct.<br />

FINDING. Some continue <strong>to</strong> believe that Cuba has at least a limited offensive<br />

biological warfare research <strong>and</strong> development effort <strong>and</strong> that this effort is in violation of<br />

Cuba’s obligations under the Biological <strong>and</strong> Toxin Weapons Convention. Others believe<br />

that it is unclear whether Cuba has an active offensive biological warfare (BW) effort<br />

now, or even had one in the past. However, all judge <strong>with</strong> high confidence that Cuba has<br />

the technical capability <strong>to</strong> pursue some aspects of offensive BW.<br />

The U.S. Government will seek <strong>to</strong> pursue additional information on which <strong>to</strong><br />

assess this issue.<br />

IRAN<br />

ISSUE. Despite being a long-st<strong>and</strong>ing State Party <strong>to</strong> the Biological Weapons<br />

Convention <strong>and</strong> submitting confidence-building measures under the provisions of the<br />

BWC, Iran’s capabilities <strong>and</strong> activities continue <strong>to</strong> raise concerns about the nature of its<br />

BW-related activities.<br />

HISTORY OF COMPLIANCE EVALUATION. In the unclassified version of<br />

the June 2003 Report, the United States concluded that:<br />

The United States judges, based on available evidence, that Iran has an offensive<br />

biological weapons program in violation of the BWC. Iran is technically capable<br />

of producing at least rudimentary biological warheads for a variety of delivery<br />

systems, including missiles.<br />

DISCUSSION OF OBLIGATIONS. Iran is an original state party <strong>to</strong> the BWC; it<br />

ratified the treaty in 1973. Iran submitted CBM data in 1998, 1999, <strong>and</strong> 2002.<br />

ACTIONS. Iran began its offensive BW program in the early 1980s during the<br />

Iran-Iraq war. Hashemi-Rafsanjani – then Acting Comm<strong>and</strong>er in Chief of the Armed<br />

Forces, as well as Speaker of the Majlis – was reported <strong>to</strong> have announced during an<br />

Oc<strong>to</strong>ber 1988 speech: “We should fully equip ourselves both in the offensive <strong>and</strong><br />

defensive use of chemical, bacteriological, <strong>and</strong> radiological weapons. From now on, you<br />

should make use of the opportunity <strong>and</strong> perform this task.” The United States believes<br />

Iran has endeavored <strong>to</strong> follow through on Rafsanjani’s direction in this regard.<br />

20


Iran’s technical base in biotechnology has advanced since the mid-1980s,<br />

providing further expertise that could be – <strong>and</strong> may well be – employed in support of a<br />

BW program. Over the past decade, Iran has also improved its bioproduction capabilities<br />

across the board.<br />

In spite of its growing indigenous manufacturing capability, Iran continues <strong>to</strong><br />

aggressively seek foreign technology, training, <strong>and</strong> expertise <strong>to</strong> advance its biotechnology<br />

industry. Although these relationships are ostensibly for legitimate reasons, Iran could<br />

use them <strong>to</strong> support its BW program.<br />

According <strong>to</strong> open press reporting, Iran is exp<strong>and</strong>ing its biotechnology <strong>and</strong><br />

biomedical industries by building large, state-of-the-art research <strong>and</strong> pharmaceutical<br />

production facilities. These industries could easily hide pilot <strong>to</strong> industrial-scale<br />

production capabilities for a potential BW program, <strong>and</strong> could mask procurement of BWrelated<br />

process equipment.<br />

Iran is technically capable of producing at least rudimentary, bulk-fill biological<br />

warheads for a variety of delivery systems, including missiles.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. The scope <strong>and</strong><br />

nature of Iranian activities demonstrate an exp<strong>and</strong>ing legitimate biotechnology industry,<br />

which could house an offensive biological weapons program. Particularly in light of<br />

Iran’s approach <strong>to</strong>wards compliance <strong>with</strong> its nuclear <strong>and</strong> chemical weapons-related<br />

nonproliferation obligations (see below), available information about Iranian activities<br />

indicates a maturing offensive program <strong>with</strong> a rapidly evolving capability that may soon<br />

include the ability <strong>to</strong> deliver these weapons by a variety of means.<br />

The Iranian BW program has been embedded <strong>with</strong>in Iran’s extensive<br />

biotechnology <strong>and</strong> pharmaceutical industries so as <strong>to</strong> obscure its activities. The Iranian<br />

military has used medical, education, <strong>and</strong> scientific research organizations for many<br />

aspects of BW-related agent procurement, research, <strong>and</strong> development. Iran has also<br />

failed <strong>to</strong> submit the data declarations called for in the BWC CBMs.<br />

FINDING. The United States judges that, based on all available information, Iran<br />

has an offensive biological weapons program in violation of the BWC.<br />

IRAQ<br />

ISSUE. During Saddam Hussein’s regime prior <strong>to</strong> 1991, Iraq engaged in<br />

activities that raised concerns regarding Iraq’s compliance <strong>with</strong> its BWC obligations <strong>and</strong><br />

its adherence <strong>to</strong> UN Security Council resolutions.<br />

HISTORY OF COMPLIANCE EVALUATION. In the early 1990s, the United<br />

States judged that Iraq had developed <strong>and</strong> produced biological warfare agents <strong>and</strong><br />

weapons <strong>and</strong> had likely s<strong>to</strong>ckpiled them. This assessment noted that inspections,<br />

21


conducted after the end of the first Gulf War under the auspices of the United Nations,<br />

were not able <strong>to</strong> provide any support for Iraq’s uncorroborated claims that it had<br />

performed only basic BW research. However, following the 1995 defection of General<br />

Hussein Kamel Hassan, Iraq then presented the UN Special Commission (UNSCOM)<br />

<strong>with</strong> dramatically new information on its past biological warfare program, including<br />

details concerning agent production, weaponization, <strong>and</strong> sites. We then expressed the<br />

belief that Iraq was capable of producing biological warfare agents <strong>and</strong> was probably<br />

intent on continuing its offensive BW program if the threat of UNSCOM inspections <strong>and</strong><br />

long-term moni<strong>to</strong>ring were removed.<br />

The United States declared its suspicions that “Iraq may not be in compliance<br />

<strong>with</strong> the BWC” as early as CY1996 Report; however, we could not formally assess Iraq’s<br />

compliance until we completed our review of Iraq’s “Full, Final, <strong>and</strong> Complete<br />

Declaration.” In that Report, however, we noted that “though the recent Iraqi disclosures<br />

have been substantial, we believe that Iraq has not yet presented all details of its offensive<br />

BW program.”<br />

This judgment remained unchanged until the CY1999 Report (dated Oc<strong>to</strong>ber 1,<br />

2000). In the CY1999 NCR, we noted that there had been no UNSCOM weapons<br />

inspections or moni<strong>to</strong>ring since December 1998. In the June 2003 Report, the United<br />

States concluded that:<br />

The United States judges that Iraq has biological weapons <strong>and</strong> a<br />

significant offensive biological weapons program in violation of its<br />

obligations under the BWC. After signing the BWC in 1972, Iraq<br />

developed, produced, <strong>and</strong> s<strong>to</strong>ckpiled biological warfare agents <strong>and</strong><br />

weapons <strong>and</strong> continued this activity after ratifying the BWC in 1991.<br />

Since inspections ended in 1998, Iraq has invested more heavily in<br />

biological weapons. Iraq has rebuilt its biological infrastructure under the<br />

cover of civilian production. Iraq has established large-scale, redundant,<br />

<strong>and</strong> concealed BW agent production capabilities based on mobile<br />

facilities. The Iraqi Government’s determination <strong>to</strong> hold on<strong>to</strong> a sizable<br />

remnant of its WMD arsenal, agents, equipment, <strong>and</strong> expertise has led <strong>to</strong><br />

years of dissembling <strong>and</strong> obstruction of UNSCOM inspec<strong>to</strong>rs.<br />

DISCUSSION OF OBLIGATIONS. Iraq signed the BWC in 1972. As required<br />

under UN Security Council Resolution 687, Iraq ratified the BWC in April 1991, thereby<br />

obligating it, pursuant <strong>to</strong> paragraph 1 of Article I of the BWC, <strong>to</strong> destroy or divert <strong>to</strong><br />

peaceful purposes all agents, <strong>to</strong>xins, weapons, equipment, <strong>and</strong> delivery means in its<br />

possession or under its jurisdiction or control <strong>and</strong> not <strong>to</strong> develop, produce, s<strong>to</strong>ckpile, or<br />

otherwise acquire or retain biological agents or <strong>to</strong>xins “of types <strong>and</strong> in quantities that<br />

have no justification for prophylactic, protective or other peaceful purposes.” Iraq was<br />

also required, pursuant <strong>to</strong> paragraph 2 of Article I of the BWC, <strong>to</strong> give up all weapons<br />

<strong>and</strong> means of delivery designed <strong>to</strong> use such agents or <strong>to</strong>xins for hostile purposes or in<br />

armed conflict.<br />

22


ACTIONS. Until July 1995, Iraq claimed that it had met its obligations under the<br />

BWC. As noted above, however, after the August 1995 defection of General Hussein<br />

Kamel Hassan <strong>to</strong> Jordan, Iraq presented UNSCOM <strong>with</strong> dramatically new information on<br />

its past biological warfare program, including details concerning agent production,<br />

weaponization, <strong>and</strong> sites. Nevertheless, Iraq’s accounts of weapon development <strong>and</strong><br />

deployment remained incomplete, as did its accounts of overall military doctrine <strong>and</strong><br />

concepts of use. By end of 2002, the UN had not yet received documentation or other<br />

evidence from Iraq that corroborated: (1) the majority of the information contained in<br />

Iraq’s Full, Final, <strong>and</strong> Complete Declaration; (2) Iraqi claims that all BW agents <strong>and</strong><br />

weapons have been unilaterally destroyed; <strong>and</strong> (3) Iraqi claims that its BW program has<br />

been completely dismantled. On December 7, 2002, Iraq presented <strong>to</strong> the UN<br />

Moni<strong>to</strong>ring, Verification, <strong>and</strong> Inspection Commission (UNMOVIC) a “Currently<br />

Accurate Full <strong>and</strong> complete Declaration” for its BW program, but this contained little<br />

new information <strong>to</strong> answer the remaining questions about the program. In violation of its<br />

obligations under UN Security Council resolutions, Iraq did not permit any inspections or<br />

provide any new information <strong>to</strong> the UN from December 1998 until September 2002. In<br />

UNSCR 1441, adopted November 8, 2002, the Security Council declared that “Iraq has<br />

been <strong>and</strong> remains in material breach of its obligations under relevant resolutions ….”<br />

Iraq agreed <strong>to</strong> renewed UN inspections under UNMOVIC in November 2002, <strong>and</strong><br />

UNMOVIC <strong>and</strong> IAEA issued daily inspections reports from November 27, 2002 <strong>to</strong><br />

March 13, 2003. During this time UNMOVIC collected over 100 biological samples for<br />

analysis <strong>and</strong> found them all consistent <strong>with</strong> Iraq’s declarations.<br />

Prior <strong>to</strong> Operation Iraqi Freedom (OIF), which <strong>to</strong>ok place between March 20 <strong>and</strong><br />

May 1, 2003, Iraq was legally bound by the BWC <strong>and</strong> a series of UN Security Council<br />

Resolutions obligating it <strong>to</strong> declare <strong>and</strong> destroy its WMD s<strong>to</strong>ckpiles <strong>and</strong> capabilities. The<br />

passage of UNSCR 1483 in May 2003 reaffirmed that Iraq must meet these disarmament<br />

obligations, <strong>and</strong> asked the United States <strong>and</strong> United Kingdom <strong>to</strong> keep the Council<br />

informed of U.S./UK activities in this regard. In June 2003, the Iraq Survey Group<br />

(ISG), composed of largely military experts from some coalition countries, began <strong>to</strong><br />

conduct WMD/missile search <strong>and</strong> analysis operations.<br />

On Oc<strong>to</strong>ber 2, 2003, the then-head of the ISG, Dr. David Kay, submitted his<br />

Interim Progress Report on the Activities of the Iraq Survey Group <strong>to</strong> the Senate<br />

Committee on Intelligence (SSCI) <strong>and</strong> the House Permanent Select Committee on<br />

Intelligence (HPSCI). Dr. Kay reported that Saddam Hussein had not given up his<br />

aspirations <strong>and</strong> intentions <strong>to</strong> continue work on offensive BW capabilities, <strong>and</strong> that the<br />

Ba’athist Iraqi Government had intended <strong>to</strong> resume WMD-related activities as soon as<br />

external restrictions (e.g., international sanctions, coalition “no-fly” patrols, <strong>and</strong> UN<br />

inspections) were removed.<br />

In September 2004, Charles Duelfer issued a comprehensive report <strong>to</strong> the Direc<strong>to</strong>r<br />

of Central Intelligence on Iraq’s WMD. The report notes that Saddam continued <strong>to</strong> see<br />

the utility of WMD. He explained that Saddam purposely gave an ambiguous impression<br />

23


about possession as a deterrent <strong>to</strong> Iran. The Iraq Survey Group (ISG) found no direct<br />

evidence that Iraq, after 1996 (including the reporting period of this report), had plans for<br />

a new BW program or was conducting BW-specific work for military purposes. The<br />

Duelfer report judges that in 1991 <strong>and</strong> 1992, Iraq appears <strong>to</strong> have destroyed its<br />

undeclared s<strong>to</strong>cks of BW weapons <strong>and</strong> probably destroyed remaining holdings of bulk<br />

BW agent. However, the ISG lacked evidence <strong>to</strong> document complete destruction. The<br />

Baa’thist Iraqi Government retained some BW-related seed s<strong>to</strong>cks until their discovery<br />

after OIF.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. The United States<br />

finds that Iraq, during the course of the Saddam Hussein regime, was in violation of its<br />

obligations under the BWC. After signing the BWC in 1972, Iraq developed, produced,<br />

<strong>and</strong> s<strong>to</strong>ckpiled biological warfare agents <strong>and</strong> weapons <strong>and</strong> continued this activity even<br />

after ratifying the BWC in 1991. Despite an Iraqi obligation under UN Security Council<br />

resolutions adopted after the Gulf War <strong>to</strong> fully disclose <strong>and</strong> destroy its BW program,<br />

UNSCOM reported <strong>and</strong> the United States agrees that Iraq has concealed many details of<br />

its offensive biological warfare program <strong>and</strong> has engaged in a repeated pattern of<br />

obstruction, denial, <strong>and</strong> evasion. After UNSCOM weapons inspections <strong>and</strong> moni<strong>to</strong>ring in<br />

Iraq ceased in December 1998, its successor, UNMOVIC, resumed on-site activities in<br />

Iraq but it never received full <strong>and</strong> active cooperation by Iraq. Iraq’s Declaration of<br />

December 7, 2002, failed <strong>to</strong> provide any new information or answer remaining questions<br />

about its BW program. Although the ISG found no direct evidence that Saddam’s<br />

regime, after 1996, had plans for a new offensive BW program or was conducting BWspecific<br />

work for military purposes, it did retain some BW-related seed s<strong>to</strong>cks until their<br />

discovery after OIF.<br />

FINDING. The United States finds that Iraq, during Saddam Hussein’s regime,<br />

pursued an active offensive BW development program <strong>and</strong> that various aspects of this<br />

program violated its obligations under the BWC. The United States has further<br />

determined that during this period Iraq was in violation of its obligation under UN<br />

Security Council resolutions <strong>to</strong> declare <strong>and</strong> destroy its prohibited WMD <strong>and</strong> long-range<br />

missile programs <strong>and</strong> <strong>to</strong> cooperate fully <strong>with</strong> UN <strong>and</strong> IAEA inspections <strong>and</strong> moni<strong>to</strong>ring.<br />

LIBYA<br />

ISSUE. In the wake of Libyan leader Col. Muammar Qadhafi’s pledge on<br />

December 19, 2003 <strong>to</strong> forswear all weapons of mass destruction programs, U.S.<br />

representatives continue <strong>to</strong> work <strong>to</strong> determine the extent <strong>to</strong> which Libya’s BW-related<br />

activities progressed prior <strong>to</strong> the Libyan commitment, <strong>and</strong> thus the extent <strong>to</strong> which Libya<br />

was compliant <strong>with</strong> the BWC.<br />

HISTORY OF COMPLIANCE EVALUATION. The United States assessed<br />

Libyan compliance <strong>with</strong> the BWC as early as June 1992. In that initial assessment, we<br />

concluded that Libya had the technical manpower <strong>and</strong> knowledge <strong>to</strong> produce small<br />

quantities of warfare agents <strong>and</strong> an interest in obtaining dual-use biological equipment,<br />

24


ut that there was insufficient evidence <strong>to</strong> determine whether Libya had “developed,<br />

produced, weaponized or s<strong>to</strong>ckpiled BW agents for hostile purposes.” The CY1993<br />

through CY2000 Reports reached similar conclusions, noting in CY1994 Libya’s<br />

progress in “seeking <strong>to</strong> move their research program in<strong>to</strong> a program of weaponized BW<br />

agents.” In the June 2003 Report, however, the United States concluded that “[e]vidence<br />

indicates that Libya has the expertise <strong>to</strong> produce small quantities of biological equipment<br />

for its BW program <strong>and</strong> that the Libyan Government is seeking <strong>to</strong> move its research<br />

program in<strong>to</strong> a program of weaponized BW agents. The United States judges that Libya<br />

is in probable violation of its obligations under the BWC.”<br />

DISCUSSION OF OBLIGATIONS. On 19 December 2003, Col. Muammar<br />

Qadhafi pledged <strong>to</strong> eliminate material <strong>and</strong> equipment that might lead <strong>to</strong> the production of<br />

internationally proscribed weapons, <strong>and</strong> confirmed that Libya would be bound by its<br />

obligations under the Biological Weapons Convention, <strong>to</strong> which it acceded in January<br />

1982. Libya has never submitted annual CBM declarations. As part of its December<br />

2003 WMD commitment, Libya has stated its intent <strong>to</strong> submit BWC CBMs, perhaps<br />

<strong>with</strong>in the year, <strong>to</strong> satisfy its promise <strong>to</strong> abide by the BWC.<br />

ACTIONS. As noted, in mid-December 2003, Libya publicly announced its<br />

intention <strong>to</strong> eliminate all internationally proscribed weapons programs, <strong>and</strong> affirmed that<br />

it would comply <strong>with</strong> its obligations under the Biological Weapons Convention.<br />

Since 1999, Libyan dicta<strong>to</strong>r Qadhafi invested the equivalent of millions of U.S.<br />

dollars in Libya’s biotechnology infrastructure. Tripoli has also centralized all<br />

biotechnology research efforts under the Libyan Academy of Sciences umbrella, an<br />

organization headed by Professor Ma’tuq Mohammed Ma’tuq. The Libyan<br />

biotechnological infrastructure continued <strong>to</strong> see significant growth in 2002.<br />

Prior <strong>to</strong> the Libyan disclosures in 2003, the United States had assessed that Libya<br />

had the expertise <strong>to</strong> produce small quantities of biological equipment for its BW program,<br />

<strong>and</strong> that information suggested that Libya was seeking <strong>to</strong> acquire the capability <strong>to</strong><br />

develop <strong>and</strong> produce BW agents for offensive purposes. Such development or<br />

production would have violated key provisions of the BWC.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. We judge that<br />

Libya had an offensive BW program prior <strong>to</strong> December 2003, but that this program had<br />

not progressed beyond the R&D stage.<br />

FINDING. Libya’s efforts over time result in an assessment that it had an active,<br />

developmental offensive BW program in the past that was in violation of Libya’s<br />

obligations under the BWC. While questions remain regarding the past offensive<br />

program – questions the Government of Libya has committed <strong>to</strong> help resolve – the United<br />

States judges that there is no longer an offensive biological weapons program.<br />

25


NORTH KOREA<br />

ISSUE. We continue <strong>to</strong> have serious concerns about the nature of North Korea’s<br />

BW-related activities.<br />

HISTORY OF COMPLIANCE EVALUATION. In the June 2003 Report, the<br />

United States concluded that:<br />

The United States believes North Korea has a dedicated, national-level<br />

effort <strong>to</strong> achieve a BW capability <strong>and</strong> that it has developed <strong>and</strong> produced,<br />

<strong>and</strong> may have weaponized for use, BW agents in violation of the<br />

Convention. North Korea likely has the capability <strong>to</strong> produce sufficient<br />

quantities of biological agents for military purposes <strong>with</strong>in weeks of a<br />

decision <strong>to</strong> do so.<br />

DISCUSSION OF OBLIGATIONS. North Korea became a State Party <strong>to</strong> the<br />

BWC in March 1987. North Korea’s only BWC data submission pursuant <strong>to</strong> the BWC<br />

Confidence-Building Measures was in 1990. That submission asserted that North Korea<br />

had nothing <strong>to</strong> declare.<br />

ACTIONS. Available information suggests that North Korea has a mature<br />

offensive BW program, <strong>and</strong> that it may consider the use of biological weapons as an<br />

option in any future conflict. Its BW program probably includes Bacillus anthracis,<br />

Vibrio cholerae, <strong>and</strong> possibly other agents or <strong>to</strong>xins.<br />

North Korea has pursued biological warfare capabilities since the 1960s <strong>and</strong><br />

continued its program despite having become a State Party <strong>to</strong> the BWC in 1987. In the<br />

past several years, North Korea has focused on building its biotechnology infrastructure<br />

some of which could be exploited for BW purposes.<br />

We assess that North Korea has developed <strong>and</strong> possesses a number of organisms<br />

that could be used as BW agents, including anthrax, plague, <strong>and</strong> cholera. Infectious<br />

diseases remain a serious problem in North Korea, <strong>and</strong> for the most part its vaccine<br />

program is consistent <strong>with</strong> current public health concerns. Nevertheless, North Korea is<br />

believed <strong>to</strong> possess a munitions-production infrastructure that would allow it <strong>to</strong><br />

weaponize biological warfare agents, <strong>and</strong> may have such biological weapons available<br />

for use.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. We judge that<br />

North Korea possesses a number of organisms that could be used as BW agents,<br />

including anthrax, plague, <strong>and</strong> cholera.<br />

North Korea made its only CBM declaration — a “null declaration” stating<br />

essentially that it had nothing <strong>to</strong> declare — in 1990 <strong>and</strong> claimed <strong>to</strong> be in full compliance.<br />

The United States continues <strong>to</strong> believe that this declaration is false.<br />

26


FINDING. The United States believes North Korea has a dedicated, nationallevel<br />

effort <strong>to</strong> develop a BW capability <strong>and</strong> has developed, produced, <strong>and</strong> may have<br />

weaponized for use, BW agents in violation of the BWC. North Korea probably has the<br />

capability <strong>to</strong> produce sufficient quantities of biological agents for military purposes<br />

<strong>with</strong>in weeks of a decision <strong>to</strong> do so.<br />

RUSSIA<br />

ISSUE. The United States is concerned that Russia maintains a mature offensive<br />

BW program.<br />

HISTORY OF COMPLIANCE EVALUATION. In January 1984, then-President<br />

Ronald Reagan reported <strong>to</strong> Congress that the Soviet Union was maintaining an offensive<br />

biological warfare program <strong>and</strong> capabilities <strong>and</strong> that the Soviet Union had repeatedly<br />

violated its legal obligations under the BWC. The former Soviet Union’s offensive<br />

biological warfare program, in fact, was the world’s largest <strong>and</strong> consisted of both military<br />

facilities <strong>and</strong> civilian research <strong>and</strong> development institutes. Following the collapse of the<br />

Soviet Union, the Russian Government publicly committed <strong>to</strong> ending the former Soviet<br />

BW program; it claims <strong>to</strong> have done so in 1992. Nevertheless, serious concerns remain<br />

about Russia’s offensive biological warfare capabilities <strong>and</strong> about the status of some<br />

elements of the offensive BW capability inherited from the former Soviet Union (FSU).<br />

U.S. assessments in recent years have continued <strong>to</strong> cite these concerns, highlighting the<br />

apparent tension between what appears <strong>to</strong> be the commitment of key members of the<br />

Russian leadership <strong>to</strong> resolve BWC issues, <strong>and</strong> the continued involvement of veterans of<br />

the Soviet offensive program in both BWC-related meetings <strong>and</strong> in what Russia describes<br />

as its defensive BW program. In the unclassified June 2003 Report, the United States<br />

concluded that: “[t]he United States judges, based on available evidence, that Russia<br />

continues <strong>to</strong> maintain an offensive BW program in violation of the BWC. ”<br />

DISCUSSION OF OBLIGATIONS. The Soviet Union, the United Kingdom, <strong>and</strong><br />

the United States, as the three deposi<strong>to</strong>ry governments for the BWC, all deposited their<br />

Instruments of Ratification on March 26, 1975. Russia has assumed BWC successor<br />

status from the Soviet Union <strong>and</strong> therefore is bound <strong>to</strong> comply fully <strong>with</strong> the obligations<br />

contained therein.<br />

Even though the Soviet Union, <strong>and</strong> now Russia, regularly submitted annual<br />

CBMs, including in 2003, these submissions continue <strong>to</strong> be incomplete <strong>and</strong> misleading.<br />

ACTIONS. The United States continues <strong>to</strong> assess that Russia maintains a mature<br />

offensive BW program <strong>and</strong> that its nature <strong>and</strong> status have not changed. Russia’s BW<br />

program builds on capabilities <strong>and</strong> expertise inherited from the far more extensive Soviet<br />

BW program that dates back <strong>to</strong> the 1920s. Since the Soviet era, elements of that former<br />

Soviet BW program have been subject <strong>to</strong> varying degrees of downsizing <strong>and</strong><br />

restructuring. There have also been severe cuts in funding <strong>and</strong> personnel at some key<br />

BW facilities. However, some key components of the former Soviet program may<br />

27


emain largely intact <strong>and</strong> may support a mobilization capability for the production of<br />

biological agents <strong>and</strong> delivery systems. The United States continues <strong>to</strong> receive<br />

unconfirmed reports of some ongoing offensive biological warfare activities, <strong>and</strong> key<br />

officials from the Soviet offensive BW program continue <strong>to</strong> occupy influential positions.<br />

A substantial amount of dual-use research conducted in recent years has<br />

legitimate biodefense applicability, but also could be used <strong>to</strong> further an offensive<br />

program. For example,<br />

• In 2001, the former BW entity Vek<strong>to</strong>r proposed work through the International<br />

Science <strong>and</strong> Technology Center (ISTC) <strong>to</strong> examine Ebola vaccines using<br />

nanoemulsions. Although such work has clear biodefense applicability, it also<br />

could be used for offensive purposes.<br />

• Scientists from the Ministry of Defense’s (MOD) Scientific Research Institute of<br />

Microbiology in Kirov published an article, in August 2001, concerning antibiotic<br />

treatment of bubonic plague in primates.<br />

• Researchers at Vek<strong>to</strong>r in 2002 published an article on genetic manipulation of the<br />

Marburg virus.<br />

• Researchers at the Volgograd Anti-Plague Institute published work in 2002 on<br />

Burkholderia pseudomallei – the causative agent of melioidosis – that attempted<br />

<strong>to</strong> explain through genetic engineering the difference between this organism <strong>and</strong><br />

related ones.<br />

The United States also assesses that Russia has the capability <strong>to</strong> mobilize BW<br />

production.<br />

Since the demise of the Soviet Union in 1991, there has been a pronounced lack<br />

of openness <strong>and</strong> c<strong>and</strong>or about the past offensive biological weapons program. Russia<br />

regularly submits its annual BWC CBM declarations <strong>to</strong> the United Nations, including in<br />

2003, but these declarations are assessed <strong>to</strong> be only partially complete, <strong>and</strong> <strong>to</strong> include<br />

misleading information.<br />

The Soviet Government refused <strong>to</strong> admit the existence of its large <strong>and</strong> elaborate<br />

offensive BW program, despite repeated U.S. <strong>and</strong> UK inquiries <strong>and</strong> demarches. In April<br />

1992, after the demise of the Soviet Union, then-President Boris Yeltsin issued a decree<br />

prohibiting all activities that contravene the BWC.<br />

In September 1992, the United States, United Kingdom, <strong>and</strong> Russia agreed on a<br />

Trilateral Process <strong>to</strong> create confidence that Russia had terminated all illegal biological<br />

weapons activity. While there was progress <strong>to</strong>wards achieving the openness intended in<br />

the Joint Statement (which calls for a series of confidence-building visits <strong>and</strong> information<br />

exchanges), not all U.S. concerns were resolved. The Trilateral Process broke down in<br />

28


the mid-1990s <strong>with</strong>out resolving U.S. <strong>and</strong> UK concerns regarding Russia’s compliance<br />

<strong>with</strong> the BWC. In June 2000, Russian President Vladimir Putin reiterated Russia’s<br />

adherence <strong>to</strong> the Convention. In April 2001, the Duma removed Russia’s reservations <strong>to</strong><br />

the 1925 Geneva Pro<strong>to</strong>col that allowed for Russia’s retalia<strong>to</strong>ry use of biological weapons<br />

– thereby eliminating an inconsistency <strong>with</strong> its BWC obligations.<br />

The U.S.-funded Cooperative Threat Reduction (CTR) <strong>and</strong> International Science<br />

<strong>and</strong> Technology Center (ISTC) programs continue <strong>to</strong> have access <strong>to</strong> several civilian<br />

facilities formerly involved in the Soviet offensive BW program. This transparency has<br />

lessened, but not eliminated our concerns that these civilian facilities are directly<br />

involved in an ongoing, offensive BW program.<br />

In 2002 <strong>and</strong> 2003, for instance, the United States was unable <strong>to</strong> certify, under the<br />

Cooperative Threat Reduction Act <strong>and</strong> Title V of the Freedom Support Act (FSA),<br />

Russia’s commitment <strong>to</strong> comply <strong>with</strong> the Biological (<strong>and</strong> Chemical) Weapons<br />

Conventions, explaining U.S. concerns as follows:<br />

... Russia continues an offensive BW program, although it is much smaller<br />

than the massive Soviet BW program. Research activities <strong>with</strong> potential<br />

offensive applications are ongoing at certain facilities known <strong>to</strong> have been<br />

involved in offensive BW work during the Soviet era. Some civilian<br />

facilities previously-associated <strong>with</strong> the Soviet offensive BW program<br />

have been subject <strong>to</strong> varying degrees of modification <strong>and</strong> equipment<br />

removal, <strong>and</strong> U.S. assistance has facilitated access <strong>to</strong> some of these<br />

civilian facilities, although many retain a capability <strong>to</strong> engage in offensive<br />

activity. Many key officials from the former Soviet offensive BW program<br />

continue <strong>to</strong> occupy influential positions. Funding for possible offensive<br />

BW activities at certain military sites has continued. Because the Ministry<br />

of Defense facilities remain closed <strong>to</strong> the West, the nature of Russian<br />

activities there remains uncertain.<br />

Russia’s Pathogen Biodefense Initiative, publicly initiated in 1999,<br />

is ostensibly aimed at providing a unified government system <strong>to</strong> defend<br />

against human, animal, <strong>and</strong> environmental pathogens, but could also<br />

potentially support or provide cover for offensive BW capabilities.<br />

Moscow has stated that it possesses no s<strong>to</strong>ckpile of BW agents <strong>and</strong><br />

filled munitions. The United States is concerned, however, that dedicated<br />

<strong>and</strong> dual-use Russian facilities maintain a mobilization capability <strong>to</strong><br />

produce such weapons [agents] quickly in time of need.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. The United States<br />

continues <strong>to</strong> have concerns in several areas <strong>with</strong> respect <strong>to</strong> a Russian offensive BW<br />

program.<br />

29


The United States discussed Russia’s BWC noncompliance, in the CTR Waiver<br />

request, as follows:<br />

The Administration has continuing concerns about Russia’s commitment<br />

<strong>to</strong> comply <strong>with</strong> the 1972 BWC <strong>and</strong> believes that Russia continues <strong>to</strong><br />

maintain a covert offensive BW program in violation of the BWC.<br />

Russian offensive BW activities are detailed above in the discussion of<br />

CTR Act <strong>and</strong> FSA Certification No. 2, in the section entitled ‘Biological<br />

Weapons.’<br />

Russia regularly submits an annual BWC declaration <strong>to</strong> the United<br />

Nations, pursuant <strong>to</strong> voluntary Confidence-Building Measures adopted at<br />

past BWC Review Conferences. Russia’s initial 1992 declaration was<br />

purported <strong>to</strong> be a complete declaration of the Soviet BW program. A<br />

review of Russia’s 2001 BWC Confidence Building Measures Data<br />

Declaration, however, reaffirmed U.S. concerns that Russia’s 1992<br />

declaration was incomplete <strong>and</strong> misleading in certain areas. There<br />

continues <strong>to</strong> be a profound lack of openness about the offensive BW<br />

program inherited from the Soviet Union. Subsequent data declarations<br />

provide no additions <strong>to</strong> Russia’s 1992 declaration of past offensive BW<br />

activities, which falsely denied past production <strong>and</strong> s<strong>to</strong>ckpiling of BW.<br />

The 1992 declaration also failed <strong>to</strong> list all of the sites that supported the<br />

Soviet offensive BW program <strong>and</strong> that retain at least some of their<br />

offensive capability. The more recent declarations focus on the ostensibly<br />

defensive aspects of military <strong>and</strong> civilian facilities <strong>with</strong>out acknowledging<br />

the support many of them provided <strong>to</strong> the massive Soviet offensive BW<br />

program in the past <strong>and</strong> that at least some continue <strong>to</strong> provide <strong>to</strong> the<br />

current Russian program.<br />

It is a matter of concern that contacts between the United States <strong>and</strong> the<br />

Russian Federation on BWC-related issues are increasingly strained, <strong>with</strong><br />

public statements by Russian officials appearing <strong>to</strong> retreat from the<br />

statements made by President Yeltsin in 1992. Some have asserted that<br />

Russia has never had an offensive BW program. The United States has<br />

offered several times <strong>to</strong> have regular bilateral meetings on the BWC, but<br />

Russia has not accepted.<br />

Not<strong>with</strong>st<strong>and</strong>ing U.S. concerns <strong>with</strong> Russia's offensive BW capabilities,<br />

the massive BW program Russia inherited from the Soviet Union has been<br />

considerably reduced. Since the Soviet era, there have been severe cuts in<br />

funding <strong>and</strong> personnel at key BW facilities associated <strong>with</strong> the Soviet<br />

program. In another positive development, U.S.-Russian cooperative<br />

biotechnology programs in recent years have enhanced transparency by<br />

providing controlled access <strong>to</strong> non-MoD [Ministry of Defense] facilities<br />

<strong>and</strong> personnel associated <strong>with</strong> the Soviet Union’s offensive BW program.<br />

This transparency has reduced, but not eliminated, U.S. concerns that<br />

30


these civilian facilities are directly involved in an ongoing, offensive BW<br />

program. This year, access for United States Government personnel was<br />

exp<strong>and</strong>ed <strong>to</strong> include cooperation-related visits <strong>to</strong> several key Soviet-era<br />

civilian BW production facilities in Russia. In another positive<br />

development, in November 2001, President Putin signed a Joint Statement<br />

<strong>with</strong> President Bush that reaffirmed Russia’s commitment <strong>to</strong> the BWC.<br />

Russia continues, however, <strong>to</strong> deny Western access <strong>to</strong> certain biological<br />

facilities, including Ministry of Defense <strong>and</strong> Ministry of Health facilities<br />

believed <strong>to</strong> have been associated <strong>with</strong> the Soviet offensive BW program.<br />

This remains the United States’ assessment. Russia continues <strong>to</strong> challenge these<br />

charges.<br />

FINDING. The United States judges based on all available evidence that Russia<br />

continues <strong>to</strong> maintain an offensive BW program in violation of the Convention.<br />

SYRIA<br />

ISSUE. We continue <strong>to</strong> have concerns regarding the nature of Syria’s BW-related<br />

activities.<br />

HISTORY OF COMPLIANCE EVALUATION. The first time the United States<br />

discussed Syrian compliance in this version of the Report was in the June 2003 NCR. In<br />

that Report, the we concluded that: “[t]he United States judges, based upon the evidence<br />

available, that Syria is pursuing the development of biological weapons that would<br />

constitute a violation of the BWC if Syria were a State Party.”<br />

DISCUSSION OF OBLIGATIONS. Syria signed the BWC in 1972, but has yet<br />

<strong>to</strong> ratify the Convention. Syria has indicated that its ratification of the BWC is contingent<br />

upon Israeli accession <strong>to</strong> the Nuclear Non-Proliferation Treaty.<br />

ACTIONS. Syria’s biotechnical infrastructure is capable of supporting agent<br />

development. However, Syria lacks the technical infrastructure for a robust or<br />

sophisticated BW program <strong>and</strong> depends on foreign assistance <strong>to</strong> upgrade its<br />

biotechnology infrastructure.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. The United States<br />

believes that Syria, as a signa<strong>to</strong>ry <strong>to</strong> the BWC, has conducted research <strong>and</strong> development<br />

for an offensive BW program.<br />

FINDING. The United States judges that based upon the evidence available,<br />

Syria is developing an offensive biological warfare capability that would constitute a<br />

violation of the BWC if Syria were a State Party.<br />

31


B. THE TREATY ON CONVENTIONAL ARMED FORCES IN EUROPE<br />

(CFE)<br />

The Treaty on Conventional Armed Forces in Europe (CFE) was signed<br />

November 19, 1990, by 22 States. On June 14, 1991, the Soviet Union issued two related<br />

statements in an extraordinary conference in Vienna <strong>and</strong> in the Joint Consultative Group<br />

(JCG). One contained legally-binding obligations related <strong>to</strong> equipment of the same<br />

categories as treaty-limited equipment (TLE) held by Naval Infantry, Coastal Defense<br />

(NI/CD), <strong>and</strong> Strategic Rocket Forces. The second contained political commitments<br />

related <strong>to</strong> equipment of Treaty-limited types removed from the CFE area of application<br />

by the Soviet Union prior <strong>to</strong> Treaty signature.<br />

In December 1991, the Soviet Union dissolved, <strong>and</strong> 12 newly-independent states<br />

(NIS) came in<strong>to</strong> existence. In the Tashkent Agreement of May 15, 1992, the eight NIS<br />

<strong>with</strong> terri<strong>to</strong>ry in the CFE Treaty’s area of application (Armenia, Azerbaijan, Belarus,<br />

Georgia, Kazakhstan, Moldova, Russia <strong>and</strong> Ukraine) agreed on principles for, <strong>and</strong> most<br />

of the details of, allocating the CFE rights <strong>and</strong> obligations of the Soviet Union. At the<br />

Oslo Extraordinary Conference of all CFE participants in June 1992, these eight states<br />

confirmed their acceptance of all CFE <strong>and</strong> CFE-related rights <strong>and</strong> obligations of the<br />

former Soviet Union (FSU).<br />

On July 17, 1992, the CFE Treaty came in<strong>to</strong> full provisional application. After<br />

the final instrument of ratification was deposited, the Treaty formally entered in<strong>to</strong> force<br />

on November 9, 1992, <strong>with</strong> all Treaty timelines calculated from July 17, 1992.<br />

CFE-1A, an associated agreement that came in<strong>to</strong> effect simultaneously <strong>with</strong> the<br />

CFE Treaty, establishes aggregate national ceilings for personnel in military forces in the<br />

area of application. It requires each CFE State Party <strong>to</strong> provide data on its peacetime<br />

authorized personnel strength <strong>and</strong> <strong>to</strong> brief on-site inspection (OSI) teams on the personnel<br />

holdings of units inspected.<br />

In January 1993, the Czechoslovak Federated Republic (CSFR) split in<strong>to</strong> two<br />

separate states, the Czech Republic <strong>and</strong> the Slovak Republic, which accepted the rights<br />

<strong>and</strong> obligations of the former CSFR <strong>and</strong> were accepted in<strong>to</strong> the Treaty. This brought the<br />

number of CFE States Parties <strong>to</strong> its present 30.<br />

Detailed CFE data, as of July 17, 1992, were exchanged in August 1992.<br />

Subsequent data exchanges required by the Treaty have occurred each year on December<br />

15, <strong>with</strong> information as of January 1 of the following year. There was an additional data<br />

exchange as of November 16, 1995, at the end of the Treaty reduction period, when the<br />

Treaty’s limits on TLE <strong>and</strong> CFE-1A’s limits on personnel went in<strong>to</strong> effect.<br />

The first Review Conference of States Parties <strong>to</strong> the Treaty <strong>to</strong>ok place on May 15-<br />

31, 1996. Among the achievements of this conference were: agreement on<br />

underst<strong>and</strong>ings <strong>and</strong> interpretations <strong>to</strong> improve the viability <strong>and</strong> effectiveness of the<br />

32


Treaty; identification of technical/administrative issues requiring further consideration in<br />

the Treaty’s Joint Consultative Group (JCG); a commitment <strong>to</strong> begin a negotiation<br />

process aimed at preserving the Treaty’s viability <strong>and</strong> improving its operation in a<br />

changing security environment (CFE adaptation); acceptance of a new schedule <strong>with</strong><br />

some additional modalities for Russia’s obligations <strong>to</strong> destroy or convert equipment east<br />

of the Urals; <strong>and</strong>, in response <strong>to</strong> recognized Russian <strong>and</strong> Ukrainian flank concerns, an<br />

agreement revising the Treaty’s flank regime.<br />

The Flank Document has three basic elements: (1) reduction of the size of the<br />

flank zone in Russia <strong>and</strong> Ukraine by a map realignment; (2) establishment of limits on<br />

overall Russian TLE that could be in the original flank zone, <strong>and</strong> on Russian ACVs <strong>and</strong><br />

all three categories of Ukrainian ground TLE in specific areas removed from the original<br />

flank zone; <strong>and</strong> (3) provision of greater transparency regarding military forces on Russian<br />

<strong>and</strong> Ukrainian terri<strong>to</strong>ry in the original flank zone through additional inspections, data<br />

exchanges, <strong>and</strong> notifications.<br />

Under the agreement, Russia <strong>and</strong> Ukraine were required <strong>to</strong> meet all CFE<br />

obligations in the new <strong>and</strong> old (original) flank zones by May 31, 1999.<br />

Major parts of the Flank Document went in<strong>to</strong> provisional effect immediately<br />

(including an interim cap on Russian TLE in the original flank area, as well as the<br />

enhanced transparency measures). The Flank Document entered in<strong>to</strong> force on May 15,<br />

1997.<br />

In January 1997, the States Parties began negotiations in the JCG <strong>to</strong> adapt the<br />

Treaty <strong>to</strong> new political circumstances, including the dissolution of the Warsaw Pact <strong>and</strong><br />

the Soviet Union <strong>and</strong> enlargement of NATO. During 1997, NATO proposed a new<br />

structure of limitations that all States Parties accepted. In summer 1998, NATO tabled<br />

detailed proposals concerning the operation of the new limitations, including key military<br />

flexibilities, enhancement of data <strong>and</strong> verification provisions, <strong>and</strong> reconciliation of the<br />

1996 Flank Agreement <strong>and</strong> related provisions. On November 19, 1999, an amendment<br />

document <strong>to</strong> adapt the CFE Treaty was signed at the OSCE summit in Istanbul; it will<br />

enter in<strong>to</strong> force upon ratification by all 30 States Parties. Key elements of the Adapted<br />

Treaty include: national <strong>and</strong> terri<strong>to</strong>rial ceilings (NC <strong>and</strong> TC); flexibilities for situations<br />

when it would be necessary <strong>to</strong> exceed TCs; enhanced provisions regarding host state<br />

consent for the presence of foreign forces; enhanced transparency on forces, activities,<br />

<strong>and</strong> TLE holdings; increased opportunities for on-site inspections; <strong>and</strong> the opening of the<br />

Treaty <strong>to</strong> accession on a case-by-case basis.<br />

As noted in previous reports, including last year’s Condition 5 Report, in spite of<br />

some troubling exceptions, most of the provisions of the Treaty have been implemented<br />

<strong>with</strong> success. By the end of 2001, more than 52,000 pieces of conventional armaments<br />

<strong>and</strong> equipment had been reduced inside the CFE zone according <strong>to</strong> the Treaty’s reduction<br />

provisions, <strong>with</strong> many States Parties having reduced their holdings <strong>to</strong> lower levels than<br />

required – notifying over 6,000 voluntary reductions below limits. By that date, Russia<br />

33


had notified for destruction or conversion approximately 15,400 additional items in<br />

accordance <strong>with</strong> the provisions of Treaty-related agreements. Almost 4,100 intrusive onsite<br />

inspections had taken place by the end of 2001 (including supplementary flank<br />

inspections, expert’s visits, <strong>and</strong> reduction inspections). Through December 2002, Russia<br />

notified the destruction of over 5,700 tanks against its remaining east of the Urals (EoU)<br />

commitments. Through December 2003, States Parties notified over 1500 added<br />

reductions below their limits. Finally, the States Parties notified some 550 on-site<br />

inspections during 2002 <strong>and</strong> 2003 (including supplementary flank inspections, expert’s<br />

visits, <strong>and</strong> reduction inspections).<br />

On a major compliance concern – Russian stationing of forces in Moldova <strong>and</strong><br />

Georgia <strong>with</strong>out host state consent – some important progress has been made, but more<br />

needs <strong>to</strong> be done. In regard <strong>to</strong> a second major concern, Russian data <strong>and</strong> related<br />

notifications indicated that the overages above Adapted Treaty flank limits had been<br />

almost eliminated. Nevertheless, there remained a continuing need <strong>to</strong> moni<strong>to</strong>r the<br />

situation. (Subsequently, Russia’s flank data as of July 1, 2002, <strong>and</strong> a related notification<br />

indicated that Russian holdings of TLE for the adapted flank area were <strong>with</strong>in the future<br />

limits of the Adapted Treaty.) In addition, a number of other longst<strong>and</strong>ing concerns<br />

remained in regard <strong>to</strong> Armenia, Azerbaijan, Belarus, Russia, <strong>and</strong> Ukraine. In addition,<br />

new issues arose in 2002 <strong>and</strong> 2003. These are all discussed below. Additional details<br />

can be found in the CFE <strong>Compliance</strong> Report pursuant <strong>to</strong> Condition 5 on the Senate<br />

Resolution of Advice <strong>and</strong> Consent <strong>to</strong> the CFE Flank Document.<br />

Finally, there were a number of smaller, more technical concerns such as late or<br />

erroneous notifications, failure <strong>to</strong> notify removal of TLE from designated permanent<br />

s<strong>to</strong>rage sites (DPSS), failure <strong>to</strong> report correctly objects of verification (OOV), <strong>and</strong> the<br />

inability of escorts <strong>and</strong> unit comm<strong>and</strong>ers <strong>to</strong> account for missing TLE.<br />

COUNTRY ASSESSMENTS<br />

ARMENIA<br />

Declaring <strong>and</strong> Meeting Required Reduction Liabilities. As noted in previous<br />

Reports, Armenia has failed <strong>to</strong> notify properly or carry out all of the reductions required<br />

by the Treaty. This problem has existed since the Treaty came in<strong>to</strong> force. Armenia’s<br />

failure <strong>to</strong> notify properly or <strong>to</strong> complete its required CFE reduction obligations<br />

contributes <strong>to</strong> the collective failure by the Soviet CFE successor states <strong>to</strong> meet their 1992<br />

Oslo commitment <strong>to</strong> declare <strong>and</strong> <strong>to</strong> complete reduction requirements that are no less than<br />

the reduction requirements of the FSU (discussed under Collective Obligations).<br />

Apparent Failure <strong>to</strong> Report TLE Received from Russia. Reports over the last<br />

three years outlined possible Treaty implications of TLE transfers from Russia in<strong>to</strong><br />

Armenia between 1994 <strong>and</strong> 1996. There has been no change in this issue on the<br />

Armenian side, <strong>and</strong> there have been no new steps <strong>to</strong>ward resolving the CFE issues<br />

surrounding these transfers. It is not clear whether it will be possible <strong>to</strong> make progress on<br />

34


this issue outside of the context of a political settlement of the Nagorno-Karabakh (N-K)<br />

dispute which is the focus of the OSCE’s Minsk Group (co-chaired by the United States,<br />

Russia, <strong>and</strong> France).<br />

Failure <strong>to</strong> Declare Look-Alikes of the MT-LB Variant Armored Personnel<br />

Carrier (APC). For the first time in several years (after repeated U.S. questioning, <strong>and</strong><br />

after an on-site inspection [OSI] in 2000 observed several MT-LB-U APC look-alikes at<br />

a site in Armenia), Armenia declared in its data as of January 1, 2001, exactly the number<br />

of MT-LB APC look-alikes based on the MT-LB-U chassis that had been observed<br />

during the inspection. Questions, however, remain. When Armenia previously declared<br />

MT-LB-Us in its annual data, for instance, it declared a much larger figure, <strong>and</strong> the<br />

declared Armenian force structure has not changed significantly.<br />

Late, <strong>and</strong> Possibly Incomplete, Notification of TLE Entry in<strong>to</strong> Service. As<br />

reported previously, Armenia was late in notifying entry in<strong>to</strong> service of multiple rocket<br />

launcher (MRL) systems acquired from China, <strong>and</strong> may have failed <strong>to</strong> report the full<br />

number received (according <strong>to</strong> press reports). Armenian representatives deny that more<br />

MRLs were received than the number they notified. The Armenians did not follow CFE<br />

procedures for providing technical data <strong>and</strong> pho<strong>to</strong>graphs of these systems, but they<br />

hosted a Vienna Document 1999 demonstration of the new equipment in August 2000.<br />

Improper Site Diagram <strong>and</strong> Denial of Inspection Access. As reported last<br />

year, during the U.S.-led inspection in May 2000, the Armenian site diagram improperly<br />

excluded two common area units <strong>and</strong> access was denied <strong>to</strong> those areas. This problem,<br />

however, has not resurfaced <strong>and</strong> Armenian representatives have attributed it <strong>to</strong><br />

inadequately trained escort personnel.<br />

<strong>Compliance</strong> <strong>with</strong> Limits. Previously, Armenia, while asserting compliance <strong>with</strong><br />

its limits in the five major categories of TLE, exceeded its limit in the armored infantry<br />

fighting vehicle (AIFV)/heavy armament combat vehicle (HACV) sub-category of ACVs<br />

by more than 30. This overage had remained unchanged since Treaty limits came in<strong>to</strong><br />

effect. However, on August 22, 2000, Armenia notified the transfer of almost 60 AIFVs<br />

from the conventional armed forces <strong>to</strong> internal security forces <strong>and</strong> Armenian data as of<br />

January 1, 2001 through January 1, 2004 showed Armenia <strong>to</strong> be <strong>with</strong>in all of its limits,<br />

including those for AIFV/HACVs. However, because of other questions we continue <strong>to</strong><br />

track this issue.<br />

Possibly Unreported TLE. In addition <strong>to</strong> the MT-LBu variant APC look-alikes<br />

<strong>and</strong> any TLE apparently transferred <strong>to</strong> Armenian forces from Russia between 1994 <strong>and</strong><br />

1996, there have been several indications <strong>and</strong> confirmations of other TLE (<strong>and</strong> possibly<br />

APC look-alikes) that Armenia has never declared.<br />

Tanks: As reported previously, although Armenia never reported T-54s or T-55s<br />

in any of its CFE data declarations through 2000, information in 1999 <strong>and</strong> later indicated<br />

that it did possess such equipment. In May 1999, a U.S. inspec<strong>to</strong>r reported several T-55s<br />

35


at a Russian Armor Maintenance Facility in Georgia, <strong>and</strong> the Russian escorts stated that<br />

three of them belonged <strong>to</strong> Armenia. The Russians also stated that one of these tanks had<br />

arrived in 1996 <strong>and</strong> the other two in 1998. In its data as of January 1, 2001, for the first<br />

time, Armenia declared the same number of “T-54/T-55” tanks as those seen at the<br />

Russian facility in Georgia. Subsequently the Armenians issued a notification raising the<br />

number by several more. However, the designation “T-54/T-55” was highly<br />

questionable. Although not always readily distinguishable by external observation, the<br />

owner would be expected <strong>to</strong> know the difference between the two types, <strong>and</strong> other States<br />

Parties holding T-54 or T-55 tanks identify them separately. This sequence strongly<br />

suggested that the Armenians were responding <strong>to</strong> their having been caught in<br />

noncompliance <strong>with</strong> reporting obligations in regard <strong>to</strong> these tanks. Later, in its data as of<br />

January 1, 2004, Armenia did break out these tanks separately in<strong>to</strong> T-54s <strong>and</strong> T-55s.<br />

Artillery: As previously reported, figures in Russian open sources identified 18<br />

D-1 artillery pieces as being shipped from Russia in<strong>to</strong> Armenia between 1994 <strong>and</strong> 1996.<br />

Since its data as of January 1, 1994 (prior <strong>to</strong> the shipping of items from Russia in<strong>to</strong><br />

Armenia), Armenia has consistently declared less than five D-1s. This may leave several<br />

D-1s transferred from Russia unaccounted for. Finally, as discussed in previous reports,<br />

although Armenia has declared only a small number of WM-80 MRLs received from<br />

China, Azerbaijani officials have claimed, <strong>and</strong> the Russian open press has indicated that<br />

the actual number received may have been slightly larger. See last year’s report for<br />

additional details.<br />

ACVs: Armenia has never declared any MT-LB APCs in its data <strong>and</strong> ceased<br />

reporting MT-LBT APC look-alikes as of January 1, 1998. However, during the past<br />

three years inspection reporting has documented the presence of MT-LB APCs <strong>and</strong>/or<br />

MTLB APC look-alikes among Armenia’s conventional forces. A U.S.-led inspection in<br />

May 2000 revealed a small number of both MT-LB APCs <strong>and</strong> MT-LBT APC look-alikes,<br />

none of which were included in Armenian data for the site inspected or briefed during the<br />

inspection. The Armenians stated that the MT-LBs belonged <strong>to</strong> the Volunteer Society for<br />

Assistance <strong>to</strong> the Army, Air Force, <strong>and</strong> Navy (DOSAAF) -- the auxiliary organization<br />

that prepares youths for service in the armed forces. However, Armenia has still not<br />

declared any MT-LB APCs in either its conventional armed forces or its internal security<br />

forces. The Treaty requires that armored combat vehicles (ACVs) in the conventional<br />

armed forces be declared both by number <strong>and</strong> type, but APCs in internal security forces<br />

are only required <strong>to</strong> be declared by aggregate numbers in each administrative district or<br />

region. However, Armenia’s data each year show all declared internal security APCs by<br />

type <strong>and</strong> have never included any MT-LBs.<br />

FINDINGS. Armenia has failed <strong>to</strong> comply <strong>with</strong> Treaty provisions in regard <strong>to</strong><br />

reduction liability declarations <strong>and</strong> reductions completed. According <strong>to</strong> notifications <strong>and</strong><br />

Armenian data as of January 1, 2000, through January 1, 2004, Armenia no longer<br />

exceeds Treaty limits in the AIFV/HACV sub-category of ACVs, but the possibly<br />

unreported TLE creates questions. There is evidence that Armenia may have failed <strong>to</strong><br />

notify increases in unit holdings involving TLE transferred from Russia. After several<br />

36


years during which Armenia failed <strong>to</strong> report MT-LB-U look-alikes of the MT-LB APC<br />

that have remained in its inven<strong>to</strong>ry, Armenia in its latest data did report several such<br />

look-alikes, but far fewer than it had regularly reported in the years before Armenia<br />

s<strong>to</strong>pped including them in its data. Also, in 2000, Armenia notified the acquisition of<br />

MRLs late, <strong>and</strong> may not have reported all of them. There is also evidence of possibly<br />

unreported TLE. Finally, Armenia presented an improper site diagram <strong>and</strong> improperly<br />

denied access <strong>to</strong> two excluded common area units during an U.S.-led inspection in May<br />

2000, although this problem has not resurfaced since then <strong>and</strong> is considered <strong>to</strong> have been<br />

corrected.<br />

AZERBAIJAN<br />

Declaring <strong>and</strong> Meeting Required Reduction Liabilities. As noted in previous<br />

reports, Azerbaijan has stated that it cannot notify <strong>and</strong> carry out its required reductions so<br />

long as the dispute in N-K continues. This position has not changed. Nevertheless,<br />

Azerbaijan has notified <strong>and</strong> carried out reduction events. To date, Azerbaijan has<br />

notified <strong>and</strong> apparently completed some 430 TLE reductions out of a putative liability of<br />

over 1,000. Azerbaijan’s failure either <strong>to</strong> notify or <strong>to</strong> complete its required reductions<br />

contributes <strong>to</strong> the collective failure by the Soviet CFE successor states <strong>to</strong> meet the Oslo<br />

commitment <strong>to</strong> declare <strong>and</strong> <strong>to</strong> complete reduction requirements that are no less than the<br />

reduction requirements of the FSU.<br />

<strong>Compliance</strong> <strong>with</strong> Limits. According <strong>to</strong> its data as of January 1, 2000, January 1,<br />

2001, <strong>and</strong> January 1, 2002, Azerbaijan no longer exceeds its declared limits in any TLE<br />

category. However, as described in previous reports, two inspections (one in 1999 <strong>and</strong><br />

one in 2000) led <strong>to</strong> questions about these data. See previous Reports for details.<br />

Suspension of CFE Provisions. In its data as of January 1, 2001, Azerbaijan<br />

continued <strong>to</strong> fail correctly <strong>to</strong> report eight objects of verification (OOVs). Then, in its data<br />

as of January 1, 2002, January 1, 2003, <strong>and</strong> January 1, 2004, this number rose <strong>to</strong> nine.<br />

Also, during 2002 <strong>and</strong> 2003, Azerbaijan continued its unilateral suspension of CFE<br />

provisions requiring notifications of changes of ten percent or more in TLE assigned <strong>to</strong><br />

units. Azerbaijan has continued <strong>to</strong> defend its unilateral suspension of certain Treaty<br />

notifications on the grounds that these notifications would provide operational<br />

information <strong>to</strong> Armenia in the N-K context, <strong>and</strong> again alluded <strong>to</strong> military security<br />

necessity in regard <strong>to</strong> the lack of notifications on changes in unit holdings <strong>and</strong> the failure<br />

<strong>to</strong> report locations for deployed units whose garrisons were occupied by the enemy.<br />

However, considering that a cease-fire in Nagorno-Karabakh has been in place for<br />

several years, it is difficult <strong>to</strong> justify increasing the number of units whose garrisons are<br />

“enemy-occupied.”<br />

FINDINGS. Azerbaijan has failed <strong>to</strong> comply <strong>with</strong> Treaty provisions <strong>with</strong> regard<br />

<strong>to</strong> reduction liability declarations, <strong>and</strong> has continued <strong>to</strong> unilaterally suspend selected<br />

Treaty requirements. Although, according <strong>to</strong> its last three data exchanges, Azerbaijan has<br />

asserted that it is in compliance <strong>with</strong> its Treaty limits, there is continuing information <strong>to</strong><br />

37


suggest improper use of equipment allegedly reduced by virtue of being transformed in<strong>to</strong><br />

working order static display items.<br />

BELARUS<br />

Questionable Declaration of Tanks for Export. As reported for several years,<br />

there have been questions about the number of tanks Belarus has declared as being in the<br />

“awaiting export” category. Over the last few years, these numbers have decreased, <strong>and</strong><br />

subsequent UN <strong>and</strong> OSCE data about Belarusian tank exports confirm that (except for<br />

one instance in which the number of modern tanks decreased due <strong>to</strong> their replacement in<br />

the export category by older, more exportable models) the decreases have represented<br />

exports. Belarusian data as of January 1, 2001, continued <strong>to</strong> show almost 150 tanks<br />

awaiting export. Its data as of January 1, 2002 through January 1, 2004 showed very<br />

slightly fewer. Although Belarus now apparently is properly implementing its<br />

obligations in regard <strong>to</strong> TLE awaiting export, this does not fully resolve all of our<br />

concerns about previous Belarusian use of the exemption from accountability for<br />

equipment awaiting export, especially in regard <strong>to</strong> its reduction liability <strong>and</strong> <strong>to</strong> the<br />

collective obligation described below. Belarus continues <strong>to</strong> state that the tanks declared<br />

as awaiting export are in excess of its needs <strong>and</strong> that it needs the hard currency they could<br />

bring if exported.<br />

Denial of Access <strong>to</strong> a Portion of a Declared Site <strong>and</strong> Failure <strong>to</strong> Declare<br />

Equipment. In its data as of January 1, 2001 through January 1, 2004, Belarus continued<br />

<strong>to</strong> declare the Spetsnaz brigade at Marina Gorka, but again <strong>with</strong>out any of the TLE that<br />

could still remain there. The site has not been subject <strong>to</strong> inspection since 1999, when<br />

access was last denied.<br />

FINDINGS. Belarus’ recent tank exports reinforce the conclusion reported<br />

previously that Belarus is now using its holdings of equipment for export in the manner<br />

intended. Belarus has continued <strong>to</strong> fail <strong>to</strong> report TLE at one site, <strong>and</strong> <strong>to</strong> deny access <strong>to</strong><br />

part of that site, where TLE could still be present.<br />

RUSSIA<br />

Failure <strong>to</strong> Declare Look-Alikes. There has been no change on this issue. Russia<br />

continues <strong>to</strong> refuse <strong>to</strong> declare either APC look-alikes of the MT-LB-U version or<br />

Engineer Reconnaissance Vehicle (IRM) AIFV look-alikes, insisting that their earlier<br />

inclusion in Soviet data as of Treaty signature <strong>and</strong> in Russia’s first data exchange of July<br />

17, 1992, was merely a technical error. The United States rejects this view. Moreover,<br />

the MT-LB-U is included in the Pro<strong>to</strong>col on Existing Types (POET) <strong>and</strong> Russia’s refusal<br />

<strong>to</strong> declare these APC look-alikes is not in accord <strong>with</strong> Treaty rules.<br />

Russian Stationed Forces. For several years, there have been important<br />

concerns about Russian forces stationed in Moldova <strong>and</strong> Georgia <strong>with</strong>out host state<br />

consent. At the November 1999 OSCE Summit in Istanbul, Russia committed <strong>to</strong> specific<br />

38


actions related <strong>to</strong> <strong>with</strong>drawal of Russian forces from Georgia <strong>and</strong> Moldova, <strong>and</strong> there<br />

was, until recently, considerable progress in the case of Russian forces in Georgia.<br />

Meanwhile, after a year <strong>and</strong> a half of virtually no progress in Moldova, a number of<br />

encouraging developments have taken place there since the summer of 2001.<br />

The United States <strong>and</strong> the OSCE have continued <strong>to</strong> offer <strong>and</strong> provide assistance in<br />

the form of reimbursement for costs associated <strong>with</strong> the relocation of Russian troops <strong>and</strong><br />

military equipment from Georgia <strong>and</strong> Moldova, as well as for removal or destruction of<br />

military equipment <strong>and</strong> ammunition s<strong>to</strong>red at Russian facilities in Moldova. (Previous<br />

reports, including last year’s Condition 5 Report, provide additional details.)<br />

As also reported previously, in Annex 14 of the CFE Final Act, Russia committed<br />

<strong>to</strong> decrease, by no later than December 31, 2000, its TLE holdings on Georgian terri<strong>to</strong>ry<br />

<strong>to</strong> not more than 153 tanks, 241 ACVs, <strong>and</strong> 140 pieces of artillery. Russian CFE data<br />

reported some 140 tanks, over 500 ACVs, <strong>and</strong> close <strong>to</strong> 170 pieces of artillery in Georgia<br />

as of January 1, 2000, not including ACVs <strong>and</strong> artillery in Russian “peacekeeping” forces<br />

present in the Abkhaz <strong>and</strong> South Ossetian regions of Georgia. Russia’s flank data as of<br />

July 1, 2000, showed the same numbers of tanks <strong>and</strong> pieces of artillery, but a drop in<br />

ACVs <strong>to</strong> about 480. But counting the peacekeeping forces <strong>and</strong> over 20 decommissioned<br />

ACVs, the <strong>to</strong>tal number of ground items present on Georgian terri<strong>to</strong>ry was some 140<br />

tanks, close <strong>to</strong> 650 ACVs, <strong>and</strong> almost 170 pieces of artillery. After a series of<br />

<strong>with</strong>drawals <strong>and</strong> TLE destruction events which were all either observed <strong>and</strong> confirmed by<br />

U.S. <strong>and</strong>/or OSCE observers or confirmed by Georgia, Russia met this TLE commitment<br />

by the end of 2000 <strong>and</strong> issued a notification <strong>to</strong> that effect. Russia’s data as of both<br />

January 1, 2001, <strong>and</strong> July 1, 2001 (adjusted <strong>to</strong> include the peacekeeping forces), showed<br />

<strong>to</strong>tal TLE holdings in Georgia <strong>to</strong> be <strong>with</strong>in the levels committed <strong>to</strong> at Istanbul.<br />

At Istanbul, Russia also agreed <strong>to</strong> <strong>with</strong>draw or dispose of the TLE at the Russian<br />

military bases at Vaziani <strong>and</strong> Gudauta <strong>and</strong> the repair facility in Tbilisi by December 31,<br />

2000, <strong>and</strong> <strong>to</strong> disb<strong>and</strong> <strong>and</strong> <strong>to</strong> <strong>with</strong>draw from the bases at Vaziani <strong>and</strong> Gudauta by July 1,<br />

2001. Other aspects of the remaining Russian presence in Georgia were <strong>to</strong> be resolved in<br />

the same timeframe. While the Vaziani base was turned over on time, agreement over<br />

some of the terms of the closure of Gudauta was not reached by the July deadline. In<br />

November, the Russians announced fulfillment of their Istanbul Summit commitments<br />

<strong>with</strong> respect <strong>to</strong> Gudauta, claiming <strong>to</strong> have disb<strong>and</strong>ed the base <strong>and</strong> <strong>with</strong>drawn regular<br />

military forces there – leaving only CIS “peacekeepers” <strong>and</strong> the necessary facilities <strong>to</strong><br />

support their presence. Georgia, however, disputed Russia’s characterization of the status<br />

of Gudauta. The United States <strong>and</strong> NATO Allies underscored <strong>to</strong> Russia that it was<br />

essential <strong>to</strong> reach agreement <strong>with</strong> Georgia on any continuing Russian presence at<br />

Gudauta <strong>and</strong> urged Russia <strong>and</strong> Georgia <strong>to</strong> renew their talks. This theme was echoed in<br />

the Statement on Georgia agreed by all 54 OSCE Ministers at their meeting in Bucharest<br />

December 3-4. The Ministerial document, agreed by Russia <strong>and</strong> Georgia, called for the<br />

resumption of Georgia-Russia talks on transparency regarding Gudauta <strong>and</strong> early legal<br />

transfer of the facility <strong>to</strong> Georgia. This appears <strong>to</strong> offer a way forward on these issues<br />

that both Russia <strong>and</strong> Georgia can accept. (In May 2005, Georgian <strong>and</strong> Russian Foreign<br />

39


Ministers signed a Joint Statement establishing timelines for the <strong>with</strong>drawal of Russian<br />

forces from the Akhalkalaki <strong>and</strong> Batumi bases <strong>and</strong> addressing the Russian presence at the<br />

Gudauta base. Under the Joint Statement additional actions are needed, including<br />

completion of a technical agreement -- which was under negotiation in summer 2005 --<br />

on Akhalkalaki <strong>and</strong> Batumi, <strong>and</strong> further steps regarding Gudauta, in order <strong>to</strong> fulfill the<br />

Istanbul commitments <strong>with</strong> respect <strong>to</strong> Georgia.)<br />

With regard <strong>to</strong> Moldova, Russia announced in November that it had fulfilled its<br />

Istanbul commitment <strong>to</strong> <strong>with</strong>draw or destroy all TLE by the end of 2001. In Russia’s<br />

CFE data both as of January 1, 2001, <strong>and</strong> as of July 1, 2001, there were close <strong>to</strong> 110<br />

tanks, some 130 ACVs, <strong>and</strong> over 120 pieces of artillery stationed in Moldova. Russia<br />

began notifying <strong>and</strong> carrying out destruction events in July, completing the TLE portion<br />

of the Istanbul requirement. By December 2001, OSCE observers, including CFE<br />

inspec<strong>to</strong>rs, confirmed the <strong>with</strong>drawal or destruction of all TLE Russia had declared in<br />

Moldova, <strong>and</strong> Russian data as of January 1, 2002 through January 1, 2004 showed no<br />

TLE in Moldova.<br />

The second Istanbul commitment regarding Moldova was for the full <strong>with</strong>drawal<br />

of all Russian forces by the end of 2002. Other than the politics related <strong>to</strong> Transnistria,<br />

the biggest obstacle <strong>to</strong> meeting this second commitment is the removal, destruction, or<br />

demilitarization of some 42,000 <strong>to</strong>ns of s<strong>to</strong>red Russian ammunition. In addition, there<br />

are over 25,000 s<strong>to</strong>red Russian small arms that must be <strong>with</strong>drawn. Throughout the<br />

summer <strong>and</strong> fall, intensive negotiations were under way <strong>to</strong> identify the best <strong>and</strong> most<br />

satisfac<strong>to</strong>ry methods, including on a cost-effectiveness basis, <strong>to</strong> accomplish the disposal<br />

of the ammunition <strong>and</strong> the <strong>with</strong>drawal of the remaining Russian materiel. Russia invited<br />

the OSCE mission <strong>to</strong> observe loading of the first four trainloads of ammunition <strong>to</strong> be<br />

<strong>with</strong>drawn <strong>to</strong> Russia. The first trainload of Russian munitions departed the Kolbasna<br />

depot December 2, containing 20 cars carrying approximately 1,000 220mm Uragan<br />

rockets. Developments on Moldova were welcomed at the December OSCE Ministerial,<br />

<strong>and</strong> several states, including the United States, announced their intention <strong>to</strong> make<br />

additional contributions <strong>to</strong> the OSCE Voluntary fund-Moldova <strong>to</strong> help support the<br />

Russian <strong>with</strong>drawal effort, in particular the costly process of disposing of ammunition<br />

s<strong>to</strong>cks.<br />

Throughout 2002 <strong>and</strong> 2003, U.S. <strong>and</strong> NATO officials continued <strong>to</strong> press the<br />

Russians bilaterally <strong>and</strong> at the OSCE in Vienna <strong>to</strong> take action <strong>to</strong> fulfill their commitment<br />

<strong>to</strong> <strong>with</strong>draw Russian equipment <strong>and</strong> personnel from Moldova. Important progress began<br />

in spring 2001. The OSCE Head of Mission agreed <strong>with</strong> Russian authorities on<br />

procedures for the use of the OSCE Voluntary Fund <strong>to</strong> support <strong>with</strong>drawal <strong>and</strong>/or<br />

destruction of Russian troops, arms, <strong>and</strong> military equipment from Moldova. It was<br />

agreed <strong>to</strong> establish a group of experts <strong>to</strong> work out the technical procedures for the<br />

destruction, conversion, or removal of the large quantities of Russian ammunition s<strong>to</strong>red<br />

in Moldova. Meetings were held in August <strong>and</strong> September of 2001. Discussions have<br />

also been ongoing between Russia <strong>and</strong> the OSCE <strong>to</strong> arrange the <strong>with</strong>drawal of the large<br />

numbers of s<strong>to</strong>red Russian small arms. Contributions by the United States <strong>to</strong> the OSCE<br />

40


Voluntary Fund <strong>to</strong> support the <strong>with</strong>drawal of Russian troops <strong>and</strong> <strong>to</strong> support the<br />

<strong>with</strong>drawal or destruction of Russian arms <strong>and</strong> military equipment from Moldova have<br />

been critical <strong>to</strong> these efforts.<br />

A Russian representative has also reiterated the argument that Russia’s non-TLE<br />

related Istanbul commitments regarding Georgia <strong>and</strong> Moldova “did not have anything <strong>to</strong><br />

do <strong>with</strong> CFE.” This is not correct. The stationing of a State Party’s forces on another<br />

State Party’s terri<strong>to</strong>ry <strong>with</strong>out permission from the host state is a violation of Treaty rules<br />

(specifically in Article IV, paragraph 5) regardless of whether or not TLE is present.<br />

Additional details on U.S. actions can be found in the Secretary of State’s Annual<br />

Report on Withdrawal of Russian Armed Forces <strong>and</strong> Military Equipment.<br />

Failure <strong>to</strong> Notify of Equipment Transfers <strong>with</strong>in the CFE Zone. The last<br />

three Reports outlined details of the possible Treaty implications of TLE transfers from<br />

Russia in<strong>to</strong> Armenia between 1994 <strong>and</strong> 1996. There has been no change in this issue on<br />

the Russian side (as previously reported, Russia has admitted that “illegal” transfers did<br />

take place), <strong>and</strong> there have been no new steps <strong>to</strong>ward resolving the CFE issues<br />

surrounding these transfers. It is not clear whether it will be possible <strong>to</strong> make progress on<br />

this <strong>with</strong>out a political settlement of the N-K dispute, which is the focus of the OSCE’s<br />

Minsk Group (co-chaired by the United States, Russia, <strong>and</strong> France).<br />

Improper Designation of ACVs as Ambulances. Last year’s Condition 5<br />

Report, based on examination of Russia’s data as of January 1, 1999, indicated that, at<br />

least at two sites of previous concern, units might no longer hold improperly marked<br />

“ambulances” – suggesting that this issue had been resolved. Subsequently, however, a<br />

U.S.-led challenge inspection of the Sevas<strong>to</strong>pol area discovered a number of questionable<br />

APC “ambulances” <strong>and</strong> a corresponding reduction in previous declared holdings of<br />

APCs. As a result, it is not clear how much of the APC ambulance problem was<br />

eliminated <strong>and</strong> how much had just been relocated. In a number of these inspections<br />

BTR-70 APCs <strong>and</strong> BTR-80 APCs marked as ambulances were observed. The<br />

designation of BTR-70s <strong>and</strong> BTR-80s as ambulances raises questions because the small<br />

access doors make it virtually impossible for a stretcher carrying an injured soldier <strong>to</strong> be<br />

placed inside the vehicle – thus seeming <strong>to</strong> preclude the vehicles’ use as ambulances <strong>and</strong><br />

suggesting the possibility of a fraudulent redesignation.<br />

Since September 2000, Russian representatives have maintained that this issue<br />

had been solved. But, as noted earlier, subsequent inspections again suggested it was not.<br />

In 2001, when this issue was raised, the Russian representatives questioned the<br />

significance of the instances cited <strong>and</strong> stated that Russian inspec<strong>to</strong>rs often saw more<br />

ambulances than this during inspections at U.S. <strong>and</strong> German sites. The United States<br />

pointed out that its concerns had nothing <strong>to</strong> do <strong>with</strong> the relative number of ambulances,<br />

but <strong>with</strong> situations where the previous unit holdings of APCs (e.g., in a mo<strong>to</strong>rized rifle<br />

battalion) had been replaced by APC ambulances that were marked only by the addition<br />

of a red cross, <strong>with</strong> no other modifications, <strong>and</strong> were parked in mo<strong>to</strong>rized rifle battalion<br />

41


sets alongside the other equipment of a mo<strong>to</strong>rized rifle battalion. The Russians<br />

responded only by indicating that they did not see this as a continuing problem.<br />

Decommissioned Equipment. As noted in previous Reports, Russian data<br />

through July 1, 1999, regularly declared more decommissioned tanks, ACVs, <strong>and</strong><br />

artillery items than the Treaty allows <strong>to</strong> be exempted from counting against limits.<br />

Russian data as of January 1, 2000, no longer showed an excess of decommissioned<br />

items. However, in those data, Russia improperly wrote off a <strong>to</strong>tal of almost 190 tanks<br />

<strong>and</strong> over 250 ACVs that were present at two capital repair facilities <strong>and</strong> had previously<br />

been reported as either decommissioned or in service (see discussion below on the issue<br />

of manipulation of annual data). Because these tanks <strong>and</strong> ACVs have never been<br />

properly removed from Russia’s accountable holdings, they should still be listed as either<br />

decommissioned or in service. Subsequent Russian data continued <strong>to</strong> exclude somewhat<br />

diminishing numbers of such items. Russian data as of January 1, 2001, once again<br />

showed an excess in decommissioned items (over 10 items), while still continuing<br />

improperly <strong>to</strong> exclude almost 15 tanks <strong>and</strong> over 250 ACVs that should either be included<br />

in its holdings or reported as decommissioned. In Russia’s data as of July 1, 2001, the<br />

number of decommissioned items in the flank alone was over 40 tanks <strong>and</strong> almost 170<br />

ACVs – some 10 items of decommissioned ground TLE above what the Treaty allows for<br />

Russia in the entire area of application (AoA). The number of improperly excluded tanks<br />

dropped slightly, but the number of excluded ACVs remained the same. These same<br />

concerns, albeit <strong>with</strong> slightly different numbers, continued through 2002 <strong>and</strong> 2003.<br />

<strong>Compliance</strong> <strong>with</strong> Flank Limits. According <strong>to</strong> its own data <strong>and</strong> notifications,<br />

Russian holdings continue <strong>to</strong> exceed most of the legally binding limits for both the<br />

original <strong>and</strong> revised flank zones. Russian holdings also continue <strong>to</strong> exceed the future<br />

limits for tanks in the flank area of Russia under the Adapted CFE Treaty. According <strong>to</strong><br />

Russian data as of January 1, 2002, <strong>and</strong> a related notification, the overages related <strong>to</strong> the<br />

Adapted Treaty had been reduced <strong>and</strong> ostensibly eliminated by the end of 2001.<br />

However, these data <strong>and</strong> the notification do not incorporate 11 tanks still improperly<br />

excluded from accountability at St Petersburg – leaving a continuing overage of at least<br />

five tanks. In its data as of January 1, 2001, July 1, 2001, <strong>and</strong> January 1, 2002, Russia<br />

continued <strong>to</strong> improperly exclude equipment at capital repair facilities that it characterizes<br />

as “non-combat capable.”<br />

A notification accompanying the Russian data as of January 1, 2000, voluntarily<br />

referenced TLE “temporarily introduced” in<strong>to</strong> the adapted flank from outside the AoA.<br />

This information was not provided, however, in subsequent data exchanges <strong>and</strong><br />

notifications on the amount of TLE temporarily located in the adapted flank. In these<br />

latter exchanges <strong>and</strong> notifications, the Russians only referenced TLE temporarily<br />

introduced in<strong>to</strong> the adapted flank <strong>with</strong> no clarification of how much came from other<br />

locations in the AoA or how much came from outside the AoA. Because no information<br />

was provided on the peacetime locations of this TLE, it is not possible <strong>to</strong> determine how<br />

much of the <strong>to</strong>tal amounts were added <strong>to</strong> the original flank area.<br />

42


The amounts of these overages, according <strong>to</strong> Russian figures, <strong>and</strong> comparisons<br />

among the last three data exchanges <strong>and</strong> notifications are shown in the charts below. In<br />

all cases, Russian data <strong>and</strong> notifications have been adjusted <strong>to</strong> also include the items<br />

improperly excluded from data, but do not account for excess decommissioned items.<br />

Overages above Adapted Treaty Flank Limits on Russian Terri<strong>to</strong>ry:<br />

Tanks ACV Artillery<br />

Future limits 1300 2140 1680<br />

Jan 2002 Overages At least 5 0 0<br />

July 2002 Overages 0 0 0<br />

Jan 2003 Overages 0 0 0<br />

July 2003 Overages 0 0 0<br />

Headroom as of July 2003 1<br />

Over 70 Almost 80 Over 200<br />

Overages above Current Treaty Limits for Active Units in the Revised Flank Zone: 2<br />

Tanks ACV Artillery<br />

Current active limits 700 580 1280<br />

Jan 2002 Overages Over 750 Over 2000 Over 500 3<br />

July 2002 Overages Over 650 Almost 2000 Over 460<br />

Jan 2003 Overages Almost 700 Almost 2050 Close <strong>to</strong> 500<br />

July 2003 Overages Close <strong>to</strong> 700 Over 2000 Almost 450<br />

Overages above Current Treaty Flank Limits for the Original Flank Zone:<br />

Tanks ACV Artillery<br />

Current <strong>to</strong>tal limits 1800 3700 2400<br />

Jan 2002 Overages 0 At least some 475 0<br />

July 2002 Overages 0 At least some 700 0<br />

Jan 2003 Overages 0 At least almost 750 0<br />

July 2003 Overages 0 At least almost 600 0<br />

Headroom as of July 2003 Almost 200 N/A Over 300<br />

1 Headroom, a term <strong>with</strong> important meaning in the Adapted Treaty, refers <strong>to</strong> the difference between the<br />

limit for a category of TLE <strong>and</strong> the number actually present in a State Party’s armed forces or in a specified<br />

terri<strong>to</strong>rial unit or subunit.<br />

2 The active-unit overages were significantly increased in late 1999 in part because of the conflict in<br />

Chechnya, <strong>and</strong> in part because the new Russian data declared all flank TLE <strong>to</strong> be in active units, the limits<br />

for which are lower now than under the future limits of an adapted Treaty. In this <strong>and</strong> other matters, Russia<br />

has acted as if the Agreement on Adaptation had already entered in<strong>to</strong> force <strong>and</strong> modified (“adapted”) the<br />

Treaty, but the Agreement has not done so, there is no authority <strong>to</strong> provisionally apply the Agreement in<br />

whole or in part <strong>and</strong> no State Party may unilaterally apply future provisions that are not yet in force.<br />

3 These overage figures do not take in<strong>to</strong> account Russian notifications of temporary deployments in<br />

Armenia, Ukraine, <strong>and</strong> Georgia <strong>and</strong> on Russian terri<strong>to</strong>ry in the original flank -- some of which may no<br />

longer be entirely valid.<br />

43


Nevertheless, there are concerns that Russia may not be declaring properly the<br />

<strong>to</strong>tal number of ACVs in the adapted flank area. First there is the question of APCs that<br />

are being used <strong>to</strong> transport combat infantry squads, but which are claimed improperly <strong>to</strong><br />

be “ambulances” as discussed earlier. A second concern relates vehicles that are being<br />

declared as MT-LBT APC look-alikes but are configured <strong>and</strong> used as MT-LB APCs.<br />

(Physically the only significant <strong>and</strong> readily visible difference between the MT-LB APC<br />

<strong>and</strong> the MT-LBT APC look-alike is that the inside of the MT-LB contains passenger<br />

seats on both sides allowing transport of a full infantry squad, while the MT-LBT<br />

contains artillery ammunition racks instead of seats on the left side, <strong>and</strong> is a <strong>to</strong>wed<br />

artillery primemover <strong>with</strong> seats only for the smaller gun crew. Both versions existed in<br />

the Soviet (<strong>and</strong> Russian) inven<strong>to</strong>ry prior <strong>to</strong> entry in<strong>to</strong> force of the Treaty. According <strong>to</strong><br />

the POET, for 40 months after entry in<strong>to</strong> force of the Treaty, an MT-LB could be<br />

modified in<strong>to</strong> an MT-LBT against reduction obligations by altering the interior of the<br />

vehicle through removal of the left-h<strong>and</strong> combat infantry squad seating <strong>and</strong> the welding<br />

of the ammunition racking <strong>to</strong> the side <strong>and</strong> floor at a minimum of six points. To replace<br />

seats <strong>with</strong> ammunition racks, or vice-versa, is a simple procedure that can be easily<br />

carried out at the holding unit level.) This practice could lead <strong>to</strong> declarations of<br />

artificially lower holdings of ACVs for the units in question <strong>and</strong> for the adapted flank<br />

area as a whole.<br />

a) During a U.S.-led inspection in February 2002, Russian escorts claimed that<br />

some 40 “may have been deployed <strong>to</strong> Chechnya.” Inspec<strong>to</strong>rs observed some 40<br />

ammunition racks of the type used in MT-LBT APC look-alikes stacked in a s<strong>to</strong>rage<br />

shed.<br />

b) On Oc<strong>to</strong>ber 1-2, 2002, a U.S.-led inspection examined more than 60 MT-<br />

LBTs that may have returned from Chechnya. The welds of the ammunition racks of all<br />

of these MT-LBTs appeared <strong>to</strong> have been completed only recently, <strong>and</strong> a few of the<br />

vehicles required additional welds <strong>to</strong> complete the process of modification.<br />

This raises another complex issue. The footnote in the POET that allowed nations<br />

<strong>to</strong> receive credit for “reducing” MT-LB APCs via modification in<strong>to</strong> MT-LBT APC lookalikes<br />

had only a 40-month duration – the 40 months of the CFE reduction period, during<br />

which the groups of states were required <strong>to</strong> destroy or otherwise eliminate equipment in<br />

excess of agreed ceilings according <strong>to</strong> methods specified in the Treaty. The MB-LT<br />

modification allowed a limited exceptional reduction mechanism in order <strong>to</strong> reach limits.<br />

However, the Treaty is silent on what can or must be done <strong>to</strong> eliminate TLE from<br />

accountability beyond the reduction period of the Treaty, which ended in 1995, nor does<br />

it specify how decommissioned items can be disposed of. Accepted practice over the life<br />

of the Treaty after the Treaty reduction period offers some answers. Several NATO allies<br />

have notified reductions below limits that involved TLE being converted <strong>to</strong> other non-<br />

TLE (or even other non-Treaty-reportable) items that would continue <strong>to</strong> be used<br />

militarily, <strong>and</strong> no nation has raised an objection in the CFE Joint Consultative Group<br />

(JCG), the Treaty’s implementation body. Similarly, during recent Russian conversions<br />

of MT-LB vehicles that changed the mix of TLE <strong>and</strong> TLE look-alikes, no nation has<br />

44


pursued a formal objection. What does seem clear, however, is that such changes must<br />

be reflected in annual CFE data, <strong>and</strong>, if involving a change of 10 percent or more in a<br />

unit’s holdings of APCs, they must be formally notified. Russian annual data has<br />

regularly reflected such changes, but timely notifications of 10 percent changes have not<br />

always been made in these cases.<br />

In its data as of January 1, 2001, through that of January 1, 2004, Russia<br />

continued <strong>to</strong> exclude equipment at capital repair facilities in the flank that it characterizes<br />

as “non-combat capable” but which, by the Treaty, must be counted against limits if not<br />

declared as decommissioned. Details are provided below.<br />

A notification accompanying the Russian data as of January 1, 2000 voluntarily<br />

referenced TLE “temporarily introduced” in<strong>to</strong> the adapted flank from outside the AoA.<br />

This information has not been provided in conjunction <strong>with</strong> subsequent data exchanges<br />

<strong>and</strong> notifications on the amount of TLE temporarily located in the adapted flank. In these<br />

subsequent data exchanges <strong>and</strong> notifications, the Russians only referenced TLE<br />

temporarily introduced in<strong>to</strong> the adapted flank, <strong>with</strong> no clarification of how much came<br />

from other locations in the area of application (AoA) or how much came from outside the<br />

AoA. Because no information was provided on the peacetime locations of the TLE<br />

temporarily introduced, it was not possible <strong>to</strong> determine how many of the “temporarily<br />

introduced vehicles” had been added <strong>to</strong> the original flank area or Russian terri<strong>to</strong>ry <strong>with</strong>in<br />

the AoA.<br />

Denial of Full Access During Inspections <strong>and</strong> Improper Site Diagrams. As<br />

reported last year, this recurring problem continued in 2001, when this issue occurred at<br />

least once. However, in 2002 <strong>and</strong> 2003, it has apparently not occurred. In the past, this<br />

infrequent, but recurring, problem has involved a Russian attempt improperly <strong>to</strong> define a<br />

declared site (<strong>and</strong> thus inspection access) on the basis of subordination, rather than<br />

geography (as the Treaty requires). This Russian practice is an issue that has been<br />

discussed in the JCG. The disagreement over the definition of a declared site <strong>and</strong> the<br />

contents of a site diagram has not been resolved. Only Belarus supports the Russian<br />

interpretation; the United States believes it <strong>to</strong> be incorrect.<br />

East of the Urals (EoU) Commitment. As discussed in last year’s Report, the<br />

Russian EoU commitment, as revised by the 1996 Review Conference, called for the<br />

destruction (or conversion in<strong>to</strong> civilian equipment) of 6,000 tanks, 1,500 ACVs, <strong>and</strong><br />

7,000 pieces of artillery “by the year 2000.” Annex E of the Final Document of the First<br />

Conference <strong>to</strong> Review the CFE Treaty allows Russia <strong>to</strong> apply ACVs destroyed in excess<br />

of the 1,500 commitment <strong>to</strong> any shortfall of not more than 2,300 in tanks. However, a<br />

number of tanks equal <strong>to</strong> the shortfall must be subsequently eliminated. Although Russia<br />

had not destroyed or converted the full 6,000 tanks, as of February 24, 2001, Russia had<br />

notified the destruction of a sufficient number of tanks (almost 5,000) <strong>and</strong> excess ACVs<br />

(over 1,500) so as <strong>to</strong> allow it <strong>to</strong> claim the EoU commitment “in general <strong>to</strong> be deemed<br />

completed.” Since then, Russia has continued <strong>to</strong> notify the destruction of additional<br />

tanks. In late spring, 2003, the United States <strong>and</strong> NATO concluded that there was<br />

45


sufficient evidence <strong>to</strong> support Russia’s claim of having fulfilled its entire EoU<br />

commitment. See previous Reports for details of the events leading up <strong>to</strong> this decision.<br />

Violation of Overall Limits for Holdings in Active Units. For several years,<br />

Russian data have shown violations of overall limits in ground TLE in active units.<br />

Russia’s data as of January 1, 2002, showed only an overage above overall active unit<br />

limits in artillery of over 100, but these did not include any of the items notified as being<br />

temporarily in the adapted flank zone (a few tanks, over 175 ACVs, <strong>and</strong> over 40 pieces of<br />

artillery) that may have come from outside the AoA. Russia’s data as of January 1, 2003,<br />

showed overages above overall limits for holdings in active units in tanks of over 125 <strong>and</strong><br />

in artillery of some 270, but did not include any of the items notified as being temporarily<br />

in the adapted flank zone (a few tanks, close <strong>to</strong> 160 ACVs, <strong>and</strong> over 40 pieces of<br />

artillery) that may have come from outside the AoA. One reason for the overage in tanks<br />

probably is that Russia no longer declared Buy as a DPSS, thus adding its declared<br />

holding of over 190 tanks <strong>to</strong> its holdings in active units. Russia’s data as of January 1,<br />

2004 showed holdings in active units in tanks of over 170 <strong>and</strong> in artillery of over 220.<br />

Russia also appears unilaterally <strong>to</strong> have applied the Adapted Treaty limits for overall<br />

holdings of TLE in active units that are greater than the current Treaty limits for such<br />

holdings. However, as noted earlier, Russia has acted as if the Agreement on Adaptation<br />

had already entered in<strong>to</strong> force <strong>and</strong> modified (“adapted”) the Treaty, but the Agreement<br />

has not done so, there is no authority <strong>to</strong> provisionally apply the Agreement in whole or in<br />

part <strong>and</strong> no State Party may unilaterally apply future provisions that are not yet in force.<br />

On the basis for these future limits, Russia’s overall holdings in active units would be<br />

below limits.<br />

Improper Exemption of TLE from Accountability. As reported previously, for<br />

the past few years Russian data have improperly excluded from accountability a<br />

significant number of tanks <strong>and</strong> ACVs that were present at Kushchevskaya <strong>and</strong> St.<br />

Petersburg. Because these tanks <strong>and</strong> ACVs were not properly removed from Russia’s<br />

accountable holdings, they should have been listed as either decommissioned or in<br />

service. Proper accounting of these items would have resulted in Russia having (1)<br />

declared far more decommissioned items than allowed, <strong>and</strong>/or (2) increased overages<br />

above overall limits in active units <strong>and</strong> flank limits. Russian data as of January 1, 2002,<br />

excluded over 10 tanks <strong>and</strong> some 250 ACVs at the two capital repair facilities on these<br />

same improper grounds. As noted earlier, during the first half of 2002, the “non-combat<br />

capable” tanks at St Petersburg were destroyed, but a note in Russia’s data as of July 1,<br />

2002, still showed a few tanks <strong>and</strong> over 250 such ACVs at Kushchevskaya. This same<br />

situation was reflected in Russia’s data as of January 1, 2003, <strong>and</strong> Russia’s flank data as<br />

of July 1, 2003. In the notification on holdings at Kushchevskaya as of Oc<strong>to</strong>ber 1, 2003,<br />

Russia reported a slight decrease in the number of “non-combat-capable” ACVs. This<br />

continued in Russia’s data as of January 1, 2004, <strong>with</strong> only minor changes.<br />

New MT-LB Variants. As previously reported, in a development that had<br />

potential compliance ramifications, the Russians deployed limited numbers of two new<br />

variants of the MT-LB APC, the Kondor <strong>and</strong> the Berkut, in Chechnya as of September<br />

46


24, 2001. Both variants have characteristics of ACVs as defined in Article II of the<br />

Treaty, but neither vehicle is listed in the POET, nor had either been notified as entering<br />

in<strong>to</strong> service <strong>with</strong> the Russian armed forces in the AoA. See previous reports for details.<br />

The United States conducted a declared site inspection of a DPSS in Oc<strong>to</strong>ber<br />

2002 where the Russians briefed the presence of over 90 MT-LB variants <strong>and</strong> declared<br />

them <strong>to</strong> be used exclusively for R&D. The inspection team observed over 70 of the MT-<br />

LB variants, all of which were canvas covered. The escort team chief declared the<br />

remaining MT-LB variants <strong>to</strong> be in a s<strong>to</strong>rage building at the DPSS <strong>to</strong> which he denied the<br />

inspection team access by declaring the building a sensitive point.<br />

However, through November 30, 2003, there had been no notification of Kondors<br />

entering in<strong>to</strong> service nor had Russia notified the presence of these vehicles at any unit. In<br />

December, 2003, Russia notified the entry in<strong>to</strong> service of the MT-LBMB (Kondor) AIFV<br />

<strong>and</strong> the MT-LBMA (Berkut) APC <strong>and</strong> included these vehicles at a naval infantry unit in<br />

its CFE data exchange on December 15, 2003 (as of January 1, 2004). Given that Russia<br />

has interpreted the June 1991 agreement on Naval Infantry/Coastal Defense forces<br />

(NI/CD) as somewhat separate from many Treaty rules relating <strong>to</strong> TLE, earlier absence of<br />

notifications may not be surprising. Russia does not normally notify changes of ten<br />

percent or more in TLE holdings in NI/CD forces, but such changes are incorporated in<br />

holdings declared in the separate Charts on these forces during the annual data exchange.<br />

FINDINGS. Although Russia continues <strong>to</strong> station forces in both Georgia <strong>and</strong><br />

Moldova, Russia has committed <strong>to</strong> the <strong>with</strong>drawal of some (Georgia) or all (Moldova)<br />

Russian TLE <strong>and</strong> forces, <strong>and</strong> has met its commitments in regard <strong>to</strong> TLE in Georgia <strong>and</strong><br />

Moldova, but has failed <strong>to</strong> complete the second part of these commitments in either<br />

Georgia or Moldova. Russia continues <strong>to</strong> refuse <strong>to</strong> declare MT-LB-U APC look-alikes<br />

<strong>and</strong> IRM AIFV look-alikes in data exchanges <strong>and</strong>, in some cases, <strong>to</strong> include them in<br />

inspection briefings. Russia may have failed <strong>to</strong> make Treaty-required notifications of<br />

transfers or reassignment of TLE entering Armenia. Russia again has declared excessive<br />

numbers of decommissioned ground items. Russia remains far over the current Treaty<br />

limits for tanks, ACVs, <strong>and</strong> artillery in active units in the revised flank <strong>and</strong> the current<br />

limits in ACVs for the original flank zone. Russian data <strong>and</strong> notifications now portray<br />

Russia as being in compliance <strong>with</strong> flank limits for the Adapted Treaty. Moreover,<br />

Russia is over its limits for artillery in active units in the AoA. In 2001, Russia again<br />

improperly denied access <strong>to</strong> part of at least one declared site, but has not done so in 2002<br />

or 2003. As noted above, Russia continues <strong>to</strong> manipulate its data by unilaterally <strong>and</strong><br />

improperly excluding some 250 items of TLE as “non-combat capable.” Although<br />

Russia failed <strong>to</strong> complete its CFE-related EoU destruction commitment by the year 2000<br />

as required, Russia did meet most of the terms of that commitment by February 2001 by<br />

an allowed substitution of ACV destructions for shortages in tank destructions – leaving<br />

only a non-time-limited commitment eventually <strong>to</strong> destroy additional tanks equal <strong>to</strong> the<br />

numbers for which excess ACV destructions had been substituted. This was completed<br />

by Spring 2003. Finally, a new potential compliance issue arose in 2001 in regard <strong>to</strong><br />

apparently new variants of the MT-LB APC, but was resolved by the end of 2003.<br />

47


UKRAINE<br />

Active Unit Limits. As noted in previous Reports, Ukrainian data since 1996<br />

have repeatedly indicated that Ukraine was above several of its notified limits for<br />

holdings in active units. In its data as of January 1, 2001, Ukraine no longer had any<br />

overages above overall active unit limits. Ukraine, however, still had overages above<br />

active unit limits in Zone 4.3 of almost 140 tanks <strong>and</strong> close <strong>to</strong> 50 artillery pieces.<br />

Although there are some internal inconsistencies in Ukraine’s data as of January 1, 2002,<br />

it appears <strong>to</strong> show an overage, but only in tanks in active units in Zone 4.3 of some 120.<br />

Ukraine’s data as of January 1, 2003, shows no overage in tanks in active units in Zone<br />

4.3, but an overage of close <strong>to</strong> 20 artillery pieces in holdings in active units in Zone 4.3.<br />

It also shows an overage of some 50 ACVs in active units in Zone 5.1. Ukraine’s data as<br />

of January 1, 2004 showed overages in Zone 5.1 of over 100 APCs. The changes in Zone<br />

4.3 appear <strong>to</strong> be the result of changes in the number of tanks <strong>and</strong> artillery pieces in DPSS,<br />

while the changes in Zone 5.1 appear <strong>to</strong> be the result of transferring SRF ACVs <strong>to</strong> the<br />

conventional armed forces. (ACVs assigned <strong>to</strong> the SRF in Russia, Belarus, <strong>and</strong> Ukraine<br />

are limited in number by a Treaty-related commitment, but do not count against TLE<br />

limits in the conventional armed forces.)<br />

The overages in Zone 4.3 began following the entry in<strong>to</strong> force of the Flank<br />

Document, which removed the Odessa Oblast from the revised flank zone, thereby<br />

adding the equipment in that oblast <strong>to</strong> Zone 4.3.<br />

FINDINGS. Ukraine remains over its limits in active units in Zone 4.3 in tanks.<br />

COLLECTIVE OBLIGATIONS<br />

Naval Infantry/Coastal Defense-related Reductions. Russia <strong>and</strong> Ukraine<br />

shared a legally-binding commitment <strong>to</strong> declare <strong>and</strong> <strong>to</strong> complete Naval Infantry/Coastal<br />

Defense-related (NI/CD) reductions equal <strong>to</strong> those the Soviet Union had committed <strong>to</strong><br />

carry out. In March 2000, Russia completed its remaining share of the NI/CD-related<br />

reduction obligations. Ukraine has not fulfilled its share of the reductions.<br />

There have been no further tangible developments in regard <strong>to</strong> Ukraine on the<br />

issue of the unfulfilled Ukrainian obligation for NI/CD-related reductions (close <strong>to</strong> 160<br />

tanks, some 370 ACVs, <strong>and</strong> over 150 pieces of artillery) that Ukraine shared <strong>with</strong> Russia.<br />

Ukraine continues <strong>to</strong> contend that it should not have <strong>to</strong> carry out these reductions because<br />

it is already in compliance <strong>with</strong> overall limits.<br />

When this issue was raised <strong>with</strong> Ukraine in 2001, the Ukrainians responded <strong>with</strong> a<br />

detailed argument against the reduction obligation. This argument ignored some of the<br />

precise wording of the NI/CD commitment <strong>and</strong>, in the final analysis, differs from the<br />

conclusions <strong>and</strong> interpretations held by the United States <strong>and</strong> (apparently) all other States<br />

Parties except Ukraine. A main thrust of the Ukrainian argument continued <strong>to</strong> be that<br />

Ukraine is fully <strong>with</strong>in all of its overall limits when NI/CD holdings are added <strong>to</strong><br />

48


holdings of conventional armed forces (after having conducted very significant CFE<br />

reductions outside of any theoretical NI/CD-related reduction obligations).<br />

Declaring <strong>and</strong> Meeting the Reduction Obligations of the USSR. There have<br />

been no changes from what was reported in the Oc<strong>to</strong>ber 2, 2000 Report on this issue.<br />

FINDINGS. Ukraine has not yet met its shared NI/CD-related reduction<br />

obligation. In addition, the USSR’s eight CFE successor states have not fulfilled their<br />

collective obligation <strong>to</strong> declare reduction liabilities <strong>and</strong> <strong>to</strong> complete reductions that will,<br />

in the aggregate, be no less than what the USSR would have had <strong>to</strong> declare <strong>and</strong> <strong>to</strong><br />

complete. The majority of the shortfall in reduction liabilities can be attributed <strong>to</strong><br />

Armenia, Azerbaijan, <strong>and</strong> Belarus. However, even if Armenia <strong>and</strong> Azerbaijan were <strong>to</strong><br />

declare <strong>and</strong> <strong>to</strong> complete their maximum putative reduction liabilities <strong>and</strong> Belarus were <strong>to</strong><br />

increase its reduction obligation <strong>to</strong> include tanks awaiting export, there would still be<br />

shortfalls.<br />

C. THE VIENNA DOCUMENTS OF 1992, 1994, AND 1999<br />

On March 4, 1992, the participating States in the Conference on Security <strong>and</strong><br />

Cooperation in Europe (CSCE), including all successor states <strong>to</strong> the Soviet Union,<br />

adopted the Vienna Document 1992 (VD-92), which added <strong>to</strong> <strong>and</strong> built upon the<br />

undertakings in Vienna Document 1990 (VD-90). Subsequently, most of the successor<br />

states of the former Yugoslavia also joined VD-92. In November 1994, at the CSCE<br />

Summit in Budapest, VD-92 was exp<strong>and</strong>ed <strong>and</strong> incorporated in<strong>to</strong> Vienna Document 1994<br />

(VD-94). At that time, the CSCE also changed its name <strong>to</strong> the Organization for Security<br />

<strong>and</strong> Cooperation in Europe (OSCE). During 1999, the participating Parties <strong>to</strong> VD-94<br />

completed discussions <strong>to</strong> update VD-94. Improved provisions were accepted in the<br />

Vienna Document 1999 (VD-99) at the Istanbul Summit in November. The measures<br />

contained in Vienna Documents 1992, 1994, <strong>and</strong> 1999 are politically binding.<br />

The main provisions of the VD include: an exchange of military information,<br />

requirements <strong>to</strong> notify <strong>and</strong> invite observers <strong>to</strong> military exercises above certain thresholds<br />

in personnel <strong>and</strong> equipment, airfield visits, provisions for on-site evaluations of military<br />

units <strong>to</strong> confirm the information on them, provisions for inspections of specified areas <strong>to</strong><br />

determine if an unnotified military activity is going on, <strong>and</strong> other confidence <strong>and</strong> security<br />

building measures (CSBMs).<br />

In general terms, compliance <strong>with</strong> the Vienna Document was good in 2002 <strong>and</strong><br />

2003. During 2002 <strong>and</strong> 2003, 209 VD inspections <strong>and</strong> 145 VD unit evaluations were<br />

conducted by the participating States. These included 27 inspections <strong>and</strong> 52 evaluations<br />

conducted according <strong>to</strong> VD rules under bilateral agreements that offer extra VD quotas <strong>to</strong><br />

the participants. As in the past, however, some VD signa<strong>to</strong>ry nations did not provide<br />

Confidence <strong>and</strong> Security-Building Measures data on time when required in December.<br />

For data as of January 1, 2003, these nations included: Andorra, Icel<strong>and</strong>, Kazakhstan,<br />

Kyrgyzstan, San Marino, Tajikistan, Turkmenistan, <strong>and</strong> Uzbekistan. These data were<br />

49


supposed <strong>to</strong> be distributed on December 13 th in 2002. None of the participating states<br />

that did not provide these data (or nil reports) had corrected the discrepancy by the end of<br />

December. Two other participating States, Georgia <strong>and</strong> Armenia, provided only<br />

unofficial au<strong>to</strong>mated VD data on time, but promised <strong>to</strong> provide hard copy data as soon as<br />

“technical difficulties” were corrected. For data as of January 1, 2004, these nations<br />

included: Bosnia-Herzegovina, Kazakhstan, Kyrgyzstan, Monaco, San Marino,<br />

Turkmenistan, <strong>and</strong> Uzbekistan. These data were supposed <strong>to</strong> be distributed on December<br />

15, 2003. None of the participating states that did not provide data (or nil reports) had<br />

corrected the discrepancy by the end of December. Andorra, Monaco, <strong>and</strong> San Marino<br />

do not have armed forces but should have submitted negative reports. In the past many<br />

such states have provided late data in January.<br />

In addition, several states have not hosted an air base visit. These include:<br />

Albania, Azerbaijan, Bosnia-Herzegovina, Georgia, Kazakhstan, Kyrgyzstan,<br />

Turkmenistan, <strong>and</strong> Uzbekistan. The Vienna Document requires that each participating<br />

state <strong>with</strong> reported air combat units will arrange at least one air base visit during any one<br />

five-year period. The current scheduled five-year period began January 1, 2002.<br />

Two more complex concerns, the Nagorno-Karabakh dispute <strong>and</strong> the nature of<br />

Russia’s military operations in Chechnya, continued <strong>with</strong>out significant change. See<br />

previous Reports for details.<br />

In addition, there have been other -- mostly minor -- notification, data, <strong>and</strong><br />

inspection problems similar <strong>to</strong> those discussed under CFE.<br />

D. THE CHEMICAL WEAPONS CONVENTION (CWC)<br />

As of December 31, 2003, there were 158 States Parties <strong>to</strong> the Convention on the<br />

Prohibition of the Development, Production, S<strong>to</strong>ckpiling <strong>and</strong> Use of Chemical Weapons<br />

<strong>and</strong> on their Destruction, (hereinafter “the CWC”). While the United States has concerns<br />

regarding the activities of other countries, this version of the Report only addresses our<br />

concerns <strong>with</strong> China, Iran, Russia <strong>and</strong> Sudan, as well as the results of our interactions<br />

<strong>with</strong> Libya <strong>to</strong> assist it <strong>to</strong> declare <strong>and</strong> eliminate its CW program.<br />

The United States also has conducted bilateral discussions <strong>with</strong> other States<br />

Parties during this reporting period. These bilateral efforts have been well received <strong>and</strong><br />

useful in laying the groundwork for judging compliance; as a result, the United States has<br />

resolved a number of its CWC compliance concerns.<br />

In this regard, the United States welcomes Albania’s actions upon its discovery of<br />

chemical weapons. The actions undertaken by Albania <strong>to</strong> declare newly discovered<br />

chemical weapons, obtain an extension of its CW destruction deadlines, <strong>and</strong> work<br />

transparently <strong>and</strong> cooperatively <strong>to</strong> ensure the security <strong>and</strong> elimination of chemical<br />

weapon s<strong>to</strong>cks sets a positive precedent for CWC compliance <strong>and</strong> deserves recognition.<br />

50


The United States is working <strong>with</strong> the Albanians <strong>to</strong> ensure the security <strong>and</strong> destruction of<br />

this s<strong>to</strong>ckpile until it is eliminated in accordance <strong>with</strong> the CWC.<br />

The CWC imposes a number of basic obligations upon States Parties. Under the<br />

“general obligations” provisions of Article I, States Parties undertaken not <strong>to</strong> develop,<br />

produce, otherwise acquire, s<strong>to</strong>ckpile, or retain chemical weapons (CW), or <strong>to</strong> transfer<br />

them <strong>to</strong> anyone, directly or indirectly. Article I also obliges Parties <strong>to</strong> “never, under any<br />

circumstances” <strong>to</strong> use chemical weapons, undertake “military preparations” for their use,<br />

or “assist, encourage or induce, in any way, anyone <strong>to</strong> engage in any activity prohibited<br />

<strong>to</strong> a State Party under this Convention.” Additionally, each State Party must destroy all<br />

chemical weapons in its possession or control, or that it ab<strong>and</strong>oned in another country,<br />

<strong>and</strong> must destroy all its chemical weapons production facilities. Parties are also obliged<br />

not <strong>to</strong> use riot control agents (RCAs) as a method of warfare.<br />

Article III imposes additional obligations, specifically by requiring the submission<br />

of detailed declarations of chemical weapons s<strong>to</strong>ckpiles, production facilities, other<br />

related facilities (e.g., labora<strong>to</strong>ries <strong>and</strong> test <strong>and</strong> evaluation sites), <strong>and</strong> types of RCAs<br />

possessed. Specifically, a State Party is required <strong>to</strong> declare, inter alia, whether it:<br />

• Owns or possesses any chemical weapons, or whether there are any chemical<br />

weapons located in any place under its jurisdiction or control;<br />

• Has on its terri<strong>to</strong>ry old or ab<strong>and</strong>oned chemical weapons or has ab<strong>and</strong>oned<br />

chemical weapons on the terri<strong>to</strong>ry of another State;<br />

• Has or has had any chemical weapons production facility under its ownership or<br />

possession, or that is or has been located in any place under its jurisdiction or<br />

control at any time since January 1, 1946;<br />

• Has transferred or received directly or indirectly any equipment for the production<br />

of chemical weapons since January 1, 1946;<br />

• Has any facility or establishment under its ownership or possession, or located in<br />

any place under its jurisdiction or control, that has been designed, constructed or<br />

used since January 1, 1946, primarily for the development of chemical weapons;<br />

<strong>and</strong>,<br />

• Holds chemicals for riot control purposes.<br />

Countries that were original States Parties <strong>to</strong> the CWC were required <strong>to</strong> submit<br />

their initial data declaration not later than 30 days after entry in<strong>to</strong> force. Countries that<br />

ratified after the CWC entered in<strong>to</strong> force, or acceded, became States Parties 30 days after<br />

the deposit of their instrument of ratification or accession <strong>and</strong> were required <strong>to</strong> submit<br />

their initial data declaration 30 days after becoming a State Party. Articles IV <strong>and</strong> V, <strong>and</strong><br />

the corresponding parts of the Verification Annex provide detailed requirements<br />

51


governing the implementation of the obligations on the destruction of chemical weapons<br />

<strong>and</strong> production facilities.<br />

Article VI of the CWC makes clear that each State Party has “the right, subject <strong>to</strong><br />

the provisions of this Convention, <strong>to</strong> develop, produce, otherwise acquire, retain, transfer<br />

<strong>and</strong> use <strong>to</strong>xic chemicals <strong>and</strong> their precursors for purposes not prohibited under this<br />

Convention.” It thus makes clear that – even if the formal declaration <strong>and</strong> verification<br />

provisions of the CWC are followed – States Parties have no right <strong>to</strong> have or <strong>to</strong> deal in<br />

<strong>to</strong>xic chemicals or their precursors if their purpose in so doing is one that is prohibited<br />

under this Convention (e.g., <strong>to</strong> acquire chemical weapons or in any way <strong>to</strong> assist,<br />

encourage, or induce another <strong>to</strong> do so). Article VI also imposes specific obligations <strong>with</strong><br />

respect <strong>to</strong> controlling specific chemicals listed in Schedules 1, 2, <strong>and</strong> 3 of the Annex on<br />

Chemicals – as well as facilities related <strong>to</strong> such scheduled chemicals – <strong>and</strong> subjects these<br />

chemicals <strong>to</strong> verification measures provided in the Convention’s Verification Annex.<br />

The Organization for the Prohibition of Chemical Weapons (OPCW) was<br />

established pursuant <strong>to</strong> the CWC in order, among other things, <strong>to</strong> “ensure the<br />

implementation of its provisions, including those for international verification of<br />

compliance <strong>with</strong> it.” Under Article VIII, the Conference of States Parties is authorized <strong>to</strong><br />

“review compliance” <strong>with</strong> the CWC, <strong>and</strong> is <strong>to</strong> “[t]ake the necessary measures <strong>to</strong> ensure<br />

compliance <strong>with</strong> this Convention <strong>and</strong> <strong>to</strong> redress <strong>and</strong> remedy any situation which<br />

contravenes the provisions of this Convention, in accordance <strong>with</strong> Article XII.” Article<br />

XII, in turn, provides that the Conference may, inter alia, “restrict or suspend” a viola<strong>to</strong>r<br />

State’s “rights <strong>and</strong> privileges” under the CWC until compliance resumes. In “cases of<br />

particular gravity,” the Conference can bring the issue <strong>to</strong> the attention of the United<br />

Nations Security Council <strong>and</strong> General Assembly.<br />

For its part, both as a matter of national policy <strong>and</strong> as a guide <strong>to</strong> national policy,<br />

the United States undertakes its own independent review – based upon the best available<br />

information, including intelligence information – of the compliance of CWC States<br />

Parties <strong>with</strong> their obligations under the Convention. The United States believes that<br />

States Parties should be held <strong>to</strong> their obligations under the CWC, <strong>and</strong> places a high<br />

premium upon their compliance both <strong>with</strong> specific detailed declaration <strong>and</strong><br />

implementation provisions (e.g., Article III, IV, <strong>and</strong> V) <strong>and</strong> <strong>with</strong> the “general<br />

obligations” of Article I.<br />

U.S. compliance assessments under the CWC focus upon the degree <strong>to</strong> which<br />

States Parties fulfil not only their detailed declaration <strong>and</strong> destruction/conversion<br />

obligations under Articles III through V, but also their “general obligations” under<br />

Article I. Information tending <strong>to</strong> show that chemical weapons have actually been used, or<br />

that a State Party has helped or encouraged anyone <strong>to</strong> engage in any activity prohibited <strong>to</strong><br />

a State Party under this Convention (e.g., by helping another country, or a non-state ac<strong>to</strong>r<br />

such as an international terrorist entity, acquire chemical weapons) would thus be highly<br />

relevant <strong>to</strong> an Article I compliance finding.<br />

52


The United States also believes that because of their obligation under<br />

subparagraph (1)(d) of Article I which requires States Parties not in any way <strong>to</strong> assist,<br />

encourage, or induce others <strong>to</strong> acquire chemical weapons, States Parties are under an<br />

obligation <strong>to</strong> exercise due diligence in their trade in precursor chemicals <strong>and</strong> dual-use<br />

equipment that could be employed in the development of chemical weapons. In<br />

particular, States Parties should exercise restraint in their dealings <strong>with</strong> recipient entities,<br />

<strong>and</strong> should not undertake any potentially CW-related transfers of technology or<br />

chemicals <strong>to</strong> any entity about which there is a reasonable suspicion that it is engaged, or<br />

seeks <strong>to</strong> be engaged, in the development, production, s<strong>to</strong>ckpiling, or use of chemical<br />

weapons in any way that would be prohibited <strong>to</strong> a State Party <strong>to</strong> the CWC.<br />

Moreover, under paragraph 5 of Article V of the CWC, a State Party may not<br />

“construct any new chemical weapons production facilities or modify any existing<br />

facilities for the purpose of chemical weapons production or for any other activity”<br />

prohibited by the CWC. This focus upon the purpose for which construction or<br />

modification occurs indicates that whether or not prohibited quantities of banned or<br />

controlled chemicals are actually present, the development <strong>and</strong> maintenance of a CW<br />

mobilization capability would amount <strong>to</strong> noncompliance <strong>with</strong> the Convention if it were<br />

undertaken <strong>with</strong> such CW applications in mind. In judging such CW mobilization intent,<br />

where more direct evidence is unavailable, a number of fac<strong>to</strong>rs may be relevant,<br />

including: the country’s record of CWC compliance in other respects; the accuracy <strong>and</strong><br />

completeness of its declarations; its his<strong>to</strong>ry of CW-related activity; the legitimate<br />

economic or commercial need for chemicals the production of which requires the<br />

development of processes easily adaptable for CW production; <strong>and</strong> the degree <strong>to</strong> which<br />

production methods it adopts diverge in otherwise inexplicable ways from industry<br />

practice, or are uneconomical or implausibly inefficient in peaceful applications.<br />

Finally, the United States notes that subparagraph 9(b) of Article II expressly<br />

permits possession of chemical agents for “[p]rotective purposes, namely those purposes<br />

directly related <strong>to</strong> protection against <strong>to</strong>xic chemicals <strong>and</strong> <strong>to</strong> protection against chemical<br />

weapons.” By contrast, subparagraph 1(c) of Article I prohibits engaging in “any<br />

military preparations <strong>to</strong> use chemical weapons.” Part VI, Section (A) of the Verification<br />

Annex spells out in more detail which activities are permitted under the CWC, making<br />

clear that a State Party may not “produce, acquire, retain, transfer or use” Schedule 1<br />

chemicals unless they are applied <strong>to</strong> legitimate “research, medical, pharmaceutical or<br />

protective purposes,” <strong>and</strong> possessed only in small quantities “strictly limited <strong>to</strong> those<br />

which can be justified for such purposes” but in no circumstances more than one metric<br />

<strong>to</strong>n. Part VI, Section C of the Verification Annex specifies allowable production<br />

quantities at declared <strong>and</strong> undeclared facilities, but it does not alter the basic rule that<br />

purpose is the <strong>to</strong>uchs<strong>to</strong>ne of compliance <strong>with</strong> regard <strong>to</strong> research quantities of chemical<br />

agents. Appropriately-scaled research undertaken for legitimate protective purposes<br />

against chemical weaponry is thus permitted, but research aimed at developing or<br />

improving weapons applications would constitute noncompliance. It should be noted,<br />

moreover, that under subparagraph 1(c) of Article I there is no requirement that “military<br />

preparations <strong>to</strong> use chemical weapons” actually involve chemical agents. Accordingly,<br />

53


esearch undertaken for the purpose of facilitating weapons uses rather than for protective<br />

purposes would constitute a violation of the CWC whether or not chemical agents were<br />

involved. (Research using CW agent simulants or CW munitions development, for<br />

example, would thus present noncompliance problems if undertaken for weapons, <strong>and</strong> not<br />

protective, purposes.)<br />

COUNTRY ASSESSMENTS<br />

CHINA<br />

ISSUE. The issue is whether China maintains an active offensive CW research<br />

<strong>and</strong> development (R&D) program, has a CW production mobilization capability, <strong>and</strong> has<br />

made inaccurate declarations regarding its past transfer of chemical weapons <strong>and</strong><br />

undeclared CW-related facilities.<br />

HISTORY OF COMPLIANCE EVALUATION. The Peoples Republic of China<br />

(PRC) submitted its initial declaration <strong>to</strong> the OPCW on time in 1997 but the United<br />

States was not initially given a complete copy of the Chinese declaration upon which <strong>to</strong><br />

base a compliance judgment. As a result of a comprehensive review of the Chinese<br />

declaration, the United States entered in<strong>to</strong> a dialogue <strong>with</strong> the Chinese in December 1998<br />

highlighting our concerns about anomalies <strong>and</strong> shortcomings in its declaration. As noted<br />

in the CY1999 unclassified version of the NCR, the United States continued<br />

unsuccessfully <strong>to</strong> press China for a response <strong>to</strong> our concerns, stating that “until the<br />

United States received <strong>and</strong> evaluated the Chinese response, a compliance judgment is not<br />

possible.” The finding in the unclassified version of the June 2003 Report stated that:<br />

The United States assesses that China maintains an active offensive R&D<br />

CW program, a possible undeclared CW s<strong>to</strong>ckpile, <strong>and</strong> CW-related<br />

facilities that were not declared. Such activities are inconsistent <strong>with</strong> the<br />

CWC.<br />

DISCUSSION OF OBLIGATIONS. China is an original State Party <strong>to</strong> the CWC,<br />

<strong>and</strong> submitted its initial declaration on time. In this initial declaration, China declared<br />

that it had eliminated facilities, s<strong>to</strong>ckpile <strong>and</strong> materials relating <strong>to</strong> CW. However, it said<br />

that it maintained a defensive research <strong>and</strong> development capability in accordance <strong>with</strong> the<br />

Convention. The Chinese chemical industry has the capability <strong>to</strong> produce many<br />

chemicals, some of which have been sought by states trying <strong>to</strong> develop a chemical<br />

warfare capability.<br />

ACTIONS. China continues <strong>to</strong> conduct CW research <strong>and</strong> development that has<br />

applications for either defensive or offensive purposes. China also has the capability <strong>to</strong><br />

quickly mobilize its chemical industry <strong>to</strong> produce a wide variety of chemical agents.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. Since 1998, the<br />

United States <strong>and</strong> China have been in a dialogue regarding CWC compliance issues. The<br />

54


United States have discussed a number of these issues between experts, in written<br />

communiqués, <strong>and</strong> in the ongoing U.S.–China Security dialogues. As a result of these<br />

contacts, we have improved our underst<strong>and</strong>ing of the Chinese initial declaration. That<br />

said, however, concerns remain <strong>and</strong> the dialogue continues.<br />

FINDING. The United States judges that China maintains a CW production<br />

mobilization capability, although there is insufficient information available <strong>to</strong> determine<br />

whether it maintains an active offensive CW research <strong>and</strong> development program.<br />

Moreover, in violation of its CWC obligations, China has not acknowledged past<br />

transfers of chemical weapons <strong>and</strong> it may not have declared the full extent of its CWrelated<br />

facilities.<br />

IRAN<br />

ISSUE. The United States is concerned that Iran is retaining <strong>and</strong> modernizing key<br />

elements of its CW infrastructure, <strong>to</strong> include: offensive research <strong>and</strong> development; a<br />

possible undeclared s<strong>to</strong>ckpile; <strong>and</strong> an offensive production capability.<br />

HISTORY OF COMPLIANCE EVALUATION. The United States assessed<br />

Iranian compliance as early as the CY1998 NCR. At that time, the United States was<br />

unable <strong>to</strong> certify Iran <strong>to</strong> be in compliance <strong>with</strong> the CWC because of concerns about its<br />

initial declaration <strong>and</strong> the need <strong>to</strong> assess Iran’s supplemental declaration. Because of<br />

continued U.S. concerns about Iran’s declaration, the Oc<strong>to</strong>ber 2, 2000 Report made the<br />

same compliance judgment. The finding in the unclassified version of the June 2003<br />

Report stated that:<br />

The United States assesses that Iran has not submitted a complete <strong>and</strong><br />

accurate declaration, <strong>and</strong> in fact is acting <strong>to</strong> retain <strong>and</strong> modernize key<br />

elements of its CW program. Some of these elements include an offensive<br />

R&D CW program, an undeclared s<strong>to</strong>ckpile <strong>and</strong> an offensive production<br />

capability. Such activities are inconsistent <strong>with</strong> the CWC.<br />

DISCUSSION OF OBLIGATIONS. Iran became a State Party <strong>to</strong> the CWC on<br />

December 3, 1997. The United States received the first part of Iran’s initial declaration<br />

from the OPCW in December 1998. Iran’s declaration arrived piecemeal <strong>with</strong> another<br />

submission received by the United States in July 1999.<br />

ACTIONS. In May 1998, during the Conference of the States Parties, Tehran, for<br />

the first time, acknowledged the existence of a past chemical weapons program. Iran<br />

admitted developing a chemical warfare program during the latter stages of the Iran-Iraq<br />

war, as a deterrent against Iraq’s use of chemical agents. Moreover, Tehran claimed that<br />

after the 1988 cease-fire, it “terminated” its CW program. Despite this revelation, Iran<br />

has not acknowledged actually possessing chemical weapons. The United States believes<br />

Iran has manufactured <strong>and</strong> s<strong>to</strong>ckpiled blister, blood, <strong>and</strong> choking chemical agents, <strong>and</strong><br />

weaponized some of these agents in<strong>to</strong> artillery shells, mortars, rockets, <strong>and</strong> aerial bombs.<br />

55


We continue <strong>to</strong> believe that Iran has not acknowledged the full extent of its chemical<br />

weapons program, that it has indigenously produced several first-generation CW agents<br />

(blood, blister, <strong>and</strong> choking agents), <strong>and</strong> that it has the capability <strong>to</strong> produce traditional<br />

nerve agents. However, the size <strong>and</strong> composition of any Iranian s<strong>to</strong>ckpile is not known.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. The United States,<br />

on the margins of the OPCW Executive Council meeting on June 27-28, 2001, delivered<br />

written questions <strong>to</strong> the Iranian delegation seeking <strong>to</strong> clarify gaps <strong>and</strong> inconsistencies in<br />

Iran’s CWC declaration. The Iranians accepted the U.S. questions <strong>with</strong> the<br />

underst<strong>and</strong>ing that they were asked in accordance <strong>with</strong> Article IX of the CWC.<br />

In February 2002, Iran responded <strong>to</strong> U.S. questions. Iran also provided its A-2<br />

form <strong>to</strong> the OPCW Technical Secretariat. This form, however, still did not declare the<br />

possession of chemical weapons.<br />

FINDING. The United States judges that Iran is in violation of its CWC<br />

obligations because Iran is acting <strong>to</strong> retain <strong>and</strong> modernize key elements of its CW<br />

infrastructure <strong>to</strong> include an offensive CW R&D capability <strong>and</strong> dispersed mobilization<br />

facilities.<br />

LIBYA<br />

ISSUE. As of December 31, 2003, Libya was not a State Party <strong>to</strong> the Chemical<br />

Weapons Convention, but we are addressing Libya’s chemical weapons activity because<br />

of its December 2003 commitment <strong>to</strong> disb<strong>and</strong> its WMD programs <strong>and</strong> <strong>to</strong> accede <strong>to</strong> the<br />

CWC. Libya acceded <strong>to</strong> the CWC on January 6, 2004, <strong>and</strong> became a State Party<br />

effective February 5, 2004. Libya had been publicly known <strong>to</strong> have a chemical weapons<br />

program.<br />

HISTORY OF COMPLIANCE EVALUATION. This is the first time that<br />

Libya has been discussed in the CWC section of this Report.<br />

DISCUSSION OF OBLIGATIONS. On December 19, 2003, Col. Muammar<br />

Qadhafi pledged <strong>to</strong> eliminate material <strong>and</strong> equipment related <strong>to</strong> Libya’s pursuit of WMD<br />

<strong>and</strong> long-range missile systems. Among other things, he confirmed that Libya would<br />

accede <strong>to</strong> Chemical Weapons Convention. Libya subsequently acceded <strong>to</strong> the CWC.<br />

ACTIONS. In March 2003, Libya approached the United Kingdom <strong>and</strong> United<br />

States, expressing interest in removing concerns about whether it was pursuing WMD<br />

programs. In the course of subsequent discussions <strong>and</strong> visits, the Libyans made<br />

significant disclosures about their chemical weapons programs, as well as other WMD<br />

activities. The United States <strong>and</strong> the United Kingdom conducted a number of exchanges<br />

<strong>with</strong> the Libyans intended <strong>to</strong> explore the depth <strong>and</strong> commitment of their initiative. A<br />

team of American <strong>and</strong> British experts traveled <strong>to</strong> Libya twice – in Oc<strong>to</strong>ber <strong>and</strong> December<br />

2003 <strong>to</strong> receive detailed presentations on Libya’s nuclear, chemical, biological, <strong>and</strong><br />

56


missile activities. In addition <strong>to</strong> extensive discussion during a <strong>to</strong>tal of three weeks of<br />

meetings, the experts were shown covert facilities <strong>and</strong> equipment <strong>and</strong> were <strong>to</strong>ld about<br />

years of Libyan efforts <strong>to</strong> develop chemical weapons capabilities. With regard <strong>to</strong><br />

chemical issues, Libya showed these initial U.S./UK teams:<br />

• A significant quantity of sulfur mustard chemical agent that was produced at the<br />

Pharma 150 plant near Rabta more than a decade previously;<br />

• Aerial bombs that were designed <strong>to</strong> be filled <strong>with</strong> mustard agent on short notice;<br />

• Equipment in s<strong>to</strong>rage that could be used <strong>to</strong> outfit a second CW production<br />

facility; <strong>and</strong><br />

• Dual-use chemical precursors that could be used <strong>to</strong> produce mustard <strong>and</strong> nerve<br />

agent.<br />

During these visits, Libya reiterated its commitment <strong>to</strong> complete its accession <strong>to</strong> the<br />

Chemical Weapons Convention, <strong>and</strong> committed <strong>to</strong> destroy all its chemical warfare<br />

s<strong>to</strong>ckpiles <strong>and</strong> munitions.<br />

In March 2004, Libya destroyed all of its declared unfilled chemical munitions<br />

<strong>and</strong> secured all sensitive CW materials, agents, <strong>and</strong> equipment pending their elimination<br />

under the CWC.<br />

UCOMPLIANCE-RELATED DIALOGUE AND ANALYSISU. As 2003 ended, the<br />

United States <strong>and</strong> the United Kingdom prepared <strong>to</strong> launch an intensive joint effort <strong>to</strong><br />

verify Libya’s compliance <strong>with</strong> its commitments of December 19, 2003.<br />

The December 2003 commitment led directly <strong>to</strong> Libya’s accession <strong>to</strong> the CWC on<br />

January 6, 2004, <strong>and</strong> <strong>to</strong> its agreement <strong>to</strong> a series of overt visits in 2004 by U.S. <strong>and</strong><br />

United Kingdom technical experts aimed at ascertaining the nature <strong>and</strong> scope of Libya’s<br />

past CW activity <strong>and</strong> ensuring the termination of its CW program. As a result of this<br />

transparent <strong>and</strong> cooperative process, Libya destroyed all of its declared unfilled chemical<br />

munitions in March 2004, <strong>and</strong> secured all sensitive CW materials, agents, <strong>and</strong> equipment<br />

pending their elimination under the CWC.<br />

UFINDINGU. The United States believes Libya’s disclosure regarding its chemical<br />

weapons program, <strong>and</strong> its December 2003 commitment <strong>to</strong> accede <strong>to</strong> the CWC <strong>and</strong><br />

disb<strong>and</strong> such weapons is a significant step <strong>to</strong>ward coming in<strong>to</strong> full compliance, <strong>and</strong> a<br />

model for those countries that remain outside the CWC. The United States will continue<br />

<strong>to</strong> work closely <strong>with</strong> the Libyans <strong>to</strong> clarify any remaining concerns both through the<br />

OPCW, <strong>and</strong> the Trilateral Steering Cooperation Committee’s Chemical Weapons Sub-<br />

Committee.<br />

57


RUSSIA<br />

ISSUE. The principal issue is whether Russia’s CWC declaration is adequate as it<br />

relates <strong>to</strong> CW production <strong>and</strong> development facilities, chemical agent <strong>and</strong> weapons<br />

s<strong>to</strong>ckpiles, <strong>and</strong> whether Russia has met the CWC-established timelines for submission of<br />

plans for destruction <strong>and</strong> verification of destruction of its CW.<br />

HISTORY OF COMPLIANCE EVALUATION. The United States assessed<br />

Russia’s CWC compliance as early as the unclassified CY1998 NCR. In that Report, the<br />

United States noted a number of issues <strong>and</strong> concerns <strong>with</strong> Russia’s declaration, <strong>and</strong> that it<br />

could not certify Russia as being in compliance <strong>with</strong> the CWC. Similarly, in the CY1999<br />

Report, Russia could not be certified as CWC compliant until the U.S. questions <strong>and</strong><br />

concerns had been addressed <strong>and</strong> resolved. The finding in the June 2003 Report stated<br />

that:<br />

Although the United States continues <strong>to</strong> engage the Russian Federation on<br />

these <strong>and</strong> other issues <strong>with</strong> some progress, it is our assessment that the<br />

Russian Federation has not divulged the full extent of their chemical agent<br />

<strong>and</strong> weapon inven<strong>to</strong>ry. We assess their declaration <strong>to</strong> be incomplete <strong>with</strong><br />

respect <strong>to</strong> CW production, development facilities <strong>and</strong> chemical agent <strong>and</strong><br />

weapons s<strong>to</strong>ckpiles. Such activities are inconsistent <strong>with</strong> the CWC.<br />

DISCUSSION OF OBLIGATIONS. The Russian Federation became a State<br />

Party <strong>to</strong> the CWC on December 5, 1997, <strong>and</strong> submitted its initial declaration on time.<br />

The Russian declaration included CW production facilities (CWPFs), CW s<strong>to</strong>rage<br />

facilities (CWSFs), a development facility, <strong>and</strong> a s<strong>to</strong>ckpile of approximately 40,000<br />

metric <strong>to</strong>ns of CW agent.<br />

ACTIONS. The United States has longst<strong>and</strong>ing concerns about the completeness<br />

<strong>and</strong> accuracy of Russia’s CW s<strong>to</strong>ckpile declaration. As early as August 1999, the United<br />

States sought clarification of certain issues regarding the Russian CW s<strong>to</strong>ckpile <strong>and</strong><br />

raised a variety of other compliance concerns such as CW production, s<strong>to</strong>rage, <strong>and</strong><br />

development facilities. A regular bilateral dialogue on such subjects continues <strong>to</strong> this<br />

day, <strong>and</strong> U.S. officials continue <strong>to</strong> stress <strong>with</strong> their senior Russian counterparts the<br />

importance of resolving concerns about the Russian s<strong>to</strong>ckpile.<br />

In becoming a State Party <strong>to</strong> the CWC, Russia accepted legal obligations <strong>to</strong><br />

destroy its CW s<strong>to</strong>ckpile <strong>and</strong> <strong>to</strong> forego the development or possession of CW. In May<br />

1997, the Duma passed, <strong>and</strong> President Yeltsin signed, the Russian Federal Law on<br />

Chemical Weapons Destruction, approving implementation of the 1996 destruction plan.<br />

The Russians provided additional details on <strong>and</strong> changes <strong>to</strong> their destruction plan in June<br />

2002 <strong>and</strong> 2003. In recent years, Russia has taken steps <strong>to</strong> strengthen its CW destruction<br />

program, <strong>and</strong> has significantly increased funding for this program, although admittedly<br />

from a low starting point. For both financial <strong>and</strong> bureaucratic reasons, progress <strong>to</strong>ward<br />

fulfilling Russia’s CWC obligations has been slow, <strong>and</strong> senior-level Russian policy<br />

58


statements regarding Russia’s general commitment <strong>to</strong> destroy its CW s<strong>to</strong>cks remain<br />

largely unimplemented. As a result, Russia has requested extensions on its CW<br />

destruction deadlines from the OPCW. With international assistance, Russia in April<br />

2003 completed the destruction of one percent of its Category 1 CW s<strong>to</strong>ckpile three years<br />

after the original CWC deadline for completing such destruction.<br />

The United States believes the Russian-proposed extended deadlines remain very<br />

optimistic <strong>and</strong> that it will be difficult for Russia <strong>to</strong> meet them <strong>with</strong>out a practical plan.<br />

The United States further believes that Russia’s CWC declaration is incomplete, <strong>and</strong> that<br />

Russia failed fully <strong>to</strong> declare its CW s<strong>to</strong>ckpile <strong>and</strong> CW-related facilities, including some<br />

related <strong>to</strong> production <strong>and</strong> development. In addition, Russia may maintain CW<br />

mobilization capacities. Moscow television commentary, for instance, related <strong>to</strong> a July<br />

1998 OPCW inspection of the Khimprom CWPF in Novocheboksarsk noted that, “in line<br />

<strong>with</strong> safety regulations, the so-called mobilization capacities are being maintained. This<br />

is costing Khimprom vast sums of money even though this is a matter for the federal<br />

government.”<br />

The Russian declared chemical warfare agent inven<strong>to</strong>ry that is awaiting<br />

destruction consists of a comprehensive array of blister, choking, <strong>and</strong> nerve agents in<br />

weaponized <strong>and</strong> bulk form. In addition, since 1992, Russian scientists familiar <strong>with</strong><br />

Moscow’s chemical warfare development program have been publicizing information on<br />

a new generation of agents, sometimes referred <strong>to</strong> as “Novichoks.” These scientists<br />

report that these compounds, some of which are binary agents, were designed <strong>to</strong><br />

circumvent the Chemical Weapons Convention <strong>and</strong> <strong>to</strong> defeat Western detection <strong>and</strong><br />

protection measures. Furthermore, it is believed that their production can be hidden<br />

<strong>with</strong>in commercial chemical plants. There is concern that the technology <strong>to</strong> produce<br />

these compounds might be acquired by other countries.<br />

The United States <strong>and</strong> other States Parties also voiced their opposition <strong>to</strong> Russia<br />

regarding destruction of Russian Category 2 chemical weapons at a facility that was not<br />

designated for CW destruction as required by the CWC.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. Since Oc<strong>to</strong>ber<br />

2000, the United States <strong>and</strong> Russia have met at the expert <strong>and</strong> senior levels on several<br />

occasions <strong>to</strong> discuss Russia’s CW s<strong>to</strong>ckpile declaration. The consultations have been<br />

cordial, but little progress has been made. In February 2002, the United States presented<br />

questions on the accountability of Russia’s CW s<strong>to</strong>ckpile, <strong>and</strong> proposed a plan that<br />

included a series of non-reciprocal, short-notice visits <strong>with</strong> unimpeded access <strong>to</strong><br />

undeclared suspect Russian CW sites. To date, Russia has only agreed <strong>to</strong> site visits at<br />

declared CW s<strong>to</strong>rage <strong>and</strong> destruction facilities. We have indicated that our concern is not<br />

<strong>with</strong> declared facilities, but <strong>with</strong> sites that were not declared under the CWC (but should<br />

have been).<br />

In response <strong>to</strong> U.S. questions, Russia provided some additional information <strong>and</strong><br />

offered U.S. experts the opportunity <strong>to</strong> review his<strong>to</strong>rical documentation used <strong>to</strong> prepare<br />

59


its s<strong>to</strong>ckpile declaration. A team of U.S. experts visited Moscow in December 2002 <strong>to</strong><br />

review such documentation, but Russia knowingly provided only documents already<br />

available <strong>to</strong> the United States <strong>and</strong> other CWC States Parties through the OPCW. In<br />

response, the U.S. team pointed out the potential impact of Russian actions as it relates <strong>to</strong><br />

U.S. Congressional funding for its CW destruction program, <strong>and</strong> further noted the<br />

seriousness of such uncooperative methods.<br />

During 2002, the United States engaged in numerous exchanges <strong>with</strong> Russia<br />

regarding a number of compliance issues, specifically the conditions imposed by the U.S.<br />

Congress that halted Cooperative Threat Reduction (CTR) funding for construction of a<br />

chemical weapons destruction facility in Shchuch’ye. During this dialogue, the United<br />

States proposed an approach <strong>to</strong> address <strong>and</strong> resolve concerns over Russia’s CW s<strong>to</strong>ckpile.<br />

In order <strong>to</strong> gain a sufficient level of confidence that our concerns <strong>with</strong> Russia’s CW<br />

s<strong>to</strong>ckpile are adequately addressed, the United States developed a two-fold approach that<br />

included: (1) providing specific detailed questions on aspects of Russia’s CWC<br />

declaration regarding its CW s<strong>to</strong>ckpile <strong>and</strong> (2) requesting a series of short-notice visits <strong>to</strong><br />

suspect facilities. The practical objective of this initiative was <strong>to</strong> work <strong>with</strong> Russia <strong>to</strong><br />

gain the appropriate information that will affect our confidence level, either positively or<br />

negatively, <strong>with</strong> regard <strong>to</strong> U.S. concerns regarding Russia’s CW s<strong>to</strong>ckpile.<br />

To further address these <strong>and</strong> other concerns, the United States <strong>and</strong> Russia held<br />

consultations in September 2003, during which Russian officials agreed <strong>to</strong> provide or<br />

authorize the OPCW Technical Secretariat <strong>to</strong> h<strong>and</strong> over documents, if available,<br />

regarding CW demilitarization activities at former CW production facilities, which could<br />

help address questions regarding CW s<strong>to</strong>ckpiles. To facilitate this process, the United<br />

States provided a list of OPCW documents in which references appeared <strong>to</strong> Russian<br />

documents. In June 2004, however, Russia claimed that the referenced documents had<br />

already been destroyed pursuant <strong>to</strong> its document retention policy. Russia also indicated<br />

that the United States needed further <strong>to</strong> justify its proposal for short-notice site visits <strong>to</strong><br />

undeclared sites <strong>and</strong> insisted – despite the apparent lack of corresponding concerns about<br />

U.S. compliance – that such visits be carried out on a reciprocal basis. Nevertheless,<br />

despite these tactics, Russia continues <strong>to</strong> insist that it does not possess any undeclared<br />

chemical weapons s<strong>to</strong>cks.<br />

The United States intends <strong>to</strong> address these concerns, based on current assessments<br />

of the completeness <strong>and</strong> accuracy of Russia’s chemical weapons s<strong>to</strong>ckpile declaration,<br />

through a combination of gathering corroborating information, encouraging Russian<br />

cooperation <strong>and</strong> transparency, continuing bilateral expert consultations, <strong>and</strong>, where<br />

appropriate, seeking Russian agreement <strong>to</strong> a U.S. proposal that would allow for shortnotice<br />

visits, <strong>with</strong> unimpeded access, <strong>to</strong> undeclared suspect Russian CW sites.<br />

On CW development facilities, the United States assesses that Russia did not<br />

declare all of its development facilities as required under Article III (1)(d) of the<br />

Convention, which obligates States Parties <strong>to</strong> declare any facility or establishment under<br />

its ownership or possession, or located in any place under its jurisdiction or control, <strong>and</strong><br />

60


that has been designed, constructed, or used since January 1, 1946 primarily for<br />

development of chemical weapons. Judged by this st<strong>and</strong>ard, the United States judges that<br />

Russia did not declare the required number of CW development facilities operational<br />

between 1946 <strong>and</strong> 1960, a time when the majority of development work on CW agents in<br />

the Russian declared s<strong>to</strong>ckpile likely <strong>to</strong>ok place. During bilateral discussions <strong>with</strong> the<br />

United States, <strong>and</strong> ongoing debate at the OPCW Executive Council meetings concerning<br />

this issue, Russia has continued <strong>to</strong> take the position that until a decision by the Council is<br />

agreed on how more specifically <strong>to</strong> define the term “primarily for”, the Russian<br />

declaration remains consistent <strong>with</strong> its treaty obligations.<br />

CW Destruction at an Undeclared Facility. In March 2002, the Direc<strong>to</strong>r<br />

General of the OPCW Technical Secretariat announced that phosgene drained from 3,844<br />

artillery shells at Shchuch’ye <strong>and</strong> sent <strong>to</strong> a commercial facility for processing had been<br />

completely destroyed under OPCW supervision. However, Russia had never received<br />

formal OPCW approval <strong>to</strong> process the drained phosgene at the commercial site in<br />

question, <strong>and</strong> did not designate that facility as a CW destruction facility as required by<br />

the CWC. Despite these failures, however, the processing of the phosgene was done<br />

under continuous moni<strong>to</strong>ring by OPCW inspec<strong>to</strong>rs.<br />

Not<strong>with</strong>st<strong>and</strong>ing the presence of OPCW inspec<strong>to</strong>rs, the United States <strong>and</strong> other<br />

States Parties at that time maintained that the phosgene should have been destroyed<br />

pursuant <strong>to</strong> the requirements of Article IV <strong>and</strong> Part IV(A) of the CWC.<br />

FINDING. The United States judges that Russia is in violation of its CWC<br />

obligations because its CWC declaration was incomplete <strong>with</strong> respect <strong>to</strong> declaration of<br />

production <strong>and</strong> development facilities, <strong>and</strong> declaration of chemical agent <strong>and</strong> weapons<br />

s<strong>to</strong>ckpiles.<br />

SUDAN<br />

ISSUE. Sudan did not declare any CW-related work or capabilities. The issue is<br />

whether Sudan was in the past, <strong>and</strong> continues <strong>to</strong> be, involved in CW programs <strong>and</strong><br />

possible use of CW agents.<br />

HISTORY OF COMPLIANCE EVALUATION. The United States first assessed<br />

Sudan’s CWC compliance in the Oc<strong>to</strong>ber 2, 2000 Report. In that Report, the United<br />

States noted that Sudan has been interested in acquiring a chemical warfare capability<br />

since the 1980s, <strong>and</strong> has sought assistance from a number of countries <strong>with</strong> chemical<br />

warfare programs in order <strong>to</strong> maintain <strong>and</strong> advance its CW capabilities. The United<br />

States further believed that Sudan might have been pursuing a more advanced chemical<br />

warfare capability. Although Sudan is a party <strong>to</strong> the CWC, there have been allegations<br />

of CW use by the Sudanese against rebels in southern Sudan, although these allegations<br />

have not been confirmed. The June 2003 Report stated that:<br />

61


The United States assesses that Sudan has established a CW R&D<br />

program <strong>with</strong> the goal of indigenously producing CW. The United States<br />

believes Sudan will continue <strong>to</strong> seek foreign assistance <strong>and</strong> technical<br />

expertise from a number of countries. Such activities are inconsistent <strong>with</strong><br />

the CWC.<br />

DISCUSSION OF OBLIGATIONS. Sudan became a State Party on June 23,<br />

1999. Sudan submitted its initial declaration <strong>to</strong> the OPCW in January 2000, declaring<br />

only unspecified riot control agents.<br />

ACTIONS. Numerous unconfirmed reports throughout the 1990s indicated that<br />

Sudan was researching, developing, producing, <strong>and</strong> testing CW agents. Reporting<br />

indicates that by the mid-1990s Sudan had established, <strong>with</strong> foreign assistance a CW<br />

research <strong>and</strong> development <strong>and</strong> small-scale production effort <strong>with</strong> the goal of indigenously<br />

producing CW. The United States previously assessed that Sudan was maintaining its<br />

R&D capability <strong>and</strong> probably had produced at least small quantities of CW agents. In<br />

August 1998, acting on the basis of intelligence information, the United States destroyed<br />

a facility, at Al Shifa in Khar<strong>to</strong>um, that had been suspected of producing nerve agent.<br />

Unconfirmed reports dating back <strong>to</strong> the early 1990s also suggest the use of CW<br />

agents by the Sudanese Government against rebel forces in the south. Although claims<br />

continue <strong>to</strong> surface in press reporting, the information – particularly regarding symp<strong>to</strong>ms<br />

<strong>and</strong> likely chemical use – generally has been contradic<strong>to</strong>ry. A series of allegations,<br />

appearing in late 1999, was investigated by several organizations <strong>and</strong> judged <strong>to</strong> be<br />

unsubstantiated. More recently, additional allegations of use of CW agents have<br />

surfaced.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. U.S. <strong>and</strong> Sudanese<br />

officials have discussed allegations of Sudanese CW activity, <strong>and</strong> Sudan has responded <strong>to</strong><br />

U.S. inquiries.<br />

In August 2003, Khar<strong>to</strong>um hosted jointly <strong>with</strong> the OPCW a regional meeting for<br />

national authorities of the 32 African Signa<strong>to</strong>ries <strong>to</strong> the CWC <strong>and</strong> observers from Great<br />

Britain, France, <strong>and</strong> the United States <strong>to</strong> signal its opposition <strong>to</strong> weapons of mass<br />

destruction.<br />

FINDING. The United States lacks sufficient evidence <strong>to</strong> determine whether<br />

Sudan is in violation of its CWC obligations.<br />

E. THE NUCLEAR NON-PROLIFERATION TREATY (NPT)<br />

This section of the Report updates developments relevant <strong>to</strong> other nations’<br />

compliance <strong>with</strong> the 1968 Nuclear Non-Proliferation Treaty (NPT) <strong>and</strong> addresses, in<br />

particular, developments in China, Iran, Iraq, Libya, <strong>and</strong> North Korea (DPRK).<br />

62


Some 47 countries have not complied <strong>with</strong> their obligations under Article III of<br />

the NPT <strong>to</strong> conclude <strong>with</strong> the International A<strong>to</strong>mic Energy Agency (IAEA) <strong>and</strong> put in<strong>to</strong><br />

effect a full-scope safeguards agreement <strong>with</strong>in 18 months after joining the NPT. The<br />

NPT does not require application of strengthened safeguards pursuant <strong>to</strong> the IAEA<br />

Additional Pro<strong>to</strong>col (AP). Nevertheless, by the end of 2003, there were 79 Additional<br />

Pro<strong>to</strong>col signa<strong>to</strong>ries <strong>and</strong> 38 such Pro<strong>to</strong>cols had entered in<strong>to</strong> force. The United States will<br />

continue <strong>to</strong> urge all NPT Parties required <strong>to</strong> do so <strong>to</strong> conclude a full-scope safeguards<br />

agreement <strong>with</strong> the IAEA, <strong>and</strong> <strong>to</strong> urge universal adherence <strong>to</strong> the Additional Pro<strong>to</strong>col.<br />

(The United States has signed the Additional Pro<strong>to</strong>col, <strong>and</strong> the U.S. Senate gave its<br />

advice <strong>and</strong> consent <strong>to</strong> the Pro<strong>to</strong>col on March 31, 2004.) The United States has also urged<br />

the Nuclear Suppliers Group (NSG) <strong>to</strong> make agreement <strong>to</strong> the Additional Pro<strong>to</strong>col a<br />

condition of nuclear supply.<br />

During the reporting period, four countries — Iran, North Korea, Libya, <strong>and</strong> the<br />

former regime in Iraq — did not comply <strong>with</strong> their obligations under Article II of the NPT<br />

not <strong>to</strong> “manufacture or otherwise acquire” nuclear weapons or “seek or receive any<br />

assistance” <strong>to</strong> this end. Of these four, only Libya voluntarily chose <strong>to</strong> renounce the<br />

pursuit of WMD, <strong>and</strong> is cooperating <strong>with</strong> the United States, the United Kingdom, <strong>and</strong> the<br />

international community <strong>to</strong> come in<strong>to</strong> full NPT compliance. The illicit pursuit of nuclear<br />

weapons by Iran <strong>and</strong> the DPRK, however, remain fundamental challenges <strong>to</strong> the NPT<br />

regime, which have yet <strong>to</strong> be resolved.<br />

AGREEMENT PROVISIONS<br />

Article I<br />

Article I of the NPT requires that Nuclear-Weapon State (NWS) Parties (1) not<br />

transfer nuclear weapons or other nuclear explosive devices or control over such weapons<br />

or explosive devices <strong>to</strong> “any recipient whatsoever” <strong>and</strong> (2) “not in any way <strong>to</strong> assist,<br />

encourage, or induce any non-nuclear-weapon State <strong>to</strong> manufacture or otherwise acquire<br />

nuclear weapons or other nuclear explosive devices, or control over such weapons or<br />

explosive devices.”<br />

The NPT does not define the specific terms of the second obligation (i.e., “assist,<br />

encourage, or induce”). Nor does the NPT negotiating record suggest specific criteria for<br />

determining whether a NWS has “assisted,” “encouraged,” or “induced” a Non-Nuclear-<br />

Weapon State (NNWS) <strong>to</strong> manufacture or acquire nuclear weapons.<br />

For its part, however, the United States has made clear <strong>to</strong> the other NWS Parties<br />

that it views comprehensive controls over the following categories of items as helping<br />

fulfill a State Party’s obligations under Article I: (1) specialized nuclear equipment,<br />

nuclear material <strong>and</strong> certain non-nuclear material covered by paragraph 2 of Article III of<br />

the Treaty; (2) nuclear-related dual-use equipment, material <strong>and</strong> all nuclear-related<br />

technology covered by the Guidelines of the Nuclear Suppliers Group (NSG); <strong>and</strong> (3)<br />

equipment, material, <strong>and</strong> technology <strong>with</strong> direct relevance <strong>to</strong> nuclear weapons.<br />

63


Article II<br />

Under Article II, NNWS Parties undertake four distinct obligations: (1) not <strong>to</strong><br />

receive a nuclear weapon or other nuclear explosive device; (2) not <strong>to</strong> exercise control<br />

over such weapons or explosive devices directly or indirectly; (3) not <strong>to</strong> manufacture or<br />

otherwise acquire nuclear weapons or other nuclear explosive devices; <strong>and</strong> (4) not <strong>to</strong> seek<br />

or receive any assistance in the manufacture of nuclear weapons or nuclear explosive<br />

devices.<br />

In assessing a NNWS Party’s compliance <strong>with</strong> its Article II obligations – not <strong>to</strong><br />

manufacture, or <strong>to</strong> seek or receive any assistance in the manufacture of, nuclear weapons<br />

– no simple, clear, “bright-line” rule exists. In explaining the term “manufacture” <strong>to</strong> the<br />

U.S. Senate in connection <strong>with</strong> the NPT ratification process, <strong>Arms</strong> <strong>Control</strong> <strong>and</strong><br />

Disarmament Agency Direc<strong>to</strong>r William Foster stated that it was not possible <strong>to</strong><br />

“formulate a comprehensive definition or interpretation,” <strong>and</strong> he doubted the efficacy of<br />

such efforts “unrelated <strong>to</strong> specific fact situations.” Accordingly, compliance assessments<br />

are highly contextual, <strong>and</strong> no single, comprehensive definition, unrelated <strong>to</strong> specific<br />

factual situations, would be useful. However, the United States has explicitly stated that<br />

the prohibition against the “manufacture” of a nuclear weapon, as well as against seeking<br />

or receiving any assistance in this regard, reaches more than simply the final assembly of<br />

such a device. In addition, Direc<strong>to</strong>r Foster advised the Senate that “facts indicating that<br />

the purpose of a particular activity was the acquisition of a nuclear explosive device<br />

would tend <strong>to</strong> show noncompliance.” Thus, as <strong>with</strong> Article I, an important fac<strong>to</strong>r in<br />

Article II compliance analysis is the purpose of a particular activity.<br />

U.S. officials have publicly outlined some of the “warning signs” that may<br />

indicate a prohibited nuclear weapons purpose, <strong>and</strong> thus suggest that a country’s<br />

ostensibly “peaceful” nuclear program might have violated Article II <strong>and</strong> should be<br />

closely scrutinized. Such indicia can include: (a) the presence of undeclared nuclear<br />

facilities; (b) procurement patterns inconsistent <strong>with</strong> a civil nuclear program (e.g.,<br />

cl<strong>and</strong>estine procurement networks, possibly including the use of front companies, false<br />

end-use information, <strong>and</strong> fraudulent documentation); (c) security measures beyond what<br />

would be appropriate for peaceful, civil nuclear installations; (d) a pattern of Article III<br />

safeguards violations suggestive not of mere mistake or incompetence, but of willful<br />

violation <strong>and</strong>/or systematic deception <strong>and</strong> denial efforts aimed at concealing nuclear<br />

activities from the International A<strong>to</strong>mic Energy Agency (IAEA); (e) a nuclear program<br />

<strong>with</strong> little (or no) coherence for peaceful purposes, but great coherence for weapons<br />

purposes (e.g., heavy water production in a country the civil nuclear facilities of which<br />

use only light water as a modera<strong>to</strong>r, or pursuit of enrichment facilities when other,<br />

cheaper energy-producing resources or an outside source of enriched uranium are<br />

available, or the pursuit of a full fuel cycle for a civil reac<strong>to</strong>r program <strong>to</strong>o small <strong>to</strong><br />

provide economic justification for such an effort). As cited by Direc<strong>to</strong>r Foster in his<br />

testimony <strong>to</strong> the Senate as relevant <strong>to</strong> a finding of “manufacture,” activities related <strong>to</strong> the<br />

acquisition or testing of the non-nuclear components of the nuclear explosion are an<br />

example of the type of activities that would provide a more direct indica<strong>to</strong>r of a weapons<br />

64


program. Informed by the analysis of such fac<strong>to</strong>rs, judgments as <strong>to</strong> the purpose of a<br />

Party’s nuclear activities therefore lie at the core of Article II compliance assessments.<br />

In sum, Article II assessments must look at the <strong>to</strong>tality of the facts, including<br />

judgments as <strong>to</strong> the NNWS Party’s purpose in undertaking the nuclear activities in<br />

question, <strong>to</strong> determine whether the Party has engaged in efforts <strong>to</strong> manufacture or<br />

otherwise acquire a nuclear weapon or other nuclear explosive device, or has sought or<br />

received any assistance in such manufacture. Such compliance assessments are acquiring<br />

particular salience given the linkage between Article II compliance <strong>and</strong> a Party’s rights <strong>to</strong><br />

share in the benefits of nuclear technology pursuant <strong>to</strong> Article IV (see below).<br />

Article III<br />

To prevent the diversion of nuclear energy from peaceful uses <strong>to</strong> nuclear<br />

weapons, Article III requires that each NNWS Party enter in<strong>to</strong> a safeguards agreement<br />

setting out the safeguards procedures <strong>to</strong> be applied <strong>to</strong> all source or special fissionable<br />

material in all peaceful nuclear activities. Paragraph 1 of Article III requires NNWS<br />

Parties “<strong>to</strong> accept safeguards, as set forth in an agreement <strong>to</strong> be negotiated <strong>and</strong> concluded<br />

<strong>with</strong> the International A<strong>to</strong>mic Energy Agency.” The same Article specifies that<br />

“[p]rocedures for the safeguards required by this article shall be followed <strong>with</strong> respect <strong>to</strong><br />

source or special fissionable material whether it is being produced, processed, or used in<br />

any principal nuclear facility or is outside any such facility,” <strong>and</strong> goes on <strong>to</strong> state that<br />

“safeguards required by this Article shall be applied on all source or special fissionable<br />

material in all peaceful nuclear activities <strong>with</strong>in the terri<strong>to</strong>ry of such State, under its<br />

jurisdiction, or carried out under its control anywhere.”<br />

As required by Paragraph 2 of Article III, each State Party undertakes not <strong>to</strong><br />

provide source or special fissionable material, or equipment or material especially<br />

designed or prepared for processing, use, or production of special fissionable material <strong>to</strong><br />

any NNWS for peaceful purposes unless it is subject <strong>to</strong> safeguards in that NNWS.<br />

Paragraph 4 specifies that, for States depositing their instruments of ratification or<br />

accession later than 180 days after the original entry in<strong>to</strong> force of the Treaty, “negotiation<br />

of such agreements shall commence not later than the date of such deposit ... [<strong>and</strong>] such<br />

agreements shall enter in<strong>to</strong> force not later than eighteen months after the date of initiation<br />

of negotiations.”<br />

The IAEA’s strengthened safeguard system was designed <strong>to</strong> enhance the IAEA’s<br />

verification capacity <strong>with</strong> regard <strong>to</strong> NNWS Parties by: (1) detecting the diversion of<br />

declared materials for nuclear weapons purposes, <strong>and</strong> (2) detecting undeclared activities<br />

in those states. In furtherance of these goals, in 1992, a voluntary universal reporting<br />

system for transfers of nuclear equipment <strong>and</strong> specified non-nuclear materials was<br />

created, the IAEA’s right <strong>to</strong> conduct special inspections was affirmed, <strong>and</strong> the Agency<br />

was granted permission <strong>to</strong> use all available information sources, including intelligence.<br />

Under Program 93+2, the IAEA began a dedicated program <strong>to</strong> enhance safeguards in<br />

1993. Under Part 1 of the program, first implemented in 1995, the IAEA began making<br />

65


enhanced use of existing authorities, in particular of environmental sampling at existing<br />

locations of nuclear materials.<br />

UIAEA Additional Pro<strong>to</strong>colU. In May 1997, the IAEA approved the Model<br />

Additional Pro<strong>to</strong>col (AP) under Part 2 of Program 93+2. If a NNWS adheres <strong>to</strong> the AP,<br />

it accepts obligations additional <strong>to</strong> those of its full-scope safeguards agreement <strong>and</strong><br />

exp<strong>and</strong>s the IAEA’s rights <strong>with</strong> respect <strong>to</strong> that State. Among the provisions of the<br />

Additional Pro<strong>to</strong>col are the following:<br />

• States are required <strong>to</strong> submit an exp<strong>and</strong>ed declaration <strong>to</strong> the Agency. For<br />

example, under the Additional Pro<strong>to</strong>col, all buildings on the site of a nuclear<br />

facility must be declared <strong>and</strong> identified, regardless of use. States are also<br />

required <strong>to</strong> include in their declarations specified nuclear-related activities,<br />

such as information regarding public <strong>and</strong> private nuclear-related fuel cycle<br />

R&D not involving nuclear material.<br />

• IAEA inspec<strong>to</strong>rs have “complementary access” rights <strong>to</strong> additional locations,<br />

including but not limited <strong>to</strong> those reported in the exp<strong>and</strong>ed declaration, for the<br />

purpose of resolving questions about the correctness <strong>and</strong> completeness of a<br />

State’s declaration or resolving inconsistencies relating <strong>to</strong> that information.<br />

Such access, which may be conducted upon 24- hours notice or less, may<br />

include the collection of environmental samples. The IAEA also has the<br />

authority, under certain circumstances, <strong>to</strong> conduct environmental sampling at<br />

undeclared locations.<br />

While most countries <strong>with</strong> major nuclear activities have signed the AP, it is not<br />

universal. President Bush has made clear that achieving universal adherence <strong>to</strong> the AP as<br />

the new minimum st<strong>and</strong>ard for strengthened IAEA safeguards is a high U.S.<br />

nonproliferation objective, <strong>and</strong> that such acceptance is vital <strong>to</strong> the long-term health <strong>and</strong><br />

effectiveness of the NPT, although failure <strong>to</strong> adhere <strong>to</strong> the Additional Pro<strong>to</strong>col is not<br />

considered noncompliance in this report. While not a panacea, the AP represents the<br />

strongest <strong>to</strong>ol now widely available <strong>to</strong> the IAEA in its work <strong>to</strong> detect safeguards<br />

violations <strong>and</strong> assess the presence or absence of undeclared nuclear activities.<br />

As suggested previously, Article III (safeguards) violations can sometimes be the<br />

result of mistake, error, or simple incapacity. In other cases, they can represent willful<br />

efforts <strong>to</strong> conceal more serious violations of nonproliferation obligations, such as the<br />

existence of a cl<strong>and</strong>estine nuclear weapons program in violation of Article II. There is,<br />

therefore, a potential link between Article III compliance <strong>and</strong> compliance <strong>with</strong> Articles I<br />

<strong>and</strong> II. Accordingly, recent U. S. public statements have stressed the importance of<br />

Article III safeguards compliance, noting the potential connection between Article III<br />

violations <strong>and</strong> Article II noncompliance. These statements have further indicated that<br />

nuclear cooperation, as called for in Article IV, may be jeopardized when a Party’s<br />

Article III problems create concerns that such problems are indica<strong>to</strong>rs of a cl<strong>and</strong>estine<br />

nuclear weapons program.<br />

66


IAEA Safeguards <strong>Compliance</strong>. There is a distinction between IAEA safeguards<br />

compliance determinations <strong>and</strong> judgments about compliance <strong>with</strong> the Nuclear Non-<br />

Proliferation Treaty. While safeguards compliance is necessary for Article III<br />

compliance, the Treaty Article is slightly broader. The IAEA does not make<br />

determinations regarding compliance <strong>with</strong> the NPT. Such questions are for the States<br />

Parties <strong>to</strong> the Treaty.<br />

With regard <strong>to</strong> assessing safeguards compliance, it may on occasion occur that an<br />

anomaly or question arises <strong>with</strong> respect <strong>to</strong> the implementation of a country’s IAEA<br />

Safeguards Agreement. Some such anomalies or questions may be cleared up easily <strong>and</strong><br />

quickly. Minor, merely technical errors in the implementation of safeguards are normally<br />

resolved between the IAEA Secretariat <strong>and</strong> the State concerned. Such incidents may<br />

raise compliance concerns, but generally do not constitute noncompliance, in <strong>and</strong> of<br />

themselves for purposes of the United Nations reporting requirement of the IAEA<br />

Statute.<br />

It may be, however, that more significant issues arise. For instance, information<br />

that calls in<strong>to</strong> question the IAEA’s ability <strong>to</strong> verify that nuclear material required <strong>to</strong> be<br />

safeguarded (including material that should have been declared but may not have been)<br />

has not been diverted can be information of great significance <strong>to</strong> the IAEA, <strong>to</strong> national<br />

governments, <strong>and</strong> <strong>to</strong> the broader international community. It is the technical objective of<br />

the safeguards system <strong>to</strong> ensure the timely detection of the diversion of significant<br />

quantities of material <strong>to</strong> nuclear weapons or other nuclear explosive devices or <strong>to</strong><br />

purposes unknown. If the Board of Governors finds that the IAEA is unable <strong>to</strong> verify<br />

such non-diversion, this may be reported <strong>to</strong> the United Nations pursuant <strong>to</strong> Paragraph 19<br />

of the IAEA’s model for the structure for NPT safeguards agreements (INFCIRC/153).<br />

Indeed, the United States believes that such instances should be so reported if, for<br />

instance, the Agency’s inability <strong>to</strong> verify non-diversion continues for any significant<br />

length of time, especially in circumstances that suggest any reason <strong>to</strong> be concerned about<br />

the possibility of access <strong>to</strong> fissile materials by criminals, terrorists, or others who might<br />

have an interest in the acquisition of nuclear materials for non-peaceful or unlawful<br />

purposes. (Even if the inability <strong>to</strong> verify occurred in the past <strong>and</strong> all materials have<br />

subsequently been accounted for, it may be appropriate <strong>to</strong> communicate <strong>with</strong> the UN <strong>to</strong><br />

the extent that the episode reveals flaws in the safeguards system in that country or –<br />

more generally – flaws in the international safeguards system of which the UN should be<br />

aware.) If the IAEA determines that it is unable <strong>to</strong> verify a State Party’s compliance <strong>with</strong><br />

its Safeguards Agreement because that state refuses <strong>to</strong> allow timely access <strong>to</strong> a facility,<br />

then the IAEA should conclude that the state’s denial of access constitutes<br />

noncompliance. In other words, in certain circumstances, a state’s decision not <strong>to</strong> let the<br />

IAEA carry out its safeguards mission should be considered noncompliance.<br />

Information may also come <strong>to</strong> light indicating that the country in question is or<br />

was in noncompliance <strong>with</strong> its safeguards obligations. This is a slightly different<br />

question than that raised by inability <strong>to</strong> verify non-diversion under Paragraph 19 of<br />

INFCIRC/153, though in some circumstances the same information will likely meet both<br />

67


st<strong>and</strong>ards, insofar as some noncompliance may naturally raise questions about the<br />

IAEA’s ability <strong>to</strong> verify non-diversion. In any event, a finding by the Board of Governors<br />

of noncompliance must be reported <strong>to</strong> the United Nations General Assembly <strong>and</strong> Security<br />

Council – as well as specifically <strong>to</strong> all IAEA member states – pursuant <strong>to</strong> Article XII.C of<br />

the IAEA Statute. In pertinent part, Article XII.C states:<br />

... The inspec<strong>to</strong>rs shall report any noncompliance <strong>to</strong> the Direc<strong>to</strong>r General<br />

who shall thereupon transmit the report <strong>to</strong> the Board of Governors. The<br />

Board shall call upon the recipient State or States <strong>to</strong> remedy forth<strong>with</strong> any<br />

noncompliance which it finds <strong>to</strong> have occurred. The Board shall report<br />

the noncompliance <strong>to</strong> all members <strong>and</strong> <strong>to</strong> the Security Council <strong>and</strong><br />

General Assembly of the United Nations. 4<br />

Within the IAEA system, the Board of Governors has final responsibility for a<br />

question central <strong>to</strong> safeguards enforcement – i.e., determining whether or not a matter<br />

qualifies as safeguards “noncompliance,” <strong>and</strong> thus whether that matter falls <strong>with</strong>in the<br />

m<strong>and</strong>a<strong>to</strong>ry reporting rule of Article XII.C of the Statute. A finding of noncompliance<br />

need not necessarily use the word “noncompliance,” though such clarity is certainly<br />

preferable. The United States believes noncompliance judgments by national<br />

governments or by the IAEA should be made on the basis of the facts, not based upon<br />

political calculation or the mere use (or avoidance) of specific trigger words.<br />

The lapse of time between the occurrence of a violation <strong>and</strong> its discovery is not a<br />

relevant consideration for judging safeguards compliance. In addition, neither a<br />

country’s lack of intent <strong>to</strong> violate its agreement nor its close cooperation <strong>with</strong> the IAEA<br />

subsequent <strong>to</strong> the point at which the violation occurred preclude a finding of<br />

noncompliance. Information suggesting that a problem is deliberate would certainly<br />

support a finding of noncompliance, but some problems remain significant whether or not<br />

they are intentional.<br />

Safeguards compliance judgments are necessarily somewhat contextual, <strong>and</strong> may<br />

be affected by a number of fac<strong>to</strong>rs. Such fac<strong>to</strong>rs must be carefully considered in light of<br />

all the circumstances. Considerations that may be quite relevant in assessing the<br />

significance of a safeguards problem include: the nature <strong>and</strong> quantity of the material<br />

involved; the relevance of the activity in question <strong>to</strong> nuclear weapons development (e.g.,<br />

enrichment or reprocessing versus civil reac<strong>to</strong>r operations); <strong>and</strong> the degree <strong>to</strong> which the<br />

problem is part of a pattern of similar or related problems. Thus, it is possible that even<br />

the non-declaration of a very small quantity of some materials in one single instance<br />

could constitute noncompliance if it occurred in connection <strong>with</strong> activities that were<br />

4 Article III.B.4 of the Statute also provides that the IAEA “shall notify the Security Council, as the organ<br />

bearing the main responsibility for the maintenance of international peace <strong>and</strong> security, if in connection<br />

<strong>with</strong> the activities of the Agency questions arise <strong>with</strong>in the competence of the Security Council.” Although<br />

issues of safeguards compliance may lie <strong>with</strong>in the Security Council’s competence because of their<br />

intrinsic connection <strong>to</strong> nuclear nonproliferation, Article III.B.4 is broad enough <strong>to</strong> permit the IAEA <strong>to</strong><br />

report an issue <strong>to</strong> the Council even when it is not specifically related <strong>to</strong> safeguards at all. (U)<br />

68


closely related <strong>to</strong> nuclear weapons development. Information suggesting deliberate<br />

concealment or other deceptive practices would be highly relevant <strong>to</strong> a safeguards<br />

compliance assessment. Indeed, the presence of such practices could make the difference<br />

in distinguishing a mere technical error or mistake in one country from an instance of<br />

noncompliance in another – even where the activities in question were otherwise similar.<br />

A state’s past record of safeguards compliance, moreover, would also be a relevant fac<strong>to</strong>r<br />

in how future problems are evaluated; countries that have a his<strong>to</strong>ry of serious compliance<br />

problems should be scrutinized <strong>with</strong> particular care.<br />

It should also be noted that a state party that <strong>with</strong>draws from the NPT after<br />

violating the Treaty’s provisions should not escape responsibility for those violations.<br />

Finally, in grappling <strong>with</strong> safeguards compliance issues, it must be remembered<br />

that the technical objective of IAEA safeguards (as stated in paragraph 28 of<br />

INFCIRC/153) is <strong>to</strong> ensure the timely detection of any diversion of nuclear material <strong>to</strong><br />

nuclear weapons or other nuclear explosive devices, or <strong>to</strong> purposes unknown.<br />

<strong>Compliance</strong> <strong>with</strong> safeguards agreements is critical because their role is <strong>to</strong> give the<br />

international community sufficient warning <strong>to</strong> permit responses before malefac<strong>to</strong>rs can<br />

capitalize upon such a diversion. In an era of increasing dissemination of proliferationsensitive<br />

nuclear technologies, regional nuclear arms races, illicit nuclear smuggling <strong>and</strong><br />

acquisition networks, <strong>and</strong> terrorist networks bent upon the acquisition of weapons of<br />

mass destruction, determinations about the significance of safeguards problems must be<br />

made in view of their potential consequences in <strong>to</strong>day’s dangerous world. The United<br />

States believes that in the event of “close calls,” it is better <strong>to</strong> err on the side of prudence<br />

in formally calling attention <strong>to</strong> – <strong>and</strong> notifying the international community of –<br />

noncompliance problems.<br />

Article IV<br />

Article IV of the NPT speaks both <strong>to</strong> the right of States Parties <strong>to</strong> participate in<br />

taking advantage of the benefits of nuclear technology <strong>and</strong> <strong>to</strong> their NPT obligation <strong>to</strong> do<br />

so only in ways consistent <strong>with</strong> the nonproliferation obligations of the Treaty. The first<br />

paragraph of Article IV provides that “nothing in this Treaty shall be interpreted as<br />

affecting the inalienable right” of States Parties <strong>to</strong> pursue the use of nuclear energy “for<br />

peaceful purposes” <strong>and</strong> “in conformity <strong>with</strong> articles I <strong>and</strong> II of the Treaty.” The second<br />

paragraph in Article IV deals <strong>with</strong> international cooperation in developing nuclear<br />

energy. Article IV(2), however, does not compel supplier states <strong>to</strong> provide any specific<br />

nuclear technology <strong>to</strong> any specific NPT party. Therefore, it is not inconsistent <strong>with</strong><br />

Article IV for an NPT party <strong>to</strong> restrict nuclear supply <strong>to</strong> another NPT party or otherwise<br />

exercise discretion in determining the nature of its relationship <strong>with</strong> other countries.<br />

Therefore, nonproliferation efforts such as export control restrictions, Nuclear Suppliers<br />

Group technology-transfer guidelines, end-use restrictions, interdiction measures such as<br />

the Proliferation Security Initiative, the imposition of national or international sanctions<br />

in response <strong>to</strong> nuclear-related proliferation problems, <strong>and</strong> efforts <strong>to</strong> restrict the spread of<br />

69


proliferation-sensitive enrichment <strong>and</strong> reprocessing technology are in no way inconsistent<br />

<strong>with</strong> Article IV.<br />

States Parties <strong>to</strong> the Treaty have accepted the condition that their nuclear activities<br />

must be carried out in conformity <strong>with</strong> Articles I <strong>and</strong> II of the Treaty. Thus, if a State<br />

Party has violated Article I or Article II, that state cannot argue that Article IV protects it<br />

from the consequences of breach, including the imposition of measures by other states<br />

against its nuclear program.<br />

COUNTRY ASSESSMENTS<br />

CHINA<br />

ISSUE. China’s nuclear-related interactions <strong>with</strong> other countries have raised<br />

concerns regarding China’s compliance <strong>with</strong> its NPT Article I obligation “not in any way<br />

<strong>to</strong> assist, encourage, or induce any non-nuclear-weapon State <strong>to</strong> manufacture or otherwise<br />

acquire nuclear weapons.”<br />

HISTORY OF COMPLIANCE EVALUATION. China has joined several<br />

international nuclear regimes <strong>and</strong> has promulgated comprehensive nuclear export<br />

controls over the past decade in an effort <strong>to</strong> bolster its credentials as a responsible<br />

international player. Beijing signed the <strong>Nonproliferation</strong> Treaty in 1992, joined the NPT<br />

Exporters (“Zangger”) Committee in 1997, <strong>and</strong> implemented dual-use nuclear export<br />

controls based on the Nuclear Suppliers Group (NSG) control list in 1998. Nevertheless,<br />

until May 2004, China was the only NPT nuclear weapon state that had declined <strong>to</strong> join<br />

the NSG. It should be noted, however, that NSG membership is not required by the NPT.<br />

Since the Zangger Committee only requires item-specific safeguards; as opposed <strong>to</strong> the<br />

more stringent requirement of the NSG, which m<strong>and</strong>ates full-scope safeguards, China<br />

was therefore technically in a position <strong>to</strong> sell controlled nuclear-related items <strong>to</strong> non-NPT<br />

members, as long as the items themselves went <strong>to</strong> a facility subject <strong>to</strong> safeguards. This<br />

technical difference made it possible for China <strong>to</strong> provide assistance <strong>to</strong> safeguarded<br />

facilities, in such countries as Pakistan, should it choose <strong>to</strong> do so. It appears that Chinese<br />

policies <strong>and</strong> nuclear export control systems contain all the necessary elements <strong>to</strong> enforce<br />

China’s obligations under Article I of the NPT should China wish <strong>to</strong>. In the June 2003<br />

Noncompliance Report, the United States concluded that:<br />

While we continue <strong>to</strong> believe that Beijing is seriously prepared <strong>to</strong><br />

implement its NPT obligations, <strong>and</strong> has taken steps <strong>to</strong> do so, given all the<br />

available information, the United States remains concerned about China’s<br />

compliance <strong>with</strong> its nuclear nonproliferation commitments.<br />

DISCUSSION OF OBLIGATIONS. In early 1992, China acceded <strong>to</strong> the NPT.<br />

By joining the Treaty as a Nuclear-Weapon State Party, China became obligated under<br />

Article I of the Treaty not in any way <strong>to</strong> assist, encourage, or induce any NNWS <strong>to</strong><br />

manufacture or otherwise acquire nuclear weapons or other nuclear explosive devices.<br />

70


Under Article III, China also made a commitment <strong>to</strong> ensure the application of<br />

IAEA safeguards on exports <strong>to</strong> any NNWS of nuclear material <strong>and</strong> equipment especially<br />

designed or prepared for the processing, use, or production of special nuclear material.<br />

The NPT exporters’ Zangger Committee has defined a “trigger list” of such equipment<br />

<strong>and</strong> material, <strong>and</strong> members have announced a common underst<strong>and</strong>ing on controlling<br />

listed items as a guideline for implementing this provision.<br />

While China is a member of the Zangger Committee, until May 2004 it was the<br />

only nuclear weapons state that was not also a member of the Nuclear Suppliers Group<br />

(NSG), which requires full scope safeguards (i.e., IAEA safeguard on all nuclear<br />

material) in a recipient NNWS state as a condition of nuclear exports. At that time,<br />

China did, however, have export control laws that mirror the NSG guidelines during the<br />

reporting period. In addition, on May 11, 1996, China publicly pledged <strong>to</strong> the United<br />

States that it would not provide assistance <strong>to</strong> unsafeguarded nuclear facilities. China was<br />

accepted in<strong>to</strong> the NSG in May 2004.<br />

In a 1997 letter provided <strong>to</strong> the United States, the Chinese Vice Premier stated<br />

that “China consistently has opposed the proliferation of weapons; does not advocate,<br />

encourage or engage in proliferation of nuclear weapons, nor assists other countries in<br />

developing nuclear weapons.”<br />

ACTIONS. As the United States has moni<strong>to</strong>red China’s actions in relation <strong>to</strong> its<br />

obligations under the NPT, China’s interactions <strong>with</strong> two countries, in particular, have<br />

raised concerns. Most of the basis for these concerns cannot be discussed here, but it is<br />

worth noting that in February 2003, an anti-Iranian opposition group alleged publicly that<br />

Chinese experts were continuing <strong>to</strong> work at Iran’s Sagh<strong>and</strong> uranium mine as supervisors.<br />

In 2002 <strong>and</strong> 2003, foreign entities also continued their efforts <strong>to</strong> acquire nuclearrelated<br />

materials <strong>and</strong> dual-use equipment from Chinese suppliers. Such contacts remain<br />

an intense concern of the United States.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. China’s<br />

compliance <strong>with</strong> its nuclear nonproliferation obligations has been the subject of<br />

considerable scrutiny. In the past, the United States has cited two key fac<strong>to</strong>rs as being<br />

especially relevant <strong>to</strong> our judgment of China’s compliance <strong>with</strong> the NPT: (1) China’s<br />

May 11, 1996, public <strong>and</strong> private commitments not <strong>to</strong> provide assistance <strong>to</strong><br />

unsafeguarded nuclear facilities; <strong>and</strong> (2) the establishment of a comprehensive national<br />

nuclear export control system. U.S. officials stressed that China’s May 11, 1996,<br />

commitments should also prohibit assistance <strong>to</strong> entities involved in the design or testing<br />

of the non-nuclear components of a nuclear device.<br />

In laying out the principal elements of a comprehensive nuclear export control<br />

system, U.S. officials stressed a number of fac<strong>to</strong>rs: that controls should apply <strong>to</strong> all<br />

private <strong>and</strong> public entities; that the control list should encompass all equipment, material<br />

<strong>and</strong> technology covered by the NSG, including dual-use items; that technology controls<br />

71


should extend <strong>to</strong> personnel as well as information; that some type of catch-all control<br />

should be part of the system; <strong>and</strong> that the controls should extend <strong>to</strong> nuclear weapons<br />

information <strong>and</strong> equipment.<br />

It appears that Chinese policy <strong>and</strong> nuclear export control systems, adopted in the<br />

aftermath of the Oc<strong>to</strong>ber 1997 U.S.-China Summit, contain all the elements necessary <strong>to</strong><br />

permit China <strong>to</strong> implement its obligations under Article I of the NPT. This conclusion<br />

led President Clin<strong>to</strong>n, on January 12, 1998, <strong>to</strong> send <strong>to</strong> Congress the certifications<br />

necessary <strong>to</strong> implement the 1985 U.S.-China peaceful nuclear cooperation agreement.<br />

Thereafter, members of Congress were briefed in closed session on the details of a few<br />

cases. On March 18, 1998, following a review of 30 days of continuous session of<br />

Congress, the conditions for the initiation of U.S. peaceful nuclear cooperation <strong>with</strong><br />

China were met.<br />

Chinese regulations in place cover both trigger list items (i.e., those items relevant<br />

<strong>to</strong> Article III of the NPT) <strong>and</strong> nuclear dual-use items. China promulgated nuclear dualuse<br />

regulations by mid-1998. “Catch-all” control authority exists for Chinese<br />

government departments <strong>and</strong> the government has the authority <strong>to</strong> control items that may<br />

not be on control lists. The controls apply <strong>to</strong> technology in the form of exchanges of<br />

personnel, as well as <strong>to</strong> the transfer of written information <strong>and</strong> tangible items.<br />

China’s export control system appears designed <strong>to</strong> ensure adequate review for<br />

those exports that come <strong>to</strong> the attention of Chinese export control authorities if these<br />

authorities choose <strong>to</strong> exercise this authority.<br />

FINDING. China has joined several international nuclear regimes <strong>and</strong> has<br />

promulgated comprehensive nuclear export controls over the past decade. Nevertheless,<br />

based upon all available information, the United States remains concerned about the<br />

effectiveness of Chinese nuclear export controls <strong>and</strong> China’s compliance <strong>with</strong> its NPT<br />

Article I nuclear nonproliferation commitments.<br />

IRAN<br />

ISSUE. The issue is whether Iran is in violation of its obligations as a nonnuclear<br />

weapon State Party <strong>to</strong> the NPT.<br />

HISTORY OF COMPLIANCE EVALUATION. The United States assessed<br />

Iran’s compliance <strong>with</strong> the NPT as early as the January 14, 1993 Report. At that time,<br />

the United States concluded that Iran had demonstrated a continuing interest in nuclear<br />

weapons <strong>and</strong> related technology that caused the United States <strong>to</strong> assess that Iran was in<br />

the early stages of developing a nuclear weapons program, <strong>with</strong> an emphasis on<br />

developing centrifuge technology. The Report in 1993 stated that Iran’s “nuclear<br />

intentions are suspect despite its NPT adherence.” The Noncompliance Reports from<br />

1994 through 1998 said similarly that Iran’s “NPT nonproliferation credentials” were<br />

“highly questionable” or “questionable.” In 1997, 1998, <strong>and</strong> 1999, the Unites States<br />

72


declared that Iran’s nuclear intentions were “suspect despite its status as an NPT State<br />

Party.” In the June 2003 Noncompliance Report, the United States concluded that:<br />

Based on the <strong>to</strong>tality of the available information, the United States<br />

assesses that Iran is pursuing a program <strong>to</strong> develop nuclear weapons.<br />

Aspects of this activity are in violation of Iran’s NPT commitments.<br />

DISCUSSION OF OBLIGATIONS. Iran signed the NPT in July 1968, <strong>and</strong><br />

deposited its instrument of ratification in February 1970. Iran’s full-scope Safeguards<br />

Agreement <strong>with</strong> the IAEA entered in<strong>to</strong> force in May 1974. The 1992 IAEA Board of<br />

Governors called upon all states <strong>with</strong> NPT type safeguards agreements <strong>to</strong> revise the<br />

timing for advance notification of planned nuclear facilities <strong>to</strong> provide for earlier notice<br />

<strong>to</strong> the IAEA. (Iran did not agree <strong>to</strong> this until February 2003 <strong>and</strong> was the last <strong>to</strong> do so.) In<br />

late 1995, Iran accepted part one of the IAEA Strengthened Safeguards System<br />

(developed under Program 93+2) which, among other things, allows the IAEA <strong>to</strong> conduct<br />

environmental sampling at declared facilities, other declared locations, <strong>and</strong> locations of<br />

special inspections. In the 2001 IAEA’s Safeguards Implementation Report (SIR), Iran<br />

was singled out as the last State that refused <strong>to</strong> accept the key safeguards-strengthening<br />

measure <strong>to</strong> revise the timing for advance notification of planned nuclear facilities.<br />

During the February 21-22, 2003 visit of the IAEA Direc<strong>to</strong>r General (DG) <strong>to</strong> Iran, Iran<br />

reportedly agreed <strong>to</strong> adhere <strong>to</strong> a subsidiary arrangement obligating it <strong>to</strong> provide the IAEA<br />

<strong>with</strong> design information in advance of construction of nuclear-related facilities. As part<br />

of a political agreement in the autumn of 2003, Iran agreed <strong>to</strong> permit IAEA access as if<br />

the AP were in force. In December 2003, Iran signed the Additional Pro<strong>to</strong>col, but has not<br />

yet ratified it.<br />

ACTIONS. Iran has continued the indigenous construction of nuclear-related<br />

facilities, such as Arak <strong>and</strong> Nantaz, <strong>and</strong> attempts <strong>to</strong> acquire equipment for such facilities<br />

from abroad. Iran has obtained considerable quantities of nuclear equipment – including<br />

both P-1 designs, components <strong>and</strong> centrifuges, <strong>and</strong> more advanced P-2 centrifuge design<br />

drawings – from foreign companies, including those associated <strong>with</strong> the AQ Khan illicit<br />

procurement network. As confirmed by the IAEA in 2003, Iran engaged in a secret effort<br />

for nearly two decades <strong>to</strong> acquire uranium enrichment <strong>and</strong> plu<strong>to</strong>nium production <strong>and</strong><br />

reprocessing technology.<br />

Iran sought assistance during the reporting period of this Report in mining <strong>and</strong> ore<br />

concentration, as well as uranium recovery process technology from numerous states in<br />

central Asia <strong>and</strong> Europe. These activities reconfirmed that Iran is developing domestic<br />

sources of uranium, which could eventually be used in its nuclear weapon development<br />

program. Additionally, Iran renewed its efforts <strong>to</strong> acquire significant quantities of natural<br />

uranium from foreign sources. Although Iran claims an economic rationale for its<br />

nuclear programs – Iranian use of nuclear power will free up oil for exports – its pursuit<br />

of expensive uranium <strong>and</strong> recovery technology, given the insufficient size of Iran’s<br />

domestic uranium reserves, does not make economic sense, suggesting an ulterior motive<br />

for such expensive activities. Moreover, these activities are particularly suspicious in<br />

73


view of the contract Iran is negotiating <strong>with</strong> Russia <strong>to</strong> supply fuel for the Bushehr reac<strong>to</strong>r<br />

for the lifetime of operation.<br />

In 2000, Iran declared the existence of its uranium conversion facility (UCF) <strong>to</strong><br />

IAEA officials <strong>and</strong>, in 2001, submitted <strong>to</strong> the IAEA a design information questionnaire<br />

for the UCF. The IAEA, in consultation <strong>with</strong> experts from the United States <strong>and</strong> other<br />

countries, began in 2002 <strong>to</strong> develop a robust safeguards approach for the UCF. As part of<br />

this effort, IAEA safeguards experts visited the UCF.<br />

Iran has conducted research, in some cases extensively, in several enrichment<br />

technologies, including gas centrifuge, <strong>and</strong> laser iso<strong>to</strong>pe separation. In August 2002, an<br />

Iranian opposition group revealed the existence of two covert nuclear facilities under<br />

construction in Iran – a heavy water production plant at Arak <strong>and</strong> a “fuel production”<br />

plant at Natanz.<br />

As subsequently detailed by the IAEA acting on the basis of the August 2002<br />

revelations, Iran had embarked years before upon a hugely ambitious production-scale<br />

centrifuge program. Iran confirmed <strong>to</strong> the IAEA DG in February 2003 that the Natanz<br />

site is intended <strong>to</strong> be an industrial-scale centrifuge enrichment facility, ostensibly <strong>to</strong><br />

supply nuclear fuel for three 1,000-MWe nuclear power plants. The DG in February<br />

2003 visited the plant <strong>and</strong> viewed a pilot-scale centrifuge plant under construction <strong>with</strong> a<br />

number of centrifuges spinning under vacuum <strong>and</strong> many more in various states of<br />

assembly. The IAEA was unable at that time <strong>to</strong> take samples that would provide specific<br />

evidence of the materials that had been introduced in<strong>to</strong> the facility. Prior <strong>to</strong> the public<br />

revelations, Iran had failed <strong>to</strong> declare this <strong>and</strong> the Arak facilities <strong>to</strong> the IAEA, despite<br />

public statements by Iranian officials that all their nuclear activities were being<br />

undertaken <strong>with</strong> the supervision of the IAEA. Under Iran’s subsidiary arrangements then<br />

in effect <strong>with</strong> respect <strong>to</strong> its safeguards agreement, Iran was not required <strong>to</strong> declare nuclear<br />

facilities until six months before nuclear material was introduced. Under the revised<br />

subsidiary arrangements adopted in February 2003, Iran is required <strong>to</strong> provide design<br />

information on such facilities at a much earlier stage, during planning, construction <strong>and</strong><br />

testing.<br />

As outlined in IAEA reports, Iran also engaged in a systematic practice of denial<br />

<strong>and</strong> deception, not only concealing its enrichment work from the Agency for many years,<br />

but also responding <strong>to</strong> IAEA inquiries <strong>with</strong> a shifting pattern of false or misleading<br />

statements as details gradually emerged. Iran, for instance, had declared no uranium<br />

centrifuge program <strong>to</strong> the IAEA at all, but after the Natanz facility was publicly revealed,<br />

Iran admitted that it had indeed been developing such a program since 1997. After the<br />

IAEA began probing further in<strong>to</strong> the development of this program, Iran changed its s<strong>to</strong>ry<br />

again – admitting that the program had in fact been underway since 1985. Iran first<br />

claimed that its centrifuge program had been designed only on the basis of simulations,<br />

but after IAEA experts questioned this closely <strong>and</strong> argued that Iran must have tested <strong>with</strong><br />

UF6, Iran admitted that it had actually used foreign design information. This<br />

74


contradicted Iran’s previous claims that it had developed centrifuges entirely<br />

indigenously.<br />

When confronted <strong>with</strong> the IAEA’s discovery of highly-enriched uranium (HEU)<br />

particles in environmental samples taken at the Natanz facility <strong>and</strong> two other locations,<br />

Iran declared that it had used not only foreign design information, but also foreign<br />

centrifuge components, which it claimed were the source of the HEU. Iran for some time<br />

refused <strong>to</strong> provide the IAEA <strong>with</strong> any information about the source of either the foreign<br />

design information or the components. When the IAEA asked <strong>to</strong> see the original foreign<br />

designs, Iran also refused – providing only “redrawn” versions for inspection by IAEA<br />

experts. It has subsequently become clear that the Iranian design information (as well as<br />

a quantity of centrifuge components) in fact came from the A.Q. Khan nuclear supply<br />

network – the same network that provided such technology, as well as actual nuclear<br />

weapons designs, <strong>to</strong> Libya.<br />

When suspicions were raised about possible enrichment activity at the Kalaye<br />

Electric Company facility in Tehran, Iran first denied it, claiming that the facility was a<br />

warehouse or watch fac<strong>to</strong>ry. Iran subsequently admitted that it was a nuclear-related<br />

location, but identified Kalaye as merely a centrifuge component facility. Iran then<br />

changed its s<strong>to</strong>ry again, as the IAEA probed more closely, conceding that it had tested<br />

centrifuges there for at least five years. Iran refused IAEA requests <strong>to</strong> conduct<br />

environmental sampling at Kalaye for many months, however, during which time it<br />

reportedly cleaned <strong>and</strong> refurbished the interior of the buildings at the facility – activities<br />

clearly intended <strong>to</strong> thwart the IAEA’s ability <strong>to</strong> obtain useful samples. At another facility<br />

suspected of conducting laser enrichment activities, Iran similarly denied permission for<br />

IAEA sampling <strong>and</strong> moved equipment out of the building. More recently, Iran has<br />

completely razed a building at Lavisan that had been publicly identified by an opposition<br />

group as being associated <strong>with</strong> WMD-related activity. The IAEA’s success in obtaining<br />

information from environmental sampling appears <strong>to</strong> have led Tehran <strong>to</strong> assume that the<br />

only safe way <strong>to</strong> “sanitize” an illicit facility is <strong>to</strong> demolish it completely.<br />

After years of concealing it from the IAEA, Iran has also admitted that it<br />

conducted labora<strong>to</strong>ry-scale uranium conversion work <strong>and</strong> small-scale laser iso<strong>to</strong>pe<br />

separation during the 1990s, using uranium compounds not declared by Iran <strong>to</strong> the IAEA.<br />

The failure <strong>to</strong> report this material was a violation of Iran’s safeguards agreement. Iran<br />

also conducted undeclared plu<strong>to</strong>nium separation experiments using uranium metal<br />

“targets” secretly irradiated in its research reac<strong>to</strong>r, as well as the production of polonium-<br />

210 (Po-210), an iso<strong>to</strong>pe that is used in many nuclear weapons triggers.<br />

Iran’s pursuit of the foregoing capabilities is suspicious for a number of reasons.<br />

These capabilities are well suited <strong>to</strong> the development of a nuclear weapons capability, but<br />

they are unnecessary <strong>and</strong> uneconomic for a civil nuclear program at Iran’s level of<br />

development. Iran failed <strong>to</strong> declare these activities <strong>and</strong> engaged in systematic deception<br />

in order <strong>to</strong> conceal them from the IAEA, <strong>and</strong> <strong>to</strong> that end delayed acceptance of<br />

strengthened measures including the Additional Pro<strong>to</strong>col. It is suspicious, as well,<br />

75


ecause this nuclear program makes little sense in the context of Russia’s stated<br />

commitment <strong>to</strong> supply fuel for the lifetime of the Russian-supplied Bushehr reac<strong>to</strong>r <strong>and</strong><br />

Iran’s lack of any serious economic or energy policy justification for such an extensive<br />

nuclear fuel-cycle effort. Iran, for instance, wastes more energy in flaring off natural gas<br />

in its extensive refinery operations than it would be able <strong>to</strong> produce even were it able <strong>to</strong><br />

complete its ambitious nuclear construction program. As noted, according <strong>to</strong> the<br />

Organization for Economic Cooperation <strong>and</strong> Development’s statistics, Iran does not<br />

possess sufficient “known reserves” of uranium <strong>to</strong> supply a civil power program of the<br />

size it claims <strong>to</strong> be pursuing. During the reporting period, Iran continued efforts <strong>to</strong><br />

develop all aspects of the nuclear fuel cycle <strong>and</strong> sought foreign assistance, <strong>to</strong> include<br />

training for its nuclear personnel. We believe this effort combines elements of not only<br />

the activities declared <strong>to</strong> the IAEA <strong>and</strong> ostensibly run by the civilian AEOI, but also<br />

undeclared fuel cycle activities that may be run solely by the military. The United States<br />

continues <strong>to</strong> work at all levels <strong>to</strong> prevent such transfers from occurring.<br />

IAEA inspections throughout 2003 uncovered Iran’s covert construction of a large<br />

nuclear fuel cycle program <strong>and</strong> numerous “breaches” of, <strong>and</strong> “failures” <strong>to</strong> comply <strong>with</strong>,<br />

Iran’s safeguards agreement. The IAEA uncovered, or Iran was forced <strong>to</strong> admit, design<br />

work on a large heavy water research reac<strong>to</strong>r, a uranium enrichment AVLIS facility,<br />

reprocessing experimentation, past polonium production, <strong>and</strong> research <strong>and</strong> development<br />

of a more advanced P-2 centrifuge design (in addition <strong>to</strong> the P-1 program discovered at<br />

Natanz). Moreover, IAEA investigations have uncovered previously undeclared<br />

enrichment experiments, plu<strong>to</strong>nium production experiments, <strong>and</strong> numerous uranium<br />

conversion experiments.<br />

At the November 2003 IAEA Board of Governors meeting, <strong>and</strong> in the wake of a<br />

French, British, <strong>and</strong> German diplomatic mission <strong>to</strong> Iran, the Board adopted a resolution<br />

strongly deploring Iran’s past failures <strong>and</strong> breaches of its obligation <strong>to</strong> comply <strong>with</strong> its<br />

Safeguards Agreement. While the Board did not report Iran’s noncompliance <strong>to</strong> the<br />

Security Council at that point as required by the IAEA Statute, it did formally resolve that<br />

“should any further serious Iranian failures come <strong>to</strong> light, the Board of Governors would<br />

meet immediately <strong>to</strong> consider, in the light of the circumstances <strong>and</strong> of advice from the<br />

Direc<strong>to</strong>r General, all options at its disposal, in accordance <strong>with</strong> the IAEA Statute <strong>and</strong><br />

Iran’s Safeguards Agreement.” In connection <strong>with</strong> the diplomatic effort of the so-called<br />

EU-3, Iran made a detailed declaration <strong>to</strong> the IAEA <strong>and</strong> decided voluntarily <strong>to</strong> suspend<br />

all “uranium enrichment <strong>and</strong> reprocessing activities as defined by the IAEA.” On<br />

Oc<strong>to</strong>ber 29, the IAEA specified that the enrichment-related activities <strong>to</strong> be suspended<br />

should include assembly of centrifuges <strong>and</strong> manufacture or import of enrichment<br />

equipment, <strong>and</strong> that Iran should “consider suspending” production or import of feed<br />

material. Iran never fully ceased the production of centrifuge components <strong>and</strong> was<br />

discovered <strong>to</strong> having omitted the more advanced P-2 centrifuge information from its<br />

Oc<strong>to</strong>ber 2003 declaration. In the summer of 2004, Iran repudiated its February 2004<br />

addendum <strong>and</strong> its Oc<strong>to</strong>ber 2003 suspension pledge <strong>and</strong> announced that it was resuming<br />

full-scale centrifuge production <strong>and</strong> uranium conversion. Iran re-committed itself <strong>to</strong> the<br />

EU-3 in the November 2004 Paris Agreement <strong>to</strong> voluntarily <strong>and</strong> temporarily suspend<br />

76


specified enrichment-related activities, including “all testing or production at any<br />

uranium-conversion installation,” during the period of negotiations on a longer term<br />

arrangement. These developments will be detailed in the next NCR.<br />

Iran also continued <strong>to</strong> pursue uranium mining <strong>and</strong> ore concentration activities<br />

throughout the period of this Report.<br />

Additionally, Iran attempted <strong>to</strong> obtain laser <strong>and</strong> other dual-use equipment from<br />

Russia that can have applications in a<strong>to</strong>mic vapor laser iso<strong>to</strong>pe separation (AVLIS), as an<br />

alternative means of uranium enrichment. In the fall of 2000, Russian President Putin<br />

indicated that Russia would suspend any AVLIS-related transactions <strong>with</strong> Iran, at least<br />

for the immediate future. MINATOM Minister Aleks<strong>and</strong>r Rumyantsev reaffirmed this <strong>to</strong><br />

Under Secretary of State John Bol<strong>to</strong>n in November 2002. Russian export authorities<br />

<strong>with</strong>held authorization <strong>to</strong> export two critical AVLIS-related items <strong>to</strong> Iran, <strong>and</strong> by 2003<br />

Russia appeared <strong>to</strong> have <strong>with</strong>drawn from the AVLIS cooperation. It is now publicly<br />

known that Iran conducted AVLIS enrichment work in violation of its safeguards<br />

agreement. Iran declared its AVLIS program <strong>to</strong> the IAEA only in Oc<strong>to</strong>ber 2003, <strong>and</strong> in<br />

May 2004 admitted, contrary <strong>to</strong> previous claims, that it had achieved enrichment levels –<br />

in very small quantities – as high as 15 percent.<br />

In January 1995, Iran signed a contract <strong>to</strong> purchase from Russia a light water<br />

nuclear power reac<strong>to</strong>r (model VVER-1000) <strong>to</strong> be constructed at Bushehr. In addition <strong>to</strong><br />

Russia’s continuing construction activities at the site of the first reac<strong>to</strong>r of the Bushehr<br />

complex, Russia <strong>and</strong> Iran have discussed provision of up <strong>to</strong> five additional reac<strong>to</strong>rs.<br />

Russian officials have noted publicly that construction of those reac<strong>to</strong>rs will not begin<br />

until the first unit is complete.<br />

Although the Bushehr project is not a compliance issue, in <strong>and</strong> of itself, the<br />

secondary proliferation potential for Iran <strong>to</strong> exploit this facility <strong>and</strong> use it as a cover for<br />

weapons-related training <strong>and</strong> technology acquisition is an enduring NPT concern.<br />

Specifically, the United States is concerned that the Bushehr project can be a cover <strong>to</strong><br />

acquire more sensitive nuclear technologies <strong>and</strong> provides an ostensibly legitimate reason<br />

for Iran <strong>to</strong> acquire <strong>and</strong> maintain skills <strong>and</strong> nuclear expertise applicable <strong>to</strong> weapons work.<br />

In previous years, several countries agreed <strong>to</strong> pull back from lucrative contracts relating<br />

<strong>to</strong> Bushehr. Even in the face of ongoing revelations of undeclared Iranian activities <strong>and</strong><br />

deceptions upon the IAEA, however, Russia remains committed <strong>to</strong> the Bushehr project.<br />

Iran has made persistent efforts <strong>to</strong> construct a large, heavy water moderated<br />

nuclear research reac<strong>to</strong>r, which would be well suited for the production of weapons-grade<br />

plu<strong>to</strong>nium. Iran’s ability <strong>to</strong> produce heavy water <strong>and</strong> nuclear-grade graphite would<br />

materially support its efforts <strong>to</strong> design <strong>and</strong> indigenously construct a reac<strong>to</strong>r intended for<br />

producing weapons-grade plu<strong>to</strong>nium. This activity is also entirely consistent <strong>with</strong> Iran’s<br />

past undeclared experiments <strong>with</strong> target irradiation <strong>and</strong> plu<strong>to</strong>nium separation.<br />

77


COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. Iran is aware that<br />

many states view its nuclear intentions <strong>with</strong> suspicion despite its status as an NPT State<br />

Party, <strong>and</strong> that these suspicions have limited its ability <strong>to</strong> obtain foreign technology,<br />

equipment, <strong>and</strong> facilities. The Iranian announcements <strong>and</strong> admissions of the<br />

development of an indigenous nuclear fuel cycle, in late 2002 <strong>and</strong> early 2003, have<br />

occurred immediately after suspicious activity was revealed <strong>and</strong> were not undertaken in<br />

the spirit of providing the IAEA <strong>with</strong> the required safeguards information. As detailed<br />

above, Iran’s long series of progressive admissions <strong>to</strong> the IAEA followed this same<br />

pattern: previously secret activities have usually been admitted only after Iran has been<br />

presented <strong>with</strong> evidence thereof, or been confronted <strong>with</strong> internal contradictions in the<br />

accounts it has given. Admissions have been grudging <strong>and</strong> piecemeal, <strong>and</strong> cooperation<br />

<strong>with</strong> the IAEA has been reluctant <strong>and</strong> accompanied by protests, accusations, <strong>and</strong> threats.<br />

As the United States put it at the November 2003 IAEA Board of Governors meeting, the<br />

IAEA’s own investigations have “confirmed Iran systematically <strong>and</strong> deliberately<br />

deceived the IAEA <strong>and</strong> the international community about these issues for year after year<br />

after year.” The United States believes that the IAEA Direc<strong>to</strong>r General’s reports make it<br />

“unequivocally clear that Iran chose – as a matter of government policy sustained for well<br />

over a decade – <strong>to</strong> violate its safeguards obligations in full knowledge that its actions <strong>and</strong><br />

omissions were violations.” Iran concealed its secret nuclear program, the United States<br />

has said, “behind a cloud of lies.” Even the IAEA Direc<strong>to</strong>r General has declared that Iran<br />

engaged in a longst<strong>and</strong>ing “policy of concealment.”<br />

Iran’s safeguards agreement is based on the st<strong>and</strong>ard NPT safeguards model<br />

agreement found in IAEA Information Circular (INFCIRC) 153. Under this agreement,<br />

Iran is obligated <strong>to</strong> provide the IAEA <strong>with</strong> information about the nuclear compounds it<br />

imported so that safeguards could be applied. Iran’s safeguards agreement <strong>with</strong> the<br />

IAEA also allows that “nuclear material that would otherwise be subject <strong>to</strong> safeguards<br />

shall be exempted from safeguards at the request of the State” provided that nuclear<br />

material does not exceed a certain quantity. Iran should have reported the nuclear<br />

material it received in 1991 from a different country when it received that material. (Two<br />

of the compounds in question – uranium hexafluoride (UF6) <strong>and</strong> uranium oxide (U02) –<br />

meet the threshold for application of safeguards.) If Iran had done so, it could have<br />

sought <strong>to</strong> obtain an exemption from the application of these safeguards for any quantities<br />

that were below the threshold level. Iran, however, did neither; therefore, Iran’s actions<br />

<strong>with</strong> regard <strong>to</strong> the materials received in February 1991 violate Iran’s obligations under<br />

Article III, paragraph 1 of the NPT. So also do Iran’s undeclared experiments <strong>with</strong><br />

uranium conversion, plu<strong>to</strong>nium separation, <strong>and</strong> laser iso<strong>to</strong>pe separation.<br />

In November 1996, Iranian authorities permitted the IAEA <strong>to</strong> conduct<br />

environmental sampling as provided for under part one of the IAEA Strengthened<br />

Safeguards System (SSS). In 2003, the IAEA extensively sampled newly disclosed<br />

Iranian facilities as part of its ongoing investigation in<strong>to</strong> Iran’s nuclear program. Samples<br />

taken by the IAEA at Natanz after the public revelation of that facility in 2002, however<br />

– along <strong>with</strong> samples taken at the Kalaye Electric compound <strong>and</strong> the Fary<strong>and</strong> Technique<br />

centrifuge workshop – indicated the presence of enriched uranium (<strong>and</strong> in one instance,<br />

78


very highly enriched uranium). Iran has claimed that these samples resulted only from<br />

foreign contamination on centrifuge components acquired abroad. Through the end of<br />

the period of this Report, the IAEA continued <strong>to</strong> investigate the HEU particles found at<br />

Iranian centrifuge facilities.<br />

Iran’s failure <strong>to</strong> ratify <strong>and</strong> fully abide by the IAEA Additional Pro<strong>to</strong>col – <strong>and</strong> its<br />

continuing efforts <strong>to</strong> stymie international inspec<strong>to</strong>rs through such means as remodeling<br />

the interior of the Kalaye Electric facility or razing the building at Lavisan before they<br />

could be inspected by the IAEA – underline Iran’s lack of good faith in complying <strong>with</strong><br />

its safeguards agreement <strong>and</strong> its NPT obligations.<br />

In June 2001, Iranian President Mohammed Khatami was reelected in a l<strong>and</strong>slide<br />

election vic<strong>to</strong>ry. Despite short-lived signs of possible moderation <strong>with</strong>in the Iranian<br />

regime, there is no evidence that Iran’s nuclear ambitions have changed. More recently,<br />

vic<strong>to</strong>ries by clerically-supported conservatives in the Iranian national legislature – not <strong>to</strong><br />

mention explicit declarations by some legisla<strong>to</strong>rs that they will not ratify the Additional<br />

Pro<strong>to</strong>col – casts further doubt upon the prospect of Iranian compliance <strong>and</strong> on Iran’s<br />

continued commitment <strong>to</strong> its IAEA <strong>and</strong> NPT obligations. The United States assesses that<br />

Iran has an ongoing program aimed at developing nuclear weapons, <strong>and</strong> it continues its<br />

efforts <strong>to</strong> exp<strong>and</strong> its nuclear infrastructure <strong>to</strong> support nuclear weapons development <strong>and</strong><br />

manufacture.<br />

Because of the U.S. assessment that Iran is intent on developing a nuclear<br />

weapons capability, the United States has long had a policy of not engaging in any<br />

nuclear cooperation <strong>with</strong> Iran. We continue <strong>to</strong> urge other countries <strong>to</strong> forego any nuclear<br />

cooperation <strong>with</strong> Iran. Moreover, until early in 2000, when trade sanctions were lifted on<br />

Iranian pistachio nuts <strong>and</strong> carpets, the United States had maintained a virtually complete<br />

trade <strong>and</strong> investment embargo against Iran since 1995. In 1996, the Iran <strong>and</strong> Libya<br />

Sanctions Act (ILSA), which provides for the imposition of sanctions against persons<br />

making certain investments in the petroleum sec<strong>to</strong>rs of Iran <strong>and</strong> Libya, became law. It<br />

provides for sanctions designed in part <strong>to</strong> deny Iran the ability <strong>to</strong> fund the acquisition of<br />

weapons of mass destruction <strong>and</strong> missile delivery systems. The United States urges other<br />

governments <strong>to</strong> act rapidly <strong>and</strong> effectively <strong>to</strong> apply such pressures on Iran in order <strong>to</strong><br />

emphasize <strong>to</strong> its leaders that continued pursuit of nuclear weapons is in the interest<br />

neither of the Iranian people nor of Iranian national security.<br />

Iran’s nuclear procurement activities <strong>and</strong> public revelations, including the<br />

evidence reported by IAEA DG ElBaradei in his multiple reports <strong>to</strong> the IAEA Board of<br />

Governors, confirm our assessment that Iran has been vigorously pursuing a nuclear<br />

weapons capability. This conclusion is based on Iran’s documented 18-year record of<br />

secret nuclear procurement <strong>and</strong> development, its systematic deceptions of the IAEA, <strong>and</strong><br />

the economic implausibility of its expensive <strong>and</strong> technically over ambitious nuclear fuel<br />

cycle program. Iran is attempting <strong>to</strong> obtain a broad range of foreign nuclear <strong>and</strong> nuclearrelated<br />

technology <strong>and</strong> equipment, most elements of which appear more suited for a<br />

weapons program than <strong>to</strong> meeting Iran’s legitimate energy needs. For example, Iran<br />

79


continues <strong>to</strong> build a heavy water production plant <strong>and</strong> <strong>to</strong> pursue heavy water reac<strong>to</strong>r<br />

design, intending <strong>to</strong> build <strong>and</strong> operate a heavy water reac<strong>to</strong>r, which is ideally suited for<br />

producing weapons-usable plu<strong>to</strong>nium. Iran claims its uranium mining activities are <strong>to</strong><br />

fuel power reac<strong>to</strong>rs, but Iran does not have enough domestic uranium deposits <strong>to</strong> fuel<br />

even one reac<strong>to</strong>r for its lifetime, although those deposits are sufficient for a nuclear<br />

weapons program. Iran has acknowledged undertaking experiments involving uranium<br />

metal, which has uses in its AVLIS program <strong>and</strong> is a necessary component <strong>to</strong> nuclear<br />

weapons design. Iran has also acknowledged pursuing uranium enrichment via<br />

centrifuges <strong>and</strong> its AVLIS program. Iran has admitted <strong>to</strong> conducting undeclared<br />

plu<strong>to</strong>nium separation experiments, giving Iran important knowledge in support of<br />

weapons intentions. Although Iran pledged in Oc<strong>to</strong>ber 2003 <strong>to</strong> provide full cooperation<br />

<strong>and</strong> transparency <strong>to</strong> the IAEA, we do not believe Iran has made a strategic decision <strong>to</strong><br />

ab<strong>and</strong>on its longst<strong>and</strong>ing nuclear weapons ambitions <strong>and</strong> has not admitted the full scope<br />

of its nuclear activity <strong>to</strong> international authorities.<br />

FINDING. Article II prohibits NNWS from seeking or receiving assistance in the<br />

manufacture of nuclear weapons. It also prohibits NNWS from the receipt, manufacture<br />

or other acquisition of such weapons. The United States has previously found that Iran is<br />

pursuing a nuclear weapons capability. The breadth of Iran’s nuclear development<br />

efforts, the secrecy <strong>and</strong> deceptions <strong>with</strong> which they have been conducted for nearly 20<br />

years, its redundant <strong>and</strong> surreptitious procurement channels, Iran’s persistent failure <strong>to</strong><br />

comply <strong>with</strong> its obligations <strong>to</strong> report <strong>to</strong> the IAEA <strong>and</strong> <strong>to</strong> apply safeguards <strong>to</strong> such<br />

activities, <strong>and</strong> the lack of a reasonable economic justification for this program leads us <strong>to</strong><br />

conclude that Iran is pursuing an effort <strong>to</strong> manufacture nuclear weapons, <strong>and</strong> has sought<br />

<strong>and</strong> received assistance in this effort in violation of Article II of the NPT. This weapons<br />

program combines elements of not only the activities declared <strong>to</strong> the IAEA <strong>and</strong><br />

ostensibly run by the civilian A<strong>to</strong>mic Energy Organization of Iran (AEOI), but also any<br />

still undeclared fuel cycle <strong>and</strong> other activities that may exist, including those that may be<br />

run solely be the military.<br />

In addition, Iran’s past failure <strong>to</strong> declare the import of UF6, failure <strong>to</strong> provide<br />

design information <strong>to</strong> the IAEA on the existing centrifuge facility prior <strong>to</strong> the<br />

introduction of nuclear material, <strong>and</strong> its conduct of undeclared laser iso<strong>to</strong>pe separation,<br />

uranium conversion experiments, <strong>and</strong> plu<strong>to</strong>nium separation work further reinforce this<br />

assessment <strong>and</strong> also make clear that Iran has violated Article III of the NPT <strong>and</strong> its IAEA<br />

safeguards agreement.<br />

IRAQ<br />

ISSUE. During Iraqi dicta<strong>to</strong>r Saddam Hussein’s regime prior <strong>to</strong> 1991, Iraq<br />

engaged in activities that raised concerns regarding Iraq’s compliance <strong>with</strong> its NPT<br />

Article II <strong>and</strong> Article III (safeguards) obligations <strong>and</strong> its adherence <strong>to</strong> UN Security<br />

Council resolutions.<br />

80


HISTORY OF COMPLIANCE EVALUATION. The United States assessed<br />

Iraq’s compliance <strong>with</strong> the NPT as early as the January 14, 1993 Report. At that time,<br />

the United States concluded that prior <strong>to</strong> 1991, Iraq had an active nuclear weapons<br />

program that violated its Article II NPT obligations <strong>and</strong> that its noncompliance <strong>with</strong> its<br />

Safeguards Agreement constituted a violation of Article III. In the July 1, 1996 Report,<br />

this finding was exp<strong>and</strong>ed <strong>to</strong> include a determination that Iraq also had been “in violation<br />

of its obligation under UN Security Resolutions <strong>to</strong> declare <strong>and</strong> destroy its prohibited<br />

WMD <strong>and</strong> long-range missile programs <strong>and</strong> <strong>to</strong> cooperate fully <strong>with</strong> UN <strong>and</strong> IAEA<br />

inspections <strong>and</strong> moni<strong>to</strong>ring.” In subsequent years, our compliance judgment did not<br />

change regarding these pre-1991 activities. In the June 2003 Noncompliance Report, the<br />

United States concluded that:<br />

Iraq had pursued an active nuclear weapons development program that<br />

violated its obligations under its Safeguards Agreement <strong>and</strong> Articles II <strong>and</strong><br />

III of the NPT. The United States Government has further determined that<br />

Baghdad is in violation of its obligation under UN Security Council<br />

resolutions <strong>to</strong> declare <strong>and</strong> destroy its prohibited WMD <strong>and</strong> long-range<br />

missile programs <strong>and</strong> <strong>to</strong> cooperate fully <strong>with</strong> UN <strong>and</strong> IAEA inspections<br />

<strong>and</strong> moni<strong>to</strong>ring.<br />

DISCUSSION OF OBLIGATIONS. Iraq signed the NPT in July 1968 <strong>and</strong><br />

deposited its instrument of ratification in Oc<strong>to</strong>ber 1969. Iraq’s full-scope safeguards<br />

agreement <strong>with</strong> the IAEA entered in<strong>to</strong> force in February 1972.<br />

ACTIONS. During Saddam Hussein’s regime prior <strong>to</strong> 1991, Iraq engaged in<br />

activities that violated its Article II <strong>and</strong> III obligations. It secretly irradiated indigenously<br />

manufactured target materials <strong>and</strong> IAEA-exempted fuel elements in a safeguarded<br />

research reac<strong>to</strong>r at the Tuwaitha Nuclear Research Center. This irradiated material was<br />

used in an undeclared pilot-scale reprocessing experiment using labora<strong>to</strong>ry hot cells. Iraq<br />

also conducted undeclared uranium enrichment operations <strong>and</strong> produced associated feed<br />

materials in direct contravention of Iraq’s NPT safeguards agreement, <strong>and</strong> built a facility<br />

intended for nuclear weapons development <strong>and</strong> assembly.<br />

Iraq cl<strong>and</strong>estinely explored virtually every method <strong>to</strong> enrich uranium in its pre-<br />

1991 nuclear weapons program, including Electro-Magnetic Iso<strong>to</strong>pe Separation (EMIS),<br />

centrifuge, gaseous diffusion, laser iso<strong>to</strong>pe separation, <strong>and</strong> chemical enrichment<br />

techniques. Of these, EMIS progressed farthest, <strong>with</strong> two production-scale facilities<br />

having been under development as of 1991. Centrifuge efforts probably were poised <strong>to</strong><br />

advance past labora<strong>to</strong>ry-scale work <strong>with</strong> the aim of eventually replacing EMIS as the<br />

primary enrichment effort. Labora<strong>to</strong>ry pilot-scale chemical enrichment efforts appear <strong>to</strong><br />

have been intended <strong>to</strong> enhance EMIS enrichment.<br />

After the 1991 Gulf War, Iraq endeavored <strong>to</strong> conceal its nuclear program by<br />

removing <strong>and</strong> concealing telltale equipment, material <strong>and</strong> documentation; in some cases,<br />

81


y unilaterally destroying <strong>and</strong> burying other equipment <strong>and</strong> materials; <strong>and</strong> by denying the<br />

actual role of key facilities.<br />

In August 1998, in violation of UN Security Council resolutions (UNSCR) <strong>and</strong> a<br />

February 1998 Memor<strong>and</strong>um of Underst<strong>and</strong>ing between the UN Secretary-General <strong>and</strong><br />

Iraqi Deputy Prime Minister Tariq Aziz, Iraq suspended cooperation <strong>with</strong> the UN Special<br />

Commission (UNSCOM) <strong>and</strong> the IAEA. Although the IAEA was able <strong>to</strong> continue<br />

limited activities until December 1998, there were no UN-m<strong>and</strong>ated moni<strong>to</strong>ring or<br />

inspections activities in Iraq between December 1998 <strong>and</strong> November 27, 2002, following<br />

adoption of UNSCR 1441.<br />

In January <strong>and</strong> December 2002 as well as June 2003, the IAEA, in accordance<br />

<strong>with</strong> its NPT safeguards agreement <strong>with</strong> Iraq, conducted a physical inven<strong>to</strong>ry verification<br />

(PIV) inspection of declared material in Iraq. These inspections were not pursuant <strong>to</strong> the<br />

authority granted the IAEA under Security Council resolutions <strong>and</strong> thus was limited in<br />

scope. They did not satisfy or address Iraq’s disarmament obligations. The IAEA’s<br />

Direc<strong>to</strong>r-General stated at the time of the January 2002 inspection that the “limited<br />

objective” of the PIV was neither sufficient <strong>to</strong> provide any assurance that Iraq is in full<br />

compliance <strong>with</strong> its safeguards obligations nor a substitute for the Agency’s activities<br />

under the relevant Security Council resolutions.<br />

On November 8, 2002, UNSCR 1441 incorporated crucial elements sought by the<br />

U.S. Government: a clear statement that Iraq was in material breach of its international<br />

obligations, enhanced authority for the inspections regime, <strong>and</strong> a warning of serious<br />

consequences should Iraq continue <strong>to</strong> violate its obligations. Furthermore, the resolution<br />

set out a clear timetable for Iraq’s submission of an accurate, full <strong>and</strong> complete<br />

declaration of WMD <strong>and</strong> related programs <strong>and</strong> for the resumption of inspections, <strong>and</strong><br />

strengthened the m<strong>and</strong>ate of both UNMOVIC <strong>and</strong> the IAEA’s Iraq Nuclear Verification<br />

Office.<br />

Iraq agreed <strong>to</strong> renewed UN inspections under UNMOVIC in November 2002, <strong>and</strong><br />

UNMOVIC <strong>and</strong> IAEA issued daily inspections reports from November 27, 2002 <strong>to</strong><br />

March 13, 2003.<br />

Prior <strong>to</strong> Operation Iraqi Freedom (OIF), which <strong>to</strong>ok place between March 20 <strong>and</strong><br />

May 1, 2003, Iraq was legally bound by the NPT, <strong>and</strong> by a suite of UN Security Council<br />

Resolutions obligating it <strong>to</strong> declare <strong>and</strong> destroy its WMD s<strong>to</strong>ckpiles <strong>and</strong> capabilities. The<br />

passage of UNSCR 1483 in May 2003 reaffirmed that Iraq had <strong>to</strong> meet these<br />

disarmament obligations, <strong>and</strong> asked the United States <strong>and</strong> UK <strong>to</strong> keep the UNSC<br />

informed of U.S./UK activities in this regard. In June 2003, the Iraq Survey Group<br />

(ISG), composed of largely military experts from coalition countries, assumed<br />

responsibility for the WMD/missile effort.<br />

On Oc<strong>to</strong>ber 2, 2003, Dr. David Kay submitted an Interim Progress Report on the<br />

Activities of the Iraq Survey Group <strong>to</strong> Senate <strong>and</strong> House intelligence committees.<br />

82


Dr. Kay reported that Saddam Hussein had not given up his aspirations <strong>and</strong> intentions <strong>to</strong><br />

continue <strong>to</strong> acquire a nuclear weapons program <strong>and</strong> intended <strong>to</strong> resume WMD-related<br />

activities whenever external restrictions were removed. Upon the fall of Saddam<br />

Hussein’s regime as a consequence of Operation Iraqi Freedom, Iraq was for a time not in<br />

a position as a sovereign nation <strong>to</strong> express any intent <strong>with</strong> regards <strong>to</strong> the NPT; Iraq’s legal<br />

obligations <strong>with</strong> regard <strong>to</strong> NPT remained the same as before OIF.<br />

Dr. Kay noted dozens of WMD-related program activities but no s<strong>to</strong>ckpiles per se.<br />

Iraqi scientists <strong>and</strong> officials admitted <strong>to</strong> deliberately <strong>with</strong>holding WMD-related<br />

information from UN inspec<strong>to</strong>rs. Equipment components, blueprints, <strong>and</strong> documents<br />

from the pre-1991 Iraqi nuclear weapons program were hidden from the United States<br />

<strong>and</strong> IAEA until 2003. While the order was never given, Saddam Hussein intended <strong>to</strong><br />

rebuild Iraq’s nuclear program after UN sanctions were lifted.<br />

In September 2004, Charles Duelfer issued a comprehensive report of the Special<br />

Advisor <strong>to</strong> the Direc<strong>to</strong>r of Central Intelligence on Iraq’s WMD. The report notes that<br />

Saddam ended the nuclear program in 1991 following the Gulf War. Although Saddam<br />

continued <strong>to</strong> see the utility of WMD <strong>and</strong> sought <strong>to</strong> preserve the ability <strong>to</strong> reconstitute the<br />

Iraqi nuclear program, the report notes that the Iraqi Survey Group found a limited<br />

number of post-1995 activities that would have aided the reconstitution of the nuclear<br />

weapons program once sanctions were lifted. The activities of the Iraqi A<strong>to</strong>mic Energy<br />

Commission (IAEC) sustained some talent <strong>and</strong> limited research <strong>with</strong> potential relevance<br />

<strong>to</strong> a reconstituted nuclear program. Specific projects, <strong>with</strong> significant developments,<br />

such as the efforts <strong>to</strong> build a rail gun <strong>and</strong> a copper vapor laser could have been useful in a<br />

future effort <strong>to</strong> restart a nuclear weapons program, but ISG found no indications of such<br />

purpose. As funding for the Military Industrial Commission <strong>and</strong> the IAEC increased<br />

after the introduction of the Oil-for-Food program, there was some growth in programs<br />

that involved former nuclear weapons scientists <strong>and</strong> engineers.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. While the 1991<br />

Gulf War <strong>and</strong> the resulting UN-m<strong>and</strong>ated inspections significantly set back Saddam<br />

Hussein’s program <strong>to</strong> develop a nuclear weapon during the 1990s, more than ten years of<br />

sanctions <strong>and</strong> the loss of much of Iraq’s physical nuclear infrastructure under IAEA<br />

oversight hampered the regime’s ability <strong>to</strong> acquire or develop nuclear weapons but it did<br />

not diminish the regime’s interest in resuming its nuclear weapons program whenever<br />

external restrictions were removed. Iraq’s pre-1991 cl<strong>and</strong>estine nuclear weapons<br />

program constituted a clear violation of Article II of the NPT. Baghdad’s construction of<br />

secret facilities, including a facility for nuclear weapons development <strong>and</strong> assembly, are<br />

among the key indicia of this violation. Iraq’s failure <strong>to</strong> apply safeguards <strong>to</strong> its<br />

cl<strong>and</strong>estine program also constituted a violation of Article III, which requires that<br />

safeguards be applied <strong>to</strong> all “source or specialized fissionable material <strong>with</strong>in its<br />

jurisdiction.” Over the years of inspections, IAEA inspec<strong>to</strong>rs noted Iraq <strong>with</strong>held<br />

important details relevant <strong>to</strong> its nuclear program, including procurement logs, technical<br />

documents, experimental data, accounting of materials, <strong>and</strong> foreign assistance. It also<br />

likely <strong>with</strong>held other data about enrichment techniques, foreign procurement, weapons<br />

83


design <strong>and</strong> the role of Iraqi security services in concealing its nuclear facilities <strong>and</strong><br />

activities.<br />

During Saddam Hussein’s regime, Baghdad continued <strong>to</strong> maintain a cl<strong>and</strong>estine<br />

procurement network which could be used for procuring nuclear items. Saddam Hussein<br />

gave explicit direction <strong>to</strong> sustain the intellectual capability achieved over so many years<br />

<strong>and</strong> supported key technical groups who continued work on nuclear-relevant dual-use<br />

technologies. Virtually no senior Iraqi believed that Saddam had foresaken WMD<br />

forever. Evidence suggests that, as resources became available <strong>and</strong> the constraints of<br />

sanctions decayed, there was a direct expansion of activity that would have the effect of<br />

supporting WMD reconstitution.<br />

FINDING. The United States finds that Iraq, during the course of the Saddam<br />

Hussein regime prior <strong>to</strong> 1991, pursued an active nuclear weapons development program<br />

<strong>and</strong> that various aspects of this program violated its obligations under Articles II <strong>and</strong> III<br />

of the NPT. The United States has further determined that during this period Baghdad<br />

was in violation of its obligation under UN Security Council resolutions <strong>to</strong> declare <strong>and</strong><br />

destroy its prohibited WMD <strong>and</strong> long-range missile programs <strong>and</strong> <strong>to</strong> cooperate fully <strong>with</strong><br />

UN <strong>and</strong> IAEA inspections <strong>and</strong> moni<strong>to</strong>ring.<br />

LIBYA<br />

ISSUE. Prior <strong>to</strong> December 19, 2003, the People’s Libyan Arab Jamahiriya<br />

(Libya) engaged in activities that raised concerns regarding Libya’s compliance <strong>with</strong> its<br />

NPT Article II <strong>and</strong> Article III obligations, as well as <strong>with</strong> its IAEA safeguards<br />

obligations.<br />

HISTORY OF COMPLIANCE EVALUATION. The United States assessed<br />

Libya’s compliance <strong>with</strong> the NPT as early as the January 14, 1993 Report. At that time,<br />

the United States concluded that despite Libya’s status as an NPT party, Colonel Qadhafi<br />

had a well-known <strong>and</strong> long-st<strong>and</strong>ing desire for nuclear weapons <strong>and</strong> Libya was covertly<br />

seeking <strong>to</strong> acquire technology relevant <strong>to</strong> nuclear weapons production. The May 30,<br />

1995 Report noted that Libya had demonstrated a continuing interest in the acquisition of<br />

enrichment-related equipment, but that its nuclear program had not progressed beyond<br />

the early stages of developing nuclear weapons. This finding was modified slightly in the<br />

CY1998 Report, <strong>to</strong> state that Libya’s nuclear weapons program had not progressed<br />

beyond the early stages of developing an independent nuclear research <strong>and</strong> fuel-cycle<br />

related capability. In the June 2003 Noncompliance Report, the United States concluded<br />

that:<br />

The United States has determined that Libya has demonstrated a<br />

continuing interest in the acquisition of nuclear weapons. Since UN<br />

sanctions were suspended in 1999, Libya has resumed investment in its<br />

nuclear infrastructure.<br />

84


DISCUSSION OF OBLIGATIONS. Libya signed the NPT in July 1968 <strong>and</strong><br />

ratified it in May 1975. Its full-scope Safeguards Agreement <strong>with</strong> the IAEA entered in<strong>to</strong><br />

force in July 1980. During most of the period of this Report, Libya did not accept the<br />

broader safeguards strengthening measures embodied in the Additional Pro<strong>to</strong>col, which<br />

include exp<strong>and</strong>ed IAEA rights <strong>to</strong> visit undeclared <strong>and</strong> suspected sites. In late December<br />

2003, however, Libya stated its intention <strong>to</strong> act as if the Pro<strong>to</strong>col were in force as of<br />

December 29, 2003, pending its formal entry in<strong>to</strong> force. Libya signed the Additional<br />

Pro<strong>to</strong>col on March 10, 2004. Libya signed the African Nuclear Weapon Free Zone<br />

Treaty in 1996, but has not ratified it.<br />

ACTIONS. In March 2003, Libya began discussions <strong>with</strong> the United States <strong>and</strong><br />

the United Kingdom regarding Libya’s WMD <strong>and</strong> MTCR-class missile programs. This<br />

launched nine months of delicate <strong>and</strong> secret negotiations between Libya, the United<br />

States, <strong>and</strong> the United Kingdom, resulting in Libya’s public commitment on December<br />

19, 2003, <strong>to</strong> reveal <strong>and</strong> eliminate its WMD programs. On March 2, 2004, Qadhafi<br />

publicly explained that during the Cold War, Libya had sought <strong>to</strong> develop nuclear<br />

weapons, but that “now … if you built a nuclear bomb you would be in big trouble.” He<br />

said that it was now in Libya’s “own interest” <strong>to</strong> relinquish pursuit of nuclear weapons,<br />

because “the nuclear bomb represents a danger <strong>to</strong> the country which has them.”<br />

Since December 19, 2003, the United States, in conjunction <strong>with</strong> the United<br />

Kingdom, has worked <strong>to</strong> assist Libya in implementing its decision <strong>to</strong> eliminate its nuclear<br />

weapons program. This cooperative activity has included extensive interaction <strong>with</strong> U.S.<br />

<strong>and</strong> UK officials both in Libya <strong>and</strong> abroad in connection <strong>with</strong> the removal of<br />

proliferation-sensitive items <strong>and</strong> material from Libya, as well as U.S./UK efforts <strong>to</strong> assist<br />

Libya in meeting its IAEA safeguards obligations, including under the Additional<br />

Pro<strong>to</strong>col. The IAEA has conducted inspections, starting in January 2004, <strong>to</strong> confirm<br />

Libya’s revised declarations.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. Prior <strong>to</strong> Qadhafi’s<br />

December 19, 2003, decision <strong>to</strong> eliminate Libya’s nuclear weapons program, the United<br />

States had urged other countries <strong>to</strong> refrain from engaging in nuclear cooperation <strong>with</strong><br />

Libya because of Tripoli’s stated interest in acquiring nuclear weapons.<br />

Libya’s Russian-assisted efforts in 2000 <strong>to</strong> res<strong>to</strong>re <strong>and</strong> upgrade its nuclear<br />

infrastructure following the lifting of UN sanctions raised concerns that the program may<br />

have been active beyond our previous estimates.<br />

Since Oc<strong>to</strong>ber 2003, Libyan officials have revealed the scope of Libya’s<br />

previously undeclared nuclear activities. These activities included a gas centrifuge<br />

program, undeclared labora<strong>to</strong>ry-scale <strong>and</strong> bench-scale uranium conversion experiments, a<br />

uranium conversion facility, <strong>and</strong> previously undeclared s<strong>to</strong>cks of uranium yellowcake.<br />

Libya also bought a supply of uranium hexafluoride (UF6) which is used as feeds<strong>to</strong>ck in<br />

gas centrifuges, <strong>and</strong> had received nuclear weapons design documents from the Khan<br />

network.<br />

85


Libya’s longst<strong>and</strong>ing interest in acquiring nuclear weapons, Libya’s efforts <strong>to</strong><br />

obtain <strong>and</strong> develop the infrastructure for an indigenous nuclear weapons capability,<br />

including through acquisition from the A.Q. Khan network, <strong>and</strong> its receipt of nuclear<br />

weapons design documents are clear indications that it sought <strong>and</strong> received assistance for<br />

the expressed purpose of manufacturing nuclear weapons in violation of its obligations<br />

under Article II of the NPT. Libya’s previous failure <strong>to</strong> declare <strong>to</strong> the IAEA certain<br />

nuclear material <strong>and</strong> certain activities involving nuclear material (including experiments<br />

involving plu<strong>to</strong>nium production <strong>and</strong> separation <strong>and</strong> uranium conversion) constituted a<br />

violation of its IAEA safeguards agreement <strong>and</strong> of the NPT’s Article III, which requires<br />

that safeguards be applied <strong>to</strong> all “source or specialized fissionable material <strong>with</strong>in its<br />

jurisdiction.”<br />

In the IAEA Board of Governors meeting in March 2004, the Direc<strong>to</strong>r General of<br />

the IAEA was requested <strong>to</strong> report <strong>to</strong> the Security Council, for information purposes only,<br />

Libya’s past failure <strong>to</strong> meet its obligations under its safeguards agreement <strong>with</strong> the IAEA.<br />

On April 22, 2004, the UN Security Council <strong>to</strong>ok note of the IAEA resolution, welcomed<br />

Libya’s decision <strong>to</strong> ab<strong>and</strong>on its programs for developing WMD <strong>and</strong> their means of<br />

delivery, <strong>and</strong> encouraged Libya <strong>to</strong> ensure the verified elimination of all of its WMD<br />

programs.<br />

FINDING. The United States finds that prior <strong>to</strong> its decision <strong>to</strong> rid itself of its<br />

WMD <strong>and</strong> long-range missile programs, Libya pursued an active nuclear weapons<br />

development program, <strong>and</strong> that various aspects of this program violated Libya’s<br />

obligations under Articles II <strong>and</strong> III of the NPT, as well as its IAEA safeguards<br />

agreement. Consistent <strong>with</strong> the IAEA statute, Libya’s previous safeguards<br />

noncompliance was reported <strong>to</strong> the UN Security Council.<br />

The United States notes, however, that Libya has worked <strong>with</strong> the United States<br />

<strong>and</strong> United Kingdom <strong>to</strong> remove virtually all declared proliferation-sensitive documents,<br />

equipment <strong>and</strong> material directly associated <strong>with</strong> its previously covert nuclear program,<br />

including design documents, UF6, gas centrifuges, various components, the uranium<br />

conversion facility, <strong>and</strong> dual-use equipment <strong>and</strong> materials. Libya is also working <strong>with</strong><br />

the United States <strong>and</strong> Russia <strong>to</strong> convert the Tajura reac<strong>to</strong>r <strong>to</strong> low-enriched uranium<br />

(LEU) <strong>and</strong> permit the removal of its fresh <strong>and</strong> irradiated HEU. On March 7, 2004, about<br />

17 kilograms of unirradiated, fresh HEU was removed from Tajura <strong>and</strong> flown <strong>to</strong> Russia<br />

under the Tripartite Russian Research Fuel-Return Program. Preparations for the<br />

conversion of the Tajura reac<strong>to</strong>r <strong>to</strong> LEU have begun, the irradiated HEU will be removed<br />

following the conversion.<br />

On April 22, 2004, the UN Security Council welcomed Libya’s decision <strong>to</strong><br />

ab<strong>and</strong>on its programs for developing WMD <strong>and</strong> their means of delivery.<br />

86


NORTH KOREA<br />

ISSUE. The Democratic People’s Republic of Korea (DPRK) is pursuing an<br />

active nuclear weapons development program. The issue is whether this program<br />

violated the DPRK’s obligations under the NPT, its IAEA safeguards agreement <strong>and</strong> its<br />

political commitments <strong>to</strong> the United States under the 1994 Agreed Framework <strong>and</strong> the<br />

North-South Joint Declaration on the Denuclearization of the Korean Peninsula.<br />

HISTORY OF COMPLIANCE EVALUATION. The United States assessed<br />

North Korea’s compliance <strong>with</strong> the NPT as early as the January 14, 1993 Report. At that<br />

time, the United States concluded in the unclassified version of the Report that based<br />

upon North Korea’s actions since IAEA inspections began, the DPRK was “attempting <strong>to</strong><br />

hide facilities that may contain evidence indicating a DPRK violation of NPT Articles II<br />

or III, or both.” The next year, the Report noted that “North Korea’s refusal in 1994 <strong>to</strong><br />

permit the IAEA <strong>to</strong> conduct routine, ad-hoc, or special inspections constitutes<br />

noncompliance <strong>with</strong> its Article III obligations.” It also said that “although conclusive<br />

statements cannot yet be made about the extent <strong>to</strong> which North Korea is concealing<br />

evidence that would indicate a violation of its Article II commitments,” the United States<br />

believes that the DPRK’s efforts <strong>to</strong> prevent the IAEA from learning about past activity<br />

“raises serious questions about a potential violation of Article II. In 1995, the United<br />

States declared that “North Korea has yet <strong>to</strong> meet its Article III obligations,” <strong>and</strong> that<br />

“[s]erious questions remain regarding the DPRK’s intentions <strong>and</strong> a potential violation of<br />

its obligations under Article II of the NPT.” A similar finding was made in the three<br />

subsequent reports. The June 2003 Report declared that:<br />

… North Korea continues <strong>to</strong> be in violation of its IAEA safeguards<br />

agreement <strong>and</strong> … has produced enough plu<strong>to</strong>nium for one or more nuclear<br />

weapons. The United States judges that the DPRK is in violation of the<br />

NPT <strong>and</strong> that it has not complied <strong>with</strong> its international commitments under<br />

the Agreed Framework, <strong>and</strong> the Joint South-North Declaration on the<br />

Denuclearization of the Korean Peninsula.<br />

DISCUSSION OF OBLIGATIONS<br />

Agreed Framework. In Oc<strong>to</strong>ber 1994, North Korea <strong>and</strong> the United States signed<br />

the Agreed Framework. Pursuant <strong>to</strong> these commitments, North Korea initially was <strong>to</strong><br />

freeze <strong>and</strong> eventually <strong>to</strong> dismantle its graphite-moderated nuclear reac<strong>to</strong>rs <strong>and</strong> related<br />

facilities at Yongbyon <strong>and</strong> Taechon in exchange for two light-water reac<strong>to</strong>rs (LWRs) <strong>and</strong><br />

interim energy assistance in the form of heavy fuel oil. Under the Agreed Framework,<br />

North Korea was required <strong>to</strong> be in full compliance <strong>with</strong> its safeguards agreement <strong>with</strong> the<br />

IAEA before any key nuclear components for the LWRs could be delivered. In<br />

accordance <strong>with</strong> the Agreed Framework, from 1994 <strong>to</strong> December 2002, North Korea<br />

allowed the IAEA <strong>to</strong> moni<strong>to</strong>r the freeze on its nuclear reac<strong>to</strong>rs <strong>and</strong> related facilities, <strong>and</strong><br />

<strong>to</strong> maintain a continuous presence at Yongbyon. Under the Framework, North Korea<br />

also committed <strong>to</strong> “consistently take steps <strong>to</strong> implement the North-South Joint<br />

87


Declaration on the Denuclearization of the Korean Peninsula.” Article III of the Joint<br />

Declaration on the Denuclearization calls for North <strong>and</strong> South Korea not <strong>to</strong> possess<br />

uranium enrichment <strong>and</strong> nuclear reprocessing facilities.<br />

In Oc<strong>to</strong>ber 2002, when confronted by the United States about its cl<strong>and</strong>estine<br />

efforts <strong>to</strong> develop a uranium enrichment capability, North Korea acknowledged<br />

possessing a uranium enrichment program for nuclear weapons, though it has since<br />

denied this. Furthermore, DPRK officials <strong>to</strong>ld the United States that they considered the<br />

United States <strong>to</strong> have effectively nullified the Agreed Framework. The Agreed<br />

Framework does not specify a mechanism for termination or <strong>with</strong>drawal. However,<br />

Secretary of State Colin Powell acknowledged that, in light of the DPRK’s statements<br />

about developing an enrichment capability, the DPRK’s actions had effectively nullified<br />

the agreement. Prior <strong>to</strong> that time, however, North Korea failed <strong>to</strong> meet several<br />

important, voluntarily undertaken political commitments <strong>to</strong> the United States under the<br />

Agreed Framework <strong>and</strong> the North-South Joint Declaration on the Denuclearization of the<br />

Korean Peninsula.<br />

NPT. North Korea acceded <strong>to</strong> the NPT in December 1985, but did not sign its<br />

Safeguards Agreement (INFCIRC/403) <strong>with</strong> the IAEA until January 30, 1992. The<br />

Safeguards Agreement was ratified by North Korea on April 9, <strong>and</strong> brought in<strong>to</strong> force on<br />

April 10, 1992. The Safeguards Agreement (INCIRC/403) requires North Korea <strong>to</strong><br />

accept IAEA safeguards on all source <strong>and</strong> special fissionable material in all peaceful<br />

nuclear activities <strong>with</strong>in the terri<strong>to</strong>ry of the DPRK, <strong>with</strong>in its jurisdiction or carried out<br />

under its control anywhere.<br />

In 1993, North Korea provided notice of <strong>with</strong>drawal from the NPT under Article<br />

X. It then “suspended” its <strong>with</strong>drawal notice one day short of the three-month period<br />

required in Article X of the NPT for a <strong>with</strong>drawal <strong>to</strong> become effective. On January 10,<br />

2003, the DPRK notified the UN Security Council of its decision “<strong>to</strong> revoke the<br />

suspension on the effectuation” of its 1993 <strong>with</strong>drawal from the NPT, purportedly<br />

making the <strong>with</strong>drawal effective the next day. The United States, however, viewed North<br />

Korea’s 2003 notice as a new notice of <strong>with</strong>drawal under Article X of the NPT – thus<br />

triggering a new three-month period (after notice <strong>to</strong> all NPT Parties <strong>and</strong> the UN Security<br />

Council) before <strong>with</strong>drawal would be effective. In any case, North Korea continued <strong>to</strong> be<br />

bound by its NPT obligations – <strong>and</strong> its NPT safeguards agreement <strong>with</strong> the IAEA – until<br />

its 2003 notice of <strong>with</strong>drawal became effective.<br />

ACTIONS. On Oc<strong>to</strong>ber 21, 1994, the United States <strong>and</strong> North Korea signed an<br />

Agreed Framework, which, if fully implemented, would ultimately have resulted in<br />

dismantlement of North Korea’s indigenous plu<strong>to</strong>nium reac<strong>to</strong>r program <strong>and</strong> associated<br />

facilities. Although as an NPT party, North Korea was under a continuing obligation <strong>to</strong><br />

comply <strong>with</strong> its IAEA safeguards agreement, the Agreed Framework did not call for the<br />

DPRK <strong>to</strong> come in<strong>to</strong> full compliance <strong>with</strong> its safeguards agreement until a particular stage<br />

of the light-water reac<strong>to</strong>r (LWR) project – specifically, after a significant portion of the<br />

LWR program was completed, but before delivery of key nuclear components for the first<br />

88


LWR. Based on the original 2003 target completion date for the LWR project, this stage<br />

might have been reached before 2000, but delays in the project pushed the likely date for<br />

the DPRK coming in<strong>to</strong> full compliance many years later. As provided in the Agreed<br />

Framework, North Korea froze construction <strong>and</strong> operations at its graphite-moderated<br />

reac<strong>to</strong>rs <strong>and</strong> related facilities at Yongbyon <strong>and</strong> Taechon.<br />

Between 1994 (after the Agreed Framework was signed) <strong>and</strong> December 2002<br />

(when North Korea expelled IAEA inspec<strong>to</strong>rs from the country), North Korea allowed<br />

the IAEA <strong>to</strong> moni<strong>to</strong>r the freeze on its graphite-moderated nuclear reac<strong>to</strong>rs <strong>and</strong> related<br />

facilities, <strong>and</strong> <strong>to</strong> maintain a permanent presence at Yongbyon.<br />

Despite North Korea’s international obligations <strong>and</strong> commitments <strong>to</strong> freeze its<br />

nuclear program, we assess that at some point during the freeze on its plu<strong>to</strong>nium<br />

program, North Korea had embarked on an effort <strong>to</strong> develop a centrifuge-based uranium<br />

enrichment program. There have been press reports that the A.Q. Khan network provided<br />

enrichment technology, including centrifuges <strong>and</strong> uranium hexafluoride (the feeds<strong>to</strong>ck<br />

for gas centrifuge uranium enrichment programs) <strong>to</strong> the North Korean nuclear program.<br />

After the United States gained information about North Korea’s covert uranium<br />

enrichment program, a U.S. delegation traveled <strong>to</strong> Pyongyang in Oc<strong>to</strong>ber 2002 <strong>to</strong> convey<br />

our grave concerns. Our delegation advised the North Koreans that we had acquired<br />

information indicating that they had a program <strong>to</strong> enrich uranium for nuclear weapons in<br />

violation of the Agreed Framework <strong>and</strong> other agreements. North Korea’s First Vice<br />

Minister Kang Sok-chu acknowledged that such a program existed, though North Korean<br />

officials attempted <strong>to</strong> accuse the United States of nullifying the Agreed Framework.<br />

Following this acknowledgement, the United States determined that it could no longer<br />

proceed <strong>with</strong> the Agreed Framework on a business-as-usual basis. As a result, the<br />

members of the Executive Board of the Korean Peninsula Energy Economic<br />

Development Organization (KEDO) – the United States, Republic of Korea (ROK),<br />

Japan, <strong>and</strong> the EU – agreed in November 2002 <strong>to</strong> suspend shipments of heavy fuel oil<br />

beginning in December, while calling on North Korea promptly <strong>to</strong> eliminate its nuclear<br />

weapons program in a transparent <strong>and</strong> verifiable manner. In response <strong>to</strong> this KEDO<br />

action, the DPRK announced its intention <strong>to</strong> unfreeze the nuclear reac<strong>to</strong>r <strong>and</strong><br />

reprocessing facilities at Yongbyon.<br />

On December 12, 2002, North Korea announced that it would “immediately<br />

resume the operation <strong>and</strong> construction of its nuclear facilities <strong>to</strong> generate electricity.” On<br />

December 14, the DPRK instructed the IAEA <strong>to</strong> “remove the seals <strong>and</strong> cameras – that<br />

moni<strong>to</strong>r the nuclear facilities at the Yongbyon nuclear complex – <strong>and</strong> collect them.” On<br />

December 18, start-up preparations began on the steam plant used <strong>to</strong> provide heat <strong>to</strong> the<br />

reprocessing facility at Yongbyon. On December 27, North Korea wrote the IAEA that<br />

“we will soon be prepared for the operation” of the reprocessing plant, “<strong>to</strong> secure safe<br />

s<strong>to</strong>rage of the large quantity of spent fuel rods” that would eventually be removed from<br />

its graphite-moderated reac<strong>to</strong>rs “once these power plants are in operation.”<br />

89


On December 29, 2002, the DPRK Foreign Ministry issued a statement indicating<br />

that North Korea’s “special status” in the Non-Proliferation Treaty “is now in peril.” On<br />

December 31, the DPRK expelled the two IAEA inspec<strong>to</strong>rs resident in Yongbyon,<br />

prompting IAEA Direc<strong>to</strong>r General <strong>to</strong> publicly announce that North Korea was “a country<br />

in violation of its international obligations.” The DPRK’s expulsion of IAEA inspec<strong>to</strong>rs,<br />

the DG said, “sets a dangerous precedent for the integrity of the non-proliferation<br />

regime.” The IAEA stated that the departure of the inspec<strong>to</strong>rs left it “<strong>with</strong> virtually no<br />

possibility <strong>to</strong> moni<strong>to</strong>r the DPRK’s nuclear activities nor <strong>to</strong> provide any assurances <strong>to</strong> the<br />

international community that they are not producing a nuclear weapon.” On January 6,<br />

2003, the IAEA Board of Governors convened a special meeting on the DPRK <strong>and</strong> issued<br />

a resolution deploring North Korea’s unilateral acts <strong>to</strong> remove <strong>and</strong> impede the<br />

functioning of IAEA containment <strong>and</strong> surveillance equipment, <strong>and</strong> calling on it <strong>to</strong><br />

cooperate fully <strong>and</strong> urgently <strong>with</strong> the Agency. On February 12, 2003, the IAEA Board of<br />

Governors declared that the DPRK’s actions constituted “further noncompliance” <strong>with</strong> its<br />

safeguards obligations <strong>and</strong> called on the DPRK <strong>to</strong> remedy that noncompliance. Pursuant<br />

<strong>to</strong> this February 12 IAEA Board of Governors resolution, the Direc<strong>to</strong>r General<br />

transmitted a letter <strong>to</strong> the UN Security Council informing it about the DPRK’s<br />

noncompliance.<br />

In between these IAEA Board decisions, on January 10, 2003, North Korea<br />

announced that it had ended the suspension of its <strong>with</strong>drawal from the NPT, effective<br />

January 11, 2003, as previously described.<br />

The United States has publicly assessed that by the early 1990s, North Korea had<br />

sufficient plu<strong>to</strong>nium for one or possibly two nuclear weapons. Since that assessment,<br />

North Korea has engaged in further nuclear weapons activities, despite the Agreed<br />

Framework <strong>and</strong> the 1992 Joint Declaration.<br />

The North has publicly stated that the plu<strong>to</strong>nium recovered from reprocessing has<br />

been used in the direction of increasing its nuclear “deterrent” force, <strong>and</strong> that it will<br />

reprocess more spent fuel when necessary. The DPRK’s resumption of work at<br />

Yongbyon has permitted, or will permit, the construction of additional plu<strong>to</strong>nium<br />

weapons.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. North Korea<br />

continued <strong>to</strong> be bound by its NPT obligations, <strong>and</strong> its safeguards agreement <strong>with</strong> the<br />

IAEA, as long as North Korea remained a party <strong>to</strong> the NPT – that is, until its 2003 notice<br />

of <strong>with</strong>drawal became effective. The DPRK remained subject <strong>to</strong> its commitments in the<br />

Agreed Framework <strong>and</strong> the 1992 Joint Declaration until its repudiation of these<br />

agreements in admitting <strong>to</strong> its uranium enrichment program in 2002.<br />

NPT. The DPRK’s uranium enrichment program – which it admitted privately <strong>to</strong><br />

the United States during the reporting period, <strong>and</strong> thereafter publicly in early 2005 –<br />

violated the Joint North-South Declaration on the Denuclearization of the Korean<br />

Peninsula <strong>and</strong> the Agreed Framework. The DPRK was in violation of its safeguards<br />

90


agreement – <strong>and</strong> therefore NPT Article III – from at least 1993, when the IAEA Board of<br />

Governors found it in noncompliance <strong>with</strong> its safeguards agreement. Subsequent North<br />

Korean actions in 2002 <strong>and</strong> 2003 constituted further noncompliance. The DPRK’s<br />

actions in December 2002 in removing IAEA seals <strong>and</strong> cameras, <strong>and</strong> expelling<br />

inspec<strong>to</strong>rs, also constituted a violation of Article III – indeed, perhaps the most egregious<br />

<strong>and</strong> blatant violation of IAEA safeguards <strong>and</strong> of Article III in the Treaty’s his<strong>to</strong>ry. As the<br />

IAEA Direc<strong>to</strong>r-General has noted, North Korea “displayed complete disregard for its<br />

obligations under the Safeguards Agreement by cutting all seals <strong>and</strong> impeding the<br />

functioning of surveillance cameras that were in its nuclear facilities.” In fact, North<br />

Korea was in “chronic noncompliance” <strong>with</strong> its safeguards agreement <strong>and</strong> Article III of<br />

the NPT since 1993, <strong>and</strong> the IAEA remains unable <strong>to</strong> verify that there has been no<br />

diversion of nuclear materials. Indeed, the IAEA’s continual attempts <strong>to</strong> bring North<br />

Korea in<strong>to</strong> compliance <strong>with</strong> its Safeguard Agreement meet <strong>with</strong> little more than<br />

s<strong>to</strong>newalling.<br />

The obvious <strong>and</strong> admitted purpose of North Korea’s uranium enrichment program<br />

– the development of nuclear weapons – also makes it a violation of Article II of the<br />

NPT. North Korea’s work on plu<strong>to</strong>nium production for nuclear weapons, both before the<br />

Agreed Framework <strong>and</strong> thereafter, was also a violation of Article II. North Korea was<br />

thus guilty of multiple, <strong>and</strong> egregious, violations of the NPT at the time it <strong>with</strong>drew from<br />

the Treaty.<br />

The North Korean uranium enrichment program, <strong>and</strong> the DPRK’s possession of<br />

nuclear weapons, was also a violation of the DPRK’s commitments under the Agreed<br />

Framework <strong>and</strong> the Joint Declaration.<br />

The United States has made it clear that a key precondition for improved U.S.-<br />

DPRK relations is North Korea’s agreement <strong>to</strong> <strong>and</strong> implementation of complete,<br />

verifiable, <strong>and</strong> irreversible dismantlement of its nuclear program; one important element<br />

of such an outcome must be the DPRK’s prompt, verifiable, <strong>and</strong> full compliance <strong>with</strong> its<br />

obligations under the NPT as a non-nuclear weapons state <strong>and</strong> its IAEA safeguards<br />

agreement.<br />

The United States is working <strong>with</strong> South Korea, Japan, China, Russia, the EU,<br />

<strong>and</strong> a large number of other like-minded nations, <strong>to</strong> increase international pressure on <strong>and</strong><br />

isolation of North Korea until it agrees <strong>to</strong> the dismantlement of its nuclear program in a<br />

permanent, thorough <strong>and</strong> transparent manner, <strong>and</strong> subject <strong>to</strong> effective verification.<br />

Agreed Framework. The Agreed Framework created a process for resolving the<br />

North Korean nuclear issue, addressing international concerns about the DPRK’s nuclear<br />

intentions, <strong>and</strong> bringing it in<strong>to</strong> compliance <strong>with</strong> its NPT commitments. However, North<br />

Korea’s uranium program was inconsistent <strong>with</strong> paragraph 2 of Article III of the Agreed<br />

Framework, under which the DPRK was <strong>to</strong> consistently take steps <strong>to</strong> implement the 1992<br />

North-South Joint Declaration on the Denuclearization of the Korean Peninsula, which<br />

prohibited uranium enrichment facilities. As the IAEA Direc<strong>to</strong>r General has also noted,<br />

91


“[s]ince 1994, the DPRK has sought shelter behind the U.S.-DPRK Agreed Framework,<br />

claiming a legally untenable ‘unique status’ under the NPT <strong>to</strong> circumvent compliance<br />

<strong>with</strong> its nonproliferation obligations.”<br />

FINDING. Not<strong>with</strong>st<strong>and</strong>ing its 2003 notice of <strong>with</strong>drawal from the NPT, North<br />

Korea was obligated through much of the reporting period <strong>to</strong> comply <strong>with</strong> the Treaty <strong>and</strong><br />

<strong>with</strong> its NPT safeguards agreement. North Korea’s refusal <strong>to</strong> permit the IAEA <strong>to</strong> verify<br />

the completeness <strong>and</strong> correctness of its initial nuclear material declaration, as well as its<br />

continuing refusal <strong>to</strong> permit IAEA safeguards <strong>to</strong> be applied <strong>to</strong> its nuclear activities as<br />

required by its NPT Safeguards Agreement, constituted longst<strong>and</strong>ing <strong>and</strong> continuous<br />

violations of its safeguards agreement. The United States judges that North Korea was in<br />

noncompliance <strong>with</strong> its safeguards obligations since 1993. North Korean actions in 2002<br />

<strong>and</strong> 2003 constituted further violations of its safeguards obligations <strong>and</strong> its obligations<br />

under Article III of the NPT. (U)<br />

Based on the information available, including the DPRK’s own statements, North<br />

Korea possessed nuclear weapons, manufactured nuclear weapons, <strong>and</strong> has sought <strong>and</strong><br />

received assistance in this effort, all in violation of Article II of the NPT.<br />

North Korea also violated its political commitments <strong>to</strong> the United States under<br />

Article III of the Joint Declaration on the Denuclearization of the Korean Peninsula <strong>and</strong><br />

therefore paragraph 2 of Article III of the Agreed Framework by developing a cl<strong>and</strong>estine<br />

uranium enrichment program <strong>and</strong> by breaking the freeze on its plu<strong>to</strong>nium production<br />

facilities.<br />

F. THE TREATY ON OPEN SKIES<br />

The Treaty on Open Skies was signed at Helsinki on March 24, 1992, by 26<br />

States encompassing NATO <strong>and</strong> the Former Warsaw Pact: Belarus, Belgium, Bulgaria,<br />

Canada, former Czechoslovakia, Denmark, France, Georgia, Germany, Greece, Hungary,<br />

Icel<strong>and</strong>, Italy, Kyrgyzstan, Luxembourg, Netherl<strong>and</strong>s, Norway, Pol<strong>and</strong>, Portugal,<br />

Romania, Russia, Spain, Turkey, United Kingdom, Ukraine, <strong>and</strong> the United States. The<br />

United States <strong>and</strong> most other signa<strong>to</strong>ries had ratified the Open Skies Treaty by the end of<br />

1993. However, the Treaty did not enter in<strong>to</strong> force until January 1, 2002, following the<br />

requisite deposit of 20 instruments of ratification, including those of the Depositaries <strong>and</strong><br />

of States Parties <strong>with</strong> eight or more passive quotas. The Treaty on Open Skies is of<br />

unlimited duration.<br />

Kyrgyzstan is the only original signa<strong>to</strong>ry that has not yet ratified the Treaty. Prior<br />

<strong>to</strong> entry in<strong>to</strong> force (EIF), the Czechoslovak Socialist Federated Republic (CSFR), split<br />

in<strong>to</strong> two separate independent states, the Czech Republic <strong>and</strong> the Slovak Republic; both<br />

of these new states accepted the rights <strong>and</strong> obligations of the former CSFR <strong>and</strong> deposited<br />

instruments of ratification <strong>to</strong> the Treaty. Before EIF, the Treaty was opened for signature<br />

by the former Soviet republics. Any of these States that did not sign the Treaty prior <strong>to</strong><br />

EIF may accede <strong>to</strong> the Treaty at any time. The remaining members of the Organization<br />

92


for Security <strong>and</strong> Cooperation in Europe (OSCE) were able <strong>to</strong> apply for accession during<br />

the first six months after EIF. Six months after EIF, the Treaty opened <strong>to</strong> request for<br />

accession by any State that, in the judgment of the Open Skies Consultative Commission<br />

(OSCC), is able <strong>and</strong> willing <strong>to</strong> contribute <strong>to</strong> the objectives of the Treaty. By the end of<br />

2003, Bosnia <strong>and</strong> Herzegovina, Finl<strong>and</strong>, Latvia, <strong>and</strong> Sweden had become States Parties <strong>to</strong><br />

the Treaty, bringing the <strong>to</strong>tal number <strong>to</strong> 30 States Parties.<br />

The Treaty on Open Skies established a regime for the conduct of unarmed<br />

observation flights by States Parties over the terri<strong>to</strong>ries of other States Parties. The Treaty<br />

contains twelve Annexes, which are integral parts of the Treaty. The OSCC is the<br />

Treaty-established diplomatic organization comprised of representatives of all States.<br />

Due <strong>to</strong> the timing of the delivery of the final required instruments of ratification<br />

by Russia <strong>and</strong> Ukraine, the Treaty’s first quota year of implementation covered calendar<br />

years 2002 <strong>and</strong> 2003, meaning each State Party had two calendar years in which <strong>to</strong><br />

execute one Treaty year’s quota of observation missions. States Parties spent the first six<br />

months following EIF completing the certification of aircraft <strong>and</strong> sensors for use on<br />

observation missions, in accordance <strong>with</strong> Treaty provisions <strong>and</strong> OSCC Decisions.<br />

In August 2002, Russia conducted the first Open Skies observation mission over<br />

the terri<strong>to</strong>ry of the United Kingdom. By December 31, 2003, seventeen States Parties<br />

had executed 67 observation missions over the terri<strong>to</strong>ries of seventeen other States<br />

Parties. During 2002-2003 the United States planned <strong>and</strong> attempted <strong>to</strong> conduct nine<br />

missions as allocated at Treaty signature: eight over the Russia/Belarus Group of States<br />

Parties <strong>and</strong> one over Ukraine (a mission shared <strong>with</strong> Canada). Ultimately, however, the<br />

United States completed only eight: seven over Russia/Belarus <strong>and</strong> one over Ukraine.<br />

The United States employed its OC-135B aircraft for seven missions <strong>and</strong> a leased<br />

Ukrainian An-30 for the two remaining (one of which ultimately was cancelled due <strong>to</strong> a<br />

l<strong>and</strong>ing incident <strong>and</strong> adverse weather conditions at the Russian Point of Entry/Exit<br />

[POE]). (The cancelled mission is discussed in more detail below.) The United States<br />

requested copies of imagery collected during eight observation missions conducted by six<br />

other States Parties (Benelux, Canada, France, Germany, Norway <strong>and</strong> Turkey). Two<br />

States Parties (France <strong>and</strong> Germany) requested <strong>and</strong> received copies of portions the<br />

imagery collected during seven United States observation missions.<br />

As of December 31, 2003, no State Party had conducted an observation mission<br />

over the terri<strong>to</strong>ry of the United States. Russia conducted the first Open Skies mission<br />

over the United States in June 2004.<br />

Because Treaty EIF occurred in January 2002, this is the first time compliance<br />

<strong>with</strong> the treaty has been assessed in a Noncompliance Report. Because the Treaty is<br />

lengthy <strong>and</strong> contains portions that are technically detailed, there were several issues that<br />

arose during the first two years of Treaty operations. Issues that have initially raised<br />

compliance concerns are implementation-oriented, <strong>and</strong> can largely be attributed <strong>to</strong><br />

different interpretations <strong>and</strong> underst<strong>and</strong>ings of various Treaty provisions by the different<br />

93


States Parties as new (<strong>and</strong> often unanticipated) situations were encountered during the<br />

nascent stages of Treaty implementation. In all cases, the United States has quickly<br />

engaged other Parties, either bilaterally or in the OSCC, <strong>to</strong> address these concerns,<br />

preserve our Treaty rights, <strong>and</strong> ensure States Parties remain in compliance <strong>with</strong> the<br />

Treaty. We have been largely successful in this approach.<br />

The issue of altering maximum flight distances (MFD) remained under discussion<br />

in Vienna at the close of 2003. MFD is the maximum distance an Open Skies aircraft<br />

may fly over the terri<strong>to</strong>ry of the observed party from the airfield at which the observation<br />

flight commences. During the period of provisional application of the Treaty (the period<br />

between signature <strong>and</strong> EIF), many States Parties, including the United States, changed<br />

the airfields they originally designated at Treaty signature pursuant <strong>to</strong> Treaty provisions.<br />

However, Russia <strong>and</strong> Ukraine notified States Parties that, in addition <strong>to</strong> changing certain<br />

designated airfields, they were also reducing the MFDs associated <strong>with</strong> the originally<br />

designated airfields. Although there are Treaty provisions for changing airfields, there<br />

are no provisions for changing the associated MFDs.<br />

The United States <strong>and</strong> other States Parties objected <strong>to</strong> MFD changes made by<br />

Russia <strong>and</strong> Ukraine. Russia’s <strong>and</strong> Ukraine’s new MFDs reduced the amount of terri<strong>to</strong>ry<br />

available for observation during a mission <strong>and</strong> also increased the number of observation<br />

flights needed <strong>to</strong> cover the same amount of terri<strong>to</strong>ry than originally agreed at Treaty<br />

signature. Russia <strong>and</strong> Ukraine both provided interim solutions for their MFDs that<br />

allowed other States Parties <strong>to</strong> conduct missions while seeking a final solution <strong>to</strong> the<br />

overall issue. The United States is actively engaged in negotiating an OSCC Decision <strong>to</strong><br />

establish procedures for changing MFDs that preserve Treaty rights for observation. The<br />

OSCC adopted a Decision in March 2004 that resolved this issue, preserving Treaty<br />

rights <strong>and</strong> eliminating the compliance concern.<br />

COUNTRY ASSESSMENTS<br />

RUSSIA<br />

ISSUE. The issue is whether Russia’s failure <strong>to</strong> provide Treaty-required airfield<br />

<strong>and</strong> airspace information in a timely manner, delaying U.S Treaty missions over Russia<br />

was inconsistent <strong>with</strong> its obligations under the Open Skies Treaty.<br />

A second issue is whether Russia’s attempt <strong>to</strong> refuse a notified U.S. Treaty<br />

mission over Russia for which the United States held a valid quota was inconsistent <strong>with</strong><br />

its obligations under the Open Skies Treaty.<br />

HISTORY OF COMPLIANCE EVALUATION. This is the first time that<br />

Russian compliance <strong>with</strong> the Treaty on Open Skies has been assessed.<br />

DISCUSSION OF OBLIGATIONS. Annex I, an integral part of the Open Skies<br />

Treaty, has three key provisions <strong>to</strong> which States Parties must adhere in providing the<br />

94


necessary information on airspace operating procedures, including hazardous airspace.<br />

The first provision is that no later than 90 days after EIF, each State Party was required <strong>to</strong><br />

notify all other States Parties of the source of their airspace information. The second<br />

requires that no earlier than 90 days after EIF, at the request of any other State Party, a<br />

State Party must provide no later than 30 days after the receipt of such a request, airspace<br />

information in accordance <strong>with</strong> International Civil Aviation Organization (ICAO)<br />

provisions. Lastly, States Parties are required <strong>to</strong> notify other State Parties that have<br />

requested this information of any changes <strong>to</strong> the information provided. The second<br />

provision requires a State Party <strong>to</strong> provide information on: A) its airspace structure, as<br />

published in the Aeronautical Information Publication (AIP) series; B) detailed<br />

information on all hazardous airspace; <strong>and</strong> C) airfield information <strong>and</strong> arrival <strong>and</strong><br />

departure procedures for each of its POEs, Open Skies airfields, alternate airfields <strong>and</strong><br />

refueling airfields for its points of entry, points of exit, <strong>and</strong> Open Skies airfields. The<br />

United States interprets this <strong>to</strong> mean that the information provided must satisfy the<br />

information requirements contained in Annex 15 <strong>to</strong> the Convention on International Civil<br />

Aviation.<br />

Under the Open Skies Treaty, observing States Parties are required <strong>to</strong> announce<br />

their intent <strong>to</strong> conduct an observation mission no less than 72 hours prior <strong>to</strong> the estimated<br />

time of arrival of the mission at the point of entry. The observed State Party is required<br />

<strong>to</strong> acknowledge, <strong>with</strong>in 24 hours, receipt of the notice of intent <strong>to</strong> conduct an observation<br />

flight. There is no right <strong>to</strong> refuse an announced observation mission prior <strong>to</strong> its arrival<br />

for any reason. For no less than 24 hours after an observation mission arrives at the<br />

point, the sides will negotiate a mission plan <strong>and</strong> prepare <strong>to</strong> conduct the mission. If the<br />

observing State Party fails <strong>to</strong> arrive <strong>with</strong>in 24 hours of the estimated time of arrival the<br />

observed State Party may refuse the mission.<br />

ACTIONS. When the Open Skies Treaty was signed, the Republic of Belarus <strong>and</strong><br />

the Russian Federation group of State Parties identified four Open Skies airfields,<br />

including two POEs. By September 2002, this list had been modified <strong>to</strong> include 10 Open<br />

Skies airfields <strong>and</strong> 15 refueling airfields. In January 2003, Russia notified all States<br />

Parties that one POE would be deleted <strong>and</strong> replaced <strong>with</strong> another.<br />

Just prior <strong>to</strong> the April 1, 2002 deadline for providing the source of its Annex I<br />

information, Russia announced that it was reorganizing portions of its national airspace<br />

<strong>and</strong> that Treaty-required information <strong>and</strong> its source would not be available until a later<br />

date. In July <strong>and</strong> August 2002, the United States requested Annex I information from<br />

Russia through several channels. Information was provided by Russia in September<br />

2002, though it was not complete.<br />

In January 2003, the United States again approached Russia/Belarus seeking<br />

further information. In response, Russia/Belarus invited experts <strong>to</strong> Moscow <strong>to</strong> seek<br />

resolution of this issue. The United States accepted this offer <strong>and</strong> in June 2003 a<br />

delegation went <strong>to</strong> Moscow, clearly outlining what information would be needed <strong>to</strong><br />

95


satisfy Annex I requirements. During these discussions <strong>and</strong> throughout the remainder of<br />

the summer, Russia provided further detailed information on some of its airfields.<br />

During this period, the United States postponed two Open Skies missions it had<br />

planned over Russia, awaiting satisfac<strong>to</strong>ry resolution of Annex I requirements. By July<br />

2003, the United States had obtained sufficient information, <strong>and</strong> resumed missions over<br />

Russia/Belarus. By the end of 2003, there were two remaining refueling airfields for<br />

which the United States did not have information <strong>to</strong> satisfy the requirements of Annex I.<br />

In 2004 the United States obtained the remaining Treaty-required information <strong>and</strong><br />

additional requested information that allowed us <strong>to</strong> exercise our Treaty rights <strong>and</strong> operate<br />

<strong>with</strong>in U.S. safety st<strong>and</strong>ards.<br />

In July 2003, when the United States announced its intent <strong>to</strong> conduct its first<br />

mission since resuming operations over Russia/Belarus <strong>and</strong> the first in<strong>to</strong> Russia’s western<br />

POE (Klin), Russia refused <strong>to</strong> accept the mission as announced. Their stated reason for<br />

rejecting the mission was that they were not sure the U.S. OC-135 could safely operate at<br />

the announced airfield. This appeared <strong>to</strong> be a spurious objection, however, because the<br />

required aircraft information had been previously provided. Additionally, both sides had<br />

just made a breakthrough after nearly a year of negotiations obtaining airfield information<br />

<strong>to</strong> ensure the U.S. OC-135 could operate safely from Russia’s airfields. Unofficially, the<br />

Russians also objected that the announced mission would have extended in<strong>to</strong> the<br />

weekend. (This appears <strong>to</strong> have been the real motive, as it appears Russia was<br />

logistically unable <strong>to</strong> host the United States at the airbase over the weekend.) As noted,<br />

however, there is no right <strong>to</strong> refuse an announced observation mission for any reason.<br />

The United States delayed the announced mission, <strong>and</strong> formally objected <strong>to</strong> Russia’s<br />

actions at the OSCC. After a brief exchange of further information <strong>and</strong> diplomatic notes,<br />

flights resumed <strong>with</strong> the mutual underst<strong>and</strong>ing that, per the Treaty, missions can be<br />

conducted on any date or time, but that where possible, the sides would seek <strong>to</strong> avoid<br />

conducting missions over weekends <strong>and</strong> holidays.<br />

In December 2003, the last U.S. active mission over Russia/Belarus was<br />

scheduled using a leased Ukrainian aircraft. The aircraft ran off the end of the runway<br />

while arriving at the POE <strong>to</strong> begin the mission. No aircrew or ground personnel were<br />

injured <strong>and</strong> no damage occurred <strong>to</strong> the aircraft or runway. The U.S. inspec<strong>to</strong>rs <strong>and</strong><br />

Ukrainian flight crew were prepared <strong>to</strong> continue <strong>with</strong> the announced mission the next<br />

day. After the incident, the Russians agreed <strong>to</strong> the observation flight plan proposed by<br />

the U.S. team. At the same time, the Russians insisted on their right <strong>to</strong> conduct an<br />

incident investigation as provided by Article VIII of the Treaty. Despite having grounded<br />

the aircraft <strong>to</strong> conduct the investigation, Russia argued that because a flight plan had been<br />

agreed <strong>to</strong> by both parties, the 96-hour rule for conducting the observation mission was<br />

applicable <strong>to</strong> the mission. The Russians concluded their investigation just in time for the<br />

aircraft <strong>to</strong> depart the POE near the end of that period. The United States argued that the<br />

96-hour period should have been suspended while the investigation was ongoing.<br />

Unfortunately, adverse weather made it impractical for the U.S. team <strong>to</strong> press this Treaty<br />

point by submitting a flight plan that extended beyond the original 96-hour period. In<br />

96


2004, the United States formally objected <strong>to</strong> Russia’s actions during the event at the<br />

OSCC.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. The U.S.-Russian<br />

dialogue on required airfield data has been a long, complex, <strong>and</strong> iterative one. Each time<br />

we have asked for information, the Russians have provided only some of that<br />

information, <strong>and</strong> sometimes not in the most useable format. Our response has always<br />

been further <strong>to</strong> refine <strong>and</strong> clarify our request, <strong>to</strong> which the Russians have eventually<br />

presented the required information. In some cases, the United States has requested<br />

additional information beyond the ICAO requirements. Some of this information was<br />

provided when it was available. The trip <strong>to</strong> Moscow in June 2003 was successful in<br />

encouraging more useful information <strong>and</strong> seemed <strong>to</strong> be the tipping point, when their<br />

experts <strong>and</strong> ours were able <strong>to</strong> communicate face-<strong>to</strong>-face, <strong>and</strong> Russia now appears <strong>to</strong><br />

underst<strong>and</strong> the requirements as we do <strong>and</strong> now does provide Treaty-required information<br />

when we request it (albeit not as rapidly as we would prefer). The United States is still<br />

awaiting some information.<br />

The Russian refusal <strong>to</strong> accept the U.S. mission as announced at Klin airbase<br />

appears <strong>to</strong> have been driven by their inability <strong>to</strong> put <strong>to</strong>gether the logistics of hosting our<br />

aircraft <strong>and</strong> inspection team at Klin over the weekend upon 72 hours notice. When the<br />

United States formally raised the issue in Vienna, the issue of flying over the weekend<br />

quickly became the focus of Russia’s argument. U.S. insistence that there was no right of<br />

refusal under the Treaty held the day however, <strong>and</strong>, thereafter, no violation of this type<br />

occurred. As part of the discussion, an agreement was reached whereby, if possible, the<br />

sides would seek <strong>to</strong> avoid conducting missions over weekends <strong>and</strong> holidays. However,<br />

the United States has made clear that it reserves the right <strong>to</strong> fly missions on weekends <strong>and</strong><br />

holidays when it sees fit. No State Party has yet tested this principle, however.<br />

FINDING. Although the Republic of Belarus <strong>and</strong> the Russian Federation group<br />

of States Parties have taken steps <strong>to</strong> resolve the issue, the airspace <strong>and</strong> airfield<br />

information provided <strong>to</strong> date has not satisfied the requirements of Annex I of the Open<br />

Skies Treaty.<br />

UKRAINE<br />

ISSUE. The issue is whether Ukraine’s attempt <strong>to</strong> prohibit observation of a<br />

portion of its terri<strong>to</strong>ry, claiming that the proposed Open Skies mission would occur<br />

<strong>with</strong>in hazardous airspace, was inconsistent <strong>with</strong> its obligations under the Open Skies<br />

Treaty.<br />

HISTORY OF COMPLIANCE EVALUATION. This is the first time that<br />

Ukrainian compliance <strong>with</strong> the Treaty on Open Skies has been assessed.<br />

DISCUSSION OF OBLIGATIONS. The Treaty on Open Skies provides an<br />

observing State Party <strong>with</strong> the right <strong>to</strong> observe any point on the entire terri<strong>to</strong>ry of the<br />

97


observed State Party, including areas designated as hazardous. It further obligates States<br />

Parties <strong>to</strong> give observation missions priority over any regular air traffic.<br />

ACTIONS. The United States <strong>and</strong> Canada conducted their shared active quota<br />

mission over the terri<strong>to</strong>ry of Ukraine in November 2003. When the joint team presented<br />

their mission plan, however, the Ukrainian representatives stated that part of the planned<br />

mission route was <strong>with</strong>in a hazardous area <strong>and</strong> therefore the mission could not overfly<br />

that area. As the maximum allowed period for negotiating a flight plan approached,<br />

Ukrainian representatives relented, allowing for a “one-time” overflight of the area, but<br />

said that they did not consider this waiver as setting a precedent for future overflights.<br />

The Ukrainian representative stated that Ukraine considered that there should be no<br />

difference in the h<strong>and</strong>ling of Open Skies missions <strong>and</strong> commercial flights <strong>with</strong> respect <strong>to</strong><br />

hazardous areas.<br />

The United States approached the Ukrainians at the OSCC <strong>to</strong> clarify the<br />

Ukrainian position. The Ukrainian representative at the OSCC reiterated the statement<br />

made by the Ukrainian representative during the flight plan negotiations as representing<br />

the Ukrainian position, but promised <strong>to</strong> take the issue back <strong>to</strong> Kiev for review. In 2004,<br />

following bilateral U.S. diplomatic action at the OSCC, Ukraine has adopted the U.S.<br />

underst<strong>and</strong>ing of this Treaty point. Subsequent missions over the Ukraine have been free<br />

of controversy.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. During the mission<br />

plan negotiation, the U.S. team was insistent on the United States’ right <strong>to</strong> observe any<br />

point of terri<strong>to</strong>ry pursuant <strong>to</strong> the Treaty. This mission was one of the first Open Skies<br />

missions over Ukraine, <strong>and</strong> it soon became clear the problem was the lack of a complete<br />

underst<strong>and</strong>ing of the treaty provisions (from an implementation perspective) <strong>with</strong> respect<br />

<strong>to</strong> the special air-traffic control h<strong>and</strong>ling required for Open Skies missions. As the timeperiod<br />

for negotiating the mission plan neared expiration, the U.S./Canadian team refused<br />

<strong>to</strong> yield on the point of this Treaty right. Ukraine partially relented, allowing the<br />

abovementioned “one-time” overflight <strong>and</strong> giving Ukraine the time <strong>to</strong> re-examine the<br />

issue.<br />

The U.S.-Ukrainian dialogue in these regards has been cordial, <strong>with</strong> Ukrainian<br />

representatives expressing a desire <strong>to</strong> fully underst<strong>and</strong> the issue <strong>and</strong> resolve it. We<br />

expect resolution of the issue, consistent <strong>with</strong> the U.S. interpretation of the Treaty.<br />

FINDING. Ukraine would not have been in compliance <strong>with</strong> Article VI of the<br />

Open Skies Treaty had Ukraine not permitted the “one-time” overflight or had it persisted<br />

<strong>with</strong> its refusal <strong>to</strong> allow the observation of any point on its terri<strong>to</strong>ry by subjecting Open<br />

Skies observation missions <strong>to</strong> commercial air traffic restrictions. However, because the<br />

issue was successfully resolved, the United States judges that Ukraine did not fail <strong>to</strong><br />

comply <strong>with</strong> its Open Skies Treaty obligations.<br />

98


VII. COMPLIANCE OF OTHER NATIONS (INCLUDING<br />

SUCCESSORS TO THE SOVIET UNION) WITH THEIR<br />

INTERNATIONAL COMMITMENTS<br />

A. MISSILE NONPROLIFERATION COMMITMENTS<br />

The United States employs a range of <strong>to</strong>ols <strong>to</strong> impede the proliferation of missile<br />

systems capable of delivering weapons of mass destruction (WMD). Multilateral<br />

nonproliferation regimes <strong>and</strong> bilateral diplomacy are among the primary <strong>to</strong>ols used <strong>to</strong><br />

dissuade supplier states from assisting the missile programs of proliferant states <strong>and</strong> <strong>to</strong><br />

induce proliferant states <strong>to</strong> end their missile programs. The Missile Technology <strong>Control</strong><br />

Regime (MTCR) <strong>and</strong> the Hague Code of Conduct against Ballistic Missile Proliferation<br />

(HCOC), also known as the International Code of Conduct (ICOC), are the main<br />

multilateral mechanisms that address the proliferation of missiles <strong>and</strong> missile-related<br />

technology. The United States also uses every opportunity <strong>to</strong> hold bilateral discussions<br />

<strong>with</strong> other countries on nonproliferation, <strong>with</strong> a particular focus on those that are not<br />

members of multilateral regimes. In several instances, the United States has sought <strong>and</strong><br />

received separate political nonproliferation commitments from nations like China <strong>to</strong> limit<br />

their missile proliferation activities or <strong>to</strong> implement controls on their missiles <strong>and</strong> related<br />

technologies. The United States expects these countries <strong>to</strong> fulfill their commitments.<br />

Some nations that are significant prolifera<strong>to</strong>rs of ballistic missile technology, such<br />

as North Korea <strong>and</strong> increasingly Iran, are not members of the MTCR or HCOC <strong>and</strong> have<br />

not made separate political nonproliferation commitments <strong>to</strong> the United States <strong>to</strong> halt<br />

their proliferation activities. Through our participation in multilateral regimes <strong>and</strong> in<br />

bilateral discussions <strong>with</strong> our allies <strong>and</strong> other like-minded states, the United States has<br />

attempted <strong>with</strong> little success <strong>to</strong> dissuade these states from their missile-proliferation<br />

activities. In response <strong>to</strong> continuing proliferation activities, in 2002 the United States<br />

imposed sanctions for missile-related transfers on entities in North Korea <strong>and</strong> Moldova<br />

for their missile-related transfers. In 2003, the United States imposed sanctions for<br />

missile-related transfers on entities in China, Iran, North Korea, Moldova <strong>and</strong><br />

Macedonia. In addition, missile proliferation sanctions were waived against an Yemeni<br />

entity in August 2002 for national security reasons.<br />

This Annex discusses the compliance of other nations <strong>with</strong> their Missile<br />

Technology <strong>Control</strong> Regime commitments <strong>and</strong> the compliance of other nations <strong>with</strong><br />

separate political nonproliferation commitments they have made <strong>to</strong> the United States.<br />

MISSILE TECHNOLOGY CONTROL REGIME. The Missile Technology<br />

<strong>Control</strong> Regime, created in 1987, is the centerpiece of international efforts <strong>to</strong> curb the<br />

spread of missiles capable of delivering weapons of mass destruction.<br />

The MTCR is not a treaty, but a voluntary arrangement among member countries<br />

sharing a common interest in controlling missile proliferation. While the MTCR does not<br />

impose any legally binding obligations on participating countries, the Regime rests on<br />

99


adherence <strong>to</strong> common export policy guidelines (the MTCR Guidelines) applied <strong>to</strong> an<br />

integral common list of controlled items (the MTCR Equipment, Software <strong>and</strong><br />

Technology Annex). The Guidelines <strong>and</strong> Annex are implemented according <strong>to</strong> each<br />

country’s national legislation <strong>and</strong> regulations.<br />

The Regime implements the missile controls in two categories. Category I items<br />

are complete rocket systems (including ballistic missile systems, space launch vehicles,<br />

<strong>and</strong> sounding rockets) <strong>and</strong> unmanned air vehicles (including cruise missile systems,<br />

target drones <strong>and</strong> reconnaissance drones) capable of delivering at least a 500 kg payload<br />

<strong>to</strong> a range of at least 300 km, the major subsystems that could be used on these systems,<br />

<strong>and</strong> their production facilities. Category II items are other less sensitive <strong>and</strong> dual-use<br />

missile-related components that could be used <strong>to</strong> develop a Category I system, <strong>and</strong><br />

complete missiles <strong>and</strong> major subsystems of missiles capable of delivering a payload of<br />

any size <strong>to</strong> a range of 300 km.<br />

Specifically, the MTCR Partners undertake the following commitments:<br />

A. General Restraint <strong>and</strong> Case-by-Case Consideration. The MTCR Guidelines<br />

provide that “restraint will be exercised in the consideration of all transfers of items<br />

<strong>with</strong>in the Annex <strong>and</strong> all such transfers will be considered on a case-by-case basis.” In<br />

evaluating transfer applications for Annex items, Governments undertake <strong>to</strong> take in<strong>to</strong><br />

account the following fac<strong>to</strong>rs: (a) concerns about the proliferation of weapons of mass<br />

destruction; (b) the capabilities <strong>and</strong> objectives of the missile <strong>and</strong> space programs of the<br />

recipient state; (c) the significance of the transfer in terms of the potential development of<br />

delivery systems (other than manned aircraft) for weapons of mass destruction; (d) the<br />

assessment of the end-use of the transfers, including the relevant assurances of the<br />

recipient states regarding end use, replication, <strong>and</strong> retransfer; (e) the applicability of<br />

relevant multilateral agreements; <strong>and</strong>, since May 15, 2003, (f) the risk of controlled items<br />

falling in<strong>to</strong> the h<strong>and</strong>s of terrorist groups <strong>and</strong> individuals. (U)<br />

B. No Transfer of Category I Production Facilities. The MTCR Guidelines<br />

contain a commitment specifying that “the transfer of Category I production facilities will<br />

not be authorized.” The MTCR defines production facilities as “equipment <strong>and</strong> specially<br />

designed ‘software’ therefore integrated in<strong>to</strong> installations for ‘development’ or for one or<br />

more phases of ‘production.’”<br />

C. Category I Transfer Requests: Strong Presumption of Denial. Pursuant <strong>to</strong> the<br />

MTCR Guidelines, “particular restraint will be exercised in the consideration of Category<br />

I transfers, regardless of their purpose, <strong>and</strong> there will be a strong presumption <strong>to</strong> deny<br />

such transfers.” The Guidelines further provide that the transfer of Category I items “will<br />

be authorized only on rare occasions <strong>and</strong> where the Government (a) obtains binding<br />

government-<strong>to</strong>-government undertakings embodying the assurances from the recipient<br />

government called for in paragraph 5 [regarding end-use, replication <strong>and</strong> retransfer] <strong>and</strong><br />

(b) assumes responsibility for taking all steps necessary <strong>to</strong> ensure that the item is put only<br />

<strong>to</strong> its stated end-use.”<br />

100


D. Category II Transfer Requests. Category II transfers are subject <strong>to</strong> “restraint”<br />

<strong>and</strong> “case-by-case” consideration, taking in<strong>to</strong> account the required fac<strong>to</strong>rs, as described in<br />

A above. In addition, “particular restraint will also be exercised in the consideration of<br />

transfers of any items in the Annex, or of any missiles (whether or not in the Annex), if<br />

the Government judges, on the basis of all available, persuasive information, evaluated<br />

according <strong>to</strong> fac<strong>to</strong>rs including those in paragraph 3 [see A above], that they are intended<br />

<strong>to</strong> be used for the delivery of weapons of mass destruction, <strong>and</strong> there will be a strong<br />

presumption <strong>to</strong> deny such transfers.”<br />

E. Transfers of Design <strong>and</strong> Production Technology. The Guidelines provide that<br />

“the transfer of design <strong>and</strong> production technology directly associated <strong>with</strong> any items in<br />

the Annex will be subject <strong>to</strong> as great a degree of scrutiny <strong>and</strong> control as will the<br />

equipment itself, <strong>to</strong> the extent permitted by national legislation.”<br />

These MTCR export controls are not bans, but regula<strong>to</strong>ry efforts by individual<br />

Partners <strong>to</strong> prevent transfers of items that could contribute <strong>to</strong> delivery systems for WMD.<br />

<strong>Control</strong>ling such exports through licensing is consistent <strong>with</strong> the MTCR’s objective of<br />

curbing the flow of missile equipment <strong>and</strong> technology worldwide. It also helps suppliers<br />

have confidence that they can provide access <strong>to</strong> sensitive items <strong>with</strong>out fear of these<br />

items being diverted <strong>to</strong> programs of concern.<br />

The MTCR Partners do not make export licensing decisions as a group. Rather,<br />

each individual Partner implements the MTCR Guidelines <strong>and</strong> Annex in accordance <strong>with</strong><br />

national legislation <strong>and</strong> practice <strong>and</strong> the Guidelines specify that “the decision <strong>to</strong> transfer<br />

remains the sole <strong>and</strong> sovereign judgment of the Government.” In addition, there are no<br />

provisions in the Regime <strong>to</strong> review the individual licensing decisions by Partner nations<br />

for conformity <strong>with</strong> the Guidelines, <strong>and</strong> there are no inherent penalties if some members<br />

believe another member has made a “wrong” decision. Instead, Partners regularly<br />

exchange information on relevant licensing matters in order <strong>to</strong> ensure consistency <strong>with</strong><br />

the Regime’s overall nonproliferation objectives, <strong>and</strong> when questions arise, concerned<br />

Partners consult bilaterally <strong>to</strong> promote a common underst<strong>and</strong>ing of the issue <strong>and</strong> a<br />

consistent approach <strong>to</strong> the Regime’s overarching nonproliferation objectives.<br />

Over the course of the MTCR’s his<strong>to</strong>ry, the Regime has made some important<br />

strides in slowing missile proliferation worldwide. The MTCR Partners’ efforts have:<br />

induced most major suppliers <strong>to</strong> control their missile-related exports responsibly, reduced<br />

the number of countries <strong>with</strong> MTCR-class missile programs, <strong>and</strong> added countries <strong>with</strong><br />

significant economic <strong>and</strong> political potential <strong>to</strong> the MTCR <strong>to</strong> increase its influence <strong>and</strong><br />

capabilities. The MTCR Partners also have cooperated <strong>to</strong> halt numerous shipments of<br />

proliferation concern <strong>and</strong> have established the MTCR Guidelines <strong>and</strong> Annex as the<br />

international st<strong>and</strong>ard for responsible missile-related export behavior. In addition, they<br />

have established a broad outreach program <strong>to</strong> non-members, in order <strong>to</strong> increase<br />

awareness of the global missile proliferation threat <strong>and</strong> <strong>to</strong> urge countries that have<br />

engaged in missile proliferation <strong>to</strong> desist. In recent years, the MTCR Partners also have<br />

101


focused increasingly on new ideas for addressing ongoing global missile proliferation<br />

challenges <strong>and</strong> the dem<strong>and</strong>-side issues posed by non-MTCR members.<br />

Membership in the MTCR has grown steadily since the Regime’s creation in<br />

1987. In 2001, the Republic of Korea joined the Regime, bringing the <strong>to</strong>tal number of<br />

MTCR Partners by the end of the reporting period <strong>to</strong> 33: Argentina, Australia, Austria,<br />

Belgium, Brazil, Canada, the Czech Republic, Denmark, Finl<strong>and</strong>, France, Germany,<br />

Greece, Hungary, Icel<strong>and</strong>, Irel<strong>and</strong>, Italy, Japan, the Republic of Korea, Luxembourg, the<br />

Netherl<strong>and</strong>s, New Zeal<strong>and</strong>, Norway, Pol<strong>and</strong>, Portugal, Russia, South Africa, Spain,<br />

Sweden, Switzerl<strong>and</strong>, Turkey, Ukraine, the United Kingdom, <strong>and</strong> the United States.<br />

The MTCR Guidelines <strong>and</strong> Annex are open <strong>to</strong> all nations <strong>to</strong> implement<br />

unilaterally, <strong>and</strong> the United States <strong>and</strong> its MTCR partners encourage all governments <strong>to</strong><br />

do so. Several countries have declared unilateral adherence <strong>to</strong> the MTCR Guidelines <strong>and</strong><br />

have implemented export controls consistent <strong>with</strong> the MTCR Guidelines <strong>and</strong> Annex.<br />

These states include Bulgaria, Israel, Romania, <strong>and</strong> the Slovak Republic. China has<br />

committed <strong>to</strong> the original 1987 Guidelines of the MTCR but not the Annex. The United<br />

States <strong>and</strong> several other MTCR Partner countries maintain an active nonproliferation<br />

dialogue <strong>with</strong> these countries. However, these countries do not participate as Partners in<br />

the Regime, e.g., they do not participate in the decision-making process regarding the<br />

activities <strong>and</strong> future orientation of the MTCR.<br />

HAGUE CODE OF CONDUCT AGAINST BALLISTIC MISSILE<br />

PROLIFERATION. On November 25, 2002, the International Code of Conduct<br />

(ICOC) was launched in The Hague, Netherl<strong>and</strong>s. Now known as the Hague Code of<br />

Conduct (HCOC), it is intended <strong>to</strong> create a widely subscribed international predisposition<br />

against ballistic missile proliferation. It consists of a set of broad principles, general<br />

commitments, <strong>and</strong> modest confidence-building measures. It is a voluntary political<br />

commitment, not a treaty, <strong>and</strong> is open for subscription by all countries. The Code is<br />

intended <strong>to</strong> supplement, not supplant, the Missile Technology <strong>Control</strong> Regime.<br />

States subscribing <strong>to</strong> the HCOC “resolve <strong>to</strong> implement” the following General<br />

Measures: (a) ratify, accede or otherwise abide by three space-related international<br />

agreements — the Outer Space Treaty; the Convention on International Liability for<br />

Damage Caused by Space Objects; <strong>and</strong> the Convention on Registration of Objects<br />

Launched in<strong>to</strong> Outer Space; (b) “curb <strong>and</strong> prevent the proliferation” of WMD-capable<br />

ballistic missiles; (c) “exercise maximum possible restraint” in the development, testing,<br />

<strong>and</strong> deployment of WMD-capable ballistic missiles; (d) “exercise the necessary vigilance<br />

in the consideration of assistance <strong>to</strong> space launch vehicle programs in any other country”<br />

so as <strong>to</strong> prevent contributing <strong>to</strong> WMD-capable delivery systems <strong>and</strong> (e) “not <strong>to</strong> contribute<br />

<strong>to</strong>, support or assist any Ballistic Missile program in countries which might be developing<br />

or acquiring weapons of mass destruction in contravention of norms established by, <strong>and</strong><br />

of those countries’ obligations under, international disarmament <strong>and</strong> nonproliferation<br />

treaties.”<br />

102


In addition, the HCOC subscribing states “resolve <strong>to</strong> implement” the following<br />

transparency measures: (1) annual declarations outlining the nation’s ballistic missile<br />

policies <strong>and</strong> information on the numbers <strong>and</strong> generic class of ballistic missiles launched<br />

during the preceding year as declared under the HCOC’s pre-launch notification<br />

mechanism; (2) annual declarations outlining the nation’s space launch vehicle policies<br />

<strong>and</strong> information on the number <strong>and</strong> generic class of space launch vehicles launched<br />

during the preceding year as declared under the HCOC’s pre-launch notification<br />

mechanism; <strong>and</strong> (3) exchanges of pre-launch notifications on their ballistic missile <strong>and</strong><br />

space launch vehicle launches <strong>and</strong> test flights.<br />

As of December 2003, 111 states had subscribed <strong>to</strong> the ICOC including Russia<br />

<strong>and</strong> Libya. Other states, including China, North Korea, India, Pakistan, Yemen <strong>and</strong> Iran<br />

have not subscribed. Iraq was not originally invited <strong>to</strong> subscribe, but would be able <strong>to</strong><br />

subscribe if it chose <strong>to</strong> do so.<br />

CHINESE NONPROLIFERATION COMMITMENTS. Intensive bilateral<br />

dialogue <strong>and</strong> high-level political efforts augmented by trade sanctions imposed in 1991-<br />

92, 1993-94, <strong>and</strong> since September 2001 have resulted in a variety of Chinese missile<br />

nonproliferation commitments.<br />

China is not an MTCR partner. However, as described below, it has committed<br />

over the course of a number of years <strong>to</strong> abide by various missile nonproliferation<br />

commitments.<br />

Noncompliance concerns emerged soon after China issued its first missile<br />

nonproliferation commitment in March 1992. Previously in June 1991, the United States<br />

imposed sanctions on two Chinese entities-- China Great Wall Industry Corporation<br />

(CGWIC) <strong>and</strong> the China Precision Machinery Import/Export Corporation (CPMIEC)-- in<br />

connection <strong>with</strong> the sale of M-11 missile-related equipment <strong>to</strong> Pakistan. In return for<br />

ending sanctions on these two entities, China provided a written commitment in March<br />

1992 <strong>to</strong> then Secretary of State James Baker that it would abide by the original<br />

“guidelines <strong>and</strong> parameters” of the MTCR, which the United States publicly stated were<br />

applicable <strong>to</strong> both the M-9 (CSS-6) <strong>and</strong> M-11 (CSS-7) missiles. After issuing this<br />

commitment, Chinese entities transferred M-11 missiles <strong>to</strong> Pakistan. In response <strong>to</strong> U.S.<br />

complaints, China indicated that the M-11 missile was not covered by the MTCR <strong>and</strong> that<br />

it was fully complying <strong>with</strong> its 1992 pledge. In 1993, the United States imposed<br />

Category II sanctions on the Chinese Ministry of Aerospace Industry <strong>and</strong> the Pakistani<br />

Ministry of Defense for their roles in the transfer. Some of the divisions of the Ministry<br />

of Aerospace Industry that were affected by the sanctions included: the China Precision<br />

Machinery Import-Export Corporation (CPMIEC), China Great Wall Industrial<br />

Corporation (CGWIC), China Aerospace Corporation (CASC), <strong>and</strong> the Chinese<br />

Academy of Space Technology (CAST).<br />

In return for the lifting of the sanctions imposed in 1993, China pledged in<br />

Oc<strong>to</strong>ber 1994 in a Joint Statement <strong>with</strong> the United States that it would not transfer<br />

103


ground-<strong>to</strong>-ground missiles “inherently capable of reaching a range of at least 300 km<br />

<strong>with</strong> a payload of at least 500 kilograms.” In the years following this commitment,<br />

Chinese entities continued <strong>to</strong> provide missile-related items <strong>and</strong> assistance <strong>to</strong> countries,<br />

including Iran <strong>and</strong> Pakistan. China declared in Oc<strong>to</strong>ber 1996 that its previous<br />

commitments did not cover items contained on the MTCR Annex. However, following<br />

additional negotiations, in June 1998, China in a Joint Statement reaffirmed that its policy<br />

was “<strong>to</strong> prevent the export of equipment, materials, or technology that could in any way<br />

assist programs in India or Pakistan, for nuclear weapons or for ballistic missiles capable<br />

of delivering such weapons.” Nevertheless, despite these Chinese assurances, the United<br />

States continued <strong>to</strong> detect evidence of Chinese missile-related transfers.<br />

In return for the waiving of sanctions on several companies, China in November<br />

2000 issued a stronger commitment <strong>to</strong> missile nonproliferation, stating it would not assist<br />

“in any way, any country in the development of ballistic missiles that can be used <strong>to</strong><br />

deliver nuclear weapons (i.e., missiles capable of delivering a payload of at least 500<br />

kilograms <strong>to</strong> a distance of at least 300 kilometers).” The Chinese, however, continued <strong>to</strong><br />

make no mention of preventing or restricting the proliferation of Category II missiles in<br />

their commitment. In addition, China agreed <strong>to</strong> enact <strong>and</strong> publish comprehensive<br />

missile-related export controls “at an early date.” China’s unilateral political<br />

commitment <strong>and</strong> the related discussions <strong>with</strong> the United States have been referred <strong>to</strong> as<br />

“the November 2000 Arrangement.”<br />

Since China’s first commitment in March 1992 <strong>and</strong> until these negotiations<br />

s<strong>to</strong>pped in November 2000, these successive cycles of bilateral compliance diplomacy<br />

have fallen in<strong>to</strong> a common pattern. When U.S. intelligence detects evidence of missilerelated<br />

transfers by Chinese entities <strong>to</strong> proliferant countries, China first either denies such<br />

transfers occurred or asserts that the transfers in question did not violate its commitments<br />

<strong>to</strong> the United States. Then, after protracted bilateral consultations, China issues another<br />

nonproliferation pledge <strong>and</strong> the United States waives sanctions, only <strong>to</strong> begin the cycle<br />

again.<br />

Despite the November 2000 Arrangement, the United States continues <strong>to</strong> have<br />

similar concerns about Chinese compliance <strong>with</strong> <strong>and</strong> implementation of its missile<br />

nonproliferation commitments. Transfers that assist in the development of Category I<br />

missile programs in Iran <strong>and</strong> Pakistan continue. The continued proliferation of missilerelated<br />

technology led the United States <strong>to</strong> impose sanctions in September 2001 on the<br />

China Metallurgical Equipment Corporation (CMEC/MECC). Since then, <strong>and</strong> as detailed<br />

in this report, numerous Chinese entities have continued <strong>to</strong> provide missile-related<br />

technology <strong>to</strong> nuclear-capable Category I ballistic missile programs.<br />

In addition, China has interpreted <strong>and</strong> implemented its November 2000 political<br />

commitments in ways that have fallen short of establishing an effective missile<br />

nonproliferation system.<br />

104


OTHER NONPROLIFERATION COMMITMENTS. As part of its bilateral<br />

diplomatic consultations, the United States has sought nonproliferation commitments<br />

from both missile technology supplier states <strong>and</strong> recipient nations that are not members<br />

of the MTCR or the HCOC. Some countries have agreed <strong>to</strong> support common<br />

nonproliferation objectives by making a commitment <strong>to</strong> the United States not <strong>to</strong> acquire<br />

WMD-capable delivery systems for their military.<br />

COUNTRY ASSESSMENTS<br />

CHINA<br />

ISSUE. Proliferation of missile-related technology by Chinese entities continues<br />

<strong>and</strong> calls in<strong>to</strong> question China’s stated commitment <strong>to</strong> controlling missile proliferation.<br />

HISTORY OF ADHERENCE EVALUATION. Chinese compliance <strong>with</strong> its<br />

missile nonproliferation commitments was first assessed in the June 2003 (CY2001)<br />

NCR. In that Report, the United States concluded that:<br />

[China’s] actions call in<strong>to</strong> serious question China’s stated commitment <strong>to</strong><br />

controlling missile proliferation. Chinese state-owned corporations have<br />

engaged in transfer activities <strong>with</strong> Pakistan, Iran, North Korea, <strong>and</strong> Libya<br />

that are clearly contrary <strong>to</strong> China’s commitments <strong>to</strong> the United States.<br />

COMMITMENTS UNDERTAKEN. In return for the waiving of a number of<br />

sanctions required by U.S. law for past serious transfers by Chinese entities <strong>to</strong> the Iranian<br />

<strong>and</strong> Pakistani missile programs, including the transfer of a missile production facility <strong>to</strong><br />

Pakistan, China in November 2000 issued a stronger commitment <strong>to</strong> missile<br />

nonproliferation stating it would not assist “in any way, any country in the development<br />

of ballistic missiles that can be used <strong>to</strong> deliver nuclear weapons (i.e., missiles capable of<br />

delivering a payload of at least 500 kilograms <strong>to</strong> a distance of at least 300 kilometers).”<br />

In addition, China agreed <strong>to</strong> enact <strong>and</strong> publish comprehensive missile-related export<br />

controls “at an early date.” China’s unilateral political commitment <strong>and</strong> the related<br />

discussions <strong>with</strong> the United States have been referred <strong>to</strong> as “the November 2000<br />

Arrangement.”<br />

ACTIONS. Despite China’s November 2000 Arrangement <strong>and</strong> the promulgation<br />

of export control regulations, China’s proliferation of missile-related technology<br />

continues <strong>and</strong> calls in<strong>to</strong> question China’s stated commitment <strong>to</strong> controlling missile<br />

proliferation. These missile-related transfers continued in 2002 <strong>and</strong> 2003 <strong>to</strong> ballistic<br />

missile programs in Iran, Iraq, Libya, Pakistan, <strong>and</strong> North Korea. The United States has<br />

sanctioned several of the companies transferring these technologies.<br />

Chinese entities continued <strong>to</strong> transfer missile-related goods <strong>and</strong> technical<br />

knowledge <strong>to</strong> countries such as Pakistan, Iran, Libya, <strong>and</strong> North Korea. These transfers<br />

continue <strong>to</strong> contribute the development of MTCR Category I ballistic missiles in these<br />

105


countries. In addition, Chinese entities provided dual-use missile-related items, raw<br />

materials, <strong>and</strong> assistance <strong>to</strong> Iran, Libya, <strong>and</strong> North Korea.<br />

China’s implementation <strong>and</strong> enforcement of the missile export control regulations<br />

remain problematic. The Chinese Government has not established a system of end-use<br />

verification checks <strong>to</strong> ensure that items approved for transfer are not diverted. China<br />

must also ensure that “catch-all” controls are effectively implemented <strong>with</strong>in China.<br />

Finally, China needs clearly <strong>to</strong> signal <strong>to</strong> all Chinese entities that it intends vigorously <strong>to</strong><br />

enforce its export controls. Beijing has also not taken adequate steps under these new<br />

regulations <strong>to</strong> prevent sensitive transfers or prosecute violations, <strong>and</strong> China needs <strong>to</strong><br />

publicize its efforts <strong>to</strong> enforce its export control regulations.<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. Despite its<br />

November 2000 pledge, Chinese companies in 2002 <strong>and</strong> 2003 continued <strong>to</strong> supply<br />

technology <strong>and</strong> assistance <strong>to</strong> missile programs in various countries; this technology <strong>and</strong><br />

assistance was of direct use <strong>to</strong> these programs. The United States has gone <strong>to</strong><br />

considerable lengths <strong>to</strong> inform the Chinese Government about the proliferation activities<br />

of these entities. However, despite these efforts, the Chinese Government almost<br />

invariably denies that such activities are occurring, <strong>and</strong> Chinese entities <strong>and</strong> persons<br />

continue <strong>to</strong> proliferate missile technology.<br />

FINDING. The United States finds that items transferred by Chinese entities<br />

contributed <strong>to</strong> Category I missile programs contrary <strong>to</strong> the Chinese Government’s<br />

November 2000 missile nonproliferation commitments. The United States remains<br />

concerned <strong>and</strong> will continue <strong>to</strong> moni<strong>to</strong>r this situation closely.<br />

RUSSIA<br />

ISSUE. During the period of this Report, Russian entities continued <strong>to</strong> supply<br />

missile-applicable technologies <strong>to</strong> missile programs of proliferation concern in China,<br />

India, Iran, <strong>and</strong> other countries.<br />

HISTORY OF COMPLIANCE EVALUATION. Russian compliance <strong>with</strong> its<br />

MTCR commitments was first assessed in the June 2003 (CY2001) NCR. In that Report<br />

the United States concluded that:<br />

Russian commercial <strong>and</strong> governmental entities have engaged in transfers<br />

that are contrary <strong>to</strong> the nonproliferation criteria outlined in the MTCR<br />

Guidelines. To date, Russia’s efforts <strong>to</strong> prevent further transfers have<br />

been inadequate.<br />

COMMITMENTS UNDERTAKEN. Russia became an MTCR Partner on<br />

August 8, 1995. Since then, the Russian Government has enacted a number of laws <strong>and</strong><br />

presidential decrees that implement controls on missile technology. The current Russian<br />

law governing the export of complete missile systems is the September 6, 1999, edict by<br />

106


President Yeltsin, “On Measures <strong>to</strong> Increase the Efficiency of Russian Federal Military-<br />

Technical Cooperation <strong>with</strong> Foreign States.” This edict makes the Ministry of Trade<br />

responsible for processing general licenses that allow enterprises <strong>to</strong> export arms<br />

independently <strong>and</strong> for granting individual equipment or technology export license for<br />

specific contracts. The Ministry is also responsible for determining the legal competence<br />

of a foreign partner <strong>to</strong> receive Russian military equipment, including verifying the enduser<br />

certificate. This edict was replaced by Edict No. 1953, December 1, 2000, “Issues<br />

Concerning the Russian Federation’s Military – Technical cooperation <strong>with</strong> Foreign<br />

States.”<br />

The current law governing the export of dual-use exports is the Federal Law on<br />

Export <strong>Control</strong>, which the Russian Government enacted on July 18, 1999. Article 20 of<br />

this law also includes “catch all” provisions. Government Resolution No. 296<br />

“Governing Foreign Trade <strong>Control</strong> over Equipment, Materials <strong>and</strong> Technologies Which<br />

Can be Used <strong>to</strong> Make Missile Weapons,” enacted on April 16, 2001 <strong>and</strong> subsequently<br />

updated in Oc<strong>to</strong>ber 2001 <strong>and</strong> Oc<strong>to</strong>ber 2002, creates the procedures by which the trade of<br />

missile technology in the Russian Federation is <strong>to</strong> occur. The Federal Law created the<br />

Department of Export <strong>Control</strong> (DEK) which was responsible for conducting license<br />

determinations at the request of exporters, for processing <strong>and</strong> issuing export licenses, for<br />

developing <strong>and</strong> maintaining commodity classification lists, <strong>and</strong> for drafting regulations<br />

designed <strong>to</strong> ensure continued implementation of nonproliferation export controls.<br />

The March 2003 government reshuffling transferred export control oversight <strong>to</strong><br />

the Ministry of Defense (MOD). As a result, the Federal Service for Technical <strong>and</strong><br />

Export <strong>Control</strong>s under the MOD assumed responsibilities for export controls from<br />

Ministry of Economic Development <strong>and</strong> Trade (MEDT) DEK.<br />

The current limitations of Russia’s export control system are hindering the<br />

Russian Government’s ability <strong>to</strong> implement its MTCR commitment <strong>to</strong> review all Annex<br />

item transfers on a case-by-case basis, which in turn undermines its ability <strong>to</strong> “exercise<br />

restraint” in considering such transfers <strong>and</strong> effectively halt them.<br />

ACTIONS. While some progress has been made, Russian entities continued<br />

during the reporting period <strong>to</strong> supply sensitive missile-applicable items, technology, <strong>and</strong><br />

expertise <strong>to</strong> missile programs in India, Iran, <strong>and</strong> China, indicating that in many cases<br />

Russia’s export control system has been ineffective in assuring case-by-case review of<br />

Annex item transfers that would halt problematic missile-related transfers. Based on all<br />

available information, the continuing pattern of missile-related transfers by Russian<br />

entities calls in<strong>to</strong> serious question Russia’s ability <strong>to</strong> control missile proliferation<br />

COMPLIANCE-RELATED DIALOGUE AND ANALYSIS. Transfers by<br />

entities under Russia’s jurisdiction still call in<strong>to</strong> question the Russian Government’s<br />

ability <strong>to</strong> conduct case-by-case review or its willingness <strong>to</strong> exercise restraint <strong>with</strong> respect<br />

<strong>to</strong> MTCR-controlled technologies <strong>to</strong> ballistic missile programs of concern. Although<br />

107


such transfers are not directly barred by the MTCR, Russia’s actions do not accord <strong>with</strong><br />

the MTCR implementation policies of the United States <strong>and</strong> other MTCR members.<br />

The United States has raised its concerns about these transfers at all levels of the<br />

Russian Government. If this assistance is authorized by the Russian Government, this<br />

assistance is not directly precluded by Russia’s commitments under the MTCR<br />

Guidelines. To the extent these transfers are not authorized by the Russian Government,<br />

they raise concerns regarding its ability <strong>to</strong> implement controls on missile-related<br />

technologies.<br />

FINDING. Russian entities have engaged in transfers that, although not directly<br />

precluded by Russia’s commitments under the MTCR Guidelines, raise serious missile<br />

proliferation concerns <strong>and</strong> call in<strong>to</strong> question Russia’s ability <strong>to</strong> implement controls on<br />

missile-related technologies. To date, Russia’s efforts <strong>to</strong> prevent further transfers have<br />

been inadequate.<br />

108

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!