Flights created in ForeFlight Dispatch can be released to Jeppesen FliteDeck Pro X. However, any changes made in FliteDeck Pro X will not sync back to Dispatch. Releasing a flight to FliteDeck Pro X requires both a callsign and crew. The release includes route strings, alternates, and ETPs/ETOPS.
To release a flight to Jeppesen FliteDeck Pro X, follow these steps:
-
Request Dispatch FDPX Integration Access
- Enterprise customers can submit a request by logging into their support portal.
- Non-Enterprise customers can use the contact form or email team@foreflight.com.
-
Enable Jeppesen FliteDeck Pro Integration in Dispatch
- After activation, open Dispatch.
- Go to Settings > Planning Settings and locate the Release section.
- Confirm that Jeppesen FliteDeck Pro is enabled (this is enabled by default).
-
Generate FDPX Configuration
- Go to the Tools tab and open the API Console page.
- Select External EFB Integration.
- Choose Generate FDPX Configuration and copy the information provided.
-
Configure the iPad for Jeppesen FliteDeck Pro X
- Open the iPad’s Settings app.
- Select FD Pro X > Services.
- Enter the following details copied from step 3:
- Name: Any desired identifier.
- Password: Your API key.
-
URL:
https://fojar.ac.foreflight.com/API
-
Importing Flights in Jeppesen FliteDeck Pro X
- Open FliteDeck Pro X on the iPad.
- Go to the Flight tab.
- Tap Flight.
- Select Import.
- Search by callsign or tail number.
- Tap the flight to import.
- Select Load Flight to complete the process.
Importing a Flight via the Dispatch FDPX integration
NOTE: If ETOPS rings are not displayed, follow these steps:
- Tap the chevron at the bottom of Enroute Filters.
- Scroll to Other.
- Enable ETOPS.
Last Updated: