Go Back  PPRuNe Forums > Ground & Other Ops Forums > ATC Issues
Reload this Page >

Destination Aiport not allowing T/O's to their Airport because of WX

Wikiposts
Search
ATC Issues A place where pilots may enter the 'lions den' that is Air Traffic Control in complete safety and find out the answers to all those obscure topics which you always wanted to know the answer to but were afraid to ask.

Destination Aiport not allowing T/O's to their Airport because of WX

Thread Tools
 
Search this Thread
 
Old 4th Nov 2008, 11:01
  #1 (permalink)  
Thread Starter
 
Join Date: Jan 1999
Location: Does not matter
Posts: 56
Likes: 0
Received 0 Likes on 0 Posts
Destination Aiport not allowing T/O's to their Airport because of WX

Can/does ATC in your part of the world denay commercial operators to take off from their departure Airport because - their - Airport which happens to be your destination is below landing WX minimums?

Alternate airport is Cavok so no problem if the WX at Dest. does not change and you have to divert

The point is not because of traffic congestion in their airspace but because actual and forcasted WX shows to be below minimums for arrival at destination.

Q. is also not if it makes any sense or not to T/O with that WX at destination.
manuel ortiz is offline  
Old 4th Nov 2008, 16:13
  #2 (permalink)  
 
Join Date: Aug 2007
Location: South East
Posts: 40
Likes: 0
Received 0 Likes on 0 Posts
UK MATS part 1 Section 1, Chapter 4, Page 5

A controller has no authority to withhold take-off clearence because the intended destination is closed.


I assume it would be the same for weather below minima.
JonG is offline  
Old 4th Nov 2008, 17:10
  #3 (permalink)  
 
Join Date: Feb 2006
Location: I Wish I Knew
Posts: 71
Likes: 0
Received 0 Likes on 0 Posts
OK good point. Maybe I misunderstood the original question. I was not talking about a controller specifically witholding clearance, more in terms of Flow Management issuing flight suspension messages due to weather below minima.
Mad As A Mad Thing is offline  
Old 4th Nov 2008, 17:51
  #4 (permalink)  
 
Join Date: Nov 2000
Location: Greystation
Posts: 1,086
Likes: 0
Received 0 Likes on 0 Posts
I think it has been known for Flow Control to impose a "zero flow rate" occasionally to certain routes for a/c inbound to certain large UK airfields simply to protect the controllers. If you are sat on the ground waiting to get airborne you wouldn't know about any congestion at your destination and this would not be specified in the flow restriction, but I would imagine (or have actually seen) at say Heathrow, the stacks would fill very quickly with anything already airborne from departure points further away. Simple solution, stop anything else getting airborne temporarily until the situation can be controlled safely. Imagine 42 aircraft entering the stacks every hour, the RTF is quite loaded. Then they all ask to divert.............

5mb
5milesbaby is offline  
Old 4th Nov 2008, 18:46
  #5 (permalink)  

 
Join Date: May 2006
Location: UK
Posts: 796
Likes: 0
Received 0 Likes on 0 Posts
It used to be, maybe still is, the case that LHR could apply an RVR barrier in low vis ops i.e. only traffic able to land below a certain IRVR would be accepted.

Not seen that done for a while though.

It was probably done when there were more a/c about that couldn't land in IRVRs below around 600m. Didn't want the stacks filling with traffic that couldn't make an approach.

Now that the bulk of traffic can land in very low IRVRs the low vis flow control takes care of the airborne holding situation (most of the time anyway).
Roffa is offline  
Old 4th Nov 2008, 19:36
  #6 (permalink)  
Thread Starter
 
Join Date: Jan 1999
Location: Does not matter
Posts: 56
Likes: 0
Received 0 Likes on 0 Posts
Tks for the good feedback and to clarify my original Q!!

It is actually the destination airport (180 nm away) telling the departure airport ATC to not give the IFR clearence to that aircraft because they (Destination) are below minimums for their VOR App.

So, can the destination aiport at your part of the world do that and is there any written guidance on that.
Would be particulary interested in an ICAO Ref. but any further feedback will be very much appreciated.

Pilot/Operator point of view might be to depart and if WX remains below minimums before the FAF divert to the alternate but the departure airport follows the destination ATC instructions and will not issue an IFR clearence to that destination.
manuel ortiz is offline  
Old 4th Nov 2008, 20:22
  #7 (permalink)  
 
Join Date: Apr 2001
Location: Near Stalyvegas
Age: 78
Posts: 2,022
Likes: 0
Received 0 Likes on 0 Posts
When I worked in Manch Tower, we would sometimes get flow messages stating that a/c which could not meet a set RVR minimum, were not being given a slot. As has been said, it's not necessarlily the destination a/f, but en-route holds, that stack up as well.
chiglet is offline  
Old 4th Nov 2008, 21:15
  #8 (permalink)  
Thread Starter
 
Join Date: Jan 1999
Location: Does not matter
Posts: 56
Likes: 0
Received 0 Likes on 0 Posts
Traffic congestion was not an issue, enroute or at destination.
manuel ortiz is offline  
Old 5th Nov 2008, 07:25
  #9 (permalink)  
 
Join Date: Jun 2001
Posts: 69
Likes: 0
Received 0 Likes on 0 Posts
Why didn't you refile to your alternate airport, which was cavok, and have your original airport as the alternate? Then when airbourne if your original airport became within limits you could divert into them and everybody happy.
Captain Windsock is offline  
Old 5th Nov 2008, 10:43
  #10 (permalink)  
 
Join Date: Aug 2004
Location: In the world
Posts: 205
Likes: 0
Received 0 Likes on 0 Posts
It is actually the destination airport (180 nm away) telling the departure airport ATC to not give the IFR clearence to that aircraft because they (Destination) are below minimums for their VOR App.
This sounds very much like a situation we had the other day at the airfield where I work (where are you referring to manuel?)

In our case, the zero rate flow restrictions inbound were not implemented by us (at the airfield) but by the flow manager on behalf of the local radar unit who physically cannot handle a stream of inbounds (not just for our airfield but another one they deal with up the road) when the weather for one or the other deteriorates and or is below minimums and it is highly likely that the aircraft will be asking to divert. This particular radar unit has a tough time of it already with only 3 levels to handle traffic. 2 of these levels being inside controlled airspace and 1 out!

Like I said, in our case the zero rate was not implemented by us but having seen the ATFM messages myself in the past they do look like we had issued them. Regardless of who issued the zero rate flow, or what the messages said, due to the local set-up, when the weather is below the absolute minima (and aircraft shouldn't be making approaches anyway), zero rate is the only the option available.
Dizzee Rascal is offline  
Old 5th Nov 2008, 15:41
  #11 (permalink)  
Thread Starter
 
Join Date: Jan 1999
Location: Does not matter
Posts: 56
Likes: 0
Received 0 Likes on 0 Posts
DR
It happened between two small Countries in the Americas.

The mentioned option to depart putting the alternate as destination and departure as alternate was one of the solutions considered but it also had some PAX impact. At the end we got a release to go, WX did not change and we just headed to the alternate.

This all prompted my Q. to know if in other parts of the world the two airports involved had the right to do the same.

By the way, not that I am really complaining!

Of course I have started to contact the two ATC's involved just to know their point of view.

How do you all interpret JonG's first feed back post to all this topic?

Great to be in contact with you ATC guys!! Believe its my first post here... Very seldom fly to Europe, you all do a grat job!!
manuel ortiz is offline  

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.