Gumbodadfs

OK, so here's an update. Went back into the same flight (plan), but with an added STAR before the ILS. Also, reinstalled the WT 530 update to the stock 530. All went well until the last waypoint just before final, when "msg" in the 530, and sure enough: "approach not active". So I decide to proceed without the GPS, set nav to vloc, check that loc and GS are lit up, and - plane flies right over the glideslope - and yes, I did turn nav on and off several times before. And what makes it worse (of course this all has to happen in fog too, so zero ground reference 🙂) is that during the go-around my trim goes haywire too with the plane, until the end, is trimmed up massively, no matter what I did. To cut a long story short, I managed to land, but only by flying everything manually, and because in the fog, I did have the MSFS guides for the glideslope turned on, so I could keep the plane on the glideslope. With the trim being totally off as well, I had to push the nose down all the way to touchdown to stay on the glideslope. Crazy, and again totally reminiscent of flights two years ago when I flew a Twin Otter under similar conditions, also with a stock 530, and ended up in exactly the same kind of situation. After that, I changed plane and flew (until yesterday) the stock Beech King Air with the glass cockpit which also has its quirks, but never messes up in this way... there must be something I don't get, but I really don't know what it is.

Thanks for the reactions. I'm always happy to remove mods - the reason for installing it in the first place was that the 530 does not natively have access to the flight plan in the main msfs folder. I'll pass on commenting on that issue... but now it turns out that the mod does not have access either... Anyway after reflecting some more, I think the problem is with the way the flight plans are set up I'll try a flight today with a modified flight plan that includes a different approach routing. The flight plans where this happened in the past as well always included an ILS, and a routing where the plan would lead me to the airport first, then make a turn to follow the final in the opposite direction, a loop to get onto final and then glideslope in the right direction. And it would always mess up, completely, as we approach the waypoint where that turn above the airport needs to be made. I also looked up some recent tutorials about the 530. Will revert.

Unfortunately, I never got this far... Indeed I had set the loc/ILS frequency. What happened was that before hitting the waypoint directly at the airport, which was the "starting point" to bring me to final (sharp right turn, heading away from airport, planned "u-turn" then straight on to final/ILS glideslope), the 530 suddenly tells me "the approach is not active", and shortly after that proceeds to send me on a course directly away from my planned track, and away from the airport. I remember the exact same thing happening to me two years ago. And then, you get all sorts of other things happening, resulting in the AP doing one thing, me trying to correct/turn AP off, and the plane which is already slow and sluggish, ending up in a stall. I wish I had kept the recording I made, but it is incredibly frustrating. Edit: maybe the 530 allows to load flight plans, but then I'd like to know how to do it; until now, the only method I'm aware of is to export the plan with a name which cannot be different from fplx.pln (where x is a number) in a folder in the GPS community folder.

So here goes. I just installed the FSW C414 which is a great plane. First flight with stock 530, went fine, notably because there was no flight plan in the GPS and I had to follow the MSFS stock ATC which went OK, warts and all. Then, I added the mod which allows to load flight plans into the 530, and all went fine until, you guessed it, the approach, and I had happen to me something which I thought was a thing of the past: the AP basically crashed the plane. At some point, the AP sets the plane into a curve, and since I was set up for landing, full flaps, gear down, low speed, I had an unrecoverable stall (a couple of other things happened to as in new keyboard and trying to manage all this with a VR headset on). This happened before in I think the Twin Otter, with the same GPS, and its similarly losing the plot at the end with the approach. I know better now and will not use this GPS anymore and fly flight plans with just the VR map and the ATC guidance. The thing that amazes me though is that I used the same flight plans (LNM) with the stock Beech King Air and its built in GPS/FMD, and it all went perfectly, every single flight. Maybe a couple of interesting moments also with the approach, but none where the GPS essentially tells the AP to fly in circles around the ILS or runway endpoint to the point of making the plane uncontrollable. So since it worked in one of the stock MSFS planes it cannot be a limitation of the sim, it has to be a problem with the implementation of the 530. Amazing that this still happens after 2 years that I did not use this type of set-up. I'm happy to be told that I'm doing something wrong somewhere btw, so if there's any advice, I'll gladly take it...

On the engine start, both the mixture levers and the fuel switches have to be in the right position.

Thank you all! So: @Siouxper71I am not sure what you mean by adding ILS; I do add it correctly in LNMP in any case. @orchestra_nl Indeed, I think the issue with the ATC/AP mess at the end is because I had forgotten to update the LNMP scenery database after update 12; having said that, it doesn't explain to me why the flight path is displayed correctly both in the Flight plan in the FMS, in the map in in-plane GPS, and in the MSFS map, but the AP still ignores the star :-)... I'll try again now with updated LNMP scenery database and will update!

