2-2-6. IFR FLIGHT PROGRESS DATA

  • Views Views: 10
  • Last updated Last updated:
  • 2-2-6. IFR FLIGHT PROGRESS DATA

    Forward control information from controller to controller within a facility, then to the receiving facility as the aircraft progresses along its route. Where appropriate, use computer equipment in lieu of manual coordination procedures. Do not use the remarks section of flight progress strips in lieu of voice coordination to pass control information. Ensure that flight plan and control information is correct and up-to-date. When covered by a letter of agreement/facility directive, the time requirements of subpara a may be reduced, and the time requirements of subpara b1 and para 2-2-11, Forwarding Amended and UTM Data, subpara a may be increased up to 15 minutes when facilitated by automated systems or mandatory radar handoffs; or if operationally necessary because of manual data processing or nonradar operations, the time requirements of subpara a may be increased.

    • NOTE:
    • 1. The procedures for preparing flight plan and control information related to altitude reservations (ALTRVs) are contained in FAA Order JO 7210.3, para 8-1-2, Facility Operation and Administration, ALTRV Flight Data Processing. Development of the methods for assuring the accuracy and completeness of ALTRV flight plan and control information is the responsibility of the military liaison and security officer.
    • 2. The term facility in this paragraph refers to centers and terminal facilities when operating in an en route capacity.
    1. Forward the following information at least 15 minutes before the aircraft is estimated to enter the receiving facility’s area:
      1. Aircraft identification.
      2. Number of aircraft if more than one, heavy aircraft indicator “H/” if appropriate, type of aircraft, and aircraft equipment suffix.
      3. Assigned altitude and ETA over last reporting point/fix in transferring facility’s area or assumed departure time when the departure point is the last point/fix in the transferring facility’s area.
      4. Altitude at which aircraft will enter the receiving facility’s area if other than the assigned altitude.
      5. True airspeed.
      6. Point of departure.
      7. Route of flight remaining.
      8. Destination airport and clearance limit if other than destination airport.
      9. ETA at destination airport (not required for military or scheduled air carrier aircraft).
      10. Altitude requested by the aircraft if assigned altitude differs from requested altitude (within a facility only).

        NOTE: When an aircraft has crossed one facility’s area and assignment at a different altitude is still desired, the pilot will re-initiate the request with the next facility.

      11. When flight plan data must be forwarded manually and an aircraft has been assigned a beacon code by the computer, include the code as part of the flight plan.

        NOTE: When an IFR aircraft, or a VFR aircraft that has been assigned a beacon code by the EAS and whose flight plan will terminate in another facility’s area, cancels ATC service or does not activate the flight plan, send a remove strips (RS) message on that aircraft via the EAS keyboard, the FDIO keyboard or call via service F.

      12. Longitudinal separation being used in non-radar operations between aircraft at the same altitude if it results in these aircraft having less than 10 minutes separation at the facilities’ boundary, unless (otherwise) specified in a Letter of Agreement (LOA).
      13. Any additional nonroutine operational information pertinent to flight safety.
      14. NOTE: EN ROUTE. This includes alerting the receiving controller that the flight is conducting celestial navigation training.

    2. Forward position report over last reporting point in the transferring facility’s area if any of the following conditions exist:
      1. Time differs more than 3 minutes from estimate given.
      2. Requested by receiving facility.
      3. Agreed to between facilities.
Top