arinc leg types

7/24/2019 Arinc Leg Types

http://slidepdf.com/reader/full/arinc-leg-types 1/67

10-11-12-13 September 2002-Morocco ARAB INSTRUMENT PROCEDURE DESIGN SEMINAR

Navigation & flight planning Navigation & flight planning

by FMS-equipped aircraft by FMS-equipped aircraft

AI/EE-A 441.0144/01



Table of contentsTable of contentsP.3 Navigation & flight anageent

P.! "n overvie# of aircraft avionics

P.$ %PS P'M"( navigation

P.) NP navigation

P.*+ Flight anageent

P.11 Flight planning

P.12 Vertical navigation

P.*3 Navigation database , "'N !! forat

P.*! Path terinator concept

P.15 IF leg type

P.16 TF leg type

P.17 RF leg type (new leg type)

P.18 F leg type

P.1! "F leg type

P.2# F$ leg type

P.21 F leg type

P.22 F" leg type

P.2% F& leg type

P.2' $ leg type

P.25 " leg type

P.26 I leg type

P.27 R leg type

P.28 $F leg type

P.2! V$ leg type

P.%# V" leg type

P.%1 VI leg type

P.%2 V& leg type

P.%% VR leg type

P.%' PI leg type

P.%5 $ F & leg type*

P.3/ "'N !! leg transitions

P.30 Navigation database related issues

P.3) opatibili ty.. .

P.31 Production process

P.!+ Soe top level issues

P.!! ecoendations

P.!$ 'ssues suary

P.!/ Short ter

P.$ Mediu ter

P.$! 2onger ter




Navigation & flight anageent Navigation & flight anageent



"n overvie# of aircraft avionics ..."n overvie# of aircraft avionics ... Modern avionics have considerably iproved flight safety on

non-precision approaches ,

accurate position NP +.34 flight plan display on 5F'S

reference approach path

autoated lateral guidance

autoated vertical guidance ground pro6iity #arning syste %P7S4

terrain display on 5F'S 5%P7S4

terrain clearance floor #arnings 5%P7S4



"n overvie# of aircraft avionics ..."n overvie# of aircraft avionics ...

700’

AGL500’ AGL

5 NM 12 NM15 NM

3 d e g r e

e s



%PS P'M"( navigation%PS P'M"( navigation "'89S is prooting %PS P'M"( navigation

"ll ne# "3*):"3*1:"3+:"3*:"33+:"3!+ production

aircraft are fitted #ith %PS P'M"( capable equipent %round navaids are only used as a bac;up

<=> ?M5

"?F is not used for navigation only for procedural navigation chec;



@ybrid "3+ faily & "3!+ faily4

"'89S syste %PS architecture"'89S syste %PS architecture

MMR

or

GPSSU

ADIRS FMS

IRS position

GPIRS position

GPS ra data

GPS positionFMS position

!GP"S



"utonoous "3++-/++:"3*+ faily> retrofit solution

for "3+ faily #ith older "?'S4

"'89S syste %PS architecture"'89S syste %PS architecture

MMR

IRS

FMS

IRS position

GPS position

FMS position

!GP"S



'n %PS P'M"( ode> on-board syste integrity has

a confidence greater than 11.1A> so the FMS position

can be relied upon #ithout any additional navigationcross chec; using ground based navaids4

lear status of %PS P'M"( is therefore provided to

the cre#

%PS P'M"( cre# interface%PS P'M"( cre# interface



GPS PRIMAR# L$S%GPS PRIMAR#

%PS P'M"( cre# interface%PS P'M"( cre# interface

CLB FLT4567890 CRZ OPT REC MAXFL350 FL370 FL390

<REPORT UPDATE AT*[ ] BRG /DIT !!!" /!!!!#! TO [ ] PREDICTI$E<GP GP PRIMAR%RE&UIRED ACCUR ETIMATED '#()M IG 0#(6)M

GP PRIMAR%


<REPORT UPDATE AT*[ ] BRG /DIT !!!" /!!!!#! TO [ ] PREDICTI$E<GPRE&UIRED ACCUR ETIMATED '#()M IG 0#'8)M

GP PRIMAR% LOT

& trip'e ('i() d*ring approa(+



NP navigationNP navigation "'89S is prooting NP required navigation

perforance4

"ll "3*):"3*1:"3+:"3*:"33+:"3!+ aircraft are

fitted or have been retrofitted #ith NP capable

equipent

NP allo#s cre# a#areness of estiated aircraft position accuracy copared to procedure designerBs

