Leidos Flight Service Web Services Support

The 11.5 Software Release is scheduled to be deployed on March 24, 2025 at around 0200Z, there will be a 10 - 15 minute down-time for web services during the deployment. There is no Web Service updates in this release.

The 11.4 Software Release is scheduled to be deployed on November 19, 2024. at around 0200Z, there will be a 10 - 15 minute down-time for web services during the deployment. Please review the lab Leidos Web Service API (WSDL) for more detailed information regarding these updates and enhancements. The Software Release will include the following:

• GFA and G-AIRMET products:

  • Route and Area Briefings: In briefings, textual area forecast products are now replaced with enhanced Graphical Forecast Area (GFA) products for CONUS, the Gulf of Mexico, the Caribbean, and Hawaii.  In addition, Textual AIRMETs in the CONUS region are replaced with Graphical AIRMETs forecasts.

    • NGBv2 Briefings: Graphical images for G-AIRMETs and GFA weather products replace textual AIRMETs and area forecast weather products.

    • NGB and Simple Briefings: Summary text and links to the Flight Service Interactive Map are provided for the graphical images of G-AIRMETs and GFA weather products.

    • GFA Product Codes Added:

      • GFA_CLOUD_COVER - GFA Cloud Cover

      • GFA_CLOUD_TOP - GFA Cloud Top

      • GFA_CLOUD_BASE - GFA Cloud Base

      • GFA_FLIGHT_CATEGORY - GFA Flight Category

      • GFA_VISIBILITY - GFA Visibility

      • GFA_PRECIPITATION - GFA Precipitation

      • GFA_THUNDER_COVERAGE - GFA Thunder Coverage

      • GFA_WINDS - GFA Winds

      • GFA_FREEZING_LEVEL - GFA Freezing Level

      • GFA_CEILING_LEVEL - GFA Ceiling Level

      • GFA_SURFACE_WINDS_LEVEL - GFA Surface Winds Level

    • Product Codes Removed:

      • CC - Graphical Area Forecast Cloud Coverage

      • VIS - Graphical Area Forecast Vis, Sfc. Winds, and Precip

  • Evaluate Departure Time: G-AIRMET products are added to the Evaluate Departure Time details. The existing "AIRMET" rows are renamed G-AIRMET/AIRMET. The details in the rows are based on G-AIRMETs (CONUS) and AIRMETs (Alaska/Hawaii/Caribbean). This applies to the following web services:

    • EvaluateDepartureTimeRequest - This endpoint brings the Web Site Evaluate Departure Time flight planning capability to web services. The EvaluateDepartureTime provides a summarization of the forecasted TAF and adverse conditions that a flight will encounter over a range of departure times. The response now includes G-AIRMETS.

    • RouteBriefingRequest (NGBV2) – If the “includeEvaluateDepartureTimeDetails” parameter is set to true, the response will contain the Evaluate Departure Time graphic which now includes G-AIRMETs.

  • G-AIRMET products will be added to the following Web Services:

    • RetrieveAlertByFlightIdResponse

    • RetrieveAlertByRouteResponse

    • WebServicePushNGBAlertResponse

  • GFA and G-AIRMET products are added to the Interactive Map at http://1800wxbrief.com :

    • To view GFA products, select “Map” from the main menu, click the Layers icon, and then select products in the section titled "Graphical Forecasts for Aviation."

    • To view G-AIRMETs, select “Map” from the main menu, click the Layers icon, and then select the "AIRMET" section which expands to show the G-AIRMET options.

• EMAIL briefings:

  • When the “briefingType=EMAIL” parameter is used with the areaBriefing and routeBriefing web services, the email now includes an NGBv2 PDF briefing attached to the email instead of the briefing text embedded in the email.

If you are experiencing an operational issue, please contact the National Support Center at R-FFSP-NSC@leidos.com. For other questions, please email R-FFSP-WebServicesSupport@leidos.com.

The 11.3 Software Release is scheduled to be deployed on July 30, 2024. At around 04:00 GMT (00:00 EDT), there will be a 10 - 15 minute down-time for web services during the deployment. The Software Release will include the following updates for new FAA guidelines for ICAO flight plans (Order 7110.10). Please also see the note at the end for upcoming changes in the 11.4 Software Release for GFA and G-AIRMET products.

• Flight Rules: YFR and ZFR values will no longer be allowed for the "flightRules" parameter. Each segment of the flight that will be operating under different flight rules must have a separate flight plan. If the flight rules contain YFR or ZFR, then the following web services will return an error:

  • FileFlightPlan

  • AmendFlightPlan

  • NavLog

  • RetrieveAlertByRoute

  • RouteBriefing

  • OptimizeAltitude

  • If an existing flight plan contains YFR/ZFR flight rules, then the following web services to retrieve flight data will return the YFR/ZFR value in the "FlightRules" field:

    • RetrieveFlightPlan

    • RetrieveFlightPlanSummaries 

• Flight Rule Transitions: For the following web services, if the "route" parameter contains Flight Rule transition elements "VFR" or "IFR", an error message is displayed: "\"VFR\" and \"IFR\" are invalid":

  • FileFlightPlan

  • AmendFlightPlan

  • NavLog

  • OptimizeAltitude

  • RetrieveAlertByRoute

  • RouteBriefing 

• Aircraft ID: An Aircraft ID that begins with a number will be changed to an Aircraft ID beginning with a “Q”.

  • If the “aircraftIdentifier” parameter in the flight plan starts with a number and is 7 characters, the first character will be removed, and a "Q" will be added to the front of the Aircraft ID.

  • If the “aircraftIdentifier” parameter starts with a number and is 6 characters or less, a "Q" will be added to the front of the Aircraft ID.

  • In either case, the original Aircraft ID will be added to the RMK/ subfield in the “otherInfo” field. For example, RMK/ACID 1234567.

  • This applies to the following web services:

    • FileFlightPlan

    • AmendFlightPlan

  • The new Aircraft ID will be in the response to the following web services:

    • AreaBriefing

    • RouteBriefing

    • NavLog

    • FlightInfo

    • RetrieveFlightPlanSummaries

    • RetrievePilotProfile 

