MantisBT

View Revisions: Issue #291 All Revisions ] Back to Issue ]
Summary 0000291: Allow to predefine departure and landing runway
Revision 2017-07-10 00:34 by AdvMichael
Description This one is going through my mind for quite some time now. Currently the plugin is choosing the runways by some algorithm and the flow data, which however is not working perfectly well and therefore not reliable, for several reasons:

1) for landing: the plugin does only know the wind around the aircraft and not the ground winds at the arrival airport. The landing runway is calculated based on winds when still at high altitude, so using no suitable wind information.

2) there is no optimization regarding preferred runways, for example in EDDM there are 26L and 26R. For an arrival from south RW26L (or 08R) should be assigned by ATC in most cases, but the plugin does not properly consider this (see also ticket 0000280).

3) somtimes a grass runway is picked for airliners (see ticket 0000112) even there would be a better runway available. Maybe also related to incorrect airport data in Freeware scenery.

4) for departures also often not the optimal runway is choosen (same as for the landing as described in item 2)

5) sometime mistakes occur (see for example ticket 0000290), when the runway for approach is changed. I also noticed other issues, for example not enough time for descent, if the approach is shortened due to runway Change.

CONCLUSION:
As with actual flight planning tools usually the runways are already fixed during planning considering the actual winds at the time of planning, the plugin should provide the option to choose the runways manually, before they are fixed and announced by the plugin. This would have the advantages that all above mentioned items, which often break the immersion, could be simply avoided.

Revision 2017-07-09 23:47 by AdvMichael
Description This one is going through my mind for quite some time now. Currently the plugin is choosing the runways by some algorithm and the flow data, which however is not working perfectly well and therefore not reliable, for several reasons:

1) for landing: the plugin does only know the wind around the aircraft and not the ground winds at the arrival airport. The landing runway is calculated based on winds when still at high altitude, so using no suitable wind information.

2) there is no optimization regarding preferred runways, for example in EDDM there are 26L and 26R. For an arrival from south RW26L (or 08R) should be assigned by ATC in most cases, but the plugin does not properly consider this (see also ticket 0000280).

3) somtimes a grass runway is picked for airliners (see ticket 0000112) even there would be a better runway available. Maybe also related to incorrect airport data in Freeware scenery.

4) for departures also often not the optimal runway is choosen (same as for the landing as described in item 2)

5) sometime mistakes occur (see for example ticket 0000290), when the runway for approach is changed. I also noticed other issues, for example not enough time for decent, if the approach is shortened due to runway Change.

CONCLUSION:
As with actual flight planning tools usually the runways are already fixed during planning considering the actual winds at the time of planning, the plugin should provide the option to choose the runways manually, before they are fixed and announced by the plugin. This would have the advantages that all above mentioned items, which often break the immersion, could be simply avoided.



Copyright © 2000 - 2020 MantisBT Team
Powered by Mantis Bugtracker