Jump to content

Flightplans Concorde Routes In Current Airacs


Kyprianos Biris

Recommended Posts

Kyprianos Biris

Equally you could put KESUP/N0550F280 which means I will be steady 550 TAS F280 by/until KESUP.

Link to post
Kyprianos Biris

Ahh, Martin Tornberg makes an appearance!

I notified him of this post because he's one among the most active CONC pilots & (domestic) ATC on VATSIM ;)

Link to post
Jonathan Fong

I notified him of this post because he's one among the most active CONC pilots & (domestic) ATC on VATSIM ;)

Indeed he is :) I've got him on my "Alert when Online" list on VATTASTIC, and 9 out of 10 times when I log on he's flying Concorde!

  • Like 1
Link to post
Charan Kumar

The documentation has probably not been updated in years since it was written. the UK ATC is pretty spot on, as you approach MERLY/UPGAS, whatever is in your FP, they will call you ahead of time to ask if you are ready for transonic climb at that way point, assuming they aren't too busy. And as Martin mentioned, they also catch the step downs and will offer ahead of time.

Link to post
Jonathan Fong

petakas, I have a few more updated routes for you. I'll send them over via PM so as not to clog up the thread too much. By the way, I'd recommend changing NAT_S(letter) back to NATS(letter), as the former won't work on some pilot clients (at least, it doesn't on vPilot).

Link to post
Kyprianos Biris

