BY ORDER OF THE COMMANDER YOKOTA AIR BASE...

BY ORDER OF THE COMMANDER

YOKOTA AIR BASE

YOKOTA AIR BASE INSTRUCTION

10-202

21 SEPTEMBER 2017

Operations

YOKOTA AIR BASE RECALL

PROCEDURES

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: Publications and forms are available for downloading or ordering on the

e-Publishing website at www.e-Publishing.af.mil

RELEASABILITY: There are no releasability restrictions on this publication

OPR: 374 AW/CP

Supersedes: YOKOTA ABI 10-202,

7 February 2013

Certified by: 374 AW/CP

(Maj Justine T. Nardone)

Pages: 30

This instruction implements Air Force Policy Directive (AFPD) 10-2, Readiness, and describes

procedures used by Yokota Air Base (AB) to implement pyramid recalls. This instruction applies

to all agencies assigned to the 374 AW and partner units. This instruction requires collecting and

maintaining information protected by the Privacy Act of 1974 authorized by 10U.S.C. 8013,

Secretary of the Air Force and E.O. 9397 (SSN). System of records notice F033 AF C Locator,

Registration and Postal Directory Files (May 9, 2003, 68 FR 24944) applies. Ensure that all

records created as a result of processes prescribed in this publication are maintained in

accordance with (IAW) AFMAN 33-363, Management of Records, and disposed of IAW the Air

Force Records Disposition Schedule (RDS) located at: www.e-publishing.af.mil. Refer

recommended changes and questions about this publication to the Office of Primary

Responsibility (OPR) using the AF Form 847, Recommendation for Change of Publication; route

AF Forms 847 from the field through the appropriate functional chain of command.

SUMMARY OF CHANGES

This document has been substantially revised and must be completely reviewed. Major changes

include: Updated general information; changed Group Command Centers (GCCs) to Group

Subject Matter Experts (Group SMEs); clarified the role of Installation Personnel Readiness

(IPR); updated Pyramid Recall Procedures; updated 515 AMOG/730 AMS recall procedures;

updated types of recalls; updated responsibilities; updated WSA recall procedures, updated 374

AW Director of Staff responsibilities; changed recall roster submission timeline; added key

http://www.e-publishing.af.mil/

http://www.e-publishing.af.mil/

2 YOKOTAABI10-202 21 SEPTEMBER 2017

personnel and on-call roster section; added INWS section; updated Figure A4.2; added Figure

A4.3; added Attachment 6; updated references.

1. General Procedures and Terminology. ................................................................... 3

2. Recall Types/Options. ............................................................................................. 4

3. Pyramid Recall System Execution. ......................................................................... 7

4. Responsibilities ....................................................................................................... 9

5. Recall Roster Maintenance / Responsibilities. ........................................................ 13

6. Key Personnel Status/On-Call Rosters / Aircrew Accountability........................... 15

7. Installation Notification & Warning System (INWS)/Mass Notifications. ............ 16

Attachment 1— GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION 18

Attachment 2— RECALL STATUS REPORTS 20

Attachment 3— PARTNER UNIT NOTIFICATION LIST (WHEN DIRECTED BY 374

AW/CC) 22

Attachment 4— PYRAMID RECALL ROSTER FORMAT EXAMPLE 25

Attachment 5— PYRAMID RECALL PROCEDURE BASELINE 29

Attachment 6— EXAMPLE ON-CALL / STANDBY LETTER 30

YOKOTAABI10-202 21 SEPTEMBER 2017 3

1. General Procedures and Terminology.

1.1. The purpose of a base-wide recall or mass notification is to provide timely notification

and/or information to all Wing and Partner (Tenant) units and/or to recall personnel to duty.

This is accomplished using the Pyramid Recall System (PRS). The type of information

passed using these procedures includes, but is not limited to: establishing accountability,

disseminating critical information, threat to the installation, host-nation/US emergency,

natural disaster, severe weather alerts, changes in Defense Readiness Condition

(DEFCON)/Force Protection Condition (FPCON)/Typhoon Conditions (TCCOR), major

accidents; or other time-sensitive information requiring broad dissemination.

1.2. The primary means of base-wide recalls/notifications is the Pyramid Recall

System . Enhanced notification tools such as AtHoc, Microsoft Lync, and other mass

messaging systems are all tools to augment the Pyramid Recall System. These tools will not

replace Pyramid Recalls. If a member receives an AtHoc or other type of mass notification

message, do not assume other people have been notified. Proceed with Pyramid Recall

procedures. It is each member’s responsibility to ensure the next person in the chain has been

notified.

1.3. The term “partner unit” refers to all tenant military and civilian organizations located on

or assigned to Yokota AB that are not under the 374th Airlift Wing.

1.4. The 374 AW/CP also acts as the 5th Air Force Command Center and Air Mobility

Command Center (AMCC) for Yokota Air Base.

1.5. The 374th Airlift Wing Commander (374 AW/CC) or designated representative is the

authority for ordering base wide recall/notification procedures. The 374th Airlift Wing

Command Post (374 AW/CP) will initiate all base-wide notifications/recalls. Flexibility

exists to accommodate varying levels of personnel recalled. Partner units’ inclusion in

recalls will be at the discretion of the 374 AW/CC or designated representative.

1.6. Pyramid Recall System (PRS) . Each group, unit/squadron, and partner organization

is responsible for developing and maintaining a plan to contact all assigned unit personnel; as

well as providing a method to be contacted by the 374 AW/CP during duty and non-duty

hours.

1.6.1. The primary means of recalling personnel is the Pyramid Recall System (PRS).

Units must develop and maintain current Pyramid Recall Rosters (PRRs) to facilitate

immediate recall of personnel, both overtly and covertly, whether or not electronic

communications are available.

1.7. Overt Recall Procedures: Use all means available to recall personnel to include use of

Giant Voice, telephones, radios, speaker-equipped vehicles, mass notification systems such

as AtHoc, etc.

1.8. Covert Recall Procedures: Use only telephone, encrypted radio or personal contact to

recall base personnel. Do not use Giant Voice, unencrypted radios, AtHoc, speaker equipped

vehicles, etc.

1.9. Crisis Action Team (CAT). The CAT will be activated by the 374 AW/CC or

designated representative IAW YABI 10-203 Yokota Crisis Action Team (CAT) Operations.


