Narrative:

There is an error in the amylu RNAV STAR into chs. If you reference the arrival; this will be clearer. On the descent into chs; the altitude restrictions on the bamde transition from amylu are 'at or above' until you actually talk to chs approach and they assign you a final and a runway. However; in our case today; if you get handed off late to approach you can be on vpath and then have them assign you an approach and; when you select the approach; be immediately 6;000 feet high. The problem is that the bamde altitude needs to be a hard altitude or a window; say 5;000 feet to 3;000 feet. As it is; either 3;001 feet or 10;999 feet satisfies the arrival programming. All other ending altitudes that I find on RNAV arrivals are hard altitudes. Even the other transitions on the amylu arrival have hard altitudes as final altitudes; i.e. Kreis at 3;000 feet; wablo at 3;000 feet; and kmbee at 4;000 feet.today we found ourselves in this position and had to ask for and execute a 360-degree turn to lose enough altitude to shoot the RNAV rnp Z to 21. In accordance with the procedure; approach control assigns the approach and runway and; until they do that; you have a discontinuity from the end of the arrival to the approach. It is this discontinuity that causes the FMC to not descend at the proper rate so as to be in a position to execute the approach.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B737-700 Captain believes the crossing altitude depicted at BAMDE waypoint (at or above 3;000 feet); on the AMYLU RNAV STAR for arrivals to Runway 21 at CHS; is inappropriate and should be a hard altitude to prevent arriving aircraft from being too high to continue the approach.

Narrative: There is an error in the AMYLU RNAV STAR into CHS. If you reference the arrival; this will be clearer. On the descent into CHS; the altitude restrictions on the BAMDE transition from AMYLU are 'at or above' until you actually talk to CHS Approach and they assign you a final and a runway. However; in our case today; if you get handed off late to Approach you can be on VPATH and then have them assign you an approach and; when you select the approach; be immediately 6;000 feet high. The problem is that the BAMDE altitude needs to be a hard altitude or a window; say 5;000 feet to 3;000 feet. As it is; either 3;001 feet or 10;999 feet satisfies the arrival programming. All other ending altitudes that I find on RNAV arrivals are hard altitudes. Even the other transitions on the AMYLU Arrival have hard altitudes as final altitudes; i.e. KREIS at 3;000 feet; WABLO at 3;000 feet; and KMBEE at 4;000 feet.Today we found ourselves in this position and had to ask for and execute a 360-degree turn to lose enough altitude to shoot the RNAV RNP Z to 21. In accordance with the procedure; Approach Control assigns the approach and runway and; until they do that; you have a discontinuity from the end of the arrival to the approach. It is this discontinuity that causes the FMC to not descend at the proper rate so as to be in a position to execute the approach.

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.