• Flight Type: The "typeOfFlight" field will be optional for the FileFlightPlan and AmendFlightPlan web services. For RetrieveFlightPlan, depending on the version requested, the following applies:

  • If the version requested is older than “20240801” and the flight plan does not include the “typeOfFlight” parameter, an error will be returned:

    • "Flight contains a null typeOfFlight, not supported for versions before 20240801"

  • If NO version is requested or if the version requested is equal to or later than “20240801” and the flight plan does not include the “typeOfFlight” parameter:

    • SOAP - The "typeOfFlight" field will not be included in the response.

    • REST - The "typeOfFlight" field will be null. 

• IFR Amendment and Cancellation Cutoff: The cutoff time before ETD for IFR flight plan amendments and cancellations is updated for flight plans whose departure is within the ARTCCs specified below:

  • Anchorage: The cutoff has changed from 46 minutes to 43 minutes.

  • Boston: The cutoff has changed from 46 minutes to 55 minutes.

  • Indianapolis and New York: The cutoff has changed from 46 minutes to 61 minutes.

  • Guam and Honolulu: The cutoff has changed from 46 minutes to 22.5 hours (when an IFR flight plan would normally be sent to ATC)

    • The Guam ARTCC cutoff time applies for any airport starting with “PGxx” (such as PGUM, PGUA, PGRO, PGWT, and PGSN).

    • The Honolulu ARTCC cutoff time applies for any airport starting with “PHxx” (such as PHNL, PHOG, PHKO, and PHTO).

  • The cutoff time for all other ARTCCs remain unchanged at 46 minutes.

  • This applies to the following web services:

    • AmendFlightPlan

    • CancelFlightPlan

  • If an attempt is made to amend or cancel an IFR flight plan after the cutoff time, the following error message will be returned: "Amendment or Cancellation of an IFR flight plan departing <ARTCC name> ARTCC airspace must be at least <XX minutes/hours> prior to proposed departure time.  Please contact a Leidos Flight Service Specialist (800-WX-BRIEF) for assistance." 

• EET Subfield for International ICAO Flight Plans: International ICAO flight plans require the Estimated Elapsed Time (EET) values in the EET/ subfield of the “otherInfo” parameter (ICAO Field 18) for oceanic or FIR boundaries. For FileFlightPlan and AmendFlightPlan, the following applies:

  • If the EET/ subfield with EET elements is included in the request, they are used in the requested action.

  • If the EET elements are NOT included in the request, the EET elements are automatically calculated for each FIR boundary crossing, inserted into the “otherInfo” field, and used in the requested action.

• Full Route Clearance (FRC): For an ICAO flight plan, when an FRC is added to the RMK/ subfield in the Other Information field, the system reorders the data in the RMK/ subfield to display the FRC message first. Similarly, for a Domestic flight plan form, the system reorders data in the “remarks” field to display the FRC message first.

• PIREP Location: If the PIREP Location is a latitude/longitude and is more than 12 NM from the U.S. coastline (Continental U.S., Alaska, or Hawaii), the location will be unchanged. Otherwise, the location will be changed to a fixed radial distance (FRD) before transmission.

• Equipment Codes: For ICAO flight plans submitted through the FileFlightPlan and AmendFlightPlan web services, the meaning of some Equipment Codes (J6 & M2) have changed, and the description of other codes have changed (I, J4, M1, W, X, Y):

  • I: "Inertial Navigation"

  • J4: "CPDLC FANS 1/A Mode 2"

  • J6: "Reserved"

  • M1: "ATC SATVOICE (INMARSAT)"

  • M2: "Reserved"

  • W: "RVSM Approved"

  • X: "MNPS Approved /North Atlantic (NAT) High Level Airspace (HLA) approved"

  • Y: "VHF with 8.33 kHz Channel Spacing Capability" 

• Upcoming Changes in 11.4 Software Release for GFA and G-AIRMET products:

  • In briefings, textual area forecast products will be replaced with enhanced Graphical Forecast Area (GFA) products for CONUS, the Gulf of Mexico, the Caribbean, and Hawaii.  In addition, Textual AIRMETs in the CONUS region will be replaced with Graphical AIRMETs forecasts.

    • NGBv2 Briefings: Graphical images for G-AIRMETs and GFA weather products will replace textual AIRMETs and area forecast weather products.

    • NGB and Simple Briefings: Summary text and links to the Flight Service Interactive Map will be provided for the graphical images of G-AIRMETs and GFA weather products.

    • Product Codes Added:

      • GFA_CLOUD_COVER - GFA Cloud Cover

      • GFA_CLOUD_TOP - GFA Cloud Top

      • GFA_CLOUD_BASE - GFA Cloud Base

      • GFA_FLIGHT_CATEGORY - GFA Flight Category

      • GFA_VISIBILITY - GFA Visibility

      • GFA_PRECIPITATION - GFA Precipitation

      • GFA_THUNDER_COVERAGE - GFA Thunder Coverage

      • GFA_WINDS - GFA Winds

      • GFA_FREEZING_LEVEL - GFA Freezing Level

      • GFA_CEILING_LEVEL - GFA Ceiling Level

      • GFA_SURFACE_WINDS_LEVEL - GFA Surface Winds Level

    • Product Codes Removed:

      • CC - Graphical Area Forecast Cloud Coverage

      • VIS - Graphical Area Forecast Vis, Sfc. Winds, and Precip

  • G-AIRMET products will be added to the following Web Services:

    • RetrieveAlertByFlightIdResponse

    • RetrieveAlertByRouteResponse

    • WebServicePushNGBAlertResponse

  • GFA products will be added to the Interactive Map at 1800wxbrief.com. To view G-AIRMET and GFA products, select “Map” from the main menu, click the Layers icon, and then select the G-AIRMET and GFA products.

If you are experiencing an operational issue, please contact the National Support Center at R-FFSP-NSC@leidos.com. For other questions, please email R-FFSP-WebServicesSupport@leidos.com.

