August 7, 201114 yr Hi all,Thought I knew her well but a few moments after take off I get 'No Autoland' annunciated. Where did I go wrong?I'm in the air at the mo from KBFI to KJFK with the same call sign as my sig..Any help would be greatly appreciated. Thanks.
August 7, 201114 yr I am not an expert on this but I think this has to do with options selected in the PMDG menu's. Some combinations of options don't give you full capabilities....but then again I may be wrong. Mark. Mark CYYZ
August 7, 201114 yr Author Thanks Mark. I seem to think this is a flight configuration issue. My mistake somewhere obviously.
August 7, 201114 yr Off hand, I don't think there is a problem, as KBFI as far as I know is not certified for CAT III approaches. I assume since the FMS knows what airport you are departing it would give the annunciation if any of the ILS frequencies are tuned in on the NAV systems. Many assume that autoland is always an option, but in fact, the airport must be properly equipped navigation wise, and must be certified for CAT III approaches. Most airports do not have this certification. I could see, lesser add-on aircraft ignoring this fact and just allowing the function regardless, leading many a simmer to believe that this is a common option when in fact it's not. Welcome to the real world with the PMDG NGX! Cheers, Cpt. Thad Wheeler
August 7, 201114 yr Hi all, Thought I knew her well but a few moments after take off I get 'No Autoland' annunciated. Where did I go wrong? I'm in the air at the mo from KBFI to KJFK with the same call sign as my sig.. Any help would be greatly appreciated. Thanks. If you got a "No Autoland" a few moments after takeoff, then you forgot to turn something on or set something.There is no autoland because something or some system was not functioning or one of your IRS wasn't set correctly.I believe if the destination airport wasn't equipped for CATIII, you would get a Single CMD message or you just wouldn't see the "Flair" on the annunciator.If you are getting "No Autoland" it is because the aircraft don't have the systems working that are required for autoland. Robert Yunque
August 7, 201114 yr I had this once.The cause for me was a dogey panel load (I tried to save a panel in flight to practise landings)After AP disengage the 738WL rolled over to her right and I was unable to recover and soon crashed. All trims and controls looked normal from the controls, du and exterior, Oh well that will teach me for trying to be clever Thats the only time I have seen the "No Autoland" message. Mark Fernandez
August 7, 201114 yr Library Administrator I have had this problem with other Addon Aircraft that are advanced. I have found often it has something to do with the INS not being set correctly, or other speed factors not being input properly. This is my past expierence speaking though. Brian A. Neuman Proud simmer since 1982 using the following simulators: Sublogic Flight Simulator 1 and 2. Microsoft Flight Simulator 4.0, 5.1, FS95, FS98, FS2000, FS2002, FS2004, FSX (and unfortunately Flight!). Terminal Reality Fly 1 and 2. Sierra Pro Pilot, Looking Glass/Eidos/Electronic Arts Flight Unlimited I, II and III, Laminar Research X-Plane 7, 8, 9, 10 and 11, FS Aerofly 2, Lockheed Martin Perpar3D 2.X, 3.X, 4.X and 5.X and Microsoft Flight Simulator (2020). Not to mention numerous combat simulators and games related to flight that I have played with over the years. System: Intel I7-7700K-Water Cooled, 32GB Ram, GTX 1080Ti, 500gb SSD, 1TB HD and dedicated 1TB and 2TB SSD's for Flight Simulators
August 7, 201114 yr I have had this problem with other Addon Aircraft that are advanced. I have found often it has something to do with the INS not being set correctly, or other speed factors not being input properly. This is my past expierence speaking though. I think you mean IRS or IRUs (inertial reference system or inertial reference units). The INS is what is on the Concorde (inertial navigation system). Robert Yunque
Create an account or sign in to comment