OFP Import

Import flights directly from Operational Flight Plan (OFP) PDF documents.

Two OFP layouts are supported and detected automatically:

• Lido / Air France OFPs
• NavBlue OFPs

You don't need to pick a format – FlightLog recognises the document and uses the right parser.

How It Works#

1. Open a PDF OFP in any app – email, Files, Safari, or any other viewer
2. Tap Share and select FlightLog (or use "Open in FlightLog" / "Copy to FlightLog")
3. FlightLog parses the PDF and extracts the following data:
   • Flight number
   • Date
   • Route (departure and arrival airports)
   • Aircraft registration and type
   • Block times (off-block, on-block)
   • Flight times (takeoff, landing)
   • Taxi times (taxi-out, taxi-in)
   • Scheduled times (STD / STA), with delays computed against the actual times
   • Crew names (CREW field and PIC)
   • SID / STAR and the role of each airport (departure, destination, alternates, ERA, ETOPS)
   • Fuel and the NOTAM pack
   • Flight Plan Route (FPR) with full waypoint list
4. Review the extracted data on the confirmation screen

If the Flight Already Exists#

When a matching flight is found in your logbook, you are presented with three options:

• Update full flight – overwrite the fields with the OFP data (your remarks and existing scheduled times are kept)
• Update route only (FPR) – update only the flight plan route, keeping other fields unchanged
• View existing flight – open the current logbook entry without changes

If the Flight Is New#

Tap Create Flight to add the parsed OFP data as a new flight entry in your logbook.

Aircraft Matching#

When an OFP is imported, FlightLog reconciles the aircraft against your fleet:

• If the registration already exists in your aircraft list, the existing aircraft is reused – its type and details come from your fleet, not from the OFP.
• If it does not exist, a new aircraft is created from the OFP registration and type (enriched from the built-in type database).

Registrations are normalised to the same dashed form used when creating a flight manually (e.g. FABCD → F-ABCD), so matching works regardless of how the OFP prints the tail number.

Waypoint Decoding#

The FPR parser supports two waypoint encoding formats:

• ARINC 424 – standard aeronautical database format used in FMS
• ICAO – five-letter waypoint identifiers

Waypoint coordinates are downloaded from the server and follow the AIRAC cycle, ensuring up-to-date navigation data. When the AIRAC cycle updates, waypoint data is refreshed automatically.