Nothing in these logs to indicate any issues. If possible, you will need to retrieve the .dat file from the AC to determine what occurred. These logs just suddenly end at 127ft in altitude, with no indications of any issues. This sounds like a sudden and complete power loss, aka a dislodged battery. A prop would not cause this, unless there was a simultaneous loss of downlink along with a prop failure. ( Doubtful ).
Right -- your log doesn't show a collision. It looks like the battery popped out mid-flight (maybe due to it not being inserted properly).
A sudden battery anomoly is a distinct possibility. One anomoly: There is a spring-like tension that pushes out on the battery as you seat it, that’s supposed to lock it in place. Inflight vibration can push a not-so-seated battery off it’s contact points. You’ll either get one of many warning lights and just make it back (if you’re lucky like me) or it’ll just go 100% disconnected and drop from the sky. Both end results have happened to a number of pilots. SOLUTION: Seat the battery once... push it twice.
Even if the battery doesn't fully pop out, it can slide out just far enough to disconnect the battery contacts if the battery is not fully clipped into place. Unfortunately, the P4P does not have a sensor like the P4P V2 to alert the pilot when the battery is not inserted properly. See more details here.
Thankyou for reaffirming my previous reply-observation. Your reference about the P4p V2 sensor is a good mention.
True. However, there were no obstacles near the drone at the last location in the flight log.
GPS can easily be off by any number of feet. The Phantom could have actually been on the other side of the street.