The 11.2 Software Release is scheduled to be deployed on March 19, 2024. At around 04:00 GMT (12:00 EDT), there will be a 10 – 15 minute down-time for web services during the deployment. The Software Release will include the following:

• NavLog: There is no software update for the NavLog request; however, the Leidos Web Service API (WSDL) has been updated for clarification as follows:

  • NavLog calculations are generated using 6 hours of forecast wind data. Data for the 6th hour is used for calculations beyond 6 hours.

There are changes coming in the 11.3 Software Release for the new FAA guidelines (Order 7110.10): The timeline for these changes are as follows:

• Leidos Test Lab: All 11.3 updates noted below are available in the test lab. For more detailed information regarding these updates and enhancements, please review the lab WSDL: https://ffspelabs.leidos.com/Website2/resources/doc/WebService.xml

• Operations/Production: These updates will be available with the deployment of Release 11.3 in July 2024. Details on the actual date/time will be provided as we get closer to deployment.

The changes for the 11.3 Software Release include the following updates for ICAO flight plans:

• Flight Rules: YFR and ZFR values will no longer be allowed for the "flightRules" parameter. If the flight rules contain YFR or ZFR, then the following web services will return an error:

  • FileFlightPlan

  • AmendFlightPlan

  • NavLog

  • RetrieveAlertByRoute

  • RouteBriefing

  • OptimizeAltitude

  • If an existing flight plan contains YFR/ZFR flight rules, then the following web services to retrieve flight data will return the YFR/ZFR value in the "FlightRules" field:

    • RetrieveFlightPlan

    • RetrieveFlightPlanSummaries

• Flight Rule Transitions: For the following web services, if the "route" parameter contains Flight Rule transition elements "VFR" or "IFR", an error message is displayed: "\"VFR\" and \"IFR\" are invalid":

  • FileFlightPlan

  • AmendFlightPlan

  • NavLog

  • OptimizeAltitude

  • RetrieveAlertByRoute

  • RouteBriefing

• Aircraft ID: An Aircraft ID that begins with a number will be changed to an Aircraft ID beginning with a “Q”. If the “aircraftIdentifier” parameter in the flight plan starts with a number and is 7 characters, the first character will be removed, and a "Q" will be added to the front of the Aircraft ID. If the “aircraftIdentifier” parameter in the flight plan starts with a number and is 6 characters or less, a "Q" will be added to the front of the Aircraft ID. The original Aircraft ID will be added to the RMK/ subfield in the “otherInfo” field. For example, RMK/ACID 1234567. This applies to the following web services:

  • FileFlightPlan

  • AmendFlightPlan

  • The new Aircraft ID will be in the response to the following web services:

    • AreaBriefing

    • RouteBriefing

    • NavLog

    • FlightInfo

    • RetrieveFlightPlanSummaries

    • RetrievePilotProfile

• Flight Type: The "typeOfFlight" field will be optional for the FileFlightPlan and AmendFlightPlan web services. For RetrieveFlightPlan, depending on the version requested, the following applies:

  • If the version requested is older than “20240801” and the flight plan does not include the “typeOfFlight” parameter, an error will be returned:

    • "Flight contains a null typeOfFlight, not supported for versions before 20240801"

  • If NO version is requested or if the version requested is equal to or later than “20240801” and the flight plan does not include the “typeOfFlight” parameter:

    • SOAP - The "typeOfFlight" field will not be included in the response.

    • REST - The "typeOfFlight" field will be null.

• IFR Amendment and Cancellation Cutoff: The cutoff time before ETD for IFR flight plan amendments and cancellations is updated for flight plans whose departure is within the ARTCCs specified below:

  • Anchorage: The cutoff has changed from 46 minutes to 43 minutes.

  • Boston: The cutoff has changed from 46 minutes to 55 minutes.

  • Indianapolis and New York: The cutoff has changed from 46 minutes to 61 minutes.

  • Guam and Honolulu: The cutoff has changed from 46 minutes to 22.5 hours (when an IFR flight plan would normally be sent to ATC)

    • The Guam ARTCC cutoff time applies for any airport starting with “PGxx” (such as PGUM, PGUA, PGRO, PGWT, and PGSN).

    • The Honolulu ARTCC cutoff time applies for any airport starting with “PHxx” (such as PHNL, PHOG, PHKO, and PHTO).

  • The cutoff time for all other ARTCCs remain unchanged at 46 minutes.

  • This applies to the following web services:

    • AmendFlightPlan

    • CancelFlightPlan

  • If an attempt is made to amend or cancel an IFR flight plan after the cutoff time, the following error message will be returned: "Amendment or Cancellation of an IFR flight plan departing <ARTCC name> ARTCC airspace must be at least <XX minutes/hours> prior to proposed departure time.  Please contact a Leidos Flight Service Specialist (800-WX-BRIEF) for assistance."

• EET Subfield for International ICAO Flight Plans: International ICAO flight plans require the Estimated Elapsed Time (EET) values in the EET/ subfield of the “otherInfo” parameter (ICAO Field 18) for oceanic or FIR boundaries. For FileFlightPlan and AmendFlightPlan, the following applies:

  • If the EET/ subfield with EET elements is included in the request, they are used in the requested action.

  • If the EET elements are NOT included in the request, the EET elements are calculated and used in the requested action.

• PIREP Location: If the PIREP Location is a latitude/longitude and over water (more than 12 NM from the coastline or shore) the location will be unchanged. Otherwise, the location will be changed to an FRD.

• Equipment Codes: For ICAO flight plans submitted through the FileFlightPlan and AmendFlightPlan web services, the meaning of some Equipment Codes (J6 & M2) have changed, and the description of other codes have changed (I, J4, M1, W, X, Y):

  • I: "Inertial Navigation"

  • J4: "CPDLC FANS 1/A Mode 2"

  • J6: "Reserved"

  • M1: "ATC SATVOICE (INMARSAT)"

  • M2: "Reserved"

  • W: "RVSM Approved"

  • X: "MNPS Approved /North Atlantic (NAT) High Level Airspace (HLA) approved"

  • Y: "VHF with 8.33 kHz Channel Spacing Capability"  

