2-3-4. TERMINAL DATA ENTRIES

  • Views Views: 8
  • Last updated Last updated:
  • 2-3-4. TERMINAL DATA ENTRIES

    1. Arrivals: Information recorded on the flight progress strips (FAA Forms 7230-7.1, 7230-7.2, and 7230-8) must be entered in the correspondingly numbered spaces.

      Facility managers can authorize omissions and/or optional use of spaces 2A, 8A, 8B, 9A, 9B, 9C, and 10-18, if no misunderstanding will result. These omissions and/or optional uses must be specified in a facility directive.

    2. FIG 2-3-4
      Terminal Flight Progress Strip
      TBL 2-3-3
      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, heavy aircraft indicator “H/” if appropriate, type of aircraft, and aircraft equipment suffix.
      4. Computer identification number if required.
      5. Secondary radar (beacon) code assigned.
      6. (FDIO Locations.) The previous fix will be printed.
      (Non-FDIO Locations.) Use of the inbound airway. This function is restricted to facilities where flight data is received via interphone when agreed upon by the center and terminal facilities.
      7. Coordination fix.
      8. Estimated time of arrival at the coordination fix or destination airport.
      8a. OPTIONAL USE.
      8b. OPTIONAL USE, when voice recorders are operational;
      REQUIRED USE, when the voice recorders are not operating and strips are being used at the facility. This space is used to record reported RA events when the voice recorders are not operational and strips are being used at the facility. The letters RA followed by a climb or descent arrow (if the climb or descent action is reported) and the time (hhmm) the event is reported.
      Block Information Recorded
      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 must be specified in the facility directive concerning strip marking procedures.

      9b. OPTIONAL USE.
      9c. OPTIONAL USE.
      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.
    3. 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, 8A, 8B, 9A, 9B, 9C, and 10-18, if no misunderstanding will result. These omissions and/or optional uses shall be specified in a facility directive.

    4. FIG 2-3-5
      Terminal Flight Progress Strip
      TBL 2-3-4
      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, heavy aircraft indicator “H/” if appropriate, type of aircraft, and aircraft equipment suffix.
      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.
      8a. OPTIONAL USE.
      8b. OPTIONAL USE, when voice recorders are operational;
      REQUIRED USE, when the voice recorders are not operating and strips are being used at the facility. This space is used to record reported RA events when the voice recorders are not operational and strips are being used at the facility. The letters RA followed by a climb or descent arrow (if the climb or descent action is reported) and the time (hhmm) the event is reported.
      Block Information Recorded
      9. Computer-generated: Route, destination, and remarks. Manually enter altitude/altitude restrictions in the order flown, if appropriate, and remarks.
      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. OPTIONAL USE.
      9b. OPTIONAL USE.
      9c. OPTIONAL USE.
      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.
    5. 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, 8A, 8B, 9A, 9B, 9C, and 10-18, if no misunderstanding will result. These omissions and/or optional uses shall be specified in a facility directive.

    6. FIG 2-3-6
      Terminal Flight Progress Strip
      TBL 2-3-5
      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, heavy aircraft indicator “H/” if appropriate, type of aircraft, and aircraft equipment suffix.
      4. Computer identification number if required.
      5. Secondary radar (beacon) code assigned.
      6. Proposed departure time.
      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.
      8b. OPTIONAL USE, when voice recorders are operational;
      REQUIRED USE, when the voice recorders are not operating and strips are being used at the facility. This space is used to record reported RA events when the voice recorders are not operational and strips are being used at the facility. The letters RA followed by a climb or descent arrow (if the climb or descent action is reported) and the time (hhmm) the event is reported.
      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. OPTIONAL USE.
      9b. OPTIONAL USE.
      9c. OPTIONAL USE.
      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.

    7. 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:
        1. (a) Departure areas and/or procedures.
        2. (b) Arrival procedures.
        3. (c) Overflight handling procedures.
        4. (d) Transition from radar to nonradar.
        5. (e) Transition from ARTS to non-ARTS.
        6. (f) Transition from ASR to CENRAP.
        7. (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 d1 are not available.
    8. 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.
Top