Honestly I can’t have enough of this plane, it is the most fun plane I have rn in MSFS.
Surely the Cessna 414, the FBW A320 or the CRJ are excellent and maybe more reallistic, but the Concorde is a blast to fly, and way more complex than I expected given the price.
For now I have more than 20h in it, and I expect that number to grow by a lot in the following weeks 
I made it to JFK in 3:44. The Concorde performed very well with only a few minor issues.
Like others I couldn’t make it to 60K even after waiting until under 45K fuel. Highest I could make it was 56K. And I could only do M1.96 the whole flight. ISA varied between +0 and +6 and skin temperature was about 115 so I don’t know what the issue was except that there was a headwind. Don’t know if that was a factor.
I still am having trouble with the ILS Localizer. It seems (for me) VOR LOC doesn’t work, but that may be the general problem many people have reported in not capturing localizers in MSFS. I might have caught whatever bug it is. But strangely, the GLIDE button captures not only Glideslope but Localizer too, so that’s my workaround for now.
I set JFK DME (115.90) in both ADF1 and ADF2 but I only saw a distance in the DME2 readout. DME1 showed only 0.0 miles. Not sure if I’m using that right though.
Fuel management was not trivial but pretty easy and I didn’t have to babysit the plane during the flight. The new checklist (in v1.0.2) was very nice and much better. Thanks for the work. I hope that there will be more updates continuing with improvements to dials and gauges as well as systems functionality and autopilot modes.
Well done! 
Concorde rarely made Mach 2 and FL600 on the JFK route as the atmosphere is generally just too warm. It’s testimony to @CodenameJack447 incredible work on the flight model and the amazing atmospheric modeling in MSFS that this reality is realised in the sim.
I’ve never used VOR LOC for AUTOLAND or ILS approaches - just hit GLIDE or LAND as you describe and it will detect the GS and localiser.
Not sure about the DMEs - I’d imagine they are maybe designed to display different ADF signals but can’t be sure, Jack will know more about that.
Many more updates to come, this is the start of the Concorde project really, not the end of it. Better textures, modeling and systems is all on the list, really glad you enjoyed the JFK run and that it went well for you
One more question – I’ve noticed since the latest update, my CG bugs don’t align with the manual’s TakeOff/Landing of 54% CG and 59%CG for supersonic…
Do I try to follow these yellow bug lines OR do I follow the manual’s recommendation of 54% and 59%?
The FWD & AFT bug markers represent Mach CG Limits, not CG. The white marker on the left represents the actual aircraft CG which is reading 53% MAC there. The digital counter in the centre reads Main CG computation ( which you don’t need to worry about too much, but it’s a handy reference to quickly identify if fuel is moving as commanded ).
So it’s the white marker on the left of the gauge, which needs to remain centred between the FWD and AFT markers. You can get away with it being outside of them for short periods, but it will affect Concorde’s performance and efficiency in the long term.
54% MAC for takeoff and landing, 59% MAC for Mach 2 flight, are the correct primary figures.
Thanks Dean – you and @CodenameJack447 are always so helpful. We appreciate it. I LOVE THIS BIRD!!!
One other quick question for anyone who knows – if you get over 2.1 mach, like I am right now at 2.17… should I engage auto throttle (I’m at cruise level) or keep my manual throttle all the way forward?
i.e. Autothrottle is engaged, MAX cruise is engaged, but it keeps going faster and faster (2.17!!) – what am I doing wrong? Autothrottle doesn’t seem to work.
I cannot seem to get 1.0.1 or 1.0.2 working. There is a black screen which appears after I try to load the plane into an airport from the world map. MSFS does not crash, but it does say not responding when I look at it in the Windows task manager. 1.0.0 works fine. I had no issues until I tried to update the concorde. Any ideas?
This happened to me. Uninstall it completely, reinstall and voila.
Thanks for your suggestion to leave the VOR LOC alone and just use GLIDE. I think this was part of my problem. Also the post about changing the Approach Freq. on the panel only sets secondary unless you push the center button. (I didn’t know there was a center button). Now I have everything working, and, as others noted, this is a really fun aircraft to fly.
Well done.
Were you using auto throttle when you only reached 1.96? I’m experiencing the same, but with autothrottle turned OFF, I can get 2.14 currently at 60k.
can someone try ILS approach at Dublin, EIDW, rw28
try to see if you can intercept the ILS (freq 111.35) using LOC
I think the crs is 277 if I remember correctly (should auto tune)
Im having some issues
Try using GLIDE instead of LOC
Yes auto throttle on. Max Cruise selected. Max Cruise doesn’t work without auto throttle being on. You shouldn’t exceed M2.05 anyway.
Understood, but I think this latest update has changed something with MAX CRUISE on… it doesn’t seem to reach 2.04 mach on it’s own when autothrottles are armed and max cruise armed. So when I turn MAX CRUISE off and just use my throttles manuallly, I can go past 2.04 easily. It’s weird.
I agree. I hope the developers will chime in here.
You have always to respect 53,4% CG for take off. Said that no matter fuel total amount, respect the CG number.
With autothrottle on press Mach hold first (the left button, not the right on), and then engage max cruise. Should work.
You can pass 2.04 easily depending on isa temps, or if you go with afterburners on.
Max speed of Concorde is somewhere near 2.24 Mach. 2.04 is the max cruise speed.
He’s not talking about maximum speed. He’s talking about how the behavior of Max Cruise appears to have changed in 1.0.2. For example, it previously wasn’t necessary to press Mach Hold first.
