Ex Machina
Captain
Flight distance : 1806362 ft
United States
Offline
|
BengalBoy Posted at 2017-4-26 09:04
You know, I've been flying at this area with my Phantom 2 Vision+ and Phantom 4 for years. I really learned to fly on the open ocean here. Admittedly, there was no NFZ issue with the Phantom 2. The Phantom 4 was a monster out on the ocean and I captured many sunsets flying on the very beach I lost the Mavic. So, I'm kinda at a loss as to why the NFZ is even an issue in this matter when the Mavic had been flown here that morning at altitudes above 200 feet and obviously took off and flew from the beach before the auto land. I don't think its the NFZ issue, I've flown my Phantom 4 into airspace and it immediately give you a warning that you are approaching a NFZ and will not travel any further in the direction of the NFZ. It does not auto land, its stops and tells you to turn around. I had none of those errors with the Mavic. It flew like a F18 until the DJI Go 4 app crashed and upon restart, the Mavic went into Auto Land mode. I think its a software thing,,, not an actual NFZ thing...
I've had the Mavic initiate autoland just after launching very near a NFZ, a few yards closer to the NFZ and it wouldn't take off at all. It seems to be normal behavior when the Mavic thinks it's too close to a NFZ.
Pure speculation, but it could be that after the crash and restart, before the app got it's GPS coords from the AC, the app decided it was too close to a GZ, either because with .0600 the app always thinks it's in a NFZ until it attains a lock from the AC, or it somehow got a spurious location that placed it too close to a nearby NFZ.
Lots of people are claiming spurious NFZ messages at start-up, and I think you are one of them. I can't say I've noticed this, myself, but I live inside the Washington, DC NFZ, so...
|
|