Narrative:

Why? Why? Why? Why? Why? Whhhhhhhhhhhhhy? Do we repeatedly file over ladix on our zbaa departures? The SID contains altitude restrictions that this aircraft cannot comply with! We are asked to cross AA176 at or above 9;850 feet only 16 miles from departure; generally at a weight exceeding 800;000 lbs! Now I don't know how other captain's do it nor do I know what scenario you guys at operations play with; but in my experience I know for a fact that this restriction is unachievable. I also do not have the bravery to play stupid and accept the SID on the 'hope' that departure will grant an unrestricted climb. In fact; in my experience; departure continually is asking that we climb as fast as we can and they also continually give us crossing restrictions that are not on the SID. Their desired departure for us is to use runway 01. Unfortunately; in order to preserve my ticket and accept a legal departure; we have to request the LADIX8A and runway 36R. Even so; at the best climb rate; crossing AA175 at FL236 is close. The communication gap with clearance delivery is atrocious and they do not understand anything other than yes or no; as to whether you can fly the SID. If you communicate and say; 'unable altitude restrictions' their response is 'can you fly the LADIX8E?' repeatedly. They don't understand. Why do we not file over tonil? The SID contains altitude restrictions that are achievable and allows me to keep my license and not have to write any reports! This is an ongoing frustration on departure. Sometimes it ends up resolved and being a non-event. Other times; like today it was a nightmare where clearance refused to release us even though our pre departure clearance acknowledged our request and amended our clearance to 36R/LADIX8A and merely said; 'expect a long; long delay. Call your operations.' when asked why; was told to 'call your operations.'

Google
 

Original NASA ASRS Text

Title: Widebody transport Captain reported he is regularly routed over LADIX on the LADIX8E departing ZBAA which contains a crossing restriction that is not achievable. The LADIX8A SID from Runway 36L is achievable; but is not acceptable to ATC. The reporter suggested the TONIL SID.

Narrative: WHY? WHY? WHY? WHY? WHY? WHHHHHHHHHHHHHY? do we repeatedly file over LADIX on our ZBAA departures? The SID contains altitude restrictions that this aircraft cannot comply with! We are asked to cross AA176 at or above 9;850 feet only 16 miles from departure; generally at a weight exceeding 800;000 lbs! Now I don't know how other Captain's do it nor do I know what scenario you guys at Operations play with; but in my experience I know for a fact that this restriction is unachievable. I also do not have the bravery to play stupid and accept the SID on the 'hope' that departure will grant an unrestricted climb. In fact; in my experience; Departure continually is asking that we climb as fast as we can and they also continually give us crossing restrictions that are not on the SID. Their desired departure for us is to use Runway 01. Unfortunately; in order to preserve my ticket and accept a legal departure; we have to request the LADIX8A and Runway 36R. Even so; at the best climb rate; crossing AA175 at FL236 is close. The communication gap with Clearance Delivery is atrocious and they do not understand anything other than YES or NO; as to whether you can fly the SID. If you communicate and say; 'unable altitude restrictions' their response is 'can you fly the LADIX8E?' repeatedly. They don't understand. Why do we not file over TONIL? The SID contains altitude restrictions that are achievable and allows me to keep my license and not have to write any reports! This is an ongoing frustration on departure. Sometimes it ends up resolved and being a non-event. Other times; like today it was a nightmare where Clearance refused to release us even though our PDC acknowledged our request and amended our clearance to 36R/LADIX8A and merely said; 'Expect a long; long delay. Call your operations.' When asked why; was told to 'call your operations.'

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.