杰普逊航图与导航数据库-第八章课件.ppt

《杰普逊航图与导航数据库-第八章课件.ppt》由会员分享，可在线阅读，更多相关《杰普逊航图与导航数据库-第八章课件.ppt（91页珍藏版）》请在淘文阁 - 分享文档赚钱的网站上搜索。

1、Chapter 8 Differences Between Jeppesen Database&ChartsChapter 8 Differences Between Jeppesen Database&Charts8.1 Introduction8.2 Aeronautical Information Cut-off Dates&Effective Dates8.3 General Differences8.4 Navaids8.5 Waypoints8.6 Airways8.7 Arrivals&Departures Procedures8.8 Titles&Omitted Procedu

2、res of Approach Procedure 8.9 Plan View Of Approach Procedure8.10 Profile Of Approach Procedures 8.11 Approach Procedures 8.12 Routes On Charts But NOT In Databases8.13 Final Cockpit Authority,Charts Or Database 8.1 IntroductionThe basic design for most aeronautical information contained in instrume

3、nt procedures has been created for the analog world.Virtually all the aeronautical databases are loaded according to the specifications in the Aeronautical Radio,Incorporated(ARINC)424 standard“Navigation Databases.”Many of the differences between charts and databases are because there can be no sta

4、ndard implemented to have the information in both places depicted the same.There are some cases where it is desirable not to have the information the same because of the different type of media where the information is displayed.There are many different types of avionics equipment utilizing the Jepp

5、esen NavData database.The same database information may be presented differently on different types of airborne equipment.In addition,some equipment may be limited to specific types of database information,omitting other database information.Pilots should check their Operating Handbooks for details

6、of operation and information presentation.A major factor in“apparent”differences between database and charts may be due to the avionics equipment utilized.As avionics equipment evolves,the newer systems will be more compatible with charts,however the older systems will still continue with apparent d

7、ifferences.8.2 Aeronautical Information Cut-off Dates&Effective DatesThe ICAO Aeronautical Information Regulation and Control(AIRAC)governs the 28-day cycle between effective dates of aeronautical information.Charts typically use 7-day and 14-day cycles for terminal charts and 28-day and 56-day cycl

8、es for Enroute and Area charts.8.3 General DifferencesCharted Information Not Provided in the Jeppesen Navdata DatabaseMagnetic Courses,DistancesReference Datum 8.3.1 Charted Information Not Provided in the Jeppesen Navdata DatabaseNot all the information that is included on the charts is included i

9、n the airborne database.The following is a general listing of some of those items:Altimetry QNH/QFE information Alternate altimeter setting sourcesIntersection formations(radials,bearings,DME)Terrain and ObstaclesAirport Operating Minimums Landing,take-off and alternate minimumsAirport taxiways and

10、rampsSome types of special use airspace and controlled airspace 8.3.2 Magnetic Courses,DistancesBecause of different magnetic models used in airborne systems,a magnetic course read on the airborne system may differ from the charted magnetic course.Avionics computed distances may disagree with charte

11、d distances.Differences may appear on airways on Enroute Charts,and on flight procedures included on SID,DP,STAR,Approach,and Airport charts.In addition,when the database requires a specific course to be flown from“A”to“B”,the differences in magnetic variation or VOR station declination may result i

12、n a“jog”between the two fixes in lieu of a direct track.8.3.3 Reference DatumNot all States(countries)have complied with the ICAO Annex that specifies the use of the WGS-84 reference datum.Differences in reference datums can cause significant“accuracy bias”in the navigation guidance provided by avio

13、nics systems.8.4 NavaidsCompletenessNDB and Locator IdentifiersLocator IdentifiersDuplicate Navaid Identifiers 8.4.1 CompletenessBecause of the duplication of identifiers and other factors,not all charted navaids are included in the database.8.4.2 NDB and Locator IdentifiersAs an example of the diff

14、erences between the display from one avionics system to another:some avionics systems will display the Foley NDB as“FPY”.Some avionics systems include a suffix“NB”after the NDB identifiers and will display the Foley NDB as“FPYNB”.For NDBs and locators with duplicate Morse code identifiers that are l

15、ocated within the same State(country),may only be available using the airport identifier for access.8.4.3 Locator IdentifiersMost locators in the United States have unique five-letter names,but most international locators have names that do not have five letters.Some systems may display U.S.locators

16、 as“CASSE”.Some systems may display U.S.locators as“AP”.8.4.4 Duplicate Navaid IdentifiersThere are numerous duplicates in the database.Refer to your avionics handbook for the proper procedure to access navaids when duplicate identifiers are involved.Not all navaids in the database are accessible by

