> 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/flight.md).

# Flight Part 2: Take off and flight

#### Before takeoff

* Make sure all personnel are clear of the aircraft and tether.
* Turn on the ground unit’s main power switch and backup power button.
* Enable HV last, immediately before arming. You can enable it from the Flying Sun app or the ground unit screen.&#x20;

#### Takeoff

* Take off in Position mode or use auto takeoff.
* Ascend directly above take off point, and avoid flying laterally at low altitudes
* The ground unit keeps tension on the tether once the aircraft reaches altitude.
* Keep the tether taut during extended hovers.

#### During flight

* Monitor tether power:
  * Under about 1100W when hovering with the lights off.
  * Under about 2800W when hovering with the lights at 100%.
  * The max limit is 3000W.
* Things that increase power draw: climbing, slowing a descent, raising the lights, high altitude and wind.
* Slightly dimming the lights while climbing gives more power margin.
* Monitor tether extension. The ground unit alarms at 95m.&#x20;
* Avoid hovering at the tether zero point, where the tether can oscillate.
* If BLE drops, the app shows estimated power and length from aircraft telemetry. HV stays in its last state.
* Never leave the controls. Know how to cut the power source and keep a Class D extinguisher on hand.


---

# 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/flight.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.
