I suppose this is technically my fault, but the situation really highlights the problems with how DJI implements GeoZones and how it affects drone behavior.
So I got a weeks-long authorization to fly in the Class C airspace in the city where my in-laws live, since we travel there often and it's a nice area to fly. This particular zone spans a river, and the zone I got cleared by the FAA included a sliver of land on the south side of the river where there's a good spot to take off and fly across the river to get the shots I wanted on the north side. I used this spot a couple of weeks ago and had no issues with unlocking the zone and flying all around the area.
Fast forward to 4th of July and I went to the same spot and, after launching and flying several minutes without any issues, got a "restricted zone, exit promptly" error or something similar to that. I've flown in controlled airspace A LOT (with authorization, obvs) and have never gotten this warning until this weekend and didn't think much of it because it went away and didn't seem to be affecting my flight at all...and I assumed it was because the area that I was launching from was right at the edge of the area where I had drawn the unlock polygon in FlySafe (but still well within the area I was authorized by the FAA to fly in). Also, I had flown from this exact spot just two weeks prior and not gotten any warnings, so I didn't really understand why there would be an issue now (other than DJI GeoZone system being hot garbage).
Anyway, the fireworks wrap up and I start flying home and the drone hits an invisible wall *over the river*. So it dawns on me that DJI considered my launch location as outside of the unlocked GeoZone and now wouldn't let me return to the Home Point that it now considered outside the unlocked zone. No matter what I did, including initiating an RTH, the drone refused to let me fly it past that invisible line. Thank the drone gods for the Mavic 3's long battery life, because it gave me enough time to not panic and try and work a solution. So what I figured out was that each time I'd signal an RTH, the drone would move like 3 feet closer before it would stop, and I basically just kept re-initiating RTHs until yard-by-yard I got it over land and was able to bring it down. But if I hadn't been able to do that, I'd have had to fly it back across the river and land it somewhere discrete where no one would see and steal it.
So if DJI won't let me RTH, why would it let me take off in the first place (the warning didn't pop up until a couple of minutes into the flight)?! And why was I able to fly from this spot with no issues two weeks ago but all-of-the-sudden I'm hitting an electronic wall? And now recounting this story, I remembered that I also got this warning the day before in a different spot. I double checked that zone and I was well within the boundaries of polygon in FlySafe, so that one wasn't operator error. I wonder if the recent firmware updates included some new FlySafe parameters that are more restrictive?
I'm just carping at this point, but the TL;DR is to be very careful with how you draw your polygons in FlySafe because it could be the difference between an uneventful flight and a disaster.
So I got a weeks-long authorization to fly in the Class C airspace in the city where my in-laws live, since we travel there often and it's a nice area to fly. This particular zone spans a river, and the zone I got cleared by the FAA included a sliver of land on the south side of the river where there's a good spot to take off and fly across the river to get the shots I wanted on the north side. I used this spot a couple of weeks ago and had no issues with unlocking the zone and flying all around the area.
Fast forward to 4th of July and I went to the same spot and, after launching and flying several minutes without any issues, got a "restricted zone, exit promptly" error or something similar to that. I've flown in controlled airspace A LOT (with authorization, obvs) and have never gotten this warning until this weekend and didn't think much of it because it went away and didn't seem to be affecting my flight at all...and I assumed it was because the area that I was launching from was right at the edge of the area where I had drawn the unlock polygon in FlySafe (but still well within the area I was authorized by the FAA to fly in). Also, I had flown from this exact spot just two weeks prior and not gotten any warnings, so I didn't really understand why there would be an issue now (other than DJI GeoZone system being hot garbage).
Anyway, the fireworks wrap up and I start flying home and the drone hits an invisible wall *over the river*. So it dawns on me that DJI considered my launch location as outside of the unlocked GeoZone and now wouldn't let me return to the Home Point that it now considered outside the unlocked zone. No matter what I did, including initiating an RTH, the drone refused to let me fly it past that invisible line. Thank the drone gods for the Mavic 3's long battery life, because it gave me enough time to not panic and try and work a solution. So what I figured out was that each time I'd signal an RTH, the drone would move like 3 feet closer before it would stop, and I basically just kept re-initiating RTHs until yard-by-yard I got it over land and was able to bring it down. But if I hadn't been able to do that, I'd have had to fly it back across the river and land it somewhere discrete where no one would see and steal it.
So if DJI won't let me RTH, why would it let me take off in the first place (the warning didn't pop up until a couple of minutes into the flight)?! And why was I able to fly from this spot with no issues two weeks ago but all-of-the-sudden I'm hitting an electronic wall? And now recounting this story, I remembered that I also got this warning the day before in a different spot. I double checked that zone and I was well within the boundaries of polygon in FlySafe, so that one wasn't operator error. I wonder if the recent firmware updates included some new FlySafe parameters that are more restrictive?
I'm just carping at this point, but the TL;DR is to be very careful with how you draw your polygons in FlySafe because it could be the difference between an uneventful flight and a disaster.