![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]() "Andrew Gideon" wrote in message online.com... In a country called "US" too. What a coincidence. But mine's on Earth, where controllers can err and tires can blow. Apparently your just inexperienced. |
#2
|
|||
|
|||
![]()
Steven P. McNicoll wrote:
"Andrew Gideon" wrote in message online.com... In a country called "US" too. What a coincidence. But mine's on Earth, where controllers can err and tires can blow. Apparently your just inexperienced. You have it backwards. I have experienced controllers issuing a go-around. I've also been the cause of this, I'm sorry to say, when a tire failed on landing. So if you've never experienced a controller issuing a go around, then you are lacking in that experience. Lucky you. - Andrew |
#3
|
|||
|
|||
![]() "Andrew Gideon" wrote in message online.com... You have it backwards. Actually, I'm dead on. I have experienced controllers issuing a go-around. I've also been the cause of this, I'm sorry to say, when a tire failed on landing. So if you've never experienced a controller issuing a go around, then you are lacking in that experience. Lucky you. So a blown tire means the controller didn't provide proper spacing? |
#4
|
|||
|
|||
![]()
Steven P. McNicoll wrote:
Andrew Gideon wrote: I have experienced controllers issuing a go-around. I've also been the cause of this, I'm sorry to say, when a tire failed on landing. So if you've never experienced a controller issuing a go around, then you are lacking in that experience. Lucky you. So a blown tire means the controller didn't provide proper spacing? Steven, I don't think anyone is saying that. Proper spacing on final approach would be sufficient for the second guy to have a suitably clear runway on which to land if the first one has no problems and vacates the runway promptly. However, if something *does* go wrong, the second guy may *not* have a suitably clear runway, and so will have to go around. If he has already been "cleared to land" (US) then the controller has to call a go-around; if he has *not* been "cleared to land" (UK) then the controller needn't say anything, as he'll reach his missed approach point without his landing clearance, and execute a missed approach. |
#5
|
|||
|
|||
![]() "Robert Briggs" wrote in message ... Steven, I don't think anyone is saying that. I think Andrew Gideon is saying that. Proper spacing on final approach would be sufficient for the second guy to have a suitably clear runway on which to land if the first one has no problems and vacates the runway promptly. In the US, the first one does not have to vacate the runway for it to be suitably clear. However, if something *does* go wrong, the second guy may *not* have a suitably clear runway, and so will have to go around. I think most of us understand that. If he has already been "cleared to land" (US) then the controller has to call a go-around; if he has *not* been "cleared to land" (UK) then the controller needn't say anything, as he'll reach his missed approach point without his landing clearance, and execute a missed approach. The UK rules appear very inefficient. |
#6
|
|||
|
|||
![]()
Steven P. McNicoll wrote:
"Robert Briggs" wrote in message ... Steven, I don't think anyone is saying that. I think Andrew Gideon is saying that. What I wrote was: Where I live, controllers attempt to do so. They don't always succeed. Sometimes they err, sometimes tires fail, ... It would take creative reading to take that to mean, as you asked: a blown tire means the controller didn't provide proper spacing? I assume that you're doing this deliberately, creating noise to cover your statement: In the US, controllers would sequence the arriving aircraft so that a go around would not be necessary. which ignores that it is occasionally necessary for controllers to wave off aircraft in the US. I might have assumed this "creative reading" to be an error on your part, but you then accused me of being "inexperienced" merely because I had experienced controllers issuing go-around instructions. That's too silly, given that inexperience would be a *lack* of experience. - Andrew |
#7
|
|||
|
|||
![]()
Robert Briggs wrote:
If he has already been "cleared to land" (US) then the controller has to call a go-around; if he has *not* been "cleared to land" (UK) then the controller needn't say anything, as he'll reach his missed approach point without his landing clearance, and execute a missed approach. Right. This is my point. Since someone stated: In the US, controllers would sequence the arriving aircraft so that a go around would not be necessary. I thought it useful to point out that, in this US, this is usually but not always the case. What I wrote: Where I live, controllers attempt to do so. They don't always succeed. Sometimes they err, sometimes tires fail, ... is pretty clear. Why Steven concludes that a blown tire implies a failure to provide proper spacing is odd, but really doesn't have anything to do with the discussion here. - Andrew |
#8
|
|||
|
|||
![]() Robert Briggs wrote: Proper spacing on final approach would be sufficient for the second guy to have a suitably clear runway on which to land if the first one has no problems and vacates the runway promptly. Remeber here in the States most aircraft don't have to be off the runway for the next one to land, just a certain distance down the runway. However, if something *does* go wrong, the second guy may *not* have a suitably clear runway, and so will have to go around. Some airplanes only. If he has already been "cleared to land" (US) then the controller has to call a go-around; if he has *not* been "cleared to land" (UK) then the controller needn't say anything, as he'll reach his missed approach point without his landing clearance, and execute a missed approach. That's it? He'll just go around with nothing further said? That would never happen here. The pilot would be constantly chipping at the tower controller wondering about his landing clearance. In your scenario there are many more miles separation than the minimum if there is that kind of time to be doing all this talking. |
#9
|
|||
|
|||
![]()
Newps wrote:
Robert Briggs wrote: Proper spacing on final approach would be sufficient for the second guy to have a suitably clear runway on which to land if the first one has no problems and vacates the runway promptly. Remeber here in the States most aircraft don't have to be off the runway for the next one to land, just a certain distance down the runway. That is why I wrote "suitably clear", rather than "empty". However, if something *does* go wrong, the second guy may *not* have a suitably clear runway, and so will have to go around. If he has already been "cleared to land" (US) then the controller has to call a go-around; if he has *not* been "cleared to land" (UK) then the controller needn't say anything, as he'll reach his missed approach point without his landing clearance, and execute a missed approach. That's it? He'll just go around with nothing further said? It is quite likely that the controller *would* call the go-around, but the lack of a landing clearance would (or jolly well should) keep the second guy airborne. That would never happen here. The pilot would be constantly chipping at the tower controller wondering about his landing clearance. I don't think the pilot would often be "wondering about his landing clearance". At a field with normally light(ish) traffic where you happened to be unusually close to the guy in front the controller would tell you to expect a late landing clearance. Somewhere like LHR "late" landing clearances are the default. In your scenario there are many more miles separation than the minimum if there is that kind of time to be doing all this talking. What do you mean by "all this talking"? You can sort out things like the weather in plenty of time. I wouldn't call issuing the landing clearance itself "doing all this talking" - certainly not in comparison with a system which requires time for the controller to call a go-around. |
#10
|
|||
|
|||
![]() Robert Briggs wrote: If he has already been "cleared to land" (US) then the controller has to call a go-around; if he has *not* been "cleared to land" (UK) then the controller needn't say anything, as he'll reach his missed approach point without his landing clearance, and execute a missed approach. That's it? He'll just go around with nothing further said? It is quite likely that the controller *would* call the go-around, but the lack of a landing clearance would (or jolly well should) keep the second guy airborne. But in reality it doesn't. The sharp crews will verify their landing clearance but as an experiment I have allowed lots of pilots to land without a clearance. So your theory that witholding a landing clearance is safer is simply not true. That would never happen here. The pilot would be constantly chipping at the tower controller wondering about his landing clearance. I don't think the pilot would often be "wondering about his landing clearance". Alas, they do. At a field with normally light(ish) traffic where you happened to be unusually close to the guy in front the controller would tell you to expect a late landing clearance. There's no reason for that and causes the controller to talk more than he has to. "Follow the Cessna ahead, cleared to land." Assuming it works out as expected with the required amount of separation no further talking is required. If it doesn't then you tell the aircraft to go around. It's foolish to be issuing landing clearances with the aircraft on very short final. He's got more important things to worry about. I wouldn't call issuing the landing clearance itself "doing all this talking" - certainly not in comparison with a system which requires time for the controller to call a go-around. In my system I have a lot more time to talk because I am not giving other airplanes farther out a stupid instruction like "continue inbound." |
|
Thread Tools | |
Display Modes | |
|
|