Steve Creamer

1
AT BriefingDRVSM Overview

• Steve Creamer
• AT DRVSM Program Manager, ATP-6

2
Briefing Overview

• Program Objectives, Content and Priority
• Issues and Implementation Plan
• Training, Outreach and Preparation
• Main Points
• System-wide impact and implementation
• Benefits-driven
• Schedule-focused deliverables

3
Reduced Vertical Separation Minimum

• 1,000 ft vertical separation applied globally,
  including domestic US, up to FL 290 for past 40
  years
• Special provisions of RVSM program enable
  reduction of vertical separation from 2,000 ft to
  
• 1,000 ft. between FL 290 - FL 410 (inclusive)

4
RVSM Mandate

• When implemented, RVSM approval required for
  operation in designated airspace, with limited
  exceptions

5
DRVSM Program Objectives

• Implement DRVSM from FL290-FL410 in the airspace
  of the United States, Alaska, the Gulf of Mexico
  where the FAA provides air traffic services and
  possibly the San Juan FIR.
• The United States, Canada, and Mexico are
  planning a joint implementation of RVSM.
• DRVSM is proposed to be implemented on
• January 20, 2005 0901UTC.

6
DRVSM Environment

• Creates six additional altitudes from FL 290
  through FL 410 by the reduction of vertical
  separation from 2000 ft. to 1000 ft.
• Airspace will be exclusionary for DRVSM approved
  aircraft with the exception of accommodating DoD
  and Lifeguard aircraft.
• Non-DRVSM approved aircraft may transition
  through DRVSM airspace.

7
Major Program Elements

• Aircraft and operators authorized by
  Administrator or for non-US operators/aircraft,
  the appropriate foreign authority
• Aircraft altimetry, auto-pilot, altitude alert
  systems modified to RVSM standards
• RVSM policy/procedures incorporated into
  controller, pilot and dispatch programs
• Air Traffic systems and programs revised

8
Program Elements (cont.)

• Monitoring in-service aircraft
  altitude-keeping observed to confirm performance
  standards are being met
• Ground and airborne monitoring systems used to
  independently monitor aircraft performance
• Safety Analysis based on accepted Collision
  Risk Modeling practices

9
Rule Schedule

• May 10, 2002.NPRM published
• Aug 8, 2002formal comment period closed
• Jun 03 timeframe.publish final rule.
• Coordinating with other government agencies to
  publish as soon as possible.

10
Benefits 2004 - 2018

• Fuel Savings and Operating Efficiency Benefits
  2005 2019
• 5 billion
• 6/1 benefit/cost ratio
• 359 m. first year savings---2.0 annual increase
• Benefits to air traffic operations
• ATC Flexibility
• Mitigate conflict points
• Enhance sector throughput
• Reduce controller workloade.g., reduce vectoring

11
Operator Costs 2002 - 2016

• Operator Costs for Aircraft Approval
• Large Transport Aircraft 206 million
• Small Commercial/GA 530 million
• Downtime if work not accomplished
• during scheduled Mx 74 million
• TCAS II, Version 7.0 upgrade 46 million
• Monitoring 4 million
• Major operators started RVSM work in 2002

12
NAS Operational Evolution Plan

• DRVSM is para ER-4 in NAS OEP
• Principle Office of Delivery (POD)
• Director, Flight Standards Service AFS-1
• www.faa.gov/programs/oep

13
Implementation Date Factors

• 4,000 aircraft (30) already approved
• New airframes now delivered RVSM ready
• Project 90 of flights to be conducted by RVSM
  approved aircraft by January 2005 timeframe
• 359 m. first year fuel savings and ATM benefits
  at stake
• Aircraft Engineering Packages available for most
  aircraft
• Non-group/unique airframe process available

14
Memorandum of UnderstandingFAA and DoD

• Memorandum of Understanding signed between FAA
  and DoD in December 2001.
• Agreement governs the use of DRVSM Airspace by
  DoD aircraft.
• Policy The FAA will accommodate non-compliant
  DoD aircraft operation within DRVSM airspace.

15
Major Milestones

• Kick-off Meeting September 2000
• User Meetings Feb May 2001
• ATC First Simulation October 2001
• DoD MOU December 2001
• First DRVSM Seminar April 2002
• Publish NPRM May 2002
• Second ATC Simulation June 2002
• Second DRVSM Seminar September 2002
• Mexico Coordination Meeting November 2002
• Canada Coordination Meeting January 2003

16
DRVSM Human-in-the-Loop (HITL) Simulation

• The first HITL simulation was completed in
  October 2001.
• Objectives
• Identify impact of DRVSM on en route controller.
• Workload
• Complexity
• Potential for error

17
DRVSM Human-in-the-Loop (HITL) Simulation (cont.)

• Compare impact of DRVSM in three altitude bands
• FL350-FL390
• FL330-FL390
• FL290-FL410
• Comparison of conventional separation to three
  altitude bands above.
• Identify ATC procedural implications.
• Results
• DRVSM from FL290 to FL410 yielded superior
  results.

18
DRVSM Simulation (cont.)

• The Second HITL Simulation was completed in June
  2002 and focused on
• Non-DRVSM Approved Aircraft in DRVSM Airspace
• Non-DRVSM Approved Aircraft transitioning through
  DRVSM Airspace
• Outage of DRVSM Equipment
• Tactical use of DRVSM
• Results Non-DRVSM Approved Aircraft.
  (transitioning, DoD, Lifeguard) increased
  workload, complexity and potential for error.

