> For the complete documentation index, see [llms.txt](https://docs.deltaquad.com/evo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deltaquad.com/evo/maintenance/preventative-maintenance.md).

# Preventative maintenance

To keep your DeltaQuad EVO in proper condition the following steps should be taken:

## After every flight

* Clean the propellers of any dirt and inspect for damage.
* Clean the fuselage and wings, this will improve performance.
* Inspect the avionics, and make sure all components are still securely attached in their proper place and all connectors are securely fastened.

## After 200 flights or 12 months

To keep your vehicle in the best condition and safe to operate beyond this point scheduled maintenance should be performed. A maintenance kit can be ordered from your DeltaQuad representative.

## Replacing components

The DeltaQuad EVO has been designed to allow easy replacement of components. Every component on the DeltaQuad EVO is available as a replacement part. 

The maintenance kit includes detailed instructions on all replacement parts.


---

# 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.deltaquad.com/evo/maintenance/preventative-maintenance.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.