Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

PMDG MD-11 (FS2004) Questions

Featured Replies

  • Author
1 hour ago, Mike777 said:

 

Before we go any further, please open FS.  Take any aircraft -- the default Trike will do just fine -- and place it at LSZH, any gate, or better yet, on Runway 14.  Then go to the top menu, click on World, then Map.  Click on the airport diagram of LSZH.  You should see a list of frequencies and course headings for runways.  Tell us what it says for Runway 14.  Better yet, include a screen shot of the map that you see.

Mike

Here screenshot I guess is what I am supposed to see. If so, I realized then the data 111.75/135 provided from 747 FMC is correct. FSX World Map has 108.30/136 I didn't try on it yet. If from previous MD-11 flight I was be able to do manual landing then the 111.75/135 is the correct data. It's just the APPR/LAND doing nothing and obvious LOC will not localize.

From FSX World Map is http://www.fsfiles.org/flightsimshotsv2/image/GAvK

I will do as you ask with FSX Trike, good idea. I appreciate so much your help and I apologize if I am driving you crazy. 

Just checked FSX World Map with FSX Trike straight to LSZH rwy 14L and the map looks the exact 108.30/136 info on the runway14 but on the very left side of the map the Heading info is different. The one from MD-11 world-Map shot says Heading 135 and from FSX Trike, 45. FSX not correct sometimes (lol).

Mike, is this what you ask? I never knew by clicking on the runway inside of the map I get complete info......cool!

Here a screenshot http://www.fsfiles.org/flightsimshotsv2/image/GAvr

Patricio Valdes

  • Replies 132
  • Views 12.2k
  • Created
  • Last Reply
59 minutes ago, trisho0 said:

Mike, is this what you ask? I never knew by clicking on the runway inside of the map I get complete info......cool!

Yes!  I'm glad you found the maps with the ILS information in both simulators!

59 minutes ago, trisho0 said:

Here screenshot I guess is what I am supposed to see. If so, I realized then the data 111.75/135 provided from 747 FMC is correct. FSX World Map has 108.30/136 I didn't try on it yet. If from previous MD-11 flight I was be able to do manual landing then the 111.75/135 is the correct data. It's just the APPR/LAND doing nothing and obvious LOC will not localize.

But I don't understand you here.  The data from the 747 FMC is NOT correct. It is correct for the real airport, but not FS9 or FSX. 

Again, the problem is that the 747 in FSX has the current ILS information, but the scenery does not.  The MD-11 in FS9 has the current ILS information, but the FS9 scenery does not.  Both FS9 and FSX have the old ILS frequency, 108.3, course 136.  That's what you can see on both the FS9 and FSX maps.  This means that in both simulators, the ILS localizer and glideslope information is being transmitted on 108.3  If your ILS receiver is tuned to 111.75, it won't pick up the ILS.  Just like with a radio in the real world.  If your radio is tuned to 91.1 and the station you want to hear is on 92.5, you won't hear it.

Instead of letting the MD-11, the 747, or any other aircraft, autotune the ILS, you need to type in 108.3/136 for the ILS on the NAV/RAD page of the FMC.  Then you will get the localizer and glide slope when you get within 20 miles or so of LSZH on the proper course. 

This sort of thing happens with many out of date airports.  There are ways to update the scenery, but I don't have time to go into it now.

Mike

 

 

                    bUmq4nJ.jpg?2

 

I just flew this Tutorial. As I have stated, I usually don't do autolands, but for the sale of this Tutorial exercise, decided to follow the Tutorial to the letter.

Autolanded on Rwy 14 using the ILS frequency of 108.30 and had no issues whatsoever.

LiningUpIntoILS14.png

And as can be seen the LOC and G/S have been captured

FinalsLS14.jpg

 

Rick Almeida

  • Author
On ‎6‎/‎8‎/‎2017 at 10:09 PM, Mike777 said:

Instead of letting the MD-11, the 747, or any other aircraft, autotune the ILS, you need to type in 108.3/136 for the ILS on the NAV/RAD page of the FMC.  Then you will get the localizer and glide slope when you get within 20 miles or so of LSZH on the proper course.

I will fly MD-11 as recommended to find out. But 747 doesn't need that info because FMC tells me the f/c and it does LOC and G/S with a nice autoland.

On ‎6‎/‎8‎/‎2017 at 10:09 PM, Mike777 said:

But I don't understand you here.  The data from the 747 FMC is NOT correct. It is correct for the real airport, but not FS9 or FSX.

But the 747 does autoland nicely with the 111.75/135

Instead, I will see what I get by entering the 108.30/136

Patricio Valdes

  • Author
3 hours ago, vc10man said:

And as can be seen the LOC and G/S have been captured

Is it supposed the LOC and G/S from FMA to be in green color instead of white fonts?

Patricio Valdes

  • Author
On ‎6‎/‎7‎/‎2017 at 8:09 PM, trisho0 said:

Regarding on that http://www.fsfiles.org/flightsimshotsv2/image/GA7q screenshot it appeared again. I change FSX fullscreen to windowed and then back to fullscreen the MD-11 aircraft is restored. What can be wrong or any ideas?

My PC specs: Alienware Aurora R5 4.2GHz Windows 10 64-bit with 64G RAM, NVidia graphics card GeForce GTX-1080 VRAM 8G

Patricio Valdes

  • Author
13 hours ago, trisho0 said:

Is it supposed the LOC and G/S from FMA to be in green color instead of white fonts?

