Mrimstad. So true. I totally agree

DJI Mindy Posted at 2017-2-3 23:28
Sorry for your crash.
I have reviewed your case.
The aircraft was working in beginner mode and responded to the RC command actively.

I think Dronoob, has made a good point, pitch forward at 1.5 m/s rudder left 1.1 m/s . He would have to hit something in the air , did you have a look to see if there was anything like a tree standing at 8 meters high, it would be difficult for whom ever checked these logs to miss such an obstacle.

I think your engineer should take another look,

There is a way of being wrong which is also sometimes necessarily right.”

fansc2962bbc Posted at 2017-2-3 07:16
Harbourside. It did not hit anything. It was 8m (26ft) up in the air in an open field. The gimbal pitch indikator show movement of the cameragimbal when the drone hit the ground. See altitude figures. After the crash the altitud shows false readig. -143 meter I think.

Hi.

It seems your Mavic suddenly falls out of the sky outside and not hit anything at position 59.529213, 12.002724 both stick in neutral !!! It is about 10 meters NNW of the big tree. Seen through my eyes caused your crash Most likely, your Mavic lose power on the left front engine and thus spinning. You would think DJI in Holland should be able to see it out of the machine data.

If in doubt, try yourself and key position in Google Maps.

Good luck, Leif.

DJI Mindy Posted at 2017-2-3 23:28
Sorry for your crash.
I have reviewed your case.
The aircraft was working in beginner mode and responded to the RC command actively.

Hey Mindy,
I am not in an offensive mode please mind. Though your conclusion sounds a lot like:
Your B737 reacted fine to all controls but the fact that suddenly engine no1 exploded and the debry smashed into the tail section snapping off half of the control surfaces which caused the aircraft to end up in an uncontrollable spin causing it to crash into a mountain. Yep. Pilot error.
I don't get it.
Edit: looking into the video and the healthydrone file it is not a complex case as many others. In this case it is fairly easy to rule out pilot error. In fact it's harder to prove it is.

MacIak Posted at 2017-2-4 04:31
Hey Mindy,
I am not in an offensive mode please mind. Though your conclusion sounds a lot like:
Your B737 reacted fine to all controls but the fact that suddenly engine no1 exploded and the debry smashed into the tail section snapping off half of the control surfaces which caused the aircraft to end up in an uncontrollable spin causing it to crash into a mountain. Yep. Pilot error.

Couldnt have put it any better.

Landbo and hallmark007  I am actually at my country house where the fight took place. So I went out with a tape measure and the distance to the nearest tree is 15 meters minus branches 4 meters. So the Mavic was in the air approximately 10 meters away. Good guess Landbo. I can assure you there was no obstacle what so ever hitting the aircraft. I was standing close bye (9-10 meters) and had a visual all the time. As you can see in the flight recordings on Youtube (witch is very accurate I think ) you can see the nearest tree and the shadows on the ground. Even if the google map image was captured years ago it`s exactly the way it looks to day. The remark on maybe the left motor was failing and therefore explaining the crazy behavior is really very interesting.  I have downloaded the DAT-files to my computer but I cant find a way to convert them. I am sure there is some interesting information in those files. Its a shame DJI wont share this information .   Thank you so much for all good inputs and suggestions

fansc2962bbc Posted at 2017-2-4 04:47
Landbo and hallmark007  I am actually at my country house where the fight took place. So I went out with a tape measure and the distance to the nearest tree is 15 meters minus branches 4 meters. So the Mavic was in the air approximately 10 meters away. Good guess Landbo. I can assure you there was no obstacle what so ever hitting the aircraft. I was standing close bye (9-10 meters) and had a visual all the time. As you can see in the flight recordings on Youtube (witch is very accurate I think ) you can see the nearest tree and the shadows on the ground. Even if the google map image was captured years ago it`s exactly the way it looks to day. The remark on maybe the left motor was failing and therefore explaining the crazy behavior is really very interesting.  I have downloaded the DAT-files to my computer but I cant find a way to convert them. I am sure there is some interesting information in those files. Its a shame DJI wont share this information .   Thank you so much for all good inputs and suggestions

