Search the Community

Firstly, what a magnificent rendition and simulation, truly it sets the benchmark for flight simulation. Well done on an excellent product. No major issues, 2 small items that I cannot resolve by searching the associated documentation. i) No Land 3 message keeps repeating, I have I believe the required triple signals, any help here would be appreciated. ii) FMS message "Split IRS Controls" I cannot find a direct reference to this message, I realize that the navigation flight displays can be either linked to a single IRS or have separate IRS to each pilots displays. Maybe I'm missing the obvious, and just not discovering the solutions in the documentation. The autoland functions perfectly in Autoland 2 mode, intercepted horizontal and vertical aspects, and landed in virtual zero visibility at EDDM (Munich) :smile:

Name: PMDG 777 Autoland Category: FS Instructional Videos Date Added: 03 November 2016 - 07:16 AM Submitter: davidfein Short Description: Shows the details of how autoland works so you can duplicate solid landings yourself Learning to land the PMDG 777 was a challenge so I recorded a number of views of the PMDG 777 doing an autoland. Seeing the details (speed, decent rate, engine kill, flare details, etc) makes it much easier to learn to land because you have very specific things to model and practice. View Video

Greeting, First time posting here, I will try to be the most specific possible. Im try to use the autoland function when arriving to CYUL from KJFK, during descent after configuring the 2Nav radio with the 6R runway ILS and the course for both also I proceed in the pedestal to configure the altitude and length of the runway ( in this case 9600, I taught that was my error but then I tried with the 6L runway that is 11000 and still the same) I have my route configured in my FMS , in the autopilot I have engage VNAV both FD A/T etc. During final approach before intercepting the G/S because im using ATC my heading is selected in the autopilot I press VOR/LOC to intercept the G/S and the APP and CMD B immediately the plane starts to make his approach but the PFD and copilot also shows on top PILOT CH in yellow surround by a square green then the square green disapears. Around 1600 fts the computer make his checks the G/S indicators blinks and then it should change to AUTOLAND 3 but change to CMD in green but star to show FLARE in white but no rollout, I down the HUD and in the corner I have this Aiii indicator flashing instead of being fix. The plane lands perfect but I want to know what im missing. Jorge Lazaro.

Hi guys, I'm learning to fly the PMDG 777-200 at the moment and I did a flight from EGCN (Doncaster Sheffield, UK) to LEIB (Ibiza, Spain). I'm fine with the ground config and takeoff etc..., but I wanted to know how I find out the correct altitude I have to be at when I want to capture the Glideslope when trying to perform an ILS approach. I usually set this to around 3500ft which works fine in the 737-800, however in the 777 this left me way too high, causing me to have to manually descend and land even though the Localiser was captured and Approach Mode switched on. How do I find out the correct altitude I need to be at in order to capture both the Localiser and the Glideslope correctly? Would this be on the airport charts by any chance? Cheers! -YorkiesWorld

Dear fellow simmers, A couple of months ago an Airbus returned to Amsterdam after shutting down one engine during low visibility conditions (RVR 200-400 meters). I wondered if this also possible with the 737NGX, since it requires a single engine autoland. According to the manual this is possible on fail operational airplanes. The FCOM states (4.20.20 / Automatic Flight – System Description – Single Engine Landing): The FCTM contains a table (5.27 / Approach and Missed Approach - Fail Passive vs. Fail Operational Autoflight System – Approach and Go-Around – One Engine Inoperative) that states in the FAIL OPERATIONAL column and GENERAL row: However, I am unable to engage the A/T and I do not understand why. I am using the APU as a second electrical source, but I am unable to engage the A/T both before and after LAND3 is annunciated and FLARE and ROLLOUT are armed. After setting the A/T switch on the MCP to ARM it immediately releases to OFF. When I restart the engine I am able to engage the A/T. Are single engine autolands simulated in the NGX? And if so, has anybody been able to complete a single engine autoland with the A/T engaged? Kind regards, Joni Radelaar

