Airport Navigation Data Status

Data last parsed: 2020-05-24 18:07 UTC

Parsing Result Summary
No Message60
Information0
Warning4
Error12

File Messages
C/CYTZ/CYTZ.hjson (Error)
Severity Location Message
Error route #1, name=ILIXU SEVEN, segments list Invalid nav point "MIZEN"
Warning route #1, name=ILIXU SEVEN, "labels" list ignoring point "MIZEN" not used in this route
C/CYVR/CYVR.hjson (Error)
Severity Location Message
Error route #3, name=CASDY three arrival, segments list Invalid nav point "EMLOX"
C/CYYZ/CYYZ.hjson (Warning)
Severity Location Message
Warning route #9, name=ROKTO TWO (Rwy 33s/15s), segments list Nav point SIKMA more than 300nm from CYYZ
E/ENTC.hjson (Error)
Severity Location Message
Error route #1, name=Northeast/East Arrivals Runway "01" not valid
Error route #2, name=East Arrivals Runway "19" not valid
Error route #3, name=South Arrivals Runway "01" not valid
Error route #4, name=South Arrivals Runway "19" not valid
Error route #5, name=North/West Arrivals Runway "01" not valid
Error route #6, name=North/West Arrivals Runway "19" not valid
Error route #7, name=SENJA 8M & LURAP 3L Runway "01" not valid
Error route #8, name=North/East Departures Runway "01" not valid
Error route #9, name=South Departures Runway "01" not valid
Error route #10, name=North/East Departures Runway "19" not valid
Error route #11, name=South/West Departures Runway "19" not valid
K/KASE/KASE.hjson (Error)
Severity Location Message
Error route #2, name=final 15, segments list Invalid nav point "LASCH"
Warning route #2, name=final 15, segments list Nav point TALIA more than 300nm from KASE
K/KLAX/KLAX.hjson (Error)
Severity Location Message
Error route #22, name=SHIVE ONE, segments list Invalid nav point "HARBR"
Error route #22, name=SHIVE ONE, segments list Invalid nav point "HARBR"
Warning route #22, name=SHIVE ONE, "labels" list ignoring point "HARBR" not used in this route
Information first level properties 23 global labels found for airport ... best pratice is to limit the number of labeled nav points to those that make sense for all routes and when nor routes are displayed. VORs are a good example of a reasonable global label. Points marking key terrain features also make sense. Otherwise all points should be assigned to individual routes.
K/KONT/KONT.hjson (Error)
Severity Location Message
Error route #1, name=EAGLZ TWO, segments list Invalid nav point "SEONG"
Error route #1, name=EAGLZ TWO, segments list Invalid nav point "EAGLZ"
Error route #1, name=EAGLZ TWO, segments list Invalid nav point "SEONG"
Error route #1, name=EAGLZ TWO, segments list Invalid nav point "EAGLZ"
Error route #1, name=EAGLZ TWO, segments list Invalid nav point "SEONG"
Error route #1, name=EAGLZ TWO, segments list Invalid nav point "EAGLZ"
Error route #1, name=EAGLZ TWO, segments list Invalid nav point "EAGLZ"
Error route #1, name=EAGLZ TWO, segments list Invalid nav point "STOMN"
Error route #1, name=EAGLZ TWO, segments list Invalid nav point "EAGLZ"
Error route #1, name=EAGLZ TWO, segments list Invalid nav point "TYNIN"
Warning route #1, name=EAGLZ TWO, "labels" list ignoring point "EAGLZ" not used in this route
Warning route #1, name=EAGLZ TWO, "labels" list ignoring point "SEONG" not used in this route
Warning route #1, name=EAGLZ TWO, "labels" list ignoring point "SEONG" not used in this route
Warning route #1, name=EAGLZ TWO, "labels" list ignoring point "TYNIN" not used in this route
Error route #3, name=JCKIE ONE, segments list Invalid nav point "SEONG"
Error route #3, name=JCKIE ONE, segments list Invalid nav point "JMANN"
Error route #3, name=JCKIE ONE, segments list Invalid nav point "SEONG"
Error route #3, name=JCKIE ONE, segments list Invalid nav point "JMANN"
Error route #3, name=JCKIE ONE, segments list Invalid nav point "SEONG"
Error route #3, name=JCKIE ONE, segments list Invalid nav point "JMANN"
Error route #3, name=JCKIE ONE, segments list Invalid nav point "JMANN"
Warning route #3, name=JCKIE ONE, "labels" list ignoring point "JMANN" not used in this route
Error "labels" list Invalid nav point "EAGLZ"
K/KSFO/KSFO.hjson (Error)
Severity Location Message
Error route #5, name=SERFR 3, segments list Invalid nav point "NARWL"
Error route #9, name=AFIVA 1, segments list Invalid nav point "JAYKK"
Error route #9, name=AFIVA 1, segments list Invalid nav point "JAYKK"
Warning route #9, name=AFIVA 1, "labels" list ignoring point "JAYKK" not used in this route
L/LIMC/LIMC.hjson (Error)
Severity Location Message
Error route #1, name=35L/35R Arrivals, segments list Invalid nav point "MC407"
Error route #1, name=35L/35R Arrivals, segments list Invalid nav point "SOKBU"
Error route #1, name=35L/35R Arrivals, segments list Invalid nav point "LEMKI"
Error route #1, name=35L/35R Arrivals, segments list Invalid nav point "MC412"
Error route #1, name=35L/35R Arrivals, segments list Invalid nav point "LEMKI"
Error route #1, name=35L/35R Arrivals, segments list Invalid nav point "SOKBU"
Error route #1, name=35L/35R Arrivals, segments list Invalid nav point "MC407"
Error route #1, name=35L/35R Arrivals, segments list Invalid nav point "MC412"
Error route #1, name=35L/35R Arrivals, segments list Invalid nav point "MC407"
Warning route #1, name=35L/35R Arrivals, "labels" list ignoring point "LEMKI" not used in this route
Error "labels" list Invalid nav point "SOKBU"
L/LSGS/LSGS.hjson (Error)
Severity Location Message
Error route #2, name=departure 25, segments list Invalid nav point "SPR29"
M/MDPC/MDPC.hjson (Error)
Severity Location Message
Error route #2, name=RWY 27 ARRS, segments list Invalid nav point "PC220"
Error route #2, name=RWY 27 ARRS, segments list Invalid nav point "PC222"
Warning route #2, name=RWY 27 ARRS, "labels" list ignoring point "PC222" not used in this route
Error route #3, name=RWY 27 DEPS, segments list Invalid nav point "PC240"
Error route #3, name=RWY 27 DEPS, segments list Invalid nav point "PC245"
Error route #3, name=RWY 27 DEPS, segments list Invalid nav point "PC246"
Error route #3, name=RWY 27 DEPS, segments list Invalid nav point "PC240"
Error route #3, name=RWY 27 DEPS, segments list Invalid nav point "PC241"
Error route #3, name=RWY 27 DEPS, segments list Invalid nav point "PC242"
Error route #3, name=RWY 27 DEPS, segments list Invalid nav point "PC243"
Error route #3, name=RWY 27 DEPS, segments list Invalid nav point "PC243"
Error route #3, name=RWY 27 DEPS, segments list Invalid nav point "PC244"
Error route #3, name=RWY 27 DEPS, segments list Invalid nav point "PC244"
Warning route #3, name=RWY 27 DEPS, "labels" list ignoring point "PC240" not used in this route
Warning route #3, name=RWY 27 DEPS, "labels" list ignoring point "PC243" not used in this route
Warning route #3, name=RWY 27 DEPS, "labels" list ignoring point "PC244" not used in this route
M/MMUN/MMUN.hjson (Warning)
Severity Location Message
Warning route #1, name=12L/12R RNAV Arrivals, segments list Nav point DANUL more than 300nm from MMUN
M/MYNN/MYNN.hjson (Error)
Severity Location Message
Error route #3, name=09 GPS Approach Runway "09" not valid
S/SBGL/SBGL.hjson (Error)
Severity Location Message
Error route #2, name=TODAB, segments list Invalid nav point "TODAB"
Warning route #2, name=TODAB, "labels" list ignoring point "TODAB" not used in this route
T/TKPK/TKPK.hjson (Warning)
Severity Location Message
Warning route #1, name=07 RNAV STAR, segments list Nav point TIKAL more than 300nm from TKPK
T/TNCM/TNCM.hjson (Warning)
Severity Location Message
Warning route #1, name=ULUBA, segments list Nav point TIKAL more than 300nm from TNCM