I do not seem to be able to fly the ILS 07 approach at ENML Molde in FSiPanel. It should be easy to set up, and yet I always have to engage LNAV and VNAV to get my plane to capture the glideslope. In other words, I end up making the approach with LNAV and VNAV. It never seems to capture the ILS signal.

I am using the ORBx version of ENML Molde.

Which aircraft?

PMDG 737-600

7 hours ago, Christopher Low said:

I do not seem to be able to fly the ILS 07 approach at ENML Molde in FSiPanel. It should be easy to set up, and yet I always have to engage LNAV and VNAV to get my plane to capture the glideslope. In other words, I end up making the approach with LNAV and VNAV. It never seems to capture the ILS signal.

I am using the ORBx version of ENML Molde.

Do you see all the relevant data on the APPR PFD screen? Also the magenta horizontal LOC and vertical GS markers appear?

Does your NAV radio beep over the MARKERS?

ENML ILS07 OK with FSiPanel.

Could you do a couple screenshots of your PFD and MCP during your approach?

 

 

Edited October 12, 20241 yr by vonmar

I have solved the problem. FSiPanel sets up the approach at a heading of 070 degrees on my PC. This is slightly to the right (only two degrees) of the precise approach path, but it seems that this is enough to prevent capture of the VOR/LOC signal first, and then the ILS. When I noticed this, I tested again, and turned my plane to a heading of 068 degrees at the start of the approach (for the record, this was at 17nm out, and an altitude of 4600 feet). This time it captured the VOR/LOC signal, and shortly after that the ILS. The landing approach proceeded normally after that.

Subtle, but significant

Edited October 13, 20241 yr by Christopher Low

On a side note, I like to use the terms "Battlestar Approach" for runway 07, and "Galactica Approach" for runway 25 at this airport

ENML ILS07 CRS 070 is correct on the Approach Plate, in FSiPanel and dialed on the PMDG-600 MCP (screenshot).

FSiPanel Heading 070 to start the approach (LOC intercept) for your training is ok.

Note: HDG 068 (CDU) is the heading to the next waypoint.

 

 

It does not acquire the signal at 070 degrees on my PC.

36 minutes ago, Christopher Low said:

It does not acquire the signal at 070 degrees on my PC.

Could you do a couple screenshots of your PMGD-600 PFD / MCP when:

FSiPanel starts just before you take control

Without you making and CRS or HDG changes

Just after you take control without any changes to that FSiPanel start up

 

Edited October 13, 20241 yr by vonmar

I have taken three (one just before taking control, one just after taking control, and one after selecting APP on the MCP)

https://www.mediafire.com/view/5qku38dt0n1suvk/Molde1.jpg/file

https://www.mediafire.com/view/l7wzfcv4lxb5b6i/Molde2.jpg/file

https://www.mediafire.com/view/1qe72f20yujvnex/Molde3.jpg/file

Edited October 13, 20241 yr by Christopher Low

I have just noticed that the PFD does not have the landing reference (flaps/speed) indicated. I checked at another airport with an ILS approach, and that reference is automatically set and displayed by FSiPanel.

2 hours ago, Christopher Low said:

I have just noticed that the PFD does not have the landing reference (flaps/speed) indicated. I checked at another airport with an ILS approach, and that reference is automatically set and displayed by FSiPanel.

Reboot PC.

Set up your FSiPanel approach again.

Edit: possibly you did not tell FSiPanel you wanted e.g. Flaps 30 set for the approach.

Do a screenshot of FSiPanel before Move Aircraft.

Edited October 13, 20241 yr by vonmar

2 hours ago, Christopher Low said:

I have taken three (one just before taking control, one just after taking control, and one after selecting APP on the MCP)

https://www.mediafire.com/view/5qku38dt0n1suvk/Molde1.jpg/file

https://www.mediafire.com/view/l7wzfcv4lxb5b6i/Molde2.jpg/file

https://www.mediafire.com/view/1qe72f20yujvnex/Molde3.jpg/file

Ok
Your screenshots were helpful.

No problem doing your own vectors and V/S.

However, your FSiPanel setup from 15nm out (Clean) at 4700 feet you could:

Take control
VORLOC (button on MCP) LOC will capture
Dial lower altitude e.g. 3800 
V/S e.g. dial -1500 down to 3800
Flaps on schedule / bug the speed
APP  (button on MCP) G/S will capture

I have screenshots if needed.

The reason I used 4600 feet is because the waypoint VEXAP is 4600 feet at 15.9nm from the runway threshold. The flaps were already set to 30 in the menu.

Edited October 13, 20241 yr by Christopher Low