1.10. Emergency Operations Center (EOC). The EOC is activated by the 374 AW/CC or

designated representative. This may be delegated to the 374 MSG/CC IAW YABI 10-2

Yokota AB Installation Emergency Management Plan.

1.11. Comm-in. This means telephone systems are in working order and that no security

concerns exist. This is the primary means of conducting recalls/notifications. See Paragraph

3.5.1 for further information and procedures.

1.12. Comm-out. This means either the telephone systems are inoperative due to damaged

communication infrastructure or when a comm-in recall would cause security concerns. See

Paragraph 3.5.2. for further information and procedures.

1.13. To facilitate effective communications when the CAT/EOC is activated, or when

partner unit notifications/accountability must be maintained and tracked, the 374 AW will

use the Group Subject Matter Experts (SMEs)/UCC system. Group SMEs represent each

Group in the CAT facility. They are the conduit for information passed to, or received from,

their respective squadrons/units. They will primarily communicate with unit/squadron Unit

Control Centers (UCCs), to pass command directives. The Group SMEs also contact and

take accountability for select partner units, when required. When the CAT CORE Team is

convened, each group from the 374th Airlift Wing will send the Group SME to the primary

or alternate CAT location. Unit representation from the 730th AMS and 515th AMOG will

be present if the recall specified their presence.

1.14. Unit Control Centers (UCC). UCCs establish communication with Group SMEs when

the CAT is activated. They provide the means for squadron/unit commanders to pass and

receive information to/from Senior Leadership and the CAT Staff. Whenever the CAT

activates with Group SMEs, UCCs will also activate. EXCEPTION: When Group SMEs are

activated to conduct partner unit accountability, UCCs may not need to stand up. The 374

AW/CC will be directive.

2. Recall Types/Options.

2.1. Recall Overview. The recall process is initiated by the 374 AW/CP when directed by

the 374 AW/CC or designated representative. The 374 AW/CC or designated representative

will determine which recall to initiate depending on the situation, or as directed by higher

headquarters.

2.1.1. The R-hour is the reference time determined by the 374 AW/CC to initiate a

recall/notification. The Q-hour is the time that mobility operations will start in

preparation for a deployment and will be determined by the 374 AW/CC or HHQs (if

applicable). Since accountability reports are due based upon the R-hour, this time will be

relayed to members of the CAT/Group SMEs/UCCs (if activated). Q-hour may be

relayed for mobility recalls if known/determined at the time of the recall.

2.1.2. When directed by the 374 AW/CC, the 374 AW/CP will contact the 374 AW/CV,

374 AW/CCC, 374 AW/DS, 374 AW/XP, and Group Commanders. If directed, the CP

will also contact the 515 AMOG/CC, who will in turn, contact the 730 AMS/CC.

2.1.3. The Group CCs initiate their organization’s PRS. The 730 AMS/CC and the 515

AMOG/CC will initiate their units’ PRS.


2.1.4. If the applicable recall activates the CAT, all Group Commanders, 374 AW/XP,

and 374 AW/DS will also follow the CAT activation instructions, to include notifying

their Group SME representative, in accordance with YABI 10-203 Yokota Crisis Action

Team (CAT) Operations.

2.1.5. The 374 AW/DS (Primary) or 374 CPTS/CC (Secondary) will notify Wing Staff

Agency Chiefs (XP and CP need not be notified as they have already been notified by

CP).

2.2. General Recall . This is used to bring members into their units/work stations. Units

and agencies initiate pyramid recall. CAT/EOC will not activate unless specified by the 374

AW/CC. Units do not contact aircrew members in pre-departure crew rest and air traffic

controllers in crew rest, unless this option is authorized by the 374 AW/CC or 374 OG/CC.

This will be specified in the recall message.

2.3. Mobility Recall . This is used for the deployment of forces. Accomplish all steps for a

General Recall, and consider activation of the “Full Staff” CAT (374 AW/CC will be

directive). Additionally, all mobility work centers will activate (Deployment Reception

Control Center (DRCC)/Processing line, etc.). After contacting their UCCs, personnel will

report to their mobility work centers as applicable.

2.4. Accountability Recall : This is used for Group SMEs and UCCs to report immediately

to their duty sections, activate their workstations and conduct a communications check.

Units and agencies will initiate their pyramid recall procedures. If 374 AW/CC directs,

Group SMEs may conduct accountability from a location other than the CAT facility.

Personnel will not report to their duty sections, unless specified otherwise by their chain of

command. Units do not contact aircrew members in pre-departure crew rest and air traffic

controllers in crew rest, unless otherwise specified. Group SMEs will contact their assigned

Partner Units (see Attachment 3) and have them initiate their PRS, if required. Group SMEs

will be responsible for tracking accountability status for their units and assigned partner

units. Each unit will report to their Group SME on an hourly basis the percentage of

members contacted until 100% completion, as specified in paragraph 3.3.4. and Attachment

2.

2.4.1. The CAT Director and/or 374 AW/CP in coordination with the Installation

Personnel Readiness (IPR) office, will be the focal point to collect/monitor recall

information and make applicable reports to the 374 AW/CC. See Paragraph 3.3.4 and

Attachment 2.

2.5. Information Recall .

2.5.1. Announcement . The information recall is used if the 374 AW/CC or designated

representative only wants to push a message without a feedback loop. Examples include:

base lockdown, shelter-in-place, or other situation where the CAT cannot physically

convene. This could also be used for important announcements such as facility closures

due to forecast inclement weather, etc. The 374 AW/CC or designated representative

determines if Group SMEs/UCCs will be activated, or if mass notification methods can

be used instead.


2.5.2. Shelter-In-Place. The purpose of this notification is to protect the base population

from fire, explosive hazards, falling objects, and inhalation hazards. The 374 AW/CC

will direct the 374 AW/CP to send out Installation Notification and Warning System

(INWS) messages, to include Giant Voice and other mass notification systems (AtHoc,

etc.). An Accountability Recall is recommended following “All Clear.”

2.5.2.1. Personnel will execute Shelter-In-Place procedures IAW YABI 10-2 Yokota

AB Installation Emergency Management Plan and Airman’s Manual.

2.5.3. Lockdown. This is used when an Active Shooter or violent incident takes place or

the threat of a violent event exists, which requires all personnel to take quick action to

