> 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/gcs-software/vozilla/flights.md).

# Flights

The **Flights** sub page stores logs from all of your flights using a theseus system. Here, you can analyze the performance of the system, as well as compare the VPS position to GPS, if applicable. You can also use playback tools to review your flights.&#x20;

<figure><img src="/files/vAkNXrmOZDhDnv1owFld" alt=""><figcaption><p>Flights subpage</p></figcaption></figure>

## Syncing Flights

Vozilla automatically synchronizes all logs from your device. This enables you to review logs offline and share logs with our team for further analysis.

We read the `MAV_LANDED_STATE`  values from the autopilot throughout the flight to determine the state of the aircraft. Vozilla looks for transitions from `ON_GROUND` to `IN_AIR` states to determine whether logs synced off the device correspond to a real flight or a recording while on the bench.

{% hint style="info" %}
After a flight, plug your device into your laptop running Vozilla to auto sync flight logs.
{% endhint %}

## Evaluating Performance

Theseus software running on the edge automatically pulls GPS from GPS 1 on ArduPilot when it is available. These GPS positions get logged alongside our estimated position.

Once your flights are synchronized on Vozilla, you can review performance by clicking on flights listed under the Flights panel. Several tracks will appear on the map:

* Gray track shows GPS positions
* Dots show map matching points, color indicates scales with accuracy of the estimated position (red for lower accuracy, green for higher accuracy)

The accuracy figure shown under the Metrics tab is the median accuracy between GPS and map matching throughout the flight.
