welchb21 20 Posted January 15, 2013 Share Posted January 15, 2013 Hello Staff, I have installed the latest version 1.03B plus the Hotfix 002, and I noticed today on a flight from KEWR to KMIA (route used:BIGGY J75 CAE J51 SAV J103 OMN ANNEY2) that the Arrival Altitude restrictions were completely ignored and missing. I noticed this in the HILEY4 arr and the ANNEY2 arr, below are pictures to illustrate what I mean with the ANNEY2 arr. As you can see, per the ANNEY2 arr, you are supposed to cross PHORD at FL240 but it has me descending from FL380 at 12NM out, and ANNEY should have a constraint block of 11000-13000 but it doesnt have any and I added it in manually but Manual constraints are still not being recognised nor followed by the aircaft. The HILEY4 arrival now has all the waypoints but it does not have the block ALT constraints for MILSY of 13000-16000 or BTOGA of 11000-13000. Hope this can be looked into and changed with the next patch/update. thanks for the help and as always great aircraft. Link to comment Share on other sites More sharing options...
Joshua Che. 1601 Posted January 16, 2013 Share Posted January 16, 2013 Hello Staff, I have installed the latest version 1.03B plus the Hotfix 002, and I noticed today on a flight from KEWR to KMIA (route used:BIGGY J75 CAE J51 SAV J103 OMN ANNEY2) that the Arrival Altitude restrictions were completely ignored and missing. I noticed this in the HILEY4 arr and the ANNEY2 arr, below are pictures to illustrate what I mean with the ANNEY2 arr. As you can see, per the ANNEY2 arr, you are supposed to cross PHORD at FL240 but it has me descending from FL380 at 12NM out, and ANNEY should have a constraint block of 11000-13000 but it doesnt have any and I added it in manually but Manual constraints are still not being recognised nor followed by the aircaft. The HILEY4 arrival now has all the waypoints but it does not have the block ALT constraints for MILSY of 13000-16000 or BTOGA of 11000-13000. Hope this can be looked into and changed with the next patch/update. thanks for the help and as always great aircraft. I have noted this. Thanks for informing, There is indeed a bug on this, but the MCDU developer(I work with him) is on vacation, I will keep you informed once he is back. Link to comment Share on other sites More sharing options...
welchb21 20 Posted January 16, 2013 Author Share Posted January 16, 2013 sounds great thanks for looking at it, cant wait to have this fixed :-) -cheers Link to comment Share on other sites More sharing options...
PeterW 23 Posted January 16, 2013 Share Posted January 16, 2013 As you can see, per the ANNEY2 arr, you are supposed to cross PHORD at FL240 but it has me descending from FL380 at 12NM out, and ANNEY should have a constraint block of 11000-13000 but it doesnt have any and I added it in manually but Manual constraints are still not being recognised nor followed by the aircaft. The HILEY4 arrival now has all the waypoints but it does not have the block ALT constraints for MILSY of 13000-16000 or BTOGA of 11000-13000. Hope this can be looked into and changed with the next patch/update. thanks for the help and as always great aircraft. The aircraft not following the constraints is a bug (as Josuha said). The "missing" constraint blocks for ANNEY and MILSY is not really a bug. As you can see on the chart it is not a block, but a fixed altitude which depends on the landing direction. But as we only have one STAR here for all runways it is not possible to code it in the navdata. A "between" would not be correct and depending on which "at" altitude you choose it would be wrong for the other landing direction. You can manually enter an AT altitude constraint when you know your landing runway. Link to comment Share on other sites More sharing options...
welchb21 20 Posted January 16, 2013 Author Share Posted January 16, 2013 yes I realize that and I do but the MCDU does not recognize manual constraints thus it does not give the proper descent profile, it only makes the descent profile for the first constraint that is preprogrammed into the system. Once they get it so that Manual constraints will be recognized and followed then this issue will be solved but until they can do that, it would be nice to have a built in constraint for them points so that I can have the correct descent path calculated. Link to comment Share on other sites More sharing options...
PeterW 23 Posted January 16, 2013 Share Posted January 16, 2013 As Joshua said, this bug is known But the navdata is correct. We cannot add incorrect information to the navdata Link to comment Share on other sites More sharing options...
welchb21 20 Posted January 16, 2013 Author Share Posted January 16, 2013 ok I understand about the constraints that are "missing" but on the ANNEY2 arrival PHORD has a preprogrammed Alt constraint of FL240 which you can see in my posted pic, what I dont understand is why it is not being recognised as usually the preprogrammed constraints are recognised. I just installed the latest hotfix, I will put this route in again and see if it calculates the TD better to cross PHORD at FL240. Thanks for the information and help. Link to comment Share on other sites More sharing options...
PeterW 23 Posted January 16, 2013 Share Posted January 16, 2013 what I dont understand is why it is not being recognised as usually the preprogrammed constraints are recognised. Because there is a bug in the Airbus I have noted this. Thanks for informing, There is indeed a bug on this, but the MCDU developer(I work with him) is on vacation, I will keep you informed once he is back. Link to comment Share on other sites More sharing options...
welchb21 20 Posted January 16, 2013 Author Share Posted January 16, 2013 ah ok sorry missunderstood thanks again Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.