Hi.. Today i flied from LTAI to LTFM and when i choose arrival star from flightplanner website (SISPI1A) it doesnt match with airplane and simbrief.. Simbrief and ini A350 give me sispi2a.. My msfs airac is uptodate.. Im on SU1
Hi,
Please post a screenshot from Simbrief and the A350 with this STAR? I can’t reproduce it, and there is no SIPSI2A available. It is not in Simbrief nor the A350; therefore, I’m curious where this procedure comes from.
Here, my result in Simbrief - no SIPSI2A, only the correct one SIPSI1A (in all recommended routes):
Thank you
Richard
1 Like
The differences you noticed are because your Simbrief account is using an older AIRAC cycle.
In MSFS, the default aircraft (like the A320neo) always use the latest AIRAC provided by Asobo, but third-party aircraft like the PMDG 737 or iniBuilds A350 use separate navigation databases - Navigraph. If you haven’t installed an up-to-date AIRAC (via Navigraph software) for these third-party planes, you might see discrepancies like the one you described.
Also, keep in mind that Simbrief uses the Navigraph AIRAC as well.
1 Like
But that wouldn´t explain why he has a NEWER revision of the STAR; he wrote he had SISP2A. It´s 1A, and 2A would be a future revision, which are not in the AIP nor in any data (data provider independent).
Cheers,
Richard
I’ll try to explain as simply as possible. He mentioned STAR SISPI1A because that’s the procedure you get in Asobo’s free flight planner - which always uses the very latest AIRAC cycle.
However, Simbrief and the iniBuilds A350 both pull their nav data from Navigraph’s paid subscription. So if, for example, the OP has AIRAC 2403 tied to their Simbrief account, that cycle doesn’t include SISPI1A - instead, for runway 35R you’ll see SISP2A
That is precisely what is impossible and therefore wrong—revisions (worldwide) are in ascending order. That means 1A is before 2A and not vice versa. He wrote that he sees 2A, and that can´t be an outdated/older STAR from any older cycle. 2A is possibly a new revision in the future, but not a revision in the past.
All this has nothing to do with the data provider … or where the data comes from.
Cheers,
Richard
Yes my littlenavmap airac is 2503 and also see sispi2A
Ok, we have 2504 but anyway, can you post a screenshot from LNM … thank you!
Here what I see in LNM (Navigraph AIRAC 2503/04):
Cheers,
Richard
AIRAC 2403
AIRAC 2504
Could you please take a screenshot of your Simbrief page that clearly shows the AIRAC cycle?
For example
1 Like
Oh, mea culpa, apologize, @TenPatrol. You´re right. I have only looked back to 2504, but the STAR name change is uncommon. Hm, I don´t stop learning. Thank you very much, and please excuse.
Cheers,
Richard
2 Likes
No worries at all! Mistakes happen to everyone—only those who do nothing never slip up.
Edit
@NAVData I also made a slip when I said
In reality, the iniBuilds A350 can use either the free AIRAC (navdata) from Asobo or Navigraph subscription.
1 Like
Yes my simbrief airac is also 2403 and there the star is sispi2a that showed above but why my msfs2024 dont update last airac because i also see there sispi2A..
![Desktop Screenshot 2025.04.03 - 15.14.50.52|690x388]
Could you please confirm if you have Navigraph installed?
If yes, could you also check if the Navigraph is properly installed in your MSFS2024 “Community” folder?
No ı didnt install navigraph any time.. I dont have a subscription…
ok, so try default A320neo v2
I deleted my game and reinstall it and open the game without any addons and with defaults a320neo i couldnt choose the LTFM as a destination on ingame planner… When i add a scenery for ltfm (trscenery ltfm 1.0.8) i get all of same before i hade (sispi2a) and i decided it is all about scenery… But why vanilla game doesnt exist navdata for ltfm
For some reason, LTFM is missing in MSFS 2024 SU1. However, it is available in the SU2_beta and it’s possible to select the STAR SISP1A
Uninstall LTFM by trscenery.
Try freeware
LTFM Istanbul Airport ver. 1.9.55
The freeware also doesnt contain navdata.. Thanks for all ypur effort to solve problem.. I will wait su2 non-beta version
Have you checked STAR for runway 35R directly in FBW A32NX MCDU or A320neo v2?
ı try wit a320 neo v2 but they are many missing sid and star for freeware one