Same here. Just forced myself to use it. Griped about it for a trip or two and have now settled into a usable flow. At this point I'm an M+ user but I don't like M+. The UI is clunky and laughably bad (only comes in dark mode!? Lol), it is poorly thought out with respect to our normal work flow and the procedure to sign the release is idiotic. There is just so much room for improvement.

it's usable, but clunky. I stopped using paper flight plans as soon as we got the HTML flight plan. The HTML flight plan is far superior to the paper copy, and oak notes made mission plus easy....it put everything on one page instead of hidden amongst 30 pages like mission plus.

I don’t really mind MiserablePlus but what really drives me batsh!t is that Delta is either unwilling or unable to have fewer apps do more stuff. If we run all the apps required and recommended to get the plane off the gate and in the air I think there are about 8 or 9, and even more maddening is that they all use different communication protocols. A800, F500, cellular data, Bluetooth, American Sign Language, braille…

Why is it every time someone in a cubicle decides/realizes/proposes on a zoom meeting that something needs to be visible to the pilots they just make another app? Why can’t some of them be added to an existing app and the overall number be reduced? One app to rule them all and in the darkness bind them. Or at least not 8! Aaaargh.



I need a drink.

Hear hear! Best piece of kit I've found is the "Mission" add on. Once you download and install it, you just open Mission+ and select it from the sharing options and it automatically opens and loads FD Pro and WX Viewer for the selected flight. Saves much tap-tap-tapping.

I’ve had one or two.

That’s a lot of words to say the truth. It’s a poorly thought out POS. No need to sugar coat it.

Fundamental things like simply laying all the important stuff out on the front page. Wtf?

Day mode? What’s my planned arrival gate? Etc etc

P O S

Flush it down wherever the surface went.

Whenever I have to reference the flight log to load the FMS on the preflight…the program is a failure. I want to use it…it’s just slower than the html flight plan.

Why would you need to reference the flight log to load the FMS?

Of course these are first world problems, all our problems are first world problems and it could always be worse, welcome to the show. We're not exactly ready to get the pitchforks out here, just voicing issues. It's just a bit annoying how they are slow to fix the issues we bring up, but are quick to send and update to shut down stuff that actually is useful. They have a long history of casting aside or shutting down things that just work, nearly always falling back on the trusty "security" excuse. It would be great if they'd harness the oaknotes display that has all the pertinent data distilled into one, easy to understand, screen...rather than making us hunt and peck all over the place. Heck, I'd be a bit happier if they simply allowed the down arrow to work throughout the entire flight, rather than just the current sub-section. Also (from a WB friend), they released it without a crew rest calculator, then re-released it with a crew rest calculator that doesn't work lol.




He's probably referencing the fix list and verifying the routing on the ND. However, I believe the fix list is found on the FMS init page. Maybe looking for the reporting points?

yeah, they blocked the ability to do that....

A twofer, along with Oaknotes…long live Oaknotes!