save lives. An Accountability Recall is recommended following “All Clear.”

2.5.3.1. Any unit initiating lockdown procedures in reaction to an Active Shooter

will notify the 374 AW/CP immediately.

2.5.3.2. Refer to your unit’s lockdown procedures, in addition to YABI 10-2 Yokota

AB Installation Emergency Management Plan and Airman’s Manual for individual

Lockdown/Active Shooter actions.

2.5.4. Inquiry . This will be used when the Wing Commander desires an

acknowledgement from each unit in the Wing/Base, confirming receipt of the message.

2.5.4.1. If partner units require notification, consider activation of Group SMEs in

order to facilitate timely notifications/accountability due to Group SMEs being

responsible for maintaining 24 hour POC contact information.

2.6. Crisis Action Team (CAT) Recall : Follow CAT activation guidance in Yokota ABI

10-203. The 374 AW/CC or designated representative is the authority to activate the CAT.

The 374 AW/CC will specify a Level 2, 3 or 4 CAT in the recall order. Any caveats or

changes to the above will be specified in the recall message. This option can be stand alone

or combined with another recall option.

2.7. Emergency Operations Center (EOC) Recall : Follow EOC Activation guidance in

YABI 10-2 Yokota AB Installation Emergency Management Plan. Generally the EOC will

be activated in response to an emergency, usually after the Incident Commander (IC)

determines that the emergency can no longer be handled unless the EOC is activated. This

option can be stand alone, or combined with another recall option.

2.8. Threat Working Group (TWG) Recall : This recall assembles members of the Wing

Commander’s Threat Working Group. This can be initiated by the 374 AW/CC or designated

representative or the Wing Anti-Terrorism Officer (ATO). 374 AW/CP will contact the

Wing Anti-Terrorism Officer, and in turn, he or she is responsible for contacting the

members of the Threat Working Group.

2.9. Telephone Standby . Personnel placed on telephone standby will remain in the

immediate vicinity (i.e., within hearing distance) of their telephone or carry a cell phone

while awaiting further instructions. They will be available for immediate recall and will

report for duty at their regularly scheduled time unless otherwise directed.


2.10. Additional Recall Options . These options allow the 374 AW/CC or designated

representative the ability to further tailor or augment recall options to the particular situation

requiring a recall. These may or may not be included in a recall message. These options may

be executed individually or in combination with one another.

2.10.1. Option 1 Activates the EOC.

2.10.2. Option 2 Activates the CAT. 374 AW/CC or designated representative will

specify the CAT Level.

2.10.3. Option 3 Directs personnel to report to their unit carrying their chemical gear and

IPE (bagged).

2.10.4. Option 4 Directs Commanders to disregard crew rest for aircrew and air traffic

controllers who are in crew rest.

2.10.5. Option 5 Initiates the security forces augmentation program. Security forces

augmentees will report to their UCCs for accountability and then proceed immediately to

Building 210.

2.10.6. Option 6 Eliminates the need to recall non-mission essential civilian personnel

(e.g., exercises, PRS test).

2.10.7. Option 7 Places personnel in Telephone Standby.

2.11. For pyramid recalls and tests of the pyramid notification system, civilians will be

contacted as directed by the declaring authority but will not be placed on standby or recalled

to duty without explicit direction of the wing, group or partner unit commander.

2.12. During a recall to duty, crew/shift workers should follow their current duty schedule

and remain on telephone standby unless otherwise directed.

3. Pyramid Recall System Execution.

3.1. Pyramid Recall System Execution . The 374 AW/CC or designated representative

will direct the 374 AW/CP to initiate the recall. The recall notification may add additional

measures commensurate with the situation.

3.1.1. In the event of a natural disaster, Higher Headquarters directed, and/or national

emergency recall, IPR will also send out an Air Force Personnel Accountability and

Assessment System (AFPASS) recall. This AFPASS recall can be sent in conjunction

with Pyramid Recall procedures.

3.2. The 374 AW/CP will contact the 374 AW/CV, 374 AW Group Commanders, 374

AW/XP, 374 AW/DS, and 515 AMOG (if required).

3.2.1. The 374 AW Group Commanders, and 515 AMOG (if required), will then contact

their respective executive staff and Squadron Commanders. Squadron Commanders will,

in turn, contact their unit’s members in accordance with their Pyramid Recall System.

3.2.2. The 374 AW/CP will contact any geographically separated units which do not fall

under the responsibility of 374 AW Group Commanders; but which are still

administratively associated with Yokota AB due to MOU, MOA, etc.


3.2.3. The 374 AW/DS (Primary) or 374 CPTS/CC (Secondary) will contact the WSA

Chiefs (Except XP and CP, as they are contacted directly by the 374 AW/CP), 374

CPTS/CC, and wing front office personnel.

3.3. To facilitate effective communications when the CAT/EOC is activated or partner unit

notifications/accountability must be maintained and tracked, the 374 AW uses the Group

SME/UCC system.

3.3.1. Each group will have individuals identified to serve as their respective Group

SME, who reports to their respective Group Commander. Wing Staff Agencies (WSA)

will have a Group SME responsible to the 374 AW/DS (Primary) or 374 CPTS/CC

(Secondary).

3.3.2. Each squadron (or unit/agency) within those groups will ensure all UCC

responsibilities are fulfilled. The exceptions are the 374th Medical Group (374 MDG)

which will only operate one UCC due to its size and nature of operation.

3.3.3. Final control to deactivate the specific Group SMEs or UCC remains with the

Wing Commander or designated representative.

3.3.4. Group SMEs and UCCs will report and track personnel strength and accountability

as directed by the CAT Director (if activated) or 374 AW/CC utilizing Unit Level Unit

Virtual Operation Center (VOC), Excel, SharePoint, voice report, or other available

means. See Attachment 2 for required information to update the recall tracker. Personnel

strength reporting begins at R-Hour plus 1 and continues every hour thereafter until all

units have attained 100% personnel accountability. The 374 AW/CC’s goal is 100%

contact of all accountable personnel by R-hour plus 3. The Installation Personnel

Readiness (IPR) office, in coordination with the CAT Director and/or 374 AW/CP, will

be the focal point to collect/monitor recall information and make applicable reports to the

374 AW/CC. IPR will forward AFPAAS recall status reports to Higher Headquarters,

