Gimpy
lvl.4
United States
Offline
|
Well, the short version of my opinion is that I think you should contact DJI about this and I believe you stand a good chance of getting a warranty replacement.
"What happened to the IMU?"
I don't know, and the TXT file won't reveal much. If you'd like to retrieve the DAT file from the tablet and upload it, I can take a look and may be able to figure something out. The instructions for retrieving it are here, and to provide a link, you'll need to upload it to something like Google Drive or TinyUpload. If you decide to go this route, the correct file should be called FLY034.DAT.
"Is any of it connected to the NFZ I was in?"
I doubt it, other than the fact that your screen was partly cluttered with the warning. You probably already know that you were in a GEO 2 "Altitude Zone" (grey area), but that doesn't account for any of the problems you encountered.
"Why didn't I get the normal consent boxes to unlock an NFZ as I normally do?"
You don't have to consent to fly in an Altitude Zone; it just notifies you and restricts you to flying below a certain height. Had you been a bit farther to the southwest (closer to Hayward), you'd have been in an Authorization Zone and would have needed to check the consent boxes.
"Is any of this Pilot Error?"
Not in my opinion. The reason it slammed into the ground was due to the fact that VPS wasn't giving a reading when you brought it down, so Landing Protection didn't activate to soften the landing as you pulled back on the throttle. Technically you probably could have landed softly, but there's no good reason VPS shouldn't have detected the surface when you brought it down in the middle of the street. VPS appeared to be working fine at the beginning of the flight, but not at the end, so the fact that it went offline is probably related to the other problems you saw, and is definitely the reason why it slammed into the ground.
Again, I suggest you open a ticket and push for a warranty replacement.
|
|