ARINC424简介ppt课件

1、22-23 June 2005RNAV Procedure Coding Workshop1Introduction to ARINC 424Amsterdam22-23 June 200522-23 June 2005RNAV Procedure Coding Workshop2Flash Back (1)ARINC - Aeronautical Radio, Inc. - a cooperation of a variety of stockholders such as airlines, aircraft manufactures and other air transport com

2、panies.ARINC activities include operation of land radio stations, the allocation and assignment of frequencies and the exchange of technical information.ARINC sponsors the Airlines Electronic Engineering Committee (AEEC).AEEC formulates standards for electronic equipment and systems for airlines.22-

3、23 June 2005RNAV Procedure Coding Workshop3Flash Back (2) Purpose of ARINC Specifications1. Indicate new equipment requirements to the manufacturers of electronic equipment based upon the considered opinion of the airline technical experts.2. Influence new equipment designs in order to achieve the m

4、aximum possible standardisation of those physical and electrical characteristics which affect equipment interchangeability. 22-23 June 2005RNAV Procedure Coding Workshop4Flash Back (3)The requirement for on-board navigation data bases was identified in the 1970s with the development of the first Fli

5、ght Management Systems (FMS). ARINC 424 - first edition was published in May 1975 and adapted by the industry in July 1975. At this stage the ARINC 424 document was developed to support conventional Navigation. With the implementation of the area navigation methods, and the capability to use inputs

6、from different sensors, the requirement to have access to a sophisticated on-board navigation data base became mandatory (TGL 10).ARINC 424 has been continuously improved and adjusted over the years in order to accommodate new navigational procedures, capabilities, standards and technical characteri

7、stics. 22-23 June 2005RNAV Procedure Coding Workshop5ARINC 424 - is a standard for the preparation and transmission of data for assembly of airborne navigation system data basesARINC 424 a Specification for Navigation System Data BasesThe ARINC 424 document enables data base suppliers, avionics syst

8、ems and other users of the data bases to fly and flight plan procedures as prescribed by designers. The document is not meant to be a prescriptive document for procedure design experts.Currently ARINC 424-16 is in use ARINC 424-17 is under development22-23 June 2005RNAV Procedure Coding Workshop61.

9、Assemble a data bank. 2. Produce electronic media meeting the operational requirements of the next link in the data chain (avionics manufacturer, airlines, ATC).3. Merge the data with the operational software of airborne navigation computers.4. Produce electronic media containing the merged data for

10、 use on individual aircraft.Participants in the data processing chain are public organisations, States, avionics manufacturers, datahouses and various end-users.Any participant in the data chain may originate, transmit, assemble, prepare or integrate aeronautical data. Aeronautical Data Processing S

11、teps22-23 June 2005RNAV Procedure Coding Workshop7Differences in Avionics SystemsIndividual navigation systems require different formats for navigation reference data.The available storage in many avionics systems prevents all procedures or data elements from being loaded into the airborne database.

12、Airlines are cost driven and hence do not upgrade equipment unless there is a clear benefit.The system life cycle of most avionics equipment is 15 to 20 years.Over the years, different earth models, geodesic calculations and uses of variables such as magnetic variation have been used. Differences in

13、 avionics systems need to be considered during the processing of aeronautical data. As a result, databases from different datahouses may not always be consistent.22-23 June 2005RNAV Procedure Coding Workshop8Navigation System Data Base Sorting ProcessSorted in alpha/numerical order Divided into stan

14、dard (S) and tailored (T) recordsS records ordered by Area CodeT records ordered by Airline CodeIndividual records divided in sections/sub-sections of max. 132 characters Record: A single line of computer data made up of the fields necessary to define fully a single piece of information Field: The c

15、ollection of characters needed to define one item of informationEach record uniquely defined and stored in the master user file22-23 June 2005RNAV Procedure Coding Workshop9Geographical Area Codes22-23 June 2005RNAV Procedure Coding Workshop10Access to Navigation DataAn aeronautical database is a co

