Something went sideways? Let's get you back in the air.

Sign in and open your account orders page. Storefront orders show payment, packing, and shipment state there. If you need help on a specific order, start the support request while signed in so the order can be attached directly.

Yes. Start a support request with the same email address used at checkout and include the storefront order number. If you later create an account with that same email, eligible storefront orders can be linked to the account.

Send the order number, destination country, carrier name if visible, and a screenshot or copy of the tracking event you see. Carrier pages can lag or disagree, so the exact tracking state helps support check the shipment faster.

Send clear photos of everything received, the shipping box, labels, packing material, and the full contents laid out together. Check the packaging carefully before opening the case; small antennas, cables, screws, foam, and adapters can hide in inserts or small bags.

Use another payment method shown at checkout when available, such as bank transfer or cryptocurrency. For bank transfers, include any bank fees so the received amount matches the order total, then keep the payment slip because support may ask for it when matching the payment.

First clear the browser cache or try a different browser. If the storefront still refuses the item, open a support request with your browser, operating system, account email, and a screenshot of the cart error. Velocidrone licenses can also be purchased directly from Velocidrone when the issue is urgent.

Open a support request and choose warranty or repair. Include the product name, order or purchase context, serial number if available, photos of the product, photos of wiring or installation, and a direct description of the fault and when it started.

No. Start with a support request. Support will review the evidence first and tell you whether the next step is setup correction, more troubleshooting, replacement parts, repair, or a return.

Low output at high power can point to a power amplifier problem, but first confirm antenna condition, correct region, current firmware, clean module pins, and a known-good antenna. If range stays poor, open a support request with the module model, firmware version, antenna used, output power setting, and a short range-test description.

Send photos or a short video showing the screen behavior, the firmware version, connector condition if you opened the unit, and whether the device is still detected by TBS Agent. Do not keep re-flashing repeatedly if the unit is no longer detected; capture the current state and open a case.

Buy from Team BlackSheep or authorized TBS distributors when warranty, authenticity, and supply-chain traceability matter. Marketplace listings can be legitimate, but TBS cannot guarantee every third-party listing or counterfeit replacement part.

Start with Agent Web for normal configuration and firmware updates. Use Agent Desktop or Agent M when a product needs a desktop recovery path or when the support article for that product explicitly calls for it.

Use bootloader mode over USB. With the radio powered off, hold F while plugging in USB for the Crossfire side, or hold E while plugging in USB for the FreedomTX or EdgeTX side. Re-flash the radio firmware first, then the Crossfire firmware. The radio does not need to power on normally while it is in bootloader mode.

Try bootloader mode first, then re-flash FreedomTX or EdgeTX and Crossfire firmware through TBS Agent. Use a known data-capable USB cable and a direct computer USB port. After recovery, format the SD card as FAT32 and load the latest SD card contents from the Tango 2 product page if files are missing or corrupt.

Update the Mambo in bootloader mode. With Mambo powered off, hold Page while connecting USB to flash the radio firmware, then hold Menu while connecting USB to flash the Tracer or RF firmware. After both updates, refresh the SD card contents and confirm the external module bay is enabled in the model settings.

This usually points to mismatched or incomplete firmware on the radio/module side. Update both the radio firmware and the RF module firmware in the correct bootloader modes, then reconnect. If the device still appears but no parameters load, open a support request with the Agent version, device name, firmware versions, and screenshots.

Use the forgot-password flow for the email address on your TBS account and check spam or junk for the reset email. If login still fails after a reset, try a clean browser session or another browser and include screenshots of the error in a support request.

Hold the boot button while connecting USB, or use the Betaflight CLI command bl when the board is still reachable. On Windows, open Zadig, enable List All Devices, select the DFU device, install or replace the driver with WinUSB, then flash from the Betaflight firmware flasher.

Put the Nano RX into bind mode; a slow green pulsing LED indicates it is waiting. Put the transmitter or Tango radio into Crossfire bind mode. If firmware differs, allow the receiver update to finish before power cycling. A solid or normal green link state confirms the bind.

Crossfire binding data follows receiver ID history. Changing the receiver ID and power cycling can break the current link, but returning to the old ID may reconnect. To prevent reconnection, bind the receiver to a new unused transmitter ID and complete a firmware update or rebind cycle so the old association is overwritten.

If encryption is enabled, use one intended receiver at a time. Unbind or power down other receivers, update to current Crossfire firmware, perform a clean bind, and verify stable telemetry in Betaflight. If bind still fails, perform the documented emergency reset and then bind again.

