Federal Aviation Administration Required Communication Performance (RCP) Date:26-30 March 2007...
-
Upload
marissa-macleod -
Category
Documents
-
view
215 -
download
1
Transcript of Federal Aviation Administration Required Communication Performance (RCP) Date:26-30 March 2007...
Federal AviationAdministration
Required Communication Performance (RCP)
Date: 26-30 March 2007
Presented to: ICAO Worldwide Symposium on Performance of the Air Navigation System
By: Tom Kraft, FAA, Aviation SafetyChief Scientific and Technical Advisor (CSTA) for Aeronautical CommunicationsEmail: [email protected]: 202-369-2168
Moving toward a performance-based air transportation system
RCP2Federal Aviation
Administration26-30 March 2007
Overview
• Current situation• A little about RCP• Activities underway• Outlook for implementation
RCP3Federal Aviation
Administration26-30 March 2007
Introduction1995 air traffic data link services
Goals: Reduce separationsReroutesUser preferred trajectoriesExpose data link
Applications: CPDLC, ADS–CTechnology: FANS 1/AAirframe: Boeing 744Equipment: Honeywell
CollinsThales ATM
Comm Services: ARINCSITAINMARSAT
U.S.
New Zealand
FijiFrench Polynesia
UAL
ANZQA
Australia
RCP4Federal Aviation
Administration26-30 March 2007
Introduction2007 air traffic data link services
Pacific Sub–Region benefits from data link• Reduced separations to 50/50 NM and 30/30 NM (trials)• User preferred routes and reroute (trials) for all city pairs in South Pacific• Weather deviations• Automatic position reporting• 80% of the fleet in South Pacific use CPDLC and ADS–C, based on FANS 1/A,
60% in the Central Pacific, and 30% on average in the entire Pacific
North Atlantic Region benefits from data link• In 2004, traffic levels exceeded pre–2001 levels• NAV CANADA has reduced communication costs
to users by 50%• 55% of the fleet use either FMC WPR or FANS 1/A
ADS–C for automatic position reporting
U.S. oceanicairspace boundary
PDC & D–ATIS via ACARS
Europe plans mandate for continental data link services• Partial CPDLC application• ATN services and aircraft
equipage compulsory• Accommodation of FANS 1/A
aircraft voluntary• FANS 1/A aircraft exempt
from ATN aircraft equipage
RCP5Federal Aviation
Administration26-30 March 2007
And then some
• What will we do with
– HF voice
– INMARSAT Aero Classic Satellite Service
• And what about
– Voice communications, e.g., INMARSAT, Iridium
– Data communications, e.g., HF Data Link, Iridium, Swift Broadband, Internet Protocol Suite (IPS)
RCP6Federal Aviation
Administration26-30 March 2007
Operational Requirements
Standards for ADS-C
Harmonize data link services
• Planning & Implementation Regional Groups
– North Atlantic Systems Planning Group
– European Air Navigation Planning Group
Harmonize data link services
RCP is a key element to the convergence process
RTCA/EUROCAE FANS 1/A - ATN Interoperability Standard
Data Link Steering Group (DLSG) andATN Accommodation Drafting Group (ADG)
RCP7Federal Aviation
Administration26-30 March 2007
Continued operational safety
FANS Implementation Group (FIG)
Review operational data and advise based on results• Data link VHF, Satellite, HF data link performance• Satellite voice Security procedures
Informal South Pacific Air Traffic Services Coordinating Group
(ISPACG) FANS Interoperability Team
(FIT)
Informal Pacific Air Traffic Control (ATC) Coordinating Group
(IPACG) FANS Interoperability Team
(FIT)
Asia-PacificNorth Atlantic
Planning and Implementation Regional Groups (including subordinate groups)
FAA - Oceanic Separations Reduction Working Group (OSRWG) Scrutiny Group
RCP8Federal Aviation
Administration26-30 March 2007
Continued operational safety
• Fluctuations in performance levels for commercial satellite services
– Backups and redundancy
– Dissimilar technologies, e.g., Iridium, HF data link, INMARSAT, data/voice
– What are the performance criteria, what needs to be monitored, and what is the decision process
– What about predicted performance?
RCP9Federal Aviation
Administration26-30 March 2007
Standards & guidance material
• ICAO completed standards and guidance material for RCP
– Provisions for RCP in Annex 6 and Annex 11
– Manual on RCP ICAO Doc 9869
• RTCA SC-189/EUROCAE WG-53 completed standards for data link services
– Continental Safety and Performance Standard
– Oceanic Safety and Performance Standard
RCP10Federal Aviation
Administration26-30 March 2007
Performance-based operations
• Balances capability & performance of
– Communications, e.g., DCPC
– Navigation, e.g., RNAV/RNP
– Surveillance, e.g., ADS-C
– Air Traffic Management
• Builds on what we have to improve
What is RNP [x] airspace?What is applying separation using ADS-C?
C
S
N
ATMRNPRCP
RSPRTSP
RCP11Federal Aviation
Administration26-30 March 2007
Performance-based communications
• RCP type specifies communication transaction time, continuity, availability, integrity
• Other operational factors may be relevant, for example
– Messages or phraseology, transaction types, and intended use
– Interactive capability of voice communication
– Air–ground integration capability of data communication
– Performance monitoring and alerting
– Adapting the airspace to changes in performance level
RCP12Federal Aviation
Administration26-30 March 2007
Objectives and benefits
• Promotes a competitive market for aeronautical communication services enabling cost–effective alternatives that meet business needs in a more timely manner
• Provides means to demonstrate communication performance using a variety of acceptable methods in lieu of time consuming data collection and empirical analyses
• Defines “needed” operations based on communication performance levels that are not yet obtainable with current technology
• Enables varying service levels in common airspace to a fleet of aircraft with varying communication capabilities and performances
RCP13Federal Aviation
Administration26-30 March 2007
Applicability
• When a change is implemented in air traffic management (ATM) and/or flight operations
• And the change is predicated on communication performance
• Safety management and monitoring
RCP14Federal Aviation
Administration26-30 March 2007
What it does
• Establishes operational criteria
– Determines capability and performance criteria based on intended operations in oceanic, en route, terminal, and airport domains
– Considers voice and data communications
– Considers global seamless operations
– Specifies RCP type and other relevant operational factors
– Not based on any particular technology
RCP15Federal Aviation
Administration26-30 March 2007
How it is used
• Performance-based criteria is used to
– Determine viability of a particular technology
– Qualify, certify, and approve various parts of an implementation
– Manage performance levels needed to provide a basic level of service and, for eligible operators, higher levels of service
• Real time monitoring and alerting (air and ground)
• Historical monitoring and evaluation
• Adapting the airspace based on the results of monitoring
RCP16Federal Aviation
Administration26-30 March 2007
Candidates for implementation
• Reduced separation minima, new procedures, or increasing airspace capacity that requires a communication capability and performance
• Operating in airspace with a basic level of service and, for eligible operators, with higher levels of service
• Provision and use of air traffic service using non-traditional technology or mixed technologies
• Communication capability installed on aircraft whose performance is suitable for use in some airspace, but not in others
RCP17Federal Aviation
Administration26-30 March 2007
PARC (Who - What)
• Performance-Based Operations Aviation Rulemaking Committee (PARC)
– Operates under the FAA Administrator’s legal authority in accordance with 49 USC 106(p)(5)
– Comprises members from the aviation community at large and FAA
– Provides recommendations to FAA’s Senior Management for action & implementation
– Effective in implementing RNAV/RNP
RCP18Federal Aviation
Administration26-30 March 2007
PARC Communications Working Group
• Roadmaps, etc.– Build consensus among aviation
stakeholders
– Communicate fundamental capabilities
– Assess benefit and investment
– Set metrics to measure success of FAA implementation programs
Roadmap for Performance-Based
Communications
Roadmap for Performance-Based
Communications
IndustryCoordination
Draft
Roadmap forData Link
present — 2025
Final Draft, 25-Jul-06
IndustryCoordination
Draft
Roadmap forData Link
present — 2025
Final Draft, 25-Jul-06
Federal AviationAdministration
RCP19Federal Aviation
Administration26-30 March 2007
Outlook
• Complete industry-coordinated Roadmap for Performance-Based Communications by September 2007
– What are the applications for performance-based communications
– What standards are needed and schedule
– What is the strategy for aircraft type certification, operational approval, and implementation
RCP20Federal Aviation
Administration26-30 March 2007
Outlook
• Develop scenario outlines for implementation of RCP type, considering
– Voice and Data communications to increase capacity
– Oceanic and domestic (en route, terminal area, airport)
– Operating in airspace with a basic level of service and, for eligible operators, with higher levels of service
– Some existing communication capabilities and performance that are suitable only for basic level of service
– Performance monitoring, alerting, based on RCP type, and adaptation
RCP21Federal Aviation
Administration26-30 March 2007
And here we conduct our flight
En Route OceanicTerminal En Route Terminal
TOD
RCP 10/V - Basic
RCP 60/D - IC
RCP 400/V - Basic
RCP 240/D - RHSM
RCP 10/V - Basic
RCP 400/D – IC
RCP 60/D - TAP
SATCOM radio fails
5. Pilot/controller know RCP type, just as they know RNAV/RNP type
6. Pilot/controller operates according to RCP type
7. Pilot/controller receives alerts for communication failures
2. Ground side monitors communication service
3. Eligible Operators file for service level(s)
1. RCP types for service level(s) published in AIPs and charts
4. Air side monitors aircraft system
GES Outag
e
/D - Data/V - VoiceIC – Increased capacityRHSM – Reduced horizontal separation minimaTAP – Tailored Arrival Procedure
Federal AviationAdministrationThank you