17、 their identifier.Some navaids,for reasons such as duplication within terminal areas or lack of complete information about the navaid,are in the waypoint file and are accessible by their name or abbreviated name.8.5 WaypointsWaypoint Database IdentifiersCommon Waypoint Name for a Single LocationFly-

18、over Versus Fly-by Fixes/Waypoints 8.5.1 Waypoint Database Identifiers“Database Identifiers”refers to identifiers used only in avionics systems utilizing databases.The identifiers are not for use in flight plans or ATC communications;however,they are also included in computer flight planning systems

19、.They may be designated by the State(country)as“Computer Navigation Fixes”(CNFs)or designated by Jeppesen.To facilitate the use of airborne avionics systems,the identifiers are being added to Jeppesens charts.Both the CNFs created by States and the Jeppesen-created database identifiers are enclosed

20、within square brackets and in italics.Jeppesens ultimate goal is to include all database identifiers for all waypoints/fixes on the charts.Enroute charts include the five-character identifier for unnamed reporting points,DME fixes,mileage breaks,and any reporting point with a name that has more than

21、 five characters.SID,DP and STAR charts are being modified to include all identifiers.Approach ChartsVNAV descent angle information derived from the Jeppesen NavData database is being added to approach charts.Identifiers are shown for the Final Approach Fix(FAF),Missed Approach Point(MAP),and the mi

22、ssed approach termination point.State-named Computer Navigation Fixes(CNFs)are shown on all applicable charts.GPS(GNSS)type Approach Charts include all database identifiers.8.5.2 Common Waypoint Name for a Single LocationGovernment authorities may give a name to a waypoint at a given location,but no

23、t use the name at the same location on other procedures in the same area.The Jeppesen NavData database uses the same name for all multiple procedure applications.Charting is limited to the procedure(s)where the name is used by the authorities.8.5.3 Fly-over Versus Fly-by Fixes/WaypointsIn most cases

24、,pilots should anticipate and lead a turn to the next leg.The database indicates when the fix must be crossed(flown-over)before the turn is commenced.The fix is coded as fly-over when the requirement is inferred or is specified by the governing authority.Fixes are charted as fly-over fixes only when

25、 specified by the governing authority.Fly-over fixes have a circle around the fix/waypoint symbol.No special charting is used for fly-by fixes.8.6 AirwaysATS RoutesDesignatorsAltitudesChangeover Points 8.6.1 ATS RoutesAirways identified as ATC routes by States(countries)cannot be uniquely identified

26、.They are not included in the Jeppesen NavData database.8.6.2 DesignatorsJeppesen NavData database airway designators are followed by a code indicating ATC services(such as“A”for Advisory,“F”for Flight Information)when such a code is specified by the State(country).Not all airborne systems display t

27、he ATC services suffix.8.6.3 AltitudesMinimum Enroute Altitudes(MEAs),Minimum Obstacle Clearance Altitudes(MOCAs),Off Route Obstacle Clearance Altitudes(OROCAs),Maximum Authorized Altitudes(MAAs),Minimum Crossing Altitudes(MCAs),Minimum Reception Altitudes(MRAs),and Route Minimum Off-Route Altitudes

