Marq Aviator (gen 1) error in Fly program after update software version 27.00

Hello,

After updating the software to version  27.00 - incorrect display of the planned route.  For example, I create a new route from KJFK to KIAD (Navigation -> Flight Planning -> Saved Plans->Create New and add via Search by Ident).   The new flight plan always displays the length - 0.0 nm.  When I select Set Active and fly - the watch does not want to follow the route.  On the waypoint page, there is no point name, no DTK, no distance... Similarly, if me select Direct To and enter a point, the watch does not fly to the point.  This happened after upgrading to version 27.00.  On version 26.00, everything worked fine!  fix this error please!  I did a factory reset and a master reset - nothing changed.


I wrote twice about this to aviation support (via email), and received "Confirmation of email submission", but I never received an answer. I was buying a watch for fly work. Now it's a toy. Should I throw it away?

P.S. The GPS signal is excellent, the location on the map is indicated, ground speed is indicated correctly, heading is also indicated correctly. Altitude - also correctly

  • History ended....

    One Year on the Ground

    Why do we buy Garmin aviation devices? Of course, for flying. At least, that’s what I thought. But Garmin has a different perspective.

    So, let's talk about the Marq Aviator. A miracle has happened—after 12 months, with the release of the update version 28.02, the Marq Aviator can finally fly again. In other words, a watch that costs over $2,000 could simply stop working as an aviation device and remain useless for a year—all at Garmin’s discretion.

    A year ago, update 27.00 was released, which broke the aviation functions. The Marq Aviator essentially turned into an ordinary Fenix. Naturally, I contacted support—both general and aviation support. I wrote to them about ten times. Do you think anyone bothered to respond? No.

    I also posted on the forum. In a private conversation, I suggested to the forum administrator that they check the issue on a reference Marq Aviator unit. The response I got was:
    "I am sorry to hear that you are having trouble with the watch. I am not seeing any other reports of this issue."
    In other words, it was easier for them to dismiss it as my problem rather than actually check!

    Then, I found Garmin’s Facebook page and wrote there. To my surprise, they replied! Almost a victory! They gave me two email addresses—one in the U.S. and another in Europe, in London. I wrote to both. The U.S. email never responded. From London, I received a reply… after four months.

    They asked if my issue had been resolved. After a few emails back and forth, the London office finally decided to investigate whether update 27.00 really had a problem. And a few days later, they confirmed—they managed to reproduce the issue!

    A victory, almost a year later! They told me to wait for a new update that would fix the watch. And so, I waited. A full year.

    Finally, the update 28.02 restored the watch’s aviation functionality—turning it back into a Marq Aviator instead of just a Fenix.

    What do I have to say about Garmin support and Garmin Aviation support? Guys, not only do you do your job poorly—you don’t do it at all. You simply don’t exist. And I will think very carefully before I ever give my money to Garmin again.  

  • Have you ever called their support number? I've had plenty of really helpful conversations when I call.