← VBar NEO/EVO VLink

2x loss of control with Vstabi NEO and crash - investigation into the causes translated

VBar › VBar NEO/EVO VLink · Started by Tommy_Speedfreak on 28 September 2026 12:1228.09.2026 12:12
Tommy_Speedfreak 28 September 2026 12:1228.09.2026 12:12
Hello everyone,

Due to two crashes that I have yet to explain, I would like to contact the electronics specialists again.

It all started with a Mikado Logo 700 that I was flying on a hot summer afternoon. At the end of a series of Tic Toc maneuvers, the helicopter suddenly went into an uncontrollable state. It reacted completely erratically to my control inputs. Interestingly, I was able to right it using the rescue system and then even land it straight down. Unfortunately, during the landing, it again became uncontrollable and destroyed itself.

I myself suspected a faulty linkage or servo horn as the cause. At least all of these were defective after the crash.

Unfortunately, I had a second crash with a SAB Kraken this weekend. I was doing a few leisurely Tic-Toc maneuvers at medium speed, I righted the helicopter to my right, and then suddenly I lost control.
Here too, the behavior was completely uncontrollable. When pitch or roll commands were entered, the helicopter rotated in an arbitrary roll or pitch axis.
I was able to level the helicopter using the rescue system and bring it just above the ground using pitch control. Pitch control worked without any uncontrolled behavior.
Since no controlled movement was possible, the only remaining option was to rescue the vehicle by straightening it, switching it off, and watching.

Initially, I suspected a technical defect here as well. However, both helicopters stalled in the same way. Neither was flying at its limits, and both times the rescue system functioned correctly during the loss of control.
The Logo 700 was one of my cleanest helicopters in the vibration menu; the flight log showed no problems.
The SAB Kraken 700 has not yet completed 40 flights.

Since both crashes exhibited identical behavior, I'm wondering if the real cause could have been an electronic problem with the NEO. My suspicion is increasingly pointing towards a stuck sensor.

Looking forward to your feedback.
Greetings Thomas
machine-translated from German · Show original
RV 28 September 2026 12:2728.09.2026 12:27
I would like the serial numbers of the stabilizers and any involved VBCt/E components. If it's a VBCc component, please retrieve the logs via USB and attach them here.

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.




1 mal bearbeitet. Zuletzt am 28.09.2026 12:54 von RV.
machine-translated from German · Show original
Tommy_Speedfreak 28 September 2026 18:5528.09.2026 18:55
Hello Rainer,

VBCt - 11002989
Logo 700 - 0020047905 - Flight 20.06.26 10:18h
Kraken 700 - 0020039935 - Flight 26.09.26 14:15h

Best regards
Thomas
machine-translated from German · Show original
RV 28 September 2026 21:5628.09.2026 21:56
Logo 700 - 0020047905 - Flight 20.06.26 10:18h

The radio connection was active until it was disconnected; otherwise, the event log would have been interrupted.
The UI log also looks plausible; I can't read anything into it.
There are a few vibration entries, it would be worth investigating them; they are also present in previous flights.


Kraken 700 - 0020039935 - Flight 26.09.26 14:15h

The radio connection was active until it was disconnected; otherwise, the event log would have been interrupted.
The UI log also looks plausible; I can't read anything into it.
There would be a few more vibration entries, and one goods level higher than with the logo; it would be worth tracking them, as they are also present in previous flights.


Generally:

Since the rescue system worked in both cases, the sensors were still functioning. However, the rescue system uses a combination of all installed sensors (3 low-range, 3 high-range, 3 accelerometers), whereas during flight, under corresponding G-loads (vibrations), only the high-range sensors would likely have been effective.

The large time gap (3 months) and dozens of "io" flights with other models within it suggest a model-related problem rather than a transmitter problem.

Perhaps Eddi could take a look at the two stabilizers in the service department, just to be safe, and see if he has anything to say about them.

Please create a service case for each stabilizer.

To do this, log in to vstabi.info and navigate to your device list (bottom left). Click on the service icon next to the relevant device.

Please fill out the form (first contact details, then a description of the problem). You can also attach images, logs, etc. If it's a warranty claim, please upload your purchase invoice.

After submitting the form, a confirmation email will be sent automatically.

Our service will then contact you via email as soon as possible.

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.
machine-translated from German · Show original
VStabi VStabi Pioneer of Flybarless