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

# Flight Part 3: Landing and Pack up

#### Landing:

1. Dimming the lights before landing is recommended to avoid blinding the pilot.
2. Aircraft should land where it launched.
3. Aircraft should land with no tension in the cable.
   1. As the aircraft descend and fly closer to tether, the tension in cable will be released.

#### Pack Up:

1. After disarming, disable HV from the app or the screen and confirm it’s off.
2. Turn off the SL8, then disconnect the LP12 and the strain relief.
3. Retract the cable: hold Take Up in the app and release it before the plug reaches the ground unit.

{% hint style="info" %}
Take Up only works with HV off.
{% endhint %}

1. Check the cable isn’t kinked or knotted as it retracts.
2. Turn off the backup power switch, then the main power switch.
3. Disconnect AC input from the power source and pack up.


---

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