Air Force
Intelligence and Security Doctrine

4.2.USAF STARS Notifications.Table 4.1. is a numerical list of all START formats used by the Air Force for STARS and manual reporting. Table 4.1. can be used for a quick reference during step two of notification processing. The parenthesis around a format number in the Additional Expected Reports' columns mean a Notification Format may be required. Table 4.2. identifies applicable notifications for heavy bombers, ICBMs, and mobile ICBMs as they relate to the START Treaty Notification Protocol. Table 4.3. contains every Air Force site name, location, function, and associated TAI serial number. Table 4.4. is an alphabetical list of every TAI by name and category. Table 4.5. lists declared Air Force facilities as they appear in each Annex of the START MOU. Table 4.6. includes all conversion and elimination options. Refer to the specific notification sequence for required notifications.

4.3.Sample Instructions.The samples in figures 4.6. through 4.9. show completed STARS notification formats. Note that entries are required, except in the "References" and "Remarks" lines. If a blank is not filled in, it must read, "N/A." Abbreviations are limited: spell out "AFB" and the state (under location). List the times in Zulu. Ensure the month and year are correct. Leave the geographic coordinates blank except for Format 4 (loss location) and Format 78. The STARS Central Node will add other required coordinates to all manually-submitted notifications. The sample facsimile cover sheet (figure 4.10.) contains data required for manual reporting.
4.3.1.TAI Serial Number."Serial Number of TAI" that appears on many notification formats is not a START requirement. It is used to track items in the STARS data base and is stripped off at the STARS Central Node prior to transmission. Note that some formats have a space for a unique identifier (serial number) for mobile launchers of ICBMs (Peacekeeper).