I flew last night EDNY rwy06 to LSZH ILS14 using world/map info 103.30/136 and voila the bird intercepted ILS and LOC G/S success, landing well centered on the arrival runway. LOC and G/S changed white to green on the FMA. From some reason the FSX ADD-ON LSZH scenery, the runways was flat corrupted. Once the bird landed I switched FSX from fullscreen to windowed mode and back to fullscreen mode, the scenery was restored. Never had that before.

Patricio Valdes

  • Author
On ‎6‎/‎8‎/‎2017 at 10:09 PM, Mike777 said:

If your ILS receiver is tuned to 111.75, it won't pick up the ILS.

You are right MD-11 did LOC and G/S nicely with the world/map f/c info (108.30/136). But MD-11 FMC sent a message "Tune IKL 111.75". Also, from ND I see "Flap Disag" I think it is flap disagree but no "Protection" message from FPD as in the past while learning. (I am still learning anyway)

The 747 did many times landing on the same ILS14 and LOC G/S armed activated and landing as LAND3 with the real airport info 111.75/135? It's rare. I will later with 108.30/136.

Patricio Valdes

42 minutes ago, trisho0 said:

You are right MD-11 did LOC and G/S nicely with the world/map f/c info (108.30/136). But MD-11 FMC sent a message "Tune IKL 111.75". Also, from ND I see "Flap Disag" I think it is flap disagree but no "Protection" message from FPD as in the past while learning. (I am still learning anyway)

The 747 did many times landing on the same ILS14 and LOC G/S armed activated and landing as LAND3 with the real airport info 111.75/135? It's rare. I will later with 108.30/136.

Isn't the 747 in FSX?  The MD-11 is in FS9.  You mentioned a problem w/ add on scenery in FSX.  Do you have addon scenery installed in FSX but not FS9?  Addon scenery will often update ILS and other nav data.

Regarding the "Tune ... 111.75" message, the MD-11 has no way of detecting what the frequency in your scenery is.  It's just telling there is a discrepancy between what you have tuned and what is in its database. Don't know about the flap message but look in the MD-11 manuals.

Mike

 

                    bUmq4nJ.jpg?2

 

Forgot to add that my scenery was the FSDT Zurich add-on.

I too received that 'Tune................111.75' flash in the FMS/FMS, but I ignored it and settled for 108.30MHz for ILS14.

Rick Almeida

1 hour ago, trisho0 said:

My PC specs: Alienware Aurora R5 4.2GHz Windows 10 64-bit with 64G RAM, NVidia graphics card GeForce GTX-1080 VRAM 8G

Beats my system by a country mile.

Rick Almeida

  • Author
2 hours ago, Mike777 said:

Isn't the 747 in FSX?  The MD-11 is in FS9. 

Yes, I have 747 and MD-11 installed for fs9 and FSX Acceleration sims. Also, others PMDG for the FSX, you know.

 

2 hours ago, Mike777 said:

You mentioned a problem w/ add on scenery in FSX.  Do you have addon scenery installed in FSX but not FS9?  Addon scenery will often update ILS and other nav data.

Yes, I have the Aerosoft London Heathrow Extended FSX fs9..... both on  the same machine. I do flight on both sims. And yes, the problem was in FSX

Now flying same trip EDNY/LSZH with MD-11 in FSX to see if the corrupted image appears again like http://www.fsfiles.org/flightsimshotsv2/image/GA7q which I think is related with the PC graphics.

Patricio Valdes

  • Author
2 hours ago, vc10man said:

Forgot to add that my scenery was the FSDT Zurich add-on.

I too received that 'Tune................111.75' flash in the FMS/FMS, but I ignored it and settled for 108.30MHz for ILS14.

Then that "Tune .....message" is a common one in MD-11.

Patricio Valdes

37 minutes ago, trisho0 said:

Yes, I have 747 and MD-11 installed for fs9 and FSX Acceleration sims. Also, others PMDG for the FSX, you know.

Can you list whose 747 you have in FS9, and whose in MD-11 and 747 in FSX? Are both/all  these aircraft from PMDG? Other PMDG for FSX? Can you list those as well, please?

 

39 minutes ago, trisho0 said:

corrupted image

You keep linking to that same image. Why dont you try a different screengrab of your MD-11 in a different place? Try and approach this in a logical modus operandi.

 

38 minutes ago, trisho0 said:

common one in MD-11.

Not necessarily, as you do not have that scenery. Only common link we have is the Airac Cycle, which is in the MD-11's FMC Database, and as Rwy14 at LSZH has been chosen, logic suggests that it will flag up the correct today's world ILS frequency as opposed to a much older frequency from a mcuh older FS9 or FSX navdata.

Rick Almeida

Patricio, if you want to solve this problem, you need to stick to the particular aircraft, the particular simulator, and the particular scenery that is involved.  It is really of no help to say "My 747 works with 111.75 but my MD-11 doesn't" if you are using different scenery in different simulators (FSX instead of FS9).  If you want to try the 747 and the MD-11 with 111.75, you need to stick to one simulator, and not switch the scenery for LSZH in the middle of testing. 

You also need to read carefully all of the previous posts from Rick and me.  There is a lot of information about why you are unable to use 111.75 to land in FS9 with its original scenery for LSZH.  If you read it carefully and again look at the World>Map, as well as the frequency displayed on the ILS line of the NAV/RAD page in either aircraft, you will be able to figure out for yourself what is going on.

Thanks to Rick for providing screen shots of your autoland on Runway 14.

Mike

 

 

                    bUmq4nJ.jpg?2

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.