This document explains how you may customize FS Flight Tracker for your virtual airline.  FS Flight Tracker features both text file pilot reporting and real time web pilot reporting.  You may also add your airline banner as a custom FS Flight Tracker splash screen.

va Folder

The va folder is where the files that customize FS Flight Tracker are placed.  This folder should be placed in the FS Flight Tracker folder.  The following files may be placed in this folder:

• splash - A gif, jpg or bmp image file to display as the FS Flight Tracker splash screen.  The most common use for this file is to display your airline banner.  The screen will resize to accommodate any image file size.

• server.cfg - This file contains the address of the virtual airline web server, the post page or script for filing pilot reports and an optional post page or script to accept ACARS reports.

• pirep.cfg - This file contains a listing of all the FS Flight Tracker fields in the Pilot Report.  The purpose of this file is allow you to specify the field name that should be used for each field when filing a report on the web server.

• vafields.cfg - This file allows you to specify up to 10 additional custom fields to be used in the pilot report.  

Once the files for the VA folder are created for your airline, you may distribute it to your pilots.  Simply placing the va folder in the FS Flight Tracker folder will customize FS Flight Tracker for use with your airline!  FS Flight Tracker Version 5.1.2 is required.

A sample va folder and files is included with this SDK.

Custom Splash Screen

The FS Flight Tracker splash screen may be customized to display a banner for your airline.  Simply rename your banner image file to 'splash' and place it in the va folder.  The image may be a gif, jpg or bmp file of any size.  The screen will resize to accommodate your banner.

server.cfg

The server configuration file is used to specify the web address of your airline as well as post pages or scripts used to receive pilot reports and ACARS reports.  The use of ACARS reports is optional.  The layout of the file should be as follows:

Line 1: Web Server Address [www.va.com]

Line 2: Pilot Report Post Page or Script [/dir/postpage.asp] *cgi-bin, ASP , PHP supported

Line 3: ACARS Report Post Page or Script [/dir/postpage.asp] *cgi-bin, ASP , PHP supported

ACARS Reports are sent using the following fields:

• acars0 - acars3 = ACARS Header Information
• acars4 = Message Detail
• acars5 = Pilot ID

pirep.cfg

By default, field values sent to your web server are URL encoded.  You may turn off URL encoding by adding an additional file to the va folder.  Create an empty file in the va folder named 'noencode'.

The pirep configuration file is used to specify the field names that should be used for each field when reporting to your post page or script.  If a field is not used by your airline your server will simply ignore it.  The layout of the file is as follows:

Field Name^Name to use when posting

Aircraft Type^equipment

vafields.cfg

 The vafields configuration file allows you to add up to ten (10) custom fields for use in the pilot report.  The fields will display on a third page added to the ACARS.  The layout of the file is as follows:

Field Name^Optional list of values | delimited^Name to use when posting

Aircraft Type^B737|A319|A320|A321^equipment

How it Works

1. Add va folder to FS Flight Tracker folder
2. Check 'File Pilot Report' check box
3. Upon completion of flight - click Log Flight link
   • Pilot report text file will be saved to reports folder
   • Pilot report will be sent to web server
   • Server Response will display in message box

An additional option will appear on the File menu - Send PIREP.  This option allows you to resend a pilot report at any time.  This is done by selecting a pilot report text file from the reports folder and then resubmitting it to the server.

Important:

The response received after submitting a pilot report will be displayed EXACTLY as received.