**GREAT LAKES REGION CIVIL AIR PATROL**

**GREAT LAKES REGION REGIONAL DISASTER RESPONSE PLAN**

**GLR OPLAN 32‑1**

**DRAFT**

![](media/image1.wmf){width="4.5in" height="5.1in"}

DATE.

![](media/image2.png)

Date

Reply To The Attention of: GLR/DOS

Subject: GLR OPlan 32‑1

Memorandum For: See Distribution (Annex Z)

1\. Attached is GLR 32‑1. This plan is the Great Lakes Region CAP
supporting plan for Disaster Response by GLR Wings. Requests for change
in distribution should be sent to GLR/DO.

2\. This plan is effective for planning upon receipt and for
implementation when directed by the Commander, Great Lakes Region CAP.

3\. Elements of this plan were coordinated with HQ CAP/USAF, FEMA, and
GLR Wings.

4\. Supporting plans listed in the Plan Summary paragraph 4 must be
prepared and forwarded to this headquarters for review and approval
within 90 days after receipt of this plan. Annual review of this plan
will be conducted in October. Units preparing supporting plans must
forward review comments to this headquarters prior to March 2000.

Col. William S. Charles CAP

Commander Great Lakes Region

1 Atch.

GLR 32‑1

> HQ GLR

5440 Skeel Ave. Suite 2

> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[GLR 32‑1]{.underline}

PLAN SUMMARY

1\. [REASON FOR EXECUTION:]{.underline} The purpose of this OPlan is to
disseminate the procedures to be used in inter Wing Support during
large‑scale disasters.

2\. [FORCE EMPLOYMENT:]{.underline}

a\. [Situation.]{.underline} OPlan 32‑1 is based on the probability that
a natural disaster of such magnitude can happen in the Great Lakes
Region that the resources of any one Wing will be over tasked by a
Presidential Declaration.

b [Statement.]{.underline} This summary gives the CAP decision‑makers a
brief recapitulation of the major aspects of this OPlan. It is based on
planning factors and estimates available at the time of preparation and
is subject to modification in the context of a specific contingency. The
information in it should be reviewed and, if necessary, updated before
its use in adopting a course of action in a given situation.

c\. [Legal Considerations]{.underline}. This OPlan is based on the legal
considerations that exist in Federal Law, CAP Regulations, and State
Agreements in effect when the OPlan was written.

3\. [KEY ASSUMPTIONS:]{.underline} Assumptions used in this plan
include:

a\. [Presidential Declaration.]{.underline} A Presidential Declaration
has been made.

b\. [Wing Assets]{.underline}. The supported Wing assets are not
sufficient to meet the requirements.

4\. [OPERATIONS TO BE CONDUCTED:]{.underline}

a\. [Force Requirements.]{.underline} Force Requirements will be
dependent on the situation under which the plan is put into effect. The
requesting Wing Commander or designee will determine the Force
Requirements. The requirement may be for one special equipped asset, one
single response team, multiple teams, or perhaps an all out response
effort.

b\. [Deplovment]{.underline}. The requesting Wing will determine the
deployment locations. When the responding Wing provides availability of
assets, the location of reporting locations, Main Operating Bases (MOB)
and Forward Operating Bases (FOB) will be provided.

c\. [Employment]{.underline}. CAP assets may be called upon for, but not
limited to, Search and Rescue, Aerial Reconnaissance for Slow Scan,
video, digital, and still photography, movement of critical supplies
including parts and medications, and movement of critical personnel.

d\. [Supporting Plans]{.underline}. Wings subject to this OPlan should
prepare supporting plans.

5\. [OPERATIONAL CONSTRAINTS.]{.underline} Constraints to be considered
by Operations Planners are as follows; weather will effect the ability
of task Wings to respond to requests with the forces tasked. The school
year may limit the number of Ground Teams that are able to respond to
the tasking request. The number of aircrew respondents may be effected
by who can get off from regular jobs for long periods of time. Most
aircraft will be single engine fixed wing with the possibility of a few
light twin engines.

6\. [TIME TO COMMENCE EFFECTIVE OPERATIONS:]{.underline} Tasked forces
should be in place within 24 hours weather permitting.

7\. [COMMAND RELATIONSHIPS:]{.underline} When CAP forces are deployed
under this OPlan, operational control of those forces will transfer to
the Wing into which the forces deployed. However, command will remain
with the Wing providing the resources.

8\. [LOGISTICS:]{.underline} Shortfalls of consumables can be expected
to exist in the areas of highest devastation. Billeting at MOBs, FOBs
and other operating locations can expect to be Spartan in the worse case
scenarios. Requirements will need to be passed to the State EMA for
consumable support, but \"reach back\" support will need to be set up
for other needs.

9\. [PERSONNEL:]{.underline} Personnel requirements are sufficient for
most scenarios, however, shortfalls are expected to exist in a worse
case scenario. Support from outside the GLR may need to be requested.

> HQ GLR
>
> 5440 Skeel Ave. Suite 2
>
> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[GLR 32‑1]{.underline}

TABLE OF CONTENTS AND LIST OF EFFECTIVE PAGES

[CONTENTS PAGE]{.underline}

Plan Summary 5

Table of Contents and List of Effective Pages 7

Basic Plan 9

ANNEX A, TASK ORGANIZATIONS 13

ANNEX B, OPERATIONS 15

ANNEX C, LOGISTICS 21

ANNEX D, PERSONNEL 23

Appendix 1\--Critical Incident Stress Team 25

ANNEX E, PUBLIC AFFAIRS 27

ANNEX F, COMMUNICATIONS 29

Appendix 1‑‑Communications Planning 33

ANNEX G, COMMAND AND RELATIONSHIPS 35

Appendix 1‑‑Comrnand Relationships Diagram 37

ANNEX H, HOST WING SUPPORT 39

ANNEX I, SAFETY 41

ANNEX J, EXECUTION CHECKLIST 43

ANNEX K, REPORTS 47

ANNEX Z, DISTRIBUTION 49

> HQ GLR
>
> 5440 Skeel Ave. Suite 2
>
> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[GLR 32‑1 BASIC PLAN:]{.underline}

[TASK ORGANIZATIONS]{.underline}: See Annex A for tasked forces.

1\. [SITUATION]{.underline}

