endotherm
Second Officer
Flight distance : 503241 ft
Australia
Offline
|
The data recorded in the app on your device abruptly stops in your case. Maybe your device is to blame, maybe it isn't a supported type, maybe it crashed, maybe it went to sleep, maybe you have a faulty USB port or the cable came out, or the radio transmitter failed or the coaxial cable fell off the board etc. Any of these things might explain why your data on the app stopped. If that was the case your aircraft would still be flying and recording data, indicating there is no fault in the aircraft. That is why you need to examine the aircraft data to make a determination, and the data on the device is not definitive. If you have a loss of telemetry, like you did at 4:18 for 7.2 seconds, the aircraft's condition is not recorded on your app, but it is recorded in the aircraft. If the data in your app happens to show it spiraling into the ocean and reaching 0ft, you could probably use that to make a case for a failure. I'm not sure if the data recorded on the app is minute in detail, whether it shows the rotation speed of the motors and the load on them for example, but that data IS available in the aircraft, and on analysis it can show DJI if the prop broke or flew off or if the whole aircraft hit a fixed object or birdstrike etc. The best you can do is prove you flew it to Point "X". Your logs will confirm that everything was working perfectly. Now, you need to come up with some proof of something "happening". A blank record proves nothing.
We know what happened up to the point the data stopped recording. There is no way to prove what happened after that without further data. You can't make assumptions that it was a failure or fault on your part or DJI's part. The best they will do and that you can hope for is a discount, which is probably what they offered you. You won't share what DJI told you about their analysis which has you so upset, but you keep referring to it. |
|