My Phantom 4 Pro crash. 91% battery left, broken prop, frame, gimbal & cable. The reason for my Mavic Pro 2 purchase.
And what did you learn to keep that from happening to your M2?[/QUOTE
That is a very good question my friend and here is the answer. I have flown Litchi missions countless times with no problems what so ever, but this time after reviewing my files and mission data, the crash was caused by the pilot !! Never setup your missions up hurriedly. I had a POI hidden behind one of the other POI's that was set to 98 ft which was supposed to be at 390 ft. As a result you see the gradual decent into the trees with the drone doing exactly what it was programmed to do. No one to blame but me..... sigh.....
A miss set POI I wouldn't have thought would do that. Did you mean a WP.
I have yet to screw up with Litchi, but I had some close calls with Mission Planner on previous drones.
Have you tried Virtual Litchi Missions yet to review you flight paths? It won't really help if you setup missions in the field.
To me it looked like it stopped then flew closer to the trees and then flew backwards before descending.It does look like the sensors did stop the collision, but then, the drone went down, not up!
In theory the sensors should have stopped the Mavic 2 from crashing into the trees if they detected it.
The obstacle avoidance system still works during litchi missions from they have told me.
I had a similar experience but I had checked the box for same elevation at all waypoints BUT one waypoint did not get checked and thanks to the collision avoidance sensors, the Air 2 stopped before hitting the tree. I'll check everything more closely next time before running the mission.Been there, done that. Totally pilot error. I flew a similar Litchi mission but forgot when doing the programming just how high the hill rose up at the far end of the mission. Fortunately the bird got stuck in the top of one of those trees and after a lot of work I was able to get it down with out any damage. Litchi has a feature that allows it to take into account elevation features when flying around hills. But really, it was just stupid pilot error on my part. Hopefully a lesson learned and never to do it again!
We use essential cookies to make this site work, and optional cookies to enhance your experience.