杰普遜航圖與導航數(shù)據(jù)庫 第八章課件

Chapter8

DifferencesBetweenJeppesenDatabase&ChartsChapter8

DifferencesBetwee1Chapter8DifferencesBetweenJeppesenDatabase&Charts§8.1Introduction§8.2AeronauticalInformationCut-offDates&EffectiveDates§8.3GeneralDifferences§8.4Navaids§8.5Waypoints§8.6Airways§8.7Arrivals&DeparturesProceduresChapter8DifferencesBetween2§8.8Titles&OmittedProceduresofApproachProcedure

§8.9PlanViewOfApproachProcedure§8.10ProfileOfApproachProcedures

§8.11ApproachProcedures

§8.12RoutesOnChartsButNOTInDatabases§8.13FinalCockpitAuthority,ChartsOrDatabase§8.8Titles&OmittedProced3§8.1IntroductionThebasicdesignformostaeronauticalinformationcontainedininstrumentprocedureshasbeencreatedfortheanalogworld.VirtuallyalltheaeronauticaldatabasesareloadedaccordingtothespecificationsintheAeronauticalRadio,Incorporated(ARINC)424standard“NavigationDatabases.”§8.1IntroductionThebasicde4Manyofthedifferencesbetweenchartsanddatabasesarebecausetherecanbenostandardimplementedtohavetheinformationinbothplacesdepictedthesame.Therearesomecaseswhereitisdesirablenottohavetheinformationthesamebecauseofthedifferenttypeofmediawheretheinformationisdisplayed.Manyofthedifferencesbetwee5TherearemanydifferenttypesofavionicsequipmentutilizingtheJeppesenNavDatadatabase.Thesamedatabaseinformationmaybepresenteddifferentlyondifferenttypesofairborneequipment.

Inaddition,someequipmentmaybelimitedtospecifictypesofdatabaseinformation,omittingotherdatabaseinformation.PilotsshouldchecktheirOperatingHandbooksfordetailsofoperationandinformationpresentation.Therearemanydifferenttypes6Amajorfactorin“apparent”differencesbetweendatabaseandchartsmaybeduetotheavionicsequipmentutilized.Asavionicsequipmentevolves,thenewersystemswillbemorecompatiblewithcharts,howevertheoldersystemswillstillcontinuewithapparentdifferences.Amajorfactorin“apparent”d7§8.2AeronauticalInformationCut-offDates&EffectiveDatesTheICAOAeronauticalInformationRegulationandControl(AIRAC)governsthe28-daycyclebetweeneffectivedatesofaeronauticalinformation.Chartstypicallyuse7-dayand14-daycyclesforterminalchartsand28-dayand56-daycyclesforEnrouteandAreacharts.§8.2AeronauticalInformation8§8.3GeneralDifferencesChartedInformationNotProvidedintheJeppesenNavdataDatabaseMagneticCourses,DistancesReferenceDatum§8.3GeneralDifferencesChar9§8.3.1ChartedInformationNotProvidedintheJeppesenNavdataDatabaseNotalltheinformationthatisincludedonthechartsisincludedintheairbornedatabase.Thefollowingisagenerallistingofsomeofthoseitems:AltimetryQNH/QFEinformationAlternatealtimetersettingsourcesIntersectionformations(radials,bearings,DME)§8.3.1ChartedInformationNo10TerrainandObstaclesAirportOperatingMinimumsLanding,take-offandalternateminimumsAirporttaxiwaysandrampsSometypesofspecialuseairspaceandcontrolledairspaceTerrainandObstacles11§8.3.2MagneticCourses,DistancesBecauseofdifferentmagneticmodelsusedinairbornesystems,amagneticcoursereadontheairbornesystemmaydifferfromthechartedmagneticcourse.Avionicscomputeddistancesmaydisagreewithcharteddistances.DifferencesmayappearonairwaysonEnrouteCharts,andonflightproceduresincludedonSID,DP,STAR,Approach,andAirportcharts.§8.3.2MagneticCourses,Dist12Inaddition,whenthedatabaserequiresaspecificcoursetobeflownfrom“A”to“B”,thedifferencesinmagneticvariationorVORstationdeclinationmayresultina“jog”betweenthetwofixesinlieuofadirecttrack.Inaddition,whenthedatabase13§8.3.3ReferenceDatumNotallStates(countries)havecompliedwiththeICAOAnnexthatspecifiestheuseoftheWGS-84referencedatum.Differencesinreferencedatumscancausesignificant“accuracybias”inthenavigationguidanceprovidedbyavionicssystems.§8.3.3ReferenceDatumNotall14§8.4NavaidsCompletenessNDBandLocatorIdentifiersLocatorIdentifiersDuplicateNavaidIdentifiers§8.4NavaidsCompleteness15§8.4.1CompletenessBecauseoftheduplicationofidentifiersandotherfactors,notallchartednavaidsareincludedinthedatabase.§8.4.1CompletenessBecauseof16§8.4.2NDBandLocatorIdentifiersAsanexampleofthedifferencesbetweenthedisplayfromoneavionicssystemtoanother:someavionicssystemswilldisplaytheFoleyNDBas“FPY”.Someavionicssystemsincludeasuffix“NB”aftertheNDBidentifiersandwilldisplaytheFoleyNDBas“FPYNB”.§8.4.2NDBandLocatorIdenti17ForNDBsandlocatorswithduplicateMorsecodeidentifiersthatarelocatedwithinthesameState(country),mayonlybeavailableusingtheairportidentifierforaccess.ForNDBsandlocatorswithdup18§8.4.3LocatorIdentifiersMostlocatorsintheUnitedStateshaveuniquefive-letternames,butmostinternationallocatorshavenamesthatdonothavefiveletters.SomesystemsmaydisplayU.S.locatorsas“CASSE”.SomesystemsmaydisplayU.S.locatorsas“AP”.§8.4.3LocatorIdentifiersMos19§8.4.4DuplicateNavaidIdentifiers