16、llection of data that is arranged for ease of electronic storage and retrieval in a system that supports airborne or ground based aeronautical applications.The database structure, sorting rules and the relationships between data elements, laid down in ARINC 424 standard are indispensable prerequisit

17、es for the function of such systems. Each primary record, completed by additional primary and continuation records, covers all required data elements.Basic principles of databases is that information need to be entered, corrected, changed or deleted only once.On-board RNAV systems have access to pre

18、-programmed routes, the airspaces concerned, the navaids serving this airspace, the airports along the route including departure and destination airports.The system identifies the next waypoint, calculates the aircraft position and provides inputs to the flight control systems.22-23 June 2005RNAV Pr

19、ocedure Coding Workshop11Master Airline User fileAlternative paths to individual master airline files22-23 June 2005RNAV Procedure Coding Workshop12Data Record (1) Layout VHF NAVAIDContains:customer/area code, station identifier, navaid name, co-ordinates, frequency, elevation (DME), variation, datu

20、m code etc. 22-23 June 2005RNAV Procedure Coding Workshop13Data Record (2)Layout WaypointContains:Waypoint IDCo-ordinatesTypeENR or TerminalRNAVIAF/IF/FACF/FAF/MAPtStepdown (Terminal only)Arc centre (Terminal only)SID/STAR/APP/MultipleUsageRNAV airwayTerminal22-23 June 2005RNAV Procedure Coding Work

21、shop14Data Record (3)Layout HoldingContains:Region CodeFix IdentifierInbound CourseTurn DirectionLeg LengthLeg TimeHolding SpeedMin AltitudeMax AltitudeCycle Date22-23 June 2005RNAV Procedure Coding Workshop15Data Record (4)Layout AirportContains:Airport ICAO IdentifierATA/IATA DesignatorLongest Run

22、wayMagnetic Variation Airport ElevationARPSpeed LimitTransition Level/AltitudeAirport NameDatum Code etc.22-23 June 2005RNAV Procedure Coding Workshop16Data Record (5)Layout GateContains:Airport IdentifierCustomer Area CodeGate IdentifierLatitudeLongitudeNotes etc.22-23 June 2005RNAV Procedure Codin

23、g Workshop17Data Record (6)Layout SID/STAR/App_1Contains:Procedure IdentifierRoute TypeSID/STAR-Runway Transition,Enroute Transition, Common RouteApp-App Transition, GPS App, RNAV App, Primary MISAP, Secondary MISAP, Circling App, Straight-in App, Helo to RWYTransition IdentifierSequence NumberWaypo

24、int Identifier etc.22-23 June 2005RNAV Procedure Coding Workshop18Data Record (6)Layout SID/STAR/App_2Contains:Waypoint DescriptorEssentialFly-over waypointStepdown fixPathpointIAF/IF/FAF/FACFMAPtHoldingTurn DirectionPath and TerminationRecommended NavaidArc RadiusThetaRhoMagnetic CourseRoute/Holdin

25、g Distance/TimeAltitude1, Altitude 2, Vertical Angle22-23 June 2005RNAV Procedure Coding Workshop19Data Record (7)Layout RunwayContains:Runway IDRunway LengthRunway Magnetic BearingThreshold Co-ordinatesRunway GradientThreshold ElevationThreshold Crossing HeightDisplaced Threshold DistanceLOC/MLS/IL

26、S Ref Path IDLOC/MLS/ILS Categroy/ClassRunway Description22-23 June 2005RNAV Procedure Coding Workshop20Data Record (8-29)NDB NavaidsLocaliser and Glide Slope/MLS/GLSCompany RouteLocaliser MarkerPath PointsAirport CommunicationsMSAAirways MarkerCruising TablesFIR/UIRGRID MORAEnroute AirwaysEnroute A

27、irways Restrictive Enroute CommunicationsPreferred RoutesControlled Airspace22-23 June 2005RNAV Procedure Coding Workshop21Design and Coding IssuesWaypoint ClassificationRho-Theta ValuesRecommended NAVAIDCo-located VOR/DMESpeed RestrictionsAltitude RestrictionsWaypoint, NAVAID and Fix CoordinatesNam