By the way, I'd recommend changing NAT_S(letter) back to NATS(letter), as the former won't work on some pilot clients (at least, it doesn't on vPilot).

Why does it not on vPilot.?

Explain further please !

In the flight plan route you can enter any text.

The below is yesterday's flight submitted via vPilot. Look at the route details.

http://www.vataware.com/flight/56a26cda5352334323000015

Link to post
Jonathan Fong

Why does it not on vPilot.?

Explain further please !

In the flight plan route you can enter any text.

The below is yesterday's flight submitted via vPilot. Look at the route details.

http://www.vataware.com/flight/56a26cda5352334323000015

Nevermind. On further investigation, it seems to work when copy-pasting text into it, but doesn't work when typing it with my keyboard. Will look into the issue.

EDIT: Apparently that's intentional. You can force vPilot to put an underscore in by copy-pasting it from somewhere else, but you can't type it in by yourself.

Link to post
Andrew Wilson

From the bottom of page

I wonder why they suggest this point. Its still not within 20nm from shore.

MERLY point (51 20 00 N 005 00 00 W) is the earliest you can assure 20nm separation from coast and hence the beginning of the Transonic phase.

The above suggested coordinates at the bottom of the guide are 43nm before (east of) MERLY just 6nm from coast of Bristol Channel.

It's to do with the sonic boom projection. IIRC the majority of it is projected forward, hence why they accelerated at UPGAS.

Link to post
Jonathan Fong

It's to do with the sonic boom projection. IIRC the majority of it is projected forward, hence why they accelerated at UPGAS.

This, and the fact that they still had to wait/ask for ATC clearance to accelerate and climb as well as start climbing, during which the aircraft is still moving forward. The aircraft's already covered quite a bit of distance by the time it breaks Mach 1.

Link to post
Andrew Wilson

No no - ATC clearance to climb and accelerate was obtained long before reaching the accel point so that the acceleration could commence at the exact point defined.

Link to post
Jonathan Fong

No no - ATC clearance to climb and accelerate was obtained long before reaching the accel point so that the acceleration could commence at the exact point defined.

Oh, well then. Just used to VATSIM, I guess. Usually, on there they give you the clearance right when you pass the accel point, not before and rarely after (if ATC is busy - see CTP).

Link to post
Kyprianos Biris

I use this

KJFK JFK J37 MSS DCT YMW/M095F320 J524 YUY 5055N08200W/N0750F320F600 5159N08700W 5208N08900W 5215N09100W 5219N09300W 5222N09500W 5222N09700W 5220N09900W 5217N10100W 5211N10300W 5204N10500W 5155N10700W 5155N10900W 5155N11100W 5155N11300W 5155N11500W DCT WASEN/M095F380 DCT YNY J508 BOOTH CYVR

2317 nm

Link to post
Kyprianos Biris

Check the 5055N08200W with the / after it. There !

Also check WASEN later by where you go again subsonic.

Link to post
Kyprianos Biris

First of all, we are virtual pilots here and not travel agents so it would help if you used ICAO codes rather than IATA !

So you refer to an LFPG - LPAZ - SVMI route.

When you descend with Concorde you reach Mach 1 at 130~150nm (depending on atmosphere) from destination so for coastal airports (cities) you have no issue.

For destinations further inland just take in to account that if they are beyond 110nm from coast you will need to descend proportionally earlier to cross the coast at Mach0.95 / FL290~330 / 55% CoG with a subsonic cruise last portion for your flight (not the case for LPAZ & SVMI).

For LFPG departure just accelerate at the point you leave land beyond 20nm.

For your en route section, 450~420nm from SVMI you have the southeast series of Caribbean islands which are 10~30nm apart so you cannot avoid "booming" them. I do not know where AF flew from to cross this series of islands.

Your only option is to route east, south and then west of Barbados TBPB where you can manage to stay off 20nm from coast while supersonin to SVMI.

SVMI is coastal airport so you have no issue there.

  • Like 1
Link to post
  • 1 month later...
Anthony Pape

For EGLL-KBOS, the current route you have is this:

CPT DCT MALBY DCT KESUP DCT MERLY DCT LESLU DCT 5041N01500W 5050N02000W 5030N03000W 4916N04000W 4703N05000W 4610N05300W 4414N06000W 4246N06500W 42N067W DCT LFV DCT ARMUN DCT OOSHN

I thought maybe for easier transition to the STAR, you replace LFV ARMUN OOSHN with:

4267N DCT FERNZ OOSHN3?

I don't know if it's easier this way, but I'm planning this trip currently and noticed that ARMUN nor LFV aren't part of the OOSHN STAR.

Thanks for the conversions on everything, it really makes my life simpler (especially the subsonic points!)!

Link to post
Jonathan Fong

Actually, Concorde can't fly the OOSHN3 STAR. Originally, it flew via the SCUPP3 STAR (back in 2003) which was non-RNAV and started from the waypoint SCUPP; however, since that's been replaced by the OOSHN3 RNAV STAR from OOSHN, you'll have to request radar vectors past OOSHN.

Link to post
Anthony Pape

Actually, Concorde can't fly the OOSHN3 STAR. Originally, it flew via the SCUPP3 STAR (back in 2003) which was non-RNAV and started from the waypoint SCUPP; however, since that's been replaced by the OOSHN3 RNAV STAR from OOSHN, you'll have to request radar vectors past OOSHN.

Oh, Concorde can't do RNAV SIDs/STARs? That make sense.

Link to post
Jonathan Fong

Yes. The INS is unable to perform RNAV1 or above arrivals, even though it does have (very) basic RNAV capabilities.

Link to post
Jonathan Fong

Just letting everyone know - petakas and I have been working on updates for the modernized routes given in the thread, and now you can see some of the fruits of our labors! As you can see in the main post, some of the flight plans now have flight plan download links, which are essentially FSX format flight plans (.fpl files) which have been checked and modified for Concorde use (altitude changes, waypoint names corrected, etc.). The raw route format is still being kept, though, so that you can more easily input the route into tools which don't accept .fpl file imports. If a specific route has "3/2016 update: ATC & Raw route & .PLN download on fcisuperguy's initiative" or something along those lines in the changelog, you'll know it's been modernized. So far only routes from EGLL have been updated, but we're working on the others as well and will post them once we're done.

  • Like 2
Link to post
  • 6 months later...
EgyptianAviator
On 4/15/2013 at 10:53 AM, petakas said:

Because I always fly the Concorde on line on VATSIM network with live ATC and because there I am also an ATC (controller) I was always wondering about the original flight plans (FPLs) of Concorde and the fact that some points/names used in there are nowadays out of date in current AIRAC cycles and hence the FPLs will not appear as they should in today’s virtual ATC’s radars.

Note: This post is not VATSIM specific but applicable to IVAO flights as well since in both networks Controllers use relatively latest AIRAC data for their Radars.

I saw this issue from the ATC’s perspective since I have seen enough invalid FPLs in other areas and having to amend them and then pass the revised clearance to the pilot is always a pain for both. Also this is a hobby and nobody is “obliged” to fly the correct FPL unless they want to simulate correct routes flying properly.

For example NATSM or SL2 or SM2A means nothing in today’s airway names and would not generate the intermediate points of these old airways in the ATCs flight strip or radar screen as it used to do in the past.
Another example, UPGAS is nowadays a border fix between EGPX Scottish and EKDK Copenhagen FIRs actually too close to London FIR (in ATC perspective) so as not to get it confused. So for the EGLL CPT departing (original) FPLs you may get a track line drawn on your ATC radar from MALBY (west of London) over to Denmark border and then back to MERLY sw of Swansea !

Examples of what nowadays software recognize:
Its the EGLL KJFK flight from another pilot flown with the old format.
[Pending due to vataware UI update]
Blue is route recognized by today's AIRAC, red is route actually flown on line on VATSIM network.
[Pending due to vataware UI update]
Same route, updated to current AIRAC flown by me recently.
1/2015 Note: vataware is in software change process and old links of specific flights still do not appear. It should change soon.

Another reason that I needed current flight plans is that I use software - FSBuild, VROUTE etc. - that generate flight logs and export importable flight plan files in various other utilities formats to be used for FS weather and other flight planning software like (Active Sky, FSCommander, Jeppesen JeppView4) and simplified paper printed flight logs with coordinates etc. If these programs do not get input in current AIRAC Fixes/Airways format they simply don’t generate the flight plan export files. These files are needed for quick and seamless preflight preparation in FS so I don’t loose valuable time setting up the flight with side running software.

I have never provided ATC in VATSIM areas where the Concorde still flies (virtually) from but thinking about these inconsistencies and the flight planning software needing current AIRAC data flight plans, I tried to create new ones as close as to the original Concorde ones (track over earth, turning points, deceleration/ acceleration points, total mileage, equivalent SID-STAR points etc.) so that today’s ATCs and flight planning software can handle them more easily.

Therefore below are few FPLs as I submit them with current data validity for routes that Concorde used to fly. This is also the form I submit them when I fly. All popular FS flight planning tools like FSBuild , VROUTE etc. will generate the flight log and exported files properly with these routes.

KEY:

Real Callsign: Callsign used during real life operations

Distance: Distance of the route in nautical miles

Subsonic Until: Remain subsonic until a given waypoint

Deceleration Point: Begin descent and deceleration at a given waypoint

Alternate Airports: Alternate airports available if it is necessary to divert.

FP Download Link: Download a provided flight plan for the routes in FSX ‘.fpl’ format for use with fuel calculation tools, moving maps, etc.

ATC Route: Route to be submitted to ATC if/when flying online (VATSIM/IVAO)

Raw Route: the route in point by point format if needed so that it can be imported in flight planning tools that do not accept the ATC route format

5-digit airac waypoints format: Used for route extraction via tools like VROUTE, FSBUILD etc. Depends on existence of waypoints in AIRAC cycles nav. database

7-digit Coordinates format: (see Meese's post on this) The flight plan as it would be filed with 7 digit simple coordinates format (minutes only without seconds) independent from nav. databases and tools.

1/2016 NOTE: As of 2016 flight plans will be progressively converted to 7-digit and 11-digit coordinates as the original ones and obsolete AIRAC fix waypoints will be replaced by nearest alternative ones.

________________________________________________________________________________

 

Westbound Routes

 

EGLL-KJFK

Real Callsign: BAW1/BAW3

Distance: 3150nm

Subsonic Until: KESUP

Deceleration Point: 60nm from KENDA

Descent Target: 14.000ft by OWENZ

Alternate Airports: KEWR, KBOS

 

Download Flight Plan Here

 

ATC Route:
N0550F280 CPT L9 MALBY DCT C/KESUP/N0740F280F450 DCT MERLY UL180 C/LESLU/M200F450F600/M200F450F600 DCT 5041N01500W NATSM 42N067W KENDA/M100F490 N7A OWENZ DCT CAMRN

 

Raw Route:

CPT DCT MALBY DCT KESUP DCT MERLY DCT LESLU DCT 5041N01500W 5050N02000W 5030N03000W 4916N04000W 4703N05000W 4610N05300W 4414N06000W 4246N06500W 42N067W DCT KENDA DCT LINND DCT OWENZ DCT CAMRN

 

CHANGELOG:

1/2015 update: removed obsolete BANCS & URTAK

2/2015 update: Gander oceanic points closer to original

4/2015 update: Added 7-digit format coordinates version and refined route closer to original

1/2016 update: 11-digit format and raw/atc versions on fcisuperguy's initiative

3/2016 update: ATC & Raw route & .PLN download on fcisuperguy's initiative

 

EGLL-KIAD

Real Callsign: BAW189

Distance: 3278nm

Subsonic Until: KESUP

Deceleration Point: 4044N06955W

Alternate Airports: KBWI, KJFK

(NOTE: Special descent procedure required for Washington to avoid restricted areas. Instructions available here.)

 

Download Flight Plan Here

 

ATC Route:

N0560F280 CPT L9 MALBY DCT C/KESUP/N0740F280F450 DCT MERLY UL180 C/LESLU/M200F450F600/M200F450F600 DCT 5041N01500W NATSM 4200N06700W 4044N06955W/M200F500 4027N07230W/M130F500 DCT CAMRN/M095F370 DCT KATVE V457 LRP.DELRO3

 

Raw Route:

CPT DCT MALBY DCT KESUP DCT MERLY DCT LESLU DCT 5041N01500W 5050N02000W 5030N03000W 4916N04000W 4703N05000W 4610N05300W 4414N06000W 4246N06500W 42N067W 4044N06955W 4027N07230W DCT CAMRN DCT KATVE DCT LRP DCT DELRO

 

CHANGELOG:

1/2015 update: removed BANCS & URTAK
2/2015 update: Gander oceanic points closer to original
1/2016 update: 11-digit format and raw/atc versions on fcisuperguy's initiative

3/2016 update: ATC & Raw route & .PLN download & Instructions on fcisuperguy's initiative

 

EGLL-KBOS

Real Callsign: BAW9012

Distance: 2943nm

Subsonic Until: KESUP

Deceleration Point: 50nm from 42N067W

Alternate Airports: KJFK, KMHT

 

Download Flight Plan Here

 

ATC Route:

N0560F280 CPT L9 MALBY DCT C/KESUP/N0740F280F450 DCT MERLY UL180 C/LESLU/M200F450F600/M200F450F600 DCT 5041N01500W NATSM 4246N06500W/M100F490 42N067W LFV DCT ARMUN V167 SCUPP

 

Raw Route:

CPT DCT MALBY DCT KESUP DCT MERLY DCT LESLU DCT 5041N01500W 5050N02000W 5030N03000W 4916N04000W 4703N05000W 4610N05300W 4414N06000W 4246N06500W 42N067W DCT LFV DCT OOSHN

CHANGELOG:

1/2016 update: New entry. 11-digit format and raw/atc versions on fcisuperguy's initiative

3/2016 update: ATC & Raw route & .PLN download on fcisuperguy's initiative

 

EGLL-TBPB

Real Callsign: BAW273

Distance: 3678nm

Subsonic Until: KESUP

Deceleration Point: 200nm from 1321N05937W

Alternate Airports: TFFF, TAPA

 

Download Flight Plan Here

 

ATC Route:

N0560F280 CPT L9 MALBY C/KESUP/N0740F280F450 DCT MERLY UL180 C/LESLU/M200F450F600 4859N01443W NATSP 2700N04748W 2438N05000W 1800N05539W/N570F390 DCT 1321N05937W DCT BGI

 

Raw Route:

CPT DCT MALBY DCT KESUP DCT MERLY DCT LESLU DCT 4859N01443W 4649N02000W 4500N02353W 4136N03000W 3422N04000W 2700N04748W 2438N05000W 1800N05539W 1321N05937W DCT BGI

 

CHANGELOG:

3/2016 update: ATC & Raw route & .PLN download on fcisuperguy's initiative

 

EGLL-CYYZ

Real Callsign: BAW99

Distance: 3281nm

Subsonic Until: KESUP

Deceleration Point: 5316N07230W

Alternate Airports: KIAG, CYUL

 

Download Flight Plan Here

 

ATC Route:

N0560F280 CPT L9 MALBY C/KESUP/N0740F280F450 DCT MERLY UL180 C/LESLU/M200F450F600 DCT UNLID DCT MALOT DCT 54N020W 56N030W 57N040W 57N050W PRAWN DCT LOMTA DCT TEALS DCT TRIPE 5055N07504W DCT YXI DCT YYZ

 

Raw Route:

CPT DCT MALBY DCT KESUP DCT MERLY DCT LESLU DCT UNLID DCT MALOT DCT 54N020W 56N030W 57N040W 57N050W DCT PRAWN DCT LOMTA DCT TEALS DCT 5316N07230W 5055N07504W DCT YXI

 

CHANGELOG:

1/2015: verified that PRAWN still exists in AIRAC1501 at N57 12.2 W059 10.8, if not in your navdata just delete it, no change in route. It is the Oceanic/Domestic border of Gander CZQX.

2/2015: Replaced ROUND with HENDY, added UNLID for avoiding Cork coast while in Transonic. Ref. route http://concordefpl.co.uk/toronto.html

3/2016 update: ATC & Raw route & .PLN download on fcisuperguy's initiative

 

EGLL-BIKF

Real Callsign: BAW9034

Distance: 1262nm

Subsonic Until: KESUP

Deceleration Point: 62N020W

Alternate Airports: BIRD, BIAR

 

Download Flight Plan Here

 

ATC Route:

N0560F280 CPT L9 MALBY DCT C/KESUP/N0740F280F450 DCT MERLY UL180 C/LESLU/M200F450F600 5100N01000W 5200N01100W DCT BURAK UN531 KORIB 5600N01400W 6000N01800W 6200N02000W DCT KEF

 

Raw Route:

CPT DCT MALBY DCT KESUP DCT MERLY DCT LESLU DCT 51N010W DCT DOLIP DCT SOVED DCT 60N018W 62N020W

 

CHANGELOG:

1/2016 update: New entry. 11-digit format and raw/atc versions on fcisuperguy's initiative

3/2016 update: ATC & Raw route & .PLN download on fcisuperguy's initiative

 

 

Eastbound Routes

 

KJFK-EGLL

Real Callsign: BAW2/BAW4

Distance: 3172nm

Subsonic Until: n/a

Deceleration point: LULOX
Subsonic by: ELRAG

Alternate Airports: EGKK, EGSS

 

Download Flight Plan Here

 

ATC Route:

N0560F290 JFK3 C/SHIPP/N0740F280F450 DCT C/LINND/M200F450F600 3952N06815W NATSN 4941N01500W DCT LULOX/M095F370 DCT ELRAG DCT NUMPO UP2 BEDEK

 

Raw Route:

SHIPP DCT LINND DCT 3952N06815W 4025N06700W 4307N06000W 4510N05230W 4554N05000W 4810N04000W 4926N03000W 4949N02000W 4941N01500W DCT LULOX DCT ELRAG DCT NUMPO UP2 BEDEK

 

CHANGELOG:

1/2015 update: removed obsolete URTAK and added KENDA to replace airway N15B

2/2015 update: SUPRY last before CZQX Oceanic, replaced 5020N SOMAX with 4920N BEDRA on fcisuperguy advice

4/2015 update: Added 7-digit format coordinates version and refined route closer to original. DOPHN for KZWY/CZQX Domestic FIR borders.

1/2016 update: 11-digit format and raw/atc versions on fcisuperguy's initiative

 

KIAD-EGLL

Real Callsign: BAW190

Distance: 3192nm

Subsonic Until: LYNUS

Deceleration Point: LULOX

Alternate Airports: EGKK, EGSS

 

Download Flight Plan Here

 

ATC Route:

N0560F290 CPTAL9.SWANN DCT ENO C/SIE/M150F290F450 B24 LYNUS/M200F450F600 DCT 40N067W 4307N06000W NATSN 4941N01500W DCT LULOX/M095F370 DCT ELRAG UP2 NIGIT OCK2F

 

Raw Route:

SWANN DCT ENO DCT SIE DCT LYNUS DCT 40N067W 4307N06000W 4510N05230W 4554N05000W 4810N04000W 4926N03000W 4949N02000W 4941N01500W DCT LULOX DCT ELRAG DCT NUMPO DCT BEDEK

 

CHANGELOG:

1/2016 update: 11-digit format and raw/atc versions on fcisuperguy's initiative

 

TBPB-EGLL

Real Callsign: BAW272

Distance: 3688nm

Subsonic Until: n/a

Deceleration Point: TAKAS

Alternate Airports: EGKK, EGSS

 

Download Flight Plan Here

 

ATC Route:

N0570F250 DCT C/1800N05533W/N0740F250F450 2423N05000W C/2700N04731W/M200F450F600 3356N04000W 4100N03000W 4500N02218W 4600N02000W 4740N01500W DCT TAKAS/M100F410 DCT ORTAC UL980 DOMUT OCK4B

 

Raw Route:

1800N05533W 2423N05000W 2700N04731W 3356N04000W 41N030W 4500N02218W 46N020W 4740N01500W DCT TAKAS DCT ORTAC DCT DOMUT

(NOTE: Due to this flight being on the edge of Concorde’s range, you MUST accelerate to VMO (400kts) immediately after departure for increased fuel efficiency. Otherwise, you will NOT be able to complete the flight.)

 

CHANGELOG:

1/2016 update: New entry. 11-digit format and raw/atc versions on fcisuperguy's initiative

3/2016 update: ATC & Raw route & .PLN download on fcisuperguy's initiative
 

CYYZ-EGLL

Real Callsign: BAW98

Distance: 3358nm

Subsonic Until: 5055N07504W

Deceleration Point: LULOX

Alternate Airports: EGKK, EGSS

 

Download Flight Plan Here

 

ATC Route:

N0550F290 TRNTO2 YEE DCT C/5055N07504W/N0740F310F450 C/5317N07230W/M200F450F600 DCT TEALS DCT LOMTA DCT PRAWN 57N050W 57N040W 56N030W 54N020W 52N015W DCT LULOX/M095F370 DCT ELRAG DCT NUMPO UP2 BEDEK

 

Raw Route:

YEE DCT 5055N07504W 5317N07230W DCT TEALS DCT LOMTA DCT PRAWN DCT 57N050W 57N040W 56N030W 54N020W 52N015W DCT LULOX DCT ELRAG DCT NUMPO DCT BEDEK

CHANGELOG:

1/2015: verified that PRAWN still exists in AIRAC1501 at N57 12.2 W059 10.8, if not in your navdata just delete it, no change in route. It is the Oceanic/Domestic border of Gander CZQX.

2/2015: Replaced ROUND with HENDY, added UNLID for avoiding Cork coast. Ref. route http://concordefpl.co.uk/toronto.html

1/2016 update: New entry. 11-digit format and raw/atc versions on fcisuperguy's initiative

3/2016 update: ATC & Raw route & .PLN download on fcisuperguy's initiative

 

KBOS-EGLL

Real Callsign: BAW9011

Distance: 2960nm

Subsonic Until: n/a

Deceleration Point: LULOX

Alternate Airports: EGKK, EGSS

 

Download Flight Plan Here

 

ATC Route:

N0560F280 LOGAN9 SCUPP C/4246N06500W/M200F450F600 NATSN 4941N01500W LULOX/M095F370 DCT ELRAG DCT NUMPO UP2 BEDEK

 

Raw Route:

SCUPP DCT 4246N06500W 4307N06000W 4510N05230W 4554N05000W 4810N04000W 4926N03000W 4949N02000W 4941N01500W DCT LULOX DCT ELRAG DCT NUMPO DCT BEDEK

 

CHANGELOG:

1/2016 update: New entry. 11-digit format and raw/atc versions on fcisuperguy's initiative

3/2016 update: ATC & Raw route & .PLN download on fcisuperguy's initiative

 

BIKF-EGLL

Real Callsign: BAW9035

Distance: 1299nm

Subsonic Until: n/a

Deceleration Point: LULOX

Alternate Airports: EGKK, EGSS

 

Download Flight Plan Here

 

ATC Route:

N0570F310 DCT SUNAK C/63N021W/M200F450F600 61N018W 58N015W DCT SOVED DCT DOLIP DCT 51N011W DCT LULOX/M095F370 DCT ELRAG DCT NUMPO UP2 BEDEK

 

Raw Route:

SUNAK DCT 63N021W 61N018W 58N015W DCT SOVED DCT DOLIP DCT 51N011W DCT LULOX DCT ELRAG DCT NUMPO DCT BEDEK

 

CHANGELOG:

1/2016 update: New entry. 11-digit format and raw/atc versions on fcisuperguy's initiative

3/2016 update: ATC & Raw route & .PLN download on fcisuperguy's initiative

 

Air France Flights

 

LFPG KJFK

EVX KOTEM VEXEN PEMAK RATKA DINIM 5120N 5030N 4940N 4750N PORTI WHALE BOATE KENDA LINND OWENZ CAMRN

Mod. 3,317 nm
Original 3.334 nm

Subsonic until: 30 to KOTEM

Added: 2/2015

 

KJFK LFPG

SHIPP LINND KENDA JOBOC CARAC DOPHN SUPRY 4650N 4840N 4930N 4920N BEDRA TAKAS MOSIS GOBUR JSY INGOR LUKIP

Mod. 3,278 nm
Original 3.316 nm

Subsonic by: GOBUR

Added: 2/2015 Replaced 5020N SOMAX with 4920N BEDRA on fcisuperguy advice

 

LFPG GOOY
LGL UT176 KURIS TERPO ERIGA NOVAN KORUL 43N010W RIPEL ASGAM SAMAR DEREV AMDIB LIMAX YF
2.416 nm
Subsonic until: mid ERIGA-NOVAN

3/2015: 4310N, not an AIRAC fix, changed to 7-digit format



GOOY SBGL
BOMSA UA302 TAROT KODOS UL206 PAMOX UM661 LOBIK ADA
2.753 nm
Subsonic by: LIVOD



SBGL GOOY
ADA UL340 LOBIK UM661 PAMOX UL206 KODOS DCT TAROT UA302 BOMSA
2.753 nm
Subsonic until: LIVOD



GOOY LFPG
YF LIMAX AMDIB DEREV SAMAR ASGAM RIPEL 43N010W KORUL NOVAN UN741 ANG H34 SABLE
2.406 nm
Subsonic by: mid NOVAN-ERIGA

3/2015: 4310N, not an AIRAC fix, changed to 7-digit format

Brilliant adaptation, but the flight plan links are not active anymore. Is there a possibility you can update them?

Link to post
Kyprianos Biris
8 hours ago, EgyptianAviator said:

Brilliant adaptation, but the flight plan links are not active anymore. Is there a possibility you can update them?

@fcisuperguy copy ?!

@EgyptianAviator you can always extract (produce) the flight plan file with one of the many popular tools available by just entering the text Flight Plan.

Irrespective of the above,

I have a minor modification but have not uploaded it in the initial post.

For KJFK-EGLL flight in order to receive YYT DME for some 3.5 minutes worth of last DME update before crossing the pond, I replaced 4510N05230W with SUPRY point (4530N05200W) because I could not get within 120~130nm DME range with the realistic NAVAIDS updates ( Relevant post ). It has minor difference in mileage and this update gives me 3.5 minutes of YYT reception in contrast to none.

I wonder whether real Concorde was receiving YYT DME for update, and for how long, on the EASTBOUND route.

Link to post
EgyptianAviator
7 hours ago, petakas said:

@fcisuperguy copy ?!

@EgyptianAviator you can always extract (produce) the flight plan file with one of the many popular tools available by just entering the text Flight Plan.

Irrespective of the above,

I have a minor modification but have not uploaded it in the initial post.

For KJFK-EGLL flight in order to receive YYT DME for some 3.5 minutes worth of last DME update before crossing the pond, I replaced 4510N05230W with SUPRY point (4530N05200W) because I could not get within 120~130nm DME range with the realistic NAVAIDS updates ( Relevant post ). It has minor difference in mileage and this update gives me 3.5 minutes of YYT reception in contrast to none.

I wonder whether real Concorde was receiving YYT DME for update, and for how long, on the EASTBOUND route.

I was sticking to flying out of VATSIM for so long due to my lack of knowledge of the Concorde Performance System. Thank you for the route mate :D

Link to post

As a new ConcordeX user reading through historical forum posts, I spotted this thread which has lots of references to VatSim but very few to IVAO. I'm a regular ATC on London Control on IVAO (and current EGTT FIR Chief) and would like to think that IVAO controllers are welcoming to Concorde flights; if anyone has any issues with the way Concorde flights out of EGLL are being handled on IVAO then please let me know. I personally see at least 2 or 3 EGLL<-->KJFK Concorde flights each week when I'm controlling London.

If pilots wish to fly online with the original flight-plans (eg. UPGAS rather than KESUP) there's no reason they shouldn't be allowed to; any cosmetic issues on our radar screens are strictly our problem as controllers and we're used to working-around it. The Concorde NAT tracks are included in our ATC software (including the new ATC software currently in beta-testing) so we will know what is intended even if flightplans are filed without all the track coordinates included.

We have previously hosted Concorde-specific events and have a number of more general transatlantic events each year. However if there's groups of Concorde pilots wanting to fly together then it's worth posting in the IVAO GB division forum (or whichever division you wish to fly to/from) to let us know and we can try to arrange for as much ATC as possible to be online as oceanic sectors tend to be only online at certain times.

Link to post
Jonathan Fong
On 10/14/2016 at 7:47 PM, IDBeswick said:

As a new ConcordeX user reading through historical forum posts, I spotted this thread which has lots of references to VatSim but very few to IVAO. I'm a regular ATC on London Control on IVAO (and current EGTT FIR Chief) and would like to think that IVAO controllers are welcoming to Concorde flights; if anyone has any issues with the way Concorde flights out of EGLL are being handled on IVAO then please let me know. I personally see at least 2 or 3 EGLL<-->KJFK Concorde flights each week when I'm controlling London.

If pilots wish to fly online with the original flight-plans (eg. UPGAS rather than KESUP) there's no reason they shouldn't be allowed to; any cosmetic issues on our radar screens are strictly our problem as controllers and we're used to working-around it. The Concorde NAT tracks are included in our ATC software (including the new ATC software currently in beta-testing) so we will know what is intended even if flightplans are filed without all the track coordinates included.

We have previously hosted Concorde-specific events and have a number of more general transatlantic events each year. However if there's groups of Concorde pilots wanting to fly together then it's worth posting in the IVAO GB division forum (or whichever division you wish to fly to/from) to let us know and we can try to arrange for as much ATC as possible to be online as oceanic sectors tend to be only online at certain times.

I've tried flying on IVAO with Concorde before - I haven't encountered any major issues, just perhaps controllers being slightly unfamiliar with Concorde-specific procedures due to the rarity of Concorde flights - and that isn't an IVAO specific issue; I've encountered the same on VATSIM. It's really just a matter of preference - a significant portion of the people who beta-test and develop products like this prefer VATSIM, so it's a bit more widely promoted in the community.

I personally prefer to use updated plans - I just like to fly my flights as if Concorde never went out of service, not as if I'm frozen in 2003. Others have different point of views, which I respect - that's just my way at looking at things.

Link to post
Kyprianos Biris
2 hours ago, fcisuperguy said:

I personally prefer to use updated plans - I just like to fly my flights as if Concorde never went out of service, not as if I'm frozen in 2003. Others have different point of views, which I respect - that's just my way at looking at things.

The first reason why I created this thread was that I thought ATCo's did not see properly the route data with nowadays' AIRACs in their radar scopes. I was proven wrong with feedback by readers here who actually do provide ATC in the subject areas and this is good to know (for those who fly with pre 2003 data).

The second reason for this thread was exactly what @fcisuperguy writes, I did not like to fly frozen in 2003 but as if Concorde was still flying in our days; that's the whole joy of simulation.

I use contemporary flight planning tools to quickly generate my files (flight log print outs, flight plans for weather software, flight plans for pilot client software to seamlessly file the flight plan on line etc. etc.) mainly to have current data and to reduce the pre flight planning stage to a minimum.

I don't believe one of the two on line flying networks is promoted more. People from time to time just mention which network they fly in to, that's all there is to it.

Link to post
Kyprianos Biris

The initial post of this thread has just been updated with 2/2017 changes with the helpful input of @fcisuperguy .

Most changes are related to recent (real) airspace departure/arrivals/border crossing procedures changes like in London, Boston & Shanwick/Reykjavik.

CHANGELOG data can be found as always at bottom of each route.

  • Like 2
Link to post
  • 1 month later...
Keaton Harris

I like the idea, but i cannot download the files for the flight plans, is there something i am doing wrong or have not done to be able to download these? When i click on the links i get the sorry you do not have permission to download that error.

Link to post
Ray Proudfoot
40 minutes ago, keaton0801 said:

I like the idea, but i cannot download the files for the flight plans, is there something i am doing wrong or have not done to be able to download these? When i click on the links i get the sorry you do not have permission to download that error.

My guess is because you aren't using your real name. New forum rules mean some things may be restricted.

Link to post
Kyprianos Biris
9 hours ago, keaton0801 said:

but i cannot download the files

I tested the download and it works. Maybe it has to do with this which I have done for Concorde anyways.

Even if you can't download them just use the RAW ROUTE text, import it in a Flight Plan creation program (  FSBuild, VROUTE, PFPX ) and create your own .PLN files.

These .PLN download files are just the RAW ROUTE generated in to FSX/P3D flight plans format.

Link to post
Keaton Harris
5 hours ago, petakas said:

I tested the download and it works. Maybe it has to do with this which I have done for Concorde anyways.

Even if you can't download them just use the RAW ROUTE text, import it in a Flight Plan creation program (  FSBuild, VROUTE, PFPX ) and create your own .PLN files.

These .PLN download files are just the RAW ROUTE generated in to FSX/P3D flight plans format.

I used the raw route text and was able to create the flight plans in PFPX, thanks.

Link to post
  • 2 months later...
Kyprianos Biris
8 hours ago, Marlon Carter said:

For some reason when I tried to download the pln files I got a message saying I don't have permission to do so..

You can still create them on your own easily.

Quote

 

Even if you can't download them just use the RAW ROUTE text, import it in a Flight Plan creation program (  FSBuild, VROUTE, PFPX ) and create your own .PLN files.

These .PLN download files are just the RAW ROUTE generated in to FSX/P3D flight plans format.

 

Link to post
×
×
  • Create New...