2023-05 · NASA ASRS report 2004683
Air carrier flight crew reported receiving three CPDLC messages in less than two minutes during the arrival phase. The flight crew flew the routing and the descent clearances but failed to transmit the acknowledgment message to ATC.
In descent to MDW; we were handed off to a new ATC frequency via CPDLC acknowledged and checked in. MDW Center then sent us three CPDLC messages in less than two minutes. We received and acknowledged the first message to descend and maintain FL210. We heard the chime again and saw cross MEGGZ at 11;000 ft. I verified MEGGZ at 11;000 ft. in the FMC and on the MCP (Mode Control Panel) and thought that I acknowledged the CPDLC. We did not see the clearance to proceed direct MEGGZ which was sent also but in a separate message. We also had the ACARS chime in the midst of this for landing data as we were late to accomplish the Descent Checklist. As we were descending through FL200; ATC inquired if we had received the direct MEGGZ and the cross MEGGZ at 11;000 ft. messages; because ATC was not showing an acknowledgment from us. We responded that we had received the crossing MEGGZ at 11;000 ft.; but not the direct to MEGGZ. When we reviewed the CPDLC log page; we saw the direct to message which we hadn't acknowledged; and we saw that we hadn't actually acknowledged the descent to cross MEGGZ at 11;000 ft. either.First; with expectation bias; I was not thorough when I heard the chime and saw the ATC message to ensure I didn't have more than one open ATC message. I also missed verifying on second page of the notification that I accepted. We should have been finished with receiving landing data prior to this stage of flight. Two recommendations regarding CPDLC; the ATC message should remain or flash if a message wasn't acknowledged; and if there is any way that the audible chime could be different from an ACARS chime that would also be helpful.
About 20 miles south of PANGG through FL200; MDW Center called and asked if we received via CPDLC direct to MEGGZ and 11;000 ft. crossing restriction. We said that we received the crossing restriction but not the direct to MEGGZ. At the time of the communication; we were direct to PANGG; MEGGZ was next point on the arrival. We were set up to cross MEGGZ at 11;000 ft. When we looked back through the log; we noticed that the two clearances were sent separately and at the same time. As a crew we acknowledged the crossing restriction but did not select ACCEPT on page 2. We failed to see and respond to the direct to MEGGZ clearance. After the ATC prompt we accepted the crossing restriction that we were already performing and then proceeded to MEGGZ. No further incident.Need to continue to page 2 and accept. Need to make sure there are no new messages in the log. Aircraft should have an ATC message" voice notification or something other than the standard ACARS tone. In a descent when we are picking up weather and landing information; it is hard to differentiate between all the tones and becomes a distraction."
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.