Use different model/bind behavior where possible, such as Model Match, and configure different arm switch logic on the flight controllers. If both receivers are powered and bound in a way that accepts the same control signal, telemetry warnings alone do not prevent both aircraft from receiving control commands.

The warning can appear when RF energy is too strong at very close range or when another transmitter is close to the module. Increase physical distance between radios/modules, check antenna placement, and test again away from other active transmitters before assuming hardware failure.

It depends on whether the flight controller firmware forwards the needed CRSF VTX control. If the stack does not forward those commands, functions like PIT mode may not be controllable through that path. Use the VTX table or direct configuration path supported by the flight firmware.

Connect each ESC signal wire to an individual motor output pad such as S1, S2, S3, and S4. Do not tie all ESC TX pins into one receiver pad unless you are deliberately setting up supported telemetry. Use a proper PDB for high-current power and ground distribution, then select the correct motor protocol such as DSHOT600 in Betaflight.

Any motor phase order can spin a brushless motor, but the direction may be wrong. Solder cleanly, test one motor at a time without props, then reverse direction in firmware or by swapping two motor phase wires if needed.

Check the user1 mode in INAV. On the Lucid Wing AIO, user1 can control VTX power and must be assigned like a mode switch. Confirm the switch range is active and the physical switch is on before assuming the VTX power rail is faulty.

Use the battery monitor calibration values from the H7 Wing support notes: set BATT_VOLT_MULT to 21 and BATT_AMP_PERVLT to 8.1, then verify against a known good pack or meter. If your wiring or power module differs, treat those values as the starting point and calibrate carefully.

Yes, the Lucid 90A ESC supports KISS telemetry. Compatible flight firmware can read values such as voltage, current, temperature, and RPM when the telemetry wire and firmware settings are configured correctly.

Wire the ESC telemetry/current-sense output to a compatible flight-controller input, then configure the telemetry or current sensor source in Betaflight, INAV, or ArduPilot as appropriate. Test without props first and compare readings against expected bench current before flying.

Inspect both ends of the connector for bent or recessed pins, try the spare cable from the loom, test a known data-capable USB cable, and try another computer. If all combinations only provide power, include close-up connector photos in the support request.

Avoid old configurator/firmware combinations when setting up current Lucid or Mojito hardware. If a guide calls out INAV 8 or newer, update both configurator and firmware together before troubleshooting wiring or sensor behavior.

Usually yes. Apply gentle heat with a hair dryer or heat gun, carefully bend the elevon back to the correct shape, and hold it in place until it cools. Use moderate heat only; overheating foam or hinges can cause permanent damage.

Minor dents usually do not affect flight. Foam can often be restored with steam, hot water, or warm air. Apply heat gradually, let the foam expand, and cool it in shape. If a surface is badly warped or alignment is affected, send photos before modifying it further.

Check center of gravity, elevon neutral position, correct surface direction, wing straightness, and launch mode setup. If one wing half is visibly warped or the trim required is excessive, document the warp with photos from the leading edge, trailing edge, and top view.

Confirm correct CG, correct elevon direction, correct level calibration, enough launch power, and suitable INAV auto-launch settings before testing again. Remove props for bench checks and verify that stabilization moves surfaces in the direction that corrects the aircraft.

Yes. The Source One frame family is designed around replaceable plates and arms. Confirm the exact frame version and middle-plate version before ordering spares, because parts are not always interchangeable across V5, V6, HD, and custom variants.

Do not assume TPU parts interchange between Source One versions. Check the exact frame generation and mount geometry. If a print was made for another version, expect camera mounts, antenna mounts, or standoffs to need adjustment.

Use the Becoming a Dealer page and submit the required dealer information. TBS reviews dealer accounts before enabling dealer pricing, MOQ visibility, and ordering access. Use the same storefront account for future dealer support.

Sign in with the account that has dealer access, then start a dealer support request. This lets support see the storefront account context and avoids mixing dealer questions with unrelated guest requests.

Some products, especially batteries and regulated items, can be restricted by destination, carrier, warehouse, or dangerous-goods rules. If checkout blocks the item, include the destination country and product SKU in a support request so the team can confirm whether another channel or dealer is better.

Check the official TBS dealer information first. If supply-chain security matters for a project or procurement requirement, open a support request with the reseller name, country, and product list you plan to buy.