If you are experiencing an operational issue, please contact the National Support Center at R-FFSP-NSC@leidos.com. For other questions, please email R-FFSP-WebServicesSupport@leidos.com.

The 11.1 Software Release deployment will start on Tuesday, November 28, 2023, at 9:00 pm EST (November 29 02:00 UTC). 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.

The 10.28 Software Release is scheduled to be deployed on August 29, 2023. At around 06:00 Zulu, there will be a 10 – 15 minute down-time for web services during the deployment. The Software Release includes the following. Please review the lab Leidos Web Service API (WSDL) for more detailed information regarding these updates and enhancements.

• Deprecation of HTML Route and Area Briefings - In the WSDL, the HTML briefing type will be marked as deprecated in the 10.28 release and is currently marked as such in the test lab.

  • The HTML briefing type will be removed for both route and area briefings in a future release. You can view the updated WSDL here:  https://ffspelabs.leidos.com/Website2/resources/doc/WebService.xml.

  • Note that the RAW briefing type was previously marked deprecated and has been removed.

• AreaBriefing and RouteBriefing - For circular TFRs and UOAs, the response to these endpoints previously returned a 40-point polygon. Depending on the version requested, the response to these endpoints can now contain circular geometry instead of a polygon shape for a circular TFRs and UOAs:

  • If the version requested is prior to 20230611, for all UOAs and TFRs, the response will contain only type GeoPolygonWS.

  • If the version requested is NOT specified or is on or after 20230611:

    • For circular UOAs and TFRs, the response will contain type GeoCircleWS.

    • For non-circular UOAs and TFRs, the response will contain type GeoPolygonWS.

Vendors can try out briefings with different versions requested. See the following examples for a permanent UOA and TFR. These can be viewed on the FlightService map. In the upper, right corner of the map, click the Layer Controls icon, ensure “Weather” is selected, and in the checklist, select “TFRs” and “UOA.” To locate the UOA, use the search bar in the upper left corner of the map to find "KGTB" and click the nearby UOA to view NOTAM BDR_01/102. To locate the TFR, search for "KDAL" and click the nearby TFR to view FDC 9/2934.

Circular UOA with No Version Requested:

REST Request: https://ffspelabs.leidos.com/Website2/rest/FP/areaBriefing

includeCodedMessage=true&aircraftIdentifier=TEST01&fixName=KGTB&briefingRadius=25&departureInstant=2023-04-27T23:00:23.0&briefingType=NGB

Response:

"plainText":"NOTAM UAS Operating Area BDR_01/102DEFINED AS  20NM RADIUS OF 440336N0754317W (GTB)  SFC-29000FT (SFC-28770FT AGL) 201701091849-PERM."},"altitudeRange":{"maximum":29000,"minimum":0,"qualifier":""},"shortestLateralDistanceOfConditionToRoute":null,"geometry":{"center":{"latitude":44.059998,"longitude":-75.72139},"radius":37039.98}...

Circular TFR with No Version Requested:

REST Request: https://ffspelabs.leidos.com/Website2/rest/FP/areaBriefing

includeCodedMessage=true&aircraftIdentifier=TEST01&fixName=KDAL&briefingRadius=10&departureInstant=2023-05-03T23:00:23.0&briefingType=NGB

Response:

"plainText":"FDC 9/2934ZFW TX.. FLIGHT RESTRICTION. DALLAS, TEXAS. <br> \n   PURSUANT TO 49 USC 40103(B), THE FEDERAL AVIATION ADMINISTRATION \n(FAA) CLASSIFIES THE AIRSPACE DEFINED IN THIS NOTAM AS 'NATIONAL \nDEFENSE AIRSPACE'. ANY PERSON WHO KNOWINGLY OR WILLFULLY VIOLATES \nTHE RULES CONCERNING OPERATIONS IN THIS AIRSPACE MAY BE SUBJECT TO \nCERTAIN CRIMINAL PENALTIES UNDER 49 USC 46307.  PILOTS WHO DO NOT \nADHERE TO THE FOLLOWING PROCEDURES MAY BE INTERCEPTED, DETAINED \nAND INTERVIEWED BY LAW ENFORCEMENT/SECURITY PERSONNEL.  PURSUANT \nTO TITLE 14, SECTION 91.141 OF THE CODE OF FEDERAL REGULATIONS, \nAIRCRAFT FLIGHT OPERATIONS ARE PROHIBITED WITHIN THE FOLLOWING \nAREA(S) UNLESS OTHERWISE AUTHORIZED BY ATC \n  \nWITHIN A 1 NMR OF 325321N/0964835W OR THE CVE085004.8 UP TO AND \nINCLUDING 1500 FT AGL EFFECTIVE IMMEDIATELY UNTIL FURTHER NOTICE. 200901262213-PERM"}, "altitudeRange":null,"shortestLateralDistanceOfConditionToRoute":null,"geometry":{"shape":[{"center":{"latitude":32.889168,"longitude":-96.80972},"radius":1851.9648}]}...

Circular UOA for Version 20230611:

REST Request: https://ffspelabs.leidos.com/Website2/rest/FP/areaBriefing

includeCodedMessage=true&versionRequested=20230611&aircraftIdentifier=TEST01&fixName=KGTB&briefingRadius=25&departureInstant=2023-04-27T23:00:23.0&briefingType=NGB

Response:

"plainText":"NOTAM UAS Operating Area BDR_01/102DEFINED AS  20NM RADIUS OF 440336N0754317W (GTB)  SFC-29000FT (SFC-28770FT AGL) 201701091849-PERM."}, "altitudeRange":{"maximum":29000,"minimum":0,"qualifier":""},"shortestLateralDistanceOfConditionToRoute":null,"geometry":{"center":{"latitude":44.059998,"longitude":-75.72139},"radius":37039.98}...

Circular TFR for Version 20230611:

REST Request: https://ffspelabs.leidos.com/Website2/rest/FP/areaBriefing