Hello, I did my first flight under update 12 last night. Flight plan done under LNMP, exported to MSFS PLN, flight managed via stock ATC/AP, on stock Beech King Air. LNMP database up to date until MSFS update 11. First, the flight plan loads but departure is shown in MSFS flight planning screen as "runway" where the flight plan specifies departure from parking, cannot be changed in MSFS planning screen. So I load in as is, and to my surprise plane is at the parking anyway, not on the runway. So far so good, pushback, take off, enroute etc all OK until we reach beginning of STAR. ATC hands me over to approach, and there it starts: 1. AP leaves GPS track and goes straight for LOC1 (set to ILS frequency on correct runway). 2. Cannot get AP to refocus on fight plan, so attempt APR setting from difficult angle. 3. APR setting is ignored by AP 4. ATC stops completely 5. I ended up hand-landing the plane from a position that in real life would have been 100% go-around (far too high, too fast). 6. During the latter half of the flight, the AP seemed to be ahead of the flight plan as shown in the FMS (I tend to follow that in detail because MSFS ATC completely ignores the altitude settings in the flight plan, so I have to do altitude adjustments the wrong way around: request decrease ahead of time, instead of being given decrease). Anyway, GPS/AP follows the flight plan, but the "current leg" shown in the FMS lagged behind the actual leg being flown by AP. This is the not first time this mess-up of the approach happens, but I had not seen this dduring the last 10 ILS approaches with same set-up; the only issue had been that the localiser would systematically place me to the right of the runway (glideslope etc otherwise ok). So the problem, whatever it was, seemed to be sorted out at least to the extent that approach and landing were workeable, never mind real life. Any similar experiences (am doing something wrong? - LNMP said "cannot calculate flight plan" when I prepared but I put that down to there being very few VOR/NDB on this short track). Many thanks!

Thanks again to all who reacted. Just a quick update and a question. I've now figured out how to properly plan and execute a flight including landing on ils runways - very enjoyable, MSFS does follow the flight plan except for altitude, and for this I now follow the flight plan in the plane's FMS so I can (no kidding) request the altitude changes as I need them. I also have regularly MSFS ATC telling me to climb to say 9000 from about 4000 on the last leg before I'm supposed to capture the glide slope. Go figure. Anyway, I'm now finally back to the type of planned and controlled flying I was used to in FSX, plus all in VR which is the only way I do things in MSFS now. I still use the stock King Air, but here's two rubs: 1. When I land, and I am at a correct (I assume) approach speed (90 or less), stall horn goes off just before touch down etc, I mostly float for a bit, or touch down but the nose does not unless I push it down. What am I doing wrong? Too fast? Should I not flare at all? 2. I cannot seem to be able to feather the props. I know this is an issue with MSFS (I can't feather in the Twin Otter either), but I just want to check this once again here, just in case there is a way to do this including with my controller... Many thanks!

Ha. But here's an interesting one: of course, one example is most definitely not statistical certainty. However, I did another one of my flights yesterday. When preparing the flightplan in LNM, I proceeded in the following order in terms of adding elements of the flight plan : departure (parking) - destination - ILS at destination - STAR to ILS - SID at departure - calculate flightplan. Then save, export as pln. To my surprise, the whole process went perfectly start to finish. The AP followed the whole flight plan, flew the STAR (added a wider curve towards final but OK), switched to LOC1/ILS automatically and led to a perfect landing. What MSFS did mess up, was that their ATC kept telling me to climb to my cruise altitude up until I turned on final and I was directed to contact approach, despite the correct altitudes being displayed in the plane's FD, and therefore presumably somewhere in the "consciousness" of the MSFS ATC... I of course ignored the AP's altitude calls and followed the flight plan in the descent.

Interesting discussion, not sure anyone if still watching this thread, but, I'm using LNM, and can confirm: flying the stock beech KA, I finally realised that MSFS pushes the star approach to after the destination runway. Trying to edit this in the plane's FD basically destroys the LNM flightplan loaded before, and I ended up having to re-enter the whole flightplan manually. So here's a question for Asobo: what is the point of allowing third party export/import of flightplans if MSFS is then going to do whatever it wants with them?