28、ing ConventionsPath Terminator Concept22-23 June 2005RNAV Procedure Coding Workshop22Waypoint ClassificationThe enroute waypoint subsection contain all named intersections defined in the enroute structure. As a minimum all waypoints referenced in sections. should be available in the enroute subsecti

29、on.The terminal waypoint subsection contain those waypoints necessary to support SIDs and STARs and approach procedures.If a waypoint is used in both the terminal and enroute areas, it should appear in both the terminal and enroute subsection file. In order to achieve consistent coding, State source

30、s must clearly classify any multiple use of waypoints in the respective AIP sections.22-23 June 2005RNAV Procedure Coding Workshop23Rho-Theta Values“Rho” is defined as the geodesic distance in miles to a waypoint. Source: official government sources when available.“Theta” is defined as the magnetic

31、bearing to a waypoint. Source: official government sources when available.If a procedure leg requires Rho-Theta information e.g. from a recommended navaid, it must be published in AIP.The content is controlled through requirements of the path terminators and coding rules contained in ARINC 424.22-23

32、 June 2005RNAV Procedure Coding Workshop24Recommended NAVAIDThe Recommended NAVAID in any Enroute Airway Record may be any VOR/DME or VORTAC available in the database. The Recommended NAVAID in any Terminal Procedure Record other than final approach, shall be the procedure reference facility in acco

33、rdance with the rules governing recommended navaids for path terminators.On NDB based procedures, the recommended NAVAID information is provided with the Final Approach Course Fix (FACF), the FAF and the Missed Approch Fix record. This NDB or Locator will be the procedure reference navaid. Different

34、 possibilities of determining magnetic variation in a TMA (individual navaid station declination, variation at airport reference point etc). For database consistency the recommended NAVAID is required for certain procedure legs to enable the RNAV system to determine the correct magnetic variation. 2

35、2-23 June 2005RNAV Procedure Coding Workshop25Co-located VOR/DME NAVAID details of all VOR, VOR/DME, VORTAC and TACAN stations within a geographical area of interest.For VOR/DME and VORTAC facilities, if the identification code of the VOR and DME components is the same, the DME identifier will be bl

36、ank.If they are not the same, the DME identifier field will carry the identification of the DME component.According to ICAO Annex 10 co-located means that the latitude and longitude of the two facilities differ by no more than 1/10 arc minutes (6 seconds).If either the latitudes and/or longitudes of

37、 a VOR and TACAN or DME components of a frequency-paired VHF NAVAID differ by 1/10 arc minutes or more the character “N” needs to be entered into column 32 on VHF NAVAID record (navaid class).22-23 June 2005RNAV Procedure Coding Workshop26Speed and Altitude Restrictions (1)Speed RestrictionsThe spee

38、d limit will be derived from official government source and shown in knots on a SID/ STAR record.On SIDs, the speed limit will apply to all legs up to and including the terminator of the leg on which the limit is encoded from the beginning of the procedure.If a second speed limit is coded on a subse

39、quent leg, the limit will be applied from that leg backwards to the previous terminator which contained a speed limit.On STARs, the speed limit will be applied forward to the end of arrival unless a second speed limit is encoded.22-23 June 2005RNAV Procedure Coding Workshop27Speed and Altitude Restr

40、ictions (2)According to ARINC 424 speed limitations can be coded in different ways by using different path terminators. In order to achieve consistency all speed restrictions in RNAV procedures should be applied at specific waypoints.Speed restrictions that are only applied during specific time peri

41、ods are not coded in database.Some legacy systems can only process speed restrictions in combination with an altitude restriction. .22-23 June 2005RNAV Procedure Coding Workshop28Speed and Altitude Restrictions (3)Altitude RestrictionsThe altitude description field will designate whether a waypoint

42、should be crossed “at”, “at or above” or “at or below” specified altitudes.The conditional termination altitude can be coded in columns 90 through 95 of the SID record. If a “+”, “-” or blank is coded in the altitude description field, input of a second altitude must imply a conditional altitude ter

