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

• Field 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:

  otherInfo=TALT/KFTY

  • fuelEndurance

  • peopleOnBoard

    • Number of people on board. If peopleOnBoard should be TBN, leave out this parameter and set peopleOnBoardIsTBN to true. If there is no value for peopleOnBoard and peopleOnBoardIsTBN is false or missing, or a peopleOnBoard value is given and peopleOnBoardIsTBN is true, then the request will be rejected

  • peopleOnBoardIsTBN

    • If peopleOnBoard should be TBN, peopleOnBoardIsTBN should be set to true. If there is no value for peopleOnBoard and peopleOnBoardIsTBN is false or missing, or a peopleOnBoard value is given and peopleOnBoardIsTBN is true, then the request will be rejected

  • peopleOnBoardExtended

    • Number of people on board, allowing for additional characters consistent with the ICAO 2016 format.

  • supplementalRemarksExtended

    • For remarks pertaining to field 19, Supplemental Remarks, use the suppRemarksExtended field

  • pilotInCommand

  • 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),pilotData” is

  • pilotData:

    • The “pilotData” field i

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

  • aircraftColorExtended=W:B:BK

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

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

    • 

    • aircraftColor - If this field is used, when the flight is retrieved, the color will be in the aircraftColorExtended field. See: See: 10.24 Leidos Web Service Release Notes

  • Gear:

    • survival=MJ   [PDMJ]

      • There are four possible types of survival equipment, so include the leading character for each type you want on the flight plan.  So “PDMJ” is the code to indicate all four types are on this flight plan (Polar, Desert, Maritime, Jungle)

      • This field is 1-4 characters that must be “P”, “D”, “M” and “J” (each character can only occur once in the string, order is not important)

    • jackets=LightLUVF

      • There are four possible types of jackets, so include the leading character for each type you want on the flight plan.  So “LUVF” is the code to indicate all four types are on this flight plan (Light, UHF, VHF, Fluorescent)

      • This field is 1-4 characters that must be “L”, “U”, “V” and “F” (each character can only occur once in the string, order is not important)

    • numberOfDinghies=1

    • capacityOfDinghies=8

    • colorOfDinghies=yellowYELLOW

    • coveredDinghies=true

    • radios=UVE

      • There are three possible types of radios, so include the leading character for each type you want on the flight plan.  So “UVE” is the code to indicate all three types of radios are on this flight plan (UHF, VHF, ELT/ELBA).
        “E” is the code to indicate only ELT/ELBA radios are on the flight plan

      • So this field is 1-3 characters that must be “E”, “U” and “V” (each character can only occur once in the string, order is not important)

  • 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>

• • You can specify alternate takeoff in the otherInfo field.