4.4.Notification Tracking Logs. Figure 4.11. is a spreadsheet used primarily to track TAI movements and alert reporting nodes of upcoming required notifications. Figures 4.12. and 4.13. are used to record key data regarding incoming and outgoing notifications, respectively.
4.4.1. A description of required field entries for figure 4.11. follow. Enter the information explained below to help you track TAI movement start to finish:
4.4.1.1.Other:
4.4.1.2.FMT#:notifications (anything other than 951/952/953) number located top of notification.
4.4.1.3.RPT#: Unit ID/Message number (EXAMPLE:C9 414) number located at bottom right hand corner of screen.
4.4.1.4.Message TOR:you process the message (EXAMPLE:05JAN1215z).
4.4.1.5.TYPE:of Treaty Accountable Item (EXAMPLE:or MMII) read section A on the notification.
4.4.1.6.TAI#:number (EXAMPLE:
4.4.2.Bomber/Missile Movement.
4.4.2.1.FMT 951/953#: Enter notification ID for Non-NRRC msg 951 or 953 (EXAMPLE:453) number located at bottom right hand corner of screen.
4.4.2.2.ETA:time of arrival (EXAMPLE: 21DEC2140z) read section G on the notification.
4.4.2.3.FMT 952/26#:notification ID for Non-NRRC msg 952 or NRRC msg 26 (EXAMPLE:1090) number located at bottom right hand corner of screen.
4.4.2.4.ATA:time of arrival (EXAMPLE: 952: 21DEC2159z or 26: 22DEC93) read section C for the 952 and section G for the 26.
4.4.2.5.FMT 30#:notification ID for the NRRC msg 30 (EXAMPLE:number located at bottom right hand corner of screen.
4.4.2.6.FMT 951#:notification ID for the Non-NRRC msg (EXAMPLE:453) number located at bottom right hand corner of screen.
4.4.2.7.ETA:time of arrival (EXAMPLE:21DEC2140z) read section G on the notification.
4.4.2.8.FMT 31#:notification ID for the NRRC msg 31 (EXAMPLE:number located at bottom right hand corner of screen.
4.4.2.9.FMT 952#:notification ID for the Non-NRRC msg (EXAMPLE:453) number located at bottom right hand corner of screen.
4.4.2.10.ATA:time of arrival (EXAMPLE:read section C on the notification.
4.4.2.11.Comments:to location (EXAMPLE:Minot - Ellsworth, MMII base - complex) read on the 951: section E and F, and on 953 section D and F

4.5.Conversion Notification Log. The sample log in figure 4.14. is used to record the conversion of Missile Silos or Missiles.
4.5.1.of Required Field Entries:
4.5.1.1.Number:the serial number of TAI for the Missile Silo or Missile (EXAMPLE: KGFAI08, or 13245)
4.5.1.2.type or variant of TAI. (EXAMPLE:or MMIII)
4.5.1.3.MSG RCV'D/FILE #:the DTG of the message received (EXAMPLE:Jan 94/1300/ CI000456)
4.5.1.4.53 MSG #:the file name of the FMT 53 and the date received. (EXAMPLE: 12
4.5.1.5.Date of Initiation:the date of schedule initiation from section "F" in the FMT 53 (EXAMPLE:
4.5.1.6.58 MSG #:the file name of the FMT 58 and the date received. (EXAMPLE: M1010235/ 12NOTE: The FMT 58 is only used for conversion of a missile silo.
4.5.1.7.56 MSG #:the file name of the FMT 56 and the date received. (EXAMPLE: C1000456/ 12
4.5.1.8.of Initiation:the date of initiation found in the FMT 56 section "E" (EXAMPLE: 12
4.5.1.9.MOU Change FMT #3:the file name of the FMT 3 and the date received. (EXAMPLE: C1000456/12
4.5.1.10.any remarks necessary for a clear understanding of the sequence.

4.6.Notification Log:spreadsheet in figure 4.15. is used to record the elimination of Missile Silos, Bombers, or Facilities.
4.6.1.Description of Required Field Entries:
4.6.1.1.Number:the serial number of TAI for the Missile Silo, Bomber or Facility (EXAMPLE:580166, or KMER000)
4.6.1.2.VAR /VER:type or variant of TAI. (EXAMPLE:B52H, or Name)
4.6.1.3.MSG RCV'D/FILE #:the DTG the message was received (EXAMPLE:Jan 94/1300)
4.6.1.4.54 MSG #:the file name of the FMT 54 and the Enter the date of scheduled initiation from section "F" in the FMT 54. (EXAMPLE: C1000975/12 Feb 94)
4.6.1.5.57 MSG#:the file name of the FMT 57 and the actual date of initiation from section "E" of the FMT 57. (EXAMPLE:12 Feb 94)
4.6.1.6.COMPLETE:the date of completion found in section "D" of the FMT 59 or in section "A-3" of FMT 61. (EXAMPLE:Jan 1994)
4.6.1.7.59/61:the file name of the FMT 59 or FMT 61 and date received (EXAMPLE:12 Jan 1994)
4.6.1.8.MOU CHANGE FMT #3:the file name of the FMT 3 and the date received. (EXAMPLE:12 Jan 1994)
4.6.1.9.any remarks necessary for a clear understanding of the sequence.
NOTE:the FMT #9 Elimination of a Declared Facility in the remarks section. Enter the FMT # and the date of elimination. (EXAMPLE: C1000456/12 Jan 94)
Figure 4.1.Unit Message Processing Instructions (Automated).

STARS NOTIFICATION GENERATION CHECKLIST (Unit) 01 OF 02

______ 1. Identify the requirement for a START notification. (Ref: Notification Sequence Charts in Chapter 3 of this document).

______ 2. Locate the appropriate format. If needed, make a copy of it as it will be your worksheet.

______ 3. Complete the notification format using the examples found in this document and directions for the particular format. If you have questions, call your treaty compliance office, MAJCOM headquarters or the USAF STARS Central Node for assistance.

______ 4. Forward the draft notification to your base STARS user node for transmission. If your office hosts the STARS computer, accomplish the following.

______ 5. At the STARS computer, Enter the data in the blank notification format.

______ 6. Complete a Format and a Compliance check.

______ 7. Send informational copies, as required.

______ 8. Transmit the notification. After the notification has been transmitted, it will be removed from the local user node.

______ 9. Disconnect from the STARS Central Node and log off the machine.

______ 10. Once the DNA STARS logon screen is displayed, you are finished with the STARS computer; leave it on or turn it off depending on local policy.

______ 11. Make a log entry using the Outgoing STARS Message Log found in this document.

______ 12. As a courtesy, notify the parent MAJCOM a notification is enroute for review.

______ 1. Identify the requirement for a START notification. (Ref:Notification Sequence Charts found in Chapter 4 of this document).

______ 2. Locate the appropriate format. Make a copy of it as this will be the sheet you fax.

______ 3. Complete the notification format using the examples following these checklists. If you have questions, call your treaty compliance office, MAJCOM or the USAF STARS Central Node for assistance.

______ a. Entries are required for most lines, except "References", "Geographic coordinates" [except for Format 4 (accident sites) and a Format 3 used to add a new facility] and "Remarks". If other lines are not filled in, they must read, "N/A". Abbreviations are limited: you must spell out "AFB" and the state (under location).

______ b. Ensure the times listed in the message make sense. (In Zulu? Correct month, year, etc?)

______ c. Leave the geographic coordinates line blank to keep the notification Unclassified; the STARS Central Node will add them to most manually-submitted notifications.

______ 4. Make copies of the fax transmittal sheets from this chapter. One copy is for the MAJCOM and STARS Central Node; the others are for interested units.

______ 5. Assign a report number and complete the appropriate sections.

______ 6. Fax the notification to your MAJCOM and to interested units.

______ 7. Log the notifications on the Outgoing STARS Message Log found in this document.

______ 8. Update the tracking sheets found in this manual.

Figure 4.3.Message Processing Instructions (Automated)

______ 1. At the STARS computer retrieve the notification.

______ 2. Complete a Format and a Compliance check. Both should pass.

______ 3. After viewing the notification, you must decide to approve/transmit it, modify it or deny it. If you are satisfied with the message,

______ a. Note the originator's name and the file name for the log.

______ b. Complete the information in the "Approve and Transmit Window."

______ 4. Disconnect from the STARS Central Node and log off the machine.

______ 5. Once the DNA STARS logon screen is displayed, you are finished with the STARS computer; leave it on or turn it off depending on local policy.

______ 6. Make a log entry using the Outgoing STARS Message Log found in this document.

______ 1. Log the incoming message using the STARS Incoming Message Log found in this document. Include the notification number and the originator's name.

______ 2. Carefully check the input notification:

______ a. Entries are required for most lines except "References," "Geographic coordinates" [except for Format 4 (accident sites) and a Format 3 used to add a new facility] and "Remarks". If other lines are not filled in, they must read, "N/A." Abbreviations are limited: check "AFB", "CA", "LRNA" etc.

______ b. Reference the times listed in the message: do they make sense? (In Zulu? Correct month, year, etc?)

______ c. Geographic coordinates should be left blank to keep the notification Unclassified; the STARS Central Node will add them to most manually submitted notifications (exceptions include a Format 4 (accident sites), a Format 3 used to add a new facility, etc).

______ 3. Complete the headquarters section of the STARS Fax Transmittal Sheet used by the unit to send this notification. Or, use one found in this document. Fax it to the Central Node: AOS/AOCO.

______ 4. Log the message using the Outgoing STARS Message Log.

______ 5. Update the tracking sheets found in this document.

Figure 4.5.Node Message Processing Instructions (Automated and Manual).

STARS NOTIFICATION APPROVAL CHECKLIST (Central Node) 01 OF 01

______ 1. Identify the requirement to process a START notification.

______ 2. Assign a report number, initial the bottom of the incoming report and put a DTG (DD-MMM-YYYY, HHMMz) on the bottom of the input message.

______ 3. Log the incoming message on the appropriate log.

______ 4. Reference the SUM input instructions and format. Check the input notification.

______ a. All entries are required except remarks. If a blank is not filled in, it must say N/A.

______ b. Check the DTG.

______ c. Check the TAI serial number against the local data for accuracy.

______ d. Check the geographic coordinates if required by the notification. They are classified and can be found under separate cover.

______ 5. Reference the SUM output instructions and format.

______ a. Fill out the notification format using the examples beginning in this manual, the treaty references, the format notification directions, the notification sequences and the tables found in Chapter 5. Address questions to the STARS SA/CSSO.

______ b. The output directions are under separate cover with the NRRC formats and provide a reference for further information in the treaty.

______ 6. Perform a format, compliance and national level compliance check.

______ 7. If you are in the manual mode, complete two STARS Fax Transmittal Sheets found on page 48 of the SUM. Send one to XOXI/NRRC with the notification. The other will be sent with a copy of the notification to the MAJCOM. If you are using the automated mode you will fill out a NRRC transmittal sheet on the PC.

______ 8. Log the message using the appropriate Outgoing STARS Message Log. The outgoing logs can be found starting on page 47 of this manual.

______ 9. Check the notification carefully. Send it to XOXI/NRRC and the appropriate MAJCOM.

Table 4.1.STARS Notifications.
Format #	START Ref.	Subject	Unit Suspense	NRRC Suspense	Additional Expected Reports
					Before	After
3	N-I-3	Notification Of Change In Data In The Memorandum Of Understanding, Unless Another Notification Of Such Change Has Been Provided	24 hours after event	5 days after event	As required	As required
4	N-I-3A	Notification Of Change in Data In The Memorandum Of Understanding, Due To Accidental Loss Of A Treaty Accountable Item	24 hours after event	5 days after event	None	None
5	N-I-3B	Notification Of Change In Data In The Memorandum Of Understanding, Due To Disablement Beyond Repair Of A Treaty Accountable Item	24 hours after event	5 days after event	None	Non-mobile missile 57, 64 Mobile missile 54, 03 Bomber 54, (57), 03, 61 Launcher w/grading 54, 57, 03, 59 all other TAI 03
7	N-I-3D	Notification Of Change In Data In The Memorandum Of Understanding, With Regards To New Facilities, New Kinds Of Support Equipment, New Types, Categories, Variants, And Versions Of Treaty Accountable Items	24 hours after event	5 days after event	(16)	None
9	N-I-3, C/E IX-2	Notification Of Change In Data In The Memorandum Of Understanding, Related to Elimination Of A Declared Facility	24 hours after event	5 days after event	54, 57	None
10	N-I-4	Notification Of Reduction In Number Of Warheads Attributed To A Deployed ICBM Or SLBM	35 days before event	30 days before event	None	None
11	N-I-5	Notification Of Planned Aggregate Number And Changes Of Deployed Strategic Offensive Arms	15 Jan each year	1 Feb of each year	None	None

Table 4.1.
Format #	START Ref.	Subject	Unit Suspense	NRRC Suspense	Additional Expected Reports
					Before	After
12	N-I-5	Notification Of Expected Number Of Deployed Strategic Offensive Arms In Excess Of Previously Notified Planned Number	35 days before event	30 days before event	11	None
16	N-I-9	Notification Containing A Declaration Of The Existence Of A New Facility Or Change In Category Of A Facility	35 days before event	30 days before event	None	07 or (03)
17	N-I-10	Notification Of Location Of A Production Facility Not Previously Declared At Which Production Of ICBMs Or SLBMs Or First Stages Of ICBMs OR SLBMs Is Planned	100 days before event	90 days before event	None	03
20	N-I-13	Notification Of Data From Unique Identifiers For ICBMs For Mobile Launchers Of ICBMs	10 days after EIF	30 days after EIF	None	None
21	N-I-14	Notification That ICBMs Or SLBMs Of A Type Are Considered ICBMs Or SLBMS Of A Retired Type	None	None	None	22 or 23
22	N-I-15	Notification Of Type, Number And Location Of ICBMs Of A Type For Mobile Launchers Of ICBMs, Which Are ICBMs Of A Retired Type	10 days before and every 3 months after	3 months after notification Format 21, and every 3 months after	21	None
23	N-I-16	Notification Of Type, Number And Location Of ICBMs And SLBMS Of Retired Types, Other Than ICBMs For Mobile Launchers Of ICBMs	10 days before and every 6 months after	6 months after notification Format 21, and every 6 months after	21	None
24	N-I-17	Notification Of Type, Number And Location Of ICBMs And SLBMS Of Former Types	60 days after EIF	90 days after EIF	None	25

Table 4.1.
Format #	START Ref.	Subject	Unit Suspense	NRRC Suspense	Additional Expected Reports
					Before	After
25	N-I-18	Notification Of Updated Data Concerning Type, Number And Location Of ICBMs And SLBMS Of Former Types	10 days after 6 month period following EIF and every 6 months after	30 days after 6 month period following EIF and every 6 months after	24	None
26	N-II-1	Notification Of Completion Of Transit Of Non-Deployed ICBMs And SLBMS	12 hours after event	48 hours after arrival, transit completed less than 30 days	953	None
30	N-II-2	Notification Of Visit Of Heavy Bomber Or Former Heavy Bomber To A Specified Facility Or Eliminated Facility When Visit Exceeds 24 Hours	1 hour after HB visit exceeds 24 hours	8 hours after HB visit exceeds 24 hours	951, 952	951, 31, 952
31	N-II-3	Notification Of Conclusion Of Visit Of Heavy Bomber Or Former Heavy Bomber To A Specified Facility Or Eliminated Facility When Visit Exceeds 24 Hours	4 hours after event	24 hours after event	30, 951	952
53	N-IV-1	Notification Of Intention To Perform A Conversion	35 days before event	30 days before event	None	Bomber to ALCM 56, 3 ALCM to bomber 56, 63, 3 Silo launcher w/o door 56, 3 Silo w/Door 56, 58, 3
54	N-IV-1	Notification Of Intention To Perform An Elimination	35 days before event	30 days before event	None	Mobile missile 03 Launcher w/grading 57, 03, 59 Bomber 57, 03, 61 Facility 57, 09
55	N-IV-1	Notification Of Intention To Place An Item On Static Display	35 days before event	30 days before event	None	65, 3
56	N-IV-2	Notification Of Initiation Of A Conversion Process Not Subjected To Inspection	24 hours after event	5 days after event	53	Bomber to ALCM 03 ALCM to bomber, 63, 03 Silo w/door 58, 03

Table 4.1.
Format #	START Ref.	Subject	Unit Suspense	NRRC Suspense	Additional Expected Reports
					Before	After
57	N-IV-2	Notification Of Initiation Of An Elimination Process Not Subjected To Inspection	24 hours after event	5 days after event	54	Non-mobile missile 64 Launcher w/grading 03, 59 Bomber 03, 61 Facility 09
58	N-IV-3	Notification Of Intention To Install ICBM Of A Different Type, Or Training Model Of A Missile Of A Different Type In A Silo Launcher For ICBMs	10 days before event	5 days before event	53 56 (may proceed or follow 58)	03
59	N-IV-4A	Notification Of Completion Of Elimination Of A Silo Launcher Of ICBMs, Silo Training Launcher, Silo Test Launcher Or A Soft-Site Launcher	24 hours after event	5 days after event	54, 57, 03	None
61	N-IV-4C	Notification Of Completion Of Elimination Of Heavy Bombers Or Former Heavy Bombers	24 hours after event	5 days after event	54, (57), (03)	(03)
63	N-IV-4DC/E VI-13	Notification Of Completion Of Conversion Of A Heavy Bomber And Its Arrival At The Viewing Site	24 hours after event	5 days after event	53, 56	03
64	N-IV-4E	Notification Of Completion Of Elimination Of ICBM Or SLBM Other Than An ICBM For Mobile Launchers Of ICBMs	24 hours after event	5 days after event	57	None
65	N-IV-4F	Notification Of Completion Of Procedures Associated With Placing An Item On Static Display	24 hours after event	5 days after event	55	03
66	N-IV-5	Notification Of Static Testing Of ICBM For Mobile Launchers Of ICBMs Or Its First Stage	24 hours after event	5 days after event	(54 when eliminating)	(03 when eliminating)
67	N-IV-5	Notification Of Removal Of Propellant Segments From ICBM For Mobile Launchers Of ICBMs Or Its First Stage	24 hours after event	5 days after event	(54 when eliminating)	(03 when eliminating)

Table 4.1.
Format #	START Ref.	Subject	Unit Suspense	NRRC Suspense	Additional Expected Reports
					Before	After
68	N-IV-6	Notification Of Annual Schedule For Conversion And Elimination	60 days after EIF/120 days before ea 1 year period for 6 yrs	90 days after EIF/90 days before ea 1 year period for 6 yrs	None	None
69	N-IV-7	Notification Of Initiation Of Elimination Process For The First ICBM Of A Particular Type Of ICBM For Mobile Launchers Of ICBMs	35 days before event	30 days before event	54	03
73	N-V-2	Notification Of Inability To Display Heavy Bombers That Are Not Readily Moveable Due To Maintenance Or Operations	2 hours after unit notified	12 hours after event	Request from other Party(ies)	None
74	N-V-3	Notification Of Cancellation Of Display In The Open Due To Force Majeure Circumstances	2 hours after unit notified	12 hours after event	Request from other Party(ies)	None
78	N-VI-1	Notification Of Flight Test Of An ICBM Or SLBM	48 hours before Zulu date of launch	24 hours before planned launch	None	3
93	N-VII-10	Notification Of First Flight Test Of A Long-Range Nuclear ALCM From A Bomber Of A Type From None OfA Long-Range Nuclear ALCM Has Previously Been Flight-Tested	48 hours after event	5 days after event	None	None
94	N-VII-11	Notification Of Arrival Of First Long-Range Nuclear ALCM Of A New Type At The First Air Base For Heavy Bombers	8 hours after event	48 hours after event	91 or 92	None
104	N-VIII-2	Notification Of Change In Information Regarding The Intention To Perform A Conversion	7 days before event	5 days before event	53	See 53
105	N-VIII-2	Notification Of Change In Information Regarding The Intention To Perform An Elimination	7 days before event	5 days before event	54	See 54
Table 4.1.
Format #	START Ref.	Subject	Unit Suspense	NRRC Suspense	Additional Expected Reports
					Before	After
106	N-VIII-2	Notification Of Change In Information Regarding The Intention To Place An Item On Static Display	7 days before event	5 days before event	55	See 55
111	N-X-5	Notification Of Updated Data For Each Category Of Data Contained In The Memorandum Of Understanding, After Resumption Of Obligation To Provide Notifications That Were Suspended Related To An Operational Dispersal	as directed	3 days after date/time in Format 108	107	112, 113
112	N-X-6	Notification Of The Provision Of All Notifications That Would Have Been Provided In Accordance With Sections III, VI, and VII Of Notifications Protocol If There Had Not Been A Temporary Suspension Of The Obligation To Provide Such Notifications	as directed		108, 109	None
113	N-X-7	Notification Of Locations Of All Heavy Bombers That Were Not Located At Their Air Bases At The Completion Of The Operational Dispersal	as directed	3 days after date/time in Format 108	107	None
142		Notification Containing A Request For Clarification Of A Notification			None	None
143		Notification Containing Clarification, Correction, Or Modification Of Notification			None	None
144		Notification Of Additional START Message			None	None
145	IP-XVI-4	Notification Of Planned Exit From A Monitored Facility Of The First ICBM, SLBM Or First Stage Of Such An ICBM Or SLBM Not Subject To Numerical Limits On Non-Deployed Missiles	190 days before first planned exit	180 days before first planned exit	None	None

Table 4.1.
Format #	START Ref.	Subject	Unit Suspense	NRRC Suspense	Additional Expected Reports
					Before	After
153	N-I-19	Notification of a change to the boundary of a facility, specified on a site diagram.	24 hours after event	5 days after event	None	None
951	Non-NRRC	Notification Of Departure Of Heavy Bomber	2 hours after event			952, (30, 31 ,3)
952	Non-NRRC	Notification Of Arrival Of Heavy Bomber	2 hours after event		951	(30, 3)
953	Non-NRRC	Notification Of Departure Of A Missile	2 hours after event		(953)	(26)

Table 4.2.Listing
HEAVY BOMBER NOTIFICATIONS
Format	Notification Protocol, Section 1--HEAVY BOMBER MOU UPDATES
3	Change in Data in the Memorandum of Understanding, Unless Another Notification of Such Change has been Provided.
4	Change in Data in the Memorandum of Understanding, Due to Accidental Loss of a Treaty Accountable Item.
153	Notification of a Change to the Boundary of a Facility, Specified on a Site Diagram.
Format	Notification Protocol, Section 2--HEAVY BOMBER MOVEMENTS
5	Change in Data in the Memorandum of Understanding, Due to Disablement Beyond Repair of a Treaty Accountable Item.
7	Notification Of Change In Data In The Memorandum Of Understanding, With Regard To New Facilities, Facilities Whose Category Has Been Changed, New Kinds Of Support Equipment, And New Types, Categories, Variants, And Versions Of Treaty Accountable Items.
9	Change in Data in the Memorandum of Understanding, Related to Elimination of a Declared Facility.
11	Planned Aggregate Number and Changes of Deployed Strategic Offensive Arms.
12	Expected Number of Deployed Strategic Offensive Arms in Excess of Previously Notified Planned Number.
16	Declaration of the Existence of a New Facility or Change in Category of a Facility.
30	Visit of Heavy Bomber or Former Heavy Bomber to a Specified Facility or Eliminated Facility when Visit Exceeds 24 Hours.
31	Conclusion of Visit of Heavy Bomber or Former Heavy Bomber to a Specified Facility or Eliminated Facility when Visit Exceeds 24 Hours.
951	Departure of Heavy Bomber.
952	Arrival of Heavy Bomber.
Format	Notification Protocol, Section 3--HEAVY BOMBER THROW WEIGHT
--	N/A for Heavy Bombers.
Format	Notification Protocol, Section 4--HEAVY BOMBER CONVERSIONS/ELIMINATIONS
53	Intention to Perform a Conversion.
54	Intention to Perform an Elimination.
55	Intention to Place an Item on Static Display.
56	Initiation of a Conversion Process Not Subjected to Inspection.
57	Initiation of an Elimination Process Not Subjected to Inspection.
61	Completion of Elimination of Heavy Bombers or Former Heavy Bombers.
62	Planned Date of Arrival of Converted Heavy Bomber at the Viewing Site.
63	Completion of Conversion of a Heavy Bomber and its Arrival at the Viewing Site.
65	Completion of Procedures Associated with Placing an Item on Static Display.
68	Annual Schedule for Conversion and Elimination.
Format	Notification Protocol, Section 5--HEAVY BOMBER COOPERATIVE MEASURES
73	Inability to Display Heavy Bombers that are not Readily Moveable due to Maintenance or Operations.
74	Cancellation of Display in the Open due to Force Majeure Circumstances.
Format	Notification Protocol, Section 6--HEAVY BOMBER FLIGHT TEST
--	N/A for Heavy Bombers.
Format	Notification Protocol, Section 7--HEAVY BOMBER NEW SYSTEMS and NEW KINDS
89	Exit of First Heavy Bomber of a New Type from the Shop, Plant or Building where its Assembly was Performed.
90	Arrival of First Heavy Bomber of a New Type, Category or Variant at the First Air Base at which any such Heavy Bomber has begun to be Based.
91	Exit of First Long-Range Nuclear ALCM of a New Type from a Production Facility.
92	Planned Arrival of First Long-Range Nuclear ALCM of a New Type at the First Air Base for Heavy Bombers at which it will be Located.
93	First Flight Test of a Long-Range Nuclear ALCM from a Bomber of a Type from None of which a Long-Range Nuclear ALCM has Previously been Flight-Tested.
94	Arrival of a First Long-Range Nuclear ALCM of a New Type at the First Air Base for Heavy Bombers.
Table 4.2.
95	Exit of a First Long-Range Non-Nuclear ALCM of a New Type from a Production Facility.
96	Planned Arrival of First Long-Range Non-Nuclear ALCM of a New Type at the First Air Base for Heavy Bombers at which it will be Located Six Months in Advance of such Arrival.
97	Planned Arrival of First Long-Range Non-Nuclear ALCM of a New Type at the First Air Base for Heavy Bombers at which it will be Located 60 Days in Advance of Such Arrival.
98	First Flight Test of a Long-Range Non-Nuclear ALCM of a New Type from an Airplane of a Type from None of which a Long-Range Nuclear ALCM has been Flight Tested.
99	First Flight Test of a Long-Range Non-Nuclear ALCM of a New Type Armed with Two or More Weapons.
100	Development of New Kind of Strategic Offensive Arms.
Format	Notification Protocol, Section 8--HEAVY BOMBER RESCHEDULE
104	Change in Information Regarding the Intention to Perform a Conversion.
105	Change in Information Regarding the Intention to Perform an Elimination.
106	Change in Information Regarding the Intention to Place an Item on Static Display.
Format	Notification Protocol, Section 9--INSPECTIONS & CONTINUOUS MONITORING
--	Not used.
Format	Notification Protocol, Section 10--HEAVY BOMBER OPERATIONAL DISPERSALS
111	Updated Data for each Category of Data Contained in the Memorandum of Understanding, after Resumption of Obligation to provide Notifications that were Suspended Related to an Operational Dispersal.
112	Provision of all Notifications that would have been provided in Accordance with Sections III, VI, and VII of the Notifications Protocol if there had not been a Temporary Suspension of the Obligation to provide such Notifications.
113	Locations of all Heavy Bombers that were not located at their Air Bases at the Completion of the Operational Dispersal.
Format	Notification Protocol, Section 11--HEAVY BOMBER MISCELLANEOUS
142	Containing a Request for Clarification of a Notification.
143	Containing Clarification, Correction or Modification of a Notification.
144	Additional START Message.
ICBM NOTIFICATIONS
Format	Notification Protocol, Section 1--ICBM MOU UPDATES
3	Change in Data in the Memorandum of Understanding, Unless Another Notification of Such Change has been Provided.
4	Change in Data in the Memorandum of Understanding, Due to Accidental Loss of a Treaty Accountable Item.
5	Change in Data in the Memorandum of Understanding, Due to Disablement Beyond Repair of a Treaty-Accountable Item.
6	Change in MOU Data due to Elimination of Silo Launcher of ICBM, Silo Training Launcher, Silo Test Launcher or Soft Site Launcher at which Grading is not to be Performed.
7	Notification Of Change In Data In The Memorandum Of Understanding, With Regard To New Facilities, Facilities Whose Category Has Been Changed, New Kinds Of Support Equipment, And New Types, Categories, Variants, And Versions Of Treaty Accountable Items.
8	Change in Data in the Memorandum of Understanding: Exhibitions of New Variants of ICBMs and SLBMs, and New Versions of Mobile Launchers of ICBMs.
9	Change in Data in the Memorandum of Understanding, Related to Elimination of a Declared Facility.
10	Reduction in Number of Warheads Attributed to a Deployed ICBM or SLBM.
11	Planned Aggregate Number and Changes of Deployed Strategic Offensive Arms.
12	Expected Number of Deployed Strategic Offensive Arms in Excess of Previously Notified Planned Number.
16	Declaration of the Existence of a New Facility or Change in Category of a Facility.
17	Location of a Production Facility not Previously Declared at which Production of ICBMs or SLBMs or First Stages of ICBMs or SLBMs is Planned.
18	Beginning of Construction of a New Silo Launcher for ICBMs.

Table 4.2.
20	Notification of Data from Unique Identifiers for ICBMs for Mobile Launchers of ICBMs.
21	ICBMs or SLBMs of a type are Considered ICBMs or SLBMs of a Retired Type.
23	Type, Number and Location of ICBMs and SLBMs of retired types, other than ICBMs for Mobile Launchers of ICBMs.
24	Type, Number and Location of ICBMs and SLBMs of Former Types.
25	Updated Data Concerning Type, Number and Location of ICBMs and SLBMs of Former Types.
153	Notification of a Change to the Boundary of a Facility, Specified on a Site Diagram.
Format	Notification Protocol, Section 2--ICBM MOVEMENTS
26	Completion of Transit of Non-Deployed ICBMs and SLBMs.
953	Departure of a Missile.
Format	Notification Protocol, Section 3--ICBM THROW WEIGHT
46	Throw-Weight Data for an ICBM of a New Type.
48	Announcement of Flight Test to Determine Ballistic Missile Throw-Weight.
49	Throw Weight Data for an ICBM of a New Type Subject to Limitations Provided for in Article II of the Treaty.
51	Increase in Accountable Throw-Weight of an ICBM.
Format	Notification Protocol, Section 4--ICBM CONVERSIONS/ELIMINATIONS
53	Intention to Perform a Conversion.
54	Intention to Perform an Elimination.
55	Intention to Place an Item on Static Display.
56	Initiation of a Conversion Process Not Subjected to Inspection.
57	Initiation of an Elimination Process Not Subjected to Inspection.
58	Intention to Install ICBM of a Different Type, or Training Model of a Missile of a Different Type in a Silo Launcher for ICBMs.
59	Completion of Elimination of a Silo Launcher of ICBMs, Silo Training Launcher, Silo Test Launcher or a Soft-Site Launcher
64	Completion of Elimination of ICBM or SLBM other than an ICBM for Mobile Launchers of ICBMs.
65	Completion of Procedures Associated with Placing an Item on Static Display.
68	Annual Schedule for Conversion and Elimination.
Format	Notification Protocol, Section 5--COOPERATIVE MEASURES
--	N/A for ICBMs
Format	Notification Protocol, Section 6--ICBM FLIGHT TEST
78	Flight Test of an ICBM or SLBM.
Format	Notification Protocol, Section 7--ICBM NEW SYSTEMS and NEW KINDS
83	Planned Departure from a Production Facility of the First Prototype ICBM or SLBM.
84	Basing Mode of New Type of ICBM.
85	Decision to Forego Deployment of an ICBM of a New Type as an ICBM for Mobile Launchers of ICBMs.
86	Prototype ICBM or SLBM shall be Considered to be a New Type.
87	Cessation of Development of an ICBM or SLBM of a New Type and Intention not to Deploy such ICBMs or SLBMs.
100	Development of New Kind of Strategic Offensive Arms.
Format	Notification Protocol, Section 8--ICBM RESCHEDULE
104	Change in Information Regarding to the Intention to Perform a Conversion.
105	Change in Information Regarding to the Intention to Perform an Elimination.
106	Change in Information Regarding to the Intention to Place an Item on Static Display.
Format	Notification Protocol, Section 9--INSPECTIONS & CONTINUOUS MONITORING
--	Not Used.
Format	Notification Protocol, Section 10--OPERATIONAL DISPERSALS
--	N/A for Non-Mobile ICBMs

Table 4.2.
Format	Notification Protocol, Section 11--ICBM MISCELLANEOUS
142	Request for Clarification of a Notification.
143	Clarification, Correction, or Modification of Notification.
144	Additional START Message.
145	Planned Exit from a Monitored Facility of the First ICBM, SLBM, or First Stages of such ICBMs or SLBMs not Subject to Numerical Limits on Non-Deployed Missiles.
NOTIFICATIONS FOR MOBILE ICBMS
Format	Notification Protocol, Section 1--MOBILE ICBM MOU UPDATES
3	Change in Data in the Memorandum of Understanding, unless another Notification of such Change has been Provided.
4	Change in Data in the Memorandum of Understanding, due to Accidental Loss of a TAI.
5	Change in Data in the Memorandum of Understanding, due to Disablement Beyond Repair of a TAI.
7	Notification Of Change In Data In The Memorandum Of Understanding, With Regard To New Facilities, Facilities Whose Category Has Been Changed, New Kinds Of Support Equipment, And New Types, Categories, Variants, And Versions Of Treaty Accountable Items.
8	Change in Data in the Memorandum of Understanding: Exhibitions for New Variants of ICBMs and SLBMs, and New Versions of Mobile Launchers of ICBMs.
9	Change in Data in the Memorandum of Understanding, Related to Elimination of a Declared Facility.
11	Planned Aggregate Number and Changes of Deployed Strategic Offensive Arms.
12	Expected Number of Deployed Strategic Offensive Arms in Excess of Previously Notified Planned Number.
153	Notification of a Change to the Boundary of a Facility, Specified on a Site Diagram.
Format	Notification Protocol, Section 2--MOBILE ICBM MOVEMENTS
16	Declaration of the Existence of a New Facility or Change in Category of a Facility.
22	Type, Number and Location of ICBMs of a Type for Mobile Launchers of ICBMs, which are ICBMs of a retired type.
27	Completion of Transit of Launch Canisters that Remain After Flight Tests of ICBMs for Mobile Launchers of ICBMs.
28	Completion of Transit of Non-Deployed Mobile Launchers of ICBMs.
29	Completion of Transit of Mobile Training Launchers.
32	Departure of Each Deployed Rail-Mobile Launcher of ICBMs and its Associated Missile from a Rail-Garrison for Routine Movement.
33	Departure of Each Rail-Mobile Test Launcher From a Test Range.
34	Return of Each Deployed Rail-Mobile Launcher of ICBMs and its Associated Missile to the Rail-Garrison From which it Departed after Routine Movement.
35	Return of each Rail-Mobile Test Launcher to the Test Range from which it Departed.
36	Variations from Configuration of Train with Rail-Mobile Test Launchers while Train is Located Outside the Test Range.
37	Departure of each Deployed Mobile Launcher of ICBMs and its Associated Missile for Relocation.
38	Completion of Relocation of a Deployed Mobile Launcher of ICBMs and its Associated Missile.
39	Beginning of Exercise Dispersals of Deployed Mobile Launchers of ICBMs and their Associated Missiles.
40	Completion of Exercise Dispersals of Deployed Mobile Launchers of ICBMs and their Associated Missiles.
41	Variation from the Standard Configuration of a Train upon Departure of Deployed Rail-Mobile Launchers of ICBMs and their Associated Missiles from a Rail Garrison for the Associated Maintenance Facility.
42	Variation from the Standard Configuration of Trains with Deployed Rail-Mobile Launchers of ICBMs and Their Associated Missiles during Routine Movement or Relocation.
43	Return to Standard Configuration of a Train with Deployed Rail-Mobile Launchers of ICBMs and their Associated Missiles.
Format	Notification Protocol, Section 3--ICBM THROW WEIGHT
--	N/A for Mobile ICBMs.
Format	Notification Protocol, Section 4--MOBILE ICBM CONVERSIONS/ELIMINATIONS
53	Intention to Perform a Conversion.
54	Intention to Perform an Elimination.
55	Intention to Place an Item on Static Display.
Table 4.2.
56	Initiation of a Conversion Process Not Subjected to Inspection.
57	Initiation of an Elimination Process Not Subjected to Inspection.
65	Completion of Procedures Associated with Placing an Item on Static Display.
66	Static Testing of ICBM for Mobile Launchers of ICBMs or its First Stage.
67	Removal of Propellant Segments from ICBM for Mobile Launchers of ICBMs or its First Stage.
68	Annual Schedule for Conversion and Elimination.
69	Initiation of Elimination Process for the First ICBM of a Particular Type of ICBM for Mobile Launchers of ICBMs.
Format	Notification Protocol, Section 5--MOBILE ICBM COOPERATIVE MEASURES
74	Cancellation of Display in the Open Due to Force Majeure Circumstances.
Format	Notification Protocol, Section 6--MOBILE ICBM FLIGHT TEST
78	Flight Test of an ICBM or SLBM.
Format	Notification Protocol, Section 7--MOBILE ICBM NEW SYSTEMS AND NEW KINDS
88	Departure of Mobile Launcher of Prototype ICBMs from its Production Facility.
100	Development of New Kind of Strategic Offensive Arms.
Format	Notification Protocol, Section 8--MOBILE ICBM RESCHEDULE
101	Change in Information regarding the Departure of Each Deployed Rail-Mobile Launcher of ICBMs and its Associated Missile from a Rail-Garrison for Routine Movement.
102	Change in Information regarding the Departure of Each Rail-Mobile Test Launcher from a Test Range.
103	Change in Information regarding the Departure of each Deployed Mobile Launcher of ICBMs and its Associated Missile for Relocation.
104	Change in Information regarding the Intention to Perform a Conversion.
105	Change in Information regarding the Intention to Perform an Elimination.
106	Change in Information regarding the Intention to Place an Item on Static Display.
Format	Notification Protocol, Section 9--INSPECTIONS & CONTINUOUS MONITORING
--	Not used.
Format	Notification Protocol, Section 10--MOBILE ICBM OPERATIONAL DISPERSALS
111	Updated Data for Each Category of Data Contained in the Memorandum of Understanding, after Resumption of Obligation to provide Notifications that where Suspended Due to an Operational Dispersal.
112	The Provision of all Notifications that would have been Provided in Accordance with Sections III, VI, and VII of the Notifications Protocol if there had not been a Temporary Suspension of the Obligation to provide such Notifications.
Format	Notification Protocol, Section 11--MOBILE ICBM MISCELLANEOUS
142	Request for Clarification of a Notification.
143	Clarification, Correction, or Modification of Notification.
144	Additional START Message.
145	Planned exit from a Monitored Facility of the First ICBM, SLBM, or First Stage of such an ICBM or SLBM not Subject to Numerical Limits on Non-Deployed Missiles.

Table 4.3. Site Data.
SITE NAME & LOCATION	SITE FUNCTION	SERIAL #
AEROJET GENERAL CORPORATION, CALIFORNIA	STORAGE FACILITY FOR FORMER ICBMS	XDVA003
AIR AND SPACE MUSEUM, WASHINGTON D.C.	STATIC DISPLAY SITE	ULGZ000
ANDERSEN AIR FORCE BASE, GUAM	STATIC DISPLAY SITE	PGUA000
BARKSDALE AIR FORCE BASE, LOUISIANA	AIR BASE FOR LRNA	KBAD000
BARKSDALE AIR FORCE BASE, LOUISIANA	STATIC DISPLAY SITE	KBAD001
BOEING PLANT, KANSAS	REPAIR FACILITY FOR HEAVY BOMBERS	KIAB001
CAMP NAVAJO, ARIZONA	STORAGE FACILITY FOR ICBMS	NADA000
CASTLE AIR FORCE BASE, CALIFORNIA	STATIC DISPLAY SITE	KMER001
DAVIS-MONTHAN AIR FORCE BASE, ARIZONA	C OR E FACILITY FOR HEAVY BOMBERS	KDMA000
DAVIS-MONTHAN AIR FORCE BASE, ARIZONA	STATIC DISPLAY SITE	KDMA001
DYESS AIR FORCE BASE, TEXAS	AIR BASE FOR NUCLEAR ARMS OTHER THAN LRNA	KDYS000
DYESS AIR FORCE BASE, TEXAS	STATIC DISPLAY SITE	KDYS001
EDWARDS AIR FORCE BASE, CALIFORNIA	FLIGHT CENTER FOR TEST HEAVY BOMBERS	KEDW000
EDWARDS AIR FORCE BASE, CALIFORNIA	STATIC DISPLAY SITE	KEDW001
EGLIN AIR FORCE BASE, FLORIDA	STATIC DISPLAY SITE	KVPS000
ELLSWORTH AIR FORCE BASE, SOUTH DAKOTA	AIR BASE FOR NUCLEAR ARMS OTHER THAN LRNA	KRCA003
ELLSWORTH AIR FORCE BASE, SOUTH DAKOTA	MAINTENANCE FACILITY FOR SILO ICBMS	KRCA002
ELLSWORTH AIR FORCE BASE, SOUTH	STATIC DISPLAY SITE	KRCA004
ELLSWORTH MISSILE COMPLEX, SOUTH DAKOTA	ICBM BASE FOR SILO LAUNCHERS	KRCA001
F.E. WARREN AIR FORCE BASE, WYOMING	MAINTENANCE FACILITY FOR SILO ICBMS	KCYS002
F.E. WARREN AIR FORCE BASE, WYOMING	STATIC DISPLAY SITE	KCYS003
F.E. WARREN MISSILE COMPLEX, WYOMING	ICBM BASE FOR SILO LAUNCHERS	KCYS001
FAIRCHILD AIR FORCE BASE, WASHINGTON	STATIC DISPLAY SITE	KSKA002
GRAND FORKS AIR FORCE BASE, NORTH DAKOTA	MAINTENANCE FACILITY FOR SILO ICBMS	KRDR002
GRAND FORKS AIR FORCE BASE, NORTH DAKOTA	STATIC DISPLAY SITE	KRDR004
GRAND FORKS MISSILE COMPLEX, NORTH DAKOTA	ICBM BASE FOR SILO LAUNCHERS	KRDR001
GRIFFISS AIR FORCE BASE, NEW YORK	STATIC DISPLAY SITE	KRME002
HILL AIR FORCE BASE, UTAH	REPAIR FACILITY FOR ICBMS	KHIF000
HILL AIR FORCE BASE, UTAH	STATIC DISPLAY SITE	KHIF002
K.I. SAWYER AIR FORCE BASE, MICHIGAN	STATIC DISPLAY SITE	KSAW002
Table 4.3. Continued.
SITE NAME & LOCATION	SITE FUNCTION	SERIAL #
KELLY AIR FORCE BASE, TEXAS	STATIC DISPLAY SITE	KSKF002
KIRTLAND AIR FORCE BASE, NEW MEXICO	STATIC DISPLAY SITE	KABQ000
KOREAN WAR MEMORIAL MUSEUM SEOUL, KOREA	STATIC DISPLAY SITE	KAMU000
LACKLAND AIR FORCE BASE, TEXAS	STATIC DISPLAY SITE	MMMX000
LANGLEY AIR FORCE BASE, VIRGINIA	STATIC DISPLAY SITE	KLFI000
LOWRY AIR FORCE BASE, COLORADO	STATIC DISPLAY SITE	NTNQ000
MALMSTROM AIR FORCE BASE, MONTANA	MAINTENANCE FACILITY FOR SILO ICBMS	KGFA002
MALMSTROM AIR FORCE BASE, MONTANA	STATIC DISPLAY SITE	KGFA003
MALMSTROM MISSILE COMPLEX, MONTANA	ICBM BASE FOR SILO LAUNCHERS	KGFA001
MARCH AIR FORCE BASE MUSEUM, CALIFORNIA	STATIC DISPLAY SITE	KRIV000
MAXWELL AIR FORCE BASE, ALABAMA	STATIC DISPLAY SITE	KMXF000
MCCONNELL AIR FORCE BASE, KANSAS	AIR BASE FOR NUCLEAR ARMS OTHER THAN LRNA	KIAB000
MCCONNELL AIR FORCE BASE, KANSAS	STATIC DISPLAY SITE	KIAB002
MINOT AIR FORCE BASE, NORTH DAKOTA	AIR BASE FOR LRNA	KMIB003
MINOT AIR FORCE BASE, NORTH DAKOTA	MAINTENANCE FACILITY FOR SILO ICBMS	KMIB002
MINOT AIR FORCE BASE, NORTH DAKOTA	STATIC DISPLAY SITE	KMIB004
MINOT MISSILE COMPLEX, NORTH DAKOTA	ICBM BASE FOR SILO LAUNCHERS	KMIB001
MUSEUM OF FLIGHT ANNEX, WASHINGTON	STATIC DISPLAY SITE	KMOF000
NORTHROP PLANT, CALIFORNIA	PRODUCTION FACILITY FOR FORMER AND HEAVY BOMBERS	KPMD000
NORTON AIR FORCE BASE, CALIFORNIA	STATIC DISPLAY SITE	KSBD000
OASIS COMPLEX, UTAH	C0NVERSION OR ELIMINATION FACILITY FOR ICBMS	JJZY000
OFFUTT AIR FORCE BASE, NEBRASKA	STATIC DISPLAY SITE	KOFF000
OKLAHOMA CITY, OKLAHOMA	STATIC DISPLAY SITE	KOKC000
ORLANDO, FLORIDA	STATIC DISPLAY SITE	SLWD000
PATRICK AIR FORCE BASE, FLORIDA	STATIC DISPLAY SITE	KCOF000
PIMA AIR MUSEUM, ARIZONA	STATIC DISPLAY SITE	TFXX000
ROBINS AIR FORCE BASE, GEORGIA	STATIC DISPLAY SITE	KWRB000
ROCKWELL PLANT, CALIFORNIA	REPAIR FACILITY FOR HEAVY BOMBERS	KPMD001
ROME AIR DEVELOPMENT CENTER, NEW YORK	GROUND TRAINER SITE	ZZZZ000
SHEPPARD AIR FORCE BASE, TEXAS	GROUND TRAINER SITE	KSPS002
SHEPPARD AIR FORCE BASE, TEXAS	STATIC DISPLAY SITE	KSPS000
Table 4.3. Continued.
SITE NAME & LOCATION	SITE FUNCTION	SERIAL #
SOUTH DAKOTA AIR AND SPACE MUSEUM, SOUTH DAKOTA	STATIC DISPLAY SITE	VEZZ000
STRATEGIC AIR COMMAND MUSEUM, NEBRASKA	STATIC DISPLAY SITE	SGEY000
THIOKOL CORPORATION, UTAH	PRODUCTION FACILITY FOR ICBMS	JJZT000
THIOKOL CORPORATION, UTAH	STATIC DISPLAY SITE	JJZT004
TINKER AIR FORCE BASE, OKLAHOMA	REPAIR FACILITY FOR HEAVY BOMBERS	KTIK000
TINKER AIR FORCE BASE, OKLAHOMA	STATIC DISPLAY SITE	KTIK002
TOOELE ARMY DEPOT, UTAH	STORAGE FACILITY FOR FORMER ICBMS	KTOL000
TRAVIS AIR FORCE BASE, CALIFORNIA	STATIC DISPLAY SITE	KSUU002
UNITED STATES AIR FORCE ACADEMY, COLORADO	STATIC DISPLAY SITE	EDUY000
UNITED STATES AIR FORCE MUSEUM, OHIO	STATIC DISPLAY SITE	KFFO000
USS ALABAMA MEMORIAL PARK, ALABAMA	STATIC DISPLAY SITE	QMFZ000
VANDENBERG AIR FORCE BASE, CALIFORNIA	STATIC DISPLAY SITE	KVBG001
VANDENBERG AIR FORCE BASE, CALIFORNIA	TEST RANGE FOR ICBMS	KVBG000
VANDENBERG SPACE LAUNCH COMPLEX, CALIFORNIA	SPACE LAUNCH FACILITY	KVBG002
WHITEMAN AIR FORCE BASE, MISSOURI	MAINTENANCE FACILITY FOR SILO ICBMS	KSZL002
WHITEMAN AIR FORCE BASE, MISSOURI	STATIC DISPLAY SITE	KSZL003
WHITEMAN AIR FORCE BASE, MISSOURI	STATIC DISPLAY SITE	KSZL005
WHITEMAN AIR FORCE BASE MISSOURI	AIR BASE FOR NUCLEAR ARMS OTHER THAN LRNA	KSZL004
WHITEMAN MISSILE COMPLEX, MISSOURI	ICBM BASE FOR SILO LAUNCHERS	KSZL001

Table 4.4.Name & Category
TAI NAME	TAI CATEGORY
AIR BASE FOR FORMER HEAVY BOMBERS	FACILITY
AIR BASE FOR LRNA	FACILITY
AIR BASE FOR NON-NUCLEAR ARMAMENTS	FACILITY
AIR BASE FOR NUCLEAR ARMS OTHER THAN LRNA	FACILITY
B-1 GROUND TRAINER	GROUND TRAINER
B-1 STATIC DISPLAY	HEAVY BOMBER ON STATIC DISPLAY
B-1 TEST HEAVY BOMBER	TEST HEAVY BOMBER
B-1B WITH NUCLEAR ARMS OTHER THAN LRNA	HEAVY BOMBER WITH NUCLEAR ARMS OTHER THAN LRNA
B-2 GROUND TRAINER	GROUND TRAINER
B-2A TEST HEAVY BOMBER	TEST HEAVY BOMBER
B-2A WITH NUCLEAR ARMS OTHER THAN LRNA	HEAVY BOMBER WITH NUCLEAR ARMS OTHER THAN LRNA
B-52 TEST HEAVY BOMBER	TEST HEAVY BOMBER
B-52A STATIC DISPLAY	HEAVY BOMBER ON STATIC DISPLAY
B-52B STATIC DISPLAY	HEAVY BOMBER ON STATIC DISPLAY
B-52D STATIC DISPLAY	HEAVY BOMBER ON STATIC DISPLAY
B-52F STATIC DISPLAY	HEAVY BOMBER ON STATIC DISPLAY
B-52G GROUND TRAINER	GROUND TRAINER
B-52G STATIC DISPLAY	HEAVY BOMBER ON STATIC DISPLAY
B-52G WITH LRNA	HEAVY BOMBER WITH LRNA
B-52G WITH NUCLEAR ARMS OTHER THAN LRNA	HEAVY BOMBER WITH NUCLEAR ARMS OTHER THAN LRNA
B-52H GROUND TRAINER	GROUND TRAINER
B-52H STATIC DISPLAY	HEAVY BOMBER ON STATIC DISPLAY
B-52H WITH LRNA	HEAVY BOMBER WITH LRNA
ELIMINATED FACILITY	FACILITY
ENGINEERING MODEL OF MM-II SILO LAUNCHER	ENGINEERING MODEL
ENGINEERING MODEL OF MM-III SILO LAUNCHER	ENGINEERING MODEL
ENGINEERING MODEL OF PEACEKEEPER SILO LAUNCHER	ENGINEERING MODEL
FLIGHT CENTER FOR TEST HEAVY BOMBERS	FACILITY
FORMER HEAVY BOMBER	FORMER HEAVY BOMBER
GROUND TRAINER SITE	FACILITY
ICBM BASE FOR SILO LAUNCHERS	FACILITY
ICBM TRAINING FACILITY	FACILITY
MAINTENANCE FACILITY FOR SILO ICBMS	FACILITY
MM-I	FORMER ICBM
MM-II EMPLACEMENT EQUIPMENT	EMPLACEMENT EQUIPMENT
MM-II FOR SILO LAUNCHER	ICBM FOR FIXED LAUNCHER
Table 4.4.
TAI NAME	TAI CATEGORY
MM-II LAUNCHER STATIC DISPLAY	ICBM LAUNCHER ON STATIC DISPLAY
MM-II SILO LAUNCHER	FIXED ICBM LAUNCHER
MM-II SOFT-SITE LAUNCHER	SOFT-SITE ICBM LAUNCHER
MM-II STATIC DISPLAY	ICBM ON STATIC DISPLAY
MM-II TEST LAUNCHER	TEST FIXED LAUNCHER
MM-II TRAINING SILO LAUNCHER	TRAINING FIXED LAUNCHER
MM-III EMPLACEMENT EQUIPMENT	EMPLACEMENT EQUIPMENT
MM-III FOR SILO LAUNCHER	ICBM FOR FIXED LAUNCHER
MM-III LAUNCHER STATIC DISPLAY	ICBM LAUNCHER ON STATIC DISPLAY
MM-III SILO LAUNCHER	FIXED ICBM LAUNCHER
MM-III SOFT-SITE LAUNCHER	SOFT-SITE ICBM LAUNCHER
MM-III STATIC DISPLAY	ICBM ON STATIC DISPLAY
MM-III TEST LAUNCHER	TEST FIXED LAUNCHER
MM-III TRAINING SILO LAUNCHER	TRAINING FIXED LAUNCHER
PEACEKEEPER	ICBM FOR RAIL-MOBILE LAUNCHER
PEACEKEEPER EMPLACEMENT EQUIPMENT	EMPLACEMENT EQUIPMENT
PEACEKEEPER LAUNCHER STATIC DISPLAY	ICBM LAUNCHER ON STATIC DISPLAY
PEACEKEEPER MOBILE LAUNCHER STATIC DISPLAY	ICBM LAUNCHER ON STATIC DISPLAY
PEACEKEEPER SILO LAUNCHER	FIXED ICBM LAUNCHER
PEACEKEEPER SOFT-SITE LAUNCHER	SOFT-SITE ICBM LAUNCHER
PEACEKEEPER STATIC DISPLAY	ICBM ON STATIC DISPLAY
PEACEKEEPER TEST LAUNCHER	TEST FIXED LAUNCHER
PEACEKEEPER TRAINING SILO LAUNCHER	TRAINING FIXED LAUNCHER
POLARIS	FORMER SLBM
PRODUCTION FACILITY FOR FORMER AND HEAVY BOMBERS	FACILITY
PRODUCTION FACILITY FOR ICBMS	FACILITY
REPAIR FACILITY FOR HEAVY BOMBERS	FACILITY
REPAIR FACILITY FOR ICBMS	FACILITY
SICBM FOR ROAD-MOBILE LAUNCHER	ICBM FOR ROAD-MOBILE LAUNCHER
SPACE LAUNCH FACILITY	FACILITY
STATIC DISPLAY SITE	FACILITY
STORAGE FACILITY FOR FORMER AND HEAVY BOMBERS	FACILITY
STORAGE FACILITY FOR FORMER ICBMS	FACILITY
STORAGE FACILITY FOR ICBMS	FACILITY
STORAGE FACILITY FOR RETIRED ICBMS	FACILITY
TEST RANGE FOR ICBMS	FACILITY
TRAINING B-2	TRAINING HEAVY BOMBER
TRAINING MM-II	TRAINING MODEL OF ICBM
TRAINING MM-III	TRAINING MODEL OF ICBM
TRAINING PEACEKEEPER	TRAINING MODEL OF ICBM
TRAINING SICBM	TRAINING MODEL OF ICBM

Table 4.5.of Declared Facilities.
ICBMS AND ICBM LAUNCHERS
ICBM BASES FOR SILO LAUNCHERS OF ICBMS	MAINTENANCE FACILITIES
F.E. Warren Missile Complex, Wyoming Malmstrom Missile Complex, Montana Grand Forks Missile Complex, North Dakota Minot Missile Complex, North Dakota Ellsworth Missile Complex, South Dakota Whiteman Missile Complex, Missouri	F.E. Warren Air Force Base, Wyoming Malmstrom Air Force Base, Montana Grand Forks Air Force Base, North Dakota Minot Air Force Base, North Dakota Ellsworth Air Force Base, South Dakota Whiteman Air Force Base, Missouri
ICBM BASES FOR ROAD-MOBILE LAUNCHERS OF ICBMS	ICBM BASES FOR RAIL-MOBILE LAUNCHERS OF ICBMS
None	None
ICBM LOADING FACILITIES	STORAGE FACILITIES FOR MOBILE LAUNCHERS OF ICBMS
None	None
STORAGE FACILITIES FOR ICBMS	REPAIR FACILITIES FOR ICBMS
Camp Navajo, Arizona	Hill Air Force Base, Utah
PRODUCTION FACILITIES FOR ICBMS	TEST RANGES
Thiokol Corporation, Utah	Vandenberg Air Force Base, California
PRODUCTION FACILITIES FOR MOBILE LAUNCHERS OF ICBMS	TRAINING FACILITIES
None	None
REPAIR FACILITIES FOR MOBILE LAUNCHERS OF ICBMS	STATIC DISPLAYS
None	Air Force Museum, Wright Patterson Air Force Base, Ohio Hill Air Force Base, UT
CONVERSION OR ELIMINATION FACILITIES
Oasis Complex, Utah
HEAVY BOMBERS AND FORMER HEAVY BOMBERS
AIR BASES FOR HEAVY BOMBERS EQUIPPED FOR LONG RANGE NUCLEAR ALCMS	AIR BASES FOR HEAVY BOMBERS EQUIPPED FOR NUCLEARARMAMENTS OTHER THAN LONG-RANGE NUCLEAR ALCMS
Barksdale Air Force Base, Louisiana Minot Air Force Base, North Dakota	McConnell Air Force Base, Kansas Dyess Air Force Base, Texas Ellsworth Air Force Base, South Dakota Whiteman Air Force Base, Missouri
AIR BASES FOR HEAVY BOMBERS EQUIPPED FOR NON-NUCLEAR ARMAMENTS	AIR BASES FOR FORMER HEAVY BOMBERS
None	None
PRODUCTION FACILITIES FOR HEAVY BOMBERS AND FORMER HEAVY BOMBERS	STORAGE FACILITIES FOR HEAVY BOMBERS AND FORMER HEAVY BOMBERS
Northrop Plant, Palmdale, California	None
REPAIR FACILITIES FOR HEAVY BOMBERS AND FORMER HEAVY BOMBERS	HEAVY BOMBER FLIGHT TEST CENTERS
Tinker Air Force Base, Oklahoma Rockwell Plant, Palmdale, California Boeing Plant, Wichita, Kansas	Edwards Air Force Base, California

Table 4.5.
TRAINING FACILITIES	HEAVY BOMBERS AND FORMER HEAVY BOMBERS CONVERTED FOR USE AS GROUND TRAINERS
None	Rome Air Development Center, New York Sheppard Air Force Base, Texas
CONVERSION OR ELIMINATION FACILITIES
Davis-Monthan Air Force Base, Arizona
HEAVY BOMBER AND FORMER HEAVY BOMBER STATIC DISPLAYS
Air and Space Museum, Washington D.C.	March Air Force Base Museum, California
Andersen Air Force Base, Guam	Maxwell Air Force Base, Alabama
Barksdale Air Force Base, Louisiana	McConnell Air Force Base, Kansas
Castle Air Force Base, California	Minot Air Force Base, North Dakota
Davis-Monthan Air Force Base, Arizona	Museum Of Flight Annex, Washington
Dyess Air Force Base, Texas	Norton Air Force Base, California
Edwards Air Force Base, California	Offutt Air Force Base, Nebraska
Eglin Air Force Base, Florida	Oklahoma City, Oklahoma
Ellsworth Air Force Base, South Dakota	Orlando, Florida
Fairchild Air Force Base, Washington	Patrick Air Force Base, Florida
Grand Forks Air Force Base, North Dakota	Pima Air Museum, Arizona
Griffiss Air Force Base, New York	Robins Air Force Base, Georgia
Hill Air Force Base, Utah	Sheppard Air Force Base, Texas
K.I. Sawyer Air Force Base, Michigan	South Dakota Air And Space Museum, South Dakota
Kelly Air Force Base, Texas	Strategic Air Command Museum, Nebraska
Kirtland Air Force Base, New Mexico	Thiokol Corporation, Utah
Korean War Memorial Museum Seoul, Korea	Tinker Air Force Base, Oklahoma
Lackland Air Force Base, Texas	Travis Air Force Base, California
Langley Air Force Base, Virginia	United States Air Force Academy, Colorado
Lowry Air Force Base, Colorado	United States Air Force Museum, Ohio
Malmstrom Air Force Base, Montana	USS Alabama Memorial Park, Alabama
Vandenberg Air Force Base, California	Yankee Air Museum, Ypsilanti, Michigan
Whiteman Air Force Base, Missouri
MISCELLANEOUS
ELIMINATED FACILITIES	SPACE LAUNCH FACILITIES
None	Vandenberg Space Launch Complex, California
FACILITIES SUBJECT TO CONTINUOUS MONITORING	PRODUCTION AND STORAGE LOCATIONS OF SOLID ROCKETMOTORS FOR PEACEKEEPER FIRST STAGES
Thiokol Corporation, Strategic Operations, Peacekeeper Stage Final Assembly, Promontory, Utah	Thiokol Strategic Operations, Promontory, Utah Thiokol Space Operations, Promontory, Utah
TESTING LOCATIONS OF SOLID ROCKET MOTORS FOR PEACEKEEPER FIRST STAGES	FACILITIES SUBJECT TO SUSPECT-SITE INSPECTION
Thiokol Test Area (Solid Rocket Motor Testing); Promontory, Utah	Ogden Sacramento

Table 4.6.Procedures.

ELIMINATION OF ICBMS FOR MOBILE LAUNCHERS OF ICBMS

1. Stage shall be destroyed by explosive demolition/burning. Nozzle shall be crushed, flattened, cut into two pieces, or destroyed by explosion.

--or--

2. Stage shall be destroyed by explosive demolition/burning.

--or--

3. Motor case and nozzle shall be crushed, flattened, cut into two pieces, or destroyed by explosion.

ELIMINATION OF SILO LAUNCHERS OF ICBMS OR SILO TEST LAUNCHERS

4. The silo door shall be removed, dismantled, or destroyed, and the silo headworks and the silo shall be destroyed by excavation to a depth of no less than eight meters.

--or--

5. The silo door shall be removed, dismantled, or destroyed, and the silo headworks and the silo shall be destroyed by explosion to a depth of no less than six meters.

ELIMINATION OF SILO TRAINING LAUNCHERS

6. The silo door shall be removed, dismantled, or destroyed and the silo headworks shall be destroyed by excavation.

--or--

7. The silo door shall be removed, dismantled, or destroyed and the silo headworks shall be destroyed by explosion.

ELIMINATION OF SOFT-SITE LAUNCHERS

8. All fixed launch and propellant-handling equipment, as well as erecting and handling equipment, and fuel tanks, associated with such a launcher shall be removed at least 1000 meters from the soft-site launcher to be eliminated. The entire area, at least 20 meters in diameter and centered on the soft-site launcher shall be excavated to a depth of no less that two meters.

--or--

9. All fixed launch and propellant-handling equipment, as well as erecting and handling equipment, and fuel tanks, associated with such a launcher shall be removed at least 1000 meters from the soft-site launcher to be eliminated. The entire area, at least 20 meters in diameter and centered on the soft-site launcher shall be exploded to a depth of no less than two meters.

ELIMINATION OF HEAVY BOMBERS OR FORMER HEAVY BOMBERS

10. The tail section with tail surfaces shall be severed from the fuselage at a location obviously not an assembly joint. The wings shall be separated from the fuselage at any location by any method. The remainder of the fuselage shall be severed into two pieces, within the area of attachment of the wings to the fuselage, at a location obviously not an assembly joint.

CONVERSION OF HEAVY BOMBER EQUIPPED FOR LONG-RANGE NUCLEAR ALCMS INTO A HEAVY BOMBER EQUIPPED FOR NUCLEAR ARMAMENTS OTHER THAN LRNA

11. All weapons bays equipped to carry long-range nuclear ALCMs shall be modified so as to render them incapable of carrying long-range nuclear ALCMs. All external attachment joints for long-range nuclear ALCMs and all external attachment joints for pylons for long-range nuclear ALCMs shall be removed.

--or--

12. All weapons bays equipped to carry long-range nuclear ALCMs shall be modified so as to render them incapable of carrying long-range nuclear ALCMS. All external attachment joints for long-range nuclear ALCMs and all external attachment joints for pylons for long-range nuclear ALCMs shall be modified so as to render them incapable of carrying long-range nuclear ALCMs.

CONVERSION OF HEAVY BOMBER EQUIPPED FOR LONG-RANGE NUCLEAR ALCMS INTO HEAVY BOMBER EQUIPPED FOR NON-NUCLEAR ARMAMENTS

13. All weapons bays equipped to carry long-range nuclear ALCMs shall be modified so as to render them incapable of carrying long-range nuclear ALCMs. All external attachment joints for long-range nuclear ALCMs and all external attachment joints for pylons for long-range nuclear ALCMs shall be removed.

--or--

14. All weapons bays equipped to carry long-range nuclear ALCMs shall be modified so as to render them incapable of carrying long-range nuclear ALCMS. All external attachment joints for long-range nuclear ALCMs and all external

attachment joints for pylons for long-range nuclear ALCMs shall be modified so as to render them incapable of carrying long-range nuclear ALCMs.

--and--

15. All weapons bays equipped to carry nuclear armaments shall be modified so as to render them incapable of carrying nuclear armaments. All external attachment joints for nuclear armaments and all external attachment joints for pylons for nuclear armaments shall be removed.

Table 4.6.

--or--

16. All weapons bays equipped to carry nuclear armaments shall be modified so as to render them incapable of carrying nuclear armaments. All external attachment joints for nuclear armaments and all external attachment joints for pylons for nuclear armaments shall be modified so as to render them incapable of carrying nuclear armaments.

CONVERSION OF HEAVY BOMBER EQUIPPED FOR LONG-RANGE NUCLEAR ALCMS INTO TRAINING HEAVY BOMBER OR FORMER HEAVY BOMBER

17. All weapons bays equipped to carry long-range nuclear ALCMs shall be modified so as to render them incapable of carrying long-range nuclear ALCMs. All external attachment joints for long-range nuclear ALCMs and all external attachment joints for pylons for long-range nuclear ALCMs shall be removed.

--or--

18. All weapons bays equipped to carry long-range nuclear ALCMs shall be modified so as to render them incapable of carrying long-range nuclear ALCMs. All external attachment joints for long-range nuclear ALCMs and all external attachment joints for pylons for long-range nuclear ALCMs shall be modified so as to render them incapable of carrying long-range nuclear ALCMs.

--and--

19. All weapons bays equipped to carry nuclear armaments shall be modified so as to render them incapable of carrying nuclear armaments. All external attachment joints for nuclear armaments and all external attachment joints for pylons for nuclear armaments shall be removed.

--or--

20. All weapons bays equipped to carry nuclear armaments shall be modified so as to render them incapable of carrying nuclear armaments. All external attachment joints for nuclear armaments and all external attachment joints for pylons for nuclear armaments shall be modified so as to render them incapable of carrying nuclear armaments.

--and--

21. All weapons bays equipped for non-nuclear air-to-surface armaments shall be modified so as to render them incapable of carrying any air-to-surface armaments. All external attachment joints for such armaments and all external attachment joints for pylons for such armaments shall be removed.

--or--

22. All weapons bays equipped for non-nuclear air-to-surface armaments shall be modified so as to render them incapable of carrying any air-to-surface armaments. All external attachment joints for such armaments and all external attachment joints for pylons for such armaments shall be modified so as to render them incapable of carrying any air-to-surface armaments.

CONVERSION OF HEAVY BOMBER EQUIPPED FOR NUCLEAR ARMAMENTS OTHER THAN LRNA INTO HEAVY BOMBERS EQUIPPED FOR NON-NUCLEAR ARMAMENTS

23. All weapons bays equipped to carry nuclear armaments shall be modified so as to render them incapable of carrying nuclear armaments. All external attachment joints for nuclear armaments and all external attachment joints for pylons for nuclear armaments shall be removed.

--or--

24. All weapons bays equipped to carry nuclear armaments shall be modified so as to render them incapable of carrying nuclear armaments. All external attachment joints for nuclear armaments and all external attachment joints for pylons for nuclear armaments shall be modified so as to render them incapable of carrying nuclear armaments.

CONVERSION OF HEAVY BOMBER EQUIPPED FOR NUCLEAR ARMAMENTS OTHER THAN LRNA INTO TRAINING HEAVY BOMBER OR FORMER HEAVY BOMBER

25. All weapons bays equipped to carry nuclear armaments shall be modified so as to render them incapable of carrying nuclear armaments. All external attachment joints for nuclear armaments and all external attachment joints for pylons for nuclear armaments shall be removed.

--or--

26. All weapons bays equipped to carry nuclear armaments shall be modified so as to render them incapable of carrying nuclear armaments. All external attachment joints for nuclear armaments and all external attachment joints for pylons for nuclear armaments shall be modified so as to render them incapable of carrying nuclear armaments.

--or--

27. All weapons bays equipped non- nuclear air-to-surface armaments shall be modified so as to render them incapable of carrying any air-to-surface armaments. All external attachment joints for such armaments and all external attachment joints for pylons for such armaments shall be removed.

--or--

28. All weapons bays equipped for non-nuclear air-to-surface armaments shall be modified so as to render them incapable of carrying any air-to-surface armaments. All external attachment joints for such armaments and all external attachment joints for pylons for such armaments shall be modified so as to render them incapable of carrying any air-to-surface armaments.

Table 4.6.Procedures.

CONVERSION OF HEAVY BOMBER EQUIPPED FOR NON-NUCLEAR ARMAMENTS INTO TRAINING HEAVY BOMBERS OR FORMER HEAVY BOMBERS

29. All weapons bays equipped for non-nuclear air-to-surface armaments shall be modified so as to render them incapable of carrying any air-to-surface armaments. All external attachment joints for such armaments and all external attachment joints for pylons for such armaments shall be removed.

--or--

30. All weapons bays equipped for non-nuclear air-to-surface armaments shall be modified so as to render them incapable of carrying any air-to-surface armaments. All external attachment joints for such armaments and all external attachment joints for pylons for such armaments shall be modified so as to render them incapable of carrying any air-to-surface armaments.

CONVERSION OF HEAVY BOMBER OR FORMER HEAVY BOMBER TO GROUND TRAINER

31. At least one-third of each wing or the entire vertical stabilizer of the Heavy Bomber or Former Heavy Bomber shall be removed.

ELIMINATION OF GROUND TRAINER

32. The tail section with tail surfaces shall be severed from the fuselage at a location obviously not an assembly joint. The wings shall be separated from the fuselage at any location by any method. The remainder of the fuselage shall be severed into two pieces, within the area of attachment of the wings to the fuselage, at a location obviously not an assembly joint.

ELIMINATION OF AN AIR FORCE FACILITY

33. All strategic offensive arms and all support equipment specified for the facility shall be removed. Any silo shall be eliminated.

CONVERSION OF HEAVY BOMBER TO STATIC DISPLAY

34. For B-52, accomplished in each engine strut area. Cut all electric wire bundles, cut engine throttle control cables, cut bleed air ducts, cut all hydraulic lines, crimp fuel lines, cut water supply lines (if applicable).

--or--

35. For B-1 accomplished in each wing fairing area. Cut all electric wire bundles, cut engine throttle control cables, crimp bleed air ducts, crimp hydraulic lines, crimp fuel lines.

MINUTEMAN II/III SILO CONVERSIONS

36. The silo launcher shall be modified so as to render it incapable of launching a Minuteman II. The missile suspension and umbilical shall be adapted to the different missile type. Minuteman III components shall be installed in the launcher. Minuteman III unique computer programs shall be installed.

MINUTEMAN III/II SILO TEST CONVERSIONS

37. The silo launcher shall be modified so as to render it incapable of launching a Minuteman III. The missile suspension and umbilical shall be adapted to the different missile type. Minuteman II components shall be installed in the launcher. Minuteman II unique computer programs shall be installed.

PEACEKEEPER/MINUTEMAN III SILO CONVERSIONS

38. The silo launcher shall be modified so as to render it incapable of launching a Peacekeeper. The launch tube liner shall be removed and the missile suspension and umbilical shall be adapted to the different missile type. Minuteman III components shall be installed in the launcher. Minuteman III unique computer programs shall be installed.

ELIMINATION OF NON-MOBILE ICBMS

39. Propellant removed through static fire.

--or--

40. Destroyed by explosive demolition/burning.

--or--

41. Destroyed by dissection.

--or--

42. Propellant shall be removed by hydromining. The stage shall be crushed or a hole at least 25mm in diameter shall be created in the forward pressure dome.

AF FORM 3945, AUG 95 (Microsoft Word) STARS FORMAT INSTRUCTIONS--F
Figure 4.7.Format 26 Notification.

1. ANC/STR /26

2. REFERENCE(S):

3. CONTENT:

SERIAL NUMBER OF TAI: 13773

A) TYPE OF ICBM OR SLBM: PEACKEEPER

B) NUMBER OF ICBMS OR SLBMS: 1

C) UNIQUE IDENTIFIER FOR ICBM FOR MOBILE LAUNCHER OF ICBMS:

1) 0000116

D) DEPARTURE FACILITY: ELLSWORTH AIR FORCE BASE, SOUTH DAKOTA

51-00N, 173-59W

E) DATE OF DEPARTURE: 12-Oct-1999

F) ARRIVAL FACILITY: ELLSWORTH MISSILE COMPLEX, SOUTH DAKOTA

51-00N, 173-59W

G) DATE OF ARRIVAL: 12-Oct-1999

H) TRANSPORT MODE: RAIL

4. REMARKS:

5. END OF ANC/STR /26

Figure 4.8.Format 951 Instruction.

SUBJECT: NOTIFICATION OF DEPARTURE OF HEAVY BOMBER		FORMAT: 951
TREATY REF: Non-NRRC Notification 951	WHO SUBMITS: Assigned base
DESCRIPTION: Notification of a heavy bomber departure from a specified facility, going to another specified facility other than the specified facility from which the bomber is departing.
UNIT SUSPENSE: No later than 2 hours after departure	NRRC SUSPENSE: N/A
REPORT INCLUDES: SERIAL NUMBER OF TAI. Report the serial number of the Treaty Accountable Item. Example: 580166. A) BOMBER TYPE, CATEGORY (AND VARIANT IF APPLICABLE). Report the type, category, and variant of the bomber. Example: B-52H with LRNA. B) NUMBER OF HEAVY BOMBERS. Will always be reported as 1. C) DATE AND TIME OF DEPARTURE. Report the bomber departure as Zulu day, month, year, hour, and minutes. Example: 12-Oct-1999 17:40. D) FACILITY WHERE BASED. Report the name of the assigned location of the bomber. Example: Barksdale Air Force Base, Louisiana. E) FACILITY WHERE DEPARTING. Report the name of the current location of the bomber. Barksdale Air Force Base, Louisiana. F) FACILITY OF ARRIVAL. Report the name of the destination of the bomber. Example: Ellsworth Air Force Base, South Dakota. G) DATE AND TIME OF ESTIMATED ARRIVAL. Report the bomber estimated time of arrival as day, month, year, hour and minutes. Example: 12-Oct-1999 17:40.
ADDITIONAL INFORMATION: 1. The STARS Central Node computer normally automatically generates the Format 30 and 31. In the event that these Formats are not automatically generated, the assigned unit is responsible for their generation and submission.
ADDITIONAL EXPECTED REPORTS: Before: None After: Format 952, 30*, 31* * See Additional Information above
LOCAL PROCEDURES:
ADDITIONAL REPORTS REQUIRED

