PPRuNe Forums - View Single Post - You want us to descend now?
View Single Post
Old 6th August 2002 | 14:36
  #29 (permalink)  
AF1
 
Joined: Sep 2000
Posts: 63
Likes: 0
From: Aotearoa
Some replies ...

Thank you all for your very valuable input into the thread; some very interesting replies.

Standard Noise - somewhat off topic, but I think its an interesting situation you describe; your comments really do smack of a 'them and us' situation. When I started out I thought along the same lines. Pilots should do everything we tell them, should always listen out on frequency, and respond immediately to any instruction.

Simple fact is, it doesn't work like that. Whats funny, is that both of us (ATCOs and pilots) often have the same impression of the other side - that is to say, that when not talking on the RT, no-one is doing anything else !

ACTOs should remember that pilots often have a high workload, especially in the descent & approach phase of the flight. Whether its the approach briefing, calling ops, getting the ATIS etc. there is often only one pair of ears on the RT and a call or two may be missed. Its human nature, and it doesn't do either side any favours to berate them for missing a call. However, I would say in your case that the pilot's response was OTT as well.

Pilots should perhaps also consider that just because we ain't on the radio, don't mean we're not working either! There is often a lot of work in co-ordination, 'scanning and planning', etc. And there's the gossip to catch up on at shift-change

Max Angle is correct. We are here to provide a service. We are not deities that sit back and decide the fate of a flights progress at our whim. We work within our guidelines, to the best of our abilities, and provide the best service that we can. Well, most of us do, anyhow. The tone of your comment could be a little more gentle though!

FWA NATCA - that's one way of sorting it all right! I have only ever had a situation once where I would have liked to do this, but didn't, and it was the reverse - an aircraft, who had been given a descent clearance, subsequently refused to stop descending until the third time of asking, basing his logic on the fact that descent had previously been given!

Problem with the situation I referred to initially though, is that Im not talking about the situation where I need the aircraft to descend right NOW, as in 20 miles to a cross I've seen late or something. Its a normal, planned, control instruction. I have crossing traffic in say, 4-5 minutes, so I take positive action and sort it now with a normal, "unhurried" descent. So throwing the book at him for not descending immediately is not fair.

The issue, at the end of it all, is that the control instruction "descend", which is very simple, is now, apparently, ambiguous. It shouldn't be.

I should not need to say "Descend NOW", because then what do I say when I really want him to go down NOW ?

There is a kind of 'ranking' for urgency, in the phraseology that I use ...

1. Descend when ready
2. Descend
3. Descend now
4. Descend now, expedite through FLxxx
5. Descend immediately FLxxx, due traffic (avoiding action)

Hope that makes our perspective a bit clearer.

NW1 - very valid points. As an aside, if you "request descent in 12 miles", guaranteed some smart ar$e controller will come back and say "Roger, do that" - ie. call me when you want descent, not before. I promise you!

Personally I'd be happy with that advance warning, but would still prefer a request at the TOD only. Keeps it simpler.

Is it not possible that you just say nothing until say 3 miles to TOD, then request it. If RT is busy, or you get a "stand by" ie. - let me check my scope cause I wasn't planning ahead your descent, then what's the worst case scenario? You're chasing the profile for a few thousand feet - so what? And how often will this happen? Very rarely ... and its much safer

Finally,
NorthernSky - a most interesting perspective on how ATC should operate.

On the descend when ready bit ...

In my airspace, "Descend when ready" will only be heard when the controller is bored out of his brains and has sod all else to do. Its an unnecessary transmission. You request descent, you get it. Easy.

You say if ATC comes back and says "affirm, pilots discretion" after issuing a descent clearance, that you're not getting the service. Rubbish. Here's how it works.

I plan ahead, and I know I need to have you at say 260 crossing x point for the next sector. I give you a decent to 260, and you say "is that pilots discretion"? I then have a look at it, and agree to make it pilots discretion, but be level 15 before x point. What happens then? I sit there watching you approach x point and then perform an airshow dive to 260 just making it in time. All my time has been spent worrying whether you are going to remember to descend or not, whether I should ring the next sector to co-ordinate just in case etc. So its easier just to say "Descend FL260", and see you on your way.

That's not lack of service, that's safe service.


Re. direct routings

I wouldn't expect you to appreciate the problem in issuing long directs as regards co-ordination. Before I sign off, here's an example.

"Flight 123, request direct ABC"

"Roger, 123, standby"

Phone call 1.
"Hello Sector 1, did you get the estimate on FLT123?
"123, em, yes. I think so, hang on, oh yes have him now. Through XYZ at 37?"
"Yes, great, he's looking to go direct to ABC, that would take him about 20miles north of XYZ."
"Eh, yeah, that should be ok, check it with Sector 2 though will you"
"No problem"

Phone call 2.
"Hello Sector 2, you won't have details, but Im working a FLT123 that wants a direct clearance to ABC, he'll just cut the edge of your airspace near XYZ"
"FLT123 you say, yeah no details, hang on. (Muttering in the background to radar controller ... )
"Eh, where's he through? "
"Well hes planned though XYZ at 370, but the direct will take him through your airspace about 20 north of that"
"Ok, hang on ... yes, that should be ok, and do Sector 3 know?"
"I'll call them, and do you want to work him"
"No, no need, give him straight to 1"
"Thanks a lot"

Phone call 3.
"Hello Sector 3, do you have details on FLT123"
"Who?"
"FLT123"
"Eh, no, no details"
"OK hes wanting to route via about 20 north of XYZ and going to ABC direct, he'll cross over x at 370, is that ok?"
"How soon?"
"Eh, hang on ... oh, about 12 minutes or so"
"Yeah that's ok
"Thanks"


"FLT123, cleared direct ABC"

"Direct ABC, Flt 123"

And you want us to do this for every flight?

AF1 is offline