includeCodedMessage=true&versionRequested=20230611&aircraftIdentifier=TEST01&fixName=KDAL&briefingRadius=10&departureInstant=2023-05-03T23:00:23.0&briefingType=NGB

Response:

"plainText":"FDC 9/2934ZFW TX.. FLIGHT RESTRICTION. DALLAS, TEXAS. <br> \n   PURSUANT TO 49 USC 40103(B), THE FEDERAL AVIATION ADMINISTRATION \n(FAA) CLASSIFIES THE AIRSPACE DEFINED IN THIS NOTAM AS 'NATIONAL \nDEFENSE AIRSPACE'. ANY PERSON WHO KNOWINGLY OR WILLFULLY VIOLATES \nTHE RULES CONCERNING OPERATIONS IN THIS AIRSPACE MAY BE SUBJECT TO \nCERTAIN CRIMINAL PENALTIES UNDER 49 USC 46307.  PILOTS WHO DO NOT \nADHERE TO THE FOLLOWING PROCEDURES MAY BE INTERCEPTED, DETAINED \nAND INTERVIEWED BY LAW ENFORCEMENT/SECURITY PERSONNEL.  PURSUANT \nTO TITLE 14, SECTION 91.141 OF THE CODE OF FEDERAL REGULATIONS, \nAIRCRAFT FLIGHT OPERATIONS ARE PROHIBITED WITHIN THE FOLLOWING \nAREA(S) UNLESS OTHERWISE AUTHORIZED BY ATC \n  \nWITHIN A 1 NMR OF 325321N/0964835W OR THE CVE085004.8 UP TO AND \nINCLUDING 1500 FT AGL EFFECTIVE IMMEDIATELY UNTIL FURTHER NOTICE. 200901262213-PERM"},"altitudeRange":null,"shortestLateralDistanceOfConditionToRoute":null,"geometry":{"shape":[{"center":{"latitude":32.889168,"longitude":-96.80972},"radius":1851.9648}]}...

Circular UOA for Version Prior to 20230611:

REST Request: https://ffspelabs.leidos.com/Website2/rest/FP/areaBriefing

includeCodedMessage=true&versionRequested=20210418&aircraftIdentifier=TEST01&fixName=KGTB&briefingRadius=25&departureInstant=2023-04-27T23:00:23.0&briefingType=NGB

Response:

"plainText":"NOTAM UAS Operating Area BDR_01/102DEFINED AS  20NM RADIUS OF 440336N0754317W (GTB)  SFC-29000FT (SFC-28770FT AGL) 201701091849-PERM."},"altitudeRange":{"maximum":29000,"minimum":0,"qualifier":""},"shortestLateralDistanceOfConditionToRoute":null,"geometry":{"point":[{"latitude":44.059063,"longitude":-75.25912},{"latitude":44.111233,"longitude":-75.26441},{"latitude":44.16216,"longitude":-75.28098},{"latitude":44.21059,"longitude":-75.30845},{"latitude":44.255318,"longitude":-75.34616},{"latitude":44.29524,"longitude":-75.39321},{"latitude":44.329353,"longitude":-75.44843},{"latitude":44.356815,"longitude":-75.51047},{"latitude":44.376938,"longitude":-75.577774},{"latitude":44.389214,"longitude":-75.64867},{"latitude":44.39334,"longitude":-75.72139},{"latitude":44.389214,"longitude":-75.79411},{"latitude":44.376938,"longitude":-75.865005},{"latitude":44.356815,"longitude":-75.93231},{"latitude":44.329353,"longitude":-75.99435},{"latitude":44.29524,"longitude":-76.04957},{"latitude":44.255318,"longitude":-76.09662},{"latitude":44.21059,"longitude":-76.13433},{"latitude":44.16216,"longitude":-76.1618},{"latitude":44.111233,"longitude":-76.17837},{"latitude":44.059063,"longitude":-76.18366},{"latitude":44.00694,"longitude":-76.17757},{"latitude":43.956142,"longitude":-76.16028},{"latitude":43.907917,"longitude":-76.13223},{"latitude":43.863445,"longitude":-76.09415},{"latitude":43.82381,"longitude":-76.046974},{"latitude":43.78998,"longitude":-75.99188},{"latitude":43.76278,"longitude":-75.930214},{"latitude":43.742863,"longitude":-75.86349},{"latitude":43.730717,"longitude":-75.793304},{"latitude":43.726635,"longitude":-75.72139},{"latitude":43.730717,"longitude":-75.649475},{"latitude":43.742863,"longitude":-75.57929},{"latitude":43.76278,"longitude":-75.512566},{"latitude":43.78998,"longitude":-75.4509},{"latitude":43.82381,"longitude":-75.395805},{"latitude":43.863445,"longitude":-75.34863},{"latitude":43.907917,"longitude":-75.31055},{"latitude":43.956142,"longitude":-75.2825},{"latitude":44.00694,"longitude":-75.26521}]} ...

Circular TFR for Version Prior to 20230611:

REST Request: https://ffspelabs.leidos.com/Website2/rest/FP/areaBriefing

includeCodedMessage=true&versionRequested=20220611&aircraftIdentifier=TEST01&fixName=KDAL&briefingRadius=10&departureInstant=2023-05-03T23:00:23.0&briefingType=NGB

Response:

