MJKERR

I have the following in my terminal file, summer 2019 schedule Terminal_4A: AFL,AFR,AMC,AZA,KLM,LZB,TAR,TUA,UZB Terminal_4B: AHY,AMX,ASL,BBC,CES,CSN,DAH,ELY,ETD,GFA,HVN,KAC,KAL,KQA,KZR,MAS,MAU,OMA,QTR,RAM,RBA,ROT,SVA Terminal_Cargo1: BCS,QAC Terminal_Cargo2: ABW,CPC,ESC,KCA,QAC,SQC Terminal_VIP: QAF

It looks like you have performed a test on 09R arrivals, not 09L arrivals Some aircraft on their way from 09L avoid taxiway L, N3, S2 Instead they use taxiway A, N1, S1 This keeps N2E vacant for aborted takeoffs

X

X

X

Both taxiways exist Ideally S1 - N1 is required for 09L arrivals As above Tower 2011 only has S1 - N1 Tower 3D only has S1 - N2E

Runway 09L / 09R operations - It is very rare to get 09L departures,as there are only two holding points There are handover points, COBRA, DINGO, RABIT, SNAPA, but due to the limitations this is only used if there is an issue with 09R As a result it can restrict operations at Terminals 5A and 5B, hence why it is avoided From memory this was only used once in 2019 I would need to test this, but it looks to be correct to me

As Tower 3D EGLL was released in December 2020 I was waiting a couple of months before obtaining it myself I have been reading others issues with this, and initially was disappointed when compared to OMDB OMDB is not perfect, I only have two problems with it (exit runway and gate blocking errors) I have very good real world experience of operations at EGLL I thoroughly enjoyed Tower 2011, and heavily modified it However, it was left behind by older aircraft So it is time to move on to Tower 3D EGLL My initial tests were actually very positive So far I have only used Runway 27L/27R operations Runway 27L departures / 27R arrivals - I also ran into the problem with only one aircraft at the hold points nearest to taxiway A However, after some trial and error I managed to resolve this, and at one point had eight aircraft at the hold point I then compared to a photo from Summer 2019, and it looks almost correct Aircraft waiting at A10E, can impact following arrivals sent to A11 Aircraft asked to exit to taxiway A10W ignore this request and exit at A10E Runway 27L arrivals / 27R departures - I have only tested this once I had severe problems with the hold points A1 - A3 I will therefore need to come back to this Taxiway S1 to N1 / N2E - Initially I thought there was a misalignment across runway 27L, between S1 and N1 This is the route in Tower 2011 It was quite difficult to find a video, but the route between S1 and N2E is actually correct The route N1 to S1 is often used by aircraft heading to Terminal 4, as this allows two or more aircraft to queue ADIRS (Runway 27R arrivals) - I am finding the landing aircraft are initially very difficult to click on As soon as they appear I move the mouse pointer over them, then the aircraft moves considerably to the left In some cases I have to pause the program in order to select the aircraft Voice direction - I used this technique in OMDB Say the callsign and the view focuses on the selected aicraft However, in EGLL it seems to struggle with the Speedbird callsign The callsign appears to be accepted, but about half the time nothing happens A good example is BA64, speedbird six four When I saw this it initially appears at BAW640, but when I release the key it corrects to BAW64, but the view does not update I am in the process of modifying my Summer 2019 timetable from Tower 2011 into Tower 3D This presents an issue as there are some arrivals (04:00 to 06:00) before the first departure (06:00) In the Real Traffic schedule these flights start appearing, but in real life most of these would already have landed There is a simple solution, by removing all the arrivals before 05:30, to allow for some being late...

X

X

X

X

X

X

X

X

X

X

X

X

X

X

https://www.atcsuite.com/egll-for-tower-3d Heathrow Dulles International Airport (EGLL) for Tower!3D I assumed this was Dulles....?

X

Looks fine, with the A350 being visually longer A340-300 at 63.6m A350-900 at 66.8m