Cannot fly the ILS

[HugeHickory1800]

I have been flying the MSFS2020 Cessna Longitude using the aerodynamics fix and the WTG3000 fix.

But I am having trouble flying the ILS.

I make a flight plan using Navigraph with SIDS, STARS and approaches.

I then export the *.pln file out of navigraph and into msfs2020. That has served me well.

I fly the FMS with no problem.

During the flight I load the approach and activate it.

I change the main navigational source from FMS to NAV1

I make sure NAV 1 in the radio stack has the localizer frequency dialed in and activated

The OBS changes from the magenta FMS to the green NAV1, but there is no center needle.

I line up with the approach inbound, set app button, and still nothing.

I should see a green needle centered or centering.

I should see the glide slope approaching center.

I see neither.

I know it has to be something I am missing.

Suggestions would be very welcome.

Thank you.

[B101UKNo1]

why not do something simple, like set your self to start at one of the parking spots at EGSS and don’t set a destination in the world map, so you will be cold and dark at EGSS with no route panned.

then only using the FMS/GPS plan a simple route, e.g.

EGSS |> EKVEG > MATCH > DIGSU > UPGIR >| EGSS

that will create a trapezoidal route for you to take-off and land back on rway 22 while aligning you close enough at what would be the ILS at ~10nm out.

then just set nav1 to 110.500 which is the ILS frequency with a heading of 225 (or 45 if you reverse the route).

and just test ILS works in its most basic form without setting up SIDS, STARS or using external applications

[PilotaX57]

Did you verify the approach altitude to reach the ILS-APR descent ?

I fly several times with Londitude and Dakfly mod and dont have any problems with ils at all.

The only problems are when I forgot something.

Bye

[CasualClick]

Low-hanging fruit: Double-check the ILS frequency if you’re using auto-tune - the Navblue (built-in) FMS database has some incorrect frequencies. Compare to a published chart like Skyvector, etc.

If freq is okay:

I tend to hit APR as early as 10-15 miles out. The FMS will automatically switch to LOC1 just before or at the FAF if it didn’t before. Just be sure to hit the fixes at the published crossing altitudes, as VNAV is not yet implemented on G3000.

[PilotaX57]

I dont like MSFS flight planning.
I use Simbrief also for IVAO and is my pleasure to input airports, waypoints and procedures manually in the G3000 modded by Workingtitle.
Bye

[CasualClick]

@HugeHickory1800

I change the main navigational source from FMS to NAV1

I think this is where things fall apart for you.

Leave the guidance in GPS (Magenta). Don’t touch it at all.

As long as a) you are a reasonable distance from the FAF, and b) you are descending or level at the published crossing altitude to for the fix (i.e., 1800’) then just hit APR.

It will automatically switch to LOC1 (Green Needle) at the right time, if not immediately at that point.

[HugeHickory1800]

I really appreciate this community.

Thank you all for your input.

I have read carefully all the responses and learned things I was not aware of.

I will try all suggestions and let you know how things work out for me.

[MSFSRonS]

You might want to look at my post on 1FR/ILS.

https://forums.flightsimulator.com/t/step-by-step-wt-cj4-ifr-ils-flight-from-new-york-city-to-newark-nj-includes-flight-plan-take-off-cruise-landing-2-min-to-create-fp-15-min-flight/373613/15

[HugeHickory1800]

Thank you Ron, I will check it out.

[HugeHickory1800]

Thank you to all who contributed.

I read and tried each and every suggestion.

Eventually, I found the answer in a YouTube video. Just a passing glitch. I played it back and froze the image. There was my answer.

Last night I conducted my first ILS in the Cessna Longitude using WTG3000 mod.

The problem stemmed from my unfamiliarity with the G3000 system.

I was putting the localizer into the NAV1 correctly, but failed to transfer the frequency from standby to active.

Once that was accomplished I had a center green needle that was responding to the localizer.

On a side note, I did find the APP surprisingly unresponsive to the approach. Flew the approach with NAV.

NAV would lock onto the localizer, but select APP and the plane wandered off course.

Glide slope and NAV did the trick for me.