Haven’t played the Concorde in a while so going off memory. I remember it finally working when I made sure the ILS frequency was plugged into both nav 1 and nav 2 and even on standbys and the INS/RAD switch to the left of the autopilot controls was on ILS.
Thank you for your response but still nothing. It does not pick up ILS even though I have the same freq in standby and NAV1,2. I fly at 5000ft in the direction of the airport on INS. Once flicked to Radio signal it starts getting wrong and aircraft follows pinguins. So unless you also do something else in FMS this plane is a lost cause.
Ok I figured out what was wrong. ILS frequency was wrong all the time. It seems this needs to be validated with real settings at all times. I can finally land everywhere.
1 Like
Glad you got it figured out!
Sorry to resurrect an elderly thread, but I am having similar issues in my Concorde.
Scenario: I’m flying from Stansted to Glasgow, a route I have flown many times because it’s my default test route for getting used to airliners. Concorde is behaving impeccably right up to when it should lock on to the ILS, which it refuses to do. The localiser line is showing on the HSI, the glideslope is too, but trying to lock onto it simply does nothing. The plane ignores the glideslope and the localiser and just carries on at the same altitude and heading.
At first I assumed it was pilot error and I hadn’t pressed the right buttons, but the following day I tried the same flight again and the same thing happened. I went around four times trying to get the aircraft to grab the glideslope and localiser, and no joy. I knew it was tuned in right and picking up the beams because I could see them on the instruments. It was just refusing to follow them by itself. Eventually I hand landed it on my fifth approach.
So, the sensible thing was to test it again to work out what’s going wrong, and this is what was odd. I took off from Glasgow this time, flew out to the same point I had begun my approach, with all parameters the same - atlitude, airspeed, fuel weight, intercept angle, the lot. And it worked perfectly. So I tried again. Once again, perfect glideslope capture and autolanding.
None of this makes sense to me. Searching around the internet I have found one other person reporting that using the INS nav system in the flight before using the radio nav stopped it from working, but then they backtracked and said it was because they were at too high an altitude. But that’s the only difference I can think of.
Any suggestions?
Hey guys - is anyone having problem with Concorde NAV radio not changing ?
I dial the Mhz and Khz knobs but the numbers on the NAV radio don’t change - just stays stuck on 113.30 (or whatever the default is).
It used to work but now has stopped working.
If that only happens to you for ILS and you fly by FMS, set the ILS frequency b4 setting the approach in the FMS
My AP just dont work ! Cant do anything ! Nothing works on Concorde ! Broken addon! needs hot fix !
Hello there, I see you got quite a few problems there with the concorde.
The DC Designs Concorde’s ILS behaviour is very similar to the Asobo one, here’s how:
When you click the LOC button, it doesn’t wait for a signal, it just turns instantly assuming its there. And you can’t arm the APPR button like the Fenix or PMDG or any other half realisitc aircraft for that matter.
Here’s how I fly it:
I don’t directly line up with the runway using the HDG select, I intercept the localiser at the shallowest angle I can, so I don’t fly 90 degrees straight through it, and I keep my speed around 190 as that was the noise abadement procedure back then.
I press the LOC button once the localiser track starts moving on my HSI and normally I end up with a tiny overshoot which is corrected pretty quickly. The glideslope is self explanitory, just click the LAND button once the G/S indication goes through the line that represents your aircraft.
One problem I currently have is the actual ability to fly the ILS. The aircraft makes adjustements once in a blue moon once it’s established, so slight deviations from the localiser is a known bug for what I know.
I hope this helps and happy flying!
1 Like
Just my 2p for anyone who gets to this thread. I have always found THIS the sure fire way to intercept any ILS.
- ensure you are in RAD, and not ILS mode.
- dial in the heading toward the ILS (max 15 degree offset), then hit TRACK so you are manually flying toward the ILS beam, and track your flight in.
- Slow to 200, 190 and ensure your nose is down
- dial in the ILS frequency on NAV radio on the captains “NAV STBY” panel, then hit the middle button to “ENTER” that frequency in.
- once you start to intercept the < markers both horizontally and vertically, (ensuring you are BELOW the ILS beam and “fly into it”), quickly hit the INS button followed by LAND
- the INS button will make the aircraft “try to turn”, then LAND will “catch” the ILS beam and you will start to descend.
- There is a NEW autoland instructional video on DC designs youtube, I might try this as well. untested right now.