So, while you were actively flying did you see these references, not in retrospect and re-thinking, but while you were flying and making movement decisions?The same places they always are.
Yes. When I saw it going down I definitely gave it left stick up.I did not say that the hovering drone doesn't maintain altitude.
Here's what I said ......
But the ocean is not dead flat and a hovering drone doesn't stay a fixed distance above the water.
Ocean swells rise and fall, coming closer and falling away from the hovering drone and always changing.
Waves have no effect on air pressure that you'd notice.
It wasn't strange at all.
Your drone maintained height except when you gave it some left stick to climb or descend.
Yes. I was watching them very closely.So, while you were actively flying did you see these references, not in retrospect and re-thinking, but while you were flying and making movement decisions?
I never disputed it got down to two feet over the water. That's crystal clear. The question is why?The discussion has become comic, as @jwilson dodges and weaves avoiding addressing the most pertinent fact, the final VPS altitude data from his log.
Until he addresses the fact the drone was 2ft over the water and getting rapidly closer before he lost contact, all else is just cruel playing with the mouse before the kill![]()
It was 10 feet over the ocean until it inexplicable crashed into the ocean.Because the screen capture shows thus. 10 feet in orange.
I wasn't looking at the drone at all. It was too far away to be seen anyway.Just to be clear, your information is about what you saw on the controller screen and your interpretation of that and not about what you actually saw by visual line of sight to the drone. What did you see as to the drone without looking at the controller screen and without reviewing and screen capture videos?
There's what you think you saw and what the data shows to have actually happened.Yes. When I saw it going down I definitely gave it left stick up.
You seem to have a big problem understanding how ocean waves work.I never disputed it got down to two feet over the water. That's crystal clear. The question is why?
It was more than 10 feet over the ocean and it was less than 10 ft over the ocean as the wave levels rose and fell while you flew out into the wavebreak zone, blissfully unaware of the most basic details of how waves work. and what distance your drone really was above wave levels.It was 10 feet over the ocean until it inexplicable crashed into the ocean.
If you bothered to watch the video, maybe you couldn't understand it, you can see i was always 9 or 10 feet over the highest point of the waves. Not 9 or 10 feet over the ocean.There's what you think you saw and what the data shows to have actually happened.
Your drone was not going down, the water under it was rising.
You seem to have a big problem understanding how ocean waves work.
It's no mystery to most people.
![]()
It was more than 10 feet over the ocean and it was less than 10 ft over the ocean as the wave levels rose and fell while you flew out into the wavebreak zone, blissfully unaware of the most basic details of how waves work. and what distance your drone really was above wave levels.
Until the ocean came up, took your drone and left you puzzled about why your drone "inexplicably crashed into the ocean".
You aren't making any sense, and it's clear that you haven't understood anything I've written again and again, explaining the data to you.If you bothered to watch the video, maybe you couldn't understand it, you can see i was always 9 or 10 feet over the highest point of the waves. Not 9 or 10 feet over the ocean.
DJI's just being polite to you and avoiding saying that you are their least competent customer.Ha ha! As usual, jwilson was right again! Here's the full text of the email i got from DJI today.
"
Dear Customer,
Thanks for your patience.
This is a follow-up on your case CAS-29926644-C5B2T6.
For your experience, we have applied data analysis for you, however, we are unable to count this case as a warranty case based on DJI policy, we are sorry for this.
According to the analysis, the incident was not caused by the pilot's error. Since the product is not within the warranty period, we are sorry to inform you we are unable to provide you with a free replacement service.
One does .. but he doesn't recognise it.The key line is, "According to the analysis, the incident was not caused by the pilot's error."
I guess some members have some egg on their face now.
You've been given detailed explanations again and again, but don't want to acknowledge that you are a wreckless flyer with no idea how to keep your drones flying safely.It would of been nice if they had said what did cause the crash. But I guess you can't have everything.
I guess DJI disagrees with you because they say there was no pilot error.You aren't making any sense, and it's clear that you haven't understood anything I've written again and again, explaining the data to you.
You got a statement from DJI that you're just not happy with because it shows you're wrong. It's that simple. I have not been given and true detailed explanations of anything I've done wrong. Only erroneous ones. They don't have to be polite, because the video and data show there was no pilot error.DJI's just being polite to you and avoiding saying that you are their least competent customer.
One does .. but he doesn't recognise it.
<<hint>> he's lost more drones than any other member and learned nothing from the experience
You've been given detailed explanations again and again, but don't want to acknowledge that you are a wreckless flyer with no idea how to keep your drones flying safely.
We use essential cookies to make this site work, and optional cookies to enhance your experience.