VIDP sid path terminator
 

The path terminators of VIDP rw 09 and 10 rnav sid ,ALI 5D,ALI 5E,ITBAN 5D,ITBAN 5E after PABGU and OBDAG are DIRECT TO FIX
according to INDIA AIP but our company LIDO charts are TRACK TO FIX.Please help me to verify which one is correct? (AIP or LIDO)
Thank you.

https://cimg6.ibsrv.net/gimg/pprune....bad68aa267.png
https://cimg8.ibsrv.net/gimg/pprune....a3841ef87.jpeg

I don't see any disagreement, both are fly-over, but there is no way for a nav database to be coded so that the plane turns direct to a fix after a fly-over. The result is that it will turn after passing the previous point and then reintercept the direct line between the two fixes. The lido chart represents just that.

Noknoipobin Are you using Lido NAV db?

For the moment I am not convinced it's track-to fix based on what you posted. Certainly a conclusion which cannot be drawn from the chart itself. It looks a bit as a DF, actually.

BTW are you not highlighting the wrong line? It's path-terminator, the inbound leg is stored within its ending waypoint.

Describes well Track-to-fix or course-to-fix PTs. Unlike the DF path terminator which will provide for a simple direct steer from the where ever the turn rolls out.

https://cimg8.ibsrv.net/gimg/pprune....0dacb7d13.jpeg
https://cimg9.ibsrv.net/gimg/pprune....8ff7e14a2.jpeg

In LIDO chart ,if it is DF it must be coded DCT before that point in chart text. Aircraft must turn directly to next waypoint (MATEX) instead of turning to intercept track from OBDAG to MATEX. Even in the graphic chart there is no track number but it is a TRACK TO FIX. On that day my aircraft turned to intercept track.

After fly-over point , nav database can be coded both DF and TF. Most airports (charts) I have been around the world are DF and nav databases are also DF , aircraft fly directly to a fix after fly-over. I just saw TF after fly-over in a few airports including VIDP.(some SIDs)

I am using LIDO nav db . it is also TF after fly-over point . LIDO chart DF must be coded DCT ahead of that point as I had explained above.

Thank you very much. I have already informed LIDO and all wrong charts and nav db will be updated soon.(next cycle)

Thanks for the feedback. Based on the more details I thought you are actually correct. The Lido Charts are generated by software internal process from the Lido NAB db stored in their computer, which is their 'raw data'. Seeing the DCT missing in their description is a particularly nice find!

For future reference, the Lido NAV db has a tabulated format (Excel like) which you should be able to check with the Flt Ops team at your airline directly, without the need to second guess the cockpit display and your memory of aircraft behaviour. Then compare it directly with AIP coding table.

It was a pleasure reading about a pilot who actually cares what the computer is doing and understands why it shouldn't. To my experience, men of this character are overall fine aviators too, nice to share the same online space.

AIPs have precedence over Lido/Jeppesen. AIPs are the legal binding documents. Not Lido/Jeppesen.