Hello everybody,
on 13.06.2019 my Typhoon H520 fell like a stone from the sky. About the crash and the then until 23.07.2019 following "discussion" with Yuneec I would like to report here.
I am currently documenting progress on a large construction site, including surveying. All necessary permits are available.
In order to measure the construction site, I set up a mission via the DataPilot and also flew it off several times successfully, so I also wanted to measure the construction site on 13.06.2019. We had sunny, slightly cloudy weather and it was almost windless ... perfect flying conditions.
For security reasons, I attach importance to a comprehensive pre-flight check before starting the drone. For this I check the H for visible damage, tightness of the rotors and check whether the battery is locked. Then I started the drone, made sure that the ST16s showed no error messages and rose to about 3 meters to check the clean execution of all control commands. This too was without problems. Then I checked again the parameters of the mission and loaded them without error messages on the H520. So I started the mission.
The H520 rose to its mission height of 45 yards and made its way to its starting point. See below linked logs from the drone.
After feeling 20 seconds, the ST16s began to vibrate and reported a complete connection loss. I had set the drone to perform an RTH in case of lost connection. However, since this did not happen, I began to search the sky, I knew where she should have been. However, I could not discover the drone anywhere. Until I saw the H520 then totally destroyed lying on the ground, about 10 meters from my point of view (starting point) away.
It was noticeable here that the battery was still stuck and just about one cm had slipped out, all the propellers still sat on the engines, just one arm was bent and the H520 crashed almost horizontally. See attached pictures.
After a phone call with Yuneec I applied for an RMA number and sent (14.06.2019) the H520 together with a complete Hergangsbeschreibung (s.o).
On 27.06.2019 I received from Yuneec then the answer that you due to an unusual rotation of the Kopters in the air, the considerable damage traces on the Kopter, the burst battery, but the undamaged battery contact strip in the Kopter, from a non-latched battery and thus one User error went out. Furthermore, Yuneec submitted an offer for a new copter and camera with 20% discount.
Then I phoned the responsible technician again. In addition, I asked by mail to answer some, in my eyes, unanswered questions. Et al I am aware of cases with incorrectly latched battery, which led to the crash, however, the battery was no longer in this case after the crash in the Kopter; Also, I pointed out again that the H was in mission mode at the moment of the crash. I also asked Yuneec to provide me with the log's read out of the copter. (I could only secure the logs from the ST16s.) See the link below. Yuneec promised to review the case again.
On 04/07/2019, I received the answer from Yuneec that the, original for Yuneec incomprehensible and unusual rotation of the Kopter in the air was due to the mission plan. Furthermore, the battery is only a little out of the Kopter herausgerutsch and this probably happened only at the moment of impact. No talk of a non-latched battery. But you can definitely rule out a material / manufacturer error. Ultimately, the user error, which would have led to the crash, could no longer be detected. Yuneec increases his discount to 30%.
On 05.07.2019 I wrote then an email to Yuneec, this time a floor higher (names are in front of me, I would not publish here) pointed to the only apparent from the log's Aufaufäligkeit out, abrupt termination of all records at 3:54, which suggesting a complete breakdown of the power supply at 45 meters altitude. These logs also match the LOGS from the ST16s.
This was also admitted by Yuneec as obvious, but it can not be clarified what could have led to this power failure. It could also have been a consequential damage from any incident in the past. On my suggestion that there are more cases, was answered evasively; Yes, at first glance, there are parallels between your case and the other cases, but after a thorough examination this assumption could not be confirmed. But I was also clearly informed that I would get any information, which was investigated exactly.
08.07.2019 until today.
Multiple phone calls with Mr. XXXX did not change Yuneec's point of view, many of my questions were ignored. The attempt of a common conversation in order to achieve a mutually satisfactory solution was also expressed with the words: "Herr Göhlich, what can this bring?" abgeschmettert.
Please find attached the link to the logs and in the appendix a few pictures:
logs.px4.io/plot_app?log=b919c...67-4338-8669-d35f46146125
Everyone should form their own opinion about the behavior of Yuneec. Personally, I am quite disappointed and can not understand the above behavior. I do not know exactly how to proceed. The H520 was my 4 drone from Yuneec and maybe / probably my last drone from Yuneec.
I find it important to Yuneec's behavior in such a case, luckily no further personal injury or property damage has been incurred to show other owners or prospects.
It's a shame that Yuneec has a good platform with the H and especially with the H520.
Greetings Marc
on 13.06.2019 my Typhoon H520 fell like a stone from the sky. About the crash and the then until 23.07.2019 following "discussion" with Yuneec I would like to report here.
I am currently documenting progress on a large construction site, including surveying. All necessary permits are available.
In order to measure the construction site, I set up a mission via the DataPilot and also flew it off several times successfully, so I also wanted to measure the construction site on 13.06.2019. We had sunny, slightly cloudy weather and it was almost windless ... perfect flying conditions.
For security reasons, I attach importance to a comprehensive pre-flight check before starting the drone. For this I check the H for visible damage, tightness of the rotors and check whether the battery is locked. Then I started the drone, made sure that the ST16s showed no error messages and rose to about 3 meters to check the clean execution of all control commands. This too was without problems. Then I checked again the parameters of the mission and loaded them without error messages on the H520. So I started the mission.
The H520 rose to its mission height of 45 yards and made its way to its starting point. See below linked logs from the drone.
After feeling 20 seconds, the ST16s began to vibrate and reported a complete connection loss. I had set the drone to perform an RTH in case of lost connection. However, since this did not happen, I began to search the sky, I knew where she should have been. However, I could not discover the drone anywhere. Until I saw the H520 then totally destroyed lying on the ground, about 10 meters from my point of view (starting point) away.
It was noticeable here that the battery was still stuck and just about one cm had slipped out, all the propellers still sat on the engines, just one arm was bent and the H520 crashed almost horizontally. See attached pictures.
After a phone call with Yuneec I applied for an RMA number and sent (14.06.2019) the H520 together with a complete Hergangsbeschreibung (s.o).
On 27.06.2019 I received from Yuneec then the answer that you due to an unusual rotation of the Kopters in the air, the considerable damage traces on the Kopter, the burst battery, but the undamaged battery contact strip in the Kopter, from a non-latched battery and thus one User error went out. Furthermore, Yuneec submitted an offer for a new copter and camera with 20% discount.
Then I phoned the responsible technician again. In addition, I asked by mail to answer some, in my eyes, unanswered questions. Et al I am aware of cases with incorrectly latched battery, which led to the crash, however, the battery was no longer in this case after the crash in the Kopter; Also, I pointed out again that the H was in mission mode at the moment of the crash. I also asked Yuneec to provide me with the log's read out of the copter. (I could only secure the logs from the ST16s.) See the link below. Yuneec promised to review the case again.
On 04/07/2019, I received the answer from Yuneec that the, original for Yuneec incomprehensible and unusual rotation of the Kopter in the air was due to the mission plan. Furthermore, the battery is only a little out of the Kopter herausgerutsch and this probably happened only at the moment of impact. No talk of a non-latched battery. But you can definitely rule out a material / manufacturer error. Ultimately, the user error, which would have led to the crash, could no longer be detected. Yuneec increases his discount to 30%.
On 05.07.2019 I wrote then an email to Yuneec, this time a floor higher (names are in front of me, I would not publish here) pointed to the only apparent from the log's Aufaufäligkeit out, abrupt termination of all records at 3:54, which suggesting a complete breakdown of the power supply at 45 meters altitude. These logs also match the LOGS from the ST16s.
This was also admitted by Yuneec as obvious, but it can not be clarified what could have led to this power failure. It could also have been a consequential damage from any incident in the past. On my suggestion that there are more cases, was answered evasively; Yes, at first glance, there are parallels between your case and the other cases, but after a thorough examination this assumption could not be confirmed. But I was also clearly informed that I would get any information, which was investigated exactly.
08.07.2019 until today.
Multiple phone calls with Mr. XXXX did not change Yuneec's point of view, many of my questions were ignored. The attempt of a common conversation in order to achieve a mutually satisfactory solution was also expressed with the words: "Herr Göhlich, what can this bring?" abgeschmettert.
Please find attached the link to the logs and in the appendix a few pictures:
logs.px4.io/plot_app?log=b919c...67-4338-8669-d35f46146125
Everyone should form their own opinion about the behavior of Yuneec. Personally, I am quite disappointed and can not understand the above behavior. I do not know exactly how to proceed. The H520 was my 4 drone from Yuneec and maybe / probably my last drone from Yuneec.
I find it important to Yuneec's behavior in such a case, luckily no further personal injury or property damage has been incurred to show other owners or prospects.
It's a shame that Yuneec has a good platform with the H and especially with the H520.
Greetings Marc