28、(Route MORAs.These minimum altitudes for airways are not displayed in most avionics systems.8.6.4 Changeover PointsChangeover points(other than mid-point between navaids)are on charts but are not included in the Jeppesen NavData database.8.7 Arrivals&DeparturesProceduresArrivals&Departures Procedure

29、s Not in the DatabaseProcedure Titles400-Foot ClimbsTake-off Minimums and Climb Gradients“Expect”and“Conditional”InstructionsAltitudesSTAR Overlapping Segments 8.7.1 Arrivals&Departures Procedures Not in the DatabaseJeppesen publishes some officially designated departure procedures that include only

30、 text on IFR airport charts beneath the take-off minimums.They may be labeled“Departure Procedure”,“IFR Departure Procedure”,or“Obstacle DP”.Most of these are U.S.and Canadian procedures,although there is a scattering of them throughout the world.Any waypoint/fix mentioned in the text is in the Jepp

31、esen NavData database.However,these text-only departure procedures are not in the database.Some States publish narrative descriptions of their arrivals,and depict them on their enroute charts.They are unnamed,not identified as arrival routes,and are not included in the Jeppesen NavData database.Some

32、 States publish“DME or GPS Arrivals”,and because they are otherwise unnamed,they are not included in the database.8.7.2 Procedure TitlesProcedure identifiers for routes such as STARs,DPs and SIDs are in airborne databases but are limited to not more than six alpha/numeric characters.The database gen

33、erally uses the charted computer code(shown enclosed within parentheses on the chart)for the procedure title.For example:CHART:Cyote Four Departure (CYOTE.CYOTE4)DATABASE:CYOTE4When no computer code is assigned,the name is truncated to not more than six characters.The database procedure identifier i

34、s created according to ARINC 424 specifications.Database procedure identifiers are charted in most cases.They are the same as the assigned computer code(charted within parentheses)or are being added enclosed within square brackets.Do not confuse the bracketed database identifier with the official pr

35、ocedure name(which will be used by ATC)or the official computer code(which is used in flight plan filing).8.7.3 400-Foot ClimbsVirtually all departures in the database include a climb to 400 feet above the airport prior to turning because of requirements in State regulations and recommendations.The

36、400-foot climb is not depicted on most charts.When States specify a height other than 400 feet,it will be in the Jeppesen NavData database.8.7.4 Take-off Minimums and Climb GradientsThe take-off minimums and climb gradients that are depicted on the charts are not included in the database.8.7.5“Expec

37、t”and“Conditional”InstructionsAltitudes depicted on charts as“Expect”instructions,such as“Expect to cross at 11,000,”are not included in the Jeppesen NavData database.When“Conditional”statements,such as“Straight ahead to ABC 8 DME or 600,whichever is later”,are included on the charts,only one condit

38、ion can be included in the database.8.7.6 AltitudesDatabases include charted crossing altitudes at waypoints/fixes.Charted Minimum Enroute Altitudes(MEAs)and Minimum Obstacle Clearance Altitudes(MOCAs)are not included.8.7.7 STAR Overlapping SegmentsSTARs normally terminate at a fix where the approac

39、h begins or at a fix where radar vectoring will begin.When STAR termination points extend beyond the beginning of the approach,some avionics equipment may display a route discontinuity at the end of the STAR and the first approach fix.8.8 Titles&Omitted Procedures of Approach ProcedureICAO PANS OPS

40、approach procedure titles are officially labeled with the navaid(s)used for the approach and are different than approach procedure titles labeled according to the TERPs criteria,which are labeled only with navaids required for the final approach segment.Because of the limited number of characters th

41、at are available for the procedure title,the name displayed on the avionics equipment may not be the same as the official name shown on the Approach Chart.The Jeppesen NavData database,in accordance with ARINC 424 specifications,codes the approach procedure according to procedure type and runway num

42、ber.“Similar”type approaches to the same runway may be combined under one procedure title.The actual avionics readout for the procedure title varies from manufacturer to manufacturer.Some avionics systems cannot display VOR and VOR DME(or NDB and NDB DME)approaches to the same runway,and the approac

43、h displayed will usually be the one associated with DME.Generally,most Cat I,II,and III ILS approaches to the same runway are the same basic procedure,and the Cat I procedure is in the database.However,in isolated cases,the Cat I and Cat II/III missed approach procedures are different,and only the C

44、at I missed approach will be in the database.Additionally,there may be ILS and Converging ILS approaches to the same runway.While the converging ILS approaches are not currently in the database,they may be at some later date.Some States are using the phonetic alphabet to indicate more than one“same

45、type,same runway”approach,such as ILS Z Rwy 23 and ILS Y Rwy 23.The phonetic alphabet starts at the end of the alphabet to ensure there is no possibility of conflict with circling only approaches,such as VOR A.In isolated cases,procedures are intentionally omitted from the database.This occurs prima

46、rily when navaid/waypoint coordinates provided by the authorities in an undeveloped are inaccurate and no resolution can be obtained.Additionally,the ARINC 424 specifications governing navigation databases may occasionally prohibit the inclusion of an approach procedure.8.9 Plan View Of Approach Pro

47、cedureInitial Approach Fix(IAF),Intermediate Fix(IF),Final Approach Fix(FAF)DesignationsBase Turn(Teardrop)ApproachesRoutes By Aircraft CategoriesDME and Along Track DistancesApproach Transition to Localizer 8.9.1 Initial Approach Fix(IAF),Intermediate Fix(IF),Final Approach Fix(FAF)DesignationsThes

48、e designations for the type of fix for operational use are included on approach charts within parentheses when specified by the State,but are not displayed on most avionics systems.ARINC 424 and TSO C-129 specifications require the inclusion of GPS approach transitions originating from IAFs.Authorit

49、ies do not always standardize the assignment of IAFs,resulting in some cases of approach transitions being included in the database that do not originate from officially designed IAFs.8.9.2 Base Turn(Teardrop)ApproachesDepending upon the divergence between outbound and inbound tracks on the base tur

50、n(teardrop turn),the turn rate of the aircraft,the intercept angle in the database,and the wind may cause an aircraft to undershoot the inbound track when rolling out of the turn,thus affecting the intercept angle to the final approach.This may result in intercepting the final approach course either