when directed by Higher Headquarters guidance and as requested by 374 AW/CC. If IPR

is directed to track recall status, all Group SMEs will collect the data for their respective

units and forward the information to them at DSN 225-8519/9518 or via email at NIPR:

[email protected] or SIPR: [email protected]. NOTE:

Personnel in crew rest will be considered accounted for, unless directed to be recalled.

3.3.4.1. Group SMEs and/or UCCs will establish accountability procedures for

dependents when their sponsor is TDY or on leave if required (natural emergencies,

regional accountabilities etc.).

3.4. Use the following verbiage during all recalls:

3.4.1. “This is (Rank/Name) from the Yokota Command Post. (XXXX) recall is in

effect. Option(s) (1, 2, 3, etc.) applies (if required). R-hour is (if required) (Add any

additional information or instructions as given by the 374 AW/CC or designated

representative).”

3.4.1.1. The 374 AW/CC has the option to pass additional information at the end of

the verbiage if deemed necessary. In order to ensure the message is relayed as

accurately as possible, it is highly encouraged that members write down the

notification message and relay it word-by-word.

mailto:[email protected]



3.4.2. If directed by the 374 AW/CC or designated representative, the 374 AW/CP will

begin recall/information announcements on the Giant Voice System at appropriate

intervals until the CAT or wing leadership determines the wing has reached a mission-

capable status.

3.5. The pyramid recall system may be implemented using either Comm-in or Comm-out

procedures.

3.5.1. Comm-in Recalls. The primary method to notify personnel is by telephone. If an

individual cannot be reached within two hours after recall start time, the unit should send

a runner to the member’s residence.

3.5.1.1. If unable to contact the next individual on the roster within 5 minutes,

contact the individual or individuals below that person in the PRR. Continue

attempting contact with that person until instructed otherwise by your

Commander/Group SME/UCC (consider dispatching a runner). The names of all

individuals not contacted should be passed to your Commander/Group SME/UCC as

soon as possible.

3.5.2. Comm-out Recalls. Under comm-out conditions, there may not be the ability to

initiate a voice recall, or the nature of the threat requires a higher level of security.

During comm-out recalls, the primary method to initiate a recall is by dispatching pre-

assigned runners during duty and non-duty hours to the BDOC.

3.5.2.1. The 374 AW/CC or designated representative will inform the 374 AW/CP

that he/she wishes to initiate a comm-out recall. Or, the 374 AW/CP will dispatch a

runner to the BDOC in order to send a patrolman to the 374 AW/CC to inform

him/her of a situation that may require a recall. The BDOC in turn will dispatch

patrolman to the 374 AW/CC/CV and/or 374 AW Group Commanders or Deputies

quarters and/or office.

3.5.2.2. If the comm-out recall includes an order to activate the CAT and/or EOC,

units will send runners to the CAT to receive further instructions (Yokota Command

Directives). The control center structure will be established using runners in place of

fax, email and telephone systems.

4. Responsibilities

4.1. The 374 AW/CC or designated representative:

4.1.1. Will direct the 374 AW/CP to initiate all recalls for Yokota AB.

4.1.2. Direct Crisis Action Team (CAT) and/or Emergency Operations Center (EOC)

activation.

4.1.3. Permit Group SMEs and UCCs to execute recall of their assigned group and unit

personnel from other than CAT/Squadron facilities, if necessary.

4.1.4. Direct/authorize use of the INWS (Giant Voice, enterprise mass notification

systems such as AtHoc, etc.) targeted to the entire base populace.

4.2. 374th Airlift Wing Command Post (374 AW/CP) will:

4.2.1. Initiate recalls when directed by the 374 AW/CC or designated representative.


4.2.2. Immediately notify the Installation Personnel Readiness (IPR, 374 FSS/FSOXI)

office or stand-by personnel in the event of a recall.

4.2.3. Notify 374th Security Forces Squadron Base Defense Operations Center (374

SFS/BDOC) in the event of a comm-out or covert recall.

4.2.4. When the CAT is activated and the situation requires, notify and request a Security

Forces sentry.

4.2.5. Notify 374 AW Group Commanders

4.2.5.1. If the 374 AW/CP is unsuccessful contacting a commander, they will contact

a deputy commander and/or an executive officer, and that commander will be

considered notified by the CP. It is the responsibility of the notified member to

contact his/her respective commander and Group SMEs, if necessary.

4.2.6. Activate the Installation Notification Warning Systems (INWS)

4.2.6.1. INWS includes the Giant Voice and enterprise mass notification systems

such as AtHoc.

4.2.7. Obtain and file current recall rosters of all 374 AW, 5th AF, and partner units

assigned or attached to Yokota AB, by working with Group/Squadron/Unit Pyramid

Recall Roster Monitors. Recall rosters will be sent to the 374 AW/CP on the first duty

day of each month.

4.2.8. Maintain procedures to initiate the PRS.

4.2.9. Execute command center activations and recalls of personnel and agencies when

directed by the appropriate authority.

4.2.10. Initiate periodic tests of the PRS when directed. Tests will consist of telephonic

contact of CAT/EOC members and/or selected units to determine their ability to perform

control center activations and pyramid recall actions.

4.2.11. Initiate 5th Air Force recalls if directed by 5 AF/CC or delegated representative.

This includes individual staff directorates as required if directed by 5 AF Chief of Staff or

other delegated representative.

4.3. 374th Airlift Wing Director of Staff (Primary) and/or 374th Comptroller Commander

(Secondary) will:

4.3.1. Ensure Wing Staff Agency (WSA) chiefs develop, maintain, and publish PRRs

and comm-out procedures.

4.3.2. Contact WSA Chiefs during recalls.

4.3.3. Identify mission essential military personnel on the unit’s recall roster.

4.3.4. Initiate pyramid recall of WSA assigned Active Duty, GS civilians, contractors,

local national members and their dependents, when directed.

4.3.5. Notify the WSA Group SME representative when the Full Staff CAT is activated.

4.4. 374th Airlift Wing Group Commanders will:

4.4.1. Develop, maintain, and publish PRRs and comm-out procedures for their staffs.


4.4.2. Ensure subordinate commanders develop, maintain, and publish PRRs and comm-

out procedures.


4.4.4. Identify mission-essential civilians needed to operate the base and its mission

