Narrative:

I was the [relief pilot] on this flight. Just before the landing; the crew returned from break we updated weather and everything looked normal for arrival and landing into zspd. Once the landing crew got in their seats; zspd approach started to give us a speed reduction and then eventually a delay turn to the north. Approach was very vague on the reason other than traffic. We flew north for some time and queried why. Eventually they turned us back towards arrival and we were told number 2 for landing and the reason was weather. Our weather radar wasn't painting anything that caused us concern. Our fuel by this time was getting close to bingo however we were assured that they will get us right in as we told approach fuel was critical. Once on the arrival the controller said 35 minute delay. This was not going to work for us so we told controller we will fly direct to our alternate of ZZZZ. He gave us a vector that was not direct and held us at a lower altitude. We then [advised ATC] and flew direct ZZZZ and continued our climb. This was caused by a communication problem with the controller. It was late into the arrival before we realized it was a weather delay. The controller did not understand our fuel situation and continued to lead us on. Even after we [advised them of the severity of the situation] he tried to vector us and keep us down low. Unacceptable considering our fuel state. Controllers in shanghai need to understand how to communicate with english carriers. They need to be very clear on the reasons for delays and real time expected delays. Dispatchers can help by being more proactive with information on flow into shanghai and expected delays. As we pass the south korean peninsula it would be nice to know how things are looking on the arrival. It's easier to stop in incheon for fuel than ZZZZ.

Google
 

Original NASA ASRS Text

Title: B787 First Officer reported the controllers at ZSPD did not convey the actual delays to be expected during arrival; and did not expedite a clearance to the alternate after being advised of the low fuel state.

Narrative: I was the [relief pilot] on this flight. Just before the landing; the crew returned from break we updated weather and everything looked normal for arrival and landing into ZSPD. Once the landing crew got in their seats; ZSPD approach started to give us a speed reduction and then eventually a delay turn to the north. Approach was very vague on the reason other than traffic. We flew north for some time and queried why. Eventually they turned us back towards arrival and we were told number 2 for landing and the reason was weather. Our weather radar wasn't painting anything that caused us concern. Our fuel by this time was getting close to bingo however we were assured that they will get us right in as we told approach fuel was critical. Once on the arrival the controller said 35 minute delay. This was not going to work for us so we told controller we will fly direct to our alternate of ZZZZ. He gave us a vector that was not direct and held us at a lower altitude. We then [advised ATC] and flew direct ZZZZ and continued our climb. This was caused by a communication problem with the controller. It was late into the arrival before we realized it was a weather delay. The controller did not understand our fuel situation and continued to lead us on. Even after we [advised them of the severity of the situation] he tried to vector us and keep us down low. Unacceptable considering our fuel state. Controllers in Shanghai need to understand how to communicate with English carriers. They need to be very clear on the reasons for delays and real time expected delays. Dispatchers can help by being more proactive with information on flow into Shanghai and expected delays. As we pass the South Korean Peninsula it would be nice to know how things are looking on the arrival. It's easier to stop in Incheon for fuel than ZZZZ.

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.