I don't know how to convert dat files,
But you could upload your logs to phantom help and download here, or just check them out yourself.

http://www.phantomhelp.com/LogViewer/Upload/ just follow instructions.

fansc2962bbc Posted at 2017-2-4 04:47
Landbo and hallmark007  I am actually at my country house where the fight took place. So I went out with a tape measure and the distance to the nearest tree is 15 meters minus branches 4 meters. So the Mavic was in the air approximately 10 meters away. Good guess Landbo. I can assure you there was no obstacle what so ever hitting the aircraft. I was standing close bye (9-10 meters) and had a visual all the time. As you can see in the flight recordings on Youtube (witch is very accurate I think ) you can see the nearest tree and the shadows on the ground. Even if the google map image was captured years ago it`s exactly the way it looks to day. The remark on maybe the left motor was failing and therefore explaining the crazy behavior is really very interesting.  I have downloaded the DAT-files to my computer but I cant find a way to convert them. I am sure there is some interesting information in those files. Its a shame DJI wont share this information .   Thank you so much for all good inputs and suggestions

Just a heads up, when replying to someone it's much easier for them if you just click on REPLY button at the bottom or there comment, they will then get a message to say you have answered there comment.

Tanks for the information hallmark007 Im on iPhone. Cant find any reply button below the comments. Just a window  for new comments.

Here is the DAT-file.
{root}INFO:lib_route_init ok
56c<raw-root>link_init <0> link_pc, ret(0x0)
56c<raw-root>link_init <1> link_vo, ret(0x0)
56c<raw-root>link_init <2> link_sdk, ret(0x0)
56c<raw-root>link_init <3> link_ofdm, ret(0x0)
56c<raw-root>link_init <4> link_bat, ret(0x0)
56c<raw-root>link_init <5> link_auto_cali, ret(0x0)
56c<raw-root>link_init <6> link_cali_led, ret(0x0)
56c<raw-root>link_init <7> link_manual_cali, ret(0x0)
{root}INFO:link_host_init ok.

      0 [L-SENSOR][ASR]sync host lead offset 0x11a

      0 [L-SENSOR][ASR]asr host sync start
{root}INFO:[panic]:******************check fault info and trace(0) ************

{root}INFO:[panic]:-----fault info is null: addr(0x2045e800),flag(0x3ccef5f4)-----

{root}INFO:[panic]:-----fault info is null: addr(0x2045e938),flag(0x36d664d7)-----

{root}INFO:[panic]:-----all task info  is null: addr(0x2045ea70),flag(0x7c12846d)-----

{root}INFO:[panic]:-----trace info  is null: addr(0x2045f260),flag(0x3acd9e77)-----

{root}INFO:[panic]:******************check last trace ******************

{root}INFO:[panic]:-----trace info  is null: addr(0x2045eca0),flag(0xa0ec7fff)-----

{root}INFO:[panic]:-----wdg_time_info is null: addr(0x2045f820),flag(0x7acdf979)-----

56d<raw-root>__comm_cfg_init(link_pc) ok.
56d<raw-root>__comm_cfg_init(link_ofdm) ok.
{root}INFO:[link_ofdm] setup entry failed


      0 [L-EMBEDDED]load  0    0  140  144 g_config.rc_cfg
      0 [L-EMBEDDED]load  1  144   76   80 g_config.mr_craft
      0 [L-EMBEDDED]load  2  224  232  240 g_config.mr_ctrl
      0 [L-EMBEDDED]load  3  464   96  104 g_config.imu_gps
      0 [L-EMBEDDED]load  4  568   88   96 g_config.control
      0 [L-EMBEDDED]load  5  664   20   24 g_config.sweep_test
      0 [L-EMBEDDED]load  6  688    8   16 g_config.engine
      0 [L-EMBEDDED]load  7  704    1    8 g_config.advanced_function
      0 [L-EMBEDDED]load  8  712    2    8 g_config.fail_safe
      0 [L-EMBEDDED]load  9  720   20   24 g_config.go_home
      0 [L-EMBEDDED]load 10  744    8   16 g_config.intelligence_orientation
      0 [L-EMBEDDED]load 11  760   32   40 g_config.flying_limit
      0 [L-EMBEDDED]load 12  800   12   16 g_config.voltage
      0 [L-EMBEDDED]load 13  816   16   24 g_config.voltage2
      0 [L-EMBEDDED]load 14  840   96  104 g_config.imu_para_cfg
      0 [L-EMBEDDED]load 15  944   20   24 g_config.mag_cfg
      0 [L-EMBEDDED]load 16  968    2    8 g_config.gyr_acc_cfg
      0 [L-EMBEDDED]load 17  976    1    8 g_config.baro_cfg
      0 [L-EMBEDDED]load 18  984    1    8 g_config.zenmuse_cfg
      0 [L-EMBEDDED]load 19  992    1    8 g_config.gps_cfg
      0 [L-EMBEDDED]load 20 1000   12   16 g_config.mode_novice_cfg
      0 [L-EMBEDDED]load 21 1016    8   16 g_config.mode_tripod_en_cfg
      0 [L-EMBEDDED]load 22 1032    2    8 g_config.mode_cinematic_en_cfg
      0 [L-EMBEDDED]load 23 1040   20   24 g_config.mode_wifi_rc_cfg
      0 [L-EMBEDDED]load 24 1064   44   48 g_config.mode_gentle_cfg
      0 [L-EMBEDDED]load 25 1112   44   48 g_config.mode_sport_cfg
      0 [L-EMBEDDED]load 26 1160   44   48 g_config.mode_normal_cfg
[          140] => g_config.mr_ctrl.atti_tilt_gain_adj
[     8.000000] => g_config.mr_ctrl.atti_tilt_k
[     4.000000] => g_config.mr_ctrl.atti_tilt_lead_fc
[     2.000000] => g_config.mr_ctrl.atti_tilt_lead_gain
[          100] => g_config.mr_ctrl.atti_tors_gain_adj
[     7.000000] => g_config.mr_ctrl.atti_tors_k
[     6.000000] => g_config.mr_ctrl.atti_tors_lead_fc
[     2.000000] => g_config.mr_ctrl.atti_tors_lead_gain
[          100] => g_config.mr_ctrl.ang_vel_tilt_gain_adj
[    19.000000] => g_config.mr_ctrl.ang_vel_tilt_k
[     0.600000] => g_config.mr_ctrl.ang_vel_tilt_pi_freq
[     2.500000] => g_config.mr_ctrl.ang_vel_tilt_lead_fc
[          100] => g_config.mr_ctrl.ang_vel_tilt_lead_fc_adj
[    10.000000] => g_config.mr_ctrl.ang_vel_tilt_lead_gain
[          100] => g_config.mr_ctrl.ang_vel_tors_gain_adj
[    19.000000] => g_config.mr_ctrl.ang_vel_tors_k
[     0.060000] => g_config.mr_ctrl.ang_vel_tors_pi_freq
[     1.300000] => g_config.mr_ctrl.ang_vel_tors_lag_fc
[     1.600000] => g_config.mr_ctrl.ang_vel_tors_lag_gain
[    35.000000] => g_config.mr_ctrl.ctrl_lowpass_fp
[    85.000000] => g_config.mr_ctrl.ctrl_lowpass_fz
[          100] => g_config.mr_ctrl.horiz_pos_gain_adj
[     0.200000] => g_config.mr_ctrl.horiz_pos_boost_fc
[     2.000000] => g_config.mr_ctrl.horiz_pos_boost_gain
[     9.000000] => g_config.mr_ctrl.horiz_pos_lead_fc
[     1.200000] => g_config.mr_ctrl.horiz_pos_lead_gain
[     0.630000] => g_config.mr_ctrl.horiz_pos_k
[          110] => horiz_vel_gain
[     2.700000] => g_config.mr_ctrl.horiz_vel_k
[     0.025000] => g_config.mr_ctrl.horiz_vel_pi_freq
[     1.500000] => g_config.mr_ctrl.horiz_vel_lead_fc
[     1.500000] => g_config.mr_ctrl.horiz_vel_lead_gain
[          120] => g_config.mr_ctrl.vert_pos_gain_adj
[     0.300000] => g_config.mr_ctrl.vert_pos_k
[          120] => vert_vel_gain
[     5.000000] => g_config.mr_ctrl.vert_vel_k
[     1.500000] => g_config.mr_ctrl.vert_vel_lead_fc
[    10.000000] => g_config.mr_ctrl.vert_vel_lead_gain
[     3.000000] => g_config.mr_ctrl.vert_acc_k
[     1.500000] => g_config.mr_ctrl.vert_acc_pi_freq
[     4.000000] => g_config.mr_ctrl.vert_acc_lag_fc
[     3.000000] => g_config.mr_ctrl.vert_acc_lag_gain
[           80] => g_config.mr_ctrl.vert_acc_i_upper_limit
[            0] => g_config.mr_ctrl.vert_acc_i_lower_limit
[           25] => g_config.mr_ctrl.horiz_vel_i_limit
[         5000] => g_config.mr_ctrl.ang_vel_tilt_i_limit
[         1500] => g_config.mr_ctrl.ang_vel_tors_i_limit
[            3] => g_config.mr_ctrl.horiz_pos_output_limit
[           30] => g_config.mr_ctrl.horiz_vel_output_limit
[          300] => g_config.mr_ctrl.horiz_atti_tilt_output_limit
  31735 [L-FLYMODE]GPS2ATTI!Init atti dynscale scale 0.300000
  31735 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI ctrl_atti
  31736 [L-FMU/LED]type:0, normal flash action:
  31736 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:4,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
  31748 [L-FDI][CTRL]: fault on , tilt_ctrl_fail
  31815 [L-RC]craft ctrl failed!!!
  31916 [L-RC]craft ctrl failed!!!
  32017 [L-RC]craft ctrl failed!!!
  32118 [L-RC]craft ctrl failed!!!
  32209 [L-FMU/MOTOR] Stop. reason:roll over or atti fail
  32209 [L-FMU/MOTOR]Total start times: 2, time: 548.26
  32209 [L-PWM]set actuator mode:IDLE
  32209 [L-FLYMODE]CTRL reset all by motor stopped
  32209 [L-FDI][CTRL]: fault off, height_ctrl_fail
  32209 [L-FDI][CTRL]: fault off, tilt_ctrl_fail
  32209 [L-FMU/FSM]state changed. cur: motor off
  32210 [L-FMU/MOTOR]fault off, esc(2) is stall
  32210 [L-FMU/MOTOR]fault off, esc(3) is stall
  32210 [L-IMU]set imu switch level = 1
  32210 [L-FDI]ns req:fdi,0to0,reason:fusion.disagree_with_mini_filter,result:fail for same in
  32211 [L-FMU/MOTOR]fault off, esc(1) is stall
  32211 [L-FMU/MOTOR]fault off, esc(4) is stall
  32219 [L-RC]craft ctrl failed!!!
  32254 [L-FDI]NS(0) COMPASS(0): fault off, noise
  32273 [L-FDI]NS(0) FUSION(0): fault on , tilt_error_in_static
  32288 [L-FDI]NS(0) FUSION(0): fault on , ag_err_large_in_static
  32320 [L-RC]craft ctrl failed!!!
  32349 [L-TAKEOFF]alti: -147.460388
  32421 [L-RC]craft ctrl failed!!!
  32513 [L-FDI]NS(0) FUSION(0): fault on , alti_walking_in_static
  32522 [L-RC]craft ctrl failed!!!
  32551 [L-FDI]NS(0) FUSION(0): fault off, tilt_error_in_static
  32623 [L-RC]craft ctrl failed!!!
  32675 [L-FDI]NS(0) FUSION(0): fault off, disagree_with_mini_filter
  32676 [L-FDI]NS(0),switch to normal filter
  32676 [L-FDI]ns req:fdi,0to0,reason:fusion.ag_err_large_in_static,result:fail for same index
  32680 [L-FLYMODE][Ctrl<1>] REQ_RC_NORMAL ATTI_HOLD ctrl_gps_atti
  32726 [L-FMU/LED]type:0, normal flash action:
  32726 [L-FMU/LED]c0:0,15;c1:0,3;c2:0,13;c3:2,3;c4:0,10;c5:0,3;c6:0,10;c7:0,3
  32792 [L-FDI]NS(0) FUSION(0): fault off, ag_err_large_in_static
  32793 [L-FDI]ns req:fdi,0to0,reason:fusion.alti_walking_in_static,result:fail for same index
  32997 [L-GPS]<GPS INFO>[monitor][0][0]:lce:0,sfe:0,dit:80,fe:1,dynseed 132 cnt 13200
  33278 [L-RC]rc_connect:1=>0
  33278 [L-SEND DATA]app connect changed:last(1) != current(0)
  33373 [L-NS][AHRS] gyro mag inconsist off
  33446 [L-FMU/LED]action changed. rc completely lost0)
  33577 [L-FMU/FSM]near ground
  33741 [L-FMU/FSM]not near ground
  33749 [L-NS][AHRS] connect us          :0
  33775 [L-NS][AHRS] connect vo          :0

If anyone is skilled to interpret the DAT-file from the Mavic crash I  would really appreciate it. Thanks.

I have mine crashed right after compass error. I have no controls on my remote.
I send to DJI support but no reply.

MikeSG. Sorry to hear. I would recomend that you download the flight record and let the forum have a look. Great people with a lot of knowlege

MikeSG Posted at 2017-2-5 01:02
I have mine crashed right after compass error. I have no controls on my remote. https://www.youtube.com/watch?v=_jZ39MFKC7U
I send to DJI support but no reply.

Seriously bad location for flying your Mavic, not nice to see it go down, did you have much damage..

MikeSG Posted at 2017-2-5 01:02
I have mine crashed right after compass error. I have no controls on my remote. https://www.youtube.com/watch?v=_jZ39MFKC7U
I send to DJI support but no reply.

You have just hijacked another thread, in which we are trying to clarify why another drone has crashed. As a result of that the original discussion is disctracted. And your issue will only get attention by people who are interested in the original topic.

Would you be so kind and post your issue as a new thread so that it gets the attention it deserves?

fansc2962bbc Posted at 2017-2-4 07:56
Here is the DAT-file.
{root}INFO:lib_route_init ok
56clink_init  link_pc, ret(0x0)

The DAT file looks like a very basic log of the RC. It loads a lot of config files at the beginning and gives some status updates afterwards. This log file cannot be used to analyse all flight situations but it might show an issue with the controller during flight (restart of controller for example).

My opinion still is: Let someone from DJI engineering have a deeper look. Would someone at DJI be so kind and take care of this?

This is IMHO the only way to clarify if there was a technical issue during flight or the aircraft crashed into something. Right now we have two stories which leave a bad taste to this issue.

One the one hand, there seems to be nothing around the aircraft could have crashed into. This seems to support the idea of a technical defect. On the other hand, a bird could have attacked the aircraft or the aircraft could have flown into a branch or something. This soundsmore like a pilot error and it should be visible in the log files as the acceleration sensors would have recorded that kind of impact before any counter-measures become active.
The current analysis by DJI Mindy says "pilot error". We can see the crash in the log file. But we cannot see if that crash was caused by a physical impact or a technical defect. This is something that probably only the engineers can see with a very detailed analysis.

DJI Mindy, DJI-Thor, DJI-Ken? Could you please help to get this sorted out and get the flight analyzed by your engineers? If so, please keep in mind that the map does not show anything the aircraft could have crashed into.

fansc2962bbc Posted at 2017-2-5 02:51
MikeSG. Sorry to hear. I would recomend that you download the flight record and let the forum have a look. Great people with a lot of knowlege

I would recommend you try to download to HD or PH you should get logs that are a lot easier to give you a better perspective on what might have occurred..

Dronoob Posted at 2017-2-5 04:02
The DAT file looks like a very basic log of the RC. It loads a lot of config files at the beginning and gives some status updates afterwards. This log file cannot be used to analyse all flight situations but it might show an issue with the controller during flight (restart of controller for example).

My opinion still is: Let someone from DJI engineering have a deeper look. Would someone at DJI be so kind and take care of this?

Dronoob. I agree. This tread has become very long and we probably cant get an answer unless DJI steps forward and share their  conclusion with us. Thanks.

hallmark007 Posted at 2017-2-5 04:23
I would recommend you try to download to HD or PH you should get logs that are a lot easier to give you a better perspective on what might have occurred..

hallmark007.  Didn`t  know HD was capable to convert DAT-files. What site is  PH.

