This shows computed velocity as a function of time. The horizontal velocities are asymptoting to the wind velocity, as expected.
Help with Mavic 2 Pro Crash Location
- Thread starter NorcalExplorer
- Start date
This shows computed velocity as a function of time. The horizontal velocities are asymptoting to the wind velocity, as expected.
Forgot to add the wind values - no vertical gradient in this particular simulation:
2Mavics4AManiac
Member
I finally found it last night. Had searched 5 previous times with no luck and decided to take a break for a few weeks. Went back last night and couldn't believe it when I finally saw it.
It had become separated from the battery which was nowhere to be found in the immediate and surrounding vicinity. The drone was found at 41.5261 -122.3472. That was about 60-70 feet short of the projected landing spot, but possibly lacking the weight of the battery, I can understand why that would change.
Amazingly, the damage was not nearly what I expected for a drone falling 400ft out of the sky. It's actually completely intact and after installing a new battery it turns on and the gimbal works as normal. There is one motor that is frozen and one front landing gear is broken. I have refresh, so I'll be sending it in.
All in all a good ending with some lessons learned. Mainly, to get some sort of third party tracker. Looking for a downed drone is much more difficult than I ever imagined.
Thanks again to all who provided some insight on this situation.
Special thanks to sar104 for providing the crash estimate. That gave me the confidence to know it had to be there somewhere.
Attachments
Jeff A
Well Worn Member
So glad you solved your mystery. And yes, SAR104 is amazing.
Excellent news. And yes - that's actually 75 ft short of my estimate, which is more than I would have expected. If the battery had ejected I would actually have expected it to go further with the wind, due to the increased vertical drag, so that's a bit of a puzzle. Perseverance rewarded though. Nice work.
If the battery ejected then it's possible the M2 achieved a nose down orientation and vertical drag actually decreased causing a more downward trajectory. But, then the horizontal force would increase due to the wind. Apparently, the vertical decrease was more than the horizontal increase.
Oh no. I'm sure your math is correct. Impeccable. Flawless. Of the highest order. Heard enough?
Kidding aside there is only so much that can be done without a better model based on empirical data. Knowing the wind field at different heights would also help.
Oh no. I'm sure your math is correct. Impeccable. Flawless. Of the highest order. Heard enough?
Kidding aside there is only so much that can be done without a better model based on empirical data. Knowing the wind field at different heights would also help.
Agreed. On the data I mean. There is also the issue that the drag model I use is fitted to previous tumbling Mavic data, and could change if the attitude is not chaotic during the descent.
Similar threads
