Section
5. Coordination
17-5-1. COORDINATION
Coordinate
through verbal and automated
methods. At times, it may be
required to utilize both
methods to ensure complete
communication and situational
awareness.
17-5-2. COMMUNICATION
When time
permits, utilize communication
techniques that emphasize
collaboration and consensus
decision-making. Use tools
that provide for common
situational awareness to the
extent possible.
17-5-3. DOCUMENTATION
The
National Traffic Management
Log (NTML) is utilized to
record TM activities in the
facility. It does not replace
the facility log; however it
may be utilized as the
facility log when documented
in a facility directive.
Facilities with the NTML are
required to make data entries.
At non-NTML facilities, the
first facility overlying the
non-NTML facility is
responsible for entering the
NTML entries. This enables all
facilities to be knowledgeable
of conditions throughout the
NAS.
17-5-4. RESPONSIBILITIES
a. All
facilities must:
1. Communicate
and coordinate events that may
have an impact on the NAS.
2. Use
the NTML to document events
and traffic management
initiatives (TMI).
b. The
ATCSCC must:
1. Provide
an FAA ATCSCC data entry web
page for facilities identified
in TBL 17-5-1, Aviation System
Performance Metrics Airport
Traffic Control Towers.
2. Transmit
these data to other FAA
offices for analysis.
3. Provide
the NTML to all ARTCC TMUs and
designated terminals.
4. Communicate
directly with facility and
service area representatives
for a critique of operations
and future plans for TM.
5. Coordinate
directly with service area
representatives on plans,
procedures, and operations
that affect interfacility
traffic flows.
6. Consult
with weather information
providers to ensure the
receipt of timely weather
forecasts (including the
collaborative convective
forecast), observed terminal
weather sequences, and any
weather data that may have a
significant impact on the NAS.
7. Coordinate
with the TMUs in the
day-to-day operations of the
NAS and resolve operational TM
disagreements between
facilities.
8. Conference
affected ARTCC TMUs as needed
when contacted by a terminal
facility.
9. Initiate
telecons and Hotlines with
customers and facilities, as
necessary, to obtain input and
to provide operational
information, as well as other
significant events affecting
the NAS.
10. Subscribe
to the NTML entries pertinent
to its position of operation.
c. ARTCC
TMUs and designated terminals
must:
1. Advise
the ATCSCC of situations and
conditions that may require
implementation of TMIs or are
of national interest.
2. Present
unresolved conflicts between
adjacent TMUs to the ATCSCC
for resolution.
3. Notify
the ATCSCC if a significant
change in capacity is expected
or has occurred.
4. Be
the contact for their
underlying facilities about
coordinating any TM issues,
initiatives, programs, or
information. Data received
from underlying facilities
must be forwarded to the
ATCSCC in a timely manner.
5. Advise
the ATCSCC if an operational
Hotline is requested
including:
(a) Facility
participation required.
(b) Requested
customer participation and
assist the ATCSCC in
determining if the Hotline
will be limited to
“listen-only” customer
capability.
(c) Other
aviation/airport resources
requested.
d. Terminal
facilities must:
1. Coordinate
with the appropriate ARTCC TMU
and ensure it is kept aware of
situations and conditions that
may require the implementation
of TM initiatives.
2. Report
to the ARTCC TMU any
significant change in capacity
that is expected or has
occurred.
3. Present
TM conflicts to the ARTCC TMU.
4. Consult
with the ATCSCC, the affected
ARTCC TMU, terminals, and
customer organizations about
the development and
implementation of procedures,
when appropriate.
e. Terminal
facilities listed in TBL
17-5-1 must:
1. Enter
the runway configurations
(specifying runway numbers)
and their associated AAR and
ADR using the NTML.
NOTE-
Local procedures must be
established to determine
whether the tower or TRACON is
responsible for these entries.
2. Enter
the hourly arrival and
departure counts starting at
0700 and ending at 2259 local
using the ATCSCC-supplied web
page.
NOTE-
These counts must include IFR/VFR
arrivals and departures that
are fixed wing itinerants.
Helicopter and local
operations must not be
included in the traffic count.
3. Investigate
and resolve issues about their
web page.
4. Submit
suggestions for improvement to
the Terminal Operations area
office, when applicable.
f. The
information for subpara e
above applies to any airport
in a ground delay program.
g. Field
facility specialists with the
NTML must:
1. Enter
sign on/off times and
initials.
2. Mark
entries for equipment (E) when
they cause a TMI or result in
a TMI.
3. Mark
entries for a QAR with a (Q)
when they cause a TMI or
result in a TMI.
4. Enter
TMIs initiated by your
facility.
5. Enter
constraints in your area of
responsibility that may impact
the NAS and forward them to
the ATCSCC.
6. Enter
arrival, departure, and en
route delay status, as
appropriate.
7. Enter
deicing status (in/out).
NOTE-
Facilities with the NTML are
required to make the above
data entries. At non-NTML
facilities, the first facility
overlying the non-NTML
facility is responsible for
entering data into the NTML.
Facility personnel must enter
data in a timely manner on the
appropriate template. Timely
is construed to mean that it
would be useful to someone
looking at the data in current
time. If workload conditions
or the situation prohibits
entering the data in a timely
manner, the information should
be recorded by a subsequent or
delayed entry.
TBL 17-5-1
AVIATION SYSTEM
PERFORMANCE METRICS
AIRPORT TRAFFIC CONTROL
TOWERS |
ABQ
ANC
ATL
AUS
BDL
BHM
BNA
BOS
BUF
BUR
BWI
CLE
CLT
CVG
DAL
DAY |
DCA
DEN
DFW
DTW
EWR
FLL
GYY
HNL
HOU
HPN
IAD
IAH
IND
ISP
JAX
JFK |
LAS
LAX
LGA
LGB
MCI
MCO
MDW
MEM
MHT
MIA
MKE
MSP
MSY
OAK
OGG
OMA |
ONT
ORD
OXR
PBI
PDX
PHL
PHX
PIT
PSP
PVD
RDU
RFD
RSW
SAN
SAT
SDF |
SEA
SFO
SJC
SJU
SLC
SMF
SNA
STL
SWF
TEB
TPA
TUS
VNY |
17-5-5. STATIC COORDINATION
a. The
ATCSCC must collect and manage
updates for ASPM facilities'
static data, currently
depicted in the NTML and on
the Operational Information
System (OIS) under the
associated ARTCC tabs in the
East and West Directories.
b. The
TMO or overlying TMO, in
conjunction with their ASPM
facilities, must provide the
following static data to their
appropriate Manager of
Tactical Operation (MTO) and
ensure the accuracy of the
information:
1. For
NTML airport information: All
normal runway configurations
and their associated AARs/ADRs
by April 30, August 31, and
December 31 of each year.
NOTE-
AARs are required for the
following four categories:
Visual meteorological
conditions (VMC), low visual
meteorological conditions (LVMC),
instrument meteorological
conditions (IMC), and low
instrument meteorological
conditions (LIMC).
2. For
OIS airport information:
Monthly changes to the
following ASPM airport data no
later than the last day of the
month:
(a) Normal
runway configuration and
associated AARs/ADRs
(b) Suggested
program rate
(c) Pertinent
notes
(d) Holding
capacities
(e) Arrival
flows
(f) Category
minimums
3. Changes
to TM Tips by the first of
every month:
(a) Configuration
instructions/planning
(b) Airport
operational challenges
(c) Seasonal
traffic information
(d) Gate
hold information
(e) Special
arrival instructions
(f) Other
pertinent information related
to airspace, procedures,
weather operations, local
traffic management
initiatives, taxiway
information, and any other
items that impact traffic
flows or runway
acceptance/configuration
c. The
MTO must provide:
1. All
normal runway configurations
and the associated AARs/ADRs
for their underlying ASPM
facilities to the ATCSCC
Facility Automation Office by
May 15 and November 15 each
year.
2. Changes
to additional supporting AAR
data and TM tips for their
underlying ASPM facilities to
the ATCSCC Facility Automation
Office by the 10th of each
month.
17-5-6. EN ROUTE
INTRA-FACILITY COORDINATION
a. The
STMC must ensure that an
operational briefing is
conducted at least once during
the day and evening shifts.
Participants must include, at
a minimum, operational
supervisors and other
interested personnel
designated by the facility
management. Discussion at this
meeting should include:
1. Planning
TELCON checklist.
2. Operations
Plan.
3. Topics
pertinent to the facility.
b. Coordination
between the TMU and Operations
Supervisor (OS): In some
facilities, the TM function
may be performed by the OS or
as designated by the air
traffic manager. Timely
coordination between the OS
and TMU is paramount in not
only implementing TM
initiatives, but also in
evaluating the effectiveness
of any initiatives.
17-5-7. TERMINAL
INTER-FACILITY COORDINATION
a. Coordination
between tower and TRACON TMUs: Towers
that are not collocated with a
TRACON TMU must coordinate
with the appropriate TMU where
the TM function has been
established. If the TM
function has not been
established, then the tower
must coordinate with the
appropriate en route TMU.
b. Coordination
between the TMU and ATCSCC
NTMSs: Unusual circumstances
or significant issues do not
preclude the terminal TMU from
contacting the ATCSCC
directly.
c. Coordination
between the TMU and the local
NWS or CWSU must be completed
as soon as practical at the
beginning of each shift, and,
as necessary, the TMU must
obtain a weather briefing from
the NWS.
d. Coordination
between the TMU and the
adjacent terminal: Timely
coordination is imperative in
order to manage the efficiency
of the tower en route control
(TEC) environment. Any TM
initiatives imposed between
two (2) or more adjacent
terminals that could have an
impact on the capacity of any
airport, sector, or ARTCC must
be coordinated with the
appropriate ARTCC TMU.
17-5-8. NATIONAL TRAFFIC
MANAGEMENT LOG (NTML)
a. Facility
personnel must enter data in a
timely manner on the
appropriate template and
verbally coordinated when
required. Timely is construed
to mean that it would be
useful to someone looking at
the data in current time. If
workload conditions or the
situation prohibits entering
the data in a timely manner,
the information should be
recorded by a subsequent or
delayed entry or on the
appropriate form. Substantive
changes in the contents or
remarks or additional
explanatory information should
be accomplished by a
subsequent or delayed entry.
b. The
data in NTML will be subject
to FAA security provisions for
Internet technology.
Facilities must use the NTML
in preference to other
methods. The NTML is an
automated FAA Form 7230-4,
Daily Record of Facility
Operation, and will record the
operating initials and
facility for all log entries.
Operating initials are removed
at the end of six months in
accordance with FAA
Order 1350.15, Records
Organization, Transfer, and
Destruction Standards.
c. The
NTML automatically closes and
reopens a new log each day; it
automatically records the
operating initials of the
person previously signed on.
Carryover items may be entered
by the specialist or
automatically be entered by
the software based on the
end/date/time group. Closing
and opening logs are
concurrent with each local
day; however, the entries are
made utilizing Coordinated
Universal Time.
d. When
it is necessary to amend a
previous entry, the original
entry may be corrected through
normal computer entries;
however, the database will be
automatically marked and the
information must be
retrievable by the system
administrator.
17-5-9. NTML
FACILITY CONFIGURATION
REQUIREMENTS
At least
one TMU position in each
facility must:
a. Subscribe
to DCC for TMIs affecting your
facility.
b. Subscribe
to underlying facilities for
the following information:
1. Runway
configurations.
2. Delays.
3. Deicing.
4. Other.
c. Enable
notification of proposed
restrictions.
17-5-10. NTML PROCEDURES
a. Facilities
must enter, review, and
respond to data in the NTML,
as appropriate.
b. TMI data must be entered using the appropriate
template and coordinated with the appropriate
facility. Appropriate template means the one best
suited for the type of event, such as a ground stop,
delays, etc. The “Miscellaneous” templates must not
be used if another template is appropriate. The
Justification, Remarks, and Text fields must not
contain any information that can be entered in other
fields on the template.
NOTE-
Causal information entered in
the “Restriction” template is
disseminated to many other
software programs for
monitoring the status of the
NAS.
c. Facilities
must verbally contact other
facilities when necessary to
accomplish a task if
electronic coordination has
not been completed or is
inappropriate to the
situation, e.g., emergencies,
classified information.
17-5-11. PROCESSING REQUESTS
FOR REROUTES AND RESTRICTIONS
FOR FACILITIES WITH NTML
a. Restrictions/modifications
that require ATCSCC review and
approval:
1. Requesting
facility must enter the
restriction/modification in
NTML.
2. Providing
facilities should review and
respond using NTML within 15
minutes.
NOTE-
The restriction/modification,
if not responded to, will be
placed in conference status 15
minutes after it has been
entered by the requesting
facility.
3. If
all providing facilities
accept the
restriction/modification using
the NTML software, the ATCSCC
must approve or deny the
restriction/modification as
appropriate. The ATCSCC may
deny/amend a restriction at
anytime; however, it must call
the requesting facility and
explain the reason for the
denial/amendment. For
automation purposes, the
ATCSCC should not approve a
restriction until all field
providers have accepted it;
however, if the ATCSCC elects
to override the automation and
approves a
restriction/modification
before all provider(s) accept,
it must coordinate this action
with the affected provider(s).
4. When
a restriction is in conference
status, the requestor must
initiate a conference through
the ATCSCC with providers. If
an amendment is necessary, the
ATCSCC amends and approves the
restriction while on the
conference.
NOTE-
Any party may initiate a
conference when deemed
appropriate.
b. Restrictions/modifications
that do not require ATCSCC
review and approval:
1. Requesting
facility must enter the
restriction/modification in
NTML.
2. Providing
facilities should review and
respond using NTML within 15
minutes.
3. If
all providing facilities
accept the
restriction/modification using
the NTML software, it must be
considered
coordinated/approved.
4. If
a providing facility does not
respond using the NTML within
15 minutes, the requesting
facility must contact the
providing facility/facilities
to verbally coordinate the
restriction/modification.
NOTE-
In the event that no one at
the providing facility is
available to accept a
restriction in NTML, the
requesting facility does have
the ability to force the
restriction into its log so it
can be used internally. This
must only be done after the
verbal coordination mentioned
in para 17-5-11b4 is complete.
c. Restrictions/modifications
associated with reroutes
coordinated through the ATCSCC:
1. Restrictions/modifications
that have been
approved/coordinated will be
discussed during the
development of the reroute.
2. Any
facility requiring a
restriction in conjunction
with a reroute that has been
coordinated through the ATCSCC
must enter the initiative into
the RSTN template with the SVR
WX RERTE button enabled. NTML
processes these restrictions
as approved and no further
coordination is required.
17-5-12. DELAY REPORTING
a. Verbally
notify the ATCSCC through the
appropriate protocol, of any
arrival, departure, or en
route delay reaching or
expected to reach 15 minutes
except for Expect Departure
Clearance Time (EDCT) delays
created by ground delay
programs or ground stops
issued by the ATCSCC. The
verbal notification must
include the number of aircraft
actually in delay, the
projected maximum delay, and
the number of aircraft
expected to encounter delays.
The facility must verbally
notify the ATCSCC and impacted
facilities when delays fall
below 15 minutes.
b. Facilities
must update their delay status
through the NTML. Facilities
that do not have NTML must
verbally report the delay
increments in 15-minute
increments to the overlying
facility. The first facility
with NTML must enter the delay
information.
c. When
notified that a facility is in
a 15-minute delay situation,
the ATCSCC and all impacted
facilities, must subscribe to
the delay report through the
NTML until the facility
verbally notifies the ATCSCC/impacted
facilities that they are no
longer in delays of 15 minutes
or more.
d. Facilities must verbally notify the ATCSCC,
through the appropriate protocol, when delays reach
or are anticipated to reach 90 minutes, except for
EDCT delays as a result of a GDP. Facilities must
document in their NTML, or daily log if the facility
does not have NTML, that the verbal notification was
completed. The ATCSCC must document in their
NTML that the 90-minute verbal notification was
received. The facility manager must be notified when
delays reach 90 minutes, except for delays as a result
of a GDP.
17-5-13. ELECTRONIC SYSTEM
IMPACT REPORTS
AT
facilities must coordinate
with their TMU or overlying
TMU for developing an
electronic system impact
report (SIR) for all planned
outages/projects/events that
could cause a significant
system impact, reduction in
service, or reduction in
capacity (for example, air
shows, major sporting events,
business conventions, runway
closures, and procedural
changes affecting terminals
and/or ARTCCs). Technical
Operations is responsible for
reporting all unplanned
outages that pertain to FAA
equipment.
NOTE-
Planned events/outages are
construed to mean that the
event or outage is scheduled
in advance of the occurrence.
a. The
TMU must coordinate the
operational impact the
outage/project/event will
cause with the MTO or
designee, through their TMO.
This includes, but is not
limited to, reduction in AAR/ADR,
anticipated TMIs, alternate
missed approach procedures,
and anticipated delays or any
other significant impacts
within the NAS.
b. To
ensure the ATCSCC receives all
planned events and outages
that could have a significant
impact on the NAS, the MTO/designee
or the OSG must enter the
impact data on the Strategic
Events Coordination Web site
at http://sec.faa.gov.
FIG
17-5-1
Electronic SIR Process

