|
|
|
|
|
|
|
|
Air Traffic Control (7110.65) | ATC | Effective: | 07-15-99 | Updated: | 04-02-99 |
---|
a. Arrivals:
Information recorded on the flight progress strips (FAA Forms 7230-7.1, 7230-7.2, and 7230-8) shall be entered in the correspondingly numbered spaces. Facility managers can authorize omissions and/or optional use of spaces 2A , 9A, and 10-18, if no misunderstanding will result. These omissions and/or optional uses shall be specified in a facility directive.
Block | Information Recorded |
1. | Aircraft identification. |
2. | Revision number (FDIO locations only). |
2A. | Strip request originator. (At FDIO locations this indicates the sector or position that requested a strip be printed.) |
3. | Number of aircraft if more than one, TCAS/ heavy aircraft indicator if appropriate, type of aircraft, and aircraft equipment suffix. The TCAS indicator is "T/" and the heavy aircraft indicator is "H/". For aircraft that are both TCAS and heavy, the indicator is "B/". For B757, the indicator is "F/" and for B757 with TCAS, the indicator is "L/". |
4. | Computer identification number if required. |
5. | Secondary radar (beacon) code assigned. |
6. | (FDIO Locations.) The previous fix will be printed.
|
7. | Coordination fix. |
8. | Estimated time of arrival at the coordination fix or destination airport. |
Block | Information Recorded |
8A. | OPTIONAL USE, when voice recorders are operational;
|
9. | Altitude (in hundreds of feet) and remarks. |
NOTE | Altitude information may be written in thousands of feet provided the procedure is authorized by the facility manager, and is defined in a facility directive, i. e., FL 230 as 23, 5,000 feet as 5, and 2,800 as 2.8. |
9A. | Minimum fuel, destination airport/point out/radar vector/speed adjustment information. Air Traffic managers may authorize in a facility directive the omission of any of these items, except minimum fuel, if no misunderstanding will result. |
NOTE | Authorized omissions and optional use of spaces shall be specified in the facility directive concerning strip marking procedures. |
10-18. | Enter data as specified by a facility directive. Radar facility personnel need not enter data in these spaces except when nonradar procedures are used or when radio recording equipment is inoperative. |
b. Departures:
Information recorded on the flight progress strips (FAA Forms 7230-7.1, 7230-7.2, and 7230-8) shall be entered in the correspondingly numbered spaces. Facility managers can authorize omissions and/or optional use of spaces 2A , 9A, and 10-18, if no misunderstanding will result. These omissions and/or optional uses shall be specified in a facility directive.
Block | Information Recorded |
1. | Aircraft identification. |
2. | Revision number (FDIO locations only). |
2A. | Strip request originator. (At FDIO locations this indicates the sector or position that requested a strip be printed.) |
3. | Number of aircraft if more than one, TCAS/ heavy aircraft indicator if appropriate, type of aircraft, and aircraft equipment suffix. The TCAS indicator is "T/" and the heavy aircraft indicator is "H/". For aircraft that are both TCAS and heavy, the indicator is "B/". For B757, the indicator is "F/" and for B757 with TCAS, the indicator is "L/". |
4. | Computer identification number if required. |
5. | Secondary radar (beacon) code assigned. |
6. | Proposed departure time. |
7. | Requested altitude. |
NOTE | Altitude information may be written in thousands of feet provided the procedure is authorized by the facility manager, and is defined in a facility directive, i. e., FL 230 as 23, 5,000 feet as 5, and 2,800 as 2.8. |
8. | Departure airport. |
Block | Information Recorded |
8A. | OPTIONAL USE, when voice recorders are operational;
|
9. | Computer-generated: Route, destination, and remarks. Manually enter altitude/altitude restrictions in the order flown, if appropriate, and remarks. |
9. | Hand-prepared: Clearance limit, route, altitude/altitude restrictions in the order flown, if appropriate, and remarks. |
NOTE | Altitude information may be written in thousands of feet provided the procedure is authorized by the facility manager, and is defined in a facility directive, i. e., FL 230 as 23, 5,000 feet as 5, and 2,800 as 2.8. |
9A. | Point out/radar vector/speed adjustment information. |
10-18. | Enter data as specified by a facility directive. Items, such as departure time, runway used for takeoff, check marks to indicate information forwarded or relayed, may be entered in these spaces. |
c. Overflights:
Information recorded on the flight progress strips (FAA Forms 7230-7.1, 7230-7.2, and 7230-8) shall be entered in the correspondingly numbered spaces. Facility managers can authorize omissions and/or optional use of spaces 2A , 9A, and 10-18, if no misunderstanding will result. These omissions and/or optional uses shall be specified in a facility directive.
Block | Information Recorded |
1. | Aircraft identification. |
2. | Revision number (FDIO locations only). |
2A. | Strip request originator. (At FDIO locations this indicates the sector or position that requested a strip be printed.) |
3. | Number of aircraft if more than one, TCAS/ heavy aircraft indicator if appropriate, type of aircraft, and aircraft equipment suffix. The TCAS indicator is "T/" and the heavy aircraft indicator is "H/". For aircraft that are both TCAS and heavy, the indicator is "B/". For B757, the indicator is "F/" and for B757 with TCAS, the indicator is "L/". |
4. | Computer identification number if required. |
5. | Secondary radar (beacon) code assigned. |
6. | Coordination fix. |
7. | Overflight coordination indicator (FDIO locations only). |
NOTE | The overflight coordination indicator identifies the facility to which flight data has been forwarded. |
8. | Estimated time of arrival at the coordination fix. |
Block | Information Recorded |
8A. | OPTIONAL USE, when voice recorders are operational;
|
9. | Altitude and route of flight through the terminal area. |
NOTE | Altitude information may be written in thousands of feet provided the procedure is authorized by the facility manager, and is defined in a facility directive, i. e., FL 230 as 23, 5,000 feet as 5, and 2,800 as 2.8. |
9A. | Point out/radar vector/speed adjustment information. |
10-18. | Enter data as specified by a facility directive. |
NOTE-
National standardization of items (10 through 18) is not practical because of regional and local variations in operating methods; e.g., single fix, multiple fix, radar, tower en route control, etc..
d. Air traffic managers at automated terminal radar facilities may waive the requirement to use flight progress strips provided:
1. Backup systems such as multiple radar sites/systems or single site radars with CENRAP are utilized.
2. Local procedures are documented in a facility directive. These procedures should include but not be limited to:
(a) Departure areas and/or procedures.
(b) Arrival procedures.
(c) Overflight handling procedures.
(d) Transition from radar to nonradar.
(e) Transition from ARTS to non-ARTS.
(f) Transition from ASR to CENRAP.
(g) Transition to or from ESL.
3. No misunderstanding will occur as a result of no strip usage.
4. Unused flight progress strips, facility developed forms and/or blank notepads shall be provided for controller use.
5. Facilities shall revert to flight progress strip usage if backup systems referred to in subpara a. are not available.
e. Air traffic managers at FDIO locations may authorize reduced lateral spacing between fields so as to print all FDIO data to the left of the strip perforation when using FAA form 7230-7.2. all items will retain the same relationship to each other as they do when the full length strip (FAA form 7230-7.1) is used.
GO TO TOP OF PAGE |
---|