a\. [General]{.underline}. This plan will be put into effect when the
assets of a CAP Wing in the disaster area are not sufficient to handle
the requirements placed upon it during a Presidential Declaration. The
disaster may be limited to the area contained within the confines of a
single Wing or of such a magnitude to cross the legal boundaries of the
Wings.

b\. [Predisaster Actions]{.underline}. Wings tasked in this plan are
responsible to train and equip themselves to be able to respond to
requests from other Wings.

c\. [Assumptions.]{.underline}

\(1\) When a disaster situation hits a State or Multi‑State area CAP
will be tasked beyond the Wing resource capabilities available. The CAP
Liaison in the State or States will make an early determination to call
for assistance from other Wings in the Region.

\(2\) Main Operating Bases (MOBs) and Forward Operating Bases (FOBs)
will be selected early and will have emergency power, sufficient POL,
and supplies to sustain initial operations.

\(3\) Minimal operating support such as POL, supplies, and food will be
available through emergency support channels. Other support will need to
be obtained through \"reach back\" support from the home Wing.

\(4\) Reimbursement will be provided in accordance with directions
established by the supported Wing and the State requesting the support.
The host Wing will provide the necessary administrative support to
obtain the reimbursements.

d\. [Legal Considerations]{.underline}. Any Wing in the Great Lakes
Region may request assistance from any other Wing in the Region when the
assets of the requesting Wing are not sufficient to meet the taskings
placed upon it in accordance with current agreements.

2 [MISSION:]{.underline} The mission is to provide support to the State
and it\'s citizens in a disaster situation to prevent death, loss of
property, and relieve suffering. CAP can be expected to support Search
and Rescue, Damage assessment, courier flights including movement of
critical personnel, communications support, and ground support to other
disaster relief organizations.

3\. [EXECUTION:]{.underline}

a\. [Concept of Operations.]{.underline} When it is determined that
mission requirements will overtax the resources of the local Wing, that
Wing can request support from other Wings in the Great Lakes Region. The
Wing Commander or Operations Officer may request the support directly
from the other Wings, route the request through the Air Force National
Security Emergency Preparedness (AFNSEP) Office for DR Missions, or
through the Air Force Rescue Coordination Center for SAR Missions. The
requesting Wing will inform the supporting Wing of type and amount of
assets required.

\(1\) [General]{.underline}. Supporting Wings will deploy aircraft with
trained crews, aerial reconnaissance capability, communications teams,
and ground support personnel as requested by the supported Wing.

\(a\) Wings will not deploy more assets than requested by the supported
Wing.

\(b\) Assets may be deployed from a couple of days or up to several
weeks. In the event of longer deployments, the supporting Wing will make
arrangements to provide relief personnel and equipment as needed. If the
supporting Wing can not meet the requirements, it is their
responsibility to notify the supported Wing as far in advance as
possible.

\(2\) Deployment. The supported Wing will notify the supporting Wing as
to the locations of the operating bases where the units will report.
Rapid Reaction Teams should be directed to set up support at MOBs and
FOBs as soon as the bases are identified.

\(3\) Employment. Initial responding support units will be involved in
providing reconnaissance and setting up MOBs and FOBs. Once operating
bases and lines of communication have been established, other taskings
will be received and acted upon as defined in priorities dictated
AFNESP. Tasking will be relayed to the field units as outlined in the
operations annex.

b\. [Coordinating Instructions.]{.underline} It is imperative that the
supported and supporting Wings coordinate on a regular bases during the
time that this plan is in force.

4\. [ADMINISTRATION AND LOGISTICS]{.underline}

a\. [Concept of Logistics Support.]{.underline} CAP assets operating at
locations such as MOBs and FOBs will get day to day operational support
from the Logistics Officer in charge of that base. CAP assets should be
cognizant of the logistics support concept in effect at the operating
base, and where appropriate, be part of the planning process. CAP units
should determine if logistics support is taking into account the day to
day requirements need to sustain operations, such as POL and sustainment
for personnel.

b\. [Concept of Administrative Support.]{.underline} Deployed assets
should take with them enough forms to support them for at least three
days. Deployed assets should be knowledgeable of the paperwork that
needs to be turned in during and after the mission. Administrative
reports and requests will flow up through CAP channels to the host Wing
for action. If the Host Wing has insufficient assets to handle the
requirements, a request for additional support can be forwarded to other
Wings.

5\. COMMAND AND COMMUNICATIONS.

a\. [Command Relationships.]{.underline} Refer to Annex G.

b\. [Emergencv Operations Centers.]{.underline} Based on large-scale
deployments, the supported Wing will establish a Wing EOC and be the
primary routing center for CAP traffic in and out of the disaster area.
Supporting Wings will maintain an EOC to handle administrative, morale,
and logistics traffic for the deployed assets. As a minimum, the
supporting Wing will provide a 24-hour Point Of Contact to the supported
Wing EOC.

c\. [Command. Control and Communications Systems]{.underline}. CAP
should deploy and utilize it\'s own communications assets to the extent
possible. They must however be cognizant of other communication
capabilities available to support the mission.

Annexes:

A Task Organization

B Intelligence

C Operations

D Logistics

E Personnel

F Public Affairs

F Command, Control, and Communications Systems

G Command Relationships

H Safety

I Execution Checklist

J Reports

Z Distribution

OFFICIAL:

> Col. William S. Charles CAP
>
> Commander, GLR
>
> HQ GLR
>
> 5440 Skeel Ave. Suite 2
>
> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[ANNEX A TO GLR 32‑1]{.underline}

TASK ORGANIZATION

[ORGANIZATION COMMANDER]{.underline}

Great Lakes Region Civil Air Patrol GLR/CC

Illinois Wing Civil Air Patrol ILWG/CC

Indiana Wing Civil Air Patrol INWG/CC

Kentucky Wing Civil Air Patrol KYWG/CC

Michigan Wing Civil Air Patrol MIWG/CC

Ohio Wing Civil Air Patrol OHWG/CC

Wisconsin Wing Civil Air Patrol WIWG/CC

> HQ GLR
>
> 5440 Skeel Ave. Suite 2
>
> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[ANNEX B TO GLR 32-1]{.underline}

OPERATIONS

1\. GENERAL.

a\. [Assumptions]{.underline}.

