Good day to all.
In fact , runways 17L and 17R exist in real world. Charts for procedures exist in real world. I have departed / landed on both for the last year… Liked using Arrival EROL7a for 17L and ILS 17L. … Until I reactivated my subscription and loaded the “Updated” Navdata. I did this because I did not have ILS runway 25 for SUMU . Now I have SUMU ok, but lost SCEL . Interesting.
And you can actually select 17L/R as departure for spawn , indeed select ILS 17R/L as approach in the world MAP ( 2409) . More , Updated LittleNavMap data per Navigraph software and , …yes , the procedures for 17R and 17L are there OK. Very interesting.
I used the search capacity in this forum , nothing there that really explains this Bug for me.
Please correct this. Thank you.
Have a nice day.
Francisco
Hi Francesco,
please use the search feature first. It works very well and you will find a lot of postings to this topic.
The current answer is here:
So, it will hopefully be back again and available with AIRAC 2410/11 (depending if the old runway 19 is still available or not).
Cheers
Richard
Of course , nothing to do but wait. That is no mistery.
The explanation offered is rather intrincate and far from representing the reality of the airport operations in the las months.
Thank you for taking the time , anyway.
And may name is Francisco.
Greetings
Sorry for wrong name Francisco …
I’m not familiar with this airport, we must trust the AIP and our data provider.
Thank you
Richard
Now , that I can understand.
Summing up , it is either Asobo or Data provider fault.
What about a little “google search button” when a customer claims for an mistake ?
As of September 5 2024
Sure a Rev 2 to 2409 could solve it in seconds.
Ok. I am resting my case now. 
No harm done but I really did not like the “tone” of your previous answers.
We all make mistakes.
Greetings
Francisco
RWY 19 is a virtual RWY established by the authorities to serve as displacement of physical RWY 17R due to construction work.
Unfortunately there is a bug in MSFS that leads to suppression of procs as it cannot assign the procedures to RWYs anymore. The only solution is to add the RWY 19 as transparent RWY via the scenery editor. Then all procedures are loaded again.
Lets see if MSFS 2024 addresses that bug.
Thank you for writing.
Sounds all so complicated, never mind, I got a temporal solution.
By swaping 1 (one) folder of scenery files I have got now the “best of two worlds”
i.e. The updated ( 2409) ILS 25 at SUMU and the (MSFS) whole set of 17L/R at SCEL.
And , that is an easy fix. 
Reversable, mind you.
Of course I know that the most part of Chile is now under “old” MSFS data.
Works ok for me until an VATSIM controller ,again, asks me for a procedure I do not have ( original problem ).
Greetings, see you on 2410…
Francisco
In fact , uninstalling all and reinstalling 2409 rev1 without further manipulation …
a) 17L nor 17R are available for Arrival selection.
b) Both 17L and 17R Approaches are there for selection , and work ok (ILS/RNAV)
So, the “faulty” Rwys are there for landing , but not for Arrival …
There you go…
Greetings
Francisco
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.