Wrong Wind Uplink Flight Levels and their impact

[Balint]

Dear Developers,

I really hope that this post catches your attention because the current implementation of wind uplink, downloads winds that are completely irrelevant to the actual cruising altitude.

Please let me explain. I will prove you in the next few screenshots and some description to each picture and what I did.

1. This first picture shows some details of the flight just as an additional information for the rest to come.

2. This screenshot shows the weights and fuels as inserted by myself as per the flight plan (from Simbrief)

3. This screenshot shows the winds uplinked to one of the waypoints right after TOC. PLEASE NOTE: the abnormally low flight levels inserted by the WIND UPLINK. FL240 and FL300 are ABSOLUTELY irrelevant to this flight, where the initial CRZ FL is FL380.

4. In this screenshot please see the winds inserted by myself, which contains RELEVANT wind data. Like FL380 and FL400 where I am expected to fly.

5. In this screenshot please pay attention to the levels and wind speed at those levels. COMPARE this with the next screenshot.

6. COMPARE this with the screenshot above. The magnitude of difference in wind speeds is vastly different which results in 31 minutes difference in calculated arrival time in TFFR. Please note: the difference is not only at this waypoint but on all the waypoints along the flight which adds up the flight time to be 31 minutes off from reality (when relevant Flight Levels and Wind Speeds are added by the user.

7. PERF page with imported wind uplink. Expected fuel burn 47.4

VS

8. PERF page with wind uplinks modified to add flight levels relevant to actual expected flight levels and due to that vastly different wind speeds. Expected fuel burn 50.5

Conclusion:

Between image 7 (WND UPLNK from Simbrief) & image 8 (WND UPLNK with relevant FL's & wind speeds) there is fuel burn difference of 3 tons of fuel (47.4 against 50.4). The difference between automatically uplinked wind data and modified wind data by me, will mean:
- incorrect fuel burn
- incorrect EFOB at arrival airport
- incorrect EFOB at ALTN airport
- incorrect OPT FL calculation on initial CLB
- incorrect STEP CLIMB because of wind data not being available at higher ALTs than FL300. Unless inserted by the user. However this should be uplinked once STEP ALT's are inserted and wind request again. This does not occur as of version 1.0.8.

I am aware that the A350 ULR is in the works however if this is not going to be fixed the aircraft will calculate all the above information with wind data which is not relevant to the flight level that is being flown. This is however having an impact on all both the current A350-900 & -1000 anyway. If iniBuilds needs more in order to fix this I am more than happy to help or test or anything just so this issue is fixed.

[Eddie]

Hello,

Thank you for the extensive post! I've forwarded this to the team and we'll take a look 🙂