19
Separation Applied Between Non-RVSM and RVSM
Aircraft Within RVSM Airspace
RVSM approved aircraft
FL 390
X
FL 380
Non-RVSM approved DoD aircraft
FL 370
X
FL 360
RVSM approved aircraft
FL 350
RVSM approved aircraft
FL 340
RVSM approved aircraft
FL 330
20
Major Milestones

• Third Simulation June 2003
• Publish Final Rule June 2003
• Safety Assessment July 2004
• Operational Readiness September 2004
• Assessment (Go/Delay)
• RVSM Implementation January 2005

21
Full Data Block Non-RVSM
N4215Y 347 056 380
22
NAS Automation Modifications

• Automation modifications to the Operational Error
  Detection Patch, (Conflict Alert) to accommodate
  DRVSM.
• Automation modifications in progress to support
  the visual cue for the controller display to
  enable a ready distinction between RVSM approved
  and non-RVSM approved aircraft. Note The
  visual cue will be applied to non-RVSM aircraft
  because it is anticipated that they will comprise
  less than 5-10 of the flights operating at RVSM
  altitudes.

23
ATC Procedures Workgroup

• Certified Professional Controllers participated
  in an ATC procedures workgroup March 4-6, 2003.
• Validate Procedures in Third Simulation.
• Coordination with industry of proposed
  new/revised procedures will be through the DCP
  process.

24
ATC Procedural Issues

• The following items could require new procedures
  to support DRVSM
• Routine RVSM procedures to manage RVSM airspace.
• Process to climb/descend non-RVSM aircraft
  through RVSM airspace.
• Accommodation of DoD, State and Lifeguard
  aircraft.
• Coordination responsibilities, i.e. point outs
  between sector stratas.

25
ATC Procedural Issues cont.

• Contingency Procedures
• Suspension of RVSM for turbulence
• Mountain wave
• Wake turbulence
• Weather deviation i.e. thunderstorms
• Air Traffic Flow Management procedural needs

26
DRVSM Simulation 3

• The third HITL Simulation scheduled for June 2003
  will focus on
• Assessing and validating proposed DRVSM
  Procedures and phraseology.
• Additional review of tactical application of
  DRVSM.
• Reviewing training considerations associated with
  DRVSM.
• Assessing of any remaining areas of concern.

27
Mountain Wave Activity

• A study has being conducted on Mountain Wave to
  assess its impact on DRVSM.
• The MWA study, field input and a review of
  current operational practices will be part of an
  assessment of this phenomenon for procedural
  consideration.

28
System Integration

• Develop a test and implementation plan.
• Seamless Integration of DRVSM within the NAS
• Coordination with other programs such as URET and
  airspace redesign, etc.

29
RVSM Implemented PlannedAs of April 2003
Canada North 4/02
Canada South 1/05
Europe 1/02
Domestic US 1/05
NAT 3/97
Mid East 11/03
Pacific 2/00
Pacific 2/00
EUR/SAM Corridor 1/02
WATRS 11/01
Western Pacific South China Sea 2/02
Asia/Europe South of Himalayas 11/ 03
CAR/SAM 2005
Australia 11/01
Western Pacific/South China Sea February
2002 Implementation
Bangkok, Ho Chi Minh, Kota
Kinabalu, Kuala Lumpur, Manila, Phnom Penh,
Sanya, Singapore, Taipei October 2002
Implementation
Hanoi, Hong Kong, Jakarta,
Ujung Pandang, Vientiane
Implemented
Planned
V. 6.8 5-23-02
30
Joint Implementation with Mexico, Canada and
Others

• Preparedness of Mexico, Canada, and the United
  States for a simultaneous implementation of RVSM.
• Procedural development for bordering ATC
  facilities.
• Consistency of training for RVSM among our three
  countries.

31
Tactical Application of RVSM

• Tactical RVSM has been applied in other
  countries.
• The second HITL Simulation provided an initial
  examination of tactical application of RVSM.
• The results were inconclusive but it appeared
  that under peak traffic conditions it becomes
  difficult to use RVSM tactically.
• The third HITL Simulation will further examine
  the use of RVSM tactically.

32
FAA HQ Deliverables (1)

• International Agreements with Mexico, Canada and
  Caribbean States
• National Procedures, Order Changes and Briefing
  Guides
• NAS Automation Changes
• Analysis support within Airspace Redesign for
  sectorization changes

33
FAA HQ Deliverables (2)

• AFTM Flow Plans for Initial Operations
• Non-Approved Aircraft biggest liability
• Flight Planning compression could overload
  sectors
• Training Plan templates
• National CADRE training instruction
• Facilitation of local coordination to prepare for
  implementation (workshops, telecons, templates)

34
FAA HQ Deliverables (3)

• Labor II negotiation
• Funding support for simultaneous national
  training effort
• Any other assistance required to keep program on
  track!

35
Regional Facility Deliverables

• Revisions to Virtually all En Route LOAs and SOPs
• Local validation that all NAS automation changes
  thoroughly tested and properly implemented
• Simultaneous DYSIM Training by CADRE of
  Instructors for over 9,000 controllers
• Local labor II on issues not covered by national
  agreements
• Local coordination with industry within
  established forums
• Leadership to keep program on track!!

36
Conclusion

• FAA committed to successful DRVSM implementation
  in the National Airspace System.
• Flight Standards is OEP Point of Delivery, but
  responsibility and critical path tasks will all
  be AAT in last half of 2004
• Program involves everyone in AAT Regions, ATP,
  ATX, ATA, ATT
• Regional and Field Facility Commitment
  Involvement Key to Successful Implementation

37
More Information
DRVSM Website
www.tc.faa.gov/act-500/niaab/drvsm/Default.asp
or, type DRVSM on Google Search Engine
Airspace Redesign Website
www1.faa.gov/ats/nar/index.html