"plainText":"FDC 9/2934ZFW TX.. FLIGHT RESTRICTION. DALLAS, TEXAS. <br> \n   PURSUANT TO 49 USC 40103(B), THE FEDERAL AVIATION ADMINISTRATION \n(FAA) CLASSIFIES THE AIRSPACE DEFINED IN THIS NOTAM AS 'NATIONAL \nDEFENSE AIRSPACE'. ANY PERSON WHO KNOWINGLY OR WILLFULLY VIOLATES \nTHE RULES CONCERNING OPERATIONS IN THIS AIRSPACE MAY BE SUBJECT TO \nCERTAIN CRIMINAL PENALTIES UNDER 49 USC 46307.  PILOTS WHO DO NOT \nADHERE TO THE FOLLOWING PROCEDURES MAY BE INTERCEPTED, DETAINED \nAND INTERVIEWED BY LAW ENFORCEMENT/SECURITY PERSONNEL.  PURSUANT \nTO TITLE 14, SECTION 91.141 OF THE CODE OF FEDERAL REGULATIONS, \nAIRCRAFT FLIGHT OPERATIONS ARE PROHIBITED WITHIN THE FOLLOWING \nAREA(S) UNLESS OTHERWISE AUTHORIZED BY ATC \n  \nWITHIN A 1 NMR OF 325321N/0964835W OR THE CVE085004.8 UP TO AND \nINCLUDING 1500 FT AGL EFFECTIVE IMMEDIATELY UNTIL FURTHER NOTICE. 200901262213-PERM"},"altitudeRange":null,"shortestLateralDistanceOfConditionToRoute":null,"geometry":{"shape":[{"point":[{"latitude":32.889168,"longitude":-96.78993},{"latitude":32.891777,"longitude":-96.79018},{"latitude":32.894325,"longitude":-96.7909},{"latitude":32.896748,"longitude":-96.79208},{"latitude":32.898983,"longitude":-96.79371},{"latitude":32.900974,"longitude":-96.79572},{"latitude":32.902676,"longitude":-96.79809},{"latitude":32.904045,"longitude":-96.800735},{"latitude":32.90505,"longitude":-96.803604},{"latitude":32.905663,"longitude":-96.806625},{"latitude":32.90587,"longitude":-96.80972},{"latitude":32.905663,"longitude":-96.81282},{"latitude":32.90505,"longitude":-96.81584},{"latitude":32.904045,"longitude":-96.81871},{"latitude":32.902676,"longitude":-96.82136},{"latitude":32.900974,"longitude":-96.82372},{"latitude":32.898983,"longitude":-96.82574},{"latitude":32.896748,"longitude":-96.82736},{"latitude":32.894325,"longitude":-96.828545},{"latitude":32.891777,"longitude":-96.82927},{"latitude":32.889168,"longitude":-96.82951},{"latitude":32.886555,"longitude":-96.82927},{"latitude":32.884007,"longitude":-96.828545},{"latitude":32.881584,"longitude":-96.827354},{"latitude":32.879353,"longitude":-96.82574},{"latitude":32.877357,"longitude":-96.823715},{"latitude":32.875656,"longitude":-96.82136},{"latitude":32.874287,"longitude":-96.81871},{"latitude":32.873287,"longitude":-96.81584},{"latitude":32.872673,"longitude":-96.81282},{"latitude":32.872467,"longitude":-96.80972},{"latitude":32.872673,"longitude":-96.806625},{"latitude":32.873287,"longitude":-96.803604},{"latitude":32.874287,"longitude":-96.800735},{"latitude":32.875656,"longitude":-96.79809},{"latitude":32.877357,"longitude":-96.79573},{"latitude":32.879353,"longitude":-96.79371},{"latitude":32.881584,"longitude":-96.79209},{"latitude":32.884007,"longitude":-96.7909},{"latitude":32.886555,"longitude":-96.79018}]}]}...

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

The 10.27 Software Release is scheduled to be deployed on April 18, 2023. At around 2:00 am EDT, there will be a 30 - 45 minute down-time for web services during the deployment. The Software Release includes the following. Please review the lab WSDL for more detailed information regarding these updates:  

• FileUoaOperatingArea and AmendUoaOperatingArea - The notificationSettings option was removed from these web services. This option was restricted to vendors who were authorized for this service and is no longer being used. If a UOA is filed with this option, the UOA will be successfully submitted, but this field will be ignored. 

• Deprecation of Web Services - In the Leidos Web Service API (WSDL) the following web services will be marked as deprecated in the 10.27 release and are currently marked as such in the test lab. These web services will be removed in the 10.28 release. You can view the updated WSDL here:  https://ffspelabs.leidos.com/Website2/resources/doc/WebService.xml.

  • ValidateOtherInfo

  • RetrieveUasOperatingAreaSummaries

  • CreatePilotProfile

  • CreateAccountWithExistingPilotProfileUsingPilotInfo

  • CreateAccountWithExistingPilotProfileUsingEmail

The 10.26 Software Release is scheduled to be deployed on January 24, 2023. At around 2:00 am EST, there will be a 30 - 45 minute down-time for web services during the deployment. The Software Release includes the following. Please review the lab WSDL for more detailed information regarding the new features and enhancements: 

• File Flight Plan and Amend Flight Plan - An RNAV SID or STAR can be included only for an ICAO flight plan. If it is included for a domestic flight plan, the response will contain an error indicating that this information can be included only for an ICAO flight plan:

  • "STAR <STAR identifier> cannot be used with a domestic flight plan."

  • "SID <SID identifier> cannot be used with a domestic flight plan." 

• Alaska Flight Planning - To align with Anchorage ARTCC flight planning rules, for IFR and YFR flights, the following web services have been changed to allow only airports, heliports, FRDs, and lat/long departures and destinations for Alaska:

  • FileFlightPlan

  • AmendFlightPlan

  • RouteBrief

  • AreaBrief

  • Navlog

If the departure, destination, or alternate destinations are invalid, the request will fail, and the failure response will contain "Invalid <LOC> for AK IFR: Must be Airport, Heliport, Fix-Radial-Distance (FRD), or Lat/Long” where <LOC> is Departure or Destination or Alternate 1 or Alternate 2. 

• RouteSearch - For ATC recent IFR routes, the maximum age of flights to search is increased from 24 hours to 30 days. 

• Service Provider Authorization – At the Leidos Flight Service website, the text on the Service Provider Authorization page has been updated to the following:

  • By authorizing your participating service provider here, their actions on your behalf will be connected to your account, so that: 

    • You can access on this website flight plans filed on your behalf. This includes viewing, amending, activating, cancelling, and closing those flight plans; it also includes receiving briefings, briefing updates, and alerts for those flight plans.

    • Flight plans filed on your behalf can use the advanced services for which you have registered.

    • When you call a specialist, your profile can be used to provide faster service.

    • Your service provider can make limited updates to your profile for you (aircraft information, service registrations, account sharing, portable position device information).

    • If multiple service providers are authorized, they can each view the actions provided on your behalf by any of the other authorized service providers. 