essential services and annotating these individuals on the unit’s recall roster.

4.4.5. When directed, recall their groups to include Active Duty, GS civilians,

contractors, local national members and their dependents.

4.4.6. If not directed by 374 AW/CC or designated representative, determine whether

civilian, contractor, assigned reserve personnel and shift workers will be

notified/recalled.

4.4.7. For CAT Activations, recall applicable agency representatives as required.

4.4.8. Ensure Group SMEs are selected and appropriately trained and qualified

personnel.

4.4.8.1. Ensure Group SMEs (primary and secondary) are appointed in writing, and

trained by the 374 AW/XP.

4.4.8.2. Commanders will ensure that if the primary Group SME member is

unavailable, the secondary is ready to assume Group SME responsibilities.

4.4.9. Notify their respective Group SME personnel during Full Staff CAT activation.

4.4.10. Initiate internal (Group Only) recalls as necessary.

4.4.10.1. If the capability exists, the Group Commander may utilize enterprise mass

notification systems (such as AtHoc, etc.) to accomplish an internal group recall.

4.4.11. If issued, Commanders will carry a government issued duty cell phone at all

times. If not issued a duty cell phone, they will ensure they are able to be contacted

during off-duty hours or ensure a good hand-off with their deputy.

4.5. 374 AW Squadron/ Unit Commanders will:

4.5.1. Develop, maintain, and publish PRRs and comm-out procedures for their

organization and staffs.


4.5.3. Identify mission-essential civilians needed to operate their mission essential

functions and include these individuals on the unit’s recall roster.

4.5.4. When directed, recall their groups to include Active Duty, GS civilians,

contractors, local national members and their dependents, as required.

4.5.5. If not directed by declaring authority, determine whether civilian, contractor,

assigned reserve personnel and shift workers will be notified/recalled.

4.5.6. For CAT Activations, recall applicable UCC personnel, as required.

4.5.7. Ensure a UCC is established and manned with appropriately trained and qualified

personnel.


4.5.8. Initiate internal (Squadron/Unit Only) recalls as necessary.

4.5.8.1. If the capability exists, the Squadron/Unit Commander may utilize enterprise

mass notification systems (such as AtHoc, etc.) to accomplish an internal

Squadron/Unit recall.

4.5.9. Inform the 374 AW/CP if you will be unable to perform duties due to absence or

other circumstance, and ensure the 374 AW/CP has the name and 24-hour contact

information of who will be acting on your behalf (Deputy, etc.).

4.5.10. If issued, Commanders will carry a government issued duty cell phone at all

times. If not issued a duty cell phone, they will ensure they are able to be contacted

during off-duty hours or ensure a good hand-off with their deputy.

4.6. 374th Force Support Squadron (374 FSS/Director) will:

4.6.1. Installation Personnel Readiness (IPR):

4.6.1.1. The 374 IPR will be manned within 1 hour of recall start time (RST) in order

to compile the Wing’s recall data.

4.6.1.2. Report Wing recall status/accountability to the 374 AW/CC every hour

through the Crisis Action Team (CAT) or through the 374 AW/CP if the CAT is not

activated.

4.7. 374th Security Forces Squadron (374 SFS) will:

4.7.1. Dispatch patrols to notify key senior leadership to enable a comm-out recall, if

necessary.

4.7.2. Dispatch an armed Entry Control guard (Sentry) to control entry to the CAT when

necessary or directed by the 374 AW/CC. The Sentry will report to the Command Post

and will receive an Entry Authorization List (EAL) and special security instructions prior

to assuming entry control duties IAW AFI 10-207_PACAFSUP.

4.8. Group SMEs will:

4.8.1. Ensure unit pyramid notification/recall procedures are executable when

communications are inoperable or impaired. Work with Commanders to ensure comm-

out procedures are as efficient as possible and personnel are familiar with the procedures.

4.8.2. Establish communications with their respective UCCs as soon as possible.

4.8.3. Establish contact with their respective list of partner units for accountability

purposes (Attachment 3).

4.8.4. Ensure strength reporting procedures are established and consistent with each

subordinate squadron and partner unit.

4.8.5. Notify IPR of group recall percentage at DSN 225-8519/9518 or via email at

NIPR: [email protected] or SIPR: [email protected].

4.8.5.1. Report recall status at RST+1 and continue to report every hour until the

entire group and/or assigned partner units have attained 100% accountability, if

required/applicable.




4.9. Unit Control Center (UCC) will:

4.9.1. Ensure unit pyramid notification/recall procedures are executable when

communications are inoperable or impaired. Work with Squadron/Unit Commander to

ensure comm-out procedures are as efficient as possible and personnel are familiar with

the procedures.

4.9.2. Ensure strength reporting procedures are established and consistent with each

subordinate squadron and partner unit.

4.9.3. Notify respective Group SME of squadron/unit recall percentage hourly or as

requested by Group SME.

5. Recall Roster Maintenance / Responsibilities.

5.1. Each Group Commander will:

5.1.1. Appoint a primary and alternate Pyramid Recall Monitor (PRM). It is

recommended that these individuals be the same members that make up their respective

Group SMEs. PRMs will:

5.1.1.1. Maintain copies of all Squadron recall rosters. Provide recall rosters to the

374 AW/CP and their responsible Group SME on the first duty day of each month.

Even if there are no changes, send the recall roster with the new month’s date.

5.1.1.2. Maintain up to date 24-hour point of contact information for the partner units

that their Group SME is responsible for during recalls/notifications (IAW Attachment

3). Provide a copy to the 374th AW/CP on the first duty day of each month.

5.1.1.3. Prepare and maintain pyramid recall rosters (IAW Attachment 4).

5.1.1.4. Develop and maintain comm-out recall procedures and maps. These maps

will include the building and/or room number of all members’ residences/dorms in

their PRR. Units will maintain detailed maps of all members who reside off-base to

include written driving directions from one of the gates.

5.1.1.5. Assign runners who are familiar with the comm-out routes.

5.2. Each Squadron/Unit Commander (to include Partner Units) will:

5.2.1. Appoint a primary and alternate Pyramid Recall Monitor (PRM). It is

recommended that these individuals be the same members that make up their respective

UCC. PRMs will:

5.2.1.1. Maintain copies of all Squadron Recall Rosters. Provide recall rosters to the