Is there some logic on the 737-800 ngx fail-operational land3 autoland that makes it disconnect if there is too much drift from the ils on the final or for example coming in too fast/slow due wind shear or in other cases making the approach unstable? I played around yesterday putting some heavy weather to my sim using Activesky 2012. I set up crosswin of 25-30kts, heavy windshear and turbulence just to see how the autoland handles it. Though a bumpy ride, the approach went pretty good but about 200ft agl there was heavy change in windspeed increasing my ias from desired 142 to 158, soon after the LAND3 mode disconnected and I ended up flying the plane manually.. Any explanation for this? I always thought that after LAND3 has engaged its (almost) impossible to get it disconnected the only method being pulling the A/P disconnect bar or pushing TO/GA switch.. Thanks!

I have flown the flightpath from KOAK to KSNA on the PMDG 737NGX prior without any issues using the autoland on ILS 19R. However recently I have been having problems with the autoland functionality. In my case just prior to reaching the runway, the aircraft will rapidly descend and my display goes from "Land 3" to "no autoland/apch warn". I found a similiar problem described here http://forum.avsim.net/topic/441447-autoland-disaster/. I am trying to ascertain if this is a FSX bug or am I doing something wrong that I must be forgetting from the past successful landings. Below is some information on my setup: [Procedures] * FSX * PMDG 737-700 NGX * AIRAC 1407 I am flying from KOAK to KSNA during my descent into the Los Angeles region, I perform the following: * Set both nav radios to KSNA ILS 19R frequency * Set the HGS runway elevation to 54 and runway length to 5701 I got these values from the IFR plate for 19R * I set both course headings for the Captain and FO to 194 * I have set a 30 degree approach in the FMC As I approach SNAKE (int) I am at an altitude of around 3600, when I am turning to align with the runway I press the VOR/LOC button once I am facing the airport I press the APP to lock on to the glidescope, shortly after this I press CMD B and both channels are active. I then set the MCP speed to the flaps 30 which is somwhere between 133-135. During this time I am extending my flaps at the correct interval when I get to flaps 15 I drop my gear, as I get close to the runway everything is great speed is good and I am at flaps 30. However just prior to reaching the runwayr, the plane will descend quickly and "no autoland" will be displayed. It should be noted that it is not stalling as it appears the autopilot is adjuting power and dropping the nose to get lower. If i continue on that course it will drop the plane a few 300-400 feet in front of the runway. To work around this I simply shutdown autopilot all together and take the aircraft in myself, but I have in the past used the autoland feature on ILS 19R without issue. [system Info] It should be noted that I do have a dated system, on average I may only get between 8-12 fps when in these approaches so while frustrating, that could be contributing to the issues. FSX is CPU bound too, so any interrupts will cause every so slight pauses which could be contributing to the issue too. However I was able to complete these approaches using the same system in the past. My installation though has been redone. Is there anything specific about 19R that I should know about, that maybe is a bug in FSX? Is it possible that the system itself could be contributing to the problems as well? Thanks again for any help and advice. Best Regards,

I have been struggling to find information in the FCOM, FCTM and in the forums that fully address the capabilities and limitation of the RNAV approach functions in the 777. I have no problem flying CAT III ILS Autoland approaches but I want to know if the autpilot will also fly an RNAV GPS approach and to what minimums, is it possible to fly an Autoland RNAV apporach, is this even possible or make sense? Also I would like to make sure I understand the requirements, in terms of cockpit setup, to complete say an RNAV GPS apporach to LPV mins. For example the RNAV (GPS) Y RWY1C to LPV mins into KIAD. Thanks for any help or references.

Every time I attempt an Autoland I get everything setup fine it seems until it kicks over to "LAND 3". The aircraft flares to early and to shallow at about 30 FEET every time no matter how fast or slow I am going resulting in a slight bounces of my main gear and settling back down again, I have tried multiple fuel/payload options. I am missing something, any suggestions? Thank you.