Therearenumerousduplicatesinthedatabase.Refertoyouravionicshandbookfortheproperproceduretoaccessnavaidswhenduplicateidentifiersareinvolved.Notallnavaidsinthedatabaseareaccessiblebytheiridentifier.Somenavaids,forreasonssuchasduplicationwithinterminalareasorlackofcompleteinformationaboutthenavaid,areinthewaypointfileandareaccessiblebytheirnameorabbreviatedname.§8.4.4DuplicateNavaidIdent20§8.5WaypointsWaypointDatabaseIdentifiersCommonWaypointNameforaSingleLocationFly-overVersusFly-byFixes/Waypoints§8.5WaypointsWaypointDataba21§8.5.1WaypointDatabaseIdentifiers“DatabaseIdentifiers”referstoidentifiersusedonlyinavionicssystemsutilizingdatabases.TheidentifiersarenotforuseinflightplansorATCcommunications;however,theyarealsoincludedincomputerflightplanningsystems.TheymaybedesignatedbytheState(country)as“ComputerNavigationFixes”(CNFs)ordesignatedbyJeppesen.§8.5.1WaypointDatabaseIden22Tofacilitatetheuseofairborneavionicssystems,theidentifiersarebeingaddedtoJeppesen’scharts.BoththeCNFscreatedbyStatesandtheJeppesen-createddatabaseidentifiersareenclosedwithinsquarebracketsandinitalics.Jeppesen’sultimategoalistoincludealldatabaseidentifiersforallwaypoints/fixesonthecharts.Tofacilitatetheuseofairbo23Enroutechartsincludethefive-characteridentifierforunnamedreportingpoints,DMEfixes,mileagebreaks,andanyreportingpointwithanamethathasmorethanfivecharacters.Enroutechartsincludethefiv24SID,DPandSTARchartsarebeingmodifiedtoincludeallidentifiers.ApproachChartsSID,DPandSTARchartsarebe25VNAVdescentangleinformationderivedfromtheJeppesenNavDatadatabaseisbeingaddedtoapproachcharts.IdentifiersareshownfortheFinalApproachFix(FAF),MissedApproachPoint(MAP),andthemissedapproachterminationpoint.VNAVdescentangleinformation26State-namedComputerNavigationFixes(CNFs)areshownonallapplicablecharts.GPS(GNSS)typeApproachChartsincludealldatabaseidentifiers.State-namedComputerNavigatio27§8.5.2CommonWaypointNameforaSingleLocationGovernmentauthoritiesmaygiveanametoawaypointatagivenlocation,butnotusethenameatthesamelocationonotherproceduresinthesamearea.TheJeppesenNavDatadatabaseusesthesamenameforallmultipleprocedureapplications.Chartingislimitedtotheprocedure(s)wherethenameisusedbytheauthorities.§8.5.2CommonWaypointNamef28§8.5.3Fly-overVersusFly-byFixes/WaypointsInmostcases,pilotsshouldanticipateandleadaturntothenextleg.Thedatabaseindicateswhenthefixmustbecrossed(flown-over)beforetheturniscommenced.Thefixiscodedasfly-overwhentherequirementisinferredorisspecifiedbythegoverningauthority.Fixesarechartedasfly-overfixesonlywhenspecifiedbythegoverningauthority.§8.5.3Fly-overVersusFly-by29Fly-overfixeshaveacirclearoundthefix/waypointsymbol.Nospecialchartingisusedforfly-byfixes.Fly-overfixeshaveacirclea30§8.6AirwaysATSRoutesDesignatorsAltitudesChangeoverPoints§8.6AirwaysATSRoutes31§8.6.1ATSRoutes

