ForeFlight Integration Features

ForeFlight Integration Features

This article covers details about the ForeFlight integration functionality. Recommended to become familiar with the ForeFlight Integration Setup article first for more information. 

ForeFlight Button 

The ForeFlight button is visible on the Trip page and the Flight Log of flights that are assigned to Aircraft that are enabled for the ForeFlight integration.

Trip page:

Flight Log page:


Button states:
  1. White ForeFlight button indicates that a ForeFlight flight has not been created for this Avianis flight. This includes if one had existed previously but has been removed/deleted in ForeFlight. Pressing the white button will create the ForeFlight flight instantly, regardless of any settings. 
    1. There are no permission controls on what users are able to create. If they have access to the Trip page or Flight Log page, the user is able to press and create. 
  2. Blue ForeFlight button indicates that a ForeFlight flight has been created / exists for this Avianis flight. Pressing the blue button will open the direct link to the ForeFlight flight page in a new browser tab.
    1. It is not possible to link an existing ForeFlight flight retroactively to an Avianis flight. In order to link the flights the ForeFlight must be created from Avianis 
  3. Grey ForeFlight button indicates that a ForeFlight flight has been created / exists for this Avianis flight. However, the data syncing has been disabled due to the current flight leg status selected and the corresponding setting. Pressing the grey button will open the direct link to the ForeFlight flight page in a new browser tab.

Using ForeFlight Flight Time Estimations 

Only Avianis flights that have a linked ForeFlight flight may use the ForeFlight flight time ("FT"). 
  1. Not applied on initial create. Avianis flights will always create by first using the default FT profile within Avianis, this is because ForeFlight FT is not immediately available / takes time to calculate.
  2. Only FT, not BT. Times fetched from ForeFlight only include FT and are only applied to Avianis flights as FT. It will not include Taxi Times from ForeFlight. Avianis flight BT will be calculated on top of the ForeFlight FT using the Avianis Taxi Times as designated on the company or aircraft. 
  3. Same rounding rules apply. Avianis company or aircraft rounding settings (if set) will apply to the ForeFlight FT, so may not be an exact match to what is seen in ForeFlight.
ForeFlight FT is only for Avianis Trips/flights and not currently available to use on Avianis Quotes.



Automated Application

ForeFlight flight time ("FT") is applied automatically to Avianis flights:
  1. As soon as a linked ForeFlight is created for an Avianis flight the automated FT application process is engaged.
  2. ForeFlight flights, when first created, will use their "DCT" (aka Great Circle) calculation until their application completes the ForeFlight Recommended Route calculations. The Avianis flight will continue to show the default FT method during this time.
  3. Once the ForeFlight Recommended Route is selected, or any other route/FT change is made in ForeFlight, ForeFlight will tell Avianis that is ready and then Avianis will pull that into the Trip automatically.
  4. Avianis flights using ForeFlight times will have 'ForeFlight' displayed on the flight row on the Trip page under the FT and shown as selected on the performance profile pop-over box.
A page refresh is required to see the ForeFlight applied when it pulls in automatically.

ForeFlight routing will also display in the Avianis performance profile pop-over box.  
Manual Application 

A user may, at any time, choose to select an alternate performance profile for a flight with a linked ForeFlight. However, if a new FT selection is made in ForeFlight it will still trigger an update into Avianis. If changing to the ForeFlight FT from an alternate selection, this may only be applied to the flight selected and not all flight for the Trip at once as is possible with other performance profile selections. 
If the ForeFlight FT is applied manually too quickly after create, only the "DCT" (aka Great Circle) from ForeFlight will be fetched. 

ForeFlight Changes by Flight Leg Status

There are two Avianis flight leg status changes that affect a linked ForeFlight:
  1. Cancelled - Changing an Avianis flight leg status to Cancelled will delete the linked ForeFlight immediately on change. If the flight leg status reverts back to another status from Cancelled, a new linked ForeFlight will need to be created manually by using the ForeFlight button
  2. Released - Changing an Avianis flight leg status to Released will also release the linked ForeFlight, but only when the ForeFlight settings indicate to do so. If the flight leg status reverts back to another status from Released for any reason, manual or automated, this will not revoke the linked ForeFlight from being released. If any changes are required in ForeFlight, they must be done manually within ForeFlight directly. 

ForeFlight Information Exchange

The Avianis<>ForeFlight integration is bidirectional for some information and only unidirectional for other information. Unless otherwise indicated below, the information does not send to ForeFlight. 

