@BossBob - the app map (and the method you describe) does NOT show an NFZ. Thus, based on comments I read on the forum, I thought the NFZ notices I get are due to a different map on the drone vs. what is shown on any other map.
The area in question was an authorization zone. (yellow) Legal to fly after giving notice and checking the boxes if you get that pop up on the controller.
So, are other people getting NFZ groundings because of a bug in 550 and later, or is it because the map the drone uses is incorrect? Meaning...the drone doesn't have a bug, it's just looking at bad data.
@Robbyg - PM sent.
You ask a couple of good questions and raise several more. I honestly don't know what "map" the Mavic sees as I am sure it is a database of coordinates, probably a digital representation of the Geo maps published by DJI, although I am not sure.
The following story illustrates the complexity involved here.
I was forced to land on the beach, just a few seconds before launching out over the Gulf of Mexico. This was in a YELLOW authorization zone after I had successfully authorized, (obviously because I was hovering at the time of the forced landing).
Upon later research, I was indeed in a yellow zone according to the Geo map, but not according to Airmap, nor the published procedures for determining NFZs according to FAAs own directions, nor according to their recently published maps to determine airspace authorizations. I was not within B,C,D, or E airspace nor within 5 miles of any airport.
When I look closely at their (DJI Geo) zones, I notice a hugely more conservative interpretation of what is "legal" and what is not, and this might be a big part of the problem.
So, did the problem occur because the internal "map" was incorrect/inaccurate (which it technically is, but the Mavic probably read it correctly based on the data) and then the firmware, erred by grounding me, after a properly executed authorization? I do not know.
Then, during the same trip, in another location, the Mavic erroneously warned me (when compared to their own Geo map) that I was in a class C airspace, but let me authorize and fly without incident. Again, I was NEAR, and below the shelf of the airspace by several hundred feet. Keep in mind that their Geo map shows me completely in the clear by miles, as it should have for recreational flying.
Admittedly this is a highly complex area with a pancake of zones, many of them higher than surface, but I'm not letting them off that easy. The mere fact that they reserve the right to ground me at all, but then based on erroneous info, just rubs me the wrong way. They need to get this stuff straightened out or simply leave us alone.
Lastly, this raises concerns for me that it can eventually be used as a method to force updates, even though many have stated that, as of now, you can unlock even with old firmware. But the one way I ensure that old firmware is not recognized on my system is to not connect my device to the net. Can't hardly get away with that if you need to connect to unlock and get off the ground.