required perforance assuptions



NAV ACCUR UPGRAD

NP anageent provides @'%@ and 2=7 navigation

accuracy syste onitoring against the equired

Navigation Perforance The syste estiated accuracy has a 1$A confidence

NP cre# interfaceNP cre# interface



NAV ACCUR UPGRAD NAV ACCUR DOWNGRAD

NP cre# interfaceNP cre# interface


<REPORT UPDATE AT*[ ] BRG /DIT !!!" /!!!!#! TO [ ] PREDICTI$E<GPRE&UIRED ACCUR ETIMATED 0#3)M IG 0#'8)M)A$ ACCUR UPGRAD


<REPORT UPDATE AT*[ ] BRG /DIT !!!" /!!!!#! TO [ ] PREDICTI$E<GPRE&UIRED ACCUR ETIMATED 0#3)M LO+ 0#56)M)A$ ACCUR DO+)GRAD



"'89S flight anageent details"'89S flight anageent details Multi-sensor navigation & autoatic navaid tuning

triple 'S> dual <= & ?M5> %PS

n'S only> n'S:<=:?M5> n'S:?M5:?M5> n'S:%PS

2= updating

NP anageent

%PS priary navigation

"'M or "'M5 on-board integrity onitoring

certified for NP +.3 NM use ?atalin;

including F-P2N> T:= ?"T" and 7'N? uplin; capability fro "=

"irline =perational ontrol4



"'89S flight anageent details"'89S flight anageent details !? flight planning & predictions

run#ay to run#ay !? pre-coputed optiiCed flight profile

real tie optiiCation decelerated approach profile> 3? non-precision approaches

full autopilot coupling capability dual FMS> dual onitored

"P4

tie resolution * inute> guidance accuracy around inutes planned iproveent to * second resolution> accuracy better

than 3+ s



Flight planningFlight planning =rigin

?eparture S'?

5ngine out S'?

5n-route

"rrival ST"

"pproach

?estination

Missed approach

"lternate flight plan

"lternate destination



<ertical flight anageent<ertical flight anageent

D

SP!!DLIMI%

SP!!D

,$NS%RAIN%S

AL%I%UD!

,$NS%RAIN%SAL%I%UD!

,$NS%RAIN%S

$RIGIN

D!S%INA%I$N

SP!!D

,$NS%RAIN%S

SP!!D

LIMI%

A,,!L!RA%I$N AL%

%-RUS% R!DU,%I$N AL%

,RUIS! FLS%!P FL

IDL! pat+

