End of Year News: Data Communications is 96.4% implemented

faa airport data communications
Share this article: FacebooktwitterlinkedinFacebooktwitterlinkedin

Airport Data Communications Abilities

FAA’s Goal Will Be Met Within Days

As 2016 comes to an end, thankfully, it is GREAT to get some positive news about the FAA and NextGen. Surprisingly, the source of the affirmative information is not the US DoT OIG, but can be found in THE BUSINESS OF FEDERAL TECHNOLOGY. Its writer Mark Rockwell wrote the following:

faa airport data communicationsWith 54 of 56 planned airports now equipped with Data Comms capabilities, the FAA is close to its goal of having the rollout completed by the end of 2016. It said on Dec. 9 capabilities at Chicago O’Hare and Midway were online. The two remaining airports, in Milwaukee and San Juan, “will be operational within days,” an FAA spokeswoman told FCW.

The Data Comms capabilities allow towers to send text messages to flight crews, which can cut through the sometimes dense voice radio communications between the two.

That’s a 96.4% closure rate against the goal.

The FAA explained the technical benefits of this text-based communications link between controllers and cockpits in this video: Data Comm – Quiet Communications Make-Over; Moving Aviation from Voice to Text.

And here is the FAA’s own scorecard on its performance on Data Comm implementation:

I. Airports

Data Comm service is operational at the following airport towers:

  • Albuquerque
  • Atlanta
  • Austin
  • Baltimore
  • Boston
  • Burbank
  • Charlotte
  • Chicago Midway
  • Chicago O’Hare
  • Cleveland
  • Dallas Fort Worth
  • Dallas Love
  • Denver
  • Detroit
  • Fort Lauderdale
  • Houston Bush
  • Houston Hobby
  • Indianapolis
  • Kansas City
  • Las Vegas
  • Los Angeles
  • Louisville
  • Memphis
  • Miami
  • Milwaukee
  • Minneapolis-St. Paul
  • Nashville
  • Newark
  • New Orleans
  • New York John F. Kennedy
  • New York LaGuardia
  • Oakland
  • Ontario
  • Orlando
  • Philadelphia
  • Phoenix
  • Pittsburgh
  • Portland
  • Raleigh-Durham
  • Sacramento
  • Salt Lake City
  • San Antonio
  • San Diego
  • San Francisco
  • San Jose
  • San Juan
  • Santa Ana
  • Seattle
  • Louis
  • Tampa
  • Teterboro
  • Washington Dulles
  • Washington Reagan
  • Westchester County
  • Windsor Locks (Bradley)

 

II. National Map

faa airport data communications

 

III. Schedule and Stats

List of capabilities and their implementation status

NOTE: The site milestones in the table below represent accelerated challenge dates which are ahead of the baseline milestones for the program.

Key Sites
Site Name Site ID ARTCC ID IOC (CY) Status
KS 1: Salt Lake City SLC ZLC

Q3 2015

Reason for date change at KS 1: Salt Lake City: Data Comm content in ERAM build delayed as ERAM Baseline finishes its deployment. Also addressing critical software PTR fixes.

Q2 2015
Baseline date

Q3 2015
Revised date

KS 2: Houston Intcl IAH ZHU Q3 2015
KS 3: Houston Hobby HOU ZHU Q3 2015
Key Sites
Site Name Site ID ARTCC ID IOC (CY) Status
New Orleans MSY ZHU Q1 2016
Austin AUS ZHU Q1 2016
San Antonio SAT ZHU Q1 2016
Los Angeles LAX ZLA Q1 2016
Las Vegas LAS ZLA Q1 2016
San Diego SAN ZLA Q2 2016
John Wayne SNA ZLA Q2 2016
Burbank BUR ZLA Q2 2016
Ontario ONT ZLA Q2 2016
San Francisco SFO ZOA Q2 2016
Oakland OAK ZOA Q2 2016
San Jose SJC ZOA Q3 2016
Sacramento SMF ZOA Q3 2016
Phoenix PHX ZAB Q3 2016
Albuquerque ABQ ZAB Q3 2016
Portland PDX ZSE Q3 2016
Seattle SEA ZSE Q3 2016
Dallas Love DAL ZFW Q4 2016
Dallas FTW (x2) DFW ZFW Q4 2016
Key Sites
Site Name Site ID ARTCC ID IOC (CY) Status
Louisville SDF ZID Q1 2016
Indianapolis IND ZID Q1 2016
Memphis MEM ZME Q2 2016
Nashville BNA ZME Q2 2016
Denver DEN ZDV Q2 2016
Atlanta ATL ZTL Q2 2016
Charlotte CLT ZTL Q2 2016
Orlando MCO ZJX Q3 2016
Miami MIA ZMA Q3 2016
Fort Lauderdale FLL ZMA Q3 2016
Tampa TPA ZMA Q3 2016
San Juan SJU ZMA Q4 2016
St. Louis STL ZKC Q4 2016
Kansas City MCI ZKC Q4 2016
Minn-St. Paul MSP ZMP Q4 2016
Key Sites
Site Name Site ID ARTCC ID IOC (CY) Status
Newark EWR ZNY Q1 2016
J F Kennedy JFK ZNY Q1 2016
LaGuardia LGA ZNY Q1 2016
Teterboro TEB ZNY Q1 2016
Westchester HPN ZNY Q2 2016
Philadelphia PHL ZNY Q2 2016
Boston BOS ZBW Q2 2016
Bradley BDL ZBW Q2 2016
Detroit DTW ZOB Q3 2016
Cleveland CLE ZOB Q3 2016
Pittsburgh PIT ZOB Q3 2016
Balt/Wash BWI ZDC Q3 2016
Dulles IAD ZDC Q3 2016
Reagan DCA ZDC Q3 2016
Raleigh/Durham RDU ZDC Q4 2016
Chicago Midway MDW ZAU Q4 2016
Chicago O’Hare ORD ZAU Q4 2016
Milwaukee MKE ZAU Q4 2016
Implementation Commitment
2014 2015 2016 2017 2018 2019
Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
Baselines-Segment 1 Phase 1 Tower Services and Segment 1 Phase 2 En Route Initial Services
DAL
DFW
MCI
MDW
MKE
MSP
ORD
RDU
SJU
STL
Initial Operating Capability (IOC) for Initial En Route Services at first Air Route Traffic Control Center (ARTCC)

• Implemented     On track

All dates are in calendar years.

Pre-Implementation Commitment
2014 2015 2016 2017 2018 2019
Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
Extend Departure Clearance Operational Trials
EWR
MEM
Final Investment Decision (FID) for En Route Services

INITIAL
SERVICES


FULL SERVICES
Reason for date change at FULL
SERVICES
: Due to budget uncertainty the FID approval for Full Services is delayed until Q3 2016.Q4 2015 Baseline dateQ3 2016 Revised date
Implementation Framework for non-VHF Digital Link (VDL) Mode 2 Media  

Implemented   On track

All dates are in calendar years.

Industry Commitments
2014 2015 2016 2017 2018 2019
Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
Airlines to Equip 1,900 Aircraft  
Assessment of Boeing 737 Flight Management Computer Issue  
Implementation Framework for non-VHF Digital Link (VDL) Mode 2 Media  
Industry Recommendation on Recorder Rule for Retrofit  

Implemented   On track

All dates are in calendar years.


CONGRATULATIONS FAA!

Share this article: FacebooktwitterlinkedinFacebooktwitterlinkedin

Be the first to comment on "End of Year News: Data Communications is 96.4% implemented"

Leave a comment

Your email address will not be published.