October 9, 20223 yr I have Ignore Altitude Airway Altitude Restrictions OFF but when I import a SimBrief planned flight, Pilot2ATC is not sticking to the Altitude Restrictions, meaning that I have to edit them each time before flying. This is in the latest Beta. Am I doing something wrong or misreading the last column Pln Alt? Thanks, Toby Edited October 9, 20223 yr by toby23 Ryzen 5800X3D, 64GB RAM, RTX 4090, Windows 11Link to my: Dynamic Flight Dispatch Tool
October 10, 20223 yr Commercial Member I don't see a problem. all the restrictions are "Above" restrictions and all the planned altitudes are above the restricted altitude. Dave
October 10, 20223 yr Author I thought that would be the case. So I was reading this chart wrong and the 4500' and 2500' are minimum not mandatory altitudes? I was confused by the lack of underscore or lines above and below the altitudes but the only mandatory altitude on this approach is the FD28Z at 1700' right? Which is why Pilot2ATC has that one set to 1700'? Thanks for your help.. Edited October 10, 20223 yr by toby23 Ryzen 5800X3D, 64GB RAM, RTX 4090, Windows 11Link to my: Dynamic Flight Dispatch Tool
October 10, 20223 yr Commercial Member Actually, the 1700 is also an At or Above restriction, but to intercept the glide slope, you want to be at 1700. When you fly this approach, how you actually descend is up to you. P2A does not enforce the planned altitudes. Those are calculated based on the Descent Rate and GS you have entered in the flight plan. In reality, you would likely use a lower descent rate closer to the ground, I would shoot for getting to 4500 ft at the VOR and then descend to 2500 ft outbound and start my descent to 1700' inbound over D12.2. Dave
October 10, 20223 yr Author Thank you as always. Pilot2ATC is the best ATC out there! Ryzen 5800X3D, 64GB RAM, RTX 4090, Windows 11Link to my: Dynamic Flight Dispatch Tool
Archived
This topic is now archived and is closed to further replies.