![]() |
Question for those who use mission+ and flysmart
Does anyone experiencing any problem recently with mission+ and flysmart? Recently mission+ crash so frequently now. And when you open eQRH it will just go blank until you force restart it. The flysmart takeoff isn’t perfect either, sometimes my take off calculation would just reset and I have to input it all over again.
Imagine if you got smoke in a cockpit and the thing just crash when you try to open smoke in the cockpit or emergency evacuation when the cockpit is fill with smoke. is anyone experiencing the same? Does your airline has any contingency for it? |
What tablet/laptop do you use? Do you do updates yourself or somebody at the office does them for you? Usually crashing is related to updates/compatibility... I have them from time to time but nothing worth mentioning.
|
You need to make sure that the device has not updated the latest OS that may not have been fully tested.
Navblue will put out emails saying when it is safe to update to the latest OS. That can be some weeks after it's released. Also, you shouldn't upgrade the app until cleared. Again, some back end tweaks from time to time, mean that your. EFB person hasn't released the load to match the latest app update. All can be resolved with comms with your EFB team. |
Regarding the eQRH issue, we stopped experiencing that problem when we changed iPad to newer models.
|
Originally Posted by ustio
(Post 11977509)
The flysmart takeoff isn’t perfect either, sometimes my take off calculation would just reset and I have to input it all over again.
You should also ‘clear all’ before each flight. Since after a period of time, i think 24hrs, the eqrh clears everything. This is to ensure that the eqrh is reset for the next flight. If you don’t clear all, the auto reset could occur mid flight |
Originally Posted by ustio
(Post 11977509)
Does anyone experiencing any problem recently with mission+ and flysmart? Recently mission+ crash so frequently now. And when you open eQRH it will just go blank until you force restart it. The flysmart takeoff isn’t perfect either, sometimes my take off calculation would just reset and I have to input it all over again.
Imagine if you got smoke in a cockpit and the thing just crash when you try to open smoke in the cockpit or emergency evacuation when the cockpit is fill with smoke. is anyone experiencing the same? Does your airline has any contingency for it? |
Originally Posted by swish266
(Post 11988738)
What tablet/laptop do you use? Do you do updates yourself or somebody at the office does them for you? Usually crashing is related to updates/compatibility... I have them from time to time but nothing worth mentioning.
|
I presume you are reporting it - screenshots, what you were doing etc, and sending it back to your EFB team who then (should) send it back to NAVBLUE?
|
Originally Posted by compressor stall
(Post 11993616)
I presume you are reporting it - screenshots, what you were doing etc, and sending it back to your EFB team who then (should) send it back to NAVBLUE?
|
Originally Posted by cpt_rock
(Post 11989326)
I am using mission+ on Ipad air (5 i believe) with iPadOS 18 something, it started crashing all the time some time ago without having updated anything. But no idea what’s the problem.
|
Mission+ is written using the Qt framework, probably to avoid developing native code separately for Windows and iPadOS. The downside is reduced stability, limited native features, and degraded user experience overall (slow scrolling, average UX, less responsive interface).
Using a framework for an EFB was already controversial a few years ago, but now with AI integration growing fast and airlines clearly prioritizing the iPad platform, it’s becoming obvious that it was the wrong move architecturally. *Delay before clearing the inputs is configurable from 30 to 180 minutes, defaulted to 60. Ask your administrator to adjust it if needed. |
Originally Posted by maxq.
(Post 12091143)
Mission+ is written using the Qt framework, probably to avoid developing native code separately for Windows and iPadOS. The downside is reduced stability, limited native features, and degraded user experience overall (slow scrolling, average UX, less responsive interface).
Using a framework for an EFB was already controversial a few years ago, but now with AI integration growing fast and airlines clearly prioritizing the iPad platform, it’s becoming obvious that it was the wrong move architecturally. *Delay before clearing the inputs is configurable from 30 to 180 minutes, defaulted to 60. Ask your administrator to adjust it if needed. |
Apple focused on cybersecurity and sandboxing first, having everything locked down but then gradually opening enterprise capabilities step by step — probably too slowly for some companies.
But the result is there: when it comes to aviation software and EFBs, other platforms are basically out of the game, despite the constant efforts from IT trying to impose the same ecosystem they use at the office. Looking back, the industry probably spent too many years trying to preserve cross-platform and desktop-oriented approaches, while operational usage was already clearly moving toward native iPad workflows. Btw, there’s also an alternative to eQRH if I remember: sQRH. Much better than PDFs or paper as a backup. |
Originally Posted by ustio
(Post 11977509)
Does anyone experiencing any problem recently with mission+ and flysmart? Recently mission+ crash so frequently now. And when you open eQRH it will just go blank until you force restart it. The flysmart takeoff isn’t perfect either, sometimes my take off calculation would just reset and I have to input it all over again.
Imagine if you got smoke in a cockpit and the thing just crash when you try to open smoke in the cockpit or emergency evacuation when the cockpit is fill with smoke. is anyone experiencing the same? Does your airline has any contingency for it? Rgds, |
| All times are GMT. The time now is 22:18. |
Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.