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.

Not getting Land3 annunciation on pfd

Featured Replies

Hi all,Ive read a couple of previous threads about autoland problems, but havent seen a soluion. Here's the problem. Am i missing anything?First, to be clear, heres how i autoland.Both fd's onSet both course controls as per fmc.Set both nav radios as per fmc.I'm just using the collins mcp.Acquire localiser, capture glidescope - no problems here.Turn on second ap with cmd button after glideslope capture.I always seem to get the 'single chanel' warning, and it doesnt go away. There's no land3, flare or rollout annunciation. So it seems to me that the ap is just running in single channel mode the whole way down.Have tried fail passive and fail active settings. Am only using the 'realistic ap' setting.This was working ok before sp1, but not with sp1 or sp1b.From previous threads im not sure if this is 1. A known bug on some systems 2. Something that can be fixed in settings or 3. Something that i and other users are doing wrong.Any suggestions?

Oz

 xdQCeNi.jpg   puHyX98.jpg

Sim Rig: MSI RTX3090 Suprim, an old, partly-melted Intel 9900K @ 5GHz+, Honeycomb Alpha, Thrustmaster TPR Rudder, Warthog HOTAS, Reverb G2, Prosim 737 cockpit. 

Currently flying: MSFS: PMDG 737-700, Fenix A320, Leonardo MD-82, MIlviz C310, Flysimware C414AW, DC Concorde, Carenado C337. Prepar3d v5: PMDG 737/747/777.

"There are three simple rules for making a smooth landing. Unfortunately, no one knows what they are."

Hi Rob,By any chance are you trying to arm the second AP below 800 feet ? It will not arm below 800 feet AGL and you may have pressed the AP button and missed seeing it not arming. Instead,when you arm approach, go ahead and arm the second AP, dont wait for intercepting the GS. See if that helps . Not sure if it matters, (think it does), make sure you are using the option of ISFD and not the analogue standby instruments.Dinshaw Parakh.

Hi all,Ive read a couple of previous threads about autoland problems, but havent seen a soluion. Here's the problem. Am i missing anything?First, to be clear, heres how i autoland.Both fd's onSet both course controls as per fmc.Set both nav radios as per fmc.I'm just using the collins mcp.Acquire localiser, capture glidescope - no problems here.Turn on second ap with cmd button after glideslope capture.I always seem to get the 'single chanel' warning, and it doesnt go away. There's no land3, flare or rollout annunciation. So it seems to me that the ap is just running in single channel mode the whole way down.Have tried fail passive and fail active settings. Am only using the 'realistic ap' setting.This was working ok before sp1, but not with sp1 or sp1b.From previous threads im not sure if this is 1. A known bug on some systems 2. Something that can be fixed in settings or 3. Something that i and other users are doing wrong.Any suggestions?
Land 3 appears below 1500 feet i do think

I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card,  RM850 power supply

 

Peter kelberg

  • Author

Hi din, i'm arming the second ap directly after gs capture - so around 2500 to 3000 feet agl usually.Pete, my problem is the land3 mode isnt coming on at all. I know that single channel annunciation is normal initally, but im expecting that it will change to a full dual-channel autoland status (land3) at some stage. From my previous boeing sim experience, this usually doesnt happen when one ap is inactive/defective.Din, i must say that i have been using the analogue standby instrument option most of the time, so ill change back to isfd just to check. Seems strange to me though that standby instruments would affect this (?).

Oz

 xdQCeNi.jpg   puHyX98.jpg

Sim Rig: MSI RTX3090 Suprim, an old, partly-melted Intel 9900K @ 5GHz+, Honeycomb Alpha, Thrustmaster TPR Rudder, Warthog HOTAS, Reverb G2, Prosim 737 cockpit. 

Currently flying: MSFS: PMDG 737-700, Fenix A320, Leonardo MD-82, MIlviz C310, Flysimware C414AW, DC Concorde, Carenado C337. Prepar3d v5: PMDG 737/747/777.

"There are three simple rules for making a smooth landing. Unfortunately, no one knows what they are."