\(1\) Power in the area of operations will initially be limited to those
facilities with generator capability.

\(2\) Communications will initially be slightly limited in the case of
major flooding, or be severely limited to only radio communications in
the case of a major earthquake.

\(3\) Aircrews, ground teams and mission support staff will deploy with
necessary maps for the expected area of operation. These will include,
but are not limited to FAA Aeronautical Charts, State Road Maps and
DeLorme Gazetteers.

\(4\) Aircrews, ground teams and mission support staff will deploy with
at least three days worth of paperwork to support the mission.

\(5\) There will be a heavy initial demand for airborne reconnaissance.
The requests will include hard copy photography, digital photography,
slow scan TV as well as visual observations. The primary mission of
reconnaissance is to provide information to other agencies involved in
mitigation and recovery operations in the disaster area.

\(6\) Wing and member provided equipment would be utilized to support
the mission. If resources are not sufficient to support requirements,
additional equipment can be requested from neighboring Wings.

\(7\) Wings should train in the use of equipment and crews to support
the airborne reconnaissance mission. Wings should plan to deploy with
the assets needed to support the missions that can be expected as
taskings.

\(8\) In most cases CAP will be based out of airports that are operating
under near normal conditions. That is, the Fixed Base Operator is
available and all facilities are available.

\(9\) However, under worse case situations, CAP may be the only
personnel at the base, and totally on their own. Communications,
fueling, and all other facilities needed to operate the base may need to
be provided by the CAP personnel operating at that location.

2\. [AREA OF OPERATIONS]{.underline}. The area of operations for this
plan includes all six States that comprise the Great Lakes CAP Region.
This is not to exclude the potential that operations of this scale will
not include some sorties into States adjacent to this Region.

a\. [Characteristics of the Area]{.underline}. The Great Lakes Region is
comprised of the States of Illinois, Indiana, Kentucky, Michigan, Ohio
and Wisconsin. The area contains large cities along its rivers and
lakes, medium sized cities throughout the area and many small towns and
cities scattered throughout its wide rural areas. There is heavy
industry along the Great Lakes and along the Mississippi and Ohio
Rivers. Mining can be found in the northwest and the southeast. The
central area is defined by extensive farming while large tracts of
hardwoods are found in the south and extensive softwood forests are
found in the north.

b\. [Weather]{.underline}.

\(1\) Central and south. The January temperatures average in the
20‑degree (F) to the high 80s in July and August. Sunny to partly cloudy
days range from 40% in the winter to 70% in the summer. Strong
thunderstorms are common in the late spring and summer. Snows are not
heavy, and usually last on the ground for only several days. Tornadoes
occasionally create damage in the area.

\(2\) North. Areas near the Great Lakes tend to be 10 degrees cooler
than areas 100 miles from the shorelines. Temperatures in the most
northern areas may run below zero for several weeks and average in the
60s and 70s in the summer. Snow fall will run from 30 inches and upward
to near 100 inches. Lake effect can produce higher rainfall and snow in
local areas. Tornadoes are rare in the north, but some thunderstorm
activity can be expected in the summer. Cloud cover is nearly the same
as the south.

c\. [Terrain]{.underline}. The southeast has the sharply rising ridges
of the Allegheny Mountains. These can be as high as 4000 feet with
valleys 1500 to 3000 feet below. The rest of the south can be considered
rolling or sharply rolling hills and valleys. Sharp bluffs can be found
along the Ohio River Valley. Most of the rest of the central and
northern areas are flat to gently rolling hills. There are many lakes,
streams and rivers in the region and some marshes can be found in the
wooded areas of the north.

3\. [CONCEPT OF OPERATIONS]{.underline}. Depending on the scope of the
disaster, it is expected that one or more MOBs will be established to
support operation. If distances and size of the area of operations
dictate, one or more FOBs will be established. ELT teams may be
dispatched by ground vehicle, or small teams may be flown into isolated
airfields to shut down ELTs that have been set off by the disaster.
Ground teams may be sent on damage assessment sorties or in support of
relief operations with other agencies. Temporary Flight Restrictions may
be established.

a\. [Training.]{.underline} All CAP Wings under this plan should train
personnel to be capable to provide assistance to other Wings under the
requirements as stated in this plan. Participants should be familiar
with Incident Command procedures.

b\. [Deployment Timing.]{.underline} Wings may have several days to
prepare to support operations in cases of major flooding. However, an
earthquake of severe weather damage can happen with little or no advance
preparation time given. Wings must have alerting and notification plans
ready and exercised.

c\. [Reporting Instructions.]{.underline} The supported Wing will notify
the supporting units where to report. This can be a MOB, or they could
be directed to report to a FOB.

\(1\) Main Operating Bases. One or more primary operating locations in
each Wing where all operational, supply, support and communication
capabilities exists. This location or locations are selected because of
the capabilities and the proximity to other supported agencies such as
the State EMA or military support agency.

\(2\) Forward Operating Bases. Are selected to meet operational
requirements such as distances from MOBs to the disaster area. Other
factors to be considered in a FOB selection are the facilities and POL
needed to support the operation.

\(3\) Ground Team Support. Ground Teams can be utilized for ramp and
communications support at MOBs and FOBs. Damage assessment and shelter
management in support of the Red Cross. Movement of food and medical
supplies out of staging areas to remote areas, and support to refugee
collection areas, donation management, and other logistical support.

d\. [ELT Operations.]{.underline} A large‑scale disaster such as an
earthquake can cause a multitude of ELTs to be activated. It is the
responsibility of the State to assess the priorities assigned to
shutting down these ELTs, but teams should be dispatched as soon as
practical to begin shutting them down. Where large numbers of ELTs are
running, DF equipped aircraft with a two‑man ground DF team on board
should be dispatched to suspect airports.

e\. [Temporary Flight Restrictions.]{.underline} If a State Director of
Aviation or the State appointed Air Operations Section has requested the
FAA and received a TFR for the disaster area, it is most probable that
experienced and trained CAP personnel will be required to augment the
State personnel to manage the air assets within the TFR.

f\. [CAP Ground Teams.]{.underline} CAP Ground Teams may be used in
support of military, FEMA Teams or law enforcement in support of rescue
operations. CAP Ground Team Leaders must be aware of the capabilities
and limitations of their teams both physically and legally.

