Ibra wrote:
Some countries (France, Germany), do not code separate RNP tables for each IAF (or transition, arrival)
I only looked at the AIP entry very quickly, so not in a position to make any definitely statements, but the table above is headed with RNP RWY 13, so perhaps in this case it is specific to the particular instrument approach?
G430W has few IAF and many HOLD missing, I get surprised when ATC ask to go for it
ABY in RNP09 at AlbertBray
From the French AIP database coding table it certainly looks like it should be included.
That’s even more curious. The KLN94 does no contain RNAV SIDs/STARs but it contains their waypoints, so it should contain TUKVI as a part of a procedure if that procedure is listed in its database.
this is probably why some IAF are missing in some navigators?
Are there any other navigators with IAFs missing, but with the waypoint in their database?
I don’t see why requiring special clearance would be a reason to exclude it from the database (in the KLN94)
Yes TUKVI clearance is unrelated to why KLN does not have it
The way how some RNP/IAF are represented in plates or coded in database is odd, this is probably why some IAF are missing in some navigators?
Some countries (France, Germany), do not code separate RNP tables for each IAF (or transition, arrival) or do not label IAF in their RNP table remarks, everything goes in one single RNP table, I think Jepps will try to decouple them for use in GPS database, then depending on navigator some IAF go missing (especially those without TF segment)
Other countries (UK, Belgium), will have 1×RNP coding table for each 1×IAF in plate, I guess this is the cleanest way to do it I just noticed that Lydd, Shoreham have 3 runways center, left, right that match each of those T-IAFs or Y-IAFs
Seems that some NAA love creating jobs for Jeppsen & Garmin (France did lot of this with separate STAR, INA, FNA plates, NFW one can fly ILS to Toussus with 3 pages of AIP plate )
In KLN, are they called “transition”? or “IAF”?
It could be something in database that relates to legacy INA/STAR arrivals? or unsupported legs? any GPS should support TF legs (track to fix: with distance, magnetic/true tracks) but I don’t see one coded to TUKVI INA/IAF in FAS data-block, the transitions associated with legs like Initial-Fix, Course-To-Fix, Procedural Turns are usually missing in old navigators, the new navigators like GTN, tend to backfill distance/track data for IF, CF, PT legs on-the-fly
OKPEM IAF has everything coded in RNP database for both IAF and HOLD, yet did not show up in your KLN list, so I don’t get it
What about ILS13, does it have TUKVI as IAF?
They can and do. (Lille)… References please.
It’s LFAT tower ATC who can’t give direct TUKVI for RNP, they can give direct to all others, Lille ATC and London ATC do give direct TUKVI
I don’t have any references but it’s written in plates and sits in London FIR
L2K ATC can’t offer direct there without handover from London ATC/FIS
They can and do. (Lille).
FIS?? Handover from London Info?
References please.
FYI the Garmin GTN trainer / simulator has TUKVI as an IAF.
Looks like a cockup in the Jepp data, but why in a KLN94 and not a GNS?
OLMAV OSDIT Vectors I selected Vectors; no problem. Then select DCT TUKVI
Looking again, I am more puzzled OKPEN IAF is not listed? especially, as it’s IAF+HOLD
Also, does KLN delete points from approach when you do “Vectors”
In Garmin, “Vectors-To-Final” VTF tend to delete all points except IF, FAF, MAPt. So one can’t do DCT to other points, in this case it works as TUKVI is an IF on extended final…sometimes VTF delete IF if IF-FAF leg differs from extended FAF-MAPT leg (say RNP04 in LFOP), thé. doing direct FAF or MAPt/RWY will toast approach and missed
The right way to do it is to press direct one of IAF and activate the leg XXXXX-FAF
PS: ILS and RNP at L2K has some funky non-standard stuff,
Foreflight also offers the point as IAF:
FYI the Garmin GTN trainer / simulator has TUKVI as an IAF.