Autel Error Code 103000 indicates that the communication link between your remote controller and the aircraft has been severed, or the Autel Explorer app has lost data communication with the controller. When this alert appears, telemetry, live video transmission, and manual control inputs cannot reach the drone. If this happens mid-flight, the drone’s automated Failsafe Return-to-Home (RTH) protocol should initiate. On the ground, it locks takeoff until the radio link or USB interface is restored.
Fast Fix
Check the remote controller’s built-in display: if telemetry is visible on the controller screen, replace the USB-C cable connecting your phone or tablet to the controller. If the controller itself shows no connection, point the flat faces of the controller antennas directly at the drone, cycle power on both devices, and execute a manual re-linking procedure.
Quick Safety Snapshot
- Severity: Critical (Mid-Flight) / Moderate (Pre-Flight)
- Safe to Fly: No (flight is locked on the ground; flight control is severed in the air)
- Primary Cause: Radio frequency (RF) signal obstruction, loose or degraded mobile device USB cable, unlinked remote controller, or firmware version mismatch
- Immediate Action: If airborne, maintain visual line of sight and do not toggle flight modes erratically. Wait for the aircraft to execute its configured Failsafe RTH.
What Error 103000 Means
Autel drones (such as the EVO II, EVO Lite, and EVO Nano series) utilize a dual-stage communication pipeline:
- The Downlink/Uplink Radio Link (Autel SkyLink): Transmits control inputs from the remote controller sticks to the aircraft’s internal receiver while receiving video and telemetry from the drone over 2.4 GHz, 5.8 GHz, or 900 MHz bands.
- The Host-to-Device Interface: Transfers that incoming telemetry and video data from the remote controller to your mobile device running the Autel Explorer app via a physical USB cable or integrated screen bus.
Error Code 103000 triggers whenever this chain breaks. Diagnosing the error requires identifying whether the radio link between the controller and drone died, or if the controller is talking to the drone while the mobile app dropped offline.
Diagnostic Path: App Disconnect vs. Radio Disconnect
Before adjusting settings, determine where the connection broke:
Error 103000 Displayed in App
│
Check the Remote Controller Screen / Status LEDs
│
┌───────────────────────┴───────────────────────┐
▼ ▼
RC Shows Live Telemetry RC Shows Disconnected
(Altitude, Speed, Satellites) (Blinking Red / Beeping)
│ │
Link Broken Between Link Broken Between
Mobile Device & Controller Controller & Aircraft Body
│ │
• Inspect/Replace USB Cable • Check RF Obstructions
• Re-enable USB Debugging (Android) • Re-link RC to Drone
• Restart Autel Explorer App • Verify Aircraft Battery Power
1. The Controller Screen Displays Telemetry, but the App Shows “Disconnected”
If your remote controller has an integrated telemetry display (or if you can still yaw the gimbal using the controller dial), the aircraft is linked to the controller. The error is isolated to the cable, port, or mobile device software.
- Unplug the USB cable from the controller and phone, wait five seconds, and reconnect it.
- If using Android, confirm the USB connection mode is set to “File Transfer” or “MIDI” rather than “Charge Only.”
- Close and restart the app. If the app remains unresponsive, follow the troubleshooting steps in Autel Explorer App Not Connecting to Drone.
2. Both the Controller and the App Are Disconnected
If the remote controller’s status LED flashes slowly (indicating searching mode) or beeps, the radio receiver on the drone has lost sync with the transmitter.
- If this happens on the ground, the drone may have lost pairing or failed its receiver power-on self-test.
- If the drone recently suffered an impact or hard landing, inspect the internal antenna leads using Drone Aircraft Disconnected & Signal Lost After Crash.
Step-by-Step Troubleshooting
Step 1: Optimize Antenna Orientation
Radio signals radiate outward from the flat sides of the remote controller antennas, not the tips:
- Ensure the antennas are unfolded and positioned parallel to one another.
- Aim the flat surfaces of the antennas directly toward the aircraft’s physical location in the sky. Pointing the tips of the antennas directly at the drone creates a signal null zone that frequently triggers Code 103000 at moderate distances. For detailed positioning techniques, see Drone Antenna Orientation: How to Point Your Controller for Max Range.
Step 2: Perform a Hardware Re-Linking (Pairing) Procedure
If the aircraft and remote controller have lost their electronic pairing table, re-bind them manually:
- Power on both the remote controller and the drone.
- Connect your mobile device and launch the Autel Explorer app.
- In the app settings, navigate to the RC Settings menu and tap Pairing (or “Link”). The controller will begin beeping rapidly.
- Locate the physical pairing button on the aircraft:
- EVO II Series: The button is recessed on the side of the fuselage under a rubber port protector, or accessed by pressing and holding the aircraft power button for 3 seconds until the LEDs cycle.
- EVO Lite / Nano Series: Press and hold the drone’s power button for approximately 5 seconds until the battery LEDs flash in sequence.
- Wait for the controller to emit a solid beep and the status LED to turn solid green. If the process times out, review Drone Controller Not Connecting or Linking to Aircraft (Master Guide).
Step 3: Eliminate RF Interference and Switch Transmission Channels
Operating near cell towers, industrial high-voltage power lines, or crowded urban Wi-Fi networks can overwhelm the receiver:
- Move the drone and controller at least 50 feet away from large metal structures or communication arrays.
- In the Autel Explorer transmission menu, review the channel quality bar graphs.
- Switch from an automatic channel selector to a manual channel with low noise, or change between 2.4 GHz and 5.8 GHz frequency bands depending on line-of-sight conditions.
Step 4: Synchronize Firmware Builds
If you recently updated either the remote controller or the aircraft individually, a protocol handshake mismatch can trigger Error 103000:
- Ensure the remote controller firmware build matches the aircraft package release.
- If the remote controller failed to complete its background flash, see Autel Controller Firmware Update Failed.
- For general update and version matching issues, refer to Autel Firmware Mismatch & Compatibility Guide.
Common Misdiagnoses
- Confusing with Video Downlink Failure: If you lose the live camera feed but still have numerical telemetry (altitude, distance, battery percentage) and full stick control, the aircraft is not disconnected. This is an image transmission or camera processing error. Troubleshoot that issue under Autel Explorer App No Camera View or Video Transmission Error.
- Confusing with Battery Communication Loss: If the battery suddenly disconnects internally, the aircraft shuts off mid-air or on the bench, causing an abrupt disconnect alert. Confirm whether the drone’s power LEDs are still physically illuminated before troubleshooting radio issues; if dark, check Autel Error Code 102700 Battery Communication Error.
Hard Stops: When to Ground the Aircraft
Cease flight attempts and inspect hardware if:
- The remote controller disconnects while the drone is within 100 feet in an open, interference-free area.
- The aircraft battery LEDs turn off spontaneously, indicating power bus collapse rather than wireless disconnection.
- The pairing sequence repeatedly times out despite using official procedures and current firmware.
- Internal antenna wires inside the landing gear or drone arms are visibly severed or crushed.