\(1\) Ground teams may not be used to enforce laws, however, they may be
used in support of law enforcement in a limited role, reference CAPR
60-3. As citizens, they are expected to report law violations to the
proper authorities.

\(2\) Two person ELT teams may be established to be flown into usable
airports to eliminate non‑distress ELT signals.

g\. [Reconnaissance.]{.underline} CAP can be expected to be tasked early
in the disaster to accomplish reconnaissance of access routes into the
disaster area. This may consist of any or all of the following, slow
scan video, visual reports, videotape, digital pictures, or film still
photography.

\(1\) Collecting. Ground teams and aircrews should be thoroughly briefed
on the types of intelligence needed by the agencies being supported.
Teams and crews should be thoroughly debriefed and any intelligence
forwarded to the controlling agency Planing Section or individual making
the request. Intelligence and reconnaissance data may be of value to
more agencies than the one that requested it. MOB Operations and
Planning Sections should review information passing through for
applicability to other agencies.

\(2\) Reporting. Intelligence gathered as part of a tasking must be
reported to the requesting agency. Copies of general intelligence should
be also reported to the Planning Section of the controlling agency. CAP
operating units should be available to relay and transport information
collected by other field agencies for delivery to their main offices.
Aircrews and ground teams must always be ready to report emergency
developing situations through the most expedient means at their
disposal. CAP personnel located at MOBs and FOBs must be ready to pass
on this information to other agencies as rapidly as possible. In any
tasking, the task is not complete until the information is delivered to
the requesting agency. All available forms of information transmission
should be considered to get the information to the requesting agency.
Visual information such as video and photographs may have to be
delivered if digital transmission is not available. CAP radio or other
radios may be used to send visual reports to or from other participating
agencies.

\(3\) Logistics. Capability to process film will need to be established.

h\. [Commitment and coordination of forces.]{.underline} This will be at
the discretion of the State and FEMA.

4\. [OPERATING BASES.]{.underline}

a\. [Selection.]{.underline} MOBs and FOBs must be selected to provide
the basic needs to sustain operations. Runways, ramps, and at least
administrative space must be in a safe operational capacity. Fuel must
be available to support the first five days of anticipated operations.
Power must either be available or generator capability must be provided.

b\. [Main Operating Base.]{.underline} A Main Operating Base is selected
for its capability to sustain heavy operations for an extended period of
time. It must have power, fuel, and facilities to handle administrative,
communications, equipment and personnel requirements. More than one may
be selected based on the situation. The MOB is normally located close to
the State EOC. This base is used as the main nerve center for CAP
operations. It must be equipped with a full range of communications,
administrative and personnel capabilities. It must be capable of
sustaining a high level of operations, and will probably be a joint use
base with other agencies. This base will be the focus of requests for
support going outside the Wing, and the initial reporting point for
incoming support. This base will be the focal point for financial and
operational reporting and the communicational link with other Wings. If
the main operations area is some distance from the MOB, additional MOBs
may be established, however, these bases will require as much equipment
and nearly as many personnel to operate.

c\. [Forward Operating Base.]{.underline} A Forward Operating Base is
selected for its proximity to the operational area. It needs at least
communications, power, fuel and administrative areas. These may be
sparse, but the minimums that are required for turn operations. Several
forward operating bases may be selected as necessary. A FOB is selected
when distances become a factor. A FOB must be equipped with good
communications and a minimal staff. It is used to recover and turn crews
nearer to the operational area. It must have fuel and space to house the
communications and support personnel. Aircrews will normally return to
the MOB at the end of the day.

d\. [Tasks]{.underline}.

\(1\) Main Operating Base.

\(a\) Maintain a full operations, planning, financial and logistics
staff.

\(b\) Dispatch and recover aircrews and ground teams.

\(c\) Provide and track taskings sent to FOBs.

\(d\) Maintain lines of communications with the FOBs and other agencies.

\(e\) Provide for the health and welfare of CAP personnel in the area of
operations.

\(2\) Forward Operating Base.

\(a\) Maintain lines of communications with CAP personnel operating
within the area.

\(b\) Recover and launch aircrews and ground teams.

\(c\) Provide for the welfare of FOB personnel.

\(d\) Continually monitor capability to maintain operations in an
austere environment.

> HQ GLR
>
> 5440 Skeel Ave. Suite 2
>
> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[ANNEX C TO GLR 32‑1]{.underline}

LOGISTICS

1\. [GENERAL.]{.underline}

a\. [Support Requirements.]{.underline} Consumables and personnel living
requirements will be tasked to, and provided by the State or military
agencies. Maintenance support beyond minor repairs, most personal needs,
and communications equipment will require \"reach back\" to the
supporting Wings. Aircrews and ground personnel should report with at
least two days of rations on hand, Meals Ready to Eat or equivalent, and
water. Several quarts of engine oil and an extra filter should be
considered for deploying aircraft.

b\. [Support Planning.]{.underline} Many daily support requirements will
be in short supply in the early stages of the disaster recovery period.
Although basic daily needs will be limited in the early phases, other
needs will be met through requests to the home Wing.

\(1\) It is assumed that minor maintenance for aircraft and vehicles
will be available from local sources. However major maintenance for
vehicles, aircraft and communications equipment will require return of
assets to the home Wing. Modifications of CAP assets should be held
until the asset returns to home base, but emergency modifications will
be determined on a case by case bases. Equipment selected for deployment
should be in good condition and have a good amount of time or miles
available for use before the next scheduled maintenance. If maintenance
capability does not exist in the deployment area, equipment must be
monitored to allow sufficient time to return to the home Wing for
maintenance.

\(2\) Generally speaking, logistics support will be coordinated through
the state resources. Deployed assets may need to contact the home Wing
for assistance when not available through the State.

2\. [OBJECTIVE.]{.underline} The objective of the logistics
infrastructure is to anticipate the needs of the deployed assets, and to
react to requests from those units.

3\. [EXECUTION]{.underline}

a\. [Requirements Flow.]{.underline} Once operations begin, MOBs and
FOBs will send logistics requirements to the supported Wings EOC or
other designated point.

