Maybe. I would expect at least a 50/50 split.What might be the situation where a warning light illuminated on the instrument cluster in a vehicle and the engine cut out and then after coasting to the side of the road, and checking the owners manual that said it wasn't safe to proceed, you persisted trying and managed to get it started and after a short time the engine failed requiring major repairs. Would you expect the dealership might, after pulling fault codes and history from the engine management computer, argue that you contributed to the loss by ignoring the warning?
I don't know the answer. I do see a similarity in this case though. No fly zone or not GO app reported a NFZ at first attempt to fly. Seemingly your determination with a power cycle and a little fiddling managed to get you flying. You then allowed the AC to proceed with a RTH which it is now very clear put the AC in what was reported (rightly or wrongly) as a NFZ causing an autoland.
DJI probably won't come too far in your direction without a lot of pressure. Your best hope is to google for similar user experiences and outcomes as a starting point.
Phantom 4 CRASH PLEASE HELP!!!
- Thread starter pete923
- Start date
From that position your prospects are probably reasonable. I can see DJI saying it was negligent to continue your efforts to launch in an are where the NFZ was reported (even if it was an error) as you had an opportunity avoid the outcome in persisting to fly. They may buckle though in good faith as, from what is known, the NFZ behaviour wasn't as advertised or expected in the circumstances.
Not yet..... it will almost certainly be available to them though (previous flight)....
I know. Just saying they didn't give that as a reason.
I'm not missing something here right? There wasn't a NFZ! And even if there was it shouldn't have let me into it, not initiated autoland!
It likley initiated autoland while you were letting it RTH to avoid entering the (what it thought was) NFZ, particularity given the altitude the AC was at.
DJI specifically mentions an "airport limit" and time entered (also saying your AC was at 380+ feet).
Have a look at your log (replay in DJI GO might be easiest for you) at the time specified and note the location. While the AC was, as explained by you, performing a RTH you said you chose to allow the AC to continue the RTH after connection was regained so you should have the information be in the GO app.
At leasf then you are in a good position to progress any further discussion you might want to have with DJI.
I've looked at the logs. The RTH was proceeding as normal when it started to descend. I had just traveled that path. There isn't a NFZ there!
Even if there was a NFZ, it shouldn't have auto landed! That's not how it is supposed to work. Can't believe this. Thanks for help
If the AC is performing a RTH and hits what the software reports as an NFZ autoland is the only option. It isn't programmed to fly around or backtrack.
So if your certain it's not a NFZ you should ask DJI to consider whether a bug in their software contributed to your loss and ask them to help. They have stated their position, it was a NFZ associated with an airport.
This is the location DJI are saying he entered the NFZ 41.7916906 -88.0248892. I can't find anything anywhere near there other than a hospital helipad about a mile north. One would think they should be able to tell him exactly what NFZ he was in even it was a TFR.
Wow I didn't know that. I thought it was just supposed to stop. Where is the info on that as I want to read it
That's all I'm asking for. They mention a helipad, but I don't think there are any NFZs associated with heliports?
There can be, but that one isn't according to DJI GEO. I'd show them the coordinates on the DJI geo map and show them there are no restricted zones where you were.
Similar threads
