PAJN LDA X missing SSR IAF in navdata

Navigation Data SID/STAR/APPR
1

This is something I’ve noted before but the SSR IAF for PAJN LDA X Rwy 8 that can be found in the chart is missing in the navdata. Instead there is a BERGS IAF that passes through SSR in the navdata although BERGS isn’t marked as an IAF on the chart.

Simbrief routes to PAJN usually end the enroute at SSR, and then there is no proper connection with the approach. I used to replace SSR with EEF as a workaround, now I see I can just use the BERGS transition and then delete BERGS to get just SSR, but those workarounds shouldn’t be needed.

2

There are a number of NOTAM’s that continue to indicate the non-availability of the LDA approaches:

!FDC 4/8830 JNU SPECIAL JUNEAU INTL, JUNEAU, AK.
LDA Z RWY 8, AMDT 11A…
PROCEDURE NA, PER FLIGHT CHECK.
2409210136-2609202330EST

!JNU 11/120 JNU NAV LOC TYPE DIRECTIONAL AID RWY 08 U/S 2511062136-2609271500EST

!FDC 5/3113 JNU IAP JUNEAU INTL, JUNEAU, AK.
LDA X RWY 8, AMDT 12E…
PROCEDURE NA.
2512021323-2607141323EST

!FDC 6/0738 JNU IAP JUNEAU INTL, JUNEAU, AK.
LDA X RWY 8, AMDT 12E…
PROCEDURE NA EXCEPT FOR ACFT EQUIPPED WITH SUITABLE RNAV SYSTEM WITH GPS,
SSR VORTAC OUT OF SERVICE. 2601052007-2602052007EST

3

Hi,
Besides the valid “notams” from @srcooke … “embedded” IAFs will not be coded as their own transition. SSR is classified as IAF, but you don´t have your own transition. SSR is part of the BERGS transition and, therefore, “embedded” between BERGS and LYNNS.

That is a data provider-independent solution, so there is no SSR transition, even when SSR is an IAF waypoint.

Cheers,
Richard

4

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.