b\. [Reports Flow.]{.underline} Daily estimates of operating capability
must be prepared for each MOB and FOB and forwarded to the State Air
Operations Section. POL replenishments must be made known to the
appropriate State resource office at lease 48 hours prior to critical
need.

c\. [Military Support.]{.underline} Some support may be available, and
these requests will be handled through the Military Liaison channels.

d\. [Record Keeping.]{.underline} The supported Wing must keep detailed
records of logistics actions for later use in supporting reimbursement
requests.

> HQ GLR
>
> 5440 Skeel Ave. Suite 2
>
> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[ANNEX D TO GLR 32‑1]{.underline}

PERSONNEL

1\. [GENERAL]{.underline}.

a\. [Personnel Requirements.]{.underline} The supported Wing will
provide requirements for personnel to the supporting Wing\'s EOC. The
supporting Wings will review available personnel and notify the
supported Wing of availability and obtain reporting instructions. This
function will normally be accomplished through the supporting Wings EOC
staff.

b\. [Rotation of Personnel.]{.underline} The supporting Wing needs to be
planning for the rotation of personnel in the disaster areas and those
manning the home EOC.

2\. PERSONNEL POLICIES AND PROCEDURES

a\. [Deployed Personnel.]{.underline} Personnel selected to deploy must
understand they will be gone for some period of time. Do not deploy
personnel who must return in a day or two. Personnel must be in good
health and physical condition. Normal preventive shots such as tetanus
and typhoid are recommended, but not mandatory.

b\. [Qualifications.]{.underline} Personnel selected to report to the
disaster area must be qualified in the specialty in which they are
tasked. They must meet all the requirements as defined in CAPR 55­15 and
be familiar with the Incident Command System of disaster management.

\(1\) Reporting procedures will be obtained from the supported Wing\'s
EOC prior to deployment, and the EOC will brief personnel on the
details.

\(a\) Determine and brief the exact location and sign in location for
deploying personnel.

\(b\) Determine route of travel to be taken and brief deploying
personnel.

\(c\) Maintain a record of the details briefed and information about the
deploying personnel.

\(2\) Supporting Wings will be notified through their EOCs when deployed
crews and teams need to be rotated out. The supporting Wing will notify
the supported Wing of replacement availability.

\(3\) Wing EOCs need to have available listings of specialized skills
available for deployment.

c\. [Family Support.]{.underline} Wings that are supporting the
execution of this plan should maintain contact with the families of the
deployed personnel. Families should be notified of the Wing EOC phone
numbers and briefed on procedures to relay family information.

d\. [Deployment Prebrief.]{.underline} Include in the briefing to
deploying personnel that they will be subject to the laws in effect in
the disaster area and the directives of CAP. Brief that they will be
representing the CAP and to act in a professional manner.

# 

# 

# [APPENDIX 1 TO ANNEX D TO GLR 32-1]{.underline}

CRITICAL INCIDENT STRESS TEAM

1.  [GENERAL.]{.underline} The Critical Incident Stress Team (CIST) will
    be activated through the Region CIS Team Coordinator upon request of
    the Supported Wing Commander following the declaration of disaster
    or large scale incident.

a\. "Critical Incident Stress Management (CISM) may be defined as a
group discussion about a traumatic event ... which is solidly based in
crisis intervention theory ... designed to mitigate the psychological
impact of a traumatic event. CISM takes care of our people who
experience a potentially traumatizing event serving at a mission site or
other CAP emergency services activity." (CAPR 60-5 Par. 1.)

2.  [PERSONNEL REQUIREMENTS.]{.underline} The supported Wing will
    provide estimations of CAP/Civilian personnel involved in rescue
    operations and the disaster scenario to the Region CIS Team
    Coordinator to determine the number of Mental Health Professionals
    and CIST Members necessary.

a\. The CISTC will activate coordination of CAP and qualified local
resources. If sufficient combined CISM resources are not available, then
the CISTC shall request support from HQ CAP/DOS to arrange for
appropriate team deployment.

b\. The size of the incident, location, circumstances and personnel
involved will determine the use of Demobilization, Defusing or
Debriefing as the process of CISM.

3.  [RESOURCES.]{.underline} Versions of CISM specifically adapted to
    the incident involved have differing requirements. Cooperation
    between the supported and supporting wing to accommodate particular
    situational needs may be accomplished through communication between
    the Logistics Officer and CISTC.

a\. Demobilization: For major incidents/large scale disasters requiring
over 100 personnel, where screening and intervention are needed before
workers return home from the incident, and a defusing is impractical
secondary to situation/location.

\(1\) The facility should be near enough to the scene to be convenient
to transfer personnel there when they have been released from the
incident.

\(2\) Requires two large rooms; one to provide information sessions in
small work groups (ten minutes), the other for food and rest (twenty
minutes).

\(3\) Coordination with Red Cross or other supporting units for
supply/management of room with snacks/fruit/juice/water/decaf coffee for
departing work groups.

\(4\) Must be followed by a debriefing in a week or so; CIST to respond
as directed by arrangements of personnel per supported/supporting wing
commanders/designees.

b\. Defusing: A 20-45 minute intervention within eight hours of the
incident provided to groups of ten or less at a time. Used in place of a
demobilization, may offset the need for debriefing.

\(1\) The facility is NEVER on site, should be close enough to the scene
for easy access.

\(2\) Requires a large room, chairs for each individual and CIST members
(placed in a circle).

a\. Room should be quiet, private, closed and marked NO ENTRY, session
in progress. NO ONE should enter after defusing begins.

b\. Room should have bathroom access.

c\. Place tissues conveniently, as defusings have emotional components.

c\. Debriefing: Structured group conversation lasting up to 2-3 hours,
performed preferably within a few days of the incident. Member contact
through supported wing commander or his/her designee.

\(1\) Physical requirements as are for a defusing.

4.  [REPORTING.]{.underline} The CISTC will report as required to the HQ
    CAP/DOS with an After Action Report. (S)he will also report to the
    supervising CIST MHP (or CIST Chief), and make recommendations for
    follow up.

a\. Non-CAP supportive personnel should be sent letters of appreciation
for their participation in the interventions. The Logistics Officer (or
whoever arranged for the additional support) may provide that
information to the CISTC.

> HQ GLR
>
> 5440 Skeel Ave. Suite 2
>
> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[ANNEX E TO GLR 32‑1]{.underline}

