5.
Supplementary address
6.
Signal code
Omissions or invalid MILSTRIP codes in any of
these fields cause DAAS to reject the document. DAAS
sends a message back to the originator with a statement
outlining the reason for rejection. Rejections are
minimized by careful drafting and proof reading by
personnel at the originating activity.
PROCESSING.Requisitions coded in the above
format and submitted to DAAS are automatically
readdress to the activity in the routing identifier. When
the requisition cannot be filled by that activity, it is
passed to the inventory manager for action to fill it.
Supply status is provided to the requisitioner, the
supplementary
address
and
to
CINCLANTFLT
according to the M&S code used. All status messages
should come directly from the processing activity or
from DAAS. These status messages should contain a
subject line indicating that it concerns ammunition
requisition status.
Exception Requisitioning by Naval Message
Requisitions that are excluded from submission by
DAAS (mentioned earlier) are the only ones that can be
submitted by naval message. The requisition should be
submitted by using the Joint Message form. The
message should be sent for action to the supply source
indicated in the routing identifier of the MILSTRIP.
The message must be sent for information to
CINCLANTFLT and the activity that the material is to
be delivered.
A MILSTRIP requisition sent by naval message is
normally unclassified. Since none of the MILSTRIP
data elements contain classified information, the
classifying of ammunition requisitions is unnecessary.
If classified remarks are necessary, they must be
provided by a separate message.
REQUISITIONING BY FLEET UNITS
The units mission assignment and geographical
location
determine
the
requisitioning
procedures
followed by fleet units. Fleet units are composed of
cargo ships (AE/AOE/AOJ/AS), mission load ships
(CV/CVN/LPH/AD/AS), and aircraft squadrons. Since
the majority of Aviation Ordnancemen are assigned to
aircraft carriers or aircraft squadrons, the discussion
that follows concerning requisitioning procedures for
fleet units are limited to these two units.
Stock Levels
Ships are required to maintain 100 percent of their
shipfill ammunition allowance on board or on order.
One exception is that stock levels can be reduced to 90
percent to permit expenditures for training, or to carry
exercise ammunition. Individual waivers of this
requirement must be requested from the ship's
operational commander.
Requisitioning Channels
The requisitioning channels for use by fleet
activities are determined by the locality of the unit.
Ships and units located in CONUS or CONUS
operating areas should submit requisitions to DAAS.
Requisitions for the following materials must be in the
format previously discussed and submitted as follows:
Requisitions for 2E COG cartridge-actuated
devices
should
be
submitted
to
Naval
Ammunition Logistics Center, Mechanicsburg,
Pennsylvania.
Requisitions for 2E COG bombs and rockets
should be submitted to the naval weapons station
closest to the unit's homeport or to the weapons
station designated for the loadout.
Requisitions for 2T COG material should be
submitted to the naval weapons station closest to
the unit's homeport or to the weapons station
designated for the loadout.
Requisitions for 4T COG torpedo components
and ASROC components should be submitted to
Naval
Ammunition
Logistics
Center,
Mechanicsburg, Pennsylvania.
Requisitions for 6T COG material that should be
submitted to the Mine Warfare Engineering
Activity
(MINEWARENGACT),
Yorktown,
Virginia.
Requisitions for the following material must be
requisitioned by naval message in the format
previously discussed and submitted as follows:
Requisitions for 2E COG aircrews escape
propulsion system (AEPS) devices should be
submitted to Naval Ammunition Logistics
Center, Mechanicsburg, Pennsylvania.
Requisitions for all 8E COG air-launch missiles,
Harpoon missiles, Seasparrow missiles, and 8T
COG surface-launch missiles and complete-
17-12