For more information, please see the Service Provider Authorization page on the Web Services Support wiki. 

• Deprecation of Web Services - In the Leidos Web Service API (WSDL) the following web services will be marked as deprecated in the 10.27 release and are currently marked as such in the test lab. These web services will be removed in the 10.28 release. You can view the updated WSDL here:  https://ffspelabs.leidos.com/Website2/resources/doc/WebService.xml.

  • ValidateOtherInfo

  • RetrieveUasOperatingAreaSummaries

  • CreatePilotProfile

  • CreateAccountWithExistingPilotProfileUsingPilotInfo

  • CreateAccountWithExistingPilotProfileUsingEmail 

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

The following update to the 10.25 release will be deployed in operations on Monday evening, 11/14/2022, around 10 pm EDT. This update is available in the test lab.

FlightInfo - The webUserName input parameter will now require the vendor that is submitting the request to be authorized by the pilot via the Leidos Flight Service website on the Service Provider Authorization page. In addition, the following input parameters will no longer be available:

• aircraftIdentifier 

• phoneNumber

For more information on credentialed web services, please see: Service Provider Authorization

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

The 10.25 Software Release is scheduled to be deployed September 20, 2022. At around 2:00 am EDT, there will be a 30 - 45 minute down-time for web services during the deployment. The Software Release includes the following. Please review the lab WSDL for more detailed information regarding the new features and enhancements:

Route Briefing and Area Briefing - These endpoints will now return the radios frequencies for the weather stations at the departure and destination airports for NGBV2 briefings for REST and SOAP requests. The radio frequencies will be listed in the Weather Stations subsection of the Overview section of the briefing. Frequencies will be included for associated AWOS or ASOS frequencies for the departure, destination or alternate destinations.

• If the destination point is not an airport with an associated AWOS or ASOS frequency, and there exists a landing facility, open or closed, with an associated AWOS or ASOS within 10NM of the destination point, then the frequency of the closest airport with an ASOS or AWOS will be given.

• If no ASOS or AWOS is within 10 miles of DEP, DEST, and Alternate DESTs, the Weather Stations sub-section will say "None within 10 nm." 

Route Briefing and Area Briefing - In accordance with FAA direction, the description of NOTAMS have been changed from “NOTICE to AIRMEN” to “Notice to Air Missions." 

NavLog - Specifying the optional parameter "includeFrequencies" will now return UNICOM and CTAF communication frequencies available for the departure and destination airports in addition to the AWOS/ASOS and FSS frequencies associated with the flight plan.

Note - At the Leidos Flight Service (LFS) website, for route and area briefings, the option to select the legacy NGB "Old" briefing was removed. The LFS website now offers only the new NGBV2 briefing in Web, PDF, or E-mail format. However, for web services, 'SIMPLE', 'NGB', 'EMAIL', and 'NGBV2' still remain valid options for the briefing type.

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

The 10.24 Software Release deployment date has been updated, and is now scheduled to be deployed on June 7, 2022. At around 4:00 am EDT, there will be a 30 - 45 minute down-time for web services during the deployment. The Software Release includes the following. Please review the lab WSDL for more detailed information regarding the new features and enhancements: 

RetrieveFlightPlanRequest

• The versionRequested field will no longer determine whether or not to return the following fields, all of these fields will be returned if appropriate:

  • beaconCode (if one has been assigned to the flight)

  • artccState (if one exists for the flight)

  • artccInfo (if one exists for the flight)

  • typeOfFix

  • expectedRoute (when an expected route change is detected)

  • peopleOnBoardIsTBN (when persons on board is TBN)

  • peopleOnBoardExtended (when persons on board is not TBN)

  • aircraftColorExtended

  • suppRemarksExtended

  • pilotInCommandExtended

• The peopleOnBoard, aircraftColor, suppRemarks, and pilotInCommand fields are no longer returned in the RetrieveFlightPlan response.

  • For REST, these fields will be set to null in the response.

  • For SOAP, the response will not contain these fields.

• For a FileFlightPlanRequest or AmendFlightPlanRequest, it is recommended that the ICAO extended fields are used: peopleOnBoardExtended, aircraftColorExtended, suppRemarksExtended, and pilotInCommandExtended. If the non-extended version of these fields are used, the RetrieveFlightPlan response will return the values in the ICAO extended fields.  

RetrievePilotProfile:

• The versionRequested field will no longer determine whether or not to return the ICAO 2016 fields. All of the ICAO 2016 fields will be returned. If the versionRequested field is included, it will not result in an error.

• For the AmendPilotProfileRequest, it is recommended that the ICAO aircraftColorExtended field is used. If the aircraftColor field is used, the response will return the value in the aircraftColorExtended field. 

  • For REST, the aircraftColor field will be set to null in the response.

  • For SOAP, the response will not contain the aircraftColor field.

SubmitPirep - This web service will be modified to accept only a valid aircraft type between 2 - 4 alphanumeric characters. The lookupAircraftType web service can be used to search for a valid aircraft type before submitting a PIREP.

GenerateGraphicImage - this previously deprecated endpoint has now been removed and can no longer be accessed.

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

The 10.23 Software Release is scheduled to be deployed on March 1, 2022. At 4:00 am EDT, there will be a 30 - 45 minute down-time for web services during the deployment. The Software Release includes the following. Please review the lab WSDL for more detailed information regarding the new features and enhancements:

Enhancements:

• Format Severe Weather Text for METARs in Briefings – severe weather text for METARS is colored red and bolded in NGBV2 Route and Area briefings. This is the same as the formatting for TAF. This applies to:

  • Briefing formats: Email and PDF

  • Standard & Abbreviated briefings

  • METAR summary text and individual METARs

  • Current METARs only (does not apply to historical METARs)

  • Plaintext METARs in briefings:

    • Thunderstorm

    • Funnel Cloud / Funnelcloud

    • Tornado

    • Volcano / Volcanic Ash

  • Encoded METARs in briefings:

    • TS

    • FC

    • +FC

    • VA