c. The
electronic SIR must contain
the following information:
1. Airport/facility
identifier.
2. Overlying
ARTCC.
3. Scheduled
dates/times.
4. Description
of outage/project/event.
5. Operational
impact.
6. Facility
recall.
7. Flight
check requirements.
8. Anticipated
delays.
9. Anticipated
TMIs.
10. Customer
coordination.
11. General
information.
12. Contact
information.
13. Date/time
of scheduled telecons.
NOTE-
SIRs cannot be viewed on the
OIS by facilities or our
customers until the ATCSCC has
approved the content.
Instructions for entering
items in detail are provided
on the Web site at http://sec.faa.gov.
d. The
ATCSCC will access the SIRs on
the SEC page, make
modifications as necessary,
and submit the SIR for
dissemination. Once the ATCSCC
has submitted the SIR, the
information can be viewed on
the intranet at http://www.atcscc.faa.gov/ois/
on the OIS page under “System
Impact Reports."
e. Field
facilities, TMUs, TMOs, MTOs,
the service center OSG, and
the ATCSCC must ensure that
SIRs:
1. Are
coordinated, developed, and
submitted with as much advance
notice as possible before the
planned event/outage.
NOTE-
Providing the SIR in a timely
manner allows our customers to
more effectively plan their
operation and reduce the
impact to the extent
practicable.
2. Do
not contain sensitive security
information.
17-5-14. TARMAC DELAY
OPERATIONS
a. Facility
Procedures. The ATCSCC, en
route facilities, and
affected terminal facilities
must develop procedures for
handling requests related to
tarmac delays for arriving
or departing aircraft. ATMs
must ensure that those
procedures are in a facility
directive and briefed
annually. Issues to consider
when developing local
procedures should include:
1. What
constitutes a “significant
disruption” of service at that
location in order to
accommodate a tarmac delay
aircraft. These issues vary by
location and may include but
are not limited to:
(a) Accommodating
a tarmac delay aircraft would
require airborne holding that
would result in delays of 15
minutes or more.
(b) Use
of an active runway to taxi a
tarmac delay aircraft that
would preclude the use of that
runway for arrivals or
departures and result in
arrival/departure delays of 15
minutes or more.
(c) Taxi
of tarmac delay aircraft would
result in placing other
aircraft in jeopardy of
violating the “Three/FourHour
Tarmac Rule.”
(d) Taxi
of tarmac delay aircraft would
displace departure aircraft
already in a reportable delay
status and result in delays in
excess of an additional 15
minutes.
(e) The
taxi of a tarmac delay
aircraft to the ramp, gate, or
alternate deplaning area would
result in a diversion or the
airborne holding of more than
three aircraft.
2. Operational
complexity, surface
operations, other
arrival/departure runways,
taxi routes, ramp areas, and
low visibility operations.
3. Security
and/or Customs concerns.
4. Local
safety considerations, such as
multiple runway crossings.
5. Location
of alternate deplanement
areas, if applicable.
6. Taxiway/runway
closures and/or airport
construction.
7. Notification,
coordination, and
investigation requirements.
b. Requirements.
1. When
a tarmac delay taxi request/deplanement
request is received, primarily
from the pilot in command:
(a) An
aircraft requesting taxi
clearance for tarmac delay
reasons should be issued
clearance as soon as
operationally practical,
unless a significant
disruption of airport
operations or a compromise of
safety or security would
result.
(b) Tower-only
and tower/TRACON facilities
must verbally notify the
overlying facility and
document the incident with
pertinent information on FAA
Form 7230-4 in CEDAR as a
QAR “Q" entry when:
(1) The
facility is informed of a
tarmac delay request or taxi
for deplanement related to
the “Three/Four-Hour Tarmac
Rule."
(2) The
facility becomes aware of an
aircraft that has or may
have exceeded the
“Three/Four–Hour Tarmac
Rule."
(c) TRACONs
must verbally notify the
overlying ARTCC TMU and
document the incident with
pertinent information
on FAA Form 7230-4 in CEDAR
as a QAR “Q" entry when:
(1) An
airport within their
geographic jurisdiction has
received a tarmac delay
request or taxi for
deplanement related to the
“Three/Four-Hour Tarmac
Rule."
(2) The
facility becomes aware of an
aircraft that has or may
have exceeded the
“Three/Four-Hour Tarmac
Rule."
(d) ARTCCs
must verbally notify the
ATCSCC and
document the incident with
pertinent information
on FAA Form 7230-4 in CEDAR
as a QAR “Q" entry when:
(1) An
airport within their
geographic jurisdiction has
received a tarmac delay
request or taxi for
deplanement related to the
“Three/Four-Hour Tarmac
Rule."
(2) The
facility becomes aware of an
aircraft that has or may
have exceeded the
“Three/Four-Hour Tarmac
Rule."
(e) Facilities
equipped with NTML should
utilize the program to
forward the information to
the TRACON/ARTCC/ATCSCC.
NOTE-
The QAR should be
comprehensive and include
pertinent information such
as date, time, location of
the occurrence, the
identification of the
aircraft involved, the time
a tarmac delay taxi request
was made, and other known
information concerning
movement of the aircraft.
Data used during the review
may include
ASDE data, flight progress
strips, voice replay, etc.
2. When
an ARTCC is notified that an
aircraft has or may have
exceeded the
“Three/FourHour Tarmac
Rule,” they must notify the
ROC as soon as possible; the
ROC must then notify the WOC
as soon as possible.
Notification should include
the date, time, and location
of the occurrence, as well
as the identification of the
aircraft involved.
3. When
a facility is notified that
an aircraft has or may have
exceeded the
“Three/Four-Hour Tarmac
Rule,” all available records
pertinent to that event will
be retained in accordance
with FAA Order JO 8020.16.
4. Consumer
complaints are to be handled
as follows:
(a) Refer
the complainant to the
appropriate airline.
(b) Do
not engage in discussion
with the consumer.
|