> For the complete documentation index, see [llms.txt](https://support.airspacelink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.airspacelink.com/user-guides/manually-create-flight-log-from-operation.md).

# Manually Create Flight Log from Operation

Even if automated flight log capture via the [Flight Log Sync App](/user-guides/executing-an-operation-and-automatic-flight-log-capture.md) is not used, Operators can manually create a flight log and associate it with a specific operation. This process ensures that a record of the actual flight details is linked to its corresponding operational plan.

**Steps to Manually Create a Flight Log:**

1. Navigate to the relevant operation within AirHub<sup>®</sup> Portal after its completion. You can find past operations in the "Plan" section.
2. Within the operation's detailed view, locate and click the **"+ Add Flight"** button.
3. Once that button is clicked, you can enter all the necessary information to properly log the record of your drone flight. This includes details such as:
   * **Flight Summary:** Operation plan, date and time, and duration.
   * **Location:** The exact geographic location of the flight.
   * **Crew:** Details of the Remote Pilot in Command and any additional crew members.
   * **Aircraft System:** The specific aircraft used for the flight.
   * **Incidents:** If any incidents occurred during the flight, you can toggle this option on and provide details. This includes selecting an **Incident Type** and a detailed **Description of the incident**.
   * **Notes:** Any additional notes or observations about the flight.

**Manually Uploading Telemetry Files:** In addition to manual data entry, you can also manually upload telemetry files (such as DJI (.txt, .csv), Mavlink (.bin), or .kml files) directly to a flight log. Uploading these files automatically associates the telemetry data with the flight log and generates a visual flight path for the recorded flight.


---

# 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://support.airspacelink.com/user-guides/manually-create-flight-log-from-operation.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.