Content Comparison

This page is in progress. If you have specific questions on these or other fields, send an email to t R-FFSP-WebServicesSupport@leidos.com

• aircraftColorExtended=W:B:BKField 18:

  • OtherInfo

    • The RMK/ field pertains to flight plan fields, up through field 18, Other Info.

    • otherInfo=TALT/KFTY

      • You can specify alternate takeoff in the otherInfo field.

• Field 19 - Supplementary Information

  • Image Added

    Note field 19 (Supplementary Information) is not transmitted to ATC for IFR flights.

  • In the FileFlightPlan web service, the SPL contains the following parameters (although this is not a complete list). 

    • supplementalRemarksExtended

      • Remarks pertaining to field 19.

    • supplementalRemarks

      • This field is an older field and should not be used. Instead, use supplementalRemarksExtended.

    • C/ [PIC name] {PIC phone] LIC [PIC pilot license] [Address] [home base] – composed of both pilotInCommandExtended and pilotData

      • pilotInCommandExtended

        • The “pilotInCommandExtended” field is ICAO Form Field 19 and has stricter character validation requirements as part of the official form. “(e.g. cannot contain “.” or “,” characters).

        • We don’t return data in this field since it is personal information (PII). If the flight plan is retrieved, this field will contain "pilotInCommandExtended": "PII restricted.”

      • pilotInCommand

        • This field is not used. Use pilotInCommandExtended.

      • pilotData:

        • The “pilotData” field is a free-text field for informational purposes and since there’s no official restrictions, we allow more characters.

        • We don’t return data in this field since it is personal information (PII). If the flight plan is retrieved, this field will contain: "pilotData": "PII restricted.”

    • aircraftColorExtended

      • 1-500 alphanumeric characters including spaces; use ":" to separate colors.

      • For example: aircraftColorExtended=W:B:BK

      • In the above example, white is the dominant color with blue and black markings on the plane.

    Valid values are:
  • Image Removed
  • aircraftColor -

    • • See the help text at the Flight Service website for specific allowed values.

    • aircraftColor

      • Use aircraftColorExtended. If this field is used, when the flight is retrieved, the color will be in the aircraftColorExtended field.

    See:

  radios=UVE

  • There are three possible types of radios

    • • See: 10.24 Leidos Web Service Release Notes

    • Gear:

  • survival=MJ   [PDMJ]

    • Polar, Desert, Maritime, Jungle

  • jackets=Light

    • Light, Fluorescent, UHF, VHF

  • numberOfDinghies=1

  • capacityOfDinghies=8

  • colorOfDinghies=yellow

  • coveredDinghies=true

  • radios=E  

    • [U V E]: U=UHF; V=VHF; E=ELT/ELBA

• pilotData - If needed, a Flight Service specialist

• will attempt to contact the pilot from the “pilotData” field in the flight plan web service. By convention, the “pilotData” field should contain the pilot's last name, first name, phone number, base airport, and base airport phone number.

  • pilotData=Joe Smith, <address>, <phone number>

• otherInfo=TALT/KFTY

  • You can specify alternate takeoff in the otherInfo field.

• • • • Survival

        • There are four possible types of survival equipment, so include the leading character for each type you want on the flight plan.  So

    “UVE”

    • • • “PDMJ” is the code to indicate all

    three

    • • • four types

    of radios

    • • • are on this flight plan (

    UHF

    • • • Polar, Desert,

    VHF

    • • • Maritime,

    ELBA

    • • • Jungle)

    .
    “E” is the code to indicate only ELBA radios are on the flight planSo this

    • • • This field is 1-

    3

    • • • 4 characters that must be

    “E”

    • • • “P”, “D”,

    “U”

    • • • “M” and

    “V”

    • • • “J” (each character can only occur once in the string, order is not important)

  survival=PDMJ

  • • • jackets

        • There are four possible types of

    survival equipment

    • • • jackets, so include the leading character for each type you want on the flight plan.  So

    “PDMJ”

    • • • “LUVF” is the code to indicate all four types are on this flight plan (

    Polar

    • • • Light,

    Desert

    • • • UHF,

    Maritime

    • • • VHF,

    Jungle

    • • • Fluorescent)

        • This field is 1-4 characters that must be

    “P”

    • • • “L”,

    “D”

    • • • “U”,

    “M”

    • • • “V” and

    “J”

    • • • “F” (each character can only occur once in the string, order is not important)

  jackets=LUVF

  • There are four possible types of jackets

    • • numberOfDinghies

        • 2 characters

      • capacityOfDinghies

        • 3 characters

      • colorOfDinghies

        • 1 – 20 characters (color code such as ‘Y’ or spelled out “YELLOW”

      • coveredDinghies

        • true or false

      • radios  (This is R/ on the FAA ICAO Supplementary Section of the Flight Plan Form.)

        • There are three possible types of radios, so include the leading character for each type you want on the flight plan.  So

    “LUVF”

    • • • “UVE” is the code to indicate all

    four

    • • • three types of radios are on this flight plan (

    Light,

    • • • UHF, VHF,

    Fluorescent)

    • • • ELT/ELBA).
          “E” is the code to indicate only ELT/ELBA radios are on the flight plan

        • This field is 1-

    4

    • • • 3 characters that must be

    “L”

    • • • “E”, “U”

    ,

    • • • and “V”

    and “F”

    • • • (each character can only occur once in the string, order is not important)