曝光臺(tái) 注意防騙 網(wǎng)曝天貓店富美金盛家居專(zhuān)營(yíng)店坑蒙拐騙欺詐消費(fèi)者

making significant safety-related changes to
ATC system
􀀴Systematic analysis of hazards and
mitigations during all phases of system’s life
cycle
􀂾GNSS safety plan
ATMB–CAAC Workshop on GNSS Beijing, 16-17 April 2007
Certification and operational approvals
􀀴 State responsibility to authorize GNSS operations
in its airspace
􀀴 Approval document: for aircraft with certified
equipment and approved flight manual
􀀴 Specifies any limitations on proposed operations
􀀴 VFR use or IFR use
􀀴 GNSS alone or with other systems
􀀴 Airworthiness certification based on
RTCA/EUROCAE documents
ATMB–CAAC Workshop on GNSS Beijing, 16-17 April 2007
Anomaly reporting
􀀴 Anomaly: GNSS service interference)
􀀴 Pilot to report to ATC asap requesting special
handling as required and file complete report in
accordance with State procedures
􀀴 Controllers to record information of the occurrence,
to identify other GNSS-equipped aircraft that may
be affected, and to forward information to
designated authority
􀀴 National focal point unit to information
outage (may be due to
collect anomaly-related
ATMB–CAAC Workshop on GNSS Beijing, 16-17 April 2007
Vulnerability
􀀴 Potential for interference is the main vulnerability
􀀴 Receiver interference mask specifies the level of interference that can be
tolerated
􀀴 Several interference sources (eg microwave links within L1 band in some
States)
􀀴 Unintentional vs intentional interference
􀀴 States should:
􀂾 assess sources of vulnerability and develop mitigations (technical,
procedural back-up)
􀂾 provide effective spectrum management and protection of GNSS
frequencies to reduce the possibility of unintentional interference
􀂾 use on-board mitigation techniques (eg inertial)
􀂾 consider selective retention of conventional navaids as part of an
evolutionary transition
􀂾 take full advantage of new GNSS signals and constellations
ATMB–CAAC Workshop on GNSS Beijing, 16-17 April 2007
GNSS and PBN
ALL PBN Navigation specifications are
based on GNSS either as the primary
navigation infrastructure or as one
element of the infrastructure
ATMB–CAAC Workshop on GNSS Beijing, 16-17 April 2007
END
Thank you for your attention!
1
Performance Based Navigation
Jim Nagle
jnagle@icao.int
Chief, Communications, Navigation and Surveillance Section
ICAO
2
Presentation
overview
􀀴PBN – background
􀀴PBN - Concept
􀀴RCP and RSP
􀀴Overview of presentations on
Thursday
3
Aviation challenges
:
􀀴 Growing demands for RNAV approaches (safety,
accessibility)
􀀴 Growing demands for solution airspace congestion
􀀴 Growing fuel efficiency requirements
􀀴 Growing Environmental requirements
􀀴 Can be met with most of current technology,
but standardization and operational
place
requirements have to be put into
4
Background
ICAO RNP concept
􀀴 FANS identified need for performance based navigation and
developed Required Navigation Performance capability concept :
􀂾 To avoid need for ICAO selection between competing systems
􀀴 Manual on Required Navigation Performance (doc 9613)
􀀴 Emphasize on the en-route phase of flight (RNP-10 and RNP-4) for
oceanic and remote applications
􀀴 No ICAO RNP requirements for continental enroute and terminal
applications.
􀂾 Proliferation of national standards
􀂾 Wide variety of functional requirements
􀂾 Variety of required navigation sensors
􀂾 Differing air crew requirements
􀂾 Lack of global harmonization
5
Approach
proliferation of types
Non-Precision
Approach
Precision Approach
NonPrecision Approach
Approach with Vertical
guidance (APV)
Precision Approach
Definition of operations become very
blurred
Need for performance requirements
and possibly need for
reclassification
Etc.
Etc.
Etc.
RNAV (GNSS)
Basic-GNSS
RNP
APV
LPV
GAGAN
GRAS
WAAS
LAAS
LNAV
LNAV/VNAV
SBAS
GBAS
Baro-VNAV
Galileo
6
Background
Industry’ s RNP concept
　
中國(guó)航空網(wǎng) m.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：空管資料4(17)