The data for LIRF ILS 26R shows an ILS frequency of 109.75 in the current data, which matches the published charts. What "bad": frequency were you seeing?
Don't worry,@Mriya. Which number of the LIRF_Scenery_Pack You are talking about? I'll try to recognize a reason of TWR disappearing. Sure, without uploading to the Gateway. It's possible by using x-plane.org post message, perhaps.
@myb considering i'm running the most recent XPlane Mobile version (number 11.0.3), i was considering the latest scenery number too! At this point i can not recognize the specific number. Now i'll try to create an account on the XPlane forum to asking more info about.
I can confirm that the control tower shows up fine on the current XPlane desktop version (11.52). There may be some specifics to the mobile version that causes this.
In Fiumicino the main runways for arrivals are 16L/34R and 16R/34L, runway 25 and 16R/34L are for departures.
Runway 16C/34C is closed and considered as taxiway D, therefore it should be lit as a taxiway.
Sorry, you are right. AD 2 LIRF 1-11,12 (AIRAC effective date 21 May 2020) has changed 'Runway preferential use'. However, when I had work for that Scenery, these changes has not been
published yet. By the way, I didn't find on the Eurocontrol more the latest docs, dated after 21 May 2020. Who knows, what the runways will be used. May be, Rwy16C/34C will be using again.
So, I suppose it's not a bug, because very difficult to track all the changes at Airport since a Scenery has been submitted.
Yeah no worries, Runway 16C/34C has been completly dismissed since Airac 04/2020 together with all the associated procedures.
I can't find the AIP airac document but I have attached a screenshot of the Italian AIP regarding the runways for LIRF, as you can see there's no 16C/34C anymore.
I am an active (well, not so much right now due to Covid) airline pilot flying to LIRF regularly since 1996. I can confirm that runway 16C/34C has never been in use since then. Much like runway 04L/22R at LIPZ, the Italians like to keep "backup" runways, and technically these were not closed for the longest time, but really never used.
Stands from 401 to 412 and from 301 to 318 (399) (new terminal building) are to be adjusted.
New taxiways NG, NC, NH and NE need to be corrected.
See image attached. Note also that the satellite image of google maps is showing the new layout.
Stand numbers need to be corrected as per new layout in terminal 1 "old pier"(for exemple stand 410 is now 407 and is no more oblique, 406 is now 409, 404 is now 410, 402 is now 411, 409 is now 404, 407 is now 403, 405 is now 402, 403 is now 401). Also stands 411, 432, 412 and 422 are now merged in one stand 406. To conclude on the new pier at terminal 1 (the one you made) stand numbers should be corrected (306 is now 301, 305 is now 302, 304 is now 303, 303 is now 304, 302 is now 305, 301 is now 306).
I hope this is the right way to report this, the touchdown zones appear not correctly placed as in the real airport. As shown in the screenshots, the main touchdown zones are in a different position in the runways 16L, 16R, 25, 07, 34R, but not on 34L.
Default scenery on 11.11.
Center runway has no runway lights and is dark at night.
bkeith April 29, 2018 8:39 AM
Corrected. Request can be closed.
Jan Vogel February 26, 2021 4:38 PM
Airport was updated in the meantime, this report can be closed.
The LIRF Gate 702 building is partially transparent. Please see the attachment. Thanks a lot for trying to eliminate the transparency.
Jan Vogel February 27, 2021 10:10 AM
Its a feature, not a bug 🙂
This can be closed.
Although most of the runways ILS frquencies have been corrected, runway 16R still shows the wrong one. For correct data see attached file
Robin Peel September 1, 2019 8:41 PM
The data for LIRF ILS 26R shows an ILS frequency of 109.75 in the current data, which matches the published charts. What "bad": frequency were you seeing?
myb March 31, 2020 8:24 PM
What did you mean 'Control TWR is missed'?
Mriya March 31, 2020 10:03 PM
@myb I'm meaning the tower is not showing up!!! I'm using X Plane Mobile and X Plane Developers told me to report the bug here.
Mriya March 31, 2020 10:06 PM
And btw, other several airports presents the same problem!
myb April 1, 2020 12:52 PM
@Mriya, Your pics are regarding to previous LIRF_Scenery_Pack not the 73111 one.
Mriya April 1, 2020 2:33 PM
@myb And why those scenery didn't get updated at all for mobile? We're running tha latest update available.. this is so frustrating.
myb April 1, 2020 7:51 PM
Don't worry,@Mriya. Which number of the LIRF_Scenery_Pack You are talking about? I'll try to recognize a reason of TWR disappearing. Sure, without uploading to the Gateway. It's possible by using x-plane.org post message, perhaps.
Mriya April 1, 2020 9:42 PM
@myb considering i'm running the most recent XPlane Mobile version (number 11.0.3), i was considering the latest scenery number too! At this point i can not recognize the specific number. Now i'll try to create an account on the XPlane forum to asking more info about.
Jan Vogel March 8, 2021 7:11 AM
I can confirm that the control tower shows up fine on the current XPlane desktop version (11.52). There may be some specifics to the mobile version that causes this.
In Fiumicino the main runways for arrivals are 16L/34R and 16R/34L, runway 25 and 16R/34L are for departures.
Runway 16C/34C is closed and considered as taxiway D, therefore it should be lit as a taxiway.
myb September 8, 2020 8:54 PM
Read more careful, please, the latest LIRF amendments documents.
Anka90 September 9, 2020 1:51 PM
Apologies , I don't understand what are you referring to
myb September 9, 2020 8:13 PM
Sorry, you are right. AD 2 LIRF 1-11,12 (AIRAC effective date 21 May 2020) has changed 'Runway preferential use'. However, when I had work for that Scenery, these changes has not been
published yet. By the way, I didn't find on the Eurocontrol more the latest docs, dated after 21 May 2020. Who knows, what the runways will be used. May be, Rwy16C/34C will be using again.
So, I suppose it's not a bug, because very difficult to track all the changes at Airport since a Scenery has been submitted.
Anka90 September 10, 2020 10:35 AM
Yeah no worries, Runway 16C/34C has been completly dismissed since Airac 04/2020 together with all the associated procedures.
I can't find the AIP airac document but I have attached a screenshot of the Italian AIP regarding the runways for LIRF, as you can see there's no 16C/34C anymore.
Jan Vogel February 26, 2021 4:38 PM
I am an active (well, not so much right now due to Covid) airline pilot flying to LIRF regularly since 1996. I can confirm that runway 16C/34C has never been in use since then. Much like runway 04L/22R at LIPZ, the Italians like to keep "backup" runways, and technically these were not closed for the longest time, but really never used.
Hi,
as discussed already in
XSG-10877
Done
, runway 16C/34C does not exist anymore and has become taxiway D.
Just landed on LIRF 16L and wondered why my X-RAAS2 started screaming to my "on runway 16C" when I taxied off 16L onto D...
Best regards,
Daniel
Jan Vogel December 1, 2021 10:24 AM
A fixed version was uploaded to the Gateway and should fix this issue in a future release (XP12).
Gate numbers and position need to be updated to the latest layout.
GiacomoPilot September 17, 2023 10:24 PM
The main problem is with terminal 3 (gate numbers and taxiways NC and NG) with problems when flying online.
Stands from 401 to 412 are to be adjusted with clockwise renumbering, one deleted and two shifted in the north portion, as per https://onlineservices.enav.it/enavWebPortalStatic/AIP/AIP/(A09-23)_2023_11_02/documents/Root/ENAV/Cartografia/AD/AD_2/AD_2_PRINCIPALI/LIRF/2-1/AIRCRAFT%20PARKING%20DOCKING%20CHART%20-%20ICAO.pdf (free subscription). If we wait for updating of google ortho, we lose something important :)
Could help you coord of stands 401 to 412:
41.47.48.42N 012.15.16.79E 41.47.49.76N 012.15.17.64E 41.47.51.04N 012.15.18.51E 41.47.52.36N 012.15.19.34E 41.47.53.68N 012.15.20.17E 41.47.54.50N 012.15.20.42E 41.47.52.94N 012.15.24.28E 41.47.51.62N 012.15.23.45E 41.47.50.31N 012.15.22.62E 41.47.48.99N 012.15.21.79E 41.47.47.67N 012.15.20.96E 41.47.46.33N 012.15.20.21E
All taxi between NG G EG H are to be deleted, also. Tnx
Stands from 401 to 412 and from 301 to 318 (399) (new terminal building) are to be adjusted.
New taxiways NG, NC, NH and NE need to be corrected.
See image attached. Note also that the satellite image of google maps is showing the new layout.
Jan Vogel June 17, 2025 9:21 AM
This was fixed by a recent submission.
Stands numbers at Terminal 1 need to be revised according to new layout as per charts.
GiacomoPilot January 8, 2024 2:36 PM
Also one or more gates are missing.
sebol1990 January 29, 2024 7:15 PM
Which stands?
GiacomoPilot January 30, 2024 4:27 PM
Stand numbers need to be corrected as per new layout in terminal 1 "old pier"(for exemple stand 410 is now 407 and is no more oblique, 406 is now 409, 404 is now 410, 402 is now 411, 409 is now 404, 407 is now 403, 405 is now 402, 403 is now 401). Also stands 411, 432, 412 and 422 are now merged in one stand 406. To conclude on the new pier at terminal 1 (the one you made) stand numbers should be corrected (306 is now 301, 305 is now 302, 304 is now 303, 303 is now 304, 302 is now 305, 301 is now 306).
GiacomoPilot January 30, 2024 4:30 PM
Also stand 412 on NG (Terminal 1 "old pier") is missing (see chart attached).
GiacomoPilot January 30, 2024 4:31 PM
The image you attached is old (see the satellite images of google maps now to see the new layout)
sebol1990 January 30, 2024 6:42 PM
Thank you for reporting. I will correct ASAP
sebol1990 March 18, 2024 4:36 PM
Hi.
Stands numbers and markings have been corrected according to navigraph
https://gateway.x-plane.com/airports/LIRF/show#Scenery-101391
GiacomoPilot March 18, 2024 4:54 PM
Also 301-306?
sebol1990 March 19, 2024 7:19 PM
Yes
I hope this is the right way to report this, the touchdown zones appear not correctly placed as in the real airport. As shown in the screenshots, the main touchdown zones are in a different position in the runways 16L, 16R, 25, 07, 34R, but not on 34L.
Julian Lockwood July 31, 2024 2:58 AM
A limitation of the existing runway tech in XP12.