Jump to content

Known open issues, please read!

Mathijs Kok

Recommended Posts

  • Root Admin

We are very excited to introduce you to the Open Beta version of the Connected Flight Deck feature on our A318/A319 & A320/321 products. This Open Beta is important so that we can gather necessary data with big enough user base to test the server stability as we are working towards the final release version of the Connected Flight Deck.

However, we would like to remind you that this is still highly Open Beta product and there is still some issues that you might encounter while trying the Connected Flight Deck out. We are actively working to get these issues sorted as soon as possible and will introduce all the latest updates with the normal update schedule as they are worked on. To have some idea what to expect with the Connected Flight Deck we have gathered a list of the issues that we already know and possible workarounds for them. Please read this list first before your first flight and keep it in mind before reporting any issues. Of course, if you find an issue that you know is Connected Flight Deck related and it’s not mentioned on the list yet, we would highly appreciate if you let us know about it so that we can have a proper look into it.

Please, note that while you are observing, you can still make inputs on switches, but these inputs will not be synced to the pilots operating the aircraft. We recommend you don’t touch any switches while observing to prevent any desync issues with switch positions.

  1. MCDU flickering and continuous printing when another pilot is making MCDU inputs.
  2. RIGHT MCDU not completely functional.
  3. FMGC Temporary flight plan is not showing for the pilot not making inputs. It will update once pilot making FMGC inputs inserts the temporary flight plan. This issue can be observed on DIR TO, DEPARTURE and ARRIVAL pages.
  4. MCDU “SELECT DESIRED SYSTEM” message not cleared for both pilots. The pilot not selecting the system must manually clear this message
  5. QNH setting has some anomalies. If one pilot changes the QNH value, it will not update straight away for the other pilot. As soon as the other pilot moves QNH value it will update the correct value selected in the first place. Same thing with STD setting where the STD label will show up for both pilots, but it will keep QNH value for the pilot who didn’t pull standard. So, both pilots have to pull STD even though it shows STD if one pilot pulls it.
  6. Brakes with button control have a slow release
  7. MCDU 3 doors sync not 100% reliable
  8. FMGC SEC F-PLN page not synced
  9. FMGC PROG page not synced
  10. FMGC INIT A page ALTN field not synced
  11. FMGC ALIGN IRS not synced
  12. FMGC Weather uplink not synced
  13. APU Start is not always synced. We recommend both pilots verifying that APU is running before disconnecting the External power.
  14. L & R radio power switches now synced
  15. FCU - Some presses can show different values like pressing altitude knob to managed leaves V/S for the pilot not making the input.
  16. Light test switch not synced
  17. Parking brake not always synced
  18. Navigation Display Chrono not synced
  19. ISIS Baro setting not synced
  20. Pedestal Predicted Windshear (PWS) button is not synced
  21. Pedal disconnect switch not synced
  22. Oxygen Mask panels not synced
  23. Sometimes PF/PM roles can change randomly during preflight
  24. PF cannot switch to PM
  25. Rudder trim reset not synced
  26. FMGC PERF -> APPR page 0/0 wind does not fill anything for the pilot not making inputs
Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

This topic is now closed to further replies.
  • Create New...