fansc2962bbc Posted at 2017-2-5 05:03
hallmark007.  Didn`t  know HD was capable to convert DAT-files. What site is  PH.

http://www.phantomhelp.com/LogViewer/Upload/

hallmark007 Posted at 2017-2-5 05:05
http://www.phantomhelp.com/LogViewer/Upload/

hallmark007 Thanks.

Dronoob Posted at 2017-2-5 03:23
You have just hijacked another thread, in which we are trying to clarify why another drone has crashed. As a result of that the original discussion is disctracted. And your issue will only get attention by people who are interested in the original topic.

Would you be so kind and post your issue as a new thread so that it gets the attention it deserves?

Yes sure. Thank you. Sorry for the intruding.

hallmark007 Posted at 2017-2-5 02:59
Seriously bad location for flying your Mavic, not nice to see it go down, did you have much damage..

Yes. 2 of the arms were damaged and the entire gimbal with the camera was broken. I have flown in these environment many times with Phantom 3 and Inspire 1 but never have lost of communication on the RC with the drone.

@fansc2962bbc, some moderators have been active lately but it seems they do not want to contribute to this discussion. I think you have to get in touch with them directly or open a support case and ask for a detailed flighzt analysis that explains what your pilot error was, that the Mavic fell down like a brick from 8m height in an open space.

MacIak Posted at 2017-2-3 06:07
I really hope to see a DJI rep in this thread!!
Just some things just need to be clarified.

    Dji has obviously determined ...the compass was working correctly.... Thats why their not paying.. Dji cant be held responsible for external interference.
  I just cant understand how people think this should be warrenty.

The op should not have continued flying after the interference warning...

z4k4tt4ck Posted at 2017-2-5 11:51
Dji has obviously determined ...the compass was working correctly.... Thats why their not paying.. Dji cant be held responsible for external interference.
  I just cant understand how people think this should be warrenty.

z4k4tt4ck.  Yes there was a brief warning message for a few second. No accoustic warning. I simply missed that. Probably because i was keeping my eyes on the Mavic. But the warning says fly with caution.
I did fly with caution. I have heard several other having this brief warning during take off. Dont know why but has not been anny problem regarding flight stabillity.  Really dont tink this would cause at total loss of control, but maybe some drifting. But then again Im not an expert.

Dronoob Posted at 2017-2-5 10:32
@fansc2962bbc, some moderators have been active lately but it seems they do not want to contribute to this discussion. I think you have to get in touch with them directly or open a support case and ask for a detailed flighzt analysis that explains what your pilot error was, that the Mavic fell down like a brick from 8m height in an open space.

Dronoob. Have sent a mail to support@dji.com and asked for their oppinion regarding the analyses of filght record and  DAT-files.  I really hope the wil shed a little light on this .It is the only way to maybe find the cause of the crash.

z4k4tt4ck Posted at 2017-2-5 11:51
Dji has obviously determined ...the compass was working correctly.... Thats why their not paying.. Dji cant be held responsible for external interference.
  I just cant understand how people think this should be warrenty.

@z4k4tt4ck: There is one thing here that does not make sense. DJI says "pilot error" which translates to "you crashed the aircraft" because otherwise it is impossible to get the aircraft down to the ground at that speed in beginner mode. But if you look a Here maps or Google maps, there is nothing around and the aircraft was 8m high.

What does a pilot error look like when a DJI aircraft falls from the sky in a wide open area? This is the question that I would like to get an answer for.
PS: The first DJI answer was "compass error", then it was "pilot error". What comes next?

z4k4tt4ck Posted at 2017-2-5 11:51
Dji has obviously determined ...the compass was working correctly.... Thats why their not paying.. Dji cant be held responsible for external interference.
  I just cant understand how people think this should be warrenty.

"Obviously"  you have not read the OP' s first message. Statement from dji: "compass error, no warranty". It would confuse me, i ll tell you that.  On top of that look at the files, they speak for themselves.
I have gone through numerous threads with mavics falling out of the sky. But this is a no- nonsense warranty issue. The OP is very kind and sportive about the situation. Yet if you have the right kind of spirit, being treated unjust itches somehow in an unpleasant way.
The only dji rep reply so far ( i agree they are generally very helpful) was so full of it, i could not even sell this to an infant. If someone would give a solid explanation we could even learn from it.

Sorry for the crash . reading this thread very carefully. I am curious how (if) this will be solved by DJI warranty. Marking... and wishing good luck.

Thanks Willik. Probably not, but would really like to know the cause

I have brought this to the attention of our support team and will make sure they follow up the case with you.

DJI Mindy Posted at 2017-2-5 19:28
I have brought this to the attention of our support team and will make sure they follow up the case with you.

Thank you . We all are eager to know the actual cause of this crash, to prevent this to happen in the future.

fansc2962bbc Posted at 2017-2-5 22:43
Thank you . We all are eager to kow the actual cause of this crash, to prevent this to happen in the future.

I showed your flight replay to a few guys in a local forum. They pointed me to the timing of error messages and warnings that pop up in the app. The first warning is "motor obstructed" and then it takes quite a longer time until further error messages appear. They say, this really looks like the aircraft hit something then crashed.

I really don't know what to believe now: The original story about a defect out of a sudden, or a physical impact resp. pilot error.

Is it just me, or is this thread not visible in the forum anymore?

Dronoob Posted at 2017-2-5 23:36
Is it just me, or is this thread not visible in the forum anymore?

Yes. It looks like the tread has disappeared. Had to do a search to find it.

Dronoob Posted at 2017-2-5 23:34
I showed your flight replay to a few guys in a local forum. They pointed me to the timing of error messages and warnings that pop up in the app. The first warning is "motor obstructed" and then it takes quite a longer time until further error messages appear. They say, this really looks like the aircraft hit something then crashed.

I really don't know what to believe now: The original story about a defect out of a sudden, or a physical impact resp. pilot error.

Dronoob.  I stick to my story. Nothing hit the Mavic in air. I really kick myself for not having filmed the flight. A video of the flight had probably been the last piece in the puzzle to convince  people.
The cost of repair is not a big issue to me, but the reason the Mavic went down. I really dont think I will dare  to fly the drone anywhere near people or in urban areas unless this issue is revealed.

Where did this thread go.  Bermuda Triangle ..

DJI Mindy Posted at 2017-2-5 19:28
I have brought this to the attention of our support team and will make sure they follow up the case with you.

Why has this thread disappeared?

Up..see if it appears on top.