Section 2. Sector Information Binders
6-2-1. EN ROUTE
CONTROLLER TEAM CONCEPT
a. There
are no absolute divisions of responsibilities regarding position
operations. The tasks to be completed remain the same whether one,
two, or three people are working positions within a facility/sector.
The team, as a whole, has the responsibility for the safe and
efficient operation of that facility/sector.
b. The
intent of the team concept is not to hold the team accountable for the
action of individual members in the event of an operational
error/deviation.
6-2-2. EN ROUTE
SECTOR INFORMATION BINDER
The en route
sector information outline is to be used for guidance in developing
facility sector binders for each sector of operation. The pertinent
items in subpara a thru subpara e below must be incorporated into each
sector binder. The format of the binder must be determined by the air
traffic manager and must contain all information necessary for the
safe and efficient operation of each sector. A sector specific binder
is required for each operational sector and is to be in a location
easily accessible by each position/sector.
a. Sector
Narrative: General description of normal traffic flows and adjacent
sector/facility coordination and potential trouble spots.
b. Assignment
of airspace:
1. Delegation
of Approach Control airspace.
2. Sectors
normally combined.
EXAMPLE-
Which sector assumes responsibility when combined or which sector
assumes responsibility for approach control airspace.
3. Military
airspace delegation.
c. Sector
Information.
1. Frequency
Information.
(a) Primary
frequency.
(b) Back-up
frequency.
(c) Primary
and back-up frequency remote communications air-ground facility (RCAG).
(d) Back-up
emergency communication (BUEC) operation priorities.
(e) Position
location.
(f) Location
of emergency frequencies and RCAG.
(g) Special
Use frequencies and RCAG.
2. Indirect
access (IA) dial codes.
3. Sector
Description (map, video map, and/or narrative).
(a) Lateral
limits.
(b) Vertical
limits.
4. Specify
unique sector equipment configurations.
d. Sector
Procedures.
1. Sector
specific directives.
2. LOAs
or LOA procedures applicable to that sector.
3. Areas
of limited radio/radar coverage.
4. Mandatory
speed restrictions.
5. Mandatory
heading requirements.
6. Mandatory
altitude requirements.
7. Sector
handoff/point out procedures if different from requirements of FAAO JO
7110.65, Air Traffic Control, Chapter 5, Section 4, Transfer of Radar
Identification.
8. Transfer
of control points other than airspace boundaries.
9. Radar
arrival routes and restrictions for airports within facility/sector
jurisdiction.
10. Normally
used sector holding fixes to include published/unpublished hold,
allowable altitudes, maximum speed, maximum length, direction of turn,
direction from fix, and if applicable, published procedures involved.
11. Special
strip or flight data requirements of sector.
12. Authorized
jump areas in Class A airspace within area of jurisdiction.
13. Special routes for dangerous cargo or
inert devices flights in area of jurisdiction.
14. Sensitive/classified
activities to be avoided by special interest flights.
15. IFR
Military Training Routes (IR) in area of jurisdiction.
16. Aerial
refueling routes, including air refueling initial point (ARIP), air
refueling control point (ARCP), and egress fix(es).
17. Special
use and ATC assigned airspace within area of jurisdiction.
e. Flight
Data Requirements.
1. Primary
and back-up printers.
2. Alternative
methods for relaying/requesting information.
3. Data
that requires expeditious handling including, flight plan data,
weather information, traffic management messages, and miscellaneous
data.
4. Specify
flight progress strips to be posted and the location to place them.
5. Sources
to obtain weather information.
6. Sources
and data required for display in SIAs. |