PUBLIC AFFAIRS

1\. [GENERAL.]{.underline}

a\. [PA Activities.]{.underline} All PA activity will be executed under
the authority and direction of the supported Wing Commander, and be in
accordance with CAP guidance.

b\. [Requests For PAs.]{.underline} The supported commander will request
additional Information Officer support if needed.

2\. [CAP INFORMATION OFFICERS.]{.underline} CAP Information Officers
will make themselves available to provide information on CAP and it\'s
activities available to news media in the disaster area and to the home
Wings of the supporting units. They will also be available to assist the
State EMA Information Officers in meeting requests for information.

a\. [State PA.]{.underline} Work closely with the State EMA Information
Officer. Coordinate releases and provide information to the supported
State and Wing.

b\. [Releases For Supporting Wings.]{.underline} Provide news releases
back to the Wing EOCs about the personnel, assets and activities of
supporting units.

c\. [MOB Support.]{.underline} Provide direction to CAP Information
Officers at the MOBs.

d\. [PA Requirements.]{.underline} The CAP Information Officer will
operate out of the MOB or out of the State EOC with the State
Information Officers. If there are more than one MOB, consideration must
be given to providing an Information Officer at each location. If the
supported Wing does not have sufficient Information Officers available,
support from other Wings should be requested.

3\. [TASKS.]{.underline} For example:

a\. [Planning]{.underline} All CAP organizations supporting this
operation will plan to:

\(1\) Identify mission qualified Information Officers.

\(2\) Ensure that all Information Officers deploying to the disaster
area contact the host Wing Information Officer.

\(3\) Publicize the operation activities through all available internal
and external information channels.

\(4\) Prepare, coordinate, and submit materials for use in CAP internal
products.

\(5\) Disseminate cleared news, photo, radio and television releases to
their home units.

e\. [Administrative Supplies.]{.underline} CAP Information Officers
should have all necessary administrative supplies with them when
reporting for duty. The Information Officer should bring prepared
handouts about CAP Emergency Services.

f\. [Computer Support.]{.underline} Bringing a personal laptop computer
should be a top consideration. The Information Officer should have a
checklist available when reporting.

> HQ GLR
>
> 5440 Skeel Ave. Suite 2
>
> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[ANNEX F TO GLR 32‑1]{.underline}

COMMUNICATIONS AND INFORMATION

1\. [GENERAL.]{.underline}

a\. [Assumptions]{.underline}.

\(1\) CAP communications are prepositioned at or near the State EOC.

\(2\) The supported Wing has an operational EOC.

\(3\) Most or all repeaters in the disaster area are non‑operational.

\(4\) Supporting Wings will be able to move communication assets
rapidly.

b\. [Resource Availabilitv]{.underline}.

\(1\) High Frequency Voice (SSB)

> A. 4.604 MHz (GLR Primary)
>
> B. 4.601 MHz (GLR Secondary)
>
> C. 14.902 MHz
>
> D. 18.205 MHz
>
> E. 20.873 MHz
>
> F. 26.620 MHz (AM ‑ short range tactical use only)
>
> \(2\) High Frequency Digital
>
> A. 7.341 MHz

\(3\) Aviation Voice

> A. 122.9 MHz (not uniquely CAP)
>
> B. 123.1 MHz (not uniquely CAP)
>
> C. 121.775 MHz
>
> D. 121.600 MHz

\(4\) FM Voice

> A. 143.750 MHz
>
> B. 143.900 MHz
>
> C. 148.125 MHz

D. 148.1375 MHz

E. 148.150 MHz

F. 149.5375 MHz

\(5\) FM Digital

A. 149.895 MHz

B. 149.925 MHz (where authorized along the Canadian border)

2\. [MISSION.]{.underline} The primary mission of CAP communications in
a disaster situation is to provide for command and control of CAP
assets. In a disaster situation, CAP communications will also support
the flow of information and intelligence for other agencies involved in
the recovery

operations.

3\. [EXECUTION]{.underline}

a\. [Operational Concept]{.underline}. As set forth previously in this
plan, information shall flow from the dispersed ground teams, to one of
several austere FOBs. The FOBs will report to one of a very few MOBs,
that will have full facilities. The MOB(s) will relay information up to
the Wing EOC, which is assumed to be collocated with the State EOC.

b\. [Tasks.]{.underline}

\(1\) EOC. Communications between the Wing EOC and the MOBs will be
conducted via HF radio. Inter‑wing communications will be conducted via
telephone or cellular phone. The Region\'s primary HF frequency shall be
dedicated to communications between the EOC and the MOBs.

\(2\) MOB. FOBs will use the state designated HF frequency to report to
the MOBs. This will reduce congestion on the VHF frequencies.

\(3\) FOBs. Due to the number of ground teams needed to respond to a
major disaster, extensive use of all available VHF frequencies is
anticipated ‑ both for team to team and team to FOB communications. With
the likelihood that the repeaters in the disaster area are offline, use
of the input frequencies is authorized. The FOB director of
communications will ensure that surviving repeaters will be taken
offline to permit local use of the input frequencies.

\(4\) Ground Teams. With the nature of the mission during a disaster,
close communications with the local FOB is critical. As outlined above,
use of the repeater input frequencies for local tactical communications
is authorized. Reserve 148.150 and 148.125 MHz for reporting to the FOB.
In the event that a high bird aircraft is available, remember the 100Hz
tone to talk to the aircraft. Those units with 26.620 MHz capability
will be used to the maximum extent possible.

c\. [Special Measures]{.underline}

\(1\) Ground teams will monitor the standard Citizen Band channels for
distress calls from the public and to communicate with local law
enforcement organizations.

\(2\) Marine band radios will provide contact with the Coast Guard for
support on major waterways

Appendices:

1\. Communications Planning

2\. New Madrid Earthquake Frequency Plan

[APPENDIX 1 TO ANNEX F]{.underline}

COMMUNICATIONS PLANN1NG

1\. [SITUATION.]{.underline}

