Tuesday, September 8, 2015

Confirmed Incidents Added to Flight Status Payload

FlightStats has enhanced its Flight Status payload to include Confirmed Incidents.  A Confirmed Incident is a major disruption to an operating flight that has been reported by two major news outlets.  When this type of incident occurs, FlightStats will add a 'confirmedIncident' block to the payload.  See the example below:

"flightStatus": {
    "confirmedIncident": {
        "date": "2015-01-01T00:00:00+00:00",
        "message": "News agencies are reporting an incident with 
                    2015-08-16 TGN 267 DJJ --> OKL.
                    The flight went missing in a remote area.
                    Please see CNN or BBC for more information."

All of our Flight Status APIs will include this additional information when 'includeNewFields' is added to the extended options, as in the example below:

These types of incidents are, thankfully, extremely rare.  However, when they do happen, we want to ensure that our API customers are informed as quickly as we can that some event has occurred.  

Thursday, July 9, 2015

Operating and Primary Carrier

On July 9th, 2015, we added some optional carrier fields to our FlightStatus Response element within certain Flex APIs. Details can be found in our developer center at:

These fields explicitly identify the Primary and Operating carriers for all flights. Every flight has a designated Primary carrier. In most cases the Primary carrier also operates the flight. However, in certain instances they establish a business relationship with another carrier to operate the flight. Often this is described as "Operated by [ExpressJet] on behalf of [Delta]." This type of business relationship is commonly called a wet lease.

Please note that we are not making any changes to our existing fields. These are additions only. Also, since these are new fields, they are only provided if you add the includeNewFields parameter in your API request:

The examples below show representations both with inline references and without.

=== If not using useInlinedReferences

<operatingCarrierFsCode>AA</carrierFsCode>0..1NEW (https://developer.flightstats.com/api-docs/version_policy) The FlightStats unique code for the operating carrier to use as a reference for finding the entry in the appendix (unless the extended option to include inlined references is used).

<primaryCarrierFsCode>AA</carrierFsCode>0..1NEW (https://developer.flightstats.com/api-docs/version_policy) The FlightStats unique code for the primary carrier to use as a reference for finding the entry in the appendix (unless the extended option to include inlined references is used).

=== Sample JSON snippet response for useInlinedReferences


fs: "EV",
iata: "EV",
icao: "ASQ",
name: "ExpressJet",
active: true,
category: "I"


fs: "DL",
iata: "DL",
icao: "DAL",
name: "Delta Air Lines",
phoneNumber: "1-800-221-1212",
active: true,
category: "I"

Friday, May 15, 2015

FlightStats APIs - Arabic Language Support

We are pleased to inform our developer community that FlightStats has added Arabic language support to the APIs:

Not only has Arabic been added as an additional language but all Flex API web services are available with multi-language response options. Languages currently available are: English, Simplified Chinese, Japanese, French, German, Portuguese and Spanish.

Read more:

How to use language localization in the APIs:

Wednesday, December 10, 2014

Developer Survey

We want your feedback!

Last week, FlightStats sent a survey to Flex API customers to gather feedback from our Developer Community as a way to inform our 2015 product planning.  

If you are a customer and did not get a survey and would like to provide feedback, please contact us at sales@flightstats.com and we will send you the survey details. 

Feedback like this is very important and helpful.  We really appreciate hearing from as many of you as possible. 

Tuesday, November 18, 2014

FlightStats releases Positions v2

FlightStats is pleased to announce an upgrade to our Flight Track API.  On December 10, 2014, FlightStats will release Positions v2 which provides a richer set of positional data to be used within flight tracker applications.  This upgraded API will include several new fields as well as derived positions when observed positions are not available.  

Additional Fields:
  • course: The direction of travel in degrees relative to geographic north, clockwise. The range for this data field is -179 to 180.
  • vrateMps: The velocity of ascent or descent (if negative) in meters per second.
  • phase: Description used to indicate the most likely activity of the plane at a given time. Phases include: Ground, Take-Off, Departure, Climb, Leveled, Cruise, Descend, Approach, Landing. Not all positions will include a phase.
  • lastObserved: The timestamp of when FlightStats last received an observed position. In cases where no observed positions are provided for a flight, this field will not be present. The 'date' field in each of the positions blocks identifies the time when the plane is believed to be at that specific location -- either observed or calculated. FlightStats continues to calculate the position even when no additional observed data is provided. In such cases, there will be a difference between date and lastObserved, a gap that increases as the flight continues.
  • stationID: The station identifier used by the FAA for ASDI data. Examples: KZLA, KZAB, KZDV.

Special Note regarding stationID:
The ASDI stream consists of a collection of observations from different regional and national tracking systems. Each of these has a separate stationId. A single aircraft may be observed by multiple stations at once, each of which may report a slightly different position due to the inherent inaccuracy of radar. Because of this, trackers showing ASDI streams should either show all signals separately, maintain an affinity between a callsign and single stationId as long as possible, or integrate the different signals.
(Note: ADS-B data payloads will be unchanged in the new system. ASDI data payloads will include one additional field - stationID.)

Request Parameters:
Applications will not need to make any changes to their current request in order to receive derived positions -- derived will be the sourceType by default. If you want to continue receiving positional data as it currently is provided, you will need to add a single argument.  (sourceType=raw)

If you would like to take advantage of the new fields, your application will need to include that value in the 'extendedOptions' n/v pair, as shown below. 

Here is an example request that will return positional data as it is currently in production, without the new fields. 


This example will return the new derived data.  sourceType is not needed, because it defaults to sourceType=derived.  In this case, new fields will be included. 


This example will return the new derived data and include new fields (extendedOptions=includeNewFields)


Please see the Developer Center for additional documentation.

(Note:  From now until release date, you will need to include the n/v pair "sourceType=derived" in order to test and review the new data payload.)

Monday, February 10, 2014

Gesture-based Flight Board with Voice and Face Recognition by Interknowlogy

There have been many great advances in digital signage technology finding their way into airports, hotel lobbies, convention centers and other travel hubs.  Here's a new take on a flight board from the folks at Interknowlogy.

Their NUI (natural user interface) Flights system lets users scroll through flights using hand gestures to find their flight.  It also features voice recognition allowing users to speak their airline and flight number.  NUI Flights then finds that flight and shows the detailed status.  A third method uses facial recognition to support a use case in which a user opts in to let the system recognize one's face and lookup the relevant flight information for display without any other interaction.

The app is powered by FlightStats FIDS API, of course, and will be featured at the upcoming Digital Signage Expo in Las Vegas Sands Hotel Expo Center on February 12-13, 2014.

Here's a link to a couple of video demos of NUI Flights available for download on HighTail.

Monday, September 23, 2013

Leading Global Airline Uses FlightStats Japanese/English API in Mobile/Web Apps

ANA Mobile Application Image
ANA (All Nippon Airways) is a leading Japanese provider of air transportation services and is one of the world’s largest airlines, serving 128 domestic Japanese routes with 912 daily flights and 34 international and regional routes to 10 countries in Asia, Europe and North America. ANA is consistently at the top in on-time performance and has been recognized as a winner or a finalist by FlightStats On-time Performance Awards in various categories since the program’s inception in 2009.


As a leading airline in Japan, ANA is continually striving to find innovative ways to provide the best customer service experience for its customers. In this case, ANA sought a powerful solution for making flight status information by route, and by flight, available to their customers via their mobile application ANA GLOBAL, as well as via their website. With ANA’s commitment to customer experience, it was important that the user experience be seamless to customers, and that the flight information available also include codeshare information. Codeshare information is typically quite difficult to integrate into a solution for independent entities because it requires the gathering, implementation, and management of multiple data sources.
“FlightStats data has made it possible to provide our customers with the latest flight status information, for both operating and marketing carrier customers. And since the data has been translated into Japanese, it was quick and easy to implement without having to do the translations ourselves. This data has received high marks from our users.” - Hiroyuki Yoshida, All Nippon Airways


ANA is using FlightStats Flex APIs to get the real-time global flight status information by route and by flight. With the option to have API responses delivered in multiple languages, ANA was able to quickly and easily provide the information in both Japanese and English for customers to choose. The breadth of FlightStats global coverage, including codeshare data, gives ANA the power easily give customers the ability to quickly find data about their flight. ANA is able to offer an enhanced travel experience to their customer but does not have to manage multiple data sources. Using FlightStats’ data shortened ANA’s development time because FlightStats has packaged its flight information and made it available via RESTful APIs that are flexible, easy-to-use, and easy-to-implement in mobile and web applications. For more information regarding this and other FlightStats data solutions please contact a FlightStats representative.