Flight

  1. Flights created in ForeFlight by Avianis will be indicated on the "Created By" column on the Dispatch page
  2. Avianis Trip number is sent to ForeFlight and will display as a tag on the ForeFlight flight.
  3. Itinerary information is bidirectional. If changed in Avianis, it will automatically send/update in ForeFlight. If changed in ForeFlight, it will automatically send/update in Avianis. Itinerary information includes:
    1. Departure Airport
    2. Arrival Airport
    3. Preference (Depart At / Arrive At)
    4. Date/Time 
  4. Flight Time estimations come from ForeFlight and may be pulled into Avianis. See the flight time section above for more information. 

Aircraft

  1. Avianis aircraft assignments for a flight are sent to ForeFlight, based on which aircraft are enabled for the integration.
    1. If the Avianis flight changes assignment...
      1. to another aircraft enabled for ForeFlight, then the aircraft update will be sent to ForeFlight. 
      2. to an aircraft not enabled for ForeFlight, the linked ForeFlight will be deleted. 
    2. If the ForeFlight flight changes assignment, then the aircraft update will be sent to Avianis. 
  2. Aircraft information sent from Avianis to ForeFlight includes tail number and callsign, but all other aircraft information used in ForeFlight comes from the ForeFlight aircraft profile (not Avianis), including performance information. 

Crew Members 

  1. In order for the crew information to come over successfully from Avianis to ForeFlight, the pilot must be created as a user in ForeFlight with an email that matches the email on the Avianis Personnel Profile
  2. Crew information is only sent from Avianis to ForeFlight. Any crew or manifest/load changes made in ForeFlight will not be reflected in Avianis. 
  3. Crew information sent includes:
    1. Crew Name
    2. Crew Email / Username
    3. Crew Weight, if provided
      If not provided, uses Gender to apply standard weights as indicated in ForeFlight. 

    4. Crew Position:
      1. Avianis 'PIC' = ForeFlight 'PIC'
      2. Avianis 'SIC' = ForeFlight 'SIC'
      3. Avianis 'CKA' = ForeFlight 'CA'
      4. Any other crew position in Avianis = ForeFlight 'Other'

Passengers 

  1. Passengers designated as pets in Avianis do not send to ForeFlight
  2. Passenger information is only sent from Avianis to ForeFlight. Any manifest/load changes made in ForeFlight will not be reflected in Avianis.
  3. Passenger information sent includes:
    1. Passenger count by...
      1. Gender, if provided
        If not provided, will be added to ForeFlight 'Adult' count.
      2. Avianis 'Minor' = ForeFlight 'Child'=
      3. Avianis 'Infant' = ForeFlight 'Infant'
    2. Passenger Weight, if provided
    3. If not provided, uses Gender (or Infant/Child) to apply standard weights as indicated in ForeFlight.

ForeFlight in Activity Feed 

All activity for ForeFlight, whether manual or automated, is logged in the Activity Feed on the Avianis Trip. If there is an error for any of the Avianis<>ForeFlight integration functions, the details on the error may be found in the Activity Feed. 





    • Related Articles

    • ForeFlight Integration Setup

      The article covers the setup and settings for the Avianis<>ForeFlight integration. To learn more about the integration functionality please reference the ForeFlight Integration Feature article. ForeFlight Integration Requirements The ...
    • Charter Flight Support Integration Setup & Features

      Charter Flight Support ("CFS") provides AOG recovery sourcing and financial support for charter flights; learn more on their website. CFS Integration Setup Take the following steps to setup the Charter Flight Support integration: Engage CFS. Avianis ...
    • PNRGo Integration Setup & Functions

      PNRGo Integration PNRGo is a 3rd party service provider which facilitates legal communication between a carrier and national authorities. It supports business and charter operators to comply with PNR, API, eu-LISA and sanctions. Find more ...
    • Integration: Pulsar Fatigue Meter

      This article covers the following What is Pulsar How to configure the integration How to use the integration What is Pulsar Pulsar is a software that analyzes crew fatigue levels and warns operators if they are scheduling crew that are too fatigued. ...
    • Fuelerlinx: Configure Integration

      Are you an existing Fuelerlinx customer? If so, reach out to an Avianis Support team member and request the module be turned on. The direct email is opsupport@avianis.com. Once turned on there will be a Fuelerlinx section on the main menu. This is ...