Adding the old Concorde flight routes to MSFS

With the impending release of Concorde into the MSFS, it would b great if the navigation system allowed the use of the three trans-Atlantic routes Sierra-Mike, Sierra-November and Sierra-Oscar that were used by Concorde. Would all a true re-creation of these routes by simmers of this iconic aircraft.

These routes run outside of the regular Atlantic corridors.

3 Likes

would ATC understand FL550?

1 Like

Hmm good point… as I understand it Concorde flights became uncontrolled above FL410 as they cruise climbed to a max alt of FL600. Its all dependent of temperature and fuel burn off to see if they get to FL600, usually the vision I have seen has it FL550-FL580. But great point ATC support as the reporting points are every 20 minutes or so on the crossing.

I wonder how Vatsim will cope :slight_smile:

1 Like

Well, you can create this flight plan using SimBrief right? and just download the flight plan file and load it up in MSFS when you want to fly the old Concorde routes.

There’s a streamer (who mainly streams DCS now) sometimes flies Concorde and on VATSIM too. Very adept with it, and procedurally strict with it, as I recall.
And of course, all those who currently fly Concorde on their own sims.
So I’m sure VATSIM is no issue with this Concorde implementation.

Someone posted here earlier asking for the waypoints. These are the waypoints for all three routes.

Sierra-Mike (Westbound Flights)
SM15W (50.41N 15.00W) SM20W (50.50N 20.00W) , SM30W (50.30N 30.00W)
SM40W (49.16N 40.00W) SM50W (47.03N 50.00W) , SM53W (46.10N 53.00W)
SM60W (44.14N 60.00W) SM65W (42.46N 65.00W) , SM67W (42.00N 67.00W)

Sierra-November (Eastbound Flights)
SN67W (40.25N 67.00W) SN65W (41.40N 65.00W) SN60W (43.07N 60.00W)
SN52W (45.10N 52.30W) SN50W (45.54N 50.00W) SN40W (48.10N 40.00W)
SN30W (49.26N 30.00W) SN20W (49.49N 20.00W) SN15W (49.41N 15.00W)

Sierra-Oscar(Alternate / Bi-directional)
SO15W (48.40N 15.00W) SO20W (48.48N 20.00W) SO30W (48.22N 30.00W)
SO40W (47.04N 40.00W) SO50W (44.45N 50.00W) SO52W (44.10N 52.00W)
SO60W (42.00N 60.00W)

2 Likes

Actually, that was me. After looking on Flightsim.to, I found the original routes and then some.

But thank you for responding. It is what I was looking for; the original east/ west routes.

1 Like

Thanks for those.

ICAO formatted for SimBrief or whatever flight planner you like and for easy copying/pasting is:

Track SM (Westbound/upper)

5041N01500W 5050N02000W 5030N03000W 4916N04000W 4703N05000W 4610N05300W 4414N06000W 4246N06500W 4200N06700W

Track SN (Eastbound/middle)

3952N06815W 4025N06700W 4025N06700W 4110N06500W 4307N06000W 4510N05230W 4554N05000W 4810N04000W 4926N03000W 4949N02000W 4941N01500W

Track SO (Alternate Bidirectional/lower)

4840N01500W 4848N02000W 4822N03000W 4704N04000W 4445N05000W 4410N05200W 4200N06000W

Chart from Gander Oceanic

(I’m leaving out FL and KIAS or Mach numbers in case your flight planner can’t deal with them, but ICAO formats will take FLs up to 600, SimBrief won’t plan higher than 999 kts, SimToolKitPro will)

If someone knows a method to reliably name custom waypoints with a newer flight planner, it’d be very useful. I’ve been spending a lot of time prepping routes in PFPX, but those will have to get exported and modded by hand, it seems, once a .pln file is exported. This will be useful for those pilots who want to be procedurally strict (and the Concorde rewards a lot of methodical planning in my experience across sims), because on either side of the tracks things get more complicated:

BA and AF charts had multiple subtracks (I think to have contingencies for weather? I’ll keep digging in my books): ‘SM1’ and ‘SM2’ forked off at 65º W just before the start of US airspace then to different decel points prior to the Marconi Beach VOR (LVZ), and about 110 nm before LINND, respectively. ‘SM3’ follows the Long Island Sound coast. ‘SM2A’ (!) splits off at 67º W to KENDA.

There are many more subtracks on the UK approaches; I haven’t been able to trace them all on the charts to be honest.

Just to make it interesting, AF and BA each had their own names for at least a couple of waypoints: ‘SM65W’ was “Sable Nord” en français about 150 mi off the coast of Sable Island, and ‘SN60W’ was “Sable Sud.” Chacun à son truc.

The CIVA units only allowed nine waypoints to be programmed at one time. BA bought card readers for theirs, AF crews had to enter everything by hand before and during each flight, nine waypoints at a time.

So similarly trying to get all this into a flight planner correctly is… part of the fun.

1 Like