AF FORM 3942, AUG 95 (Microsoft Word) STARS FORMAT INSTRUCTIONS--C
Figure 4.9.Format 951 Notification.

1. ANC/NON-NRRC /951

2. REFERENCE(S):

3. CONTENT:

SERIAL NUMBER OF TAI:580249

A) BOMBER TYPE, CATEGORY (AND VARIANT IF APPLICABLE):

B-52H WITH LRNA

B) NUMBER OF HEAVY BOMBERS: 1

C) DATE AND TIME OF DEPARTURE:

12-Oct-1999 17:40

D) FACILITY WHERE BASED:BARKSDALE AIR FORCE BASE, LOUSIANA

E) FACILITY WHERE DEPARTING: BARKSDALE AIR FORCE BASE, LOUSIANA

F) FACILITY OF ARRIVAL:ELLSWORTH AIR FORCE BASE, SOUTH DAKOTA

G) DATE AND TIME OF ESTIMATED ARRIVAL:

12-Oct-1999 19:40

4. REMARKS:

5. END OF ANC/NON-NRRC /951

Figure 4.10.Facsimile Cover Sheet for STARS Manual Reporting.

Figure 4.11.STARS Notification Tracking Log.

Figure 4.12.Incoming STARS Message Log.

Figure 4.13.Outgoing STARS Message Log

