13.07.2014 Views

Trajectory-Based Operations (TBO) - Joint Planning and ...

Trajectory-Based Operations (TBO) - Joint Planning and ...

Trajectory-Based Operations (TBO) - Joint Planning and ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Trajectory</strong>-<strong>Based</strong> <strong>Operations</strong> (<strong>TBO</strong>)<br />

Study Team Report<br />

Recommendation <strong>TBO</strong>-32<br />

Modify OI-0333 <strong>and</strong> OI-0335 to add <strong>TBO</strong> content <strong>and</strong> set the targeted distances for 2025 that are<br />

identified down to 750 feet. Add information on how spacing between aircraft is set up by <strong>TBO</strong> <strong>and</strong><br />

how <strong>TBO</strong> is used to maintain separation on dependent parallels. Independent parallel runway<br />

operations are aided by merging <strong>and</strong> spacing from TOD to roll out onto the independent approach.<br />

Missing are the dimensions for VCSPR, establishing goals for the operations. There should be an<br />

incremental activity to first reach 2,500 feet, then 1,200 feet, <strong>and</strong> finally 750 feet of runway separation<br />

distances.<br />

OI-0333 recommended changes would read:<br />

The improvement will explore concepts to recover lost capacity through reduced<br />

separation st<strong>and</strong>ards, increased applications of dependent <strong>and</strong> independent operations,<br />

enabled operations in lower visibility conditions, <strong>and</strong> changes in separation responsibility<br />

between the ATC <strong>and</strong> the flight deck. This OI sets a goal of achieving independent<br />

parallel arrivals down to 2,500 feet separation <strong>and</strong> dependent parallel arrivals to 750 feet.<br />

This improvement will develop improved procedures that enable operations for closely<br />

spaced parallel runways (runways spaced less than 4,300 feet laterally) in lower visibility<br />

conditions. This operational improvement promotes a coordinated implementation of<br />

policies, technologies, st<strong>and</strong>ards, <strong>and</strong> procedures to meet the requirement for increased<br />

capacity while meeting safety, security, <strong>and</strong> environmental goals. Intermediate concepts<br />

for maintaining access to parallel runways continue to be explored (e.g., use of RNP<br />

approaches to define parallel approaches with adequate spacing, RNP transition to an ILS<br />

final approach course, RNP/LAAS/WAAS, Wake Program Office initiatives). Research<br />

will be initiated to support far-term capacity requirements. Research will be focused on<br />

finding ways to recover lost capacity due to IMC events by providing a monitoring<br />

capability that mimics or replaces visual separation. VMC-like capacity may be achieved<br />

by integrating new aircraft technologies such as ADS-B In, precision navigation, data<br />

link <strong>and</strong> cockpit displays within the <strong>TBO</strong> capabilities.<br />

This OI seeks VMC arrival <strong>and</strong> departure rates in IMC through use of onboard displays<br />

<strong>and</strong> alerting for independent parallel runways. Using precision navigation, cooperative<br />

surveillance, <strong>and</strong> onboard algorithms <strong>and</strong> displays allows the reduction of lateral<br />

separation requirements for parallel runway operations in IMC <strong>and</strong> limited by wake<br />

vortex separation distances. This OI includes independent approaches to parallel runways<br />

with centerline distances as low as 2,500 feet. The implementation of this OI is strongly<br />

dependent on when an airline decides this is important <strong>and</strong> steps forward to advocate for<br />

it.<br />

18.20 Connecting Top of Descent to STARs <strong>and</strong> Connecting STARs to Approaches<br />

During the transition to <strong>TBO</strong> (between TOps <strong>and</strong> <strong>TBO</strong>), there is a need to build closed trajectories. To<br />

calculate an OPD, the aircraft needs to know how long its path is from TOD to the runway threshold.<br />

This path is then converted to a profile that represents what the aircraft will fly. Connecting STARs to<br />

approaches eliminates vectoring into an open trajectory. Since the aircraft will know where its TOD is<br />

likely to be, a closed trajectory to the start of a STAR can be provided to the aircraft in advance of the<br />

TOD, <strong>and</strong> the aircraft can then provide its flight profile.<br />

<strong>Joint</strong> <strong>Planning</strong> <strong>and</strong> Development Office<br />

105

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!