It does not matter if it is fail Op or Fail Passive Rob. Both can make an autoland.Both will announce Single Channel until below 1500 ft. ( if in APP mode )Fail Op then announces Land 3 or Fail Passive announces CMD.The major difference is that Fail Op will have Rollout as well as Flare.( You need the Collins MCP with the ISFD for a Fail Operational autoland. )It is important to use the data from FSX and not the Navigraph data. Just check the Ils frequency and course in the FSX Map !!Fred.

Frederic Steiner.

B7382.jpg

Are you using saved flights from before sp1?

Regards

 

Howard

 

H D Isaacs

  • Author

Hi chaps,I think we hit on the problem.I changed from analogue to isdf. I had tried both fail op and fail passive, but now i'm back to fail op. i also checked the fsx map and the course was 1 degree different, so i went with that.The outcome? The sweet sight of 'land 3', plus flare and rollout, which is what i want.I've got more autoland experience in sim 747s and 767s and have never had any problem getting them to come up with the 'land 3' signal. From previous threads and the tute, i already knew that i needed the collins mcp, both fd's on, both courses set and both aps engaged.What i was missing was the need for isdf to be chosen, and i was also unclear that fail passive would change the annunciations.So the advice above was very helpful, thankyou. If anyone else is having problems getting autoland to work (and ive seen a couple of threads) this may be the trick.What i'm still not sure about is the course setting. Noted above that the fmc and fsx may disagree, and fsx wins. I dont want to go to the map, as it breaks immersion and also sometimes crashes my sim. Coming in to nashville for my autoland, the course was one degree off. My memory was that the autoland/ils was tolerant of small differences between set and expected course. Is this correct? How far out can you be?I'm also wondering if any other factors are necessary for an autoland. Ive been making sure to set fo efis to radio and set minimms as well as the captain side. Any relevance at all to the autoland system? Anything else not covered above or have we nailed all the essential steps?Thanks again formthe suggestions above - brilliant! :)

Oz

 xdQCeNi.jpg   puHyX98.jpg

Sim Rig: MSI RTX3090 Suprim, an old, partly-melted Intel 9900K @ 5GHz+, Honeycomb Alpha, Thrustmaster TPR Rudder, Warthog HOTAS, Reverb G2, Prosim 737 cockpit. 

Currently flying: MSFS: PMDG 737-700, Fenix A320, Leonardo MD-82, MIlviz C310, Flysimware C414AW, DC Concorde, Carenado C337. Prepar3d v5: PMDG 737/747/777.

"There are three simple rules for making a smooth landing. Unfortunately, no one knows what they are."

May be some trouble when updating to SP.Same problem for me, I havent seen LAND3 since installing SP.Pål Chr. Berntsen

-Autoland is possible with ALL settings in ALL 737NG airplanes (well NGX anyway) - Collins, Honeywell, ISFD/Analogue standby.-there is a setting in the FMC that lets you choose whether the aircraft logic will compare LOC CRS with FSX internal CRS or (wha I believe to be) Navigraph database. Navigraph database incorporates changes of MAG VAR since the FSX was published, and so a one degree difference is not uncommon. Choose whichever option you please.-minimums setting is irrelevant to autoland operation.

--Peter Fabian 
RTFM.jpg

  • Author

Multiscotch, I've now done 3 more 'land 3' autolands, i'm not having any problems at all after working through the above. I don't know whether sp1/1b changed the behaviour of the ap eg to make it more realistic. right now im thinking it was just a coincidence and it was more to do with the fail op/fail passive and ifds settings around the same time as i installed the sp. but i do note a few comments from others about autoland problems post sp, so i spose its possible.Try working through with reference to the above and see if your 'land 3', flare and rollout come back.

Oz

 xdQCeNi.jpg   puHyX98.jpg

Sim Rig: MSI RTX3090 Suprim, an old, partly-melted Intel 9900K @ 5GHz+, Honeycomb Alpha, Thrustmaster TPR Rudder, Warthog HOTAS, Reverb G2, Prosim 737 cockpit. 

Currently flying: MSFS: PMDG 737-700, Fenix A320, Leonardo MD-82, MIlviz C310, Flysimware C414AW, DC Concorde, Carenado C337. Prepar3d v5: PMDG 737/747/777.

"There are three simple rules for making a smooth landing. Unfortunately, no one knows what they are."

Create an account or sign in to comment

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.