En-Route Automation Modernization (ERAM) trajectory model evolution to support trajectory-based operations (TBO)

• Kinetic capability in ERAM would provide significant descent model accuracy improvement in cases where flight-specific aircraft intent and parameters are available • Aircraft intent is expected to become increasingly available with Data Comm and SWIM. • Kinetic models do not automatically guarantee more accurate trajectories in all cases (viz. when aircraft intent is not available) • Need for kinetic capability driven, in part, by TBO concepts that expect ground automation modeling to be compatible with FMS guidance trajectories • Kinetic capability in ERAM would improve ERAM interoperability with other decision support tools (e.g., the U.S. Time Based Flow Management system) • This would be a step toward resolving one challenge to achieving TBO identified in Cate (2013) • A low risk approach to evolving the ERAM trajectory model is to initially use a hybrid parametric-kinetic model: • The Aircraft Trajectory uses the kinetic capability when better performance is expected (e.g., when flight-specific intent is available); • At least initially, the Flight Plan Trajectory continues using the parametric model.