|
Table of Contents
Table of Contents
|
Paragraph
Number
|
Title
|
|
2-1-28
|
RVSM OPERATIONS
|
|
2-3-5
|
AIRCRAFT IDENTITY
|
|
3-7-2
|
TAXI AND GROUND MOVEMENT OPERATIONS
|
|
3-9-9
|
TAKEOFF CLEARANCE
|
|
8-7-4
|
LATERAL SEPARATION
|
|
8-8-4
|
LATERAL SEPARATION
|
|
Appendix A
|
Aircraft Information FIXED-WING AIRCRAFT
|
1. PARAGRAPH NUMBER AND TITLE: 2-1-28. RVSM OPERATIONS
2. BACKGROUND: Information from FAA facility and the Department of Defense contacts indicate that STORM flight
status coordination procedures are no longer being utilized. Accordingly, the requirements related to STORM flight status
and DOD Priority Mission website are deleted.
3. CHANGE:
|
OLD
|
|
NEW
|
|
2-1-28. RVSM OPERATIONS
|
|
2-1-28. RVSM OPERATIONS
|
|
Title through a1NOTE
|
|
No Change
|
|
2. A non-RVSM exception designated by the DOD
for special consideration via the DOD Priority Mission
website shall be referred to as a STORM flight.
|
|
Delete
|
|
3 and 4
|
|
Renumber 2 and 3
|
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
|
|
Add
|
|
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.
|
|
|
Add
|
|
TBL 2-3-8
President and Family
|
|
|
|
|
|
Service
|
President
|
Family
|
|
|
|
|
|
Air Force
|
AF1
|
AF1F
|
|
|
|
|
|
Marine
|
VM1
|
VM1F
|
|
|
|
|
|
Navy
|
VV1
|
VV1F
|
|
|
|
|
|
Army
|
RR1
|
R1F
|
|
|
|
|
|
Coast Guard
|
C1
|
C1F
|
|
|
|
|
|
Guard
|
G1
|
G1F
|
|
|
|
|
|
Commercial
|
EXEC1
|
EXEC1F
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add
|
|
TBL 2-3-9
Vice President and Family
|
|
|
|
|
|
Service
|
Vice President
|
Family
|
|
|
|
|
|
Air Force
|
AF2
|
AF2F
|
|
|
|
|
|
Marine
|
VM2
|
VM2F
|
|
|
|
|
|
Navy
|
VV2
|
VV2F
|
|
|
|
|
|
Army
|
RR2
|
R2F
|
|
|
|
|
|
Coast Guard
|
C2
|
C2F
|
|
|
|
|
|
Guard
|
G2
|
G2F
|
|
|
|
|
|
Commercial
|
EXEC2
|
EXEC2F
|
|
|
|
|
|
|
|
|
|
|
c. Special‐use. Approved special‐use identifiers.
|
|
No Change
|
1. PARAGRAPH NUMBER AND TITLE: 3-7-2. TAXI AND GROUND MOVEMENT OPERATIONS
2. BACKGROUND: The FAA Administrator has made numerous recommendations to enhance runway safety. ATO-T
Safety and Operations Support assembled a Safety Risk Management (SRM) Panel to address some of the proposals from
this workgroup. The panel did a safety assessment on taxi procedures at our Tower Controlled Airports and concurred with a
recommendation to require detailed routings be issued to all aircraft and vehicles on the movement area. The panel
determined this would enhance runway safety.
3. CHANGE:
|
OLD
|
|
NEW
|
|
3-7-2. TAXI AND GROUND MOVEMENT
OPERATIONS
|
|
3-7-2. TAXI AND GROUND MOVEMENT
OPERATIONS
|
|
Issue, as required or requested, the route for the
aircraft/vehicle to follow on the movement area in
concise and easy to understand terms. When a taxi
clearance to a runway is issued to an aircraft, confirm the
aircraft has the correct runway assignment.
|
|
Issue the route for the aircraft/vehicle to follow on the
movement area in concise and easy to understand terms.
The taxi clearance shall include the specific route to
follow. When a taxi clearance to a runway is issued to an
aircraft, confirm the aircraft has the correct runway
assignment.
|
|
NOTE-
1. A pilot's read back of taxi instructions with the runway
assignment can be considered confirmation of runway
assignment.
2. Movement of aircraft or vehicles on nonmovement
areas is the responsibility of the pilot, the aircraft
operator, or the airport management.
|
|
No Change
|
|
a. When authorizing a vehicle to proceed on the
movement area, or an aircraft to taxi to any point other
than an assigned takeoff runway, absence of holding
instructions authorizes an aircraft/vehicle to cross all
taxiways and runways that intersect the taxi route. If it is
the intent to hold the aircraft/vehicle short of any given
point along the taxi route, issue the route, if necessary,
then state the holding instructions.
|
|
a. When authorizing a vehicle to proceed on the
movement area, or an aircraft to taxi to any point other
than an assigned takeoff runway, absence of holding
instructions authorizes an aircraft/vehicle to cross all
taxiways and runways that intersect the taxi route. If it is
the intent to hold the aircraft/vehicle short of any given
point along the taxi route, issue the route, and then state
the holding instructions.
|
|
NOTE-
Movement of aircraft or vehicles on nonmovement areas
is the responsibility of the pilot, the aircraft operator, or
the airport management.
|
|
No Change
|
|
PHRASEOLOGY and EXAMPLE
|
|
No Change
|
|
b. When authorizing an aircraft to taxi to an assigned
takeoff runway and hold short instructions are not issued,
specify the runway preceded by “taxi to,” and issue taxi
instructions if necessary. This authorizes the aircraft to
“cross” all runways/taxiways which the taxi route
intersects except the assigned takeoff runway. This does
not authorize the aircraft to “enter” or “cross” the
assigned takeoff runway at any point.
|
|
b. When authorizing an aircraft to taxi to an assigned
takeoff runway and hold short instructions are not issued,
specify the runway preceded by “taxi to,” and issue taxi
instructions. This authorizes the aircraft to “cross” all
runways/taxiways which the taxi route intersects except
the assigned takeoff runway. This does not authorize the
aircraft to “enter” or “cross” the assigned takeoff runway
at any point.
|
|
PHRASEOLOGY-
TAXI TO RUNWAY (number) VIA . . ..
|
|
PHRASEOLOGY-
TAXI TO RUNWAY (number) VIA (route).
|
|
EXAMPLE-
“Taxi to Runway One Two.”
“Taxi to Runway Three Six via Taxiway Echo.”
or
“Taxi to Runway Three Six via Echo.”
|
|
EXAMPLE-
Delete
“Taxi to Runway Three Six via Taxiway Echo.”
or
“Taxi to Runway Three Six via Echo.”
|
|
c. Specify the runway for departure, any necessary taxi
instructions, and hold short restrictions when an aircraft
will be required to hold short of a runway or other points
along the taxi route.
|
|
c. Specify the runway for departure, taxi instructions,
and hold short restrictions when an aircraft will be
required to hold short of a runway or other points along
the taxi route.
|
|
EXAMPLE-
“Runway Three Six Left, taxi via taxiway Alpha, hold
short of taxiway Charlie.”
or
“Runway Three Six Left, taxi via Alpha, hold short of
Charlie.”
|
|
No Change
|
|
PHRASEOLOGY-
RUNWAY (number),
TAXI/PROCEED VIA (route if necessary,
HOLD SHORT OF (runway number)
or
HOLD SHORT OF (location)
or
ON (taxi strip, runup, pad, etc.),
and if necessary,
TRAFFIC (traffic information),
or
FOR (reason).
|
|
PHRASEOLOGY-
RUNWAY (number),
TAXI/PROCEED VIA (route),
HOLD SHORT OF (runway number)
or
HOLD SHORT OF (location)
or
ON (taxi strip, runup, pad, etc.),
and if necessary,
TRAFFIC (traffic information),
or
FOR (reason).
|
|
EXAMPLE-
“Runway Three Six Left, taxi via taxiway Charlie, hold
short of Runway Two Seven Right.”
or
“Runway Three Six Left, taxi via Charlie, hold short of
Runway Two Seven Right.”
“Runway Three Six Left, hold short of Runway Two Seven
Right.”
|
|
EXAMPLE-
“Runway Three Six Left, taxi via taxiway Charlie, hold
short of Runway Two Seven Right.”
or
“Runway Three Six Left, taxi via Charlie, hold short of
Runway Two Seven Right.”
Delete
|
|
d through NOTE
|
|
No Change
|
|
e. Issue progressive taxi/ground movement
instructions when:
|
|
No Change
|
|
1. Pilot/operator requests.
|
|
1. A pilot/operator requests.
|
|
2. The specialist deems it necessary due to traffic or
field conditions, e.g., construction or closed taxiways.
|
|
No Change
|
|
3. As necessary during reduced visibility, especially
when the taxi route is not visible from the tower.
|
|
3. Necessary during reduced visibility, especially
when the taxi route is not visible from the tower.
|
|
f. Progressive ground movement instructions include
step‐by‐step routing directions.
|
|
Delete
|
|
Add
|
|
NOTE-
Progressive instructions may include step-by-step
directions and/or directional turns.
|
|
REFERENCE-
FAAO JO 7110.65, Para 3-7-4, Runway Proximity.
FAAO JO 7110.65, Para 3-11-1, Taxi and Ground Movement
Operation.
|
|
No Change
|
|
g. Instructions to expedite a taxiing aircraft or a
moving vehicle.
|
|
f. Issue instructions to expedite a taxiing aircraft or a
moving vehicle.
|
|
PHRASEOLOGY-
TAXI WITHOUT DELAY (traffic if necessary).
EXIT/PROCEED/CROSS
(runway/taxiway) WITHOUT DELAY.
|
|
No Change
|
1. PARAGRAPH NUMBER AND TITLE: 3-9-9. TAKEOFF CLEARANCE
2. BACKGROUND: The Federal Aviation Administrator's Call to Action Workgroup made numerous recommendations
to enhance runway safety. ATO-T Safety and Operations Support assembled a Safety Risk Management (SRM) Panel to
address some of the proposals from this workgroup. This change provides a requirement for controllers when a takeoff
clearance can be issued. The panel did a safety assessment on takeoff procedures at tower controlled airports and found no
high risks associated with this change.
3. CHANGE:
|
OLD
|
|
NEW
|
|
3-9-9. TAKEOFF CLEARANCE
|
|
3-9-9. TAKEOFF CLEARANCE
|
|
Title through aREFERENCE
|
|
No Change
|
|
b. If the takeoff clearance is issued before the aircraft
has crossed all intersecting runways, restate the runway
to be crossed with the takeoff clearance.
|
|
b. The controller shall ensure that all runways
along the taxi route that lead to the departure runway
are crossed before the takeoff clearance is issued,
except in subpara c.
|
|
PHRASEOLOGY-
CROSS RUNWAY (number), RUNWAY (number)
CLEARED FOR TAKEOFF.
|
|
No Change
|
|
EXAMPLE-
“CROSS RUNWAY TWO FOUR LEFT, RUNWAY
TWO FOUR RIGHT, CLEARED FOR TAKEOFF.”
|
|
No Change
|
|
c. USA/USN. Issue surface wind and takeoff
clearance to aircraft.
|
|
c. At those airports where the airport configuration
does not allow for an aircraft to completely cross one
runway and hold short of the departure runway
and/or where airports do not have runway hold
markings between runways, state the runway to be
crossed with the takeoff clearance if the aircraft is not
able to complete a runway crossing before reaching
its departure runway.
|
|
PHRASEOLOGY-
WIND (surface wind in direction and velocity).
CLEARED FOR TAKEOFF.
|
|
Delete
|
|
Add
|
|
FIG 3-9-12
Runway/Taxiway Proximity
|
|
Add
|
|
FIG 3-9-13
Runway/Taxiway Proximity
|
|
Add
|
|
REFERENCE-
FAAO JO 7210.3, Para 10-3-9, Takeoff Clearance.
P/CG Term- Clear of the Runway.
|
|
Add
|
|
PHRASEOLOGY-
CROSS RUNWAY (number), RUNWAY (number)
CLEARED FOR TAKEOFF.
|
|
Add
|
|
EXAMPLE-
“CROSS RUNWAY ONE SIX LEFT, RUNWAY ONE
SIX RIGHT, CLEARED FOR TAKEOFF.”
|
|
d. USAF. When an aircraft is cleared for takeoff,
inform it of the closest traffic within 6 miles on final
approach to the same runway. If the approaching aircraft
is on a different frequency, inform it of the departing
aircraft.
|
|
No Change
|
|
Add
|
|
e. USA/USN. Issue surface wind and takeoff
clearance to aircraft.
|
|
Add
|
|
PHRASEOLOGY-
WIND (surface wind in direction and velocity).
CLEARED FOR TAKEOFF.
|
1. PARAGRAPH NUMBER AND TITLE: 8-7-4. LATERAL SEPARATION, 8-8-4. LATERAL SEPARATION
2. BACKGROUND: In 1998, lateral separation was reduced to 50 nautical miles (NM) in conjunction with the
introduction of Required Navigation Performance 10 (RNP 10) for aircraft operating in the North Pacific Route System.
Since that time, application of 50 NM lateral separation and RNP 10 has been expanded throughout the Pacific Flight
Information Regions (FIR). Effective June 5, 2008, this reduced lateral separation minimum was authorized for qualified
aircraft operating on specified oceanic routes or areas in the New York Oceanic Control Area (CTA), the San Juan CTA/FIR,
and the Atlantic portion of the Miami Oceanic CTA/FIR.
3. CHANGE:
|
OLD
|
|
NEW
|
|
8-7-4. LATERAL SEPARATION
|
|
8-7-4. LATERAL SEPARATION
|
|
In accordance with Chapter 8, Offshore/Oceanic
Procedures,
Section 4, Lateral Separation,
apply the following:
|
|
No Change
|
|
Add
|
|
a. 50 NM between Required Navigation
Performance (RNP 4 or RNP 10) approved aircraft
which:
|
|
Add
|
|
1. Operate on routes or in areas within WATRS,
the San Juan CTA/FIR or the Atlantic portion of the
Miami Oceanic CTA/FIR; or
|
|
Add
|
|
2. Operate in the New York Oceanic CTA/FIR
outside of WATRS.
|
|
Add
|
|
NOTE-
This reduced lateral separation shall not be used if
track-keeping capability of the aircraft has been
reduced for any reason.
|
|
a. 60 NM or 1 degree latitude between:
|
|
b. 60 NM or 1 degree latitude between:
|
|
1. Supersonic aircraft operating above FL 275.
|
|
No Change
|
|
2. Aircraft which meet the MNPS and which:
|
|
No Change
|
|
NOTE-
This reduced lateral separation shall not be used if track
keeping capability of the aircraft has been reduced for
any reason.
|
|
Delete
|
|
(a) Operate within MNPS airspace; or
|
|
No Change
|
|
(b) Are in transit to or from MNPS airspace; or
|
|
No Change
|
|
(c) Operate for part of their flight within, above, or
below MNPS airspace.
|
|
No Change
|
|
Add
|
|
NOTE-
This reduced lateral separation shall not be used if
track-keeping capability of the aircraft has been
reduced for any reason.
|
|
b. 90 NM or 1 and 1/2 degrees latitude between aircraft
operating:
|
|
c. 90 NM or 1 and 1/2 degrees latitude between aircraft
not approved for RNP 4 or RNP 10 and which:
|
|
1. Within WATRS;
|
|
1. Operate on routes or in areas within WATRS,
the San Juan CTA/FIR or the Atlantic portion of the
Miami CTA/FIR;
|
|
2. Between the U.S., Canada, and Bermuda;
|
|
2. Operate between points in the U.S. or Canada,
and Bermuda;
|
|
3. West of 55° West between the U.S., Canada, or
Bermuda and points in the Caribbean ICAO Region.
|
|
3. Operate west of 55° West between the U.S.,
Canada, or Bermuda and points in the Caribbean ICAO
Region.
|
|
c. 120 NM or 2 degrees latitude between aircraft not
covered by subparas a or b above.
|
|
d. 120 NM or 2 degrees latitude between aircraft not
covered by subparas a, b or c above.
|
|
NOTE-
Tracks may be spaced with reference to their difference
in latitude, provided that in any interval of 10 degrees of
longitude the change in latitude of at least one of the
tracks does not exceed 3 degrees when operating south
of 58°North.
|
|
No Change
|
|
OLD
|
|
NEW
|
|
8-8-4. LATERAL SEPARATION
|
|
8-8-4. LATERAL SEPARATION
|
|
Provide lateral separation by assigning different flight
paths whose widths or protected airspace do not overlap.
Apply the following:
|
|
In accordance with Chapter 8, Offshore/Oceanic
Procedures, Section 4, Lateral Separation, apply the
following:
|
|
Add
|
|
a. 50 NM between Required Navigation
Performance (RNP 4 or RNP 10) approved aircraft
which:
|
|
Add
|
|
1. Operate on routes or in areas within WATRS,
the San Juan CTA/FIR or the Atlantic portion of the
Miami Oceanic CTA/FIR; or
|
|
Add
|
|
2. Operate in the New York Oceanic CTA/FIR
outside of WATRS.
|
|
Add
|
|
NOTE-
This reduced lateral separation shall not be used if
track-keeping capability of the aircraft has been
reduced for any reason.
|
|
a. 60 NM:
|
|
b. 60 NM between:
|
|
1. Supersonic aircraft operating above FL 275 within
the New York oceanic CTA/FIR.
|
|
No Change
|
|
2. Supersonic aircraft operating at or above FL 450
not covered in subpara 1 above.
|
|
No Change
|
|
NOTE-
This reduced lateral separation shall not be used if track
keeping capability of the aircraft has been reduced for
any reason.
|
|
Delete
|
|
3. Aircraft which meet the MNPS and while
operating in the New York oceanic CTA/FIR which are
in transit to or from NAT MNPS airspace.
|
|
3. Aircraft which meet the MNPS and which:
|
|
Add
|
|
(a) Operate within MNPS airspace; or
|
|
Add
|
|
(b) Are in transit to or from MNPS airspace; or
|
|
Add
|
|
(c) Operate for part of their flight within, above,
or below MNPS airspace.
|
|
Add
|
|
NOTE-
This reduced lateral separation shall not be used if
track-keeping capability of the aircraft has been
reduced for any reason.
|
|
b. 90 NM between aircraft operating:
|
|
c. 90 NM between aircraft not approved for RNP 4 or
RNP 10 and which:
|
|
1. Within WATRS;
|
|
1. Operate within WATRS; or
|
|
2. West of 55° West between the U.S., Canada, or
Bermuda and points in the Caribbean ICAO Region.
|
|
2. Operate west of 55° West between the U.S.,
Canada, or Bermuda and points in the Caribbean ICAO
Region.
|
|
c. 100 NM between aircraft operating west of 55°West
not covered by subparas b or c above.
|
|
d. 100 NM between aircraft operating west of 55°West
not covered by subparas a, b or c above.
|
|
d. 120 NM between aircraft operating east of 55°West.
|
|
e. 120 NM between aircraft operating east of 55°West.
|
1. PARAGRAPH NUMBER AND TITLE:
Appendix A. Aircraft Information FIXED-WING AIRCRAFT
2. BACKGROUND: This change adds new model descriptions and new aircraft type designators as approved by the
International Civil Aviation Organization (ICAO). A LAHSO Group for DeHavilland DH8D is also added.
3. CHANGE:
|
OLD
|
|
NEW
|
|
Appendix A. Aircraft Information
FIXED-WING AIRCRAFT
|
|
Appendix A. Aircraft Information
FIXED-WING AIRCRAFT
|
|
|
|
See Appendix A for specific changes.
|
|
