 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Captain of a part 121 turbojet reported difficulties interfacing via cpdlc with ATC.
| Attributes | |
| ACN | 1485088 |
| Time | |
| Date | 201709 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | BIRD.ARTCC |
| State Reference | FO |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Large Transport |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Communication Systems |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Type 190 |
| Events | |
| Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
While operating on nat X; cpdlc and passing zzzzz to bird flight information region (fir) boundary; we received two ATC alerts - (white ATC EICAS message and audible ding). First ATC alert at xa:41; selecting ATC button on FMC; cpdc message was: this is an automated message to confirm cpdlc with reykjavik centre. We sent our response: 'roger.' less than a minute later; received a second alert at xa:42: 'confirm assigned route.' we responded by selecting the prompts to confirm route 1; and sent the response.just to verify that all was well; I selected the ATC log page; which details all received and sent ATC messages. This is when we found an unanswered ATC message - also sent at xa:42- directing us to 'squawk ZZZZ.' we answered the message with 'roger' and changed our squawk; so no real failure to follow ATC instructions occurred. What I wanted to point out with this report is that there were three messages sent from ATC within one minute - only two messages displayed when the ATC prompt was selected on the FMC; and if we had not investigated the log page further; we would not have known that ATC had sent a third message directing the new squawk. This is a potential safety point of failure; since it is not in our normal process to constantly check the log page to make sure that we are getting all our messages.
Original NASA ASRS Text
Title: Captain of a Part 121 turbojet reported difficulties interfacing via CPDLC with ATC.
Narrative: While operating on NAT X; CPDLC and passing ZZZZZ to BIRD Flight Information Region (FIR) boundary; we received two ATC alerts - (white ATC EICAS message and audible ding). First ATC alert at XA:41; selecting ATC button on FMC; CPDC message was: This is an automated message to confirm CPDLC with Reykjavik Centre. We sent our response: 'Roger.' Less than a minute later; received a second alert at XA:42: 'Confirm assigned route.' We responded by selecting the prompts to confirm Route 1; and sent the response.Just to verify that all was well; I selected the ATC log page; which details all received and sent ATC messages. This is when we found an unanswered ATC message - also sent at XA:42- directing us to 'Squawk ZZZZ.' We answered the message with 'roger' and changed our squawk; so no real failure to follow ATC instructions occurred. What I wanted to point out with this report is that there were three messages sent from ATC within one minute - only two messages displayed when the ATC prompt was selected on the FMC; and if we had not investigated the LOG page further; we would not have known that ATC had sent a third message directing the new squawk. This is a potential safety point of failure; since it is not in our normal process to constantly check the LOG page to make sure that we are getting all our messages.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.