The red coloured values are the only ones to be imported:
. 1 – simulation entry time – DepartureTime This field represents the flight’s departure time. It will be converted from its format <HHnnss> (HH covers 3 days, so its value can be from 00 to 71), to standard <yyyy-mm-dd hh:nn:ss> date-time format. The conversion is explained further.
.
2 – flight call sign – CallSign
This field remains unchanged.
.
3 – departure airport – DepartureAirport
This field remains unchanged.
.
5 – arrival airport – ArrivalAirport
This field remains unchanged.
.
7 – aircraft type – AircraftType
This field remains unchanged.
Besides these 5 fields, another 4 fields are inserted in the traffic table:
.
Traffic unique identifier – TrafficId
This field is controlled by Access. It is an auto number.
.
Sources application (“AMOC”) – Sources
This field stores the source application name.
.
Fluid code – Fluid This field is calculated from all other fields using a predefined formula: Fluid = CCCCCCCAAAAYYMMDDHHNN, where CCCCCCC = call sign, AAAA = departure airport and YYMMDDHHNN is the departure time in <yymmddhhnn> format. If the call sign length for example is smaller than 7, then the rest of the CCCCCCC value is filled with “-”. The same procedure is used for the departure airport.
. The last possible arrival time – MaxStopTime
This field determines the possible arrival time. If for one day, more than one flight has the same call sign, then all flights are sorted ascending by departure time into a list and for each flight the MaxStopTime will be set as <DepatureTime minus 1 second> of the next flight. If the flight is the last one in the sorted list, then its MaxStopTime is set to <3000-01-01>.
2.2. AMOC flight legs text file (ex: Flight_20001005.txt)
If the text file name is Flight_20001005 then this file contains all flight legs that belong to the flight heads, which are saved in the Traffic_20001005.txt file. The file’s structure is given in Table 49.
Table 49: AMOC flight text file.
Nr Field Name Description
1 FLIGHTPLANKEY The aircraft type name
2 TRAFFIC FlightCallSign The flight's callsign
3 Event time, format of HH:MM:SS The departure time
4 ATTITUDE OF AIRCRAFT Either Climb, Cruise, Descent or Attitude Unknown
5 EVENT OF THE FLIGHT PLAN POINT
6 EVENT INFORMATION1
7 EVENT INFORMATION2
8 EVENT INFORMATION3
9 GROUND SPEED (nm) The ground speed
10 CLIMB/DESCENT RATE (ft/min)
11 LATITUDE POSITION The latitude position
12 LONGITUDE POSITION The longitude position
13 AFL Actual Flight Level in hundreds of feet
14 RLF Requested Flight Level in hundreds of feet
15 CFL Cleared Flight Level in hundreds of feet
16 Flight PHASE Flight Phase at this point
17 Flight Target Level In hundreds of feet
18 (ignore)
The content of the file looks like this:
1 2 3 4 5 6 7 8 9 10 11 12
KEY GRL781 34:54:00 Cruise FALSE FALSE FALSE FALSE 475.00 0.00 68.000000 -10.000000
KEY GRL781 35:23:00 Cruise FALSE FALSE FALSE FALSE 475.00 0.00 69.000000 -20.000000
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：AERO2K Flight Movement Inventory Project Report(45)