2\. [PLANN1NG FACTORS.]{.underline} Wings should develop mobile
communications teams, capable of rapid deployment to austere locations.
With the possibility of limited ground transportation, air mobile
communications teams should be considered. 148.1375 MHz shall be
designated the primary slow-scan video frequency, with 149.5375 MHz as
the secondary. 4.604 MHz is the primary HF channel, with 4.601 MHz
serving as the secondary. The additional HF frequencies will be used as
traffic load and band conditions require. The devastated state shall
have priority usage of the primary frequencies. In the event of a
multi-state disaster, the Region Commander shall determine which state
utilizes the primary frequency.

a\. [Concept of Operations]{.underline}. TO BE PROVIDED.

b\. [Tasks.]{.underline} TO BE PROVIDED.

c\. [Equipment requirements.]{.underline} TO BE PROVIDED.

[APPENDIX 2 TO ANNEX]{.underline} F

NEW MADRID COMMUNICATIONS PLAN

1\. [SITUATION]{.underline}. Under a New Madrid Earthquake scenario,
Multiple Wings and multiple Regions will be making heavy use of the CAP
frequency spectrum. To try to eliminate interference Air-to-Ground
frequencies will be allocated as listed below.

a\. [Concept of Operations]{.underline}. Air-To-Ground communications
will be no tone, simplex operations. Aircraft operating in the indicated
Wings will utilize these frequencies.

b\. [Frequency Assignments.]{.underline}

[WING]{.underline} [FREQUENCY]{.underline}

(1). Arkansas 148.125

(2). Illinois 148.1375

(3). Indiana 148.125

(4). Kentucky 143.90

\(5\) Mississippi 148.1375

(6). Missouri 143.75

(7). Tennessee 149.5375

> HQ GLR
>
> 5440 Skeel Ave. Suite 2
>
> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[ANNEX G TO GLR 32‑1]{.underline}

C0MMAND RELATIONSHIPS

a\. [Command.]{.underline} Command of Civil Air Patrol assets always
remains within the Civil Air Patrol chain of command.

b\. [Functional Control.]{.underline} Functional control of Civil Air
Patrol assets will vary according to the situation. Functional control
of CAP assets may come under the control of the Incident Commander or On
Scene Coordinator who may not be a CAP member. All CAP Ground Team
Leaders and Aircrews must be aware of the legal limitations of use of
CAP assets.

c\. [Incident Command System.]{.underline} All personnel should be aware
of operating under the Incident Command System of management.

d\. [Presidential Declaration.]{.underline} Under a Presidential
Declaration, CAP would be under the direction of the Emergency
Preparedness Liaison Officer (EPLO).

3\. [SUPPORT AND COORDINATION RELATIONSHIPS]{.underline}

a\. [Supporting Military Forces.]{.underline} CAP support to DOD
agencies will take place through the CAP Liaison and the EPLO.

b\. [Coordinating Authorities.]{.underline} The CAP Liaison should be
the coordinating agent for CAP operations and activities at the EPLO
level.

Appendix:

1‑Command Relationships Diagram

> HQ GLR
>
> 5440 Skeel Ave. Suite 2
>
> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[ANNEX H TO GLR 32‑1]{.underline}

HOST WING SUPPORT

1\. [General.]{.underline}

a\. [Host Wing.]{.underline} The host Wing will be the focus and
responsible for supporting responding

units.

b\. [Training.]{.underline} Procedures and training are the
responsibility of each Wing Commander.

2\. [MISSION.]{.underline} The mission of HWS is to provide support to
supporting CAP units.

a\. [Concept of HWS Support.]{.underline} There are two primary
requirements under HWS. The Host Wing is the primary contact point
between the CAP forces and the organizations listed in annex G. The
second function is to set up and maintain the reimbursement process.

b\. [Tasks]{.underline}

\(1\) The Host Wing will establish a central point for all financial
paperwork collection. This point will certify all requests for payment
by CAP personnel operating in that Wing.

\(2\) The Host Wing will position knowledgeable personnel in the State
EOC and Military operation centers to maintain liaison with these
organizations.

\(3\) The Host Wing will collect operational reports and requirements
from the MOBs and FOBs and forward them as applicable.

\(4\) The Host Wing will maintain a 24 hour EOC to handle communications
between deployed units and their home Wings.

\(5\) The Host Wing will forward copies of CAP Forms 103, 107, and 121
to each supporting Wing.

HQ GLR

> 5440 Skeel Ave. Suite 2
>
> Wright-Patterson AFB OH
>
> 45433-5267
>
> Date

[ANNEX I TO GLR 32-1]{.underline}

SAFETY

1\. [GENERAL.]{.underline}

a\. [Conditions.]{.underline} In any disaster operation unsafe
conditions will exist. All personnel must be constantly vigilant for
such conditions and mitigate their effect on the operations.

b\. [Units.]{.underline} The mission of units involved in support to the
disaster is to accomplish that support without endangering the personnel
and equipment in their care.

c\. [Supervisors.]{.underline} Disaster response activities can be
hazardous by their very nature. A11 supervisory personnel will provide
caution advisory information as often as possible.

d\. [Base Commanders.]{.underline} MOB and FOB commanders will appoint
an individual to act as the safety officer.

\(1\) The MOB or FOB commander or safety officer will review the
physical and operations at the location at least daily for unsafe
conditions or activities.

\(2\) Disaster situations cause unsafe situations. Roads and bridges can
be damaged to the point that they can give way days after the original
cause. Buildings needed by responding forces can have hidden damage
making them unsafe. After an earthquake, roads, buildings, runways, and
navigation aids may not be in perfect condition. These hazards may not
be apparent at first observation.

\(3\) Promptly report mishaps and hazards as specified in CAP
directives.

\(4\) Promptly investigate mishaps according to applicable directives.
Identify any deviations from normal investigative procedures or
responsibilities.

HQ GLR

> 5440 Skeel Ave. Suite 2
>
> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[ANNEX J TO GLR 32-1]{.underline}

EXECUTION CHECKLIST

1\. [General.]{.underline} The checklists in this annex are provided as
guidance for implementing this plan. They are intended as a reference
for the Supported and the Supporting Wings use.

a\. The Checklist for the Supported Wing contains information that must
be considered before requesting support.

b\. The Checklist for the Supporting Wing is provided for reference when
providing personnel and equipment to another Wing.

SUPPORTED WING CHECKLIST

1.  Determine tasking is beyond capability of Wing.

2.  Define support needed from other Wings.

3.  Determine which Wing(s) you are going to request support from.

