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

# Flight Part 1: Setup for flight

#### Power source

* Single-phase 240V AC, minimum 4000W, from an EV, generator, or shore power.
* Make sure the source won’t shut down mid-flight: know where the breaker is, have enough fuel, and check the EV’s charge.
* Warning: if tether power is lost, the SL8 takes over and the aircraft RTLs automatically.

#### Environment

* No rain or precipitation.
* Avoid high or gusty wind, and remember wind is often stronger at higher altitudes.
* Check for obstacles that could snag the tether, such as trees, structures and equipment.

#### Aircraft

1. Turn on the Pilot Pro. Set D2 to 0%.
2. Place the aircraft 5–10m from the tether ground unit, with a clear radius of at least 5m.
3. Unfold the aircraft, latch the booms and unfold props.
4. Install the air unit on the right-side battery interface and connect the XT90.
5. Install a fully charged SL8.&#x20;
6. Confirm the parameter FF\_ASTRO\_TYPE is set to Flying Sun. This change requires rebooting the aircraft.

#### Tether

1. Attach the strain relief to the underside of the aircraft.
2. Connect the LP12 plug to the air unit receptacle, routing the cable clear of the props.
3. Pull out about 3m of extra cable. This sets the tether zero point.
4. Power on the aircraft and confirm the Pilot Pro is connected.
5. Connect the AC input cable to the tether ground unit, then to the power source.
6. Open the Flying Sun app and connect to the ground unit over BLE.
7. Tip: Use dual screen or overlay bubble to monitor tether and HV status while running AMC.


---

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