geo.etri( pat+

approa(+ pat+

press*ri/ation

seg.ent

%A!$FF ,LIM ,RUIS! D!S,!N% APPR$A,-

APPR$A,-

SP!!DS

%A!$FF

SP!!DS

%IM!

,$NS%RAIN%




Navigation database , "'N !! Navigation database , "'N !!



"'N !! path terinator concept"'N !! path terinator concept The Path and Terinator concept is a eans to perit

coding of Terinal "rea Procedures> S'?s> ST"s and

"pproach Procedures harted procedure are translated into a sequence of

"'N !! legs in the Navigation ?atabase

Flight plans are entered into the FMS by using procedures fro the navigation database and chaining

the together



"'N !! path terinator concept"'N !! path terinator concept 3 leg types have been created to translate into coputer

language FMS4> procedure designed for cloc; &

copass anual flight 'tBs high tie to ipleent N"<> using only ?=3/

preferred leg types, 'F> TF> F #hich are fi6ed and

#ithout possible interpretation The leg type is specified at the end point , Dpath

terinator conceptE



'F leg type'F leg type The 'nitial Fi6 or 'F 2eg defines a database fi6 as a point

in space

't is only required to define the beginning of a route or

procedure



TF leg typeTF leg type Trac; to a Fi6 or TF 2eg defines a great circle trac; over

ground bet#een t#o ;no#n databases fi6es

Preferred ethod for specification of straight legs

course or heading can be entioned on charts> but

designer should ensure TF leg is used for coding4



F leg type ne# leg type4F leg type ne# leg type4 onstant adius "rc or F 2eg defines a constant radius

turn bet#een t#o database fi6es> lines tangent to the arc

and a center fi6



F leg typeF leg type ourse to a Fi6 or F 2eg defines a specified course to a

specific database fi6

TF legs should be used instead of F #henever possible

to avoid agnetic variation issues



?F leg type?F leg type ?irect to a Fi6 or ?F 2eg defines an unspecified trac;

starting fro an undefined position to a specified fi6

Procedure designers should ta;e into account the FMS

flight path depends on initial aircraft heading as #ell



F" leg typeF" leg type Fi6 to an "ltitude or F" 2eg defines a specified trac;

over ground fro a database fi6 to a specified altitude at

an unspecified position



F leg typeF leg type Trac; fro a Fi6 fro a ?istance or F 2eg defines a

specified trac; over ground fro a database fi6 for a

specific distance



F? leg typeF? leg type Trac; fro a Fi6 to a ?M5 ?istance or F? 2eg defines a

specified trac; over ground fro a database fi6 to a

specific ?M5 ?istance #hich is fro a specific database?M5 Navaid



FM leg typeFM leg type Fro a Fi6 to a Manual terination or FM 2eg defines a

specified trac; over ground fro a database fi6 until

Manual terination of the leg



" leg type" leg type ourse to an "ltitude or " 2eg defines a specified

course to a specific altitude at an unspecified position



? leg type? leg type ourse to a ?M5 ?istance or ? 2eg defines a specified

course to a specific ?M5 ?istance #hich is fro a

specific database ?M5 Navaid



' leg type' leg type ourse to an 'ntercept or ' 2eg defines a specified

course to intercept a subsequent leg



leg type leg type ourse to a adial terination or 2eg defines a

course to a specified adial fro a specific database

<= Navaid



"F leg type"F leg type "rc to a Fi6 or "F 2eg defines a trac; over ground at

specified constant distance fro a database ?M5 Navaid



<" leg type<" leg type @eading to an "ltitude terination or <" 2eg defines a

specified heading to a specific "ltitude terination at an

unspecified position



<? leg type<? leg type @eading to a ?M5 ?istance terination or <? 2eg

defines a specified heading terinating at a specified

?M5 ?istance fro a specific database ?M5 Navaid



<' leg type<' leg type @eading to an 'ntercept or <' 2eg defines a specified

heading to intercept the subsequent leg at an unspecified

position



<M leg type<M leg type @eading to a Manual terination or <M 2eg defines a

specified heading until a Manual terination



< leg type< leg type @eading to a adial terination or < 2eg defines a

specified heading to a specified radial fro a specific

database <= Navaid



P' leg typeP' leg type Procedure Turn or P' 2eg defines a course reversal

starting at a specific database fi6> includes =utbound 2eg

follo#ed by a left or right turn and *)+ degree coursereversal to intercept the ne6t leg



@"> @F> @M leg types@"> @F> @M leg types acetrac; ourse eversal or @"> @F and @M 2eg

Types define racetrac; pattern or course reversals at a

specified database fi6

A ! A"t#t$%e Term#&'t#o&

( ! S#&)"e c#rc$#t term#&'t#&)

't t*e +#, b'.e t$r&/

M ! M'&$'" Term#&'t#o&



"'N !! - allo#able leg transitions"'N !! - allo#able leg transitions ! T*e I( "e) #. co%e% o&"

*e& t*e '"t#t$%e co&.tr'#&t. 't

e'c* e&% o+ t*e (456 45 or

PI5 "e) 're %#++ere&t7

8 ! A C(9D(6 D(9D( or (C9D(

.e:$e&ce .*o$"% o&" be $.e%

*e& t*e term#&'t#o& o+ t*e +#r.t

"e) m$.t be o;er +"o&6

ot*er#.e '"ter&'t#;e co%#&)

.*o$"% be $.e%7

< ! T*e I(9R( comb#&'t#o& #.

o&" perm#tte% 't t*e .t'rt o+ t*e

+#&'" 'ppro'c* +or (MS6 GPS or

M=S co%#&) '&% o&" *e& '

.tr'#)*t "#&e6 +#,e% term#&'te%

tr'&.#t#o& procee%. t*e .t'rt o+

t*e +#&'"7




Navigation database related issues Navigation database related issues



opatibility...opatibility...



Navigation data production process Navigation data production process

Pro(ed*re design34 ,ii' Aiation A*t+orities

Data S*pp'ier

FMS Data3ase Pro(essing

FMS

AIP

ARIN, 626 .aster8 9i'e

Pa()ed Data

operator responsi3i'it4



einder - flight plan constructioneinder - flight plan construction harted procedure are translated into a sequence of

"'N !! legs in the Navigation ?atabase

Flight plans are entered into the FMS by calling procedures fro the navigation database

Procedure segents are chained together or elded4 to

for the FMS flight plan



56aple , F-P2N procedure elding56aple , F-P2N procedure elding Procedures are chained together to for the FMS flight

plan. 56aple ,

Arr#;'" c*'rt

A#r'. c*'rt

Appro'c* c*'rt

E&ro$te'#r' .

STAR-e&ro$tetr'&.#t#o&

Appro'c*STAR

STAR-'ppro'c*

tr'&.#t#o& VIA/



56aple , procedure copatibility G56aple , procedure copatibility G Possible procedure isconnects bet#een en-route>

arrival> and approach charts

Possible discontinuities bet#een or inside procedures

'ncopatible or conflicting altitude requireents

bet#een arrival and approach charts




Navigation database recoendations Navigation database recoendations



7aypoint naing issues7aypoint naing issues?ifferent approach procedure types '2S:2=:N"<H4 use

different traIectories and:or #aypoint naes #ithout reason

9nnaed #aypoints on charts are assigned default naes

Sae #aypoint naes used at different locations

hart #ording leading to usage of leg types #hich cause the

FMS to create its o#n #aypoints> #ith naes #hich do not

atch chart

oding constraints lead to creation of #aypoints not on the

chart



Procedure traIectory issuesProcedure traIectory issues hart #ording and:or coding rules lead to coding of agnetic

course leg types such as F legs

hart #ording and:or coding rules lead to bad coding ofvertical descent angles> #hich are critical to a correct vertical

path

'F iniu altitudes often coded as D"TE constraints

=verfly #aypoints traIectories are not repeatable

8aroetric teperature liitations should be indicated on

charts



=verfly #aypoints , depending on #ind> aircraft speed>

ban; angle liitation etcH the FMS traIectory #ill be

different

7hy not use overfly #aypoints G7hy not use overfly #aypoints G

trajectory

not repeatable

overfly wpt



F leg agnetic course angles ay isatch ,

e,ce..#;e ro""

m'&e$;er#&)

7hy not use F legs G7hy not use F legs G

NN



TF legs al#ays fit> independently of agnetic variation ,7hy use TF legs G7hy use TF legs G



ID=E .e)me&t

7hy code FP" constraint on each7hy code FP" constraint on each

F'N"2 leg GF'N"2 leg G

(PA .m'""er t*'&

'"t#t$%e co&.tr'#&t

(PA )re'ter t*'&'"t#t$%e co&.tr'#&t

No (PA

(PA m'tc*e. '"t#t$%e

co&.tr'#&t



7hy use "TJ=J"8=<5 altitude7hy use "TJ=J"8=<5 altitude

constraints Gconstraints G 9sing "TJ=J"8=<5 constraints and FP" constraint

on each leg ensures sealess path

MDA

&';#)'t#o& %'t'b'.e ;ert#c'" '&)"e

&';#)'t#o& %'t'b'.e ;ert#c'" '&)"e

MAP

' p p r o ' c * p r o + # " e



Mediu ter - "T" ?"@ prioritiesMediu ter - "T" ?"@ priorities edesign of e6isting non-precision approaches to accoodate <N"<

"ltitudes at precision F"FBs

9nnaed step-do#n fi6es

7aypoints on 5F'S but not in database or charts

7aypoint naes longer than five characters

?uplicate navaid and #aypoint identifiers

?ifferent altitude for sae point on ST"Bs and approaches Magnetic variation tables used in course calculations

<N"< angle depiction on charts



2onger ter - recoendations2onger ter - recoendations Publication of a single standard:language for procedure

design> database coding> and FMS

educed "'N !! set 'proved charts-database-FMS copatibility

?esign of DFMS-friendlyE procedures

Publication of these procedures using FMS copatible

language in addition to charts4

Publications of standards for navigation database integrity

and certification



2onger ter - coon language2onger ter - coon language oprehensive #orld#ide coonality requires rules at '"=

level

" coon coding Standard should be ,

clearly defined>

including rules for use by both the aircraft and the N"< "irspace

Planner>

the iniu capability of any LF"NS N"< systeE>

the a6iu set usable by the N"< "irspace Planner

This #ould ensure a unique unabiguous coding of routes and

procedures



2onger ter - integrity2onger ter - integrity 'ntegrity ust concern the entire process> fro procedure

design to the loading of the FMS

9ltiate goal should be a fully digital process Process should be under direct supervision of airspace

anageent authorities

7orld#ide ipleentation requires '"= rules



E&% o+ pre.e&t't#o& >

A& :$e.t#o&?

arinc leg types

Documents