4.  Coordinate request with Defense Coordinating Officer if under
    Presidential Declaration.

5.  Notify supporting Wing(s) of requirements.

```{=html}
<!-- -->
```
a.  Aircraft/crews, special equipment, slow-scan, digital camera, etc

b.  Ground Teams, special equipment, DF, etc.

c.  Mission Staff, what positions?

d.  Other.

```{=html}
<!-- -->
```
6.  Reporting location and point of contact.

```{=html}
<!-- -->
```
a.  Location and ingress instructions.

b.  Phone numbers.

c.  Frequencies and callsigns.

```{=html}
<!-- -->
```
7.  Provide supporting Wing with EOC and 24 hour point of contact if
    supported Wing is not 24 hour operational.

8.  Get point of contact if supporting Wing EOC is not 24 hour
    operational.

SUPPORTING WING CHECKLIST

1.  Determine if Wing can support the request.

2.  Alert personnel for deployment.

3.  Determine reporting location and point of contact.

```{=html}
<!-- -->
```
a.  Location and ingress instructions.

b.  Phone numbers.

c.  Frequencies and callsigns.

```{=html}
<!-- -->
```
4.  Provide supported Wing with EOC and 24 hour point of contact if
    supporting Wing is not 24 hour operational.

5.  Get point of contact if supported Wing EOC is not 24 hour
    operational.

CISM TEAM ACTIVATION

Early contact with the CISTC (once CAP participation is requested) is
preferred; early alert assists to logistically prepare for possible
intervention. Contact information for on-site staff at the beginning of
set up and early communications should be established.

1\. Phone Regional CIST Coordinator with on-site contact and situation
information, as follows:

Sherry Jones

H 810.773.2629

C 810.362.7437

P 877.802.7437

W 313.417.2760/1 (313.343.2931)

This is a Level One Trauma Center ER; tell them this is an Air Force
Disaster Emergency, and to FIND Sherry Jones if she is not readily
available.

2\. Arrange for CISTC transportation to the site for meeting with
MC/Logistics Officer (and staff). Preferable transport is flight in and
ground transportation from airport.

3\. Have someone on-site available to direct local debriefing staff.

4\. Arrange for lodging for CISTC (or designee) and whatever staff (s)he
brings.

5\. Arrange for meals for CISTC (or designee) and staff.

6\. Arrange for debriefing site as outlined in Ops plan addendum.

\(a\) Closed, quiet room, no distractions, bathroom nearby, sufficient
quantity of folding chairs available, tissues available.

\(b\) On site coordinator to facilitate logistics/needs of CISTC and CIS
Team.

\(c\) Local Red Cross (or other) local contact to facilitate
coordination of donation of food items for demobilization as needed.

7\. Have on-site staff establish for the CISTC or designee a complete
and current name, address and phone number contact list of ALL CAP
participants in the activity.

\(a\) Should any member leave before being debriefed by the CISTC or
designee, one on one follow up must be made.

8\. Have on-site staff establish for the CISTC or designee a separate
complete and current name, address and phone number list of ALL non-CAP
participants (including but not limited to local fire, EMS, police, and
all miscellaneous volunteer services). These are to be grouped by
specialty (fire, police, etc.).

\(a\) Should any non-member participant leave before being debriefed by
the CISTC or designee, one on one follow up must be made.

9\. Have on-site staff establish for the CISTC or designee a separate
complete and current name, address and phone number contact list of all
military participants.

\(a\) Should any military participant leave before being debriefed by
the CISTC or designee, one on one follow up must be made.

10\. Computer with print capability for the handouts should be available
to the CISTC (internet access preferred but not required).

\(a\) Access to photo-copier preferred but not required.

\(b\) Access to land line for incoming/outgoing calls required.

11\. Assure transportation for members, non-members and military
personnel to be debriefed as outlined in the appendix, to and from the
debriefing site.

12\. Have on-site availability to transport any member of debriefing to
medical facility as needed, have on-site medical personnel advised
where/when debriefing is to be held.

(a) Advise CISTC of location of first aid station on-site location.

13\. Advise CISTC of local Chaplain availability with complete contact
information.

> HQ GLR
>
> 5440 Skeel Ave. Suite 2
>
> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[ANNEX K TO GLR 32-1]{.underline}

REPORTS

1\. [GENERAL.]{.underline} This annex provides guidance to headquarters
and subordinate units for accomplishing reporting requirements during
Disaster Response under this Plan.

2\. [PURPOSE.]{.underline} The purpose of this annex is to provide basic
administrative and operational information to the commander and
subordinate units for command and control of assigned CAP forces.

a\. [Supported Wing]{.underline}.

\(1\) The supported Wing is responsible for the daily Tempest Rapid
Report. This report will be the consolidated activity of all
participating units in support of that Wing.

\(2\) The supported Wing will supply copies of operational information,
i.e. CAP Forms and a copy of the Tempest Rapid Report to all supporting
Wings.

\(1\) The CAP member in charge of CAP activities at the MOB is
responsible to collect all operational data at the MOBs and FOBs under
his direction and forwarding it to the Supported Wing\'s designated
collection point.

b\. [Voice Reports.]{.underline} Voice reports will be used when hard
copy reporting is not available. Voice reports may be by phone or radio.
When voice reporting is utilized, the reporting unit will ensure that
the receiving higher unit has in fact clearly understood the report.

c\. [Message Reports.]{.underline} Tempest Rapid Reports will format IAW
CAPR 60-3 unless requested differently by the requesting agency.

> HQ GLR
>
> 5440 Skeel Ave. Suite 2
>
> Wright‑Patterson AFB OH
>
> 45433‑5267
>
> Date

[ANNEX Z TO GLR 32‑1]{.underline} DISTRIBUTION

[DISTRIBUTION NO. COPIES]{.underline}

National Headquarters CAP 5

Great Lakes Region Liaison 2

Great Lakes Region Civil Air Patrol 5

Illinois Wing Civil Air Patrol 5

Indiana Wing Civil Air Patrol 5

Kentucky Wing Civil Air Patrol 5

Michigan Wing Civil Air Patrol 5

Ohio Wing Civil Air Patrol 5

Wisconsin Wing Civil Air Patrol 5

Region IV FEMA 1

Region V FEMA 1