> For the complete documentation index, see [llms.txt](https://docs.theseus.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theseus.us/cyclops/system-validation/flight-test.md).

# Flight Test

At this point, the hardware and software integration is complete, and Cyclops has been bench tested. The next step is observing performance in the air. Running several test flights prior to full operational deployment of Cyclops is recommended. Below is a breakdown of our standard test procedures for new platforms:

<table><thead><tr><th width="162.84375">Test Flight #</th><th>Configuration</th><th>Procedure</th></tr></thead><tbody><tr><td>Flight 1 &#x26; 2</td><td>GPS is available as the primary position source. Cyclops will run in the background during flight.</td><td>Observe background position updates on Vozilla. Collect Cyclops recording and ArduPilot logs. Analyze and confirm nominal performance of the system.</td></tr><tr><td>Flight 3 &#x26; 4</td><td>GPS is disabled by pilot. UAV navigates using Cyclops visual positioning and map matching.</td><td>Confirm nominal performance of the system on Vozilla across multiple live flights. Analyze Cyclops recordings and ArduPilot logs.</td></tr></tbody></table>

{% hint style="info" %}
Remember: Cyclops position updates **will not be used** when GPS is enabled as a position source, but they will always be recorded in the background.
{% endhint %}