Hi Dave,

it seems to me that P2A is not enforcing airway altitude restrictions at all. For example on my last flight I had a flight plan with cruise altitude FL420, but the first 100 nm or so were on an airway with an altitude restriction of FL305. This was a flight plan exported by SimBrief, in SimBrief itself the cruise altitude in the dispatch output showed as 'FL290' (in the briefing details it was FL STEPS LOWI/0290/VAMTU/0410/DIVKO/0310) and P2A imported it as FL420. When I filed the flight plan it was valid (green), andP2A correctly showed the restrictions in the Alt Restr column:

 

 

After getting the clearance for FL240 I would have expected the next one to be for FL305 (I was still long way before VAMTU), but P2A cleared me to FL360 (and later to FL420). Before reaching VAMTU I leveled off at FL305 myself, but then had to endure constant nagging to expedite my climb to FL360. So my question is - should such airway restrictions (here a step climb which is not part of a SID) work in P2A, or is this not supported? I have encountered the same in similar situations, where some airway segment in the middle of the flight plan had a lower restriction than the current cruise altitude, and in this case I also did not get any warning/instructions from P2A either... 

Oh and yes I have 'Ignore airway altitude restrictions' disabled in the FltPlan settings.

 

Thanks,

Dirk

 

 

Edited June 6, 20215 yr by woodstock327

 More bizarre is that you filed FL420. Westbound alts should be FL400 or FL430, if you wanted 42,000 you could ask for a block of 410-430. 

  As for the airway restrictions, if I was cleared to FL360 along that route with the FL305 restriction, I would assume that ATC had completed any needed coordination to do so. I definitely wouldn't stop at FL305, as you are then infringing on protected airspace for both FL300 and FL310.

14 minutes ago, Dave_YVR said:

More bizarre is that you filed FL420. Westbound alts should be FL400 or FL430, if you wanted 42,000 you could ask for a block of 410-430. 

As I said, I did not file or input FL420, it was P2A that imported the flight plan as FL420, based on the altitudes exported by SimBrief

15 minutes ago, Dave_YVR said:

As for the airway restrictions, if I was cleared to FL360 along that route with the FL305 restriction, I would assume that ATC had completed any needed coordination to do so

Sure one could explain this with 'ATC has completed any needed coordination', but I've never seen P2A consider such airway restrictions on any of my flights, hence my question whether it's simply not implemented / supported

 

19 minutes ago, Dave_YVR said:

I definitely wouldn't stop at FL305, as you are then infringing on protected airspace for both FL300 and FL310

Yeah, should have chosen FL290 (as the SimBrief briefing told me)...

P2A does not "enforce" airway altitude restrictions like it does SID and STAR restrictions.  You can set your initial cruise altitude to one that adheres to the first altitude restrictions and then request higher or lower altitudes as required for the following restrictions.

Flight Level altitude separation of 2000 ft for bearing based altitudes above FL410 is coming soon.

Dave

Edited June 6, 20215 yr by Dave-Pilot2ATC

1 hour ago, Dave-Pilot2ATC said:

P2A does not "enforce" airway altitude restrictions like it does SID and STAR restrictions.

That's what I wanted to know, thanks for clarifying Dave!

Dirk