RNP RNAV in Naval Aviation

航空论坛

游客，如果您要查看本帖隐藏内容请回复

航空论坛

RNP RNAV
in
Naval Aviation
25 June 2008
Garth Van Sickle
DCS Corporation
PMA-209
(240) 237-4886
gvansick@dcscorp.com
Frank G. Bushman
DCS Corporation
PMA-209
(240) 237-4826
fbushman@dcscorp.com
UNCLASSIFIED
Bryan M. Strong
Avineon, Inc.
NAVFIG
(202) 685-6063
bryan.strong.ctr@navy.mil
Amish Buggies Are Not Allowed On The Interstate
Minimum Functionality
is a Requirement
Performance
Based Airspace
Ahead
DoD Aircraft
Hang Gliders
UAS
N3241C
+200
VV12345
+300
REACH41
+350
ROMAN52
+850
R223102
+900
SWA452
+700
SD45
+1000
N43865
+500
Extortion Through Exclusion
RNP RNAV* will be required for Civil Airspace
*(and Other Stuff)
The Jump to RNP RNAV
• The Naval Aviation Program for TACAIR
• Defining the Required Performance
• Enablers and Requirements
• The Digital Cockpit
• The Jump to GPS RNAV TERPS
Aircraft
8.33
kHz **
Mode S
with ELS
/ EHS ** RVSM **
RNP
RNAV **
1090ES
ADS-B
(Future
Growth)
EP/P-3 G B B R
KC/C-130T B G R R
C-2A B G G R
E-2C G G G R
EA-6B B B R R
KC-130J B G R R
VH-60N B B R R
H-53 series G G R
MH-60R/S B G R R
F/A-18E/F B G G*** POM 10 R
MV-22B R G R R
A/UH-1Z/Y B G R R
AV-8B B R G*** POM 10 R
F/A-18A+/C/D Y R G*** POM 10 R
CH-46E R R R
T-45C R POM 10 R
CNS/ATM
Tactical Aircraft Compliance*
Capability
Exists
Presently
Noncompliant.
Integration
Underway
Not Applicable
for this aircraft
Some Aircraft Have
Achieved Capability B G Y R
* New development aircraft will be delivered CNS/ATM compliant
** Signed Functional Requirements Document
*** RVSM Certification Underway
What is an FRD?
• How do you achieve a required civil functionality using
military avionics and integrations?
• A Functional Requirements Document (FRD) specifies
the details of a civil functionality so we will be able to
achieve the same capability using military avionics
• Provides the basis for Navy test and evaluation
leading to Navy platform certification of functionality
• Ensures system functional commonality in all aircraft
while using different hardware, software and cockpit
displays
Once the functionality is defined, it can be achieved
• 8.33 kHz Channel Spacing – This FRD defines the functionality required to operate
in European airspace where 8.33 kHz is mandated at high altitudes.
•Mode S – This FRD defines the functionality required to operate in airspace where
Mode S surveillance is being mandated (Europe). This includes both Elementary
(ELS) and Enhanced Surveillance (EHS) requirements.
•RNP RNAV – This FRD defines the functionality required to operate in airspace
where performance based navigation mandates are emerging. It defines the
navigation accuracy, containment, integrity and appropriate alerts to file and
fly from departure through NPA with PPS GPS as the primary positioning
source. The RNP RNAV FRD also covers other navigation performance
requirements (i.e. BRNAV, RNP-10, VNAV, etc).
• RVSM – This FRD defines the functionality required to operate in airspace where
Reduced Vertical Separation Minimums (RVSM) is required. This now includes
almost all the sovereign airspace of the world
Functional Requirements Documents
(FRDs)
GPS UNIQUE CAPABILITIES
• HIGH ACCURACY 3D POSITION
• VELOCITY VECTOR AND TIME
• GLOBAL COVERAGE
• CONTINUOUS AVAILABILITY
• PASSIVE SERVICE
• RESISTANT TO INTERFERENCE AND JAMMING
• UNLIMITED NUMBER OF USERS
• ALLOWS COMMON GRID REFERENCE
– WGS-84
1176 MHz 1227 MHz 1575 MHz
L5 L2 L1
P(Y)
C/A
Present Signals P(Y)
(Block II/IIA/IIR)
2nd Civil Signal
and New Military
Signals
(Block IIR-M)
3rd Civil Signal
(Block IIF)
+ GPS III (streamlined
space and control
segments)
P(Y) P(Y)
3rd Civil
P(Y)
C/A
P(Y)
2nd Civil
M M
1227 MHz 1575 MHz
M
2nd Civil
M C/A
GPS Signal Evolution
Integrity
• INTEGRITY is the ability of a system to provide
timely warnings to users when the system should
not be used for navigation.
• TACAN and VOR have integrity at the source
• Fail integrity; kill the signal
• GPS integrity is in the user equipment
• GPS Control Segment integrity is not timely
• RAIM: Receiver Autonomous Integrity Monitoring
• Fault Detection - 5 Satellites
• Fault Detection Exclusion (FDE) – 6 Satellites
• Other Integrity options (Augmentation Systems)
• Space Based (SBAS = WAAS) Wide Area
• Ground Based (GBAS = LAAS) Local Area
• Aircraft Based (ABAS = Hybrid Integrity)
Why RNP RNAV (IFR GPS)?
• Most Naval Air Stations are equipped with GPS
RNAV or RNP procedures.
• Naval aircraft are equipped with Tactical GPS
but can not use it in civil controlled airspace or
for GPS based RNAV or RNP procedures
because:
• Tactical GPS does not have integrity
– No protected database in aircraft
– Manual entry of approach is prohibited
– No graphic display of the RNAV procedures
(SIDS, STARS, and Approach)
P-3C is certified to fly GPS RNAV procedures
F/A-18, MH-60, MV-22, T-45, AV-8Bs can not fly any GPS based procedure
Required Navigation Performance/
Area Navigation – RNP RNAV
Left Cross-Track Containment Limit
Right Cross-Track Containment Limit
RNP Value
DESIRED PATH
RNP RNAV Navigation (Example RNP 2)
95%
2 X RNP Value
2 X RNP Value
RNP Value
ACTUAL PATH
4 nm
2 nm
RNP RNAV = Flight with PPS GPS to NPA + “Containment”
No Deviations
Total System Integration
Data Base Processing Integrity
Data Integrity
Check Process
Data Transfer Device
CDU
FMS
MC
DAFIF
CD-ROM
NGA
Joint Mission Planning Station
Data Integrity
Check Process
Data Integrity
Check Process
Data Integrity
Check Process
Check Sums
or
CRC*
* CRC – Cyclic Redundancy Check
DTD
JMPS
Mid Term (2011-2015) Far Term (2016-2025)
En Route
• RNP-2 Q Routes
• RNP-1 in selected areas high altitude
• RNAV T Routes
• Lower MEAs on routes based on GPS
Terminal
• RNAV SIDs/STARs at OEP*
Airports NOTAM
• RNP-1 SIDs/STARs where beneficial
• Controller Tools for Merging and
Spacing
Approach
• 25 RNP SAAAR per year
• 300 RNAV (GPS) per year
• Standards for closely spaced
and converging Runway Operations
Based on RNP
En Route
• RNP-2 Routes
• RNAV T Routes and Lower MEAs
• Enhanced automation incorporating
aircraft navigation capabilities
Terminal
• RNP 1 and Lower SIDs/STARs
Where Beneficial
• Airspace Redesign and Procedures
for RNAV and RNP with 3D,
Constant Descent Arrivals (CDA),
and Time of Arrival Control (TOAC).
Approach
• 50+ RNP per year
• 300 RNAV (GPS) per year
• Closely spaced parallel and
converging runway operations
based on RNP
• Satellite Based Low Vis. Ldg. and
T/O Procedures (GLS)
Mandate RNP above
FL290
Mandate RNAV above
FL180
Mandate RNP
everywhere in
CONUS
Explore need for
4D, data link, and
enhanced
surveillance
capability
mandates
Performancebased
NAS
Operations
• RNP Airspace At or
Above FL290
• Separation assurance
through combination of
ground and airborne
capabilities
FAA PBN Roadmap Milestones
* OEP – Operational Evolutionary Plan
Mandate RNAV for arriving
& departing at OEP Airports
Mandate RNP in
busy en route
and terminal
airspace
Near Term (2011-2015)
TACAN Navigation today
Bearing Distance Heading
Indicator (BDHI)
289 deg
300 deg
TACAN
1.4 DME
Arc @ 8 DME
GPS RNAV/LNAV
Approach
RNAV and LNAV
APPROACHES ARE
POINT-TO-POINT
(TO-TO NAV)
BEARING,
DISTANCE,
COURSE, CDI ARE
TO THE NEXT
POINT AND NOT
THE AIRPORT
N
>
CDI
TAMAY
15.0
DTK
215
GPS RNAV/LNAV NPA Displayed
N
>
CDI
TAMAY
15.0
DTK
215
NPA – Non-Precision Approach
CAROM
IAF
3000
215o/15.0
3:00
TAMAY TAMAY
3000
HILER
FAF
2100
RWY30
MAP
880
RNAV (GPS) 30
NSI
TERM
PFD
(Primary Flight Display)
6 x 8 Display Area
Garmin 530
SA Display
PFD
(Primary Flight Display)
9 x 12 Display Area
Back-up Display Back-up Display
2 CDUs
E-2C HE2K CNS/ATM Cockpit
SA – Situation Awareness
Naval Terminal Instrument
Procedures Based on RNP RNAV
Today and the Road Ahead
Now a word from NAVFIG (N885F4)
“ We cannot remain tied to ground based NAVAIDS
forever. The Navy will help lead the way to the
RNAV/RNP future.”
“We will equip every NAS, MCAS, EAF, FOB with
RNAV approach capability consistent with mission
requirements.”
“We will anticipate the future. We will innovate
solutions. The procedures will be there waiting when
the aircraft can fly them.”
New Quote:
“We cannot flight a war or support expeditionary
operations tied to the FLIP cycle.”
NAVFIG RNP RNAV Vision
Current State of RNP RNAV IAP
• Immediate integration of new RNAV design criteria.
• Procedures designed to provide service to base line
equipped aircraft while approving minima
advantageous to more capable aircraft.
• Fleet Liaison to determine need and capabilities.
• Developing Partnership between Acquisition (NAVAIR)
and Procedure design (NAVFIG) to ensure seamless
transition to performance based navigation.
• USIFPP (United States Instrument Flight Procedures
Panel) Membership.
• 5 year Cyclic airfield survey program by NGA.
• RNAV OCONUS (Japan and Iraq)
• Recognition of civil aviation user needs. Contract
flyers need approaches too.
The Navy will help lead the way…
29 PALMS EAF
AL ASAD AB (OCONUS) 2004 5
AL TAQADDUM AB (OCONUS) 2004 1
Al QAIM FOB 2007 1
BARKING SANDS PMRF 2008 3
BEAUFORT MCAS
BRUNSWICK NAS
CAMP PENDLETON MCAS 1
CHERRY POINT MCAS 2006 3
CHINA LAKE NAWS 1998 1
CORPUS CHRISTI NAS 2008 8
EL CENTRO NAS
FALLON NAS
FORT WORTH NAS
FUTEMNA MCAS (OCONUS) 2008 2
GUANTANAMO NS (OCONUS) 2006 4
IWAKUNI MCAS (OCUNUS) 2007 1
JACKSONVILLE NAS 2001 2
KEY WEST NAS 2006 5
KINGSVILLE NAS 2008 4
KOREAN VILLAGE FOB 2004 1
LAKEHURST NAES 2007 2
LEMOORE NAS 2007 4
…Equip every NAS, MCAS, EAF, and FOB…
USN/USMC Airfields with RNAV Procedures
MAYPORT NAS
MERIDAN NAS
MIRAMAR MCAS 2006 1
NEW ORLEANS NAS 2008 2
NEW RIVER MCAS 2001 2
NORFOLK NS 2005 2
NORTH ISLAND NAS 2005 1
OCEANA NAS
ORANGE GROVE NOLF
PATUXENT RIVER NAS 1999 4
PENSACOLA NAS 2001 4
POINT MUGU NAS 1999 2
QUANTICO MCAF 1998 1
SAN CLEMENTE ISLAND NALF 2005 1
SAN NICOLAS ISLAND NOLF 2001 1
WHIDBEY ISLAND NAS 2006 2
WHITING FLD NAS – NORTH 2004 2
WHITING FLD NAS – SOUTH 2004 2
WILLOW GROVE NAS JRB 2004 2
YUMA MCAS 2007 2
Current/pending RNAV approaches
RNAV under development next 12 months
No RNAV within 12 months
…Equip every NAS, MCAS, EAF, and FOB...
CY 2006 33 Total RNAV Procedures
CY 2007 47 Total RNAV Procedures (127% increase)
CY 2008 78 Total RNAV Procedures (166% increase)
Goal: RNAV Full Operational Capability. (FOC)
Projected to have RNAV capability at all
installations by 2010.
Gathering Momentum toward a RNAV Performance
Based Navigation Full Operational Capability.
We will anticipate the future.
We will innovate solutions.
Future Growth:
•PS as unaugmented precision approach capability.
•LPV equivalency.
•otentially puts RNAV based precision approach in
every cockpit and to anyplace we care to land an
aircraft.
•RNAV Expeditionary Support Capability.
• Process development.
• Support routine training, expeditionary strike group
operations, fleet divert, and dynamic combat
environment.
• On demand support timeframe as norm not crisis.
“We cannot fight a war or
support expeditionary operations
tied to the FLIP cycle.”
DAFIF v8.0 production process does not currently support real
time use of RNAV navigation in a dynamic expeditionary
environment.
DAFIF v8.0 does not currently support RNAV precision
approach.
DAFIF v9.0 unfunded.
ANSWER: DAFIF augmentation to provide real time
database updates and FAS data block.
DOD AERONAUTICAL DATA BASE
PRODUCTION PROCESS
Development
of
Procedure
and Coding
by NAVFIG
Inclusion in
DAFIF18
DAFIF
Production
User
Requirement
Formal Request
SIAP and Coding
Source File
CRC Database File
DAFIF DVD
FLIP Publication
Current Routine Support of New Procedures
“We cannot fight a war or support
expeditionary operations tied
to the FLIP cycle.”
Current DAFIF Cycle 90-120
days for new procedure
Special Military Request
DAFIF Cycle 14-21
days for new procedure
Expeditionary Support Cycle
3-5 Days
What we need:
-Faster product development.
-Responsive 24/7 system.
-Delivery Direct to User.
GPS/RNP based procedures will get you there
From Baghdad to Pax
The Jump to RNP RNAV
• The Naval Aviation Program for TACAIR
– On Cost, On Schedule, On Performance
• Defining the Required Performance
– FRD uses PPS GPS for PVT and DAFIF for data base
• Enablers and Requirements
– RNAV from Departure through NPA
• The Digital Cockpit
– Equip the Aviator for Success
• The Jump to GPS RNAV TERPS
– IFR GPS Procedures for the Warfighter
Back up Slides
Lack of SA is a Killer
Controlled Flight Into Terrain of Hendrick Motorsports King Air 200, N501RH Oct. 24, 2004,
At Martinsville, Virginia see: http://www.ntsb.gov/publictn/2006/AAB0601.pdf
Failure to properly execute the published instrument approach procedure, and loss of SA due to GPS waypoint
Auto-sequencing and no cockpit display.
K/C-130J CNS/ATM
Platform Status
29 Nov 2007
Not Compliant
In Development
Not Applicable
Certification Complete
Dev Complete, Installs in Work
Awaiting Certification
CNS/ATM Fielding Status
Mode S = Mode Select
RVSM = Reduced Vertical Separation Minimums
RNP RNAV = Required Navigation Performance – Area Navigation
• 08/003 (A0361/07) - NEW RNAV STARS... DEAKK,
FOXXX, DADES... IFR AIRCRAFT INBOUND TO THE
TAMPA TERMINAL AREA. AIRMEN AND AIRLINE
OPERATORS ARE ADVISED THAT ALL ADVANCED
NAVIGATION AIRCRAFT WITH EQUIPMENT QUALIFIERS
/J, /Q, /R, /G, /L, AND /E ARE ADVISED TO FILE AND FLY
THE APPROPRIATE NEW RNAV STARS (DEAKK,
FOXXX, DADES) INTO THE TAMPA TERMINAL AREA.
DUE TO NAS SYSTEM ARCHITECTURE AND
LIMITATIONS THIS IS NECESSARY TO AVOID
CONFUSION, AIRBORNE REROUTES, POTENTIAL
DELAYS AND TO REDUCE COCKPIT WORKLOAD AND
ATC COMMUNICATIONS. 07 AUG 09:01 2007 UNTIL
UFN. CREATED: 04 AUG 20:25 2007 return
KTPA RNAV NOTAM
Source -
https://www.notams.faa.gov/dinsQueryWeb/queryRetrievalMapAction.do?reportType=Report&retrieveLocId
=KTPA
DEAKK ONE ARRIVAL (RNAV)
Meet the Crew

thunderland

Thanks for sharing!