I use the X56 too so it’s not the hardware. Does it happen if you start cold and dark?
Not tried that yet, I just want to get her up in the air…I’ll try and learn the systems later if possible
Maybe that’s the problem. If you’re frustrated that you can’t fly, why not learn the systems so that you can?
The new checklists make it very easy
1 Like
VOR LOC is not what should be used for an ILS approach and landing - that’s for VOR navigation. GLIDE or LAND, with both autopilots engaged, will detect the localiser and GS. I have never see it miss in all the months of testing.
3 Likes
A couple of users reported that MSFS had bound their Mixture cut off to their mouse ( they didn’t do it, it was just set that way ). That kept switching off their engines. Worth checking. I also use an X56 and have no issues with it so it’s definitely not Concorde doing this to you.
( Mixture cut off should not apply to jet engines, but it does in MSFS, another bug they still have not fixed )
Hi,
Noted that the compass cards of the RMI’s have a severe lag when maneuvering. They should be synchronized with the compass card of the HSI. The HSI compass card of the HSI seems to move correct. Note the heading difference between the RMI’s and the HSI in the screenshot.
Also, while the white VOR needles on the RMI point correctly to the VOR, the ADF needles do not. They should point to the NDB station, which is about on a 130 bearing from the present position in the screenshot.
The Flight Director cannot be trusted. During a right turn, the FD commands to further bank to the right which would result in a overbanked condition if followed. The pitch needle commands a pitch up to over 20 degrees nose up while in level flight. The pitch and roll command bars should line up with the aircraft symbol during a steady level turn.
Would be nice if this could be corrected. Many thanks in advance!
1 Like
got a question, I have in the overhead panel the icing warning light on, I switched on all 4 engine anti ice switch there and fuel heating, but it seems it just clings?
So VOR LOC is not to be used for intercepting (and following) the localizer? That was confusing to me.
Can I ask what mode you are supposed to use for intercepting and following the localizer laterally?
I figured LAND and GLIDE was for following the GS. (Like the typical APP mode)
Every since I took Dean’s advice in having a final of least 15nm I have had no issues with it picking up the glideslope. I vector myself using trk heading, switch to RAD, wait for the needle to jump (picking up the ILS) and then I hit INS and then Glide. The reason I hit INS is just hitting glide doesn’t pick up the LOC for me but hitting INS does.
ok if I understand that last paragraph (think I need more coffee), pressing GLIDE will automatically engage VOR LOC, and that will follow the localizer.
I’ll tell you my opinion and without wanting to offend you: you should stop looking for ghosts where there aren’t any.
INS is the same NAV event you have seen in other planes.
VORLOC responds to the event LOC you have seen in other planes.
GLIDE responds to the event APP you have seen in other planes.
I don’t know how many videos we have to make to show an ILS landing. but in any of the two that I uploaded I went with alt hold.
1 Like
Thanks, added to the update list for checking. Compass cards might just be the choice of code variable used. ADFs were working fine last time I used them though. FD set-up is Jack’s territory but he’ll know what to do 
I think it should but for me it doesn’t I have to also hit INS (WHEN in RAD mode) and then glide and it perfectly flies down to the runway for me
This is interesting, I have never used the INS button when using AUTOLAND as it should only have an effect with the RAD/INS switch in INS mode - I will test this tomorrow.
The ILS intercept works well when aligned like 15nm out, as recommended by Dean.
However when flying some approaches that have a sharp turn from the IAF to the final e.g. Madrid LEMD ILS V Rwy 32L ASBIN transition or something similar, it becomes a miss. Such approach procedures doesn’t seem to suit the Concorde autopilot.
Everything else including the fuel management is a such great joy to fly.
1 Like
Possibly it’s actually just picking up the NAV again and not actually the LOC as I think but it’s being taking me down to the runway every time where as just hitting glide keeps me in trk heading and I have to manually make course correction to keep on the LOC
1 Like
Doing some practice landings at Shannon and pressing just glide or land it’s picking up both the glide & LOC for me now everytime 
@DEAN01973
1 Like
I’ve done several successful ILS landings – I don’t touch the VOR LOC button. I ensure my NAV RAD button has the correct ILS, then when I turn onto the final leg of my approach, I click LAND and GLIDE and it works flawlessly.
2 Likes
So that is what is confusing. Most people are used to VOR LOC being used for localizer. I can accept that this is not the case in Concorde, but this should really be explicitly spelled out somewhere because I and many others apparently have missed it.
Also, do we have to have the localizer frequency in both NAV1 and NAV2? If the localizer frequency is only in one Nav radio, how do we tell Concorde which one to follow? I.e. how to select NAV2 for ILS? Or is that simply not possible?
Also the localizer signal does not require a course entered in all modern aircraft. Is this also true in Concorde?
1 Like
That is not true. @DEAN01973 just stated the opposite a few posts above you. According to him
“VOR LOC is not what should be used for an ILS approach and landing - that’s for VOR navigation.”
I’d be happy to provide you a video showing how it does not work for me. I’ll try to get that done today.