Modern Air Traffic Control increasingly relies on Time-Based Metering (TBM) to manage the flow of arriving aircraft into busy terminal environments. Rather than vectoring every airplane with radar instructions, TBM assigns each flight a precise time at which it must cross a specific metering fix. The onboard Flight Management System (FMS) makes this possible through its Required Time of Arrival (RTA) function — a sophisticated speed-management tool that schedules the aircraft to arrive at a waypoint within seconds of the assigned time. For ATP candidates and professional crew members alike, understanding RTA and TBM is essential to operating competently in high-density airspace.
RTA is sometimes confused with a simple Estimated Time of Arrival (ETA), but the two are fundamentally different. An ETA is a passive prediction based on current trajectory; the RTA is an active constraint that the FMS continuously works to satisfy by modulating thrust and pitch to adjust ground speed. This distinction shapes how crews interact with the automation and how ATC expects the aircraft to perform.
How Time-Based Metering Works
TBM is an ATC flow-control strategy implemented at facilities equipped with scheduling tools such as TBFM (Time-Based Flow Management), which is the FAA system that assigns Scheduled Times of Arrival (STAs). When a flight is metered, ATC issues a Controlled Time of Arrival (CTA) — sometimes called a metering fix time — requiring the aircraft to cross a specific fix at a specified UTC time. The pilot then enters that time into the FMS as an RTA constraint on the appropriate waypoint.
Once an RTA is entered, the FMS performs a continuous four-dimensional calculation: lateral path, vertical profile, speed schedule, and time. It determines whether the aircraft is early or late relative to the required time and computes the speed adjustments needed to correct the discrepancy. The FMS commands speeds within the aircraft's performance envelope — respecting Mach/airspeed limits, buffet margins, and structural limits — while factoring in the cost index, a pilot- or dispatcher-entered economic parameter that weights the normal speed schedule between minimum fuel and minimum time, to gradually absorb the time error without abrupt changes. The result is a smooth, fuel-efficient speed management solution.
The RTA Speed Window
The FMS can only satisfy an RTA if the required fix can be reached within the aircraft's achievable speed range given the remaining distance and winds. The system computes an RTA speed window: a minimum achievable time (flying at max speed) and a maximum achievable time (flying at minimum speed). If the assigned CTA falls within this window, the FMS displays the constraint as achievable and begins speed management. If the CTA falls outside the window — meaning it is impossible to go fast enough or slow enough — the FMS flags the constraint as unachievable and the crew must inform ATC. In practice, dispatchers and ATC coordinators try to assign CTAs that fall within reasonable bounds, but winds aloft can change the window significantly in cruise.
The FMS typically displays the RTA-managed speed as a cyan or magenta value (depending on manufacturer) in the cruise or descent speed window, and it revises the speed command every few seconds. On many Boeing and Airbus platforms, the RTA function is accessed through a dedicated page on the MCDU or CDU. Pilots confirm the RTA waypoint, enter the UTC time, and verify that the system shows the constraint as feasible before accepting the clearance.
Why It Matters Operationally
TBM significantly reduces the need for radar vectoring and holding, which saves fuel and reduces crew workload during the descent and approach phase. When an entire stream of aircraft is properly metered, runways operate closer to their true capacity without the traditional buffer of holding patterns. For the crew, the practical benefit is a more predictable descent profile — often enabling a Continuous Descent Arrival (CDA) or Optimized Profile Descent (OPD), both of which reduce fuel burn, noise, and emissions compared to step-down approaches.
From a safety standpoint, RTA imposes a discipline on speed management that requires crew awareness. If the FMS is commanding an unusually high or low speed to meet an RTA, pilots must recognize this and cross-check that the commanded speed remains within operational limits. An FMS that has lost accurate wind data, for example, may command a speed that achieves the RTA mathematically but is inappropriate for the phase of flight. Crew monitoring and intervention are irreplaceable.
TBM is also a key enabler of Performance-Based Navigation (PBN) and NextGen initiatives. As the National Airspace System evolves toward trajectory-based operations, the ability for aircraft to self-sequence using onboard FMS tools reduces the voice-communication burden on ATC and improves overall system efficiency. Airlines that participate in TBM programs frequently report fuel savings on the order of hundreds of pounds per flight in high-density corridors, aggregating to significant fleet-wide benefits.
Key Numbers and Rules
- RTA accuracy tolerance: RTA accuracy is not a single FAA-published numeric standard; it varies by FMS manufacturer and software version. Commonly cited figures in avionics documentation range from about ±30 seconds to tighter tolerances on advanced implementations, but crews should reference their specific FMS manufacturer documentation rather than a fixed FAA requirement.
- Entry format: The RTA is entered as a UTC time (HH:MM:SS) on the FMS flight plan or RTA page; pilots must verify the correct waypoint is constrained.
- Speed range: The FMS respects all applicable speed limits — VMO/MMO, minimum maneuvering speed, and flap placard speeds — while managing an RTA. Separately, regulatory speed restrictions such as the 250-knot limit below 10,000 feet MSL (14 CFR 91.117) apply regardless of any RTA constraint and are not something the RTA logic itself manages.
- Unachievable RTA: When the FMS flags an RTA as unachievable (typically shown as amber or with an advisory message), crews must promptly notify ATC so a revised CTA can be issued.
- CTA vs. RTA: The CTA is the ATC-assigned constraint; the RTA is the pilot-entered FMS value that implements the CTA. They should match.
- Fuel impact: Flying faster to meet an early CTA increases fuel burn; the crew and dispatcher should assess fuel reserves before accepting an RTA that requires prolonged high-speed flight.
- FMS wind updating: Accurate RTA management depends on current wind data. Pilots should update winds aloft — from ACARS, datalink, or manual entry — during cruise and descent to ensure the FMS time prediction remains accurate.
Common Test Traps
- Confusing RTA with ETA: An ETA is a passive prediction; an RTA actively commands speed to meet a time constraint. Examiners test whether candidates understand the FMS is doing work, not just calculating.
- Assuming unlimited speed authority: The FMS will not exceed VMO/MMO or descend below minimum maneuvering speed to meet an RTA. If those limits are reached, the time constraint simply goes unmet and must be flagged. The FMS does not override safety limits.
- Ignoring the unachievable flag: Candidates sometimes state they would simply accept whatever the FMS shows. The correct answer is to notify ATC when the FMS flags an RTA as unachievable — this is a crew responsibility, not an automation responsibility.
- Wind data complacency: Stale winds in the FMS can cause the RTA speed to diverge from what is actually needed. Regularly updating wind data is part of proper FMS management during RTA operations.
- Omitting the fuel check: Accepting an RTA that requires high-speed flight without checking fuel reserves is an operational error. ATP-level decision making requires integrating time constraints with fuel management, not treating them as independent.