June 19, 2013 - RTCA

RTCA Paper No 145-13/PMC-1108
June 19, 2013
TERMS OF REFERENCE
Special Committee (SC) 227
Standards of Navigation Performance
(Revision 2)
REQUESTOR:
Organization
FAA Associate Administrator for Aviation Safety
Person
Ms. Peggy Gilligan
SC LEADERSHIP:
Position Name Affiliation Telephone email
The Boeing
Chair Mr. Dave
425.829.7006 dave.nakamura@boeing.com
Company
Nakamura
DFO Mr. Jarrett Larrow FAA/AIR-130 202.385.4660 jarrett.larrow@faa.gov
Secretary
Need to confirm
BACKGROUND:
Since the 2003 publication of RTCA DO-236B, Minimum Aviation System Performance
Standards: Required Navigation Performance for Area Navigation, and DO-283A, Minimum
Operational Performance Standards for Required Navigation Performance for Area Navigation,
the Federal Aviation Administration (FAA) has utilized these standards to define the system and
functional requirements for aircraft and flight crew enabling PBN operations in the U.S. National
Airspace System (NAS). While these operations provide a significant benefit to the NAS,
lessons learned from PBN implementations, advances in the PBN concept and application at
International Civil Aviation Organization (ICAO), and improved avionics technology date these
standards. For example, further definition and standardization are needed to enable application
of fixed radius transitions, RNP holding, and standardized lateral offsets.
Meanwhile, the US’s NextGen and Europe’s Single European Sky ATM Research (SESAR)
calls for additional navigation functions left partially defined in the 2003 standards. One such
function is aircraft time of arrival control. Initiatives under both NextGen and SESAR are
developing operational concepts requiring revision and enhancements to the 4D navigation
standards of DO-236B. EUROCAE WG-85 has committed to a coordinated effort with SC 227
1

in the development of 4D standards in both RTCA DO-236 and EUROCAE ED-75 that will
support application of trajectory-based airspace.
DELIVERABLES:
Product Description Due Date Change
DO-236 – Minimum
Aviation System
Performance Standards:
Required Navigation
Performance for Area
Navigation
Change 1 to DO-236C
This document will define the
minimum aviation system
performance standards for area
navigation systems operating in an
RNP environment.
This change to the MASPS will
define:
1. The four dimensional (4D)
standards that support both RNP
and trajectory-based operations.
2. A standard for wrong runway
monitoring in support of aviation
safety initiatives.
June 2013
December,
2014*
DO-283 - Minimum
Operational Performance
Standards: Required
Navigation Performance for
Area Navigation
The document will define the 4
dimensional minimum operational
performance standards for
navigation systems intended for
application in a PBN environment.
*Committee intends to make a best effort for earlier completion.
March 2015*
March
2013
SCOPE:
The special committee will develop navigation standards intended for designers, manufacturers,
and installers of avionic equipment; airspace managers and service providers; and the users of
these navigation systems for world-wide operations. The new MASPS will provide guidance for
the development of airspace and operational concepts needed to obtain the benefits of enhanced
navigation capability in the aircraft. The MOPS will provide the minimum set of requirements
needed to demonstrate compliance with the performance and functions in the MASPS while
enabling compliance with the PBN operations envisioned to support NextGen and SESAR. The
MOPS will also be compatible with the upcoming ICAO navigation specification for advanced
RNP, to be published in the update to the ICAO PBN Manual, Document 9613.
ENVISIONED USE OF DELIVERABLE(S)
FAA policy and guidance for PBN, to include aircraft qualification and certification criteria,
along with operational approval guidance, will reference the updated MASPS.
The updated MOPS will become the foundation for a new revision to TSO-C115.
2

SPECIFIC GUIDANCE:
The special committee will work collaboratively to meet the following Terms of Reference:
Describe and revisit functions as necessary to ensure consistent navigation performance
for newly considered operations. These operations should include, but not be limited to,
RF legs, fixed radius transitions, RNP holding, lateral offsets, and time of arrival control.
The special committee will develop accuracy requirements, error budgets, and required
operational characteristics for each phase of flight, as applicable. The description will
be in sufficient detail to ensure standardization of navigation functions at the aircraft
level.
Revisit, as appropriate, lessons learned from the operational implementations of PBN to
develop further definition of the operational concepts embraced in the MASPS and
MOPS. These concepts should include, but not be limited to, RF leg performance, fly-by
fix turn performance, vertical navigation performance, and implementation and
application of temperature compensation.
Develop new criteria by considering existing reference material, including the ICAO
PBN Manual, NextGen Advisory Committee Trajectory Operations task group products,
EUROCAE ED-75B addendum supporting 4D navigation standards, operational safety
enhancements, and changes to navigation sensor standards (e.g. GNSS, SBAS, and
GBAS) since the 2003 publications. The goal is to identify duplicate and contradictory
material and coordinate actions for standardization of requirements for international
applications.
Determine appropriate level of functionality for the MOPS in order to support the needs
of industry and to enable NextGen. Define the consensus baseline performance standard.
Coordinate with SC-214 to ensure consistent definition and use of navigation metrics to
enable advanced data communications services.
Coordinate with SC-186 to ensure proper requirement allocation, as needed, to support
navigation system integration with ADS-B out and ADS-B in applications.
Coordinate with SC-217, as needed, to ensure data standards and database processes
consistent with MASPS and MOPS requirements.
Coordinate with SC-159, as needed, to ensure MASPS RNP requirements provide
greater clarity and guidance for GNSS navigators that will be developed for RNP
applications.
Initial Documentation - the following documents should be made available to this committee:
Documents
RTCA DO-236C
RTCA DO-283A
Intended Use
Review and use as baseline
Review and use as baseline
TERMINATION: Activities of SC-227 will terminate with approval by the PMC of the
committee’s final documents. Any change/extension of a committee’s terms of reference requires
prior PMC approval.
3