{"id":21670,"date":"2015-07-16T06:30:38","date_gmt":"2015-07-16T11:30:38","guid":{"rendered":"http:\/\/www.universalweather.com\/blog\/?p=21670"},"modified":"2024-01-31T12:15:14","modified_gmt":"2024-01-31T18:15:14","slug":"faas-data-comm-program-overview-and-effects-for-operators","status":"publish","type":"post","link":"https:\/\/www.universalweather.com\/blog\/faas-data-comm-program-overview-and-effects-for-operators\/","title":{"rendered":"FAA’s Data Comm Program: Overview and Effects for Operators"},"content":{"rendered":"

The Federal Aviation Administration’s (FAA’s) Data Comm program will change how operators receive flight plans and, to a certain extent, the manner in which flight plans are uplinked. It’s important to be aware of these changes as they went into effect as of June 2015.<\/p>\n

The following is an overview of what you need to know:<\/p>\n

1. New program basics<\/h2>\n

The Data Comm program uses a combination of Controller Pilot Data Link Communications (CPDLC) and pre-departure clearance (PDC) technology to enhance communications between the flight deck and air traffic control. It’s part of a baseline for other technologies that will be implemented in the future. These Data Comm changes cover items such as clearances, instructions, flight crew requests\/reports, and even traffic flow management.<\/p>\n

2. Program objectives<\/h2>\n

The Data Comm program is the first phase of NextGEN<\/a> and is a part of other traffic management improvements the FAA plans to implement downline. The objective is to improve safety, reduce traffic delays throughout the system, and maximize fuel savings by decreasing departure\/arrival delays.<\/p>\n

3. Implementation and timeline<\/h2>\n

The first phase went into effect in June 2015, at certain U.S. airports. This will eventually be rolled out nationwide in different stages. Segment one of phase one covers tower communication services. This will be followed by segment one of phase two which encompasses enroute and advanced services. Note that phase one changes will not impact general aviation but only apply to scheduled commercial airlines on a voluntary basis. Operators participating in this trial phase must ensure proper coding for International Civil Aviation Organization (ICAO) sections of their flight plans. More information can be found on the FAA’s website for Data Comm Implementation Team (DCIT)<\/a>.<\/p>\n

4. DCL considerations<\/h2>\n

Departure clearances (DCLs) will be a method to uplink clearances when a flight plan does not match the flight plan on your flight management system. You’ll be able to accept, reject, or standby the flight plan as needed.<\/p>\n

5. DCL requirements<\/h2>\n

To use DCL services, both the FAA and users need to meet certain ICAO flight plan requirements. FAA will support initial and amendment flight plan filings based on ICAO 2012 flight plan requirements<\/a>. Users must file ICAO 4444 flight plans<\/a> \u2013 essentially an ICAO 2012 flight plan \u2013 to use CPDLC DCL services. Operators must indicate, 45-60 minutes prior to departure, if they’ll use PDC or CPDLC DCL.<\/p>\n

6. CPDLC requirements<\/h2>\n

Operators must be CPDLC-equipped to use Data Comm. If you do not have CPDLC, you may use PDC for the time being. Be mindful that when this program is complete (currently estimated at the end of 2016), all aircraft operating in U.S. airspace will need to be CPDLC-equipped to use Data Comm.<\/p>\n

7. Flight plan requirements<\/h2>\n

Your ICAO flight plan must be filled out as follows:<\/p>\n

    \n
  1. Aircraft identification\n
      \n
    1. Field 7a (where the tail number or call sign will be placed)<\/li>\n<\/ol>\n<\/li>\n
    2. Aircraft equipage capabilities\n
        \n
      1. Field 10a (such as MNPS, RVSM, HF, datalink, CPDLC, FANS, etc.)<\/li>\n<\/ol>\n<\/li>\n
      2. Other information\n
          \n
        1. Aircraft registration number\n
            \n
          1. Field 18 REG\/(is where the actual aircraft registry will be placed)\n
              \n
            1. Used if Field 7a is not the aircraft registration number (if 7a is the call sign and not the registration number)<\/li>\n
            2. This item is required for CPDLC DCL service<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n
            3. Preference for clearance delivery mechanism\n
                \n
              1. Field 18 DAT\/(this is the type of datalink the aircraft has)\n
                  \n
                1. To indicate the operator’s preference for PDC or CPDLC DCL<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

                  8. Additional flight plan notations<\/h2>\n

                  Note that you must indicate the following additional information in the ICAO section of your flight plan to indicate CDPLC DCL or PDC clearance. Bold areas below are items that affect clearance type:<\/p>\n