Figure 4.14.Silo/Missile Conversion Notification Log.

Figure 4.15.Elimination Notification Log.

Chapter 5

NOTIFICATION INSTRUCTIONS AND FORMATS

5.2.Opposite most notifications are individual instructions detailing the data required. For manual reporting only include the geographic coordinates when the coordinates are not available in the automated STARS data base. Include the accident site coordinates for a Format 4, Accidental Loss of a TAI, for example, or the location of a new facility when using a Format 3, Change in the MOU Not Otherwise Notified. The coordinates in the examples are fictitious, and thus, Unclassified.

5.3.Reporting:When a heavy bomber departs a depot or contractor facility and is being flown by a depot or contractor crew, the following additional requirements apply:
5.3.1. NLT 30 minutes after departure, the crew will call the command post at the destination and provide the aircraft's tail number, departure time, departure location, destination and estimated arrival time. If the destination is not a heavy bomber specified facility, the crew will call the USAF Central Node.
5.3.2. NLT 30 minutes after arrival at the reportable location, the crew will contact the command post. If the arrival location is not a heavy bomber reportable location, the crew will call the USAF Central Node. The crew will report the tail number, arrival time and arrival location.
Figure 5.1. Format 3 Instructions.

SUBJECT: NOTIFICATION OF CHANGE IN DATA IN THE MEMORANDUM OF UNDERSTANDING, UNLESS ANOTHER NOTIFICATION OF SUCH CHANGE HAS BEEN PROVIDED		FORMAT: 3
TREATY REF: Notification Protocol, Section I, para 3	WHO SUBMITS: Based on the situation (Refer to Sequence Charts)
DESCRIPTION: Notification of a change in data of an MOU listed TAI not reported elsewhere.
UNIT SUSPENSE: No later than 24 hours after event	NRRC SUSPENSE: No later than 5 days after event
REPORT INCLUDES: SERIAL NUMBER OF TAI. Report the serial number of the Treaty Accountable Item. Examples: Silo Launcher of ICBMs (ICAO and Site Designator, KMIBA02; an ICBM (Minuteman II, III or Peacekeeper), 13774; or a heavy bomber (B-52, B-1 or B-2), 580166. A) MOU Data Change Section A is used to subtract an item from the MOU) Enter the silo designator and geographic coordinates in degrees, minutes, and direction when required. Example: A-2 51-00N, 173-59W. 1) TYPE, CATEGORY (AND VARIANT OR VERSION IF APPLICABLE) OF ITEMS. Examples: B-52G with LRNA or MM III For Silo Launcher. 2) NUMBER OF ITEMS. Always minus 1. 3) UNIQUE IDENTIFIER FOR ICBM FOR MOBILE LAUNCHER OF ICBMS. Report the serial number Peacekeeper only. Example: 0000116. 4) LOCATION. Report the assigned (accountability) location of the item. If the change is related to a specified facility, include the geographic coordinates in degrees, minutes and direction. Example: Barksdale Air Force Base, Louisiana. 51-00N, 173-59W. 5) DATE OF CHANGE. Report the Zulu day, month and year of the change. Example: 12-Oct-1999. B) MOU Data Change. (Section B is used to add an item to the MOU) (See A)) 1) TYPE, CATEGORY (AND VARIANT OR VERSION IF APPLICABLE) OF ITEMS. (See A)1)) 2) NUMBER OF ITEMS. Always plus 1. 3) UNIQUE IDENTIFIER FOR ICBM FOR MOBILE LAUNCHER OF ICBMS. (See A)3)) 4) LOCATION. (See A)4)) 5) DATE OF CHANGE. (Date must be the same as reported in A)5) when you are completing both sections.
ADDITIONAL INFORMATION: 1. When taking assignment of a bomber, the new assigned base will submit the Format 3 notification. 2. For movement of a Transporter Erector (TE) or Peacekeeper Emplacer (EM), the departure base will notify the gaining base, gaining MAJCOM, losing MAJCOM and Central Node via E-mail. The gaining base will submit the Format 3 to subtract and/or add the TE or Emplacer. Hill AFB will subtract the TE or Emplacer equipment upon arrival, but will not add the TE or Emplacer to the MOU. 3. When placing a Launch Control Center (LCC) on static display, only complete Section A of the Format 3 to remove the TAI from the MOU; do not complete Section B.

