Mission Failed Due to Anomalies During Cruising

I was flying the Airbus A330-900 - Tollis from Sapporo to Seattle. 3 hours after takeoff, I was notified that my mission had failed due to detected anomalies. The problem is that I was cruising at +30,000ft and didn’t go to the menu. So I assume it’s a rare glitch and it happened to me. Here’s a screenshot for proof.

Unfortunately, I’m unable to attach log here. So I had to upload it to google drive and leave a link to the log.

link: https://drive.google.com/file/d/15S9bNeJGzcTxQhRxpER1AUUVrQ1CM1fQ/view?usp=sharing

1 Like

today again back this mission failed
Sbpa to SAAR

Thank you for the reports.

Whenever possible, please also open a support ticket for these cases so I can easily retrieve them and keep everything properly tracked.

As I mentioned before, I’m currently finishing the new work area that will allow us to analyze and manage these kinds of issues more effectively. As soon as it is completed, I will prioritize reviewing these cases and fixing the bugs that are causing these unexpected Mission Failed results.

Thank you again for your patience and for continuing to report these issues.

1 Like

Just encounter another anomalies during cruising but on FlightFactor 777-200ER. I assume this issue is inevitable and only occurs a 30% chance or less. I’ve left a screenshot and a link to see the log. Let me know if you have any questions or ideas.

Link to log files: https://drive.google.com/file/d/10kbtFQd_WuB0xgjxtUi27Yb7MDGsC4Ng/view?usp=drive_link

(Sorry for reupload… I uploaded the same screen shot as the first post on accident)

1 Like