The Need for an Integrated PBN Strategy

1
The Need for an Integrated PBN Strategy
By Mark Steinbicker, Manager, AFS-470 U.S.
Member, ICAO PBN Study Group Leo Eldredge,
Manager, AJM-321 U.S. Member, ICAO Navigation
Systems Panel
2
U.S. PBN Operations
Terminal (Departures and Arrivals)
En Route
Approach
Oceanic/Remote
Current
RNAV 1 DP/SID and STAR
RNAV 2 Q and T/Tango Routes
RNP AR RNAV (RNP)
RNP 10
RNP 1 DP/SID and STAR With optional curved paths
RNP Approach RNAV (GPS) (LNAV to LPV-200)
RNP 4
Future ?
RNP Authorization Required (AR)
RNAV / RNP 1 / 2 Routes
Advanced-RNP
RNAV / RNP 1 / 2 Routes
Advanced-RNP Routes
Advanced-RNP
Advanced-RNP
3
PBN Strategy Considerations

• Operational Approval
• RNAV, RNP, ADS-B, and Radar as enablers of
  separation
• International harmonization (Australia, UK,
  Europe, Canada) and ICAO
• Operational approval process, procedures
  development, training
• Charting/naming schema
• Flight plan descriptors/elements for PBN
• Overall workload and coordination between
  multiple lines of business
• Navigation Enablers
• Decisions regarding backup strategy for PBN
  (e.g., DME/DME)
• VOR minimum operating network (MON)
• Dual independent navigation system equipage
  impact on Nav Services
• Automation Tools
• ATM / ATC tools to leverage aircraft capabilities
  and procedure designs
• ATM / ATC tools to enable Trajectory Based
  Operations (TBO)
• Aircraft Equipage
• Users look to FAA strategy documents for equipage
  investment decisions
• Operator investment in new technology contingent
  on significant benefits
• Potential need for new airworthiness standards
  and manufacturer support

4
NextGen Mid-Term ConOps

• RNAV or RNP precision and flexibility permits
  multiple arrival and departure paths associated
  with a single runway.
• Expanded use of RNAV or RNP approaches,
  particularly at high density airports, provides
  efficient use of runways and airspace.
• Integrated arrival/departure service, expanded
  use of 3-mile separation standards, dynamic
  airspace reconfiguration enable the creation of
  additional RNAV or RNP arrival and departure
  routes.
• At low to moderate density airports, additional
  RNAV arrival and departure routes support
  increases in operational efficiency..
• RNAV or RNP is required in certain high altitude
  airspace and on certain routes.
• IFR Cruise between FL180 and FL340 requires a
  specific navigational performance provided by
  RNAV or RNP
• Trajectory-based operations are implemented,
  allowing aircraft to fly 4DT trajectory-based
  flight plans.
• RNAV Q-Routes above FL180 and T-Routes below
  FL180 will be in use
• Trajectories have navigation performance
  standards for lateral navigation performance for
  RNAV or RNP
• ADS-B in the Gulf of Mexico allows capacity to be
  doubled by separation reductions enabled by use
  of RNAV or RNP routes and ADS-B.

5
What are the Requirements ?

• Operational Requirements for 2025
• 3 or 5nm separation en route, 3nm or less
  terminal?
• Transition routes, airways, and procedures to
  PBN?
• Functional Requirements
• RNAV Q/T Routes based on RNAV-2 (PBN Roadmap) ?
• RNP-2.0 for Enroute Airspace (PBN Roadmap) ?
• RNP-1.0 or RNAV-1.0 in Terminal Airspace (PBN
  Roadmap) ?
• RNAV(RNP) approaches where beneficial (PBN
  Roadmap) ?
• RNAV(GPS) approaches at all qualifying runways
  (WAAS Program)
• Rationalize conventional navigation
  infrastructure
• Disestablishment of unneeded costly infrastructure

6
PBN Transition
Strategy ?
En Route
Terminal
RNP / OAPM Metro-Plex
New RNAV/RNP - DPs/STARs, - OPDs - RNAV OTG -
TBOs ?
RNAV Q/T Routes ?
Open Skies ?
New Q/T Routes?
J/V Overlays?
Approach
Hybrid Open Skies gt FL?? Q/T lt FL??
RNAV(RNP)
RNAV(GPS)
- Public/AR RF-Legs - SPIA - CSPO
- LPV/LP - Public RF-Legs - SPIA, CSPO
WAAS LPV Production
7
En Route PBN Transition Options

