about the separation between departing aircraft and the following landing aircraft
in chapter 8 of ICAO doc 4444 -ATS surveillance services, the separation between the departing aircraft and following arrival aircraft is not specified, so, when can the controller in tower can instruct an aircraft to take off based on the position of arrival aircraft on final ? and what's the logic behind it?
and in this article: "Two minutes are required between take-offs when the preceding aircraft is 74 km/h (40 kt) or more faster than the following aircraft and both aircraft will follow the same track" what kind of speed does it mean ? cruising speed or the actual speed in the phase of departure? thanks! |
Originally Posted by mxwbuaa
(Post 10830448)
in chapter 8 of ICAO doc 4444 -ATS surveillance services, the separation between the departing aircraft and following arrival aircraft is not specified, so, when can the controller in tower can instruct an aircraft to take off based on the position of arrival aircraft on final ? and what's the logic behind it?
and in this article: "Two minutes are required between take-offs when the preceding aircraft is 74 km/h (40 kt) or more faster than the following aircraft and both aircraft will follow the same track" what kind of speed does it mean ? cruising speed or the actual speed in the phase of departure? thanks! What most approach controllers do, is either by standard agreement between TWR and APP, or individually, release aircraft with reference to arriving aircraft. Then the TWR controller can apply "reduced separation in vicinity of an airport", hence see both aircraft and determine there is no risk of collision, and thereby get well below normal surveillance separation. On days with bad weather, where the "vicinity separation" also known as TWR-separation, cannot be used, there are a few "procedural separations", like the departure has to depart before the arrival reaches 5 NM final etc. Most TWR controllers will gladly accept releases with reference to arriving aircraft, and apply whatever separation is available depending on weather. 40 kts? It says 40 kts.... so the speed difference has to be 40 kts... if you take the TAS from their flightplan, I'd say you need to have a chat with your OJTI again.... But that could vary from place to place... but the way I was taught was we consider actual speed of the aircraft. (I've seen TAS from the flightplan used during basic training, just for the students to get a feel for it, and not "overburden" them) |
Aircraft are deemed to be separated if the distance between them is constant or increasing thus as a departure is accelerating and an arrival is decelerating, it's up to the tower controller to decide the departure separation.
|
Aircraft are deemed to be separated if the distance between them is constant or increasing thus as a departure is accelerating and an arrival is decelerating, it's up to the tower controller to decide the departure separation. 2 s |
In an ICAO environment the departing aircraft needs to have crossed the upwind end of the runway prior to the arriving aircraft crossing the landing threshold. This assumes no reduced runway separation (RRSM) is being used. How the tower controller achieves it is usually based on experience, but will be dependent on weather conditions also i.e. VMC/IMC.
|
Originally Posted by Red Dragon
(Post 10831287)
In an ICAO environment the departing aircraft needs to have crossed the upwind end of the runway prior to the arriving aircraft crossing the landing threshold. This assumes no reduced runway separation (RRSM) is being used. How the tower controller achieves it is usually based on experience, but will be dependent on weather conditions also i.e. VMC/IMC.
|
Originally Posted by terrain safe
(Post 10831333)
Or on a nice sunny day: Wheels up before Wheels down! :O
|
Originally Posted by Red Dragon
(Post 10831595)
In the UK yes, but ICAO runway separation requires the departing to have crossed the upwind end of the runway - irrespective of the weather conditions. Quite restrictive when you've got a 4500m runway!
|
Originally Posted by Gonzo
(Post 10831726)
....as does the forthcoming EASA Part.ATS...
(Other than that, we fall under the "safe, orderly and expeditious flow" and "prevent collision". But that "runway separation" is ofcourse not something approach can use as a separation (where I've worked at least), they only have the option of having tower help with the "reducing separation in vicinity of airport" for them.) |
Originally Posted by jmmoric
(Post 10830469)
The standard surveillance separation is 5 nm, or any other depending on the minimum separation the unit has. And that is the surveillance separation between arrivals and departures as well.
What most approach controllers do, is either by standard agreement between TWR and APP, or individually, release aircraft with reference to arriving aircraft. Then the TWR controller can apply "reduced separation in vicinity of an airport", hence see both aircraft and determine there is no risk of collision, and thereby get well below normal surveillance separation. On days with bad weather, where the "vicinity separation" also known as TWR-separation, cannot be used, there are a few "procedural separations", like the departure has to depart before the arrival reaches 5 NM final etc. Most TWR controllers will gladly accept releases with reference to arriving aircraft, and apply whatever separation is available depending on weather. 40 kts? It says 40 kts.... so the speed difference has to be 40 kts... if you take the TAS from their flightplan, I'd say you need to have a chat with your OJTI again.... But that could vary from place to place... but the way I was taught was we consider actual speed of the aircraft. (I've seen TAS from the flightplan used during basic training, just for the students to get a feel for it, and not "overburden" them) but in non-radar environment or just procedural control environment , how can you know in real time the actual speed of a departing aircraft the speed of which is increasing ? |
Originally Posted by Gonzo
(Post 10831726)
....as does the forthcoming EASA Part.ATS...
|
Originally Posted by LookingForAJob
(Post 10832137)
Ask the pilot.
I was just about to say the same... |
Originally Posted by LookingForAJob
(Post 10832137)
Ask the pilot.
|
Originally Posted by usedtobeATC
(Post 10832621)
I gave clearance for take off when arriving traffic was not less then 2.5 miles before RW (VMC). I did it for 42 years as a Tower controller.
|
NATS controllers at Gatwick did it at a shorter range than that; I was on the flight deck of a '737 and from 4 mile final, 3 aircraft were cleared for departure before we got landing clearance. 2 s |
Originally Posted by 2 sheds
(Post 10833221)
All of which illustrates that Gatwick is (or was, prior to current traffic reduction) an incident waiting to happen, but does not address the OP's query.
2 s others might describe Gatwick as the worldwide standard bearer for efficient single runway operations. |
4 miles final and 3 departures? That’s 3 departures in less than 2 minutes.... if your 737 is doing 120 on final, and the departures use 40 seconds to get airborne... it’s barely doable.
I’d personally believe in 2 departures.... unless something small you can get out of the way fast. |
|
All times are GMT. The time now is 15:39. |
Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.