database design and integrity for performance based ... database integrity - jeppesen.pdf · for...
TRANSCRIPT
Copyright © 2010 Jeppesen
Database Design and Integrityfor Performance Based Navigation (PBN)
Procedures
ICAO Asia-Pacific PBN Implementation Seminar1-2 February 2010
Hong Kong
Bill KelloggDirector, International Relations
Jeppesen
Copyright © 2010 Jeppesen
The Aeronautical Data Supply ChainHow does the data get to the flight deck?
Data Originators• Aerodromes, airspace & procedure designers, ATS, service providers, etc.• Supply information to the State AIS
State AIS• Gathers, produces and distributes the State AIP• Paper or electronic
Commercial Data Suppliers• Jeppesen, Lufthansa Systems Navtech EAG, etc. process aeronautcal
information.– Gather, analyze, aggregate, standardize, reconcile, configure, integrate,
distribute– Add value (electronic & paper charts, data, flight plans, etc.)– Ready for FMS/GPS database processing
Avionics Database Processors• Honeywell, GE Aviation, Rockwell Collins, Garmin, etc.• Avionics and customer specific formats and configurations
Copyright © 2010 Jeppesen
Stakeholders in AIM - different roles, responsibilities, obligations and needs
State Civil Aviation Authority
End user
Commercial Service Provider
State Designated Service Provider
State government organization responsible for the safety, regularity and efficiency of national and international aviation within its borders.
An organization, often referred to as an ANSP, which has been designated by a State to fulfill some of the State obligations for AIS/AIM provision. ANSPs are often „corporatized“organizations.
An organization, generally a corporation, that creates value-added services from the „official“ facts, data and information about the State aviation system.
Pilots, aircraft operators, ATS organizations, flight support organizations and other entities that use aeronautical information to support safe, efficient and orderly flight operations.
The Aeronautical Data Supply Chain... backbone of Aeronautical Infomation Management
Upstream Data Operation
Downstream Data Operation
Copyright © 2010 Jeppesen
CNS Infrastructure
CNS Infrastructure
AirportsAirports
Airspace designers
Airspace designers
ATCATC
OthersOthers
AirlinesAirlines
Other Airspace Users
Other Airspace Users
CommercialData
Providers
CommercialData
Providers
AISOrganization
AISOrganization
DatabaseProcessorsDatabase
Processors
IAIPNOTAMs
PIBetc.
IAIPNOTAMs
PIBetc.
PilotsPilots
Upstream Data Operation Downstream Data Operation End User
Industy StandardsICAO SARPs
The Aeronautical Data Supply Chain... a simplified view
Copyright © 2010 Jeppesen
The Aeronautical Data Supply Chain... upstream data operation
Procedure Design
AerodromesOther Services
AirspaceDesign CNS Provider
AISAIS
AIPAmend-ments
AIPAmend-ments
AIPAmend
AIPAmend-ments
AIPAmend-ments
AIPSupp
AIPAmend-ments
AIPAmend-ments
AIC
AIPAmend-ments
AIPAmend-ments
PIB
AIPAmend-ments
AIPAmend-ments
Checklists
AIP
Permanent or long-term
information onfacilities
and services
NOTAMs
Copyright © 2010 Jeppesen
Commercial Data provider
GatherAnalyze
AggregateStandardizeReconcileConfigureIntegrateAdd valueDistribute
Data Streams
Navigation Data Services
Charting Services
Operation Services
End user
State provided data
Customer provided data
Supplier derived data
The Aeronautical Data Supply Chain... downstream data operation
Copyright © 2010 Jeppesen
AIP Source Source
Document Control Data
CodingBlind re-key
ARINC 424 Data QC
Edits (on-line, Graphic, human, etc)
ARINC 424 Data
Daily Extract Edits
Project commit
ARINC 424 Data Extract
Avionics Edit
FMS Data Extract
FMS Data Pack
Data Verify
Edit Reports
FMS Database
FMS Data Report
FMS Database
Aircraft Load
The Aeronautical Data Supply Chain... downstream data operation
Commercial Data ProvidersCommercial Data Providers
FMS DatabaseProssesors
FMS DatabaseProssesors
Copyright © 2010 Jeppesen
• Reliable and consistent data is fundamental to successfully meet the challenges of current and future ATM systems
• AIS is a critical enabler for the implementation of future data dependant ATM systems
• Data currently provided within the scope of ICAO Annex 15 and related documents is, in most cases, not suitable for future use in PBN applications.
– Higher accuracy, resolution, integrity and timeliness are needed– With a foundation of reliable data, service providers can build what the market needs.
• If we want AIM to become the “Intranet of ATM” all actors in the data supply chain must be “on board”. We need each other to do the job, including strong industry involvement and ICAO leadership.
• Airspace users and service providers need open access to a foundation of aeronautical information that defines each State’s airspace
– to provide the products the market needs to operate safely and efficiently– to allow innovation to thrive
The Aeronautical Data Supply ChainConclusions
Copyright © 2010 Jeppesen
• Area Navigation Subcommittee Meeting……………………...1973
• First Gray Cover published..1975• ARINC 424-1.……………....1980• ARINC 424-3, First "Air Mass"
Application.………………….1982• ARINC 424-11, RF legs……1993• ARINC 424-13, RNP airways and
terminal procedures………...1995• ARINC 424-14, GLS approach
and path point……………….1999• ARINC 424-15, RNP Airspace
and holding………………..…2000• ARINC 424-19……………....2008• ARINC 424A, XML 424-19
…..…..Adoption expected in 2010 • ARINC 424A-1……………..2013?
ARINC 424... the Industry Data Standard
Copyright © 2010 Jeppesen
Relationships
Aeronautical Data Structure
CommAirspace
Term NDB
Aviation Logical Rules
Company Routes (Flight Plans)
Enroute Airways SIDs STARs Apps
Navaids Enrt WP Airport Reference Points
Gates Runways Term WP
Lighting ILS
LOC DMEMkr BcnG SlopeLocalizer
Hold Pattern
Copyright © 2010 Jeppesen
PATH and TERMINATION
Describes Leg Types
Path - How do you get there - (Heading, Course, Etc.)
Termination - The event or condition that causes Leg Sequencing
(Also known as Path/Terminators)
Copyright © 2010 Jeppesen
VA leg
Heading to Altitude
Path - Heading 090°Termination - 8,000 feet
ICAO RNAV Leg One of 23 leg types
PATH and TERMINATION
Copyright © 2010 Jeppesen
VI leg
Heading to a Next Leg Intercept
Path - Heading 090°Termination - Interception of the 070°
Course to the Next Fix
PATH and TERMINATION
ICAO RNAV Leg
Copyright © 2010 Jeppesen
VM leg
Heading to a Manual Termination
Path - Heading 080°Termination - Manual Termination
(Pilot must take action to terminate)
PATH and TERMINATION
ICAO RNAV Leg
Copyright © 2010 Jeppesen
CA leg
Course to an Altitude
Path - Course 080°Termination - 6,000 feet
(default leg for most European departures)
(Along-Track Position Undefined)
PATH and TERMINATION
ICAO RNAV Leg
Copyright © 2010 Jeppesen
CF leg
Course to a Fix
Path - Course 080°Termination - Crossing the Fix
RNP Leg
PATH and TERMINATION
ICAO RNAV Leg
Copyright © 2010 Jeppesen
DF leg
Computed Track Direct to a Fix
Path - Great circle course from present position to the “to” waypoint
Termination - Passing the “To” Waypoint
RNP Leg
PATH and TERMINATION
ICAO RNAV Leg
Copyright © 2010 Jeppesen
TF leg
Track Between Two Fixes
Path - Great circle course between waypointsTermination - Passing the “To” WaypointDefault leg type for enroute airways
Primary RNP Leg
PATH and TERMINATION
ICAO RNAV Leg
Copyright © 2010 Jeppesen
IF leg
Initial Fix
Not a real Path or Termination.Initial Fix Begins the series of records for a procedure (SID, STAR, Approach)
Primary RNP Leg
PATH and TERMINATION
ICAO RNAV Leg
Copyright © 2010 Jeppesen
RF leg
Constant Radius to a Fix
Path - Arc around a reference pointTermination - Terminating Fix(all start and end fixes for RF legs are fly-by fixes)(legs to and from RF leg “should” be tangent)
Primary RNP Leg
PATH and TERMINATION
ICAO RNAV Leg
R
R
2 RNP
2 RNP
2 R
NP
2 R
NP
STEP 2:Locate Turn Center
STEP 1:
SegmentInitialFix
a=Rb=R+(2xRNP)c=R-(2xRNP)
SegmentTerminating
Fix
STEP 3
STEP 4
STEP 5
a
b
c
Tangent Points
Tangent Points
Apply para 2-2
Radius to Fix (RF) Segments
Copyright © 2010 Jeppesen
HM leg
Hold to a Manual Termination
Path - Holding PatternTermination - Manual Termination
Primary RNP Leg
PATH and TERMINATION
ICAO RNAV Leg
Copyright © 2010 Jeppesen
HA leg
Hold to an Altitude
Path - Holding PatternTerminator - Terminating Altitude(Climb in the Holding Pattern)
Primary RNP Leg
PATH and TERMINATION
ICAO RNAV Leg
Copyright © 2010 Jeppesen
HF leg
Hold to a Fix
Path - Holding PatternTermination - 2nd Fix Crossing (One circuit in the Hold)
Primary RNP Leg
PATH and TERMINATION
ICAO RNAV Leg
Copyright © 2010 Jeppesen
PathTerminators
TF
TF
TF
TF
CADF
HFIF
IFIF
Puerto Asis, Columbia HM
TF
Copyright © 2010 Jeppesen
Path and Terminator State RequirementsPANS OPS
Path and Terminator (“Path Terminator”). A two-letter code, which defines a specific type of flight path along a segment of a procedure and a specific type
of termination of that flight path. Path terminators are assigned to all RNAV, SID, STAR and approach procedure segments in an airborne navigation
database.• Note.— Path terminators as defined in PANS-OPS
are, with the exception of the RF path terminator, established in accordance with the rules set forth in ARINC Specification 424-15, Navigation System Data Base. The rules applicable to the RF path terminator are based upon ARINC 424-17.
Copyright © 2010 Jeppesen
RNAV Path TerminatorsPANS-OPS
Copyright © 2010 Jeppesen
RNAV Path Terminator Sequences
Copyright © 2010 Jeppesen
Fly-Over Fix Symbol Standard
All holding fixes are fly-over fixes
Copyright © 2010 Jeppesen
Fly-Byversus
Fly-OverFixes
WIVLI
Copyright © 2010 Jeppesen
Path Points
In Database with CRCIn Database with CRC
SBAS / WAAS(FAA)
Copyright © 2010 JeppesenNumeric4 CharactersLength Offset
Numeric5 CharactersCourse Width at Threshold
Numeric4 CharactersGlide Path Angle
Alphanumeric7 CharactersThreshold Crossing Height
Alphanumeric12 CharactersFPAP Longitude
Alphanumeric11 CharactersFPAP Latitude
Numeric6 CharactersLTP Ellipsoidal Height
Alphanumeric12 CharactersLTP Longitude
Alphanumeric11 CharactersLTP Latitude
Alphanumeric4 CharactersReference Path Identifier
Numeric2 CharactersReference Path Data Selector
Alpha1 CharacterRoute Indicator
Numeric1 CharacterApproach Performance Designator
Alphanumeric5 CharactersRunway Identifier
Alphanumeric4 CharactersAerodrome Identifier
Numeric2 CharactersSBAS Service Provider Identifier
Numeric2 CharactersOperation Type
Data TypeField SizeData Field
Path Point Record (ARINC 424)FAS Data Block (RTCA/ICAO)
Most airlines have not endorsed WAAS
• SBAS/WAAS based procedures
• Supports avionics monitoring and alerting
• ASCII digital representation
• Cyclic Redundancy Check (CRC) wrapped
• GLS FAS data block uplink
• RNP – questionable safety case to support
Copyright © 2010 Jeppesen
RNP AR Approach Enabling Features
R
R
2 RNP
2 RNP
2 R
NP
2 R
NP
STEP 2:Locate Turn Center
STEP 1:
SegmentInitialFix
a=Rb=R+(2xRNP)c=R-(2xRNP)
SegmentTerminating
Fix
STEP 3
STEP 4
STEP 5
a
b
c
Tangent Points
Tangent Points
Apply para 2-2
Radius to Fix (RF) SegmentsVertical Error Budget &
Guided Missed Approach
Narrow Segments
Narrow lateral linear segments(RNP-0.3 or less with no secondary buffers)
Curved segments anywhere along the approach(Radius-to-fix legs with shorter leg lengths)
Guided, narrower turns on missed approaches(Radius-to-fix legs, and RNP-1 or less)
Performance-based Vertical Buffers(Vertical Error Budget )
Copyright © 2010 Jeppesen
Airline Requirementsfor RNP AR APCH Operations
• Obtain RNP AR Instrument Procedures (3rd Party – e.g. Jeppesen, in house, public)
• Validate Navigation database integrity
• Acquire or equip qualified aircraft• Revise maintenance procedures• Develop Flight Crew procedures • Revise airline dispatch procedures • Implement RNP monitoring and
reporting• Prepare an application
documenting how RNP AR APCH requirements are met
Copyright © 2010 Jeppesen
Navigation Database Validation
• Document systems in place to ensure data is always correct.– Airline Internal Processes OR 3rd
Party Service (e.g. Jeppesen) for Quality Assurance of Navigation Database
• Validation of data base content
• Specific AR APCH procedures review
• Approved Navigation Database Source – Provider must “comply with
EUROCAE ED-76A / RTCA DO-200A, or equivalent approved procedures”
Copyright © 2010 Jeppesen
DO-201A / ED-77AIndustry Requirements for Aeronautical InformationDeveloped by RTCA SC-181 & EUROCAE WG-13
to document data requirements
Key elements of DO-201A incorporated in ICAO Annex 15,
Aeronautical Information Services
Industry Data Standards
Copyright © 2010 Jeppesen
Annex 15Data Quality Requirements
WGS-84
1 x 10-8 = 1 error in 100,000,000
1 x 10-5 = 1 error in 100,000
1 x 10-3 = 1 error in 1,000
Copyright © 2010 Jeppesen
Industry Data Standards
Referenced in FAA Advisory Circular 120-153, Acceptance of Data Processes
and Associated Navigation Databases
DO-200A / ED-76AStandards for Processing
Aeronautical Data
Developed by RTCA SC-181 & EUROCAE WG-13 to document data
processing requirements
DO-200A /ED-76 processes expect source data quality that meets Annex 15 SARPs
Copyright © 2010 Jeppesen
Quality Management
• Corrective action• Document control• Records management• Management review• Nonconforming products• Letters of Acceptance• Certificates of
Conformity• Audits• Preventative actions
Aeronautical data processes are expected to operate under a Quality Management System (QMS)
Copyright © 2010 Jeppesen
Quality Assured Information
ISO 9001:2000
DO-200A / ED-76Standards for Processing Aeronautical Databases
Letters of Acceptance (LoA)Issued by FAA & EASA
Copyright © 2010 Jeppesen
DO-200A Letter of AcceptanceType 1 and Type 2
• Type 1 LoA for ARINC 424 data processes
• Type 2 LoA for aircraft loadable database processes
Copyright © 2010 Jeppesen
Thank You