AirwaysidentifiedasATCroutesbyStates(countries)cannotbeuniquelyidentified.TheyarenotincludedintheJeppesenNavDatadatabase.§8.6.1ATSRoutes

Airwayside32§8.6.2DesignatorsJeppesenNavDatadatabaseairwaydesignatorsarefollowedbyacodeindicatingATCservices(suchas“A”forAdvisory,“F”forFlightInformation)whensuchacodeisspecifiedbytheState(country).NotallairbornesystemsdisplaytheATCservicessuffix.§8.6.2DesignatorsJeppesenNa33§8.6.3AltitudesMinimumEnrouteAltitudes(MEAs),MinimumObstacleClearanceAltitudes(MOCAs),OffRouteObstacleClearanceAltitudes(OROCAs),MaximumAuthorizedAltitudes(MAAs),MinimumCrossingAltitudes(MCAs),MinimumReceptionAltitudes(MRAs),andRouteMinimumOff-RouteAltitudes(RouteMORAs.Theseminimumaltitudesforairwaysarenotdisplayedinmostavionicssystems.§8.6.3AltitudesMinimumEnrou34§8.6.4ChangeoverPointsChangeoverpoints(otherthanmid-pointbetweennavaids)areonchartsbutarenotincludedintheJeppesenNavDatadatabase.§8.6.4ChangeoverPointsChang35§8.7Arrivals&Departures

ProceduresArrivals&DeparturesProceduresNotintheDatabaseProcedureTitles400-FootClimbsTake-offMinimumsandClimbGradients“Expect”and“Conditional”InstructionsAltitudesSTAROverlappingSegments§8.7Arrivals&Departures

Pr36§8.7.1Arrivals&DeparturesProceduresNotintheDatabaseJeppesenpublishessomeofficiallydesignateddepartureproceduresthatincludeonlytextonIFRairportchartsbeneaththetake-offminimums.Theymaybelabeled“DepartureProcedure”,“IFRDepartureProcedure”,or“ObstacleDP”.MostoftheseareU.S.andCanadianprocedures,althoughthereisascatteringofthemthroughouttheworld.§8.7.1Arrivals&Departures37Anywaypoint/fixmentionedinthetextisintheJeppesenNavDatadatabase.However,thesetext-onlydepartureproceduresarenotinthedatabase.Anywaypoint/fixmentionedin38SomeStatespublishnarrativedescriptionsoftheirarrivals,anddepictthemontheirenroutecharts.Theyareunnamed,notidentifiedasarrivalroutes,andarenotincludedintheJeppesenNavDatadatabase.SomeStatespublish“DMEorGPSArrivals”,andbecausetheyareotherwiseunnamed,theyarenotincludedinthedatabase.SomeStatespublishnarrative39§8.7.2ProcedureTitlesProcedureidentifiersforroutessuchasSTARs,DPsandSIDsareinairbornedatabasesbutarelimitedtonotmorethansixalpha/numericcharacters.Thedatabasegenerallyusesthechartedcomputercode(shownenclosedwithinparenthesesonthechart)fortheproceduretitle.§8.7.2ProcedureTitlesProced40Forexample:

CHART:CyoteFourDeparture(CYOTE.CYOTE4)

DATABASE:CYOTE4Forexample:41Whennocomputercodeisassigned,thenameistruncatedtonotmorethansixcharacters.ThedatabaseprocedureidentifieriscreatedaccordingtoARINC424specifications.Whennocomputercodeisassig42Databaseprocedureidentifiersarechartedinmostcases.Theyarethesameastheassignedcomputercode(chartedwithinparentheses)orarebeingadded[enclosedwithinsquarebrackets].Donotconfusethebracketeddatabaseidentifierwiththeofficialprocedurename(whichwillbeusedbyATC)ortheofficialcomputercode(whichisusedinflightplanfiling).Databaseprocedureidentifiers43§8.7.3400-FootClimbsVirtuallyalldeparturesinthedatabaseincludeaclimbto400feetabovetheairportpriortoturningbecauseofrequirementsinStateregulationsandrecommendations.The400-footclimbisnotdepictedonmostcharts.WhenStatesspecifyaheightotherthan400feet,itwillbeintheJeppesenNavDatadatabase.§8.7.3400-FootClimbsVirtual44§8.7.4Take-offMinimumsandClimbGradientsThetake-offminimumsandclimbgradientsthataredepictedonthechartsarenotincludedinthedatabase.§8.7.4Take-offMinimumsand45§8.7.5“Expect”and“Conditional”Instructions

Altitudesdepictedonchartsas“Expect”instructions,suchas“Expecttocrossat11,000,”arenotincludedintheJeppesenNavDatadatabase.§8.7.5“Expect”and“Conditio46When“Conditional”statements,suchas“StraightaheadtoABC8DMEor600",whicheverislater”,areincludedonthecharts,onlyoneconditioncanbeincludedinthedatabase.When“Conditional”statements,47§8.7.6AltitudesDatabasesincludechartedcrossingaltitudesatwaypoints/fixes.ChartedMinimumEnrouteAltitudes(MEAs)andMinimumObstacleClearanceAltitudes(MOCAs)arenotincluded.§8.7.6AltitudesDatabasesinc48§8.7.7STAROverlappingSegments

STARsnormallyterminateatafixwheretheapproachbeginsoratafixwhereradarvectoringwillbegin.WhenSTARterminationpointsextendbeyondthebeginningoftheapproach,someavionicsequipmentmaydisplayaroutediscontinuityattheendoftheSTARandthefirstapproachfix.§8.7.7STAROverlappingSegme49§8.8Titles&OmittedProceduresofApproachProcedureICAOPANSOPSapproachproceduretitlesareofficiallylabeledwiththenavaid(s)usedfortheapproachandaredifferentthanapproachproceduretitleslabeledaccordingtotheTERPscriteria,whicharelabeledonlywithnavaidsrequiredforthefinalapproachsegment.Becauseofthelimitednumberofcharactersthatareavailablefortheproceduretitle,thenamedisplayedontheavionicsequipmentmaynotbethesameastheofficialnameshownontheApproachChart.§8.8Titles&OmittedProcedu50TheJeppesenNavDatadatabase,inaccordancewithARINC424specifications,codestheapproachprocedureaccordingtoproceduretypeandrunwaynumber.“Similar”typeapproachestothesamerunwaymaybecombinedunderoneproceduretitle.Theactualavionicsreadoutfortheproceduretitlevariesfrommanufacturertomanufacturer.TheJeppesenNavDatadatabase,51SomeavionicssystemscannotdisplayVORandVORDME(orNDBandNDBDME)approachestothesamerunway,andtheapproachdisplayedwillusuallybetheoneassociatedwithDME.Generally,mostCatI,II,andIIIILSapproachestothesamerunwayarethesamebasicprocedure,andtheCatIprocedureisinthedatabase.However,inisolatedcases,theCatIandCatII/IIImissedapproachproceduresaredifferent,andonlytheCatImissedapproachwillbeinthedatabase.Someavionicssystemscannotd52Additionally,theremaybeILSandConvergingILSapproachestothesamerunway.WhiletheconvergingILSapproachesarenotcurrentlyinthedatabase,theymaybeatsomelaterdate.SomeStatesareusingthephoneticalphabettoindicatemorethanone“sametype,samerunway”approach,suchasILSZRwy23andILSYRwy23.Thephoneticalphabetstartsattheendofthealphabettoensurethereisnopossibilityofconflictwithcirclingonlyapproaches,suchasVORA.Additionally,theremaybeILS53Inisolatedcases,proceduresareintentionallyomittedfromthedatabase.Thisoccursprimarilywhennavaid/waypointcoordinatesprovidedbytheauthoritiesinanundevelopedareinaccurateandnoresolutioncanbeobtained.Additionally,theARINC424specificationsgoverningnavigationdatabasesmayoccasionallyprohibittheinclusionofanapproachprocedure.Inisolatedcases,procedures54§8.9PlanViewOfApproachProcedureInitialApproachFix(IAF),IntermediateFix(IF),FinalApproachFix(FAF)DesignationsBaseTurn(Teardrop)ApproachesRoutesByAircraftCategoriesDMEandAlongTrackDistancesApproachTransitiontoLocalizer§8.9PlanViewOfApproachPr55§8.9.1InitialApproachFix(IAF),IntermediateFix(IF),FinalApproachFix(FAF)DesignationsThesedesignationsforthetypeoffixforoperationaluseareincludedonapproachchartswithinparentheseswhenspecifiedbytheState,butarenotdisplayedonmostavionicssystems.§8.9.1InitialApproachFix(56ARINC424andTSOC-129specificationsrequiretheinclusionofGPSapproachtransitionsoriginatingfromIAFs.AuthoritiesdonotalwaysstandardizetheassignmentofIAFs,resultinginsomecasesofapproachtransitionsbeingincludedinthedatabasethatdonotoriginatefromofficiallydesignedIAFs.ARINC424andTSOC-129specif57§8.9.2BaseTurn(Teardrop)Approaches

Dependinguponthedivergencebetweenoutboundandinboundtracksonthebaseturn(teardropturn),theturnrateoftheaircraft,theinterceptangleinthedatabase,andthewindmaycauseanaircrafttoundershoottheinboundtrackwhenrollingoutoftheturn,thusaffectingtheinterceptangletothefinalapproach.ThismayresultininterceptingthefinalapproachcourseeitherbeforeoraftertheFinalApproachFix(FAF).§8.9.2BaseTurn(Teardrop)A58§8.9.3RoutesByAircraftCategoriesSomeproceduresaredesignedwithasetofflighttracksforCategoryA&BaircraftandwithadifferentsetofflighttracksforCategoryC&D.Insuchcases,thedatabasegenerallyincludesonlytheflighttracksforCategoryC&D.§8.9.3RoutesByAircraftCat59§8.9.4DMEandAlongTrackDistancesDatabaseidentifiersareassignedtomanyunnamedDMEfixes.TheJeppesenidentifierischartedonGPS/GNSStypeapproachesandchartedonanytypeapproachwhenspecifiedasacomputernavigationfix(CNF).§8.9.4DMEandAlongTrackDi60UnnamedAlongTrackDistances(ATDs)arechartedasaccumulativedistancestotheMAP.UnnamedAlongTrackDistances61§8.9.5ApproachTransitiontoLocalizerForDMEarcapproachtransitionswithlead-inradials,thefixatthetransition“terminationpoint”beyondthelead-inradialisdroppedbymanyavionicssystems.§8.9.5ApproachTransitionto62§8.10ProfileOfApproachProceduresVerticalDescentAnglesDatabaseIdentifiersFinalApproachCaptureFix(FACF)GPS/GNSSSensorFAFFinalApproachFix(FAF),ILSandLocalizerApproachesNamedandUn-namedStepdownFixesILSandRunwayAlignment§8.10ProfileOfApproachPro63§8.10.1VerticalDescentAnglesVerticaldescentanglesformoststraight-innon-precisionlandings(Descentanglesforcircle-to-landonlyapproachesarecurrentlynotinthedatabaseandarenotcharted.)

areincludedinthedatabaseandpublishedonchartswiththefollowingexceptions:Whenprecisionandnon-precisionapproachesarecombinedonthesamechart§8.10.1VerticalDescentAngl64SomeproceduresbasedonPANSOPScriteriawithdescentgradientspublishedinpercentageorinfeetperNM/metersperkilometer.However,thesevaluesarebeingconvertedintoanglesandarebeingcharted.SomeproceduresbasedonPANS65IntheUnitedStates,manynon-precisionapproacheshavedescentanglesprovidedbytheFAAandaredepictedontheapproachcharts.IntheUnitedStates,manynon66FormanyoftheU.S.procedures,andinothercountries,thedescentanglesarecalculatedbasedonthealtitudesanddistancesprovidedbytheStateauthorities.ThesedescentanglesarebeingaddedtoJeppesen’scharts.FormanyoftheU.S.procedure67Thedescentangleaccuracymaybeaffectedbytemperature.Whentheoutsideairtemperatureislowerthanstandard,theactualdescentanglewillbelower.

Thedescentangleaccuracymay68§8.10.2DatabaseIdentifiersForapproachchartswherethedescentangleispublished,alldatabaseidentifiersfromtheFinalApproachFix(FAF)tothemissedapproachterminationpointarechartedinboththeplanandprofileviews.WhenanFAFisnotspecified,theNavDatadatabaseSensorFinalApproachFix(SensorFAF)isincludedinthedatabaseandischarted.§8.10.2DatabaseIdentifiersF69§8.10.3FinalApproachCaptureFix(FACF)

Databasesinclude(whennosuitablefixisspecifiedinsource)aFACFforlocalizerbasedapproachesandthosebasedonVORDME,VORTAC,orNDBandDME.Inmostcases,itisthefixidentifiedastheintermediatefix.TheFACFischartedonlywhenspecifiedbytheState.§8.10.3FinalApproachCaptur708.10.4GPS/GNSSSensorFAFTheJeppesenNavDatadatabaseincludesaSensorFAFwhentheapproachwasnotoriginallydesignedwithanFAF,andtheyarechartedon“GPS/GNSStype”approaches.8.10.4GPS/GNSSSensorFAFThe71§8.10.5FinalApproachFix(FAF),ILSandLocalizerApproachesTheremaybeseveraltypesoffixeschartedatthesameFAFlocation-locator,waypoint,intersection,DMEfix,OM,orperhapsanNDBinsteadofalocator.Sincemanyairbornenavigationsystemswithdatabasesdon’tstorelocatorsandNDBsasnavaids,afour-orfive-characteridentifierwillbeusedfortheFAFonILSandlocalizerapproaches.Thefour-orfive-characteridentifierassignedtotheFAFlocationiscontainedinthewaypointfileoftheJeppesenNavDatadatabase.§8.10.5FinalApproachFix(F72IfthereisanamedintersectionorwaypointonthecenterlineofthelocalizerattheFAF,thenameofthefixwillbeusedfortheFAFlocation.TheFAFmustbeonthelocalizercenterlineortheavionicssystemwillflyacoursethatisnotstraight.Frequently,OMsandLOMsarenotpositionedexactlyonalocalizercenterlineandadatabasefixiscreatedtoputtheaircraftonastraightcourse.Ifthereisanamedintersecti73WhentheLOMisonthecenterlineandtherealsoisanamedintersectionorwaypointonthecenterline,thenameoftheintersectionorwaypointwillbeusedfortheFAF.WhentheLOMisonthecenterl74WhentheILSorlocalizerprocedureisbeingflownfromthedatabase,thefour-orfive-characternameoridentifiersuchasCHUPP,FF04,orFF04R,etc.willbedisplayedastheFAF.IftheLOMisnotonthelocalizercenterline,anidentifiersuchasFF04Lmaybetheidentifierforthecomputed“oncenterline”finalapproachfixforrunway04L.IfthereisonlyanoutermarkerattheFAF,theFAFidentifiermaybeOM04L.WhentheILSorlocalizerproc75WhenthereisnointersectionorwaypointattheFAFsuchastheMONRYLOM,thedatabaseidentifierwillbe“OM09”iftheLOMisonthecenterline,and“FF09”iftheLOMisnotonthecenterline.Whenthereisnointersection76Insomesystems,toaccessthelocatoronmostILSandlocalizerapproaches,theMorsecodeidentifiercanbeused.IntheUnitedStates,virtuallyalllocatorshaveafive-letteruniquename/identifiersothelocationcanusuallybeaccessedinsomesystemsbythenavaidMorsecodeidentifierorthefive-lettername.Insomesystems,thelocatorisaccessedbythenameorbyaddingtheletters“NB”totheMorsecodeidentifier.Insomesystems,toaccessthe77§8.10.6NamedandUn-namedStepdownFix

Namedandun-namedstepdownfixesbetweentheFAFandMAParecurrentlynotincludedinthedatabases,butwillbeaddedinthefuture.TheyareoftenDMEfixes,andinthosecases,canbeidentifiedbyDME.ThedistancetogototheMAPmaybelabeledonsomeGPS/GNSStypechartsandVORDMERNAVcharts.Properidentificationofthesedisplayedfixesisnecessarytoclearallstepdownfixcrossingaltitudes.§8.10.6NamedandUn-namedS78杰普遜航圖與導航數(shù)據(jù)庫第八章課件79§8.10.7ILSandRunwayAlignmentDifferencesingovernmentspecifiedvaluesforlocalizerandairportvariationmaycauseapparentnon-alignmentofthelocalizerandtherunway.Thesedifferencesaregraduallybeingresolved,andwheneverpossibletheairportvariationisusedforthelocalizervariation.§8.10.7ILSandRunwayAlignm808.11ApproachProcedures(MissedApproach)MissedApproachPoint(MAP)400-FootClimbsMissedApproachProcedure8.11ApproachProcedures(Mis81§8.11.1MissedApproachPoint(MAP)Fornon-precisionapproaches,whentheMAPisotherthananavaid,therewillbeadatabaseMAPwaypointwithauniqueidentifier.IftheMAPisawaypointandisatorwithin0.14NMofthethresholdtheMAPidentifierwillbetherunwaynumber.§8.11.1MissedApproachPoint82IftheMAPisnotattherunway,therewilleitherbeanofficialnameoranidentifierfortheMAP,oranidentifierisprovided.GPS/GNSStypeapproachesandchartswithdescentangles,includethedatabaseidentifieroftheMAP.IftheMAPisnotattherunwa83§8.11.2400-FootClimbsThedatabaseincludesaclimbto400feetabovetheairportpriortoturningonamissedapproach.Thisclimbisnotpartoftheofficialprocedure,butdoescomplywithStateregulationsandpolicies.Thisspecificclimbto400feetisnotincludedoncharts.ThemissedapproachtextsuppliedbytheStateauthorityischarted.§8.11.2400-FootClimbsTheda84杰普遜航圖與導航數(shù)據(jù)庫第八章課件85§8.11.3MissedApproachProcedureTheroutes/pathsthatcompriseamissedapproacharenotalwaysdisplayedinsomeavionicssystemsthatusedatabases.Additionally,someavionicssystemsthatincludemissedapproachproceduresdon’talwaysimplementafullsetofpathterminatorssomanylegswillnotbeincludedintheairbornedatabase.§8.11.3MissedApproachProce86Refertothechartedmissedapproachprocedurewhenexecutingamissedapproach.Refertothechartedmissedap87§8.12RoutesOnChartsButNOTInDatabasesTheroutesinapproachprocedures,SIDs,DPs,andSTARsarecodedintothedatabaseusingcomputercodescalledpathterminatorswhicharedefinedintheARINC424NavigationDatabaseSpecification.Apathterminator:DefinesthepaththroughtheairDefinesthewaytheleg(orroute)isterminated.§8.12RoutesOnChartsButNOT88NotallavionicssystemshaveimplementedthefullsetofpathterminatorsspecifiedintheARINC424document.Iftheavionicssystemsdon’thavealltheroutes,ordon’thavethemeanstodisplaythem,itisthepilot’sresponsibilitytoflytheroutesdepictedonthecharts.Notallavionicssystemshave898.13FinalCockpitAuthority,ChartsOrDatabaseTherearedifferencesbetweeninformationdisplayedonyourairborneavionicsnavigationsystemandtheinformationshownonJeppesencharts.Thecharts,supplementedbyNOTAMs,arethefinalauthority.8.13FinalCockpitAuthority,90EndEnd91Chapter8

DifferencesBetweenJeppesenDatabase&ChartsChapter8

DifferencesBetwee92Chapter