![]() |
Originally Posted by maddogmax
(Post 2212787)
You just made my case. If they want help, they will ask for it. Nine times out of ten, if it takes 3 calls to get a reply from an aircraft it's because the pilots were talking to each other about how to bid, contract negotiations, etc., not by being blocked. Saying "blocked" could actually block the controllers second or third attempt to contact the aircraft.
|
Commuting to work and the guy ahead of me puts his guitar case on the belt. We go through and TSA pulls his case aside. They go open it up and hold up a full size saber in a scabbard. Not sure if he made his flight.
|
Originally Posted by qball
(Post 2217613)
Commuting to work and the guy ahead of me puts his guitar case on the belt. We go through and TSA pulls his case aside. They go open it up and hold up a full size saber in a scabbard. Not sure if he made his flight.
|
Originally Posted by thevagabond
(Post 2217739)
The TSA gets a lot of grief. Especially from us. But here's a perfect example that in fact they do improve the safety of our flights. What a numbnut!
|
Originally Posted by maddogmax
(Post 2212787)
Saying "blocked" could actually block the controllers second or third attempt to contact the aircraft.
|
New nominee: The DL guy the other night landing on 28L at SFO who was advised by Tower while on final approach to "keep it rolling through the intersection, I've got two departures on the 1s."
(For those who are unfamiliar, 1L/R intersect with 28L/R at SFO. The 1s are typically used for departures while crossing traffic lands on the 28s. Anyone who's been to SFO before will realize that common courtesy dictates you let the airplane roll through the runway intersection, even if your gate might be in Terminals 1 or 2, necessitating a bit of a back-taxi on A or B in order to get to your gate. If you slowly roll through the intersection, you block departing traffic on both 1L and 1R, and usually both runways are in heavy use by departures.) Anyhow, said DL pilot ground to a halt right in the middle of the 1L/ 28L intersection. He obviously wanted the shortest route to his gate, and the heck with anyone else. The exchange went like this: Tower: "DL ___, I said keep it moving! You're blocking two departures!" DL: "Well, we're going to the 50 gates right here." (He didn't want to add another couple hundred feet to his taxi.) Tower: "I realize that sir but I told you to keep it rolling!" DL: (Still immobile on the runway): "OK, stand by...what taxiway did you want us to exit on?" Tower: "I don't care sir, just get off the runway and contact Ground on point eight...ahh, it's too late now. Skywest ___ and Virgin ___, sorry, gonna have to get you out after the next pair of arrivals. DL____, next time you land here, keep it rolling like I told you." DL: "Ahhh... roger that." Finally he found the thrust levers and exited the intersection. We sat there on 1L watching this in disbelief. I've never seen a 121 crew just stop smack in the middle of an active runway intersection like that. But I bet they had spiffy hats. |
Originally Posted by Turbosina
(Post 2218178)
New nominee: The DL guy the other night landing on 28L at SFO who was advised by Tower while on final approach to "keep it rolling through the intersection, I've got two departures on the 1s."
(For those who are unfamiliar, 1L/R intersect with 28L/R at SFO. The 1s are typically used for departures while crossing traffic lands on the 28s. Anyone who's been to SFO before will realize that common courtesy dictates you let the airplane roll through the runway intersection, even if your gate might be in Terminals 1 or 2, necessitating a bit of a back-taxi on A or B in order to get to your gate. If you slowly roll through the intersection, you block departing traffic on both 1L and 1R, and usually both runways are in heavy use by departures.) Anyhow, said DL pilot ground to a halt right in the middle of the 1L/ 28L intersection. He obviously wanted the shortest route to his gate, and the heck with anyone else. The exchange went like this: Tower: "DL ___, I said keep it moving! You're blocking two departures!" DL: "Well, we're going to the 50 gates right here." (He didn't want to add another couple hundred feet to his taxi.) Tower: "I realize that sir but I told you to keep it rolling!" DL: (Still immobile on the runway): "OK, stand by...what taxiway did you want us to exit on?" Tower: "I don't care sir, just get off the runway and contact Ground on point eight...ahh, it's too late now. Skywest ___ and Virgin ___, sorry, gonna have to get you out after the next pair of arrivals. DL____, next time you land here, keep it rolling like I told you." DL: "Ahhh... roger that." Finally he found the thrust levers and exited the intersection. We sat there on 1L watching this in disbelief. I've never seen a 121 crew just stop smack in the middle of an active runway intersection like that. But I bet they had spiffy hats. |
Originally Posted by maddogmax
(Post 2212584)
Ask any controller and they will tell you they hate it when the hear "blocked" If they don't get a response from the aircraft they are trying to contact, they will try again in a few seconds. They don't need help from any one else.
I've never heard other controllers rant about "blocked" either, although I've only worked in Center where about 95% of the pilots we talk to are professionals who can tell when it's the controller being blocked and not two aircraft blocking each other (when "blocked" wouldn't be appropriate). Maybe it's different in the approach and tower environment though. |
Originally Posted by ATCBob
(Post 2218419)
When it's busy, as a controller I always want to know when I was blocked so I can immediately re-transmit instead of wasting time waiting for a readback that will never come. When it's busy we need the regular rhythm of instruction/readback/instruction/readback to keep things moving. When we give "instruction" and get a readback of "blocked" we go back to "instruction" and the flow keeps going. If we give "instruction" and hear silence, now the rhythm is messed up and we have to decide to go against the flow with another instruction (when we're expecting a readback), that is likely to get blocked again if the pilot was just delayed in their response.
I've never heard other controllers rant about "blocked" either, although I've only worked in Center where about 95% of the pilots we talk to are professionals who can tell when it's the controller being blocked and not two aircraft blocking each other (when "blocked" wouldn't be appropriate). Maybe it's different in the approach and tower environment though. Thanks for the feedback. I figured you'd like to know when you were blocked, I can also understand that saying "blocked" ties up a busy frequency even more. I think the real frustration with the OP was, the obnoxious child stretching out the transmission...."blllooooooocccccckkkkkeeeddd". That would be annoying during a red eye. When a freq was saturated, it would be brutal. |
Originally Posted by Turbosina
(Post 2218178)
New nominee: The DL guy the other night landing on 28L at SFO who was advised by Tower while on final approach to "keep it rolling through the intersection, I've got two departures on the 1s."
(For those who are unfamiliar, 1L/R intersect with 28L/R at SFO. The 1s are typically used for departures while crossing traffic lands on the 28s. Anyone who's been to SFO before will realize that common courtesy dictates you let the airplane roll through the runway intersection, even if your gate might be in Terminals 1 or 2, necessitating a bit of a back-taxi on A or B in order to get to your gate. If you slowly roll through the intersection, you block departing traffic on both 1L and 1R, and usually both runways are in heavy use by departures. |
| All times are GMT -8. The time now is 04:59 AM. |
Website Copyright © 2026 MH Sub I, LLC dba Internet Brands