Hey Guys! I have a small problem with my Aerosim Boeing 787! I Fly a flight plan just fine, and then select all the correct ILS frequencies and the CRS for the autoland. The Airport Always has CAT III autoland capabilities. The plane approaches just fine, and I set all the flaps and the speed correctly, But at the end of the Approach, When Minimums is called out, The System Hangs up suddenly and then when it starts working again, The plane stalls and crashes. It tries to climb steeply. This does not happen with any other aircraft ( Tried PMDG 737 and Airbus X). Is there any solution for this?

Hey sim pilots and real pilots. So, after i moved on from GA planes to CJ4 to FBW Airbus A320Neo (and flew around the planet in SF50, then CJ4, then A320Neo), i decided to try something even bigger and started messing around with the Salty B748 mod. I wonder if it can be set-up to land itself, and if it can, how to go about it. Whatever i did, i never manged to engage more than just the left AP at once. I'm usually in LNAV most of the flight and manage my altitude with VS. Then i switch to APP mode. The localizer frequency on the RADNAV page is properly set-up. The plane captures the glideslope, and it's able to follow it to rwy, but obviously doesn't flare, it's rarely at the centerline, and the touchdown speed is something that would probably cause an angry article in a newspaper about panicked passengers if it was in real life. Soo, not an actual autoland. More like controlled descent until it hits the ground. So, if there is a way to autoland the Salty Jumbo, how to go about it? Thaaanks!

Name: Quick Tips: Autoland Capability Category: FS Instructional Videos Date Added: 07 October 2014 - 02:33 PM Submitter: scandinavian13 Short Description: None Provided Can I Autoland on That? A discussion on what types of approaches you can use for autolands, common misconceptions of ILS, and a side note to try your own hand at approaches. View Video

I have flown the flightpath from KOAK to KSNA on the PMDG 737NGX prior without any issues using the autoland on ILS 19R. However recently I have been having problems with the autoland functionality. In my case just prior to reaching the runway, the aircraft will rapidly descend and my display goes from "Land 3" to "no autoland/apch warn". I found a similiar problem described here http://forum.avsim.net/topic/441447-autoland-disaster/. I am trying to ascertain if this is a FSX bug or am I doing something wrong that I must be forgetting from the past successful landings. Below is some information on my setup: [Procedures] * FSX * PMDG 737-700 NGX * AIRAC 1407 I am flying from KOAK to KSNA during my descent into the Los Angeles region, I perform the following: * Set both nav radios to KSNA ILS 19R frequency * Set the HGS runway elevation to 54 and runway length to 5701 I got these values from the IFR plate for 19R * I set both course headings for the Captain and FO to 194 * I have set a 30 degree approach in the FMC As I approach SNAKE (int) I am at an altitude of around 3600, when I am turning to align with the runway I press the VOR/LOC button once I am facing the airport I press the APP to lock on to the glidescope, shortly after this I press CMD B and both channels are active. I then set the MCP speed to the flaps 30 which is somwhere between 133-135. During this time I am extending my flaps at the correct interval when I get to flaps 15 I drop my gear, as I get close to the runway everything is great speed is good and I am at flaps 30. However just prior to reaching the runwayr, the plane will descend quickly and "no autoland" will be displayed. It should be noted that it is not stalling as it appears the autopilot is adjuting power and dropping the nose to get lower. If i continue on that course it will drop the plane a few 300-400 feet in front of the runway. To work around this I simply shutdown autopilot all together and take the aircraft in myself, but I have in the past used the autoland feature on ILS 19R without issue. [system Info] It should be noted that I do have a dated system, on average I may only get between 8-12 fps when in these approaches so while frustrating, that could be contributing to the issues. FSX is CPU bound too, so any interrupts will cause every so slight pauses which could be contributing to the issue too. However I was able to complete these approaches using the same system in the past. My installation though has been redone. Is there anything specific about 19R that I should know about, that maybe is a bug in FSX? Is it possible that the system itself could be contributing to the problems as well? Thanks again for any help and advice. Best Regards,

