|
Briefing Guide
Change 3
Table of Contents
|
Paragraph
Number
|
Title
|
|
2-3-5
|
AIRCRAFT IDENTITY
|
|
3-6-5
|
RADAR-ONLY MODE
|
|
4-1-2
|
EXCEPTIONS
|
|
4-4-2
|
ROUTE STRUCTURE TRANSITIONS
|
|
4-5-2
|
FLIGHT DIRECTION
|
|
5-5-1
|
APPLICATION
|
|
6-5-4
|
MINIMA ALONG OTHER THAN
ESTABLISHED AIRWAYS OR ROUTES
|
|
8-1-3
|
VFR FLIGHT PLANS
|
|
9-3-3
|
VFR-ON-TOP
|
1. PARAGRAPH NUMBER AND TITLE: 2-3-5. AIRCRAFT IDENTITY
2. BACKGROUND:
VC-25 flight management system upgrades and subsequent implementation of future
air navigation procedures (FANS) have driven the need to reevaluate the Air
Force One, Air Force Two, Army One, and Army Two call signs. Within FANS, the
VC-25 now has the capability (operationally approved and certified) to obtain
digital oceanic clearances and to utilize ATS datalink services to include
automatic dependent surveillance waypoint position reporting and controller
pilot datalink communications. To utilize these services, the aircraft must
register and file a call sign with at least three characters.
3. CHANGE:
|
OLD
|
|
NEW
|
|
2-3-5. AIRCRAFT IDENTITY
|
|
2-3-5. AIRCRAFT IDENTITY
|
|
Title through
b4(b)
|
|
No Change
|
|
5. Aircraft
carrying the President, Vice President, and/or their family members will use the
identifiers in the following tables. See TBL 2-3-8 and TBL 2-3-9.
|
|
No Change
|
|
|
TBL 2-3-8
President and Family
|
|
TBL 2-3-8
President and Family
|
|
|
|
Service
|
President
|
Family
|
|
Service
|
President
|
Family
|
|
|
|
Air Force
|
AF1
|
AF1F
|
|
Air Force
|
AF1
|
EXEC1F
|
|
|
|
Marine
|
VM1
|
VM1F
|
|
Marine
|
VM1
|
EXEC1F
|
|
|
|
Navy
|
VV1
|
VV1F
|
|
Navy
|
VV1
|
EXEC1F
|
|
|
|
Army
|
RR1
|
R1F
|
|
Army
|
RR1
|
EXEC1F
|
|
|
|
Coast Guard
|
C1
|
C1F
|
|
Coast Guard
|
C1
|
EXEC1F
|
|
|
|
Guard
|
G1
|
G1F
|
|
Guard
|
G1
|
EXEC1F
|
|
|
|
Commercial
|
EXEC1
|
EXEC1F
|
|
Commercial
|
EXEC1
|
EXEC1F
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TBL 2-3-9
Vice President and Family
|
|
TBL 2-3-9
Vice President and Family
|
|
|
|
Service
|
Vice President
|
Family
|
|
Service
|
Vice President
|
Family
|
|
|
|
Air Force
|
AF2
|
AF2F
|
|
Air Force
|
AF2
|
EXEC2F
|
|
|
|
Marine
|
VM2
|
VM2F
|
|
Marine
|
VM2
|
EXEC2F
|
|
|
|
Navy
|
VV2
|
VV2F
|
|
Navy
|
VV2
|
EXEC2F
|
|
|
|
Army
|
RR2
|
R2F
|
|
Army
|
RR2
|
EXEC2F
|
|
|
|
Coast Guard
|
C2
|
C2F
|
|
Coast Guard
|
C2
|
EXEC2F
|
|
|
|
Guard
|
G2
|
G2F
|
|
Guard
|
G2
|
EXEC2F
|
|
|
|
Commercial
|
EXEC2
|
EXEC2F
|
|
Commercial
|
EXEC2
|
EXEC2F
|
|
|
|
|
|
|
|
|
|
|
|
1. PARAGRAPH NUMBER AND TITLE: 3-6-5. RADAR-ONLY MODE
2. BACKGROUND:
Airport Surface Detection Equipment System - Model X (ASDE-X) was originally
designed with surface movement radar (SMR) and Multilateration (MLAT) for
airports with no surface surveillance. SMR radar was not intended to provide
total coverage of the entire airport. ASDE-X uses fusion as a way of creating
“seamless coverage" from all sensors (MLAT, SMR, and ASR). The original design
was to critically fault and go offline when MLAT or the SMR radar was
unavailable. Radar-only mode allows the ASDE-X system to remain operational if
the MLAT sub-system incurs a critical fault and is offline. Radar-only mode is
equivalent to the present ASDE3/AMASS operation at legacy airports.
3. CHANGE:
|
OLD
|
|
NEW
|
|
Add
|
|
3-6-5. RADAR-ONLY MODE
|
|
Add
|
|
Radar-only mode is an
enhancement of the ASDE-X system which allows the system to stay operational
with safety logic processing, despite a critical fault in the Multilateration (MLAT)
subsystem. The system stays in full core alert status under radar-only mode
without data block capability.
|
1. PARAGRAPH NUMBER AND
TITLE:
4-1-2. EXCEPTIONS;
4-4-2. ROUTE STRUCTURE TRANSITIONS;
5-5-1. APPLICATION; and
6-5-4. MINIMA ALONG OTHER THAN ESTABLISHED AIRWAYS OR ROUTES
2. BACKGROUND:
Due to the limited availability of air traffic control (ATC) surveillance
service within the Anchorage ARTCC domestic controlled airspace, the FAA
promulgated special flight regulations in support of the implementation of a
statewide RNAV/GPS route structure as reflected in the FAA Flight Plan. Those
special flight regulations include aircraft equipage and pilot training
requirements to provide additional safety mitigations for the expanded use of
RNAV/GPS procedures in areas with limited or no ATC surveillance coverage.
Initially, a waiver was authorized for Anchorage ARTCC to support GPS equipped
aircraft transitioning from the en route structure to airports with GPS
instrument approaches. Based on the experience gained through the application of
the subject waiver, this change supports the use of RNAV/GPS routes for
properly-equipped aircraft operating on point-to-point RNAV routes within
Anchorage ARTCC controlled airspace, excluding oceanic airspace, regardless of
ATC surveillance coverage.
3. CHANGE:
|
OLD
|
|
NEW
|
|
4-1-2. EXCEPTIONS
|
|
4-1-2. EXCEPTIONS
|
|
Title through a2
|
|
No Change
|
|
NOTE-
1. Para 5-5-1, Application,
requires radar separation be provided to RNAV aircraft on random (impromptu)
routes at FL 450 and below.
2. When
a clearance is issued beyond the altitude and/or distance limitations of a
NAVAID, in addition to being responsible for maintaining separation from other
aircraft and airspace, the controller is responsible for providing aircraft with
information and advice related to significant deviations from the expected
flight path.
|
|
NOTE-
1. Para 5-5-1, Application,
requires radar separation be provided to RNAV aircraft on random (impromptu)
routes at FL 450 and below.
2. EN ROUTE.
Radar monitoring is not required for aircraft equipped with IFR-certified GPS
systems operating on point-to-point RNAV routes within the Anchorage Air Route
Traffic Control Center (ARTCC) controlled airspace (excluding oceanic airspace),
where ATC surveillance coverage is not available. Additionally, in accordance
with para 5-5-1, Application; such aircraft described herein may be provided
nonradar separation, in lieu of radar separation, when an operational advantage
will be gained.
3. When
a clearance is issued beyond the altitude and/or distance limitations of a
NAVAID, in addition to being responsible for maintaining separation from other
aircraft and airspace, the controller is responsible for providing aircraft with
information and advice related to significant deviations from the expected
flight path.
|
|
REFERENCE-
P/CG Term- Radar Monitoring.
|
|
REFERENCE-
FAAO JO 7110.65, Para 2-1-3, Procedural Preference.
FAAO JO 7110.65, Para 4-4-2, Route Structure Transitions.
FAAO JO 7110.65, Para 6-5-4, Minima Along Other Than Established Airways or
Routes.
P/CG Term- Radar Monitoring.
|
|
OLD
|
|
NEW
|
|
4-4-2. ROUTE STRUCTURE
TRANSITIONS
|
|
4-4-2. ROUTE STRUCTURE
TRANSITIONS
|
|
Title through f
|
|
No Change
|
|
g. Provide radar
monitor when transition to or from a designated or established RNAV route is
made along random RNAV routes.
|
|
No Change
|
|
Add
|
|
EN ROUTE
EXCEPTION. Radar monitoring is not required for aircraft equipped with IFR-certified
GPS systems operating on point-to-point RNAV routes within Anchorage Air Route
Traffic Control Center controlled airspace (excluding oceanic airspace) where
ATC surveillance coverage is not available.
|
|
Add
|
|
REFERENCE-
FAAO JO 7110.65, Para 6-5-4, Minima Along Other Than Established Airways or
Routes
FAAO JO 7110.65, Para 4-1-2, Exceptions
|
|
OLD
|
|
NEW
|
|
5-5-1. APPLICATION
|
|
5-5-1. APPLICATION
|
|
Title through a
|
|
No Change
|
|
Add
|
|
EN ROUTE
EXCEPTION. Aircraft equipped with IFR-certified GPS systems operating on
point-to-point RNAV routes within the Anchorage Air Route Traffic Control Center
(ARTCC) controlled airspace (excluding oceanic airspace) where ATC surveillance
coverage is not available, may be provided nonradar separation, in lieu of radar
separation, when an operational advantage will be gained.
|
|
Add
|
|
REFERENCE-
FAAO JO 7110.65, Para 2-1-3, Procedural Preference
FAAO JO 7110.65, Para 4-1-2, Exceptions
FAAO JO 7110.65, Para 6-5-4, Minima Along Other Than Established Airways or
Routes
|
|
OLD
|
|
NEW
|
|
6-5-4. MINIMA ALONG OTHER
THAN ESTABLISHED AIRWAYS OR ROUTES
|
|
6-5-4. MINIMA ALONG OTHER
THAN ESTABLISHED AIRWAYS OR ROUTES
|
|
Title through a3
|
|
No Change
|
|
NOTE-
Degree-distance RNAV flight (random routes) at FL 450 and below are
provided radar separation.
|
|
NOTE-
1. Degree-distance RNAV flight (random routes) at FL 450 and
below are provided radar separation.
2. EN ROUTE.
Aircraft equipped with IFR-certified GPS systems operating on point-to-point
RNAV routes within the Anchorage Air Route Traffic Control Center (ARTCC)
controlled airspace (excluding oceanic airspace), where ATC surveillance
coverage is not available, may be provided nonradar separation, in lieu of radar
separation, when an operational advantage will be gained.
|
|
Add
|
|
REFERENCE-
FAAO JO 7110.65, Para 2-1-3, Procedural Preference
FAAO JO 7110.65, Para 4-4-2, Route Structure Transitions
FAAO JO 7110.65, Para 5-5-1, Application
|
|
b through dREFERENCE-
|
|
No Change
|
|
Add
|
|
EN ROUTE
e. For aircraft
equipped with IFR-certified GPS systems operating within Anchorage Air Route
Traffic Control Center controlled airspace (excluding oceanic airspace) where
ATC surveillance coverage is not available:
1. Aircraft shall
be cleared via point-to-point route segments. Points are defined as: NAVAIDS,
intersections, airports, and waypoints.
2. Lateral
protected airspace shall be 4 nautical miles (NM) either side of the projected
centerline between the points.
3. Points used for
navigation shall be named and depicted on the controller video map, and/or on
the controller chart(s) located at the position.
4. The maximum
distance between successive fixes/waypoints shall not exceed 512 miles.
5. Assigned
altitudes shall be at or above the highest minimum IFR altitude (MIA) along the
projected route, including the protected airspace of that route, for the route
segment being flown.
|
1. PARAGRAPH NUMBER AND
TITLE: 4-5-2. FLIGHT DIRECTION
2. BACKGROUND:
When Reduced Vertical Separation Minima (RVSM) was established in Oceanic
airspace Table 4-5-1, Altitude Assignment, was modified to include a section for
aircraft operating within Oceanic RVSM or RVSM transition airspace. This section
specified any designated cardinal altitude could be assigned regardless of
course of flight. With the implementation of domestic RVSM, application of RVSM
within both domestic and oceanic airspace is based on direction of flight. This
adheres to International Civil Aviation Organization (ICAO) Annex 2, Appendix 3,
Tables of Cruising Levels, which specifies assignment of a vertical separation
minimum of 1,000 feet between Flight Level (FL) 290 and FL 410 inclusive based
on direction of flight.
3. CHANGE:
|
OLD
|
|
NEW
|
|
4-5-2. FLIGHT DIRECTION
|
|
4-5-2. FLIGHT DIRECTION
|
|
Clear aircraft at
altitudes according to the TBL 4-5-1.
|
|
No Change
|
|
|
TBL 4-5-1
Altitude Assignment
|
|
TBL 4-5-1
Altitude Assignment
|
|
|
|
Aircraft
Operating
|
On
course
degrees
magnetic
|
Assign
|
Examples
|
|
Aircraft
Operating
|
On
course
degrees
magnetic
|
Assign
|
Examples
|
|
|
|
Below 3,000
feet above
surface
|
Any course
|
Any altitude
|
|
|
Below 3,000
feet above
surface
|
Any course
|
Any altitude
|
|
|
|
|
At and below
FL 410
|
0 through
179
|
Odd cardinal
altitude or flight levels at intervals of 2,000 feet
|
3,000,
5,000, FL 310, FL 330
|
|
At and below
FL 410
|
0 through
179
|
Odd cardinal
altitude or flight levels at intervals of 2,000 feet
|
3,000,
5,000, FL 310, FL 330
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
180 through
359
|
Even
cardinal altitude or flight levels at intervals of 2,000 feet
|
4,000,
6,000, FL 320, FL 340
|
|
|
180 through
359
|
Even
cardinal altitude or flight levels at intervals of 2,000 feet
|
4,000,
6,000, FL 320, FL 340
|
|
|
|
Above FL 410
|
0 through
179
|
Odd cardinal
flight levels at intervals of 4,000 feet beginning with FL 450
|
FL 450,
FL 490, FL 530
|
|
Above FL 410
|
0 through
179
|
Odd cardinal
flight levels at intervals of 4,000 feet beginning with FL 450
|
FL 450,
FL 490, FL 530
|
|
|
|
|
180 through
359
|
Odd cardinal
flight levels at intervals of 4,000 feet beginning with FL 430
|
FL 430,
FL 470, FL 510
|
|
|
180 through
359
|
Odd cardinal
flight levels at intervals of 4,000 feet beginning with FL 430
|
FL 430,
FL 470, FL 510
|
|
|
|
One way
routes (except in composite
systems)
|
Any course
|
Any cardinal
altitude or flight level below FL 410 or any odd cardinal flight level above
FL 410
|
FL 270,
FL 280, FL 290, FL 300, FL 310, FL 410, FL 430, FL 450
|
|
One way
routes (except in composite
systems)
|
Any course
|
Any cardinal
altitude or flight level below FL 410 or any odd cardinal flight level above
FL 410
|
FL 270,
FL 280, FL 290, FL 300, FL 310, FL 410, FL 430, FL 450
|
|
|
|
Within an
ALTRV
|
Any course
|
Any altitude
or flight level
|
|
|
Within an
ALTRV
|
Any course
|
Any altitude
or flight level
|
|
|
|
|
In
transition to/from or within Oceanic airspace where composite separation is
authorized
|
Any course
|
Any odd or
even cardinal flight level
including those above FL 290
|
FL 280,
FL 290,
FL 300,
FL 310,
FL 320,
FL 330,
FL 340
|
|
In
transition to/from or within Oceanic airspace where composite separation is
authorized
|
Any course
|
Any odd or
even cardinal flight level
including those above FL 290
|
FL 280,
FL 290,
FL 300,
FL 310,
FL 320,
FL 330,
FL 340
|
|
|
|
In aerial
refueling tracks and anchors
|
Any course
|
Altitude
blocks as requested. Any altitude or flight level
|
050B080,
FL 180B220, FL 280B310
|
|
In aerial
refueling tracks and anchors
|
Any course
|
Altitude
blocks as requested. Any altitude or flight level
|
050B080,
FL 180B220, FL 280B310
|
|
|
|
Aircraft
within Oceanic RVSM or RVSM transition airspace
|
Any
course
|
Any
designated cardinal altitude
|
FL 330,
FL 340,
FL 350,
FL 360
|
|
Delete
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1. PARAGRAPH NUMBER AND TITLE: 8-1-3. VFR FLIGHT PLANS
2. BACKGROUND:
VFR Flight Plans, include procedures for Visual Flight Rules (VFR) flight in
oceanic airspace. Deletion of extraneous verbiage is called for to define the
limitation for operations on a VFR flight within the Miami, Houston, and San
Juan Oceanic Control Areas (CTA).
3. CHANGE:
|
OLD
|
|
NEW
|
|
8-1-3. VFR FLIGHT
PLANS
|
|
8-1-3. VFR FLIGHT
|
|
VFR flights in Oceanic FIRs
may be conducted in meteorological conditions equal to or greater than those
specified in 14 CFR Section 91.155, Basic VFR weather minimums. Operations on a
VFR flight plan are permitted only between sunrise and sunset and only within:
|
|
No Change
|
|
a. Miami, Houston,
and San Juan Oceanic Control Areas (CTAs) at or below FL 180.
|
|
a. Miami, Houston,
and San Juan Oceanic Control Areas (CTAs) below FL 180.
|
1. PARAGRAPH NUMBER AND
TITLE: 9-3-3. VFR-ON-TOP
2. BACKGROUND:
The subject paragraph contains language that does not clearly state the intent.
3. CHANGE:
|
OLD
|
|
NEW
|
|
9-3-3. VFR-ON-TOP
|
|
9-3-3. VFR-ON-TOP
|
|
If the aircraft's route,
track, or altitude may cause it to enter an active Prohibited/Restricted/Warning
Area, MOA, or ATCAA:
|
|
No Change
|
|
a. Inform the
pilot to conduct flight “VFR-on-top” at least 500 feet above the upper limit or
lower limit of the airspace (subject to para
7-3-1, VFR-on-top); or
|
|
a. Inform the
pilot to conduct flight “VFR-on-top” at least 500 feet above the upper limit or
below the lower limit of the airspace (subject to para 7-3-1, VFR-on-top);
or
|
|