374 AW/CP and their responsible Group SME on the first duty day of each month.

Even if there are no changes, send the recall roster with the new month’s date.

5.2.1.2. Develop and maintain comm-out recall procedures and maps. These maps

will include the building and/or room number of all members’ residences/dorms in

their PRR. Units will maintain detailed maps of all members who reside off-base to

include written driving directions from one of the gates.

5.2.1.3. Assign runners who are familiar with the comm-out routes.


5.2.1.4. Ensure the Squadron/Unit Commander (or equivalent) is able to be reached

at any time due to events that may happen outside of duty hours. If this person is on

leave/TDY, they will inform the 374 AW/CP who the acting Commander is to ensure

positive communication during a recall.

5.3. 5 AF Command Center (374 AW/CP) will coordinate with 5 AF Chief of Staff (5

AF/CoS) to:

5.3.1. Provide the 374 AW/CP (which also acts as the 5 AF Command Center) accurate

and up to date recall rosters for the various A-Staff personnel, to include 24-hour contact

information by the first duty day of each month.

5.3.2. Assist the 374 AW/CP with maintaining accurate Key Personnel information for 5

AF/CC, 5 AF/CV, and executive officers/aide-de-camps.

5.4. Prepare and maintain pyramid recall rosters using the sample in Attachment 4, Figure

A4.1, Figure A4.2, Figure A4.3, and the following guidelines:

5.4.1. PRRs must contain, as a minimum: current as of date, a header which identifies

the organization, the recall roster monitor’s name, duty position and office phone

number, the unit members’ name, grade, residence address, residence telephone number,

cell phone number (if applicable), a Privacy Act statement, the statement “For Official

Use Only,” Personnel Accounting System (PAS) code for the unit (Note: if members

under different PAS codes are on your unit’s roster, include their PAS code in the section

with the member’s name), and have the information contained in Figure A4.2. as the last

page of the PRR (see Attachment 4). PRRs must also identify personnel housing

locations next to the address element using the following abbreviations in parentheses:

dorms (D), East housing (E), South housing (S), North housing (N), off-base housing (O),

and West housing (W). Units are authorized to add additional information as needed.

5.4.2. PRRs will also include the DSN telephone numbers for the unit’s primary and

alternate UCC members and Group SMEs. Emergency telephone numbers are also

highly encouraged. See Figure A4.1 for more guidance.

5.4.3. It is mandatory for all rosters to have the AFPAAS website and phone number

annotated. This is required IAW AFI 36-3803, Personnel Accountability in Conjunction

with Natural Disasters or National Emergencies.

5.4.3.1. Refer to the most current copy of the above regulation for the current

telephone and website information.

5.4.4. It is mandatory for all rosters to have Personnel Accounting System (PAS) codes

to account for and report by individual unit. This is required IAW AFPD 36-38,

Personnel Readiness, Reporting and Accountability.

5.4.5. It is mandatory to have Figure A4.2 as the last page of all PRRs. This figure is

maintained by the 374 AW/CP.

5.4.6. It is recommended that each unit test their pyramid recall at least once each

quarter. Wing exercise recalls suffice for this recommendation. If the capability exists,

units may coordinate with the appropriate UCC/Group SME to initiate a notification

utilizing an enterprise notification system (AtHoc, etc.) for their group or squadron, as

necessary.


5.5. All military and civilian personnel will:

5.5.1. Inform their unit PRR monitor and immediate supervisor of address and/or

telephone number changes, to include providing a new or updated map to their quarters

as soon as the change occurs.

5.5.2. Individuals residing off-base will provide the PRR monitor and supervisor or

person responsible for contacting them, a detailed map of the area in which they reside

using well known streets or land marks as a guide. Each map will include written

instructions from one of the gates to the individual’s quarters.

5.5.3. Dispose of obsolete rosters in such a manner as to prevent the unauthorized release

of personal information (shredding, burning etc.).

5.6. The 374 AW/CP will:

5.6.1. File current recall rosters of all 374 AW, 5th AF, and partner units assigned or

attached to Yokota AB, provided by unit’s PRR monitor.

5.6.1.1. The 374 AW/CP will track unit’s compliance in updating & maintaining

their recall rosters in accordance with the directives stated in this instruction. The

374 AW/CP will notify the IPR office, 374 AW/DS, and 374 AW/CC of all units not

in compliance.

5.6.1.2. The 374 AW/CP will maintain up-to-date e-mail distribution lists for Partner

Units and update IPR of any changes.

5.6.2. Maintain procedures to initiate the PRS.

5.6.3. Initiate periodic tests of the PRS when directed. Tests will consist of telephonic

contact of CAT/EOC members and/or selected units to determine their ability to perform

control center activations and pyramid recall actions.

6. Key Personnel Status/On-Call Rosters / Aircrew Accountability.

6.1. Per AFI 10-205 PACAF Supplement, all PACAF, NAF, and Wing Commanders or their

designated representative must be telephonically available within 15 minutes of the Air Force

Service Watch Cell’s (AFSWC) initial attempt (through the Pacific Command Center) to

contact.

6.1.1. If 5AF/USFJ Commander or Vices, or 374 AW Commander or Vice will be

unavailable, they or their designated representative will inform the 374 AW/CP. The 374

AW/CP will maintain key leader location and availability situational awareness at all

times.

6.2. The 374 AW/CP will maintain a key personnel list, to include duty and personal

telephone contact information, as well as applicable executive officers and/or aide-de-camps,

for the following:

6.2.1. 5 AF/CC, 5AF/CV, 5AF/CoS, USFJ/CC, USFJ/CV, 374 AW/CC, 374 AW/CV,

All 374 AW Group Commanders and deputies, 515 AMOG/CC, 515 AMOG/CD, 730

AMS/CC, 730 AMS/DO.

6.2.2. The 374 AW/CP will work with the above offices/staffs to ensure changes in

status are annotated and briefed.


6.3. All 374 AW Squadrons/Units will provide the 374 AW/CP with the name and contact

information of their Commander, Deputy, Superintendent, and First Sergeant.

6.3.1. This information may be included/annotated on their monthly recall roster

submission.

6.3.2. If a Commander will be unavailable (TDY, leave, deployment, etc.), they will

inform the 374 AW/CP and provide contact information for their unit’s designated

representative during the time of absence.

