Narrative:

We were issued SIGMET B01 from iceland radio (ir) on VHF and contacted dispatch to get their advice since they had not given a heads up. A reply said we should not expect turbulence other than light. Then they sent a report of turbulence along the coast line of greenland. Then they sent a new SIGMET B02 which implied the SIGMET was now a concern. To play it safe; we decided to request a route change to try to avoid severe turbulence/mtn wave associated with SIGMET B02. We were moments away from n66w030 and needed to turn right approximately 45 degrees to avoid the area of concern; so we started to use cpdlc to make a request 'pp to n6730w030; then flight plan route'; but realized it would take a lot of typing to explain and send it. The first officer picked up the mike and asked iceland radio to get the clearance. Then we sent a similar/abbreviated cpdlc request. Iceland radio gave us the clearance and we made the turn. Cpdlc asked when we could accept FL350. A lot was going on right then with FMC changes; so I quickly sent a cpdlc request to climb to FL350; thinking that the new altitude may be important to bird. A clearance came back to climb; report leaving; and report level. The first officer told iceland radio (ir) we were departing FL340 for FL350; yet ir probably had no idea we had been cleared. We reported when level on the radio. Meanwhile the original cpdlc request for our 'time' to accept a climb was still open and the clearance to climb/report was still open. We had a difficult time trying to clear both at this point since the normal response flow was out of sequence. Iceland radio eventually told us we had cpdlc failure and instructed us to not log in to bird again. We complied by using only voice until out of bird airspace; eventually using cpdlc again with edmonton. The two methods of communication used; due to the seemingly urgent need to avoid the 'severe' and still comply with the actual clearances; became too complicated and confusing. I am confident we had both the route and altitude clearances prior to making the changes; yet I am sure that it was just as confusing on the other end for ATC. As captain; I need to ensure only one means of communication is primary. I should have waited on the altitude request until the current workload was complete.

Google
 

Original NASA ASRS Text

Title: B767 Captain is informed of sever turbulence ahead during a North Atlantic crossing while in VHF contact with BIRD and logged on with BIRD CPDLC. A deviation is requested using both VHF and CPDLC which results in confusion for both ATC and the flight crew.

Narrative: We were issued SIGMET B01 from Iceland Radio (IR) on VHF and contacted Dispatch to get their advice since they had not given a heads up. A reply said we should not expect turbulence other than light. Then they sent a report of turbulence along the coast line of Greenland. Then they sent a new SIGMET B02 which implied the SIGMET was now a concern. To play it safe; we decided to request a route change to try to avoid severe TURB/MTN wave associated with SIGMET B02. We were moments away from N66W030 and needed to turn right approximately 45 degrees to avoid the area of concern; so we started to use CPDLC to make a request 'PP to N6730W030; then flight plan route'; but realized it would take a lot of typing to explain and send it. The First Officer picked up the mike and asked Iceland Radio to get the clearance. Then we sent a similar/abbreviated CPDLC request. Iceland Radio gave us the clearance and we made the turn. CPDLC asked when we could accept FL350. A lot was going on right then with FMC changes; so I quickly sent a CPDLC request to climb to FL350; thinking that the new altitude may be important to BIRD. A clearance came back to climb; report leaving; and report level. The First Officer told Iceland Radio (IR) we were departing FL340 for FL350; yet IR probably had no idea we had been cleared. We reported when level on the radio. Meanwhile the original CPDLC request for our 'time' to accept a climb was still open and the clearance to climb/report was still open. We had a difficult time trying to clear both at this point since the normal response flow was out of sequence. Iceland Radio eventually told us we had CPDLC failure and instructed us to NOT log in to BIRD again. We complied by using only voice until out of BIRD airspace; eventually using CPDLC again with Edmonton. The two methods of communication used; due to the seemingly urgent need to avoid the 'severe' and still comply with the actual clearances; became too complicated and confusing. I am confident we had both the route and altitude clearances prior to making the changes; yet I am sure that it was just as confusing on the other end for ATC. As captain; I need to ensure only one means of communication is primary. I should have waited on the altitude request until the current workload was complete.

Data retrieved from NASA's ASRS site as of July 2013 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.