Figure 20: Representation of the flight level and ground speed for all departing flights traveled on a B733 between 1000 nm and over.
Col # Column Name Data Type Data Description
1 AIRCRAFT VARCHAR2(15) Aircraft type
2 DISTANCE NUMBER Distance at the position considered in nm
3 FLIGHT_LEVEL NUMBER Flight level at the position considered in hundred of feet
4 SPEED NUMBER Speed at the position considered in knots
5 CNT NUMBER Number of records used to produce the profile
Figure 24: Representation of the flight level and ground speed for all arriving flights traveled on a B733.
Output of the data
ETMS data used for creating the graphs were extracted from the Oracle database and exported to Excel where the profiles were drawn. Once the trends were drawn for all three types of profiles and each common aircraft type, the data were summarized into a single table and exported as text files. The text files were imported into Oracle where the second phase of the flight legs creation occurs.
Creation of city-pair flight routes
The exploitation of the profile data was possible if the position of the waypoints was known. The National Imagery and Mapping Agency (NIMA)3 of the United States Department of Defense (DOD) produces a Digital Aeronautical Flight Information File (DAFIF) showing a digital map locating world waypoints and route network. World waypoints coordinates were extracted from this file. A list of city-pair in the world was made based on Back Aviation schedule data. Each city-pair was associated to a waypoint located in a 40 nm distance criterion. City-pairs and waypoints positions were then loaded
This product was developed using DAFIF., a product of the National Imagery and Mapping Agency. This product has not been endorsed or otherwise approved by the National Imagery and Mapping Agency, or the United States Department of Defense (10
U.S.C. 425).3
into a tool named CARAT, a Computer Aided Route Allocation Tool developed by EEC. The tool delivered a list of shortest paths found between city-pairs. The capacity component was not invoked thus resulting in a route from origin to destination based only on a list of waypoints (Table 38 and Table 39).
This way, a route could be allocated to a city-pair by linking the waypoints along the route with the Great Circle.
Table 38: Table CITY_PAIR.
Col # Column Name Data Type Data Description
1 CITY_PAIR_ID NUMBER(15) Object identifier for the city pair
2 DEP_AIRPORT1 VARCHAR2(4) Airport of departure (ICAO code)
3 ARR_AIRPORT2 VARCHAR2(4) Airport of arrival (ICAO code)
4 HAS_ROUTE NUMBER Shows if a waypoint route exists (0 or 1)
Table 39: Table CITY_PAIR_WP.
Col # Column Name Data Type Data Description
1 CITY_PAIR_ID NUMBER Object identifier for the city pair
2 WP_NAME VARCHAR2(5) Name of the waypoint that constitutes the route
3 LATITUDE NUMBER(17,7) Latitude of the waypoint
4 LONGITUDE NUMBER(17,7) Longitude of the waypoint
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：AERO2K Flight Movement Inventory Project Report(32)
