> 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/ecosystem/payloads/wiris-pro-thermal/operating-handbook/pre-flight-planning.md).

# Pre-flight Planning

## Weather

* While Astro can fly in the rain, the Wiris Pro camera does not offer any ingress protection, so we do not recommend flying in any precipitation.
* In cold temperatures:
  * We recommend allowing 3-5 minutes of warm-up time after powering on. This allows the IR sensor inside the Wiris Pro to reach a steady operating temperature for the most accurate temperature measurements. During the warmup time, the gimbal and camera will still work as normal, however the temperature data from the IR sensor may be less accurate.
  * Make sure your Astro batteries don't get too cold. More info can be found in this section of [the wiki](https://freefly.gitbook.io/astro-public/astro/pilots-operating-handbook/limitations).
* The Wiris Pro Payload matches Astro's operational temperature range of -20C to +50C

## Checks

* Check that the Wiris Pro Payload is secured in the Smart Dovetail mount and that the safety latch is closed.
* When you’re ready to fly, perform the standard preflight checks for Astro (found below).

{% content-ref url="<https://github.com/freefly-systems/wiki-public-ecosystem/blob/main/pilots-operating-handbook/flight.md>" %}
<https://github.com/freefly-systems/wiki-public-ecosystem/blob/main/pilots-operating-handbook/flight.md>
{% endcontent-ref %}


---

# 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/ecosystem/payloads/wiris-pro-thermal/operating-handbook/pre-flight-planning.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.