6.3.3. All unit commanders/chiefs will carry an official or personal cell phone with them

at all times to facilitate timely message notification in the event of a recall or other

emergency.

6.4. If unit guidance dictates, or units desire, they will provide the 374 AW/CP with an “on-

call” or “standby” roster for non-duty hours notifications. Refer to Attachment 6 for an

example standby letter.

6.5. Aircrew Recall / Accountability

6.5.1. 374 AW/OGV will ensure the 374 AW/CP has the most current Operations

Supervisor phone listing. The flying squadrons will ensure the 374 AW/CP has the name

and phone number of the duty/on-call Operations Supervisor if different from this listing.

6.5.2. Yokota AB Flying Squadrons will provide the 374 AW/CP a copy of crew orders

for local training/O&M sorties or any sortie where the full crew is not entered into

GDSS2. This will assist with personnel accountability during a recall or passing

FCIF/TCTO information for off-station non-TWCF crews.

6.5.3. 374 AW/CP will maintain a list of transient aircrew lodging locations and

applicable phone numbers, in case of emergency requiring notification or if transient

crew home-station emergencies require notification of personnel.

6.5.4. 374 AW/CP will coordinate with 374 FSS to develop notification procedures for

transient personnel residing in the Kanto Lodge/billeting facilities.

7. Installation Notification & Warning System (INWS)/Mass Notifications.

7.1. The INWS consists of the Giant Voice system, and any enterprise mass notification

system (such as AtHoc, etc.). These are tools that can be used to supplement and expedite

recalls. They are not a replacement for the Pyramid Recall System or the chain of command.

7.2. This is the Recall Instruction for Yokota Air Base. For detailed information about Giant

Voice messaging, sounds, testing, etc., refer to AFI 10-2501, Air Force Emergency

Management (EM) Program; YABI 10-2 Yokota AB Installation Emergency Management

Plan, and AFTTP 3-4, Airman’s Manual.

7.3. The INWS is activated by the 374 AW/CP.

7.3.1. INWS notifications will only be made with permission from the 374 AW/CC,

unless pre-coordinated conditions exist, per existing guidance.

7.4. Base-wide notifications via an INWS system will only be used for an actual emergency.

Exercise and/or test announcements will be clearly labeled as such. If appropriate, the 374

AW/CP will coordinate with 374 AW/PA to announce a test message ahead of time.


7.4.1. The INWS will not be used for routine message traffic/notifications.

7.5. “AtHoc” INWS.

7.5.1. As of the publishing of this instruction, PACAF has designated “AtHoc” as the

INWS that will augment mass notification capabilities. MAJCOM and Yokota Air Base

guidance and policy letters are maintained by the 374 AW/CP.

7.5.2. AtHoc Wing Installation Managers are designated by the 374 AW/CC as the 374

AW/CP and the 374 Communications Squadron.

7.5.3. 374 AW/CP initiates AtHoc notifications per current MAJCOM and 374 AW/CC

guidance.

7.5.4. Per PACAF Policy Letter, all military personnel will enter emergency notification

information into the AtHoc Alerts purple globe self-service module within 30 days of

assignment to their unit. Civilians and contractors are highly encouraged (but not

required to) enter their information into AtHoc.

KENNETH E. MOSS, Colonel, USAF

Commander


Attachment 1

GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION

References

AFPD 10-2, Readiness, 6 November 2012

AFI 10-205 PACAF Sup, Availability of Key HQ AF Personnel & Major Command

Commanders, 28 March 2013

AFI 10-2501, Air Force Emergency Management Program, 19 April 2016

AFI 36-3802, Personnel Readiness Operations, 23 February 2009

AFI 36-3803, Personnel Accountability in Conjunction with Natural Disasters or National

Emergencies, 7 June 2016

AFMAN 33-363, Management of Records, 1 March 2008

AFTTP 3-4, Airman’s Manual, 19 May 2015

DoD 5400.7-R, DoD Freedom of Information Act Program, 25 January 2017

Joint Federal Transportation Regulation (JFTR), Volume 1, Chapter 7

YABI 10-2, Yokota AB Installation Emergency Management Plan

YABI 10-203, Yokota Crisis Action Team (CAT) Operations, 9 May 2012

Adopted Forms

AF Form 847, Recommendation for Change of Publication

Abbreviations and acronyms

ABI—Air Base Instruction

AFN—American Forces Network

AFPAAS—Air Force Personnel Accountability and Assessment System

AFPD—Air Force Policy Directive

AtHoc——Computer based Installation and Notification Warning System (INWS). This system

sends text, email, telephone, and desktop notifications to registered users.

AW—Airlift Wing

Comm-in—Normal Communications

Comm-out—Communications Outage

CAT—Crisis Action Team

CP—Command Post

DRCC—Deployment Reception Control Center

EOC—Emergency Operations Center


FPCON—Force Protection Condition

HHQ—Higher Headquarters

IDO—Installation Deployment Officer

INWS—Installation Notification and Warning System

IPR—Installation Personnel Readiness

MOA—Memorandum of Agreement

MOU—Memorandum of Understanding

NEO—Noncombatant Evacuation Operation

PRR—Pyramid Recall Roster

PRS—Pyramid Recall System

Q-Hour—The hour mobility operations start in preparation for deployment

R-Hour—The reference time determined by the 374 AW/CC to initiate a recall

SME—Subject Matter Expert

TCCOR—Tropical Cyclone Condition of Readiness

UCC—Unit Control Center

UMD—Unit Manning Document

WSA—Wing Staff Agency


Attachment 2

RECALL STATUS REPORTS

A2.1. UCCs and Group SMEs will report and monitor personnel strength using any tool

specified by the CAT Director, but must include Personnel Accounting Symbol (PAS) codes.

Personnel strength accounting begins at R-Hour plus 1 and continues every hour thereafter until

all units have attained 100% personnel accountability.

A2.2. The wing goal for strength reporting is: R+3, 100% personnel accountability.

A2.3. UCCs will provide the following information for assigned military personnel per PAS

code:

A2.3.1. Number of personnel authorized. (Based on Unit Manning Document [UMD].)

A2.3.2. Number of personnel assigned. (This figure will be based on the unit strength

report.)

A2.3.3. Number of personnel on leave.

A2.3.4. Number of personnel TDY/deployed.