I noticed this problem the other day when I was coming into SFO on runway 28L. I wanted to test out the autoland feature so I was coming in to intercept the localizer at a heading hold. The correct frequency and heading was input manually into the CDU via the NAV RAD page, and approach was armed. The 747 intercepted the glide slope no problem and I got a LAND 3 just fine. BUT, about 100 feet AGL, the simulator would exit and say that I had crashed - presumably into the fence next to the ocean as I was about to land. During this, I can see that the plane is following the diamonds perfectly until 100 ft AGL or so, when the aircraft seems to very quickly fall beneath the glide slope markers (even though vertical descent rate did not change). It's almost as if the vertical profile is programmed to shallow out right before the runway. The aircraft maintained a constant rate of descent and did not adjust for the veritcal diamond moving upwards very quickly that last 100 ft or so. Was I doing something wrong, or is it just an FSX bug? I feel like even if it was an FSX bug, the aircraft should have compensated for the diamond moving up and shallowed out with the ILS profile?

I have flown the flightpath from KOAK to KSNA on the PMDG 737NGX prior without any issues using the autoland on ILS 19R. However recently I have been having problems with the autoland functionality. In my case just prior to reaching the runway, the aircraft will rapidly descend and my display goes from "Land 3" to "no autoland/apch warn". I found a similiar problem described here http://forum.avsim.net/topic/441447-autoland-disaster/. I am trying to ascertain if this is a FSX bug or am I doing something wrong that I must be forgetting from the past successful landings. Below is some information on my setup: [Procedures] * FSX * PMDG 737-700 NGX * AIRAC 1407 I am flying from KOAK to KSNA during my descent into the Los Angeles region, I perform the following: * Set both nav radios to KSNA ILS 19R frequency * Set the HGS runway elevation to 54 and runway length to 5701 I got these values from the IFR plate for 19R * I set both course headings for the Captain and FO to 194 * I have set a 30 degree approach in the FMC As I approach SNAKE (int) I am at an altitude of around 3600, when I am turning to align with the runway I press the VOR/LOC button once I am facing the airport I press the APP to lock on to the glidescope, shortly after this I press CMD B and both channels are active. I then set the MCP speed to the flaps 30 which is somwhere between 133-135. During this time I am extending my flaps at the correct interval when I get to flaps 15 I drop my gear, as I get close to the runway everything is great speed is good and I am at flaps 30. However just prior to reaching the runwayr, the plane will descend quickly and "no autoland" will be displayed. It should be noted that it is not stalling as it appears the autopilot is adjuting power and dropping the nose to get lower. If i continue on that course it will drop the plane a few 300-400 feet in front of the runway. To work around this I simply shutdown autopilot all together and take the aircraft in myself, but I have in the past used the autoland feature on ILS 19R without issue. [system Info] It should be noted that I do have a dated system, on average I may only get between 8-12 fps when in these approaches so while frustrating, that could be contributing to the issues. FSX is CPU bound too, so any interrupts will cause every so slight pauses which could be contributing to the issue too. However I was able to complete these approaches using the same system in the past. My installation though has been redone. Is there anything specific about 19R that I should know about, that maybe is a bug in FSX? Is it possible that the system itself could be contributing to the problems as well? Thanks again for any help and advice. Best Regards,

Hi All - Trying to learn the PMDG737NGX. Following Tutorial #1, can't get autoland into EHAM to work. Both Navs set to 110.1, Locator captured, APP button pushed... but when I push CMD-B, instead of both CMD-A and B being lit, CMD-B lights up and CMD-A goes out.. and I end up with the yellow SINGLE CH warning in the PFD ... tried several times and can't figure out what I'm doing wrong.. Newbie Rick44 (Richard Matzick) would really appreciate some ideas.. PMDG737NGX is only a week old and has up-to-date SP. thanks