• 1- Attrition-based reduction of VORs to the MON
• When facilities fail, NOTAM them out
• Aircraft use RNAV substitution until PBN routes
  are available
• Transition J/V routes and procedures to Q/T
  gradually
• 2 - PBN transition phased in by block altitudes
• Q-routes above gtFL290, then gtFL180, then all
  T-Routes
• Overlay existing or design new routes
• 3 - Hard cutover by a preplanned transition date
• Transition all enroute airspace all at once after
  new routes and procedures are developed, training
  completed, etc.
• Similar to RVSM transition for all airspace

8
Navigation Transition Considerations

• Dual Independent Navigation System Equipage
  Requirement
• Will RNAV Q/T Routes be based on GPS/WAAS, DDI,
  or DD?
• Will RNP operations for enroute/terminal require
  a backup?
• Or, accept reversion from RNP to RNAV during RFI
  events?
• Handle potential loss of separation procedurally?
   
• Or will DME/DME/IRU and DME/DME be approved for
  RNP ?
• Integrity issue will likely require Ground and
  Avionics changes
• What are the minimum equipage percentages
  required?
• Does Air traffic need 80-90 participation in
  busy airspace

9
National Strategy Needed to Address NAS-Wide and
Location-Specific PBN Needs Requirements
Terminal En Route Approach
NAS-Level Transition RNAV Everywhere VOR-based DP/STAR To RNAV DP/STAR Jet and Victor routes To RNAV Q/T Routes VOR/NDB Approaches To RNP Approach RNAV(GPS)
Highly tailored PBN RNP Where Beneficial RNAV 1 DP/STAR OAPM TA RNP 1 with RF RNAV Q-Routes RNP routes RNP AR Approach RNAV(RNP)
Idea
In-Service
10
PBN Implementation Processes
Internal and External Communication

• Operational Impact Assessment (Cost/Benefits
  Case)
• User Benefits
• Service Provider Benefits
• RNAV Every Where Comprehensive Business Case
• RNP Where Beneficial Procedure Specific
  Business Case
• Benefits Monitoring
• ATC Modernization Dependencies
• ERAM
• ADS-B
• Terminal Automation Tools
• Enroute Automation Tools
• Common 5-Phase for all PBN
• Tailored for integration complexity, compliance
  with standards, national initiatives, etc.
• Airspace
• Environmental
• Survey
• Coordination
• Procedure Design Steps, Tools, and Automation
• 18 Step Process

Nav Lean
OAPM Lessons
11
Recommendations

• PBN Strategy Form a Capture Team to develop
  roadmap-like Operational Capability
  Implementation Plan (OCIP) document that
  addresses requirements, justification, metrics,
  execution strategy and other considerations for
  all domestic phases of flight, types of airspace,
  and stakeholders ANG to facilitate
• PBN Backup Strategy Initiate/continue work
  regarding DME for RNP operations, DME
  rationalization, GPS outage studies for terminal
  and en route operations, and VOR spacing for
  minimum network ANG, ATO, and AVS
• PBN Processes Draft Order that incorporates
  lessons learned, leverages Nav Lean and other
  relevant efforts, streamlines Safety Risk
  Management, and describes a standardized
  development process for new and ongoing
  implementations of each type of domestic PBN
  operation AJV
• PBN Naming/Charting Task U.S. IFPP to develop
  schema in coordination with the Aeronautical
  Charting Forum (ACF) and Performance Based
  Operations Aviation Rulemaking Committee (PARC)
  AJV and AFS
• PBN Program Management and Strategic
  Communications Assign responsibility for PBN
  portfolio management to a single office, which
  will function as a hub with ANG, AVS, AOC, and
  other relevant strategy execution offices AJV
  and ANG
• ATC/ATM Automation and Separation Standards
  Identify gaps in tools and separation standards
  (in coordination with Greener Skies and similar
  efforts) necessary for implementing certain PBN
  operations and enhancing PBN benefits in the
  near- and mid-term ANG and ATO

12
ADS-B Mandate
ROUTES PROCEDURES

CY12
CY13
CY14
CY15
CY16
CY17
CY18
CY20
CY19
CY21
CY22
CY23
CY24
CY25