A2.3.5. Other. (e.g., hospital, confinement, etc.)

A2.3.6. Number of personnel available. (Subtract paragraphs A2.3.3., A2.3.4., and A2.3.5.

from paragraph A2.3.2.)

A2.3.7. Number of personnel present for duty. (Present for duty is defined as the individual

either being at his or her duty section or having been contacted, briefed on the current

situation and made aware of duty requirements.)

A2.3.8. Percentage recalled at present time. (Divide paragraph A2.3.7. by paragraph A2.3.6.

and multiply by 100.)

A2.4. If the recall reporting is executed via voice report, all UCCs/Group SMEs will use

the method outlined below.


Figure A2.1. Personnel Strength Voice Report Sample.

“This is (Unit) with a recall status report for (PAS Code). Report time is XXXX. Line 1 is 45…Line

2 is 44…, etc.”

1. Number of Personnel Authorized: 45

2. Number of Personnel Assigned: 44

3. Number of Personnel on Leave: 1

4. Number of Personnel on TDY: 2

5. Number of Personnel in Other Status (Hospital, Confinement, etc.): 1

6. Number of Personnel Available: 40

7. Number of Personnel Present for Duty: 21

8. Percent of Personnel Recalled at Present Time: 51%

With each report, provide the name, grade, and duty phone of the POC.

NOTE: Report should not include what each “Line number” means/includes due to OPSEC

A2.5. UCCs will contact members who are TDY, deployed, or on leave, only when directed by

their respective commander.

A2.5.1. For individuals on TDY at a non-military installation or on leave, recall individuals

by any means necessary (e.g., fax, telephone, e-mail, etc.) while maintaining OPSEC

considerations, if required.

A2.5.2. Personnel recalled to duty while on leave will be authorized travel and transportation

allowances authorized in Joint Federal Transportation Regulation (JFTR), Volume 1,

Chapter 7, Paragraph U7220, Recall from Leave.


Attachment 3

PARTNER UNIT NOTIFICATION LIST (WHEN DIRECTED BY 374 AW/CC)

A3.1. Group SMEs are responsible for maintaining up to date 24-hour point of contact

information for partner units. They will also provide a copy to the 374 AW/CP.

A3.2. Over time, partner units may change. Please refer to the 374 AW/CP for clarification.

As of the publishing of this document, the list is maintained on the Yokota Command Post

SharePoint site.

Table A3.1. The WSA Group SME will notify the following partner units.

Unit Duty Phone

5 AF Staff 225-6067/6068

USFJ Staff 223-6066

Defense Finance Accounting Service-Japan (DFAS-J) 225-9838/9840

Defense Energy Support Center-Japan 225-2673

Pacific Stars & Stripes 225-4505

PACOM ADP Server Site-Japan (PASS-J) 225-6593

Navy Federal Credit Union (CPTS)

Community Bank (CPTS) 225-4252/8469

American Forces Network (AFN) 225-1567/5749

Table A3.2. The 374 OG Group SME will notify the following partner units.

Unit Duty Phone

Defense Information Systems Agency, Pacific Area (DISA-PAC)

Department of Defense (DoD) Special Representative, Japan (DSRJ) 224-0500

US Coast Guard (USCG) Activities, Far East 225-6133

Air Force Standards Agency Detachment 225-1316

Detachment 402 - AFISRA 225-2491/6201


Table A3.3. The 374 MXG Group SME will notify the following partner units.

Unit Duty Phone

Det 934, Air Force Audit Agency (AFAA) 225-8575

Det OD7E (HQ USAF) Area Defense Counsel 225-8114/8119

Det 621 (AFOSI) 225-9881/7910

6th Field Investigation Sq (AFOSI) 225-4968/4820

369 RCS/GG (USAF Recruiting Office) 225-6388/9329

USAF Band of the Pacific-Asia (PACAF Band) 225-3368/3260

Defense Courier Service Station (DCSTA) 225-9706

Table A3.4. The 374 MSG Group SME will notify the following partner units.

Unit Duty Phone

JASDF OSW (Operations Support Wing)

Army & Air Force Exchange Service (AAFES) Yokota 225-3700/3725

Defense Commissary Agency (DECA) Yokota 225-8585

Det 2, Pacific Air Forces Air Postal Squadron (PACAF AIRPS) 225-7463

Department of Defense Dependents Schools, Pacific Region, Japan

(DODDS)

225-3940

Allied Telesis (COMM) 415-692-8307

US Army Corps of Engineers District Japan, Yokota Resident Office 225-2935

Document Automation and Production Service (DAPS) 225-8599

University of Maryland (FSS) 225-3680

Central Texas College (FSS) 225-9133

Table A3.5. The 374 MDG Group SME will notify the following partner units.

Unit Duty Phone

American Red Cross (ARC) 225-7522

Women-Infant & Children – Overseas (WIC-O) 225-9426

Defense Threat Reduction Agency (DTRA) 225-8638/8568

Education and Development Intervention Services (EDIS) 225-9993

Veterinary Clinic, US Army 225-2143


Table A3.6. The 730 AMS Unit Control Center will notify the following partner units.

Unit Duty Phone

Navy Overseas Air Cargo Terminal (NOACT) 225-9514/9428

Army Aerial Port Liaison Office (AAPLO) 225-9524/8700


Attachment 4

PYRAMID RECALL ROSTER FORMAT EXAMPLE

Figure A4.1. Sample Unit/Agency Recall Roster.


Figure A4.2. Notification Format.



Figure A4.3. Sample Comm-Out Recall Roster.

A4.1. Comm-out recall procedures will not always match comm-in Pyramid Recall System

recall procedures. When designing comm-out procedures, consider who lives in which buildings

and who lives off-installation. Consider this to ensure the most efficient path is being used.


Attachment 5

PYRAMID RECALL PROCEDURE BASELINE

Figure A5.1. Pyramid Recall Procedure Baseline.


Attachment 6

EXAMPLE ON-CALL / STANDBY LETTER

A6.1. The following is only an example. Units may tailor their letter as needed.

Figure A6.1. Example On-Call / Standby Letter.

Date post:	09-Aug-2018
Category:	Documents
Upload:	phungtuong
View:	219 times
Download:	0 times

BY ORDER OF THE COMMANDER YOKOTA AIR BASE...

Documents