Meta 4 Thanks for the reply - I took the liberty to quote a number of your replies below to confirm the data on this drone has you both confused and guessing with regard to the drones doomed flight. For this reason, I advised you that saved data is no more accurate than the processor itself which caused the crash . . .
Thankyou Mike for trying to help.
Despite your vast experience, you seem to be far out of your depth on this one.
You haven't (maybe can't) read the flight data and your flailing attempts at trolling are only making you appear less credible.
Anyone who could read that flight should have no trouble seeing what happened in that incident.
Two data readers have independently come up with the same explanation.
My reference to a guess, was to fill in the blanks when almost all of the data was confirmed to be reliable but the altitude data was obviously not.
The motor error was most likely a result of the flight controller trying to match falling altitude (false data from a malfunctioning sensor) with other parameters that were being reported accurately.
There's no problem with the position, speed, pitch, roll and yaw data, which clearly show the drone in stable, controlled flight, even though the altitude data indicates the drone falling 1500 feet below ground level.
This data is coming from several independent sensors.
Failure of one doesn't automatically mean all data is unreliable.
And to anyone who can read the data, it's obvious that the data with the exception of the altitude data is reliable.
In conclusion, you should always respect the thoughts of other pilots, expecially when your euvaluting data which seems to have you confused and uncertain.
What you've offered has no merit, and has have been met with the respect it deserves.
I'd suggest that you should respect the evaluation from flyers that can and do read the flight data.
But you clearly aren't a guy that takes advice from anyone.
If you want to help further ... don't.
