| I. Introductionhis paper is motivated by the need for predicting wheels-off time at airports where advanced automation systems, such as the Surface Decision Support System (SDSS), that depend on surveillance information derived from Airport Surface Detection Equipment Model-X (ASDE-X) type systems will not be available.At airports with SDSS type systems, aircraft surface movement will be scheduled, which will reduce runway entry time and wheelsoff time uncertainty.Additionally, it will be possible to generate better estimates by using surveillance information.For example, the taxiway entry time of an aircraft waiting at the spot can be predicted more accurately by predicting the trajectories of aircraft in the movement areas starting from the current locations from surveillance data.At less equipped airports, wheels-off time will have to be estimated under the current day conditions with uncertainties associated with aircraft movement in the ramp-area and in the movement-area.Wheels-off time predictions are needed for coordinating departure release times with downstream facilities to meet flow management restrictions imposed by them.These restrictions are imposed for ensuring adequate separation between aircraft, creating orderly flows in terminal areas, and protecting sectors and airports from being overwhelmed by demand.Two of the commonly used restrictions that could benefit from wheels-off time estimation are Call For Release (CFR) and Expect Departure Clearance Time (EDCT).Accuracy requirement for CFR is actual wheels-off time within twominutes early to one-minute late window with respect to the estimated wheels-off time.The requirement for EDCT is plus-minus five minutes.In the first part of the paper, the initial set of 77 major U. S. airports in the Aviation System Performance Metrics (ASPM) database is reduced to the set of 29 airports after eliminating ASDE-X, small-hub and non-hub airports.This reduced set contains 27 medium-hub airports and two large-hub airports.Nine of these airports are being considered for surface surveillance systems.Currently, single radar-based Low Cost Ground Surveillance (LCGS) is | |
| II. Selection of Non-ASDE-X AirportsIn this section, the sources of taxi-out delay, taxi-out time, number of commercial operations, traffic flow management initiative caused delay counts, passenger enplanement counts, type of hub airport and type of surface surveillance equipment at the airport used for determining the non-ASDE-X airports in this study are described.Most of the data were derived from the Federal Aviation Administration's (FAA) Aviation System Performance Metrics (ASPM) and Operations Network (OPSNET) databases containing historical traffic counts and delay statistics.Data were also derived from the Terminal Area Forecast (TAF) Summary for fiscal years 2011-2040 report.The 77 airports included in the ASPM and OPSNET databases are listed in Table A-1 in the Appendix.These airports are referred to by their airport code in the rest of the document.The first report obtained from the ASPM database is the "Analysis By Airport Report (compared to flight plan)" for calendar year 2011.This report includes average taxi-out time and average taxi-out delay for each of the 77 major U. S. airports.Taxi-out time is the difference between the actual wheels-off time and the actual gate-out time.Taxi-out delay is difference between the taxi-out time and the unimpeded taxi-out time.Taxi-out times and delays are in minutes.Only data from itinerant flights to or from the ASPM 77 airports or operated by one of the ASPM 29 carriers are included.Itinerant flights are those that land at an airport, arriving from outside the airport area, or depart an airport and leave the airport area.Data on flights by ASPM carriers to international and domestic non-ASPM airports are also kept in the ASPM database.General aviation and military flights are excluded.Table A-2 in the Appendix lists the average taxi-out delay and the taxi-out delay ratio derived from this report.The average taxiout delay ratio is defined as the ratio of average taxi-out delay to average taxi-out time.The second report, "OPSNET: Airport Operations: Standard Report" for calendar year 2011 is obtained from the OPSNET database.This same report can also be obtained from the FAA's Air Traffic Activity System (ATADS) database.This report contains air-carrier, air-taxi, general aviation and military itinerant operations, and civil and military local operations.Local operations are performed by aircraft that remain in the local traffic pattern, execute simulated instrument approaches or low passes at the airport, and fly to or from the airport and a designated practice area within a 20-mile radius of the tower.Airport operations include all arrivals and departures at the airport; overflights are not included.OPSNET defines air-carrier as aircraft with a seating capacity of more than 60 seats or a maximum payload capacity of more than 18,000 pounds carrying passengers or cargo for hire or compensation and air-taxi as aircraft with a seating capacity of 60 or less or a maximum payload capacity of 18,000 pounds carrying passengers or cargo for hire or compensation.Air-carrier includes U. S. and foreign flagged carriers.Table A-2 in the Appendix lists the sum of itinerant air-carrier and air-taxi operations (commercial operations as defined by TAF report) for each of the 77 major U. S. airports based on the 2011 report.The third report, "OPSNET: Delays: Delay Types Report" was obtained from OPSNET database to get TMIfrom delay counts for calendar year 2011.These counts are also listed in Table A-2 in the Appendix.OPSNET defines TMI-from delays as traffic management initiative delays from a national or local traffic management initiative as experienced by aircraft departing from the selected facilities.These initiatives include departure spacing (DSP), enroute spacing (ESP), arrival spacing (ASP), miles-in-trail (MIT), minutes-in-trail (MINIT), Expect Departure Clearance Time (EDCT), Ground Stop (GS), and Severe Weather Avoidance Plan (SWAP).It should be understood that these delays are charged to facilities asking for the delays and not to the ones providing the delays.For example, 11,132 aircraft were delayed at Atlanta (see ATL TMI-from delay counts in Table A-2 in the Appendix) to comply with traffic management initiatives of other facilities.From this study's perspective, TMIfrom delay counts (number of aircraft experiencing TMI-from delays) indicates instances when improved wheels-off time estimate at the departure airport could help meet metering and spacing constraints imposed by others.The fourth report derived from OPSNET database, "OPSNET: Delays: EDCT/GS/TMI By Cause Report" provided the TMI-to weather delay counts and TMI-to volume delay counts.TMI-to delays is defined as delays resulting from a national or local traffic management initiative reported in OPSNET and charged to the facility that is the originating cause of the restriction.These initiatives also include DSP, ESP, ASP, MIT, MINIT, EDCT, GS, and SWAP.These delays may be experienced by aircraft at another facility, but are charged to the causal facility.For example, 5,561 aircraft were delayed at other airports due to weather caused restrictions imposed by Atlanta as listed in Table A-2 in the Appendix.TMI-to volume delays are caused by restrictions imposed for moderating the traffic demand.In addition to weather and volume delay counts and minutes, the report contains delays due to equipment, runway and other causes.Passenger enplanements data listed in Table A-2 in the Appendix were obtained from the main FAA website in the "Passenger Boarding and All-Cargo Data" Section (see Ref. 4).The main source of enplanement statistics is the U. S. Department of Transportation (DOT).Scheduled and nonscheduled U. S. certificated aircarriers, commuter air-carriers, and small certificated aircarriers submit data to DOT on Form 41 Schedule T-100.Foreign flag air carriers submit data to DOT on Form 41 Schedule T-100(f).In addition, an annual survey of airtaxi/commercial operators, who report their nonscheduled activity on FAA Form 1800-31, is conducted by the FAA.As one would expect, passenger enplanement is highly correlated to the number of commercial operations.The value of the correlation coefficient (also known as Pearson's correlation coefficient and Pearson's productmoment correlation coefficient) was found to be 96.7% and the p-value was found to be zero to six decimal places, which indicates highly significant correlation.Figure 1 shows the plot of passenger enplanements as a function of commercial operations based on the data in Table A-2 in the Appendix.The dotted line indicates a linear fit between enplanements and commercial operations.The coefficient of determination (R 2 value) was found to be 0.935.A closer look at enplanement data and commercial operations data in Table A-2 in the Appendix indicates some data inconsistencies.For example, 3,634 air-carrier and air-taxi operations were conducted at Oxnard, CA (OXR), but the number of enplanements is just 3. Similarly, numbers look very low for GYY, TEB, and VNY.The following response was received from the FAA when asked for an explanation for the discrepancy.The enplanement numbers posted by the FAA include all revenue passengers that boarded a flight conducted by a large certificated, commuter, or foreign air-carrier.They also include the enplanements for on demand air-taxi operators.However, these small operators are not required to report their passenger enplanements to the FAA.So while FAA has some data, it can vary from year to year based on whether the operators voluntarily report their passenger activity.This impacts the non-primary airports like TEB and VNY that serve corporate and business flights which may have a significant number of Part 135 on demand operations.FAA facility pay level data listed in Table A-2 in the Appendix were obtained from the "OPSNET: Facility Information: Detail Report" derived from the OPSNET database.Reference 5 provides a complete description of the formula for pay setting.The facility pay level varies between "null" and 12. Null level is indicated by a zero in the table.Since facility pay level is based on a formula that considers both the number of operations and complexity factors such as, tower with or without radar, performance characteristics of aircraft using the airport, runway and taxiway layout, proximity to other airports, military operations and terrain, it can be used as a metric for categorizing airports.Correlation between the number of operations and the levels given in Table A-2 was found to be 68.6%.The correlation improved to 78% with 0 levels excluded.In both these instances, the correlations were determined to be significant with p-value of zero up to six decimal places.It is thus seen that number of operations dominates the formula for pay setting.ASPM and OPSNET databases provide operational statistics on Core airports, Operational Evolution Partnership (OEP 35) airports, 45 airports tracked in OPSNET (OPSNET 45) and the 77 airports tracked in ASPM.Core airports are the 30 busiest commercial U. S. airports that serve as hubs for airline operations at major metropolitan areas.OEP 35 airports are commercial U.S. airports with significant activity.These airports serve major metropolitan areas and also serve as hubs for airline operations.More than 70 percent of passengers move through these airports.The Venn-diagram in Fig. 2 shows the airport codes of the Core, OEP 35, OPSNET 45 and ASPM 77 airports.The rectangular box shows all the 77 ASPM airports.The 30 Core airports are enclosed in the innermost circle with thick solid boundary.All the Core airports and five additional airports enclosed in the circle with dotted line boundary form the OEP 35 airport set.OPSNET 45 airports are enclosed in the largest circle with a thin solid boundary.Observe that OPSNET 45 set contains all the Core and OEP 35 airports except Honolulu International airport (HNL).The 31 airports outside the circles only belong to ASPM 77.The airports in Fig. 2 were identified as large-hub airports, medium-hub airports, small-hub airports and non-hub airports based on their designation in Ref. 6.A large-hub airport is defined as an airport with 1% or more of total U. S. passenger enplanements.A medium-hub airport is defined as an airport with 0.25% to 0.99% of total U. S. passenger enplanements.An airport with 0.05% to 0.249% of total U. S. passenger enplanements is categorized as a small-hub airport.Finally, an airport with less than 0.05% of total U. S. passenger enplanements is termed a non-hub airport.All Core airports other than Memphis International airport (MEM) are large-hub airports.These 29 airport codes inside the smallest circle are shown in red without a superscript.The 34 medium-hub and 6 non-hub airports are indicated in black and magenta, and by "m", and "*" superscripts, respectively.The airport codes of 8 small-hub airports are in blue and underlined.Figure 3 shows the airport codes of ASDE-X airports, Low Cost Ground Surveillance (LCGS) airports and Airport Surface Surveillance Capability (ASSC) airports.List of names of airports with ASDE-X, LCGS and ASSC were obtained from Refs.7-9.LCGS is based on single surface movement radar concept.FAA is currently evaluating LCGS at Spokane (GEG), Manchester (MHT), San Jose (SJC), Reno (RNO) and Long Beach (LGB).Airport codes of LCGS airports are indicated in blue with a "*" superscript.As opposed to ASDE-X that uses radar, multilateration and Automatic Dependent Surveillance-Broadcast (ADS-B), ASSC derives data from just multilateration and ADS-B.FAA expects ASSC to begin tracking transponder-equipped aircraft and ADS-B equipped ground vehicles by 2017 at Portland (PDX), Anchorage (ANC), Kansas City (MCI), New Orleans (MSY), Pittsburgh (PIT), San Francisco (SFO), Cincinnati (CVG), Cleveland (CLE) and Andrews Air Force Base.ASSC airport codes in green are underlined.Airports without a surface Figure 3. Airports with ASDE-X, LCGS and ASSC surface surveillance systems, and airports without surface surveillance systems.surveillance system are indicated with airport codes in black with an "n" superscript.The remaining 35 airports in red are ASDE-X airports.After removing all the ASDE-X airports, small-hub and non-hub airports from Fig. 3, the remaining 29 airports shown in Fig. 4 are considered as suitable candidates for further analysis.San Francisco and Tampa are the only two large-hub airports remaining in this set.The other 27 are medium-hub airports.Nine airports in this set will either have LCGS or ASSC systems for surface surveillance.Since surveillance data can be used for comparing estimates against reality, these airports could be considered for near term development and testing of wheels-off time estimation methods.To identify airports that could benefit from wheelsoff time estimation, the important metrics are, 1) taxi-out delay, 2) TMI-from delay counts and 3) number of commercial operations.Without a suitable means for accounting for taxiway delays due to interactions between arriving and departing aircraft, one could resort to estimating wheels-off time based on the single value of taxi-time for the airport from ASPM database.This however, would lead to larger wheels-off time prediction errors at airports with larger taxi-out delays.Thus, airports with larger taxi-out delays can be expected to benefit more by being able to reduce larger wheels-off time prediction errors by employing a wheels-off time estimation method.Airports with TMI-from delays have to ensure that the affected aircraft depart at times coordinated with downstream facilities so that the restrictions imposed by them are met.Airports with higher TMI-from delay counts have to depart more aircraft on time; therefore, wheels-off time estimate can be expected to have a greater impact at these airports.Finally, improved predictability of taxi-time and wheelsoff time has the potential of improving planning and scheduling for greater surface movement efficiency at busier airports, the ones with large number of commercial operations.In addition to estimating taxi-out time, gate departure time needs to be known or estimated for wheels-off time prediction since wheels-off time is obtained by adding the taxi-out time to the gate departure time.Unfortunately, gate departure time is difficult to estimate.If airlines are unable to provide gate departure times prior to actual departure, the only choices are scheduled departure time from the Official Airline Guide (OAG) or proposed departure time from filed flight-plans.These times, however, are not accurate.It is also difficult to estimate gate departure delay by observing airport state data.The study in Ref. 3 found the correlation between gate departure delay and metrics derived from airport state data such as, number of aircraft on the surface, airport departure rate, wind and visibility to be quite low.Like Ref. 3, this study also assumes that gate departure time is known.To group the 29 airports shown in Fig. 4 based on the values of taxi-out delay, TMI-from delay counts and number of commercial operations, and the other metrics listed in Table A-2 in the Appendix, the multiple-metric K-Means classifier described in Ref. 10 is used.The K-Means method partitions data into specified number of groups such that the means associated with the groups are as widely separated as possible.Data elements are then labeled based on their closeness to the group means for reducing the variance.Group means are then re-computed based on the elements assigned to the groups.The process of assignment of elements to the groups and computation of group means is continued till convergence is achieved, that is, group means do not change with successive iterations.The 1.The minimum, mean, standard deviation and maximum values for each group are listed in the last four columns.Airport codes in each group are arranged in the non-increasing order.For example, ONT has the maximum taxi-out delay in Group 1 and OGG has the minimum taxi-out delay in Group 1.The three groups can be considered to be low, medium and high taxi-out delay groups.Groups obtained with TMI-from delay counts and with number of commercial operations are summarized in Tables 2 and3.Observe from Table 2 that Raleigh-Durham (RDU) has to comply with more departure restrictions compared to the other airports.San Francisco (SFO), which has the most taxi-out delays and number of commercial operations, is a member of Group 2 in Table 2 with TMI-from delay counts of 1,848 in the year 2011 (see Table A-2 in the Appendix).Grouping based on taxi-out delay ratio and FAA level are summarized in Tables 4 and5.Comparing Table 1 to Table 4, it is seen that ten airports (ONT, MSY, BUR, SJC, OAK, DAL RDU, SAT, TUS and ABQ) in Table 1 move one level higher in Table 4.These airports have higher average taxi-out delays compared to their nominal taxi-out times.Comparing Table 3 two levels higher, and only two airports-SJU and SFO moved one level down.This reconfirms the finding that the number of operations is significantly correlated to the FAA pay level.Thus, FAA pay levels can be used in lieu of number of commercial operations.Finally, grouping based on TMI-to weather delay counts and TMI-to volume delay counts are given in Tables 6 and7, respectively.Only airports that delayed at least 10 aircraft in the year 2011 were considered for grouping in Tables 6 and7.This reduced the set of 29 airports to just 8 based on TMI-to weather delay counts.San Francisco, the sole member of Group 3 in Table 6, is known to be severely affected by visibility.In 2011, it was responsible for causing over 18,000 aircraft bound for SFO to be delayed elsewhere.Only three airports-CLE, SFO and DAL in Table 7 caused aircraft bound for those airports to be delayed elsewhere due to traffic volume.It is reasonable to expect that departures would be affected when arrivals are impacted by weather and traffic volume.Wheels-off time estimates at these airports would have to consider weather and traffic volume conditions.The grouping results discussed above in Tables 1 through 7 considered a single metric for classification.Groups can also be formed by first creating a composite ID for each airport based on single metric classifications and then placing all the airports with the same ID in a group.For example, CVG is a member of Group 1 based on taxi-out delay, Group 2 based on TMI-from delays and Group 2 based on number of commercial operations, therefore its composite ID is (1,2,2).Similarly, the composite ID of IND is (1,2,2).Thus, CVG and IND belong to the same group based on their composite ID.This method is described in Ref. 10. Table 8 lists the airport grouping with composite ID constructed based on Tables 1, 2 and3.Following this procedure, a member of group with Group ID (3,3,3) would be expected to benefit the most from wheels-off time estimation.Mean values of taxi-out delay, TMI-from delay counts and number of commercial operations for each group of airports are listed in the columns with headings-Mean 1, Mean 2 and Mean 3, respectively.Airport codes of airports that will receive ASSC for surface surveillance are shown in green boldface type and underlined.Airport code of San Jose, where LCGS is being tested, is shown in blue boldface type with "*" superscript.Table 8 shows that other than groups with IDs (2, 1, 1), (2,2,1) and (2,3,2), there is at least one airport in the group that will have a surveillance system.These airports should be initially targeted for developing and testing wheels-off time estimation methods.Track data (position as a function time) from surveillance can be used to determine gate, gate departure time, spot crossing time, ramp-area path and taxiway path needed for developing wheels-off time estimation methods.The estimated wheels-off time can be compared with the actual wheels-off time also using actual track data.The nine groups in Table 8 can be reduced further by merging smaller adjacent groups.Table 9 presents such a grouping by first giving preference to number of commercial operations and then to TMIfrom delay counts using the Group IDs.The first group consisting of Group IDS (1, 1, 1), (2, 1, 1) and (2, 2, 1) has MSY and SJC, two airports that will have surface surveillance systems.The second group of airports consisting of Group IDs (1, 1, 2), (2,1,2), (1,2,2), (2,2,2) and (2,3,2) has six airports-ANC, PDX, CVG, CLE, MCI and PIT that will receive ASSC.One of these airports can be chosen to represent the second set.The third group consisting of Group ID (3,2,3) has SFO as its sole member, an airport that will have ASSC.Thus, SJC with LCGS, CLE with ASSC and SFO with ASSC are good choices for representing the three groups in Table 9. | |
| III. Wheels-off Time Estimation MethodIn this section, the procedure for estimating wheel-off time at the 29 non-ASDE-X airports in Table 9 is described.It is assumed that airport geometry is available.Taxiways and runways are usually represented by polygons, where the locations of the vertices of polygons are specified by Cartesian coordinates with respect to a frame of reference.Locations of gates and spots are also specified with respect to the same frame of reference.Gate and spot locations and the polygons can be processed to create the node-link graph of the airport.An example of a node-link graph is shown in Fig. 5. Reference 11 describes the procedure for creating the node-link graph using taxiway and runway polygons.Any physical path for going from one location to another on the airport surface is represented by a sequence of nodes and links in this node-link graph.A location on the node-link graph is thus equivalent to a location on the physical airport surface.Since polygons, which are area elements, are represented by links, which are line elements, traversing along the links can be thought of as traversing along the taxiway centerline.Given this node-link graph representation, the first step of the proposed wheels-off time prediction consists of representing the taxi clearance issued by the controller as a path in the node-link graph.Taxiway clearance is specified as an ordered list of taxiway segments that the aircraft is required to follow after pushback from the gate to runway.Mapping from taxiway segments to polygons and from polygons to links is used to determine the path in the node-link graph.In this early phase of development, aircraft position data acquired by ASDE-X during surface movement at Dallas-Fort Worth airport are derived from recorded SDSS logs to identify path from gate to runway in the node-link graph.Polygon containing the aircraft position is identified and then polygon to link mapping is used to identify the corresponding link.The sequence of links then determines the path.The next step of the wheels-off time prediction consists of integrating the aircraft equations of motion along the path in the node-link graph.Starting with the gate location and the gate pushback time, this process generates a time history of positions along the path.This is the classical procedure of open-loop trajectory prediction.If this was the only aircraft moving on the surface, open-loop prediction would be reasonable.In reality however, aircraft moving on the surface interact with each other as the arrivals taxi-in towards their gates and departures taxi-out towards the runways.Aircraft have to stop at intersections to let other aircraft pass.Similarly, they have to often stop and wait for the active runway to be clear prior to crossing it.Separation rules also have to be followed.Departures also have to queue and wait prior to entering the runway so that there is adequate separation with respect to the prior aircraft that took off from the same runway.These rules have been programmed in the Surface Operation Simulator and Scheduler (SOSS) that is being developed at NASA Ames Research Center.SOSS uses kinematic models of different types of aircraft and the node-link graph to simulate surface traffic.While SOSS has been designed to work with schedulers for optimizing surface operations, SOSS has been used without a scheduler in this study.Routes from gate to runway, gate departure times and aircraft types are input to SOSS to simulate surface traffic for generating the results discussed in the section below. | |
| IV. ResultsThe SOSS-model-based method, described in Section III, and a data-driven method are evaluated.The first method consists of using SOSS.This means that ramp-area, movement-area and queue-area speeds specified for each aircraft type are used in the prediction.The second method is a data-driven method in which average taxi-times derived from several days of actual data are added to the gate-out time or the spot crossing time for predictions.Nineteen hours, 5:00 am to 12:00 midnight, of each day of Dallas-Fort Worth surface traffic data derived from 8/8/2011 to 8/13/2011 SDSS logs were processed to create inputs for the two methods and for validating the predictions.These days had good weather.There were a total of 5,208 arrivals and 5,256 departures.Table 10 the number of arrivals and departures, and the flow configuration on each day.DFW is operated in the southflow configuration 70% of the time. 3On the 11th, DFW switched from south-flow configuration to north-flow configuration at 2:00 p.m. local time and then back to southflow configuration at 5:00 p.m. DFW switched from north-flow configuration to south-flow configuration at 8:30 a.m. on the 13 th .The SOSS-based method and the data-driven method were used to generate estimates of queue-area entry time, runway entry time, wheels-off time, queue-area entry sequence and runway entry sequence.These times and sequences were compared against actual values derived from SDSS logs.Queue-area entry, runway entry and wheels-off time are defined using Fig. 6 as an example.Figure 6 shows the locations of queue-area entry nodes, hold nodes and departure nodes related to runway 17R.Observe that the queue-area entry nodes are placed such that the queue is set up in the correct order.For example, an aircraft on taxiway J could enter the queue-area earlier if the entry-node were placed closer to the intersection of taxiways J and Y than an aircraft that enters upstream on taxiway J (near the queue-entry node on taxiway J depicted in the figure) and still be behind the upstream aircraft.To maintain the correct order of entry into the queue, the queue-entry node is placed at the last entry node along the taxiway in the queue-area.In SOSS simulation, aircraft movement is simulated from gate to spot, from spot to runway hold node, from hold node to departure node and from departure node to wheels-off.For the example in Fig. 6, queues are formed along taxiways EF, EG and EH and taxiways J, K and L as aircraft wait to reach the runway hold nodes.SOSS computes spot crossing time, runway hold node arrival time, wait time at the hold node, departure node arrival time, wait time at the departure node and wheels-off time.Time from departure node to wheels-off is specified for different types of aircraft.Queue-entry time is determined as the time when SOSS simulated aircraft position is at or just prior to the queue-area entry node.Runway entry time is determined by adding the wait time at the hold node to the hold node arrival time.Actual hold node arrival time, runway entry time and wheels-off time are obtained by processing the track data obtained from SDSS logs with airport geometry data.Results obtained using the two methods are discussed below. | |
| SOSS-Model-BasedFigure 7 shows the histogram of the difference between the actual queue-area entrance time of the departures and the estimated queue-area entry times derived from SOSS simulation of 19 hours of 8/11/2011 Dallas-Fort Worth surface traffic consisting of 897 arrivals and 915 departures.August 11 was challenging because of airport configuration change from south-flow to north-flow and then back to south-flow.During the south-flow to northflow change, departures for 35L left their gates and queued in the queue-area and waited for a long time for departures and arrivals in the previous south-flow configuration to clear the runways.Queue-area entry time results shown in Fig. 7 were computed with respect to spot crossing time.This means that the SOSS simulation used spot position and time as initial conditions.The histogram in Fig. 7 shows the maximum error to be 21 minutes.It was determined that about 80% of the actual departures arrived within two-minutes early to one-minute window with respect to SOSS-based prediction of queue-area entry time.The two-minutes early to one-minute late window is Figure 10.Cumulative absolute value of wheelsoff time estimation error.used as the wheels-off time requirement in Ref. 12 for Precision Departure Capability for Call For Release.Later on results are presented with respect to gate departure time.Gate-based results were found to be worse than the spotbased results.Figure 8 shows the cumulative absolute estimation error.For example, absolute value of queue-area entry time error is less than two-minutes for 87% and less than five-minutes for 97% of the departures.The main source of queue-area entry time error is the aircraft speeds assumed in SOSS.Actual maximum speeds in SDSS logs were found to be much higher in several instances compared to the nominal speeds assumed for the aircraft type in SOSS.The maximum speed difference was found to be 16 knots compared to SOSS speed of 15 knots.Average difference was found to be 8 knots for August 11 data.These findings suggest that SOSS nominal speeds can be better tuned to improve the estimates.Figure 9 shows the histogram of the difference between the actual wheels-off time of the flights and the estimated wheels-off time derived from SOSS simulation with reference to spot crossing.Maximum wheels-off time error was found to be 24 minutes.47% of the departures were within the two-minutes early to one-minute late window and 59% were within the plus-minus two-minute window.86% were within the plus-minus five-minute window.The cumulative absolute wheels-off time estimation error is given in Fig. 10.Comparing Fig. 9 to Fig. 7 and Fig. 10 to Fig. 8, it may be seen that queue-area entry time estimation is much better than wheels-off time estimation.Part of the reason is that Dallas-Fort Worth has multiple queues in the queuing-area from which flights exit to enter the runway.Currently a simple logic of first-in first-out based on the queue-area entry time is being used to determine runway entry order.In the real operations, flights that need to comply with traffic flow management initiatives are given priority.Better prediction of runway entry time, which directly affects wheels-off time prediction, might require knowledge of flight priority.Queue-area entry time, runway entry time and wheels-off time estimation errors were computed with spot and gate as references for the six days listed in Table 10.The two-minute early to one-minute late compliance results are summarized in Table 11.The next set of results is for queue-area entry and runway entry sequences.To determine queue-area entry sequence for SOSS simulated aircraft and actual aircraft (based on SDSS track data), time of arrival at the queue entry nodes are sorted in increasing order for departures going to each runway.Sequence error is then computed as the difference between the actual aircraft and SOSS simulated aircraft positions in the sorted lists.This same procedure is repeated to determine runway entry sequence error.It should be noted that the runway entry sequence is same as the wheels-off sequence because only one aircraft is permitted to be on an active runway at a time.Table 12 shows the percentages of departures without sequence errors on the six days.Table 13 shows percentages with at most one sequence error.This means that the actual aircraft was either in the correct sequence or was just ahead or just behind the SOSS predicted sequence.These results show that sequence errors are reduced when spot crossing time is used as a reference for SOSS-based predictions.Maximum spot-based queue-area and runway entry sequence errors were found to be 13 and 12, respectively, on August 8 data.The highest gate-based queue-area and runway entry sequence errors were found to be 12 and 12, respectively, also on August 8 data.Results for the six days show that there is a significant loss of estimation accuracy from queue-area entry to runway entry.The loss is less from runway entry to wheels-off.Gate-based results are worse than spot-based results because of imprecise gate-out time information.Gate-out time is estimated based on the proximity of the SDSS reported position to the gate and SDSS reported speed, which indicates movement. | |
| SDSS-Based Average Taxi-TimeThis method assumes that historical taxi-time data from spot and gate to queue-area entry locations and wheelsoff are available.This method like the SOSS-based method, discussed in the previous section, does not assume that surface surveillance information is available in real-time.Historical information can be derived from the Out-Off-On-In (OOOI) data provided by airlines and Automatic Dependent Surveillance (ADS) position reports provided by ADS equipped aircraft.To compute the spot and gate to queue-area and wheels-off taxi-times, six days of surface data were processed to identify the unique 226 spot-runway and 522 gate-runway combinations.Next, the number of departures associated with spot-runway and gate-runway were counted.Analysis showed that 25% of the spotrunway combinations were used by a single aircraft, 36% were used by two or fewer aircraft and 61% were used by 10 or fewer aircraft.The maximum number of times the spot-runway combination was used was 301 times.Of the 522 gate-runway combinations, 31% were used by only one departure, 45% were used by two or fewer departures and 57% were used by 10 or fewer departures.The maximum number of times was 38.The six days of taxi-time data were averaged and assigned to each spot-runway and gate-runway pair.Queue-entry and wheels-off times were predicted by adding the spot crossing time or the gate departure time to the average taxi-times.The actual queueentry time and wheels-off time of the departures were compared to these predictions.Table 14 shows the percentages of departures that could be predicted within the two-minutes early to oneminute late compliance window.This table also shows that spotbased estimates are a bit better than gate-based estimates.Comparing the gate-based results in Table 11 to those in Table 14, it is seen that both queue-area entry time and wheelsoff time errors are less with this method.One of the reasons for better results is that the average taxitime is same as the actual taxi-time in instances of single departures associated with a spot-runway or gate-runway pair.The second reason is that the taxi-times based on actual track data include the influence of the actual path (not the idealized node-link path) and speed.The maximum queue-entry time and wheels-off time errors were 29 minutes and 26 minutes on August 8, respectively, when spot crossing time was used as the reference for estimation.Wheels-off time could be predicted within plus-minus five-minutes for at least 90% of the departures.This minimum value of 90% was obtained for August 11 data.Maximum queue-entry time error of 27 minutes and wheels-off time error of 24 minutes were obtained with gate-based predictions of August 8 departures.At a minimum, wheels-off time of 89% percent of departures in each of the six days could be predicted within plus-minus five-minutes.The percentage, 89%, was lowest for August 11 departures.August 13 gate-based wheels-off result of 55.6% in Table 14 are close to 59.2% obtained with the neural network in Ref. 3. Wheels-off time compliance of 53.5% of neural network predictions with respect to six days, August 7 through 12, of training data is comparable to the average compliance of 51.5% in Table 14.Queue-area entry and runway entry sequence error results are given in Tables 15 and16.Maximum queue-area entry and runway entry sequence errors were obtained with August 8 data.For spot-based estimates, these were 14 and 12 departures.For gate-based estimates, these errors were 11 and 10.The sequence errors for each of the six days were found to be very close to those obtained with the method described in the previous section.Comparing the results in Tables 15 and16 to Tables 12 and13, it is seen that the gate-based estimates are a bit better with the SDSS-based Average Taxi-time model compared to with the SOSS-based simulation method.These results suggest that the Average Taxi-Time model could be used for predictions at all airports without resorting to a more detailed simulation based approach.This method is also simple to implement, it does not require airport geometry and the Gate-out and wheels-off data reported by airlines can be used to determine the average gate to wheels-off taxi-time needed by this model.The method is also computationally efficient because an addition operation is required for estimating wheels-off time and sorting is required to estimate the runway entry sequence. | |
| V. Conclusions and Future WorkIn the first part of this paper, 29 airports were identified for development and testing of wheels-off estimation methods after removing airports with Airport Surface Detection Equipment Model-X (ASDE-X), small-hub airports and non-hub airports from the set of 77 major U. S. airports tracked in the Federal Aviation Administration's Aviation System Performance Metrics database.These 29 airports were classified into three groups using a K-Means procedure based on taxi-out delay, traffic management delay counts and number of commercial operations.Within these three groups, San Jose International, Cleveland-Hopkins International and San Francisco International are recommended for further development and validation of wheels-off time estimation methods.San Jose has the least number of commercial operations and San Francisco has the most.In the second part of the paper, a simulation based method and a data-driven method, which uses historical taxi-time information, for estimating queue-area entry time, runway entry time and wheels-off time were described.Queue-area entry time, runway entry time and wheelsoff time estimates were generated with reference to spot crossing time and gate departure time for six days of August 2011 Dallas-Fort Worth surface traffic data.These estimates were compared with the actual values determined by processing actual ASDE-X based aircraft position data.The main findings are as follows.Spot-based estimates are better compared to gate-based estimates.The data-driven method produces better gate-based estimates compared to the Surface Operation Simulator and Scheduler (SOSS) based method assuming model speeds.If surface surveillance data are unavailable, the data-driven method could be used for estimating queue-area entry time, runway entry time and wheels-off time.This method could also be used for estimating queue-area and runway entry sequence.These conclusions are expected to be equally applicable to airports such as San Jose, Cleveland and San Francisco.The next step consists of creating a geometry and node-link model for the San Jose airport with the data received from the City of San Jose.Several days of San Jose airport surface surveillance data acquired via the Low Cost Ground Surveillance (LCGS) system will be processed to create the parameters and inputs needed by the datadriven model and by the SOSS-based simulation.The estimates generated by these methods will then be compared with LCGS derived values.Figure 1 .1Figure 1.Correlation between commercial operations and passenger enplanements. | |
| Figure 2 .2Figure 2. ASPM 77 airports categorized as largehub, medium-hub, small-hub and nonhub airports. | |
| Figure 4 .4Figure 4. Airports remaining after removing ASDE-X airports, and small-hub and non-hub airports. | |
| Figure 5 .5Figure 5. Node-link graph of Dalla-Fort Worth airport. | |
| Figure 8 .8Figure 8. Cumulative absolute value of the queuearea entry time estimation error. | |
| Figure 7 .7Figure 7. Queue-area entry time estimation error. | |
| Figure 9 .9Figure 9. Wheels-off time estimation error.Figure10.Cumulative absolute value of wheels- | |
| Table 3 .3Grouping based on number of commercial operations.Group IDAirportsMin.MeanStd.Max.57,64890,43018,572 116,4142PDX, ANC, CLE, TPA, CVG, RDU, BNA, IND, MCI, SJU, OAK, PIT127,723 153,339 22,103 190,1083SFO386,941 386,9410386,9411DAL, SAT, AUS, SJC, MSY, SMF, OGG, ABQ, BUF, PBI, OMA, JAX, ONT, RSW, BUR, TUS | |
| Table 1 .1Grouping based on average taxi-out delays in minutes.Group IDAirportsMin.Mean Std.Max.1ONT, MSY, BUR, IND, AUS, SJU, CVG, SJC, OAK, DAL, ANC, OGG1.51.90.22.12RDU, PIT, CLE, SAT, TUS, ABQ, BNA, RSW, TPA, BUF, PBI, PDX, JAX, MCI, OMA, SMF2.22.50.33.23SFO4.44.40.04.4 | |
| Table 4 .4Grouping based on average taxi-out delay ratio in percentage.three groups obtained based on taxi-out delay are summarized in TableGroup IDAirportsMin.MeanStd. Max.1AUS, OGG, IND, SJU, ANC, CVG13.915.61.517.32ONT, CLE, PIT, SMF, BNA, TPA, PDX, RSW, MSY, OAK, BUF, MCI, DAL, OMA, BUR, PBI, JAX, SJC17.919.91.322.03SFO, ABQ, SAT, RDU, TUS23.324.21.526.8 | |
| Table 2 .2to Table5, it is seen that 13 airports (ABQ, AUS, JAX, MSY, PBI, BUF, DAL, RSW, TUS, CVG, TPA, CLE and PIT) moved one level up in Table5, one airport-SAT jumped Grouping based on TMI-from delay counts.Group IDAirportsMin.MeanStd. Max.1MSY, PDX, AUS, SAT, OMA, DAL, SMF, BUR, SJC, OAK, TUS, ABQ, ONT, SJU, ANC, OGG104592849052CVG, PIT, CLE, IND, SFO, BUF, TPA, MCI, BNA, PBI, JAX, RSW1,1721,772412 2,5313RDU3,5573,55703,557Downloaded by NASA AMES RESEARCH CENTER on August 14, 2013 | http://arc.aiaa.org|DOI: 10.2514/6.2013-4274Copyright© 2013 by the American Institute of Aeronautics and Astronautics, Inc.The U.S. Government has a royalty-free license to exercise all rights under the copyright claimed herein for Governmental purposes. | |
| Table 5 .5Grouping based on FAA level.Group IDAirportsMin.MeanStd.Max.1BUR, OGG, SJC, SJU, OMA, ONT, SMF66.60.572ABQ, AUS, BNA, IND, JAX, MCI, MSY, PBI, RDU, SFO, ANC, BUF, DAL, OAK, PDX, RSW, TUS88.60.593CVG, TPA, CLE, PIT, SAT1010.40.611 | |
| Table 6 .6Grouping based on TMI-to weather delay counts.Group IDAirportsMin.MeanStd.Max.1CLE, IND, TPA, RDU, CVG, SAT1849491462DAL30030003003SFO18,679 18,6790 18,679Table 7. Grouping based on TMI-tovolume delay counts.Group IDAirports Counts1CLE112SFO243DAL173 | |
| Table 9 .9Grouping based on preferences to number of commercial operations and TMI-from delay counts.Group IDAirportsMean 1Mean 2Mean 31, 1, 1AUS, OGG, BUR, DAL, MSY, ONT, SJC*1.946897,4062, 1, 1OMA, SMF, ABQ, SAT, TUS2.450390,6712, 2, 1BUF, JAX, PBI, RSW2.31,42577,9201, 1, 2ANC, SJU, OAK1.8221 151,6432, 1, 2PDX2.3887 190,1081, 2, 2CVG, IND22,209 149,2392, 2, 2BNA, CLE, MCI, PIT, TPA2.51,859 150,4312, 3, 2RDU3.23,557 144,3993, 2, 3SFO4.41,848 386,941 | |
| Table 8 .8Grouping based on taxi-out delay, TMI-from delay counts and number of commercial operations.Group IDAirportsMean 1Mean 2Mean 31, 1, 1AUS, OGG, BUR, DAL, MSY, ONT, SJC*1.946897,4061, 1, 2ANC, SJU, OAK1.8221 151,6431, 2, 2CVG, IND2.02,209 149,2392, 1, 1OMA, SMF, ABQ, SAT, TUS2.450390,6712, 1, 2PDX2.3887 190,1082, 2, 1BUF, JAX, PBI, RSW2.31,42577,9202, 2, 2BNA, CLE, MCI, PIT, TPA2.51,859 150,4312, 3, 2RDU3.23,557 144,3993, 2, 3SFO4.41,848 386,941 | |
| Table 10 .10lists Selected days.Date# Arrivals # DeparturesDayFlow8/8/2011868881MondaySouth8/9/2011870860TuesdaySouth8/10/2011900902Wednesday South8/11/2011897915ThursdaySouth, North, South8/12/2011888892FridaySouth8/13/2011785806SaturdayNorth, SouthFigure 6.Examples of queue-area entry nodes, hold nodes and departure nodes. | |
| Table 11 .11Compliance within two-minutes early to one-minute late.DateSpot-based Queue (%) Runway (%) Wheels-off (%) Queue (%) Runway (%) Wheels-off (%) Gate-based885.864.058.260.047.146.3983.753.750.363.344.540.91084.758.553.361.047.044.91180.152.647.059.542.438.61287.358.051.863.049.046.11384.660.454.262.451.447.5Table 12. No sequence error.DateSpot-based Queue (%) Runway (%) Queue (%) Runway (%) Gate-based870.462.049.547.1965.951.752.744.41072.959.148.845.01169.154.851.445.21272.262.653.647.91372.564.552.048.3 | |
| Table 13 .13At most one sequence error.DateSpot-based Queue (%) Runway (%) Queue (%) Runway (%) Gate-based894.690.785.983.2993.383.585.577.21094.690.784.181.21193.086.385.980.01292.989.084.981.41395.291.485.081.8 | |
| Table 14 .14Compliance within two-minutes early to one-minute late.DateSpot-based Queue (%) Wheels-off (%) Queue (%) Wheels-off (%) Gate-based886.956.577.750.6986.250.077.748.11086.652.578.451.61181.754.674.552.11286.853.377.250.91386.157.477.855.6 | |
| Table 16 .16At most one sequence error.DateSpot-based Queue (%) Runway (%) Queue (%) Runway (%) Gate-based896.091.490.387.1993.484.588.381.51095.690.691.985.51193.983.290.781.11294.189.590.586.91395.489.790.286.0 | |
| Table 15 .15No sequence error.models if gate departure time based wheels-off time and runway entry sequence predictions are desired.node-linkDateSpot-based Queue (%) Runway (%) Queue (%) Runway (%) Gate-based871.764.963.152.4970.054.260.051.01071.758.461.550.81168.352.263.047.31274.660.459.452.71373.458.661.851.9 | |
| Table A -A1. 77 ASPM airports.#Airport CodeAirport NameLocation1ABQAlbuquerque International SunportAlbuquerque, New Mexico2ANCTed Stevens Anchorage InternationalAnchorage, Alaska3ATLHartsfield -Jackson Atlanta InternationalAtlanta, Georgia4AUSAustin-Bergstrom InternationalAustin, Texas5BDLBradley InternationalWindsor Locks, Connecticut6BHMBirmingham-Shuttlesworth InternationalBirmingham, Alabama7BNANashville InternationalNashville, Tennessee8BOSGeneral Edward Lawrence Logan InternationalBoston, Massachusetts9BUFBuffalo Niagara InternationalBuffalo, New York10BURBob HopeBurbank, California11BWIBaltimore/Washington International Thurgood Marshall Baltimore, Maryland12CLECleveland-Hopkins InternationalCleveland, Ohio13CLTCharlotte/Douglas InternationalCharlotte, North Carolina14CVGCincinnati/Northern Kentucky InternationalCovington, Kentucky15DALDallas Love FieldDallas, Texas16DAYJames M Cox Dayton InternationalDayton, Ohio17DCARonald Reagan Washington NationalWashington, District of Columbia18DENDenver InternationalDenver, Colorado19DFWDallas/Fort Worth InternationalDallas-Fort Worth, Texas20DTWDetroit Metropolitan Wayne CountyDetroit, Michigan21EWRNewark Liberty InternationalNewark, New Jersey22FLLFort Lauderdale/Hollywood InternationalFort Lauderdale, Florida23GYYGary/Chicago InternationalGary, Indiana24HNLHonolulu InternationalHonolulu, Hawaii25HOUWilliam P HobbyHouston, Texas26HPNWestchester CountyWhite Plains, New York27IADWashington Dulles InternationalWashington, District of Columbia28IAHGeorge Bush Intercontinental/HoustonHouston, Texas29INDIndianapolis InternationalIndianapolis, Indiana30ISPLong Island Mac ArthurNew York, New York31JAXJacksonville InternationalJacksonville, Florida32JFKJohn F Kennedy InternationalNew York, New York33LASMc Carran InternationalLas Vegas, Nevada34LAXLos Angeles InternationalLos Angeles, California35LGALa GuardiaNew York, New York36LGBLong Beach (Daugherty Field)Long Beach, California36MCIKansas City InternationalKansas City, Missouri38MCOOrlando InternationalOrlando, Florida39MDWChicago Midway InternationalChicago, Illinois40MEMMemphis InternationalMemphis, Tennessee41MHTManchesterManchester, New Hampshire42MIAMiami InternationalMiami, Florida43MKEGeneral Mitchell InternationalMilwaukee, Wisconsin44MSPMinneapolis-St Paul International/Wold-ChamberlainMinneapolis, Minnesota | |
| Table A -A1. 77 ASPM airports (Contd.).Table A-2. Airport metrics.# # Airport Airport Code Code Taxi-out Avg.Taxi-out Avg.from TMI-Airport Name Air-carrier ItinerantWeather TMI-toVolume TMI-toLocation EnplanementsLevel45MSY DelayLouis Armstrong New Orleans International Delay Delay and Air-taxi DelayDelayNew Orleans, Louisiana46OAK (min.)Metropolitan Oakland International Ratio (%) Counts Ops.CountsCountsOakland, California147ABQOGG2.51Kahului 23.929399,7990Kahului, Hawaii 0 2,768,4359248ANCOMA1.66Eppley Airfield 14.0132186,6989Omaha, Nebraska 2 2,354,9878349ATLONT7.52Ontario International 37.0 11,132916,8245,561Ontario, California 1,271 44,414,12112450AUSORD1.97Chicago O'Hare International 17.3 858 113,1110Chicago, Illinois 0 4,436,6619551BDLOXR2.67Oxnard 20.81,22986,8380Oxnard, California 0 2,772,3157652BHMPBI2.34Palm Beach International 19.8 36358,6940West Palm Beach, Florida 0 1,429,2828753BNAPDX2.43Portland International 21.1 1,576142,2472Portland, Oregon 0 4,673,0479854BOSPHL5.2Philadelphia International 28.7 5,734355,6078,964Philadelphia, Pennsylvania 80 14,180,730 10955BUFPHX2.38Phoenix Sky Harbor International 19.7 1,764 80,6450Phoenix, Arizona 0 2,582,59781056BURPIT2.07Pittsburgh International 18.9 41267,7260Pittsburgh, Pennsylvania 0 2,144,91571157BWIPSP3.35Palm Springs International 26.7 4,715258,540561Palm Springs, California 97 11,067,31991258CLEPVD2.74Theodore Francis Green State 21.9 2,203 179,382146Providence, Rhode Island 11 4,401,033101359CLTRDU5.52Raleigh-Durham International 30.9 4,308 513,8021,468Raleigh/Durham, North Carolina 1,558 19,022,535 121460CVGRFD1.93Chicago/Rockford International 13.9 2,531 157,36720Chicago/Rockford, Illinois 1 3,422,466 111561DALRSW1.78Southwest Florida International 19.2 458 116,414300Fort Myers, Florida 173 3,852,886862 16 DAYSAN2.57San Diego International 19.8 82148,2170San Diego, California 0 1,247,33381763DCASAT4.3San Antonio International 26.7 7,565278,757895San Antonio, Texas 95 9,053,004101864DENSDF3.71Louisville International -Standiford Field 26.5 3,302 630,9691,702Louisville, Kentucky 7 25,667,4991265 19 DFWSEA3.26Seattle-Tacoma International 22.7 5,296 640,5411,592Seattle, Washington 5 27,518,3581266 20 DTWSFO3.25San Francisco International 18.5 4,149436,534997San Francisco, California 303 15,716,8651167 21 EWRSJC8.49Norman Y. Mineta San Jose International 40.4 6,476 402,988 26,201San Jose, California 1,419 16,814,092102268FLLSJU4.16Luis Munoz Marin International 26.2 4,397 227,06125San Juan, Puerto Rico 20 11,332,466969 23 GYYSLC0.09Salt Lake City International 0.8 101,5740Salt Lake City, Utah 0 1,42002470HNLSMF1.96Sacramento International 15.5 29206,4460Sacramento, California 0 8,689,6991171 25 HOUSNA1.8John Wayne-Orange County 19.9 593139,280112Santa Ana, California 238 4,753,55482672HPNSTL2.39Lambert-St Louis International 18.8 1,946 64,60159St Louis, Missouri 171 972,38572773IADSWF4.04Stewart International 25.2 5,766314,384899Newburgh, New York 350 11,044,383112874IAHTEB4.84Teterboro 29.34,031516,708797Teterboro, New Jersey 166 19,306,660122975INDTPA2.02Tampa International 16.6 1,886141,11149Tampa, Florida 0 3,670,39693076ISPTUS1.51Tucson International 17.5 13619,8280Tucson, Arizona 0 781,39673177JAXVNY2.22Van Nuys 18.01,19177,3150Van Nuys, California 0 2,700,514932JFK8.532.79,296405,9768,89697523,664,8321033LAS3.7926.62,700484,19441613119,872,6171134LAX3.9626.64,503583,16780832130,528,7371135LGA11.6747.3 10,716364,14019,8453,19511,989,2271036LGB2.2316.729736,839001,512,212836MCI2.2119.61,603136,398005,011,000938 MCO3.6727.33,831300,075952917,250,4151139 MDW2.9927.11,855209,789661429,134,576840 MEM2.1414.11,883291,700550114,344,2131041 MHT2.0318.21,14551,376001,342,308542MIA3.4321.22,623375,20924712218,342,15812 | |
| Downloaded by NASA AMES RESEARCH CENTER on August 14, 2013 | http://arc.aiaa.org| DOI: 10.2514/6.2013-4274Copyright© 2013 by the American Institute of Aeronautics and Astronautics, Inc.The U.S. Government has a royalty-free license to exercise all rights under the copyright claimed herein for Governmental purposes. | |
| AcknowledgementsThe authors thank Dr. Tatsuya Kotegawa, Dr. Waqar Malik, William Chan and Dr. Banavar Sridhar for their careful review and suggestions for improving the paper. | |
| AppendixThe 77 major U. S. airports in the ASPM database are listed in Table .A-1. Table A- | |
| NASA Contract Number: NNA12AA14C, Mosaic ATM, Inc., 801 Sycolin Road, SE, Suite 306 | |
| AtmMosaic | |
| Inc | |
| Airport Surface Traffic Management Requirements Resulting from Variations in Airport Characteristics: Report on Airport Survey | |
| Leesburg, VA | |
| 20175. March 21, 2012 | |
| 5686 | |
| Mosaic ATM, Inc., "Airport Surface Traffic Management Requirements Resulting from Variations in Airport Characteristics: Report on Airport Survey," NASA Contract Number: NNA12AA14C, Mosaic ATM, Inc., 801 Sycolin Road, SE, Suite 306, Leesburg, VA 20175-5686, March 21, 2012. | |
| Performance Evaluation of SARDA: An Individual Aircraft-based Advisory Concept for Surface Management | |
| YoonJung | |
| TyHoang | |
| MiwaHayashi | |
| WaqarMalik | |
| LeonardTobias | |
| GautamGupta | |
| 10.2514/atcq.22.3.195 | |
| Air Traffic Control Quarterly | |
| Air Traffic Control Quarterly | |
| 1064-3818 | |
| 2472-5757 | |
| 22 | |
| 3 | |
| 2011 | |
| American Institute of Aeronautics and Astronautics (AIAA) | |
| USA/Europe Air Traffic Management Research and Development Seminar | |
| Jung, Y., Hoang, T., Montoya, J., Gupta, G., Malik, W., Tobias, L., and Wang, H., "Performance Evaluation of a Surface Traffic Management Tool for Dallas/Fort Worth International Airport," 9th USA/Europe Air Traffic Management Research and Development Seminar, 2011, pp. 1-10. | |
| Wheels-Off Time Prediction Using Surface Traffic Metrics | |
| GanoChatterji | |
| YunZheng | |
| 10.2514/6.2012-5699 | |
| 12th AIAA Aviation Technology, Integration, and Operations (ATIO) Conference and 14th AIAA/ISSMO Multidisciplinary Analysis and Optimization Conference | |
| Indianapolis, Indiana | |
| American Institute of Aeronautics and Astronautics | |
| Sep. 17-19, 2012 | |
| Federal Aviation Administration. cited: 2/25/2013 | |
| Chatterji, G. B., and Zheng, Y., "Wheels-Off Time Prediction Using Surface Traffic Metrics," AIAA-2012-5699, Proceedings of 12th AIAA Aviation Technology, Integration, and Operations (ATIO) Conference, Indianapolis, Indiana, Sep. 17- 19, 2012. 4 Federal Aviation Administration, URL: http://www.faa.gov/airports/planning_capacity/passenger_allcargo_stats/passenger/ [cited: 2/25/2013]. | |
| Health hazard evaluation report: HHE-81-042-832, Federal Aviation Administration, New York Air Route Traffic Control Center, Ronkonkoma, New York. | |
| 10.26616/nioshhhe81042832 | |
| cited: 2/25/2013 | |
| May 12, 2009 | |
| U.S. Department of Health and Human Services, Public Health Service, Centers for Disease Control, National Institute for Occupational Safety and Health | |
| Air Traffic Control Complexity Formula for Terminal and En Route Pay Setting by Facility | |
| 5 Appendix A of the Mediation to Finality process adopted by the Federal Aviation Administration and the National Air Traffic Controllers Association, "Air Traffic Control Complexity Formula for Terminal and En Route Pay Setting by Facility," May 12, 2009, URL: http://nwp.natca.net/Documents/Arbitration_Award.pdf [cited: 2/25/2013]. | |
| FAA Aviation Forecasts Fiscal Years 1979-1990. Federal Aviation Administration, Office of Aviation Policy, 800 Independence Avenue, S.W., Washington, D.C. 20591. September 1978. 92p | |
| 10.1177/004728757901800127 | |
| cited: 2/25/2013 | |
| Journal of Travel Research | |
| Journal of Travel Research | |
| 0047-2875 | |
| 1552-6763 | |
| 18 | |
| 1 | |
| SAGE Publications | |
| Federal Aviation Administration | |
| 6 Federal Aviation Administration, "Terminal Area Forecast Summary Fiscal Years 2011-2040," URL: http://www.faa.gov/about/office_org/headquarters_offices/apl/aviation_forecasts/taf_reports/media/TAF_summary_report_FY20 112040.pdf [cited: 2/25/2013]. | |
| Runway Safety | |
| KimCardosi | |
| StephanieChase | |
| DanielleEon | |
| 10.2514/atcq.18.3.303 | |
| cited: 2/25/2013 | |
| Air Traffic Control Quarterly | |
| Air Traffic Control Quarterly | |
| 1064-3818 | |
| 2472-5757 | |
| 18 | |
| 3 | |
| 2010 | |
| American Institute of Aeronautics and Astronautics (AIAA) | |
| 7 Federal Aviation Administration Air Traffic Organization, "Annual Runway Safety Report 2010," URL: http://www.faa.gov/airports/runway_safety/news/publications/media/Annual_Runway_Safety_Report_2010.pdf [cited: 2/25/2013]. | |
| Distributing net-enabled federal aviation administration (FAA) weather data | |
| MarkSimons | |
| 10.1109/icnsurv.2008.4559189 | |
| cited: 2/25/2013 | |
| 2008 Integrated Communications, Navigation and Surveillance Conference | |
| IEEE | |
| 8 Federal Aviation Administration, "Low Cost Ground Surveillance (LCGS)," URL: http://www.faa.gov/about/office_org/headquarters_offices/ang/offices/ac_td/td/projects/lcgs/ [cited: 2/25/2013]. | |
| Comparing European ATM master plan and the NextGen implementation plan | |
| DavidBatchelor | |
| 10.1109/icnsurv.2015.7121357 | |
| cited: 2/25/2013 | |
| 2015 Integrated Communication, Navigation and Surveillance Conference (ICNS) | |
| IEEE | |
| March 2012 | |
| NextGen Implementation Plan | |
| 9 Federal Aviation Administration, "NextGen Implementation Plan," March 2012, URL: http://www.faa.gov/nextgen/implementation/media/NextGen_Implementation_Plan_2012.pdf [cited: 2/25/2013]. | |
| Characterization of Days Based on Analysis of National Airspace System Performance Metrics | |
| GanoChatterji | |
| BassamMusaffar | |
| 10.2514/6.2007-6449 | |
| AIAA Guidance, Navigation and Control Conference and Exhibit | |
| Hilton Head, South Carolina | |
| American Institute of Aeronautics and Astronautics | |
| Aug. 20-23, 2007 | |
| AIAA-2007-6449 | |
| 10 Chatterji, G. B., and Musaffar, B., "Characterization of Days Based on Analysis of National Airspace System Performance Metrics," AIAA-2007-6449, Proceedings of AIAA Guidance, Navigation and Control Conference and Exhibit, Hilton Head, South Carolina, Aug. 20-23, 2007. | |
| Automating the Process of Terminal Area Node-Link Model Generation | |
| Hak-TaeLee | |
| ThomasRomer | |
| 10.2514/6.2008-7101 | |
| AIAA Modeling and Simulation Technologies Conference and Exhibit | |
| Honolulu, Hawaii | |
| American Institute of Aeronautics and Astronautics | |
| August 18-21, 2008 | |
| 12 | |
| AIAA 2008-7101 | |
| Lee, H., and Romer, T. F., "Automating the Process of Terminal Area Node-Link Model Generation," AIAA 2008-7101, Proc. AIAA Modeling and Simulation Technologies Conference and Exhibit, Honolulu, Hawaii, August 18-21, 2008. 12 | |
| Characterization of Tactical Departure Scheduling in the National Airspace System | |
| RichardCapps | |
| ShawnEngelland | |
| 10.2514/6.2011-6835 | |
| 11th AIAA Aviation Technology, Integration, and Operations (ATIO) Conference | |
| Virginia Beach, VA | |
| American Institute of Aeronautics and Astronautics | |
| September 20-22, 2011 | |
| AIAA 2011-6835 | |
| Capps A., and Engelland, S. A., "Characterization of Tactical Departure Scheduling in the National Airspace System," AIAA 2011-6835, Proc. AIAA Aviation Technology, Integration and Operations Conference (ATIO), Virginia Beach, VA, September 20-22, 2011. | |