Ah and yes one more: whilst trying to fly the southern STAR approach, I initially wanted the AP to hold ALT, so switched off NAV and APR. The AP would have none of it and kept trying to turn me back to the GPS track. I had to turn it off completely and literally click the NAV and APR buttons several times to get it to just stick to ALT. This may be a problem with the interface between my controller (Honeycomb throttle quadrant) and the MSFS on-screen AP buttons: none of the buttons of the AP in the plane ever lights up, whether I click it on-screen, or via the buttons on the controller, for example (on the controller they do just fine). Yet another great way to fly when you can only guess from the glass cockpit screens what mode your AP is in, as the buttons don't show anything... Ah and did I mention I do all this in VR (which is itself an exercise is muscle memory 🙂 ).

Hi, selective quoting here, took me a long time to get back, because I'm quite taken by work etc and don't have nearly enough time to fly. But I managed a flight last night (trying round the world, about one third of the way). Anyway, tried the ILS approach again. Flight plan was LNM, from Noto penisula to Osaka (Itami), IFR low altitude airways. All good until I got to the last waypoint (ITE) before basically overflying the airport from the North for a STAR programmed u-turn at IKOMA to line up for ILS 32L. I get to ITE, and lo and behold, the plane switches itself to LOC1 (which I had programmed but not activated yet in AP) and starts turning towards the ILS in the opposite direction and in the wrong point on the runway. So indeed, off goes AP, I keep altitude and decide to fly the approach manually. Managed to do this in a somewhat hamfisted way(I was too low, turned final too early etc) but... decided to try ILS anyway and the AP then did capture the glideslope and brought me in almost smack on the runway (almost). And then I looked again, and something must have happened with the flight plan. I already know that MSFS will change your assigned departure runway without informing you when you use their ATC on departure, so if you don't pay attention, you end up e.g. departing in the wrong direction etc. But it works somehow because your AP will get you back to your route (never mind real world SID and other procedures). But last night, the flight plan in the plane's FD had put the landing 32L runway right after waypoint ITE, and had pushed the whole south track that was supposed to get me to the runway/ILS in the right direction, to after landing. This was done by MSFS, because when I checked the LNM flightplan again this morning, it was absolutely correct. I guess my reaction is "ah well let's see whether Asobo ever get's around to fixing MSFS' garbage ATC and flight planning mechanics..., in the meantime we'll make do and re-check the flight plan when we get into the plane"... (and stop listening to ATC for the approach cuz that's a mess anyway). On the upside: I now know how to check the flight plan imported into the FD, now I need to figure out how to correct it... And: yes indeed, who on earth designed the handling of the touch screen and the display of the NAV radios in this plane? Once you know it's fine but absolutely this would never pass certification... Thanks again all for the comments, I'll try the Black Square. Bruce: compliments on your signature quote: one of my all-time favourites.

This took me a long time to figure out. Basically the screen is a "touch screen" so you can click directly. Clicking on the heading will split the screen and get you a series of options at the bottom "map", "proc", and something else I forget but gives you the same when clicked, i.e. a series of mode buttons. On that you can click nav frequencies, that in turn allows you to set ILS in NAV 1 or 2. to change from GPS, click on the crs indicator in the main map, and you get a screen that allows you to set CDI to GPS or VOR etc.

Thank you all for the reactions, and it's a relief that you seem to run into similar things... anyway, I know how to tune the NAV1 to the ILS frequency, so that's fine. The thing that happened was that all was set (ILS tuned in NAV1, and indeed, I used xfer..., as well as CDI set to NAV1 initially). I then made the turn to final, and during the turn pressed apr. My recall is a bit hazy now but I know that the localiser/ILS was locked in because it showed in the little tab next to the heading/pitch/speed/VS indicator. I also think there was a GS bug next to the VS indicator, and, GS below the AP indication at the top of the screen. Anyway, then, instead of capturing the glideslope, the plane started turning in circles. After I had dealt with that, that's when the CDI would not capture anything except the VOR, and the ILS appeared lost. It could well have been that I was both too high and too close for the system to lock on to the GS - I did not really descend during the whole episode which maybe I should have.

Hello, I have a question regarding ILS use in the beech king air. I fly with flight plans from LNM, exported to pln, opened in MSFS, used with stock ATC. I finally figured out how to set ILS frequency and (theoretically) start the approach in the AP in the king air. However, when I activated apr mode yesterday, on final, the plane started turning in circles. Once corrected by cutting AP and lining up once more, CDI could only be set to VOR,not LOC (ils was still set correctly in nav1). So I had to do approach and landing manually, again. Any ideas on possible causes, including errors on my part? But: Please do not tell me to not use the MSFS ATC, I know it's far from OK, but the commercial non-live alternatives have their own problems, and I do not have the time to invest in learning VATSIM properly. I am happy though, if that's what it takes, to manually insert the Flight Plan in the FMS rather than loading it through MSFS world screen. Thank you!