• Route Briefing and Area Briefing - these endpoints now provide the capability to filter FDC NOTAMs from the briefing. This filtering only apply to the NGBV2 Briefing Type.  These filters are part of the NGBV2 Tailoring Options:

  • EXCLUDE_FDC_NOTAM_AIRSPACE: exclude FDC AIRSPACE NOTAMs

  • EXCLUDE_FDC_NOTAM_CHART: exclude FDC CHART NOTAMs

  • EXCLUDE_FDC_NOTAM_DATA: exclude FDC DATA NOTAMs

  • EXCLUDE_FDC_NOTAM_DVA: exclude FDC DVA NOTAMs

  • EXCLUDE_FDC_NOTAM_IAP: exclude FDC IAP NOTAMs

  • EXCLUDE_FDC_NOTAM_ODP: exclude FDC ODP NOTAMs

  • EXCLUDE_FDC_NOTAM_ROUTE: exclude FDC ROUTE NOTAMs

  • EXCLUDE_FDC_NOTAM_SECURITY: exclude FDC SECURITY NOTAMs

  • EXCLUDE_FDC_NOTAM_SID: exclude FDC SID NOTAMs

  • EXCLUDE_FDC_NOTAM_SPECIAL: exclude FDC SPECIAL NOTAMs

  • EXCLUDE_FDC_NOTAM_STAR: exclude FDC STAR NOTAMs

  • EXCLUDE_FDC_NOTAM_VFP: exclude FDC VFP NOTAM

• NavLog - this endpoint now supports an optional parameter to request frequencies associated with the departure, destination, and along the route of flight.  Specifying the new optional parameter "includeFrequencies" will return the AWOS/ASOS and Flight Service Station (FSS) frequencies associated with the flight plan in the NavLog response:

  •  Surface Weather Observation Station (AWOS/ASOS) frequencies. When a surface weather observation station (AWOS/ASOS) is located at or within 10nm of the departure airport the associated frequency along with its identifier is returned (i.e. KCUB 118.675). When a surface weather observation station (AWOS/ASOS) is located at or within 10nm of the destination airport the associated frequency along with its identifier is returned (i.e. KCUB 118.675).

  •  Flight Service Station (FSS) frequencies. When there is one or more FSS frequencies available within 50nm of the departure or destination location the nearest FSS frequency will be returned. When there are FSS frequencies available within 50nm of either side of the route of flight they will be returned in route order.

• EmailBriefing - this previously deprecated endpoint has now been removed and can no longer be accessed.

The 10.22 Software Release is scheduled to be deployed on October 5, 2021 at around 3:25 am EDT. There will be a 30 - 45 minute down-time for web services during the deployment. The Software Release includes the following. Please review the lab WSDL for more detailed information regarding the new features and enhancements:

Enhancements:

• FileFlightPlan - If an attempt is made to file an ICAO flight plan with Flight Rules of IFR or YFR, and it matches a previously filed flight plan, the web service response will return False with an error message:

  • "We detected a duplicate Flight Plan in our system filed on <Month/Date of filing> at <UTC time>Z. Duplicate flight plans will be rejected by ATC. This flight plan must be modified in order to file."

• Military Training Routes (MTRs) - IFR Routes that are currently accepted by the ARTCC will be supported in flight planning and will be used to determine briefing content. An appropriate error message will be returned for an invalid MTR, entry or exit fix.

  • This includes the following web services:

    • FileFlightPlan

    • AmendFlightPlan

    • NavLog

  • VFR Routes, Slow Routes, and Aerial Refueling Routes will be supported in a future release.

• New NavLog option to suppress fixes - The NavLog web service now includes an optional parameter to suppress NAVAIDS/fixes along an airway:

  • When the includeOnlyAirwayEntryExitFixes option is set to true, the fixes on the airways are removed except for fixes at the entry and exit of an airway.

    • Airways include airways, radials, MTRs, SIDs, and STARs.

    • The NavLog response will continue to include all user entered fixes in the route.

    • The parentAirwayName field associated with a navlog fix in the response identifies the airway/route to the fix.

The 10.21 Software Release is scheduled to be deployed on June 28, 2021 at 0300Z. There will be a 15 minute down-time for web services during the deployment. The Software Release includes the following. Please review the lab WSDL for more detailed information regarding the new features and enhancements: 

Enhancements:

• NavLog Enhancements - NavLog Request provides an optional parameter (includeTopOfClimbDescent) to include the Top of Climb and Top of Descent positions in the resulting navigation log. 

• Estimated Time of Arrival (ETA) - To support extended flight plans, the following Web Services have been updated to support an Estimated Time of Arrival (ETA) field (estimatedTimeOfArrival):

  • AmendFlightPlan

  • FileFlightPlan

  • RetrieveAlertByRoute

  • RouteBriefing

  • RetrieveFlightPlan

  • RetrieveFlightPlanSummaries. 

• NGBV2 Briefing Updates - NGBV2 briefings have been streamlined to filter out Winds Aloft and Convective Outlook data that is not pertinent to the planned time frame of the flight. This applies to the following briefing types:

  • Route and Area Briefings

  • This does not apply to Outlook briefings. 

• Briefings now include Density Altitude Warnings:

  • NGBV2 briefings now have a "Check Density Altitude Warning" in the Flight Plan Summary

  • Both NGBV2 and NGB briefings now have Density Altitude added to the METAR Summary Section of Current Weather

  • This applies to route and area briefings.

The 10.20 Software Release is scheduled to be deployed on March 11, 2021 at 0300Z.  There will be a 15 minute down-time for web services during the deployment. The Software Release includes the following (please review the lab WSDL for further information regarding the new features and enhancements):

Enhancements:

• Error Messages - The error messages related to route validation associated with briefing, filing, amending, and navigation log requests have been enhanced to be more user friendly.