> 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/overview/flying-sun-500-quick-start-guide.md).

# Flying Sun 500 Quick Start Guide

The Flying Sun 500 (FS500) is a high-intensity, tethered lighting module designed for the Astro platform. It provides 175,000 lumens of illumination and is rated for continuous, dusk-to-dawn operation.

{% hint style="danger" %}
WARNING: Review All Safety Information Before Use

Failure to adhere to the following protocols may result in serious injury or equipment damage.

* Prerequisite Knowledge: The Flying Sun 500 is an Astro-based platform. Users must read and understand the [Astro Pilot Handbook](https://docs.freeflysystems.com/astro/) before operation.
* High-Voltage Hazard: The system is powered by a high-voltage tether. All personnel must review the [Safety Information section](https://docs.freeflysystems.com/flying-sun/flight-operations/safety.md) regarding high-voltage systems before setup or use.
* Environmental Limitation: Do not operate the FS500 in rain or any other precipitation. Operation in wet conditions is prohibited.
  {% endhint %}


---

# 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/overview/flying-sun-500-quick-start-guide.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.
