DJI Responds to Third-Party App Claiming 120-Meter Altitude Limit Bypass

DJI has issued a response to a third-party modified application that claims to remove the 120-meter altitude limit on its drones, according to a report from Guandian.cn. The development sits at the intersection of firmware control, regulatory compliance, and the broader secondary market for DJI hardware, where software provenance is becoming a more visible part of purchase and fleet decisions.

The source report is limited in technical detail, but the central fact is clear: a modified app outside DJI's official ecosystem is being positioned as a way to alter a flight restriction that many operators understand as a standard safety and compliance boundary. DJI's response signals that the company is paying attention to how third-party software claims circulate among drone users, even when those claims are not tied to an official product release or firmware update.

What the source report actually says

Guandian.cn, a China-based industry publication, reported that DJI responded to the existence of a third-party modified app claiming to lift the 120-meter altitude limit. The report does not include a detailed technical breakdown of the app, its distribution method, or whether DJI confirmed that the modification works as claimed. What it does establish is that DJI felt it necessary to respond publicly to the claim.

This matters because DJI does not typically comment on every third-party software project that appears in drone forums or social channels. A response suggests that the claim was visible enough, or potentially misleading enough, to warrant an official position. For commercial operators, that is a signal worth noting: unofficial altitude-limit workarounds are not a quiet corner of the hobbyist world anymore. They are being discussed in industry media and drawing manufacturer attention.

The report does not provide a direct quote from DJI in the source data available for this analysis. Reboot Hub analysis should therefore treat the exact wording and enforcement posture of DJI's response as unconfirmed. The verified development is narrower: DJI responded, and the response was covered by a commercial drone industry outlet.

Why altitude limits are a commercial issue, not just a hobbyist debate

The 120-meter altitude limit is not simply a software setting. For many commercial operators, it is a compliance boundary tied to airspace rules, insurance requirements, and client contracts. A drone that can be pushed above that limit through an unofficial app creates several practical problems. Flight logs may not align with operational declarations. Insurance coverage may be compromised if a flight is later reviewed. A client audit may flag software that was not part of the manufacturer's supported ecosystem.

For fleet managers, the issue is even more direct. A mixed fleet where some aircraft run official firmware and others carry modified software introduces inconsistency into training, maintenance, and incident review. If a drone is involved in an incident, the software state becomes part of the investigation. A modified app that alters altitude behavior can complicate that review, regardless of whether the modification was actually used on the flight in question.

The pre-owned DJI market is also affected. Buyers evaluating an inspected pre-owned drone often focus on physical condition, battery cycles, and flight hours. Software history is harder to verify. A drone that has been paired with a modified app may carry no visible trace, but the operational risk transfers to the new owner. This is one reason why purchase documentation and seller transparency are becoming more valuable in second-hand drone transactions.

What this means for drone owners and the market

The immediate takeaway for drone owners is that unofficial altitude-limit workarounds carry a different risk profile than they did a few years ago. Manufacturer attention, regulatory scrutiny, and insurance review processes have all matured. A pilot who uses a modified app to exceed the 120-meter limit is not just bending a software setting. They are introducing a variable that can affect insurance, client trust, and resale value.

For buyers in the pre-owned DJI market, this report reinforces the case for asking about software history before purchase. A drone that has been operated with modified apps may look identical to one that has only run official firmware. The difference shows up later, in flight log reviews, firmware updates, or support interactions. Reboot Hub's Drone Wiki is one reference point for operators who want to understand how software, firmware, and hardware condition interact when evaluating a used DJI platform.

For repair customers, the implication is more subtle. A drone brought in for service after running unofficial software may present diagnostic challenges. Repair technicians working with genuine OEM spare parts need to understand whether a fault is mechanical, firmware-related, or caused by third-party software. A customer who discloses modified app usage helps the repair process. A customer who does not may face longer diagnosis times or repeated faults that look like hardware failures but are actually software state issues. For owners evaluating service and lifecycle risk, Drone Wiki explains the relevant repair, parts, resale, or operational path.

The broader market signal is that DJI's attention to third-party software claims is not fading. As the secondary market grows and more operators buy pre-owned DJI drones, the distinction between supported and unsupported software will become a more formal part of how drones are priced, inspected, and sold. Sellers who can document clean software history may find that transparency becomes a commercial advantage.

What operators should do differently now

The practical guidance for a buyer, pilot, or fleet manager is straightforward. First, keep aircraft on official firmware and official flight apps unless there is a documented, compliant reason to do otherwise. Second, if you are purchasing a pre-owned DJI drone, ask the seller about software history, app usage, and any modifications. Third, if you operate commercially, document your software state before high-value flights. That documentation can be useful in an insurance review or client audit.

This is not about panic. It is about treating software provenance as part of the asset. A drone is more than its airframe and camera. Its firmware state, app ecosystem, and flight log integrity all affect what the aircraft is worth and how safely it can be operated in a commercial environment. The Guandian.cn report is a reminder that those factors are now visible enough to draw manufacturer responses.

For the pre-owned market specifically, the report suggests that clean, documented software history will become a differentiator. Buyers who currently focus only on physical condition may start asking the next question: what software has this drone actually run? Sellers who can answer that question with confidence will be better positioned as the market matures.