MJKERR

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

That is what I have always been using It caught me out on the final test of EGLL I had to stop as aircraft would not pushback and then started getting Go Around on arrivals

Yes, the wind has been in this easterly direction every time This is the whole point of operations in runway 09L / 09R, when the wind is westerly I will check the wind on commencement, and see if it is correct If not, then close and restart

Final test for operations, Runway 09L / 09R Agreed, the holding points for departures from runway 09R are required The details do not appear in the flight strip, so had to continually click in the aircraft to make sure they were routed correctly Y1 -> N11 N10 S11 Similar to the holding points for runway 27L adjacent from taxiway A Aircraft holding at N8 and N7 block passing aircraft on taxiway A As you can see, it looks quite messy at N8 and N7, as these aircraft cannot pass

Successful test with holding points A1 to A4 This is what it should look like Example, runway out of use for inspection, all aircraft to hold It would be very rare to have that many aircraft holding The only issue I had was trying to get an aircraft to queue behind BAW832 on A3, this route seems quite restrictive as it needs to use B, M2, A, but it was always rejected It may be used by an aircraft from a stand nearer to runway 27L, and thus arriving past AB6 (link 28)

For info, as an update on point 4 HIGH IMPACT - Hold points for 27R I have been carrying out some tests on the A1- A3 taxiways for feed into the start of 27R in the last couple of days, with some input from another couple of well known forum contributors, and will not proposing any changes to this as it works pretty well with respect to the known game issues on aircraft proximity warnings, aircraft sizes etc. You can "stack" aircraft here fairly accurately with careful planning and controlling. The hold points are roughly where they should be and the only real issue was that I think that the A3 Hold Point should actually go back slightly I have now completed a few tests on Runway 27R departures Once I was aware of the restrictions it seems to work as expected The issue you found with the A3 holding point is due to a controller experience issue It is highly unlikely a B747 would be sent to A3 via taxiway A, the preferred route is taxiway B This then keeps A4 free for aircraft arriving along taxiway A Equally, it would be rare to have more than three aircraft holding at each of A1, A2, and A3, as this would back up beyond TITAN and SATUN

I have had this happen twice now Terminal 3, Stand 357 Aircraft routed to Runway 27L The pushback is excessive and the aircraft ends up off the taxiway, between taxiways A and B

X

X

X

I started on the conversion of my Tower 2011 schedule yesterday There are quite a few changes that have to be made The main issue is the update to aircraft My timetable is based on Summer 2019 In Tower 2011 this then meant rolling back any recent aircraft For example the Virgin B787, rolled back to either A346 or B744 The next issue is verifying all the airlines As there were some gaps I tried to use all the Real Colours that were available for Tower 2011 Some of these airlines have ceased operations, such as Kingfisher and German Wings I had also avoided using remote stands in Tower 2011, for Terminals 3, 4 and 5C As Tower 3D uses all the stands this actually eliminates stand blocking and dropped aircraft / flights I am about two thirds of the way through this conversion Sadly there are some compromises, as there are no specific A380 stands separated in Tower 3D When using the default Real Traffic schedule I noticed some really strange views!