GNSS Navigation Avionics Equipage Mandate?
RNP Approach LNAV, LNAV/VNAV, LP, LPV
APPROACH
RNP AR Approach (1.0nm 0.1nm)
Advanced-RNP (2.0 0.3nm) RF Required
SID / DP / STAR RNAV 1 (1.0nm) RF Not Available
SID / DP STAR RNP 1 (1.0nm) RF Optional
TERMINAL
SID / DP / STAR RNP AR (1.0nm 0.1nm)
Advanced-RNP RF Required (2.0 0.3nm)
RNP 0.3 (0.3nm) Helicopter Routes
Advanced-RNP CSPO Mandate for Top XX Airports?
Q-Routes RNAV 1 / 2 ?
T-Routes RNAV 1 / 2 ?
EN ROUTE
RNP Routes No RF-Turns ?
RNP Routes With RF-Turns ?
Advanced-RNP(2.00.3nm) FRT Optional
RNP 10 (10.0nm)
RNP 4 (4.0nm)
OCEANIC
RNP 2 (2.0nm)
Advanced-RNP (2.0nm 0.3nm)
13
LEGACY INFRASTRUCTURE
ADS-B Mandate

CY12
CY13
CY14
CY15
CY16
CY17
CY18
CY20
CY19
CY21
CY22
CY23
CY24
CY25



VOR RATIONALIZATION
MON
VOR
NDB DISESTABLISHMENT
EN ROUTE DME OPTIMIZATION
DME
TERMINAL DME OPTIMIZATION
ILS Category 1 RATIONALIZATION
ILS
ILS Category 3
14
Discussion
15
PBN Activities

1. Develop operational, functional performance
   requirements to satisfy the long term PBN needs
   for NextGen
2. Identify technical, operational, and
   institutional issues and constraints that must be
   addressed in order to achieve the long term needs
   
3. Develop an integrated strategy to achieve the
   long term needs within the constraints while
   mitigating the issues
4. Allocate needs and requirements to acquisition
   and non-acquisiton programs within the FAA
5. Identify activities, dependencies, and
   organizational responsibilities necessary to
   fulfill the long term strategy
6. Develop performance measurement tools to verify
   execution of the PBN Strategy
7. Develop a communications plan to ensure internal
   and external customers and stakeholders are
   informed about the PBN strategy
8. Evaluate work products and status during
   execution and propose mitigations to problems as
   they arise, where required

16
Work Plan

1. Establish CT Charter and terms of reference
2. Develop work plan to complete the specified
   activities
3. Develop Operational Requirements and validation
   plan
4. Develop Functional requirements and allocate to
   systems
5. Develop implementation strategy Business case
   justification
6. Develop communications strategy and metrics
7. Communicate and coordinate work plan activities
   with internal and external stake-holders
   throughout the process
8. Baseline requirements and strategy in OCIP and
   NASEA
9. Establish implementation plans and funding
   agreements with LOBs

17
ADS-B RNAV
3 nm Separation
Navigation
ADS-B Surveillance
Communications ?
Automation ?
RNAV-1/2
NIC/NAC
SSR Backup
GPS Primary
DME/DME Backup
WAM Backup
GPS Primary
SIS
SIS
Ground
Avionics
Avionics
Signal Propagation
FTE
Avionics
FTE
18
ADS-B RNAV
3 nm Separation
Loss of GPS
Navigation
ADS-B Surveillance
Communications ?
Automation ?
RNAV-1/2
NIC/NAC
APNT WAM Alternative
SSR Backup
GPS Primary
DME/DME Backup
WAM Backup
GPS Primary
Climb use VOR
SIS
SIS
VOR MON
Ground
Leverage DME sites for WAM
Avionics
Avionics
Signal Propagation
FTE
Avionics
FTE
19
3 nm Separation
ADS-B and RNP
Navigation
ADS-B Surveillance
Communications ?
Automation ?
RNP-1/2
NIC/NAC
SSR Backup
WAM Backup
GPS Primary
GPS Primary
DME/DME Backup
20
3 nm Separation
ADS-B and RNP
Loss of GPS
Navigation
ADS-B Surveillance
Communications ?
Automation ?
RNP-1/2
NIC/NAC
RNAV-1/2
Revert to RNAV
SSR Backup
WAM Backup
GPS Primary
DME/DME Backup
GPS Primary
DME/DME Backup
Procedural Mitigation
Get ATC Vectors
Climb use VOR
VOR MON
21
Operational Requirements
ORD
NAS EA
ConOps TF-5 ICWG A4A NBAA AOPA RAA
Functional Performance Requirements
NAS RD
Requirements Allocation
PLAs
PLAs
FRDs STDs
Implementation Strategy
NAPP
FRP
NGIP
NSIP
Activity Definition
OCIP
PLAs
PLAs
PLAs
PLAs
RPDs
PLAs