AF FORM 3940, AUG 95 (Microsoft Word) STARS FORMAT INSTRUCTIONS--AFigure 5.2. Unclassified Format 3.

SUBJECT: NOTIFICATION OF CHANGE IN DATA IN THE MEMORANDUM OF UNDERSTANDING, UNLESS ANOTHER NOTIFICATION OF SUCH CHANGE HAS BEEN PROVIDED

1. ANC/STR /3

2. REFERENCE(S):

3. CONTENT:

SERIAL NUMBER OF TAI:

A) MOU DATA CHANGE:

1) TYPE, CATEGORY (AND VARIANT OR VERSION IF APPLICABLE) OF ITEMS:

2) NUMBER OF ITEMS: - 1

3) UNIQUE IDENTIFIER FOR ICBM FOR MOBILE LAUNCHER OF ICBMS:

A) __ __ __ __ __ __ __

4) LOCATION:

__ __ - __ __ __, __ __ __ - __ __ __

5) DATE OF CHANGE: __ __ - __ __ __ - __ __ __ __

B) MOU DATA CHANGE:

1) TYPE, CATEGORY (AND VARIANT OR VERSION IF APPLICABLE) OF ITEMS:

2) NUMBER OF ITEMS: 1

3) UNIQUE IDENTIFIER FOR ICBM FOR MOBILE LAUNCHER OF ICBMS:

A) __ __ __ __ __ __ __

4) LOCATION:

__ __ - __ __ __, __ __ __ - __ __ __

5) DATE OF CHANGE: __ __ - __ __ __ - __ __ __ __

4. REMARKS:

5. END OF ANC/STR /3

Figure 5.3. Format 4 Instructions.

SUBJECT: NOTIFICATION OF CHANGE IN DATA IN THE MEMORANDUM OF UNDERSTANDING, DUE TO ACCIDENTAL LOSS OF A TREATY ACCOUNTABLE ITEM		FORMAT: 4
TREATY REF: Notification Protocol, Section I, para 3a	WHO SUBMITS: Assigned base or Hill AFB for an ICBM first stage in transit
DESCRIPTION: IAW the C or E Protocol, a TAI is no longer subject to treaty limits as a result of an accidental loss.
UNIT SUSPENSE: No later than 24 hours after event	NRRC SUSPENSE: No later than 5 days after event
REPORT INCLUDES: SERIAL NUMBER OF TAI. Report the serial number of the Treaty Accountable Item. Examples: Silo Launcher of ICBMs; (ICAO and site designator), KMIBA02; an ICBM (Minuteman II, III, Peacekeeper) 13774, a heavy bomber (B-52, B-1 or B-2) 580166. A. MOU Data Change: 1) TYPE, CATEGORY (AND VARIANT OR VERSION IF APPLICABLE) OF ITEMS. Examples: B-52G with LRNA or MM III For Silo Launcher. 2) NUMBER OF ITEMS. Will always be reported as 1. 3) UNIQUE IDENTIFIER FOR ICBM FOR MOBILE LAUNCHER OF ICBMS. Report the serial number for Peacekeeper only. Example: 0000116 4) LOCATION. Report the assigned (accountability) location of the item. If the change is related to a specified facility include the geographic coordinates in degrees, minutes and direction. Example: Malmstrom Air Force Base, Montana. 51-00N, 173-59W. 5) DATE OF LOSS. Report the assumed day, month and year of the loss. Example: 12-Oct-1999. 6) LOSS LOCATION. Report the approximate or assumed location of the loss and report the geographic coordinates of the loss location in degrees, minutes and direction. Example: Boston, Massachusetts. 51-00N, 173-59W. 7) CIRCUMSTANCES RELATED TO LOSS. Report the circumstances related to the loss, if such circumstances are known.
ADDITIONAL INFORMATION: 1. For the accidental loss of a heavy bomber, the catastrophic accident must either destroy the heavy bomber or otherwise render the heavy bomber unable to complete normal elimination procedures (e.g. loss at sea). 2. For the accidental loss of an ICBM first stage, the catastrophic accident must either destroy the ICBM first stage or otherwise render the ICBM first stage unrecoverable to where normal elimination procedures cannot be performed (e.g. explosion)
LOCAL PROCEDURES:

