# OFP Brief

OFP Brief reads a Lido/Flight OFP PDF and presents the parsed data in a mobile-friendly layout.

## <mark style="color:$warning;">Parsed sections</mark>

| Section          | User-visible data                                                                                          |
| ---------------- | ---------------------------------------------------------------------------------------------------------- |
| Header           | Airline, flight number, date, route, aircraft, registration, schedule, weights, cost index, and fuel bias. |
| Times            | Scheduled and estimated off-block, takeoff, landing, on-block, and block duration.                         |
| Fuel             | Taxi, trip, contingency, alternate, final reserve, hold, planned minimum, and preliminary block.           |
| Step climbs      | Fix and flight level pairs.                                                                                |
| Waypoints        | Route log with fixes, airways, planned flight levels, times, distance, and fuel.                           |
| Alternates       | Alternate airport, distance, route, level, wind correction, time, and fuel.                                |
| Weather          | METAR, TAF, SIGMET, departure, destination, alternate, and enroute airports.                               |
| Company NOTAMs   | Reference and text where present in the OFP.                                                               |
| Dispatch remarks | Dispatcher remarks as bullet items where present.                                                          |

## <mark style="color:$warning;">Waypoint table</mark>

The waypoint table combines planned OFP data with pilot-entered actual data:

* ATA entries update progress through the flight.
* Actual fuel entries recalculate downstream expected fuel.
* Notes can hold VHF, HF, XPDR, CPDLC, or other text.
* UTC alarms can be set per waypoint.
* Direct-To can mark skipped waypoints as abeam.
* Diversion notes can store offset or heading information.

## <mark style="color:$warning;">Fuel projection</mark>

AvComp uses the planned EFOB values as a fuel curve. Once actual fuel is entered at a waypoint, following waypoints project forward from that actual value instead of the original departure fuel.

This makes the table useful for trend monitoring, but the calculation remains advisory and depends on the accuracy of the original OFP and pilot-entered data.

## <mark style="color:$warning;">Persistence</mark>

OFP Brief saves the loaded OFP session locally, including:

* Parsed OFP data.
* Block fuel input.
* Waypoint actual times, fuel, notes, alarms, and options.
* Open or closed section state.
* Export panel times.

Use the clear action when you want to remove the active OFP session from the device.

## <mark style="color:$warning;">Supported OFP formats</mark>

Current parser support is built around Lido/Flight formats used by the app's target workflows. Parsed output should always be checked against the source PDF.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.avcomp.app/reference/ofp-brief.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.