MantisBT

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000291124thATC[All Projects] Planningpublic2017-07-09 23:472017-07-10 00:48
ReporterAdvMichael 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusnewResolutionopen 
Platformx64OS(All OS)OS Version(All versions)
Product Version2.0-a56 
Target VersionFixed in Version 
Summary0000291: Allow to predefine departure and landing runway
DescriptionThis 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.

Additional InformationSUGGESTION FOR IMPLEMENTATION (I could do a even more detailed specification, if you want):

a) the runways can be entered in the flight planning next to the Airports
Of course a dropdown menu with all runways after parsing the airport data would be the most convenient solution. However, for the beginning also manual entering of the runways would be alright. Just make sure to force them upper case.

b) Entering the runways for departure and arrival is fully optional. If the fields are left blank, the plugin will detect the runways as it did up to now.

c) In addition to the flight plan, it should be possible to change the preselected runways also after filing the flight plan, as wind directions may change. This should be done in the same dialog box, where you can ask for flight level changes or skip waypoints. Changing the runways should be only possible until:
- DEPARTURE: until the clearance is requested
- ARRIVAL: until ATC informs "expect XXX Approach on runway YYY". The function should not allow to change the runway when already in the Approach.

d) Handling for departure:
- when requesting the clearance, the plugin will check, if a runway was selected
- then check, if the runway is valid (available in aiport data) [please take care of upper case and leading zeros, like 8L or 08L]
- take this runway and calculate the SID
- if the entered runway is not valid or empty, use the function as it was up to now
- OPTIONAL: if the tail wind exceeds XXX knots (I could prepare a table, for simplification based on the aircraft weight), then the plugin should take the preselected runway but in opposite direction.
- basically still allow the runway change as it was up to now

e) Handling for arrival
- when approaching the Airport the plugin will check, if an airport was manually selected for landing
- then check, if the runway is valid (available in aiport data) [please take care of upper case and leading zeros, like 8L or 08L]
- take this runway and calculate the STAR
- if the entered runway is not valid or empty, use the function as it was up to now
- OPTIONAL: if the tail wind exceeds XXX knots (I could prepare a table, for simplification based on the aircraft weight), then the plugin should take the preselected runway but in opposite direction.
- basically still allow the runway change as it was up to now

f) OPTIONAL: check the LastFlightPlan.txt for RWdeparture# and RWarrival# and read the values into the flight plan window. This would allow to add the runways automatically from the EFASS NG export for even more convenience.

So basically we actually need the fields for selecting or entering the runways. Then the existing routine for choosing the runway just additionally needs to look first, if a runway was manually entered, check it against available runways and take it. If not, just use the exisiting procedure. Checking for high tails winds would be an optional Feature, but not absolutely neccessary.

This should be optional, so if no runway data is entered, everything sould work as it is now.


TagsNo tags attached.
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2017-07-09 23:47 AdvMichael New Issue
2017-07-09 23:50 AdvMichael Additional Information Updated View Revisions
2017-07-09 23:50 AdvMichael Additional Information Updated View Revisions
2017-07-09 23:52 AdvMichael Additional Information Updated View Revisions
2017-07-10 00:34 AdvMichael Description Updated View Revisions
2017-07-10 00:37 AdvMichael Additional Information Updated View Revisions
2017-07-10 00:38 AdvMichael Additional Information Updated View Revisions
2017-07-10 00:48 AdvMichael Additional Information Updated View Revisions


Copyright © 2000 - 2017 MantisBT Team
Powered by Mantis Bugtracker