AF FORM 3941, AUG 95 (Microsoft Word) STARS FORMAT INSTRUCTIONS--B
Figure 5.4. Unclassified Format 4.

SUBJECT: NOTIFICATION OF CHANGE IN DATA IN THE MEMORANDUM OF UNDERSTANDING, DUE TO ACCIDENTAL LOSS OF A TREATY ACCOUNTABLE ITEM

1. ANC/STR /4

2. REFERENCE(S):

3. CONTENT:

SERIAL NUMBER OF TAI:

A) MOU DATA CHANGE:

1) TYPE, CATEGORY (AND VARIANT, VERSION IF APPLICABLE) OF ITEMS:

2) NUMBER OF ITEMS: 1

3) UNIQUE IDENTIFIER FOR ICBM FOR MOBILE LAUNCHER OF ICBMS:

A) __ __ __ __ __ __ __

4) LOCATION:

__ __ - __ __ __, __ __ __ - __ __ __

5) DATE OF LOSS: __ __ - __ __ __ - __ __ __ __

6) LOSS LOCATION:

__ __ - __ __ __, __ __ __ - __ __ __

7) CIRCUMSTANCES RELATED TO LOSS:

4. REMARKS:

5. END OF ANC/STR /4

Figure 5.5. Format 5 Instructions.

SUBJECT: NOTIFICATION OF CHANGE IN DATA IN THE MEMORANDUM OF UNDERSTANDING, DUE TO DISABLEMENT BEYOND REPAIR OF A TREATY ACCOUNTABLE ITEM		FORMAT: 5
TREATY REF: Notification Protocol, Section I, para 3b	WHO SUBMITS: Assigned base or Hill AFB for an ICBM first stage in transit
DESCRIPTION: Notification that a treaty accountable item has been disabled beyond repair.
UNIT SUSPENSE: No later than 24 hours after event	NRRC SUSPENSE: No later than 5 days after event
REPORT INCLUDES: SERIAL NUMBER OF TAI. Report the serial number of the Treaty Accountable Item. Examples: Silo launcher of ICBMs, (ICAO and site designator); KMIBA02; an ICBM (Minuteman II, III, or Peacekeeper) 13774; a heavy bomber, (B-52, B-1 or B-2) 580166. A) MOU Data Change. 1) TYPE, CATEGORY (AND VARIANT OR VERSION IF APPLICABLE) OF ITEMS. Examples: B-52G with LRNA or MM III For Silo Launcher. 2) NUMBER OF ITEMS. Will always be reported as 1. 3) UNIQUE IDENTIFIER FOR ICBM FOR MOBILE LAUNCHER OF ICBMS. Report the serial number for Peacekeeper only. Example: 0000116 4) LOCATION. Report the assigned location of the item. The Central Node will include the geographic coordinates in degrees, minutes and direction. Example: Malmstrom Air Force Base, Montana. 51-00N, 173-59W. 5) DATE OF CHANGE. Report the day, month and year of change. Example: 12-Oct-1999. 6) CIRCUMSTANCES RELATED TO DISABLEMENT. Report the circumstances of the disablement
ADDITIONAL INFORMATION: 1. Disablement beyond repair must damage the ICBM first stage to a degree where the normal repair procedures would not be practical, but the ICBM first stage is, in principle, recoverable in the sense that the normal elimination procedures could be carried out.
ADDITIONAL EXPECTED REPORTS: Before: None After: Format 54, 57*, 59*, 61*, 64*, 3*. * - sometimes, based on the TAI to be eliminated. Refer to the Notification Sequence charts.
LOCAL PROCEDURES:
ADDITIONAL REPORTS REQUIRED

AF FORM 3942, AUG 95 (Microsoft Word) STARS FORMAT INSTRUCTIONS--C

Figure 5.6. Unclassified Format 5.

SUBJECT: NOTIFICATION OF CHANGE IN DATA IN THE MEMORANDUM OF UNDERSTANDING, DUE TO DISABLEMENT BEYOND REPAIR OF A TREATY ACCOUNTABLE ITEM

1. ANC/STR /5

2. REFERENCE(S):

3. CONTENT:

SERIAL NUMBER OF TAI:

A) MOU DATA CHANGE:

1) TYPE, CATEGORY (AND VARIANT, VERSION IF APPLICABLE) OF ITEMS:

2) NUMBER OF ITEMS: 1

3) UNIQUE IDENTIFIER FOR ICBM FOR MOBILE LAUNCHER OF ICBMS:

A) __ __ __ __ __ __ __

4) LOCATION:

__ __ - __ __ __, __ __ __ - __ __ __

5) DATE OF CHANGE: __ __ - __ __ __ - __ __ __ __

6) CIRCUMSTANCES RELATED TO DISABLEMENT:

4. REMARKS:

5. END OF ANC/STR /5

Figure 5.7. Format 7 Instructions.

SUBJECT: NOTIFICATION OF CHANGE IN DATA IN THE MEMORANDUM OF UNDERSTANDING, WITH REGARD TO NEW FACILITIES, FACILITIES WHOSE CATEGORY HAS BEEN CHANGED, NEW KINDS OF SUPPORT EQUIPMENT, AND NEW TYPES, CATEGORIES, VARIANTS, AND VERSIONS OF TREATY ACCOUNTABLE ITEMS.		FORMAT: 7
TREATY REF: Notification Protocol, Section I, para 3d	WHO SUBMITS: HQ USAF/XOXI
DESCRIPTION: Contains information for new facilities, for new kinds of support equipment, and, as applicable, for new types, categories, variants and versions of TAIs.
UNIT SUSPENSE: No later than 24 hours after event	NRRC SUSPENSE: No later than 5 days after event
REPORT INCLUDES: SERIAL NUMBER OF TAI. Report the serial number of the Treaty Accountable Item. Example: Silo launcher of ICBM's (ICAO and site designator), KMIBA02; an ICBM, 13774, a heavy bomber, 580166. A) MOU Data Change. 1) TYPE, CATEGORY (AND VARIANT OR VERSION IF APPLICABLE) OF ITEMS. Example: B-2A. 2) NUMBER OF ITEMS. Will always be reported as 1. 3) UNIQUE IDENTIFIER FOR ICBM FOR MOBILE LAUNCHER OF ICBMS. Report the serial number for Peacekeeper only. Example: 0000116 4) LOCATION. Report the assigned location of the item. If the change is related to a specified facility include the geographic coordinates in degrees, minutes and direction. Example: Malmstrom Air Force Base, Montana. 51-00N, 173-59W. 5) DATE OF CHANGE. Report the date of the change in the MOU data to include day, month and year of the change. Example: 12-Oct-1999. 6) SITE DIAGRAM FOR NEW FACILITIES, AND PHOTOGRAPHS OF NEW KINDS OF SUPPORT AND EQUIPMENT AS APPLICABLE FOR NEW TYPES, CATEGORIES, VARIANTS, AND VERSION OF ITEMS WILL BE PROVIDED THROUGH DIPLOMATIC CHANNELS WITHIN 48 HOURS AFTER TRANSMISSION OF THIS NOTIFICATION.
ADDITIONAL INFORMATION: 1. If the new facility is not inspectable, submit a Format 3 in place of the Format 7. 2. The Format 16 will precede the Format 7 for the declaration of a new facility other than ICBM first stage production.
ADDITIONAL EXPECTED REPORTS: Before: Format 16* After: None * - Based on the situation (See Additional Information #2 above)
LOCAL PROCEDURES:
ADDITIONAL REPORTS REQUIRED

AF FORM 3942, AUG 95 (Microsoft Word) STARS FORMAT INSTRUCTIONS--C

Figure 5.8. Unclassified Format 7.

SUBJECT: NOTIFICATION OF CHANGE IN DATA IN THE MEMORANDUM OF UNDERSTANDING, WITH REGARD TO NEW FACILITIES, NEW KINDS OF SUPPORT EQUIPMENT, AND NEW TYPES, CATEGORIES, VARIANTS, AND VERSIONS OF TREATY ACCOUNTABLE ITEMS

1. ANC/STR /7

2. REFERENCE(S):

3. CONTENT:

SERIAL NUMBER OF TAI:

A) MOU DATA CHANGE:

1) TYPE, CATEGORY (AND VARIANT, VERSION IF APPLICABLE) OF ITEMS:

2) NUMBER OF ITEMS (IF APPLICABLE): 1

3) UNIQUE IDENTIFIER FOR ICBM FOR MOBILE LAUNCHER OF ICBMS:

A) __ __ __ __ __ __ __

4) LOCATION:

__ __ - __ __ __, __ __ __ - __ __ __

5) DATE OF CHANGE: __ __ - __ __ __ - __ __ __ __

6) SITE DIAGRAM FOR NEW FACILITIES, AND PHOTOGRAPHS OF NEW KINDS OF SUPPORT EQUIPMENT AND AS APPLICABLE FOR NEW TYPES, CATEGORIES, VARIANTS, AND VERSION OF ITEMS WILL BE PROVIDED THROUGH DIPLOMATIC CHANNELS WITHIN 48 HOURS AFTER THE TRANSMISSION OF THIS NOTIFICATION.

5. END OF ANC/STR /7