Yesterday when I was landing the pmdg 737-800ngx using autoland the autopilot suddenly disconnected just after the flare and touchdown. I had everything set up correctly, land 3 annunciated, vref + 5 etc, I did not apply force to control columns either. It started the flare correctly at about 50ft, and just after touchdown the nose suddenly pitched up and made the aircraft bounce. It was like it would have toggled the go-around mode itself??The the A/P disconnection warning sounded. The A/P disconnection could have been because at the moment of the sudden pitch-up I reactively pushed forward on the stick to keep the aircraft on the runway. I believe there is a override function when you apply enough force on the columns? I was flying online using squawkbox. Ive had this problem once before, that was also when flying online.. Never when flying offline though.. Anyone else with this weird uncommanded G/A mode activation problem? (Btw I have the fail op seleceted in the pmdg CDU menu)

Hi all! Based on the past few days of flight testing and learning about the NGX, I successfully made an autoland and put the necessary steps in mind. I would like to share such to my fellow NGX pilots to clarify and clear their doubts. I'm not a real world pilot nor an "expert" but this information may help you. Here are two screenshots of my flight from SPIM-MPTO on final. The FMA and ND displays have been in "zoom mode" for clarity purposes. Autolanding sequence (important points only): 1. Place plane on landing configuration; gear down, spoilers, armed, autobrakes armed, flaps deployed in relation to final speed in FMC. Personally I use Vref + 5 as my final speed. 2. Verify that both FDs are active. 3. Make sure that BOTH NAV1 and NAV2 radios are tuned to the same ILS frequency. As per the manual, this is required for a dual AP autoland. 4. There is NO NEED to set the final rwy course as this will happen automatically once the LAND 3 mode is activated. 5. Upon glideslope intercept, engage the second AP, and the APP light will extinguish. "LAND 3" mode should appear in the FMA. Flare and rollout modes will be armed. Note: You will NOT be able to engage the second AP before the g/s intercept. 6. Make sure that the heading selector is set to runway heading and altitude is set to the missed approach altitude, in case of a go-around. 7. At this time, the final course will be shown on BOTH captain and F/O course displays. This is now "locked" and you cannot adjust the course value manually. 8. On final descent, your will hear the altitude callouts (as set in options menu in FMC). 9. Just before touchdown, flare mode becomes active and rollout mode will follow. At this time, engage reverse thrust and verify that spoilers have been deployed. 10. Autobrakes will also kick in and at 80 kts place the thurst levers in idle. At 40-60 kts, press and HOLD the period key (for 1-2 secs) TWICE disengage the autobrakes. 11. Exit the active runway and perform the after landing checklist.

Hello, Nowadays I'm trying to make ILS landings with my darling B737ngx pmdg I land it smoothly without problems but my problem is a bit technical. Anyway, let me ask questions 1 - In approach charts, there are ils without category such as ILS/DME Rwy 17L.Why they don't indicate CAT? As I know, all ILS systems must have a CAT. 2 - I want my flight is closer to real life so in reality, All runways doesn't have CATIII in reality so when an ils system become disabled that is CAT I or II? Is It already written in the charts? or where can I learn it? According to this, I will turn off A/P and try to land manually as if the ils is disabled. 3 - What is the difference between Radio or Barometer Altitude Settings? And what does Aproaching Minimums....Minimums...Minimums ! callouts mean? Note: This is my first topic on the avsim forum. So there might be some violations of rules and I know my english is suck and i wish you will understand it. Sorry

I have just completed a CAT III autoland instructional video. However, this is a ground school type of instructional video providing a solid background on all of the aspects of making a CAT III autolanding. It also covers everything you need to know about CAT I and CAT II ILS approaches. It is in a Power Point presentation format and is not done in the cockpit. This is what I mean by ground school format. The video is 40 minutes in length and covers the history of CAT III autolands, autolands in general and finishes up with the individual components that make it up the parts of the PMDG 737NGX system such as the ISFD, Fail Operational vs Fail Passive; and exactly what LAND3, LAND2 and NO AUOLAND mean, etc. Then ends up with showing the Boeing standard CAT III ILS autoland steps and sequence. Target audience is those new or fairly new to the PMDG 737NGX and those who do not have an instrument rating and therefore may not know or fully understand why there is a Decision Height (DH) vs an Alert Height (AH) and when you should use each one. I hope you enjoy: Thanks...