7110.65 Updated

[Bradley Grafelman]

(notwithstanding the 'expect filed altitude 10 minutes after departure)

But that's the key here, innit?

If your average groundspeed from runway 25R to SHEAD was 250 knots, it would take you almost right at 10 minutes to get to SHEAD. Considering you've got an extra 45 NM to get from SHEAD to DBIGE (the AoA FL210, which also happens to be the MEA between SHEAD and DBIGE)... the FL190 is a non-issue; either you're with CTR and they've either climbed you higher, canceled the restriction, or vectored you for holding... or you aren't with CTR because this is VATSIM and CTR isn't always online, in which case you execute the lost comms procedure of climbing to your filed altitude.

[Bradley Grafelman]

From a "Climb Via/Descend Via" FAQ published by FAASafety here:

[!--quoteo--][div class=\\\'quotetop\\\']QUOTE [/div][div class=\\\'quotemain\\\'][!--quotec--]8. Q. I am cleared to “Climb Via SID”. What if there is a published altitude restriction at a fix that is higher than the charted “Top Altitude” ?
A. You are only cleared to the charted “Top Altitude” contained in the narrative of the procedure, unless ATC assigns a different altitude.[/quote]

[Brad Littlejohn]

From a "Climb Via/Descend Via" FAQ published by FAASafety here:

This implies that the altitude in the description would be the highest an aircraft could go without ATC overriding it with another call to climb.

So for all intents and purposes, both L30 and ZLA would have to go NORDO for something like this to take place. I wondr if they'll update the charts to reflect this, or if it would be mentioned in an LOA between, say, ZLA and ZOA as to what happens should this occur.

BL.