Technical requirement
The flight movement module should operate on PC workstations with Microsoft Windows
and allowing the use of AERO2K software on the world-wide-web.
Analysis option
The end-user of the AERO2K software should be able to run scenarios. For this reason,
any global or specific query should be made possible:
On a geographical scale ranging from a city-pair destination to all arrival flights in a given
area.
On a world grid cell of 1° x 1° x 0.5 km (latitude, longitude, altitude).
In terms of flight analysis focusing on a single aircraft or all aircrafts from a given airline.
For any period within the data collection period.
Taking into account these specifications, an AERO2K prototype flight movement tool was
developed using a sample data set. The sample data set used consisted of European and
American data respectively named AMOC and ETMS for the 5th of October 2000. The
goal was to develop a procedure that would import AMOC and ETMS flight data in a
standardized Access database. This procedure developed, it was then possible to import
the delivered format, to extract the portion of data needed, to perform the required
conversion or process and to import the data in the desired format. Problems encountered
when importing the data from various sources were due to differences in the type of fields,
their format and the composition of the files. These difficulties are reviewed in Table 1.
Their listing was the starting point for elaborating AERO2K flight movement tool. Two
groups of differences were identified:
Easy to solve straightforward differences.
Complexe differences requiring other applications.
In the first category enter problems due to the selection of compulsory fields, the
harmonisation of format and the conversion of data from minutes to degrees for example.
In the second category were classified problems linked to time period differences and the
use of different airport/airline codification systems. All these points are reviewed in the
paragraphs:
1.1 The structure of the traffic and flight tables
1.2 Date-leg filtering
1.3 Relationships between AERO2K flight movement tool and other tables.
Table 1: File differences encountered between AMOC and ETMS.
AMOC ETMS
Traffic.txt Flight.txt Flight.txt Flight_chord.txt
Number of fields 12 18 38 15
listed.
Time period 4-5-6/10/2000 4-5-6/10/2000 3-4-5-6/10/2000 3-4-5-6/10/2000
Time and date format hhmmss (Greenwich mean time ) GMT hh:mm:ss GMT YYMMDD 00:00:00 GMT YYMMDDHH24 MI GMT
Callsign callsign 6 digit number+callsign
Airline 2-letter code 3-letter code
Departure/arrival airport 4-letter code 3-letter code
Aircraft ICAO code ICAO and FAA
codes
Latitude/longitude In decimal degrees In minutes
Ground speed In knots (kts) In meter/sec (m/s)
1.1. The structure of the traffic and flight tables
For both AMOC and ETMS, flight data were delivered into two text files, one file listing general information on the airport and aircraft, the other on the flight route, it was decided to keep this structure. However, the two text files were imported into two tables named Traffic and Flight within a source. Each importation procedures are detailed in Phase 1 Paragraphs 2 and 3 and in the Appendix. The common output structure is described in Table 2. 中国航空网 www.aero.cn 航空翻译 www.aviation.cn 本文链接地址：AERO2K Flight Movement Inventory Project Report(9)
