> For the complete documentation index, see [llms.txt](https://docs.freeflysystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freeflysystems.com/flying-sun/flight-operations/pro-tips.md).

# Pro Tips

**App features:**

* The overlay bubble shows tether power, length and an HV toggle on top of AMC, so you don’t need split screen.
* If BLE drops, the app keeps showing estimated power and length, calculated from aircraft telemetry.

**Tether handling:**

* Adjust tension mid-flight: run it lower near the ground for agility and raise it while climbing or in wind at altitude.

{% hint style="info" %}
To adjust tension, swipe down on the ground unit screen to open the Settings menu.
{% endhint %}

* Lay the tether out away from foot and vehicle traffic.
* When manually retracting tether cable during pack up.&#x20;
  * Release Take Up before the plug reaches the ground unit so the cable doesn’t retract too fast.
  * Guide the cable by hand while it retracts. This helps control the retraction speed and lets you inspect the cable for damage.

**Power management:**

* Dim the lights while climbing, then bring them back up at altitude. This avoids hitting the power limit.
* Know your baseline draw (about 1100W with lights off, about 2800W at 100%). A creeping number is an early sign of wind or a problem.
* For long nights on a generator, size the fuel for the full flight plus a buffer.

**Operations:**

* If the tablet has an issue, HV can still be controlled from the ground unit screen.
* Keep sunglasses handy, since the 175,000-lumen panel is blinding at close range.
* Wind at 80m can be much stronger than on the ground, so plan tension and position for that.

**Limitations:**

* Don’t fly in the rain.
* The power limit is 3000W, and the ground unit shuts down above it.
* Tether length is 110m, with the alarm at 95m.
* Estimated values are approximate. Treat them as a backup, not as primary data.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.freeflysystems.com/flying-sun/flight-operations/pro-tips.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
