Ray Proudfoot 231 Posted January 15, 2019 Share Posted January 15, 2019 Yesterday I planned a flight from ENGM to EKCH. Learjet 25 which can cruise up to FL450. I looked at the SID and decided it was taking a long route so selected another with the same exit point but a slightly different departure routing. The cruise level was shown as 110 which is absurd. I tried it again today and went with the SID selected by PFPX and the cruise level was 390. Far better. Why would manually selecting an almost identical SID have such an effect? Departure was 01L. Link to comment Share on other sites More sharing options...
Kevin_H. 1 Posted January 16, 2019 Share Posted January 16, 2019 I have the same Problem. I try to Plan a Flight vom LOWG to LOWW The Routing from LOWG to LOWW is "ROPAG DCT NIGSI" Therefor i plan the whole Flight, then click on Edit to change the Runways, SID and STARS I enter 17C as Departure Runway with ROPAG3G SID In Vienna i choose Runway 29 for Arrival with NIGSI1W arrival and 30 Miles Circuit IN Then when i click on Compute PFPX gives me this Flightplan : (FPL-AUA3456-IS -B738/M-SDE1FGHIJ1RWXYZ/LB1 -LOWG1000 -N0254A030 ROPAG DCT NIGSI -LOWW0037 LZIB -PBN/A1B1C1D1L1O1S1 NAV/RNVD1E2A1 DOF/190116 REG/OELNQ RVR/200 PER/C -E/0127) 3000 Feet is for sure NOT correct and this results in Error Messages !! Link to comment Share on other sites More sharing options...
srcooke 422 Posted January 16, 2019 Share Posted January 16, 2019 There is a known issue with the SID/STAR length automatic selection, it may be that this is linked to that same issue. Link to comment Share on other sites More sharing options...
Ray Proudfoot 231 Posted January 16, 2019 Author Share Posted January 16, 2019 I generated the same flight this morning and departing 01R or 01L to the same SID point gave acceptable flight levels. I'll keep trying until I can generate the problem then will post flight details. No point until I have hard evidence. Link to comment Share on other sites More sharing options...
srcooke 422 Posted January 16, 2019 Share Posted January 16, 2019 I could reproduce Kevin's error and when using the Find Route function a SID is not selected whereas it should be, the low altitude is also then returned. The altitude issue certainly looks to be related to this function not working correctly. Link to comment Share on other sites More sharing options...
Kevin_H. 1 Posted January 16, 2019 Share Posted January 16, 2019 And this is really annoying.. Is there a Way that the Devs can fix this Issue ? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.