Sorry if dupe. By the way, when the P4 returns to the homepoint, I'm finding (probably due to the duel IMUs and compasses) that it's landing on the dime it took off on BUT: I was up on Mulholland Drive the other day where you can get a beautiful vista by just flying off the cliff. Immediately upon doing so, you're a thousand feet above the valley so i usually head straight down. I have been keeping in VLOS lately because I am not yet trusting the P4 enough to do otherwise (and its the law ). It was a super bright day and I wanted to see my distance, so I looked down and when I looked up, I could not see the bird. So I did a RTH. Waited a min and after not really noticing that it wasn't doing and then it wanted to land! I know the manual says it will automatically land if you are in a 20 meter radius of the homepoint (something I've never understood but I was much farther than 20 meters away and it wanted to land). I kept trying it over and over and it kept trying to land. It also says in the manual (although I didn't know it) but I tried to override that by using the throttle and it says in the manual that indeed if you do that, it will dis-engage descending and return to homepoint. My question is two fold, why in all my time flying the P3P and P3A have I never once encountered this issue abd two, WHY DOES IT EXIST? Even if I'm 65 feet away, when I say RTH, why would it land instead of RTH??? Either way, I was DEFINITELY FARTHER THAN 20 meters (65 feet) so I stopped, and for the first time in about a year, I was in a panic mode and had to work myself out of it. By the way, my method for getting out of panic mode is to just admit to myself it's gone forever and work from there. As it turns out, that was almost the case. The bird was low in the valley and I had NO IDEA where it was in relation to the visual (it was super bright and had no shade on my Mini) so I just made the map full screen (switched to Atti mode), ascended to a level that I knew was about 30 meters above my starting point and followed the map back and then descended and hoped for the best. I was down to about 5% battery at that point and was already thinking about what my next step was going to be when all of a sudden I could hear the motors. I put it in S mode for some extra speed and descended as fast as I could and thank God because when I caught it, there was 2% left. I NEVER EVER return a bird with less than 15%. This was BY FAR my closest call and if there was some pilot error, I haven't a clue where it was. I have it all recorded and will upload it to this thread later along with the flight info and I'll upload the logs, but the fact that I still own a P4 is either dumb luck combined with half decent pilot skills, or dumb luck caused by poor pilot skills. I have yet to determine which. Leaving on an Easter trip with the family so I wont have a lot of time to study the flight data this weekend but I'm bringing the P3 and another one and leaving the P4 home because I won't fly it again until I know what happens and without a satisfactory answer or the thing I did wrong, this is going back home. I already called DJI and they said I could return the care but not the two batteries I just bought so if I don't get an answer, two brand new batteries will be for sale. Not for nothing, the DJI tech I spoke with on the ride home to discuss the issue said he had heard about this issue from some of his colleagues but I was the first case to have come to him with it. (Sorry that I am not proof-reading this now and typos is my best business).