The 11.1 Software Release is scheduled to be deployed in late November 2023. Details on the actual date/time will be provided as we get closer to deployment. There will be a 10 - 15 minute down-time for web services during the deployment. The Software Release will include the following. Please review the lab Leidos Web Service API (WSDL) for more detailed information regarding these updates and enhancements. 

• Alaskan Departure and Destination for IFR or YFR flight plans - To align with the Anchorage ARTCC flight planning rules and to reduce IFR or YFR flight plan rejections, only airports, heliports, lat/long, and FRDs based on VOR, VORTAC, or TACAN (NAVAIDS other than NDB) will be allowed for departures and destinations within the Anchorage ARTCC airspace for the ICAO flight plan form.

  • This includes the departure, destination, altDestination1, altDestination2, and otherInfo fields in the following web services:

    • FileFlightPlan

    • AmendFlightPlan

    • RouteBriefing

    • NavLog

  • If a departure or destination field contains AFIL or ZZZZ, then the location will be validated in the appropriate subfield in the otherInfo field (DEPT/, DEST/, ALTN/).

  • If the location is anything other than a valid airport, heliport, lat/long, or FRD based on a VOR, VORTAC, or TACAN (NAVAIDS other than NDB), then the web service response will return an error. Use of the includeCodedMessage field will return a description of the error. 

• Invalid International Round-Robin Flight Plans - For IFR or VFR flight plans, if the departure and destination is the same and anywhere in the US, and there is a point in the route field which is in foreign airspace, the response for the following web services will contain "Invalid International Round-Robin Flight":

  • FileFlightPlan

  • AmendFlightPlan

  • RouteBriefing

  • NavLog 

• NOTAM Outage Message in Route and Area Briefings - For NOTAM outages, the briefing response has been updated to include the following message in all applicable briefing sections:

  • "NOTAM data may not be current due to a US NOTAM Service interruption. A recheck of data prior to departure may be warranted."

  • This message, which applies to SIMPLE, NGB, EMAIL, and NGBV2 route and area briefings, will appear in the following briefing sections:

    • Briefing Overview

    • Temporary Flight Restrictions

    • Closed/Unsafe NOTAMs

    • Notices to Air Missions 

• NavLog - Specifying the optional parameter "includeFrequencies" with versionRequested set to 20231128 or later will return fssCommunications in the response.  This will be a list of Flight Service Stations (FSS) located within a 50nm corridor (25nm on each side) of the route of flight (i.e. MIV 122.2 255.4 BUF 122.6 255.4). Each element in the list includes FSS identifier, frequencies, RCO or NAVAID identifier, RCO or NAVAID type, RCO or NAVAID name, voice call description, and lat/long location. The elements are listed in ascending along route distance order. 

• Deprecation of HTML Route and Area Briefings - In the WSDL, the HTML briefing type was previously marked deprecated and has been removed for both route and area briefings. Valid briefing types are:

  • SIMPLE – Simple text-based briefing

  • NGB – Briefing in a structured format (JSON for REST)

  • EMAIL – PDF briefing with graphics

  • NGBV2 – PDF briefing with graphics 

If you have any questions, please email R-FFSP-WebServicesSupport@leidos.com.