43、mination. If a published take-off requires a turn greater than 15 degrees from the runway heading without an altitude specified before the turn.a CA, VA, or FA on the runway heading to an altitude of 400 feet (or as specified by source) must be coded before the turn or as first leg of the departure.

44、 22-23 June 2005RNAV Procedure Coding Workshop29Speed and Altitude Restrictions (4)ARINC 424 provides a number of ways to code altitude restrictions. For simplification and to avoid coding inconsistencies altitude restrictions should be applied at waypoints wherever possible. Altitude restrictions i

45、n the terminal area that are only applied during specific time periods will not be included in the airborne database.22-23 June 2005RNAV Procedure Coding Workshop30Waypoint, Navaid and Fix Coordinates (1)The geographic position of waypoints, intersections, navaids, runway thresholds etc. is defined

46、in the latitude/ longitude fields.Nine alpha/numeric characters define the latitude in degrees, minutes, seconds, tenth of seconds and hundredths of seconds: N45562518Ten alpha/numeric characters define the longitude in degrees, minutes, seconds, tenth of seconds and hundredths of seconds: E01552362

47、2. This resolution reflects the airlines desire for the use of best available data.22-23 June 2005RNAV Procedure Coding Workshop31Waypoint, Navaid and Fix Coordinates (2) Aviation industry requirements for accuracy and resolution for elected data elements. These industry requirements represent the r

48、esolutions that can be used by the various avionics systems.Many numerical values used in describing procedures are calculated values e.g. fixes, TMA entry or exit points etc. 22-23 June 2005RNAV Procedure Coding Workshop32Waypoint, Navaid and Fix Coordinates (3)The accuracy of calculated values is

49、limited by the accuracy of the values used in the calculation.The designer should be aware of all the navaids that an aircraft flying a certain procedure may use.This includes navaids located in nearby TMAs or in neighbouring countries. Special agreements with host countries may be required.The nava

50、id function and reliability and the consequences of navaid outages need to be addressed during design (operating hours, maintenance status, required flight checks, emergency power supply etc)22-23 June 2005RNAV Procedure Coding Workshop33ARINC 424 Naming Convention (1)ICAO Annex 11 defines the inter

51、national standards for the coded designators of NAVAIDs, waypoints, airways, SIDs and STARs. Track change points or turning points should be named and defined by co-ordinates in the AIP.ARINC 424 establishes coding rules for identifiers and name fields when the government source does not provide ide

52、ntifiers or names in accordance with Annex 11.Example: ARINC naming rule for RNAV waypoints, intersections and reporting points if the name/identifier is more or less than five characters: - if five or less characters, use the full name - if more than five characters, eliminate double letters, keep

53、the first letter, first vowel and last letter, drop other vowels from right to left, drop consonants, starting from right to left 22-23 June 2005RNAV Procedure Coding Workshop34ARINC 424 Naming Convention (2)Any planned deviation from the ICAO naming convention should be avoided. Deviations create a

54、dditional workload, cause misinterpretations and encourage errors.If required waypoints e.g. turning points are not named and defined by coordinates in database, these points must be identified in an RNAV database. The so called Computer Navigation Fixes (CNFs) will be created by the datahouses. In

55、certain cases, ATC is unaware that these fixes exist.A serious safety problem can arise when a pilot needs to select a navaid from the database by identifier and the database has multiple navaids with the same identifier. 22-23 June 2005RNAV Procedure Coding Workshop35The Path Terminator Concept (1)

56、The Path and Terminator concept was developed to permit coding of terminal area procedures, SIDs, STARs and approach procedures without proliferating the number of waypoints.The two elements Path and Terminator prescribing the way in which a path is to be flown and how the path is to be terminated.Over the years and in particular with the introduction of RNAV new leg types were added. Currently, the ARINC 424 document describes 23 path terminators.Certain limitations such as leg sequence or fly-by/ fly-over rules must be considered by procedure designers.Database suppliers must be