What a laugh

Richard

Final Approach
Joined
Feb 27, 2005
Messages
9,076
Location
West Coast Resistance
Display Name

Display name:
Ack...city life
I got a laugh yesterday. Keep in mind the rwy here is 15-33.

A Pilatus inbound from the south calls to say he'll be flying a VOR app to rwy 32.

Two other inbounds report their intentions to land 33.

The PC-12 makes a 2nd call, rwy 32.

A King Air makes his initial call saying he'll be landing rwy 32.

The other inbound traffic report their pattern legs all saying rwy 33.

The KA says he's now entering downwind rwy 32.

The local traffic report each report clear of rwy 33 after landing.

The PC-12 reports outbound on the VOR-B rwy 32.

I report inbound to land rwy 33.

A 141 flight school Bonanza holding short calls, Position and hold rwy 32.

The KA makes a full stop landing on 33, taxis back for another takeoff, and still calls rwy 32.

I report downwind and base rwy 33.

The KA reports base rwy 32.

I report clear rwy 33.

A local C-172 reports departing rwy 33.

The KA reports final rwy 32.

The PC-12 reports final rwy 22. (two-two)
 
So I land at some airport with which I am unfamiliar. Made appropriate traffic calls.

When I clear the runway, I zone-out on runway number. Do I say, "Clear of the runway..."?

No, no, I say "...clear of runway... ummm... uh.... some runway or another."

Very impressive, no?

I got a laugh yesterday. Keep in mind the rwy here is 15-33.

A Pilatus inbound from the south calls to say he'll be flying a VOR app to rwy 32.

Two other inbounds report their intentions to land 33.

The PC-12 makes a 2nd call, rwy 32.

A King Air makes his initial call saying he'll be landing rwy 32.

The other inbound traffic report their pattern legs all saying rwy 33.

The KA says he's now entering downwind rwy 32.

The local traffic report each report clear of rwy 33 after landing.

The PC-12 reports outbound on the VOR-B rwy 32.

I report inbound to land rwy 33.

A 141 flight school Bonanza holding short calls, Position and hold rwy 32.

The KA makes a full stop landing on 33, taxis back for another takeoff, and still calls rwy 32.

I report downwind and base rwy 33.

The KA reports base rwy 32.

I report clear rwy 33.

A local C-172 reports departing rwy 33.

The KA reports final rwy 32.

The PC-12 reports final rwy 22. (two-two)
 
So I land at some airport with which I am unfamiliar. Made appropriate traffic calls.

When I clear the runway, I zone-out on runway number. Do I say, "Clear of the runway..."?

No, no, I say "...clear of runway... ummm... uh.... some runway or another."

Very impressive, no?
But interspersed with your calls at an unfamiliar aprt there are numerous calls using the correct number. Were you not listening? Were all your calls in the blind?
 
So I land at some airport with which I am unfamiliar. Made appropriate traffic calls.

When I clear the runway, I zone-out on runway number. Do I say, "Clear of the runway..."?

No, no, I say "...clear of runway... ummm... uh.... some runway or another."

Very impressive, no?

You shouldn't make "clear of runway" calls at all. Traffic that cares should be able to see the runway. :rolleyes:
 
Are you still in Page? What's shaken' there during the winter? (Though with your story there must be some traffic ;) )
 
You shouldn't make "clear of runway" calls at all. Traffic that cares should be able to see the runway. :rolleyes:

Perhaps so, just doing as I was taught...

...which is never an excuse, is it?
 
You shouldn't make "clear of runway" calls at all. Traffic that cares should be able to see the runway. :rolleyes:

I can think of times when it's useful.

A hump in the runway that doesn't allow someone at the departure end to see the opposite end. The airport by Robert Lee, TX comes to mind.

Reduced visibility. Shooting approaches to minimums close behind someone else - it's nice to know they are off before you break out at.

I'm sure there's more...
 
Are you still in Page? What's shaken' there during the winter? (Though with your story there must be some traffic ;) )
Yep, still. Yesterday I had 4 flights, the most in any one day since early Nov. 14.9 TT this month so far. Last month was 7.2.

Also, got some time in a Bonanza and a geared engine C-172 yet to log.

The big news was reported today WRT the EMS helo accident in Flag last summer. Evidently, numerous news choppers circling an auto accident near the hospital provided a distraction to the EMS pilots.

Yesterday, heavy snow storm. Highs mid 30s now. Sustained seasonal winds yet to come.​
 
Sounds like every time I've been to 6Y9:

"N277DL is on a left downwind for... uhhh... errr... hmmm... the east.. yeah.. we'll be landing east... yeah yeah.. N277DL will be landing to the east. ATITAPA." :D :D
 
It's one of those calls where CFI Joe will cut off my mic button finger.
Why? From the AIM 4-1-9 (g):
(a) Inbound
EXAMPLE-
Strawn traffic, Apache Two Two Five Zulu, (position), (altitude), (descending) or entering downwind/base/final (as appropriate) runway one seven full stop, touch-and-go, Strawn.
Strawn traffic Apache Two Two Five Zulu clear of runway one seven Strawn.
 
Based on the operation you described, I'm guessing it was a newbie Duckbill driver with no brain cells left over to process the "small stuff."
 
So I land at some airport with which I am unfamiliar. Made appropriate traffic calls.

When I clear the runway, I zone-out on runway number. Do I say, "Clear of the runway..."?

No, no, I say "...clear of runway... ummm... uh.... some runway or another."

Very impressive, no?

Look at your DG. It has an automatic runway number detector that is at least close enough.

Otherwise, "clear of all runways" would work if you were indeed clear of all runways at the airport.

I do feel there is value in the call.
 
An amusing story... at least they were only off by ten degrees. :D

I like to call "clear", and give the runway number, more as a courtesy than anything else.
There may be traffic that isn't close enough to see the runway well, but could nonetheless benefit from knowing you're not still taxiing or sitting there. And the hump scenario is very real... it becomes a problem when you know, say, that there's someone on base... you could get onto the runway and outta there quickly, if only you'd heard from or could see that other plane that just landed...don't want to just pull into position, as the next plane is getting onto final, only to find the first plane is still sitting there for some reason. Can't imagine what reason anyone would have for parking on the runway after landing? There seem to be a lot of reasons, 'cuz people do it. Usually confusion, I think, or a half-hearted near-decision to back-taxi. A malfunction could cause this, too- locked brakes, flat tire, loss of power, etc.

At any rate, the "clear" call isn't a big freq-clogger, and in fact it might save more chatter. Giving the correct runway heading at a single-strip airport is just a quick courtesy for approaching traffic or maybe that pilot who's just started up and isn't sure yet what runway's in use.

Only potential harm in habitual "clear of runway" calls is that SO many people call "clear" when they are NOT clear... usually at that moment when they realize "yes, I'll make this taxiway... better call now 'cuz I'll be busy rushing my post-landing checklist while trying to turn..." :frown2:
 
Sounds like every time I've been to 6Y9:

"N277DL is on a left downwind for... uhhh... errr... hmmm... the east.. yeah.. we'll be landing east... yeah yeah.. N277DL will be landing to the east. ATITAPA." :D :D

usually when i havent looked up or have forgotten the runway number, i use the general direction.

such as: "gastons traffic Husky on left downwind for landing to the west"

or: "gastons traffic Husky on a left downwind for that runway that we land on"

Both convey the same message as saying the runway number.

It's one of those calls where CFI Joe will cut off my mic button finger.

Well Joe needs to spend more time flying at airports that arent in bowls or perfectly flat. We have numerous blind spots around here, due to slight variations in elevation, and depending on the crop rotation, how tall the Corn has gotten.
 
Well, it's all about SA. And if your radio call doesn't promote that (isn't relatable or adds to confusion) you may as well stay silent. The flight doesn't end until the wheels are chocked.

At a single strip, I know what they mean when they say, RWY 22 when they meant 33. After all, I had been mentally "flight following". But when that PC-12 did call 22 when he meant 33 it made me think of an airport with crossng runways. At those airports, yeah, it could be a big problem.
 
Last edited:
I can think of times when it's useful.

A hump in the runway that doesn't allow someone at the departure end to see the opposite end. The airport by Robert Lee, TX comes to mind.

Reduced visibility. Shooting approaches to minimums close behind someone else - it's nice to know they are off before you break out at.

I'm sure there's more...

IMO it's a good idea all the time. There are lots of situations when it's difficult or impossible to see traffic on the runway from the hold short line and even from the air, it's nice to know the traffic that just landed isn't climbing back into the pattern if you are entering same. And calls from the ground don't have much impact on CTAF bandwidth since unlike airborne transmissions they generally won't carry more than 10-15 miles.
 
"Poedunk traffic, N1233, clear 10, Poedunk" should save incoming flights from the "Poedunk unicom, which runway are you using?"
Of course my brain tells me either you should follow other traffic or....
FIGURE IT OUT. Except in those few airports that the owner feels compelled to play TOWER and tell you, it usually isn't that difficult.
 
When I clear the runway, I zone-out on runway number. Do I say, "Clear of the runway..."?

No, no, I say "...clear of runway... ummm... uh.... some runway or another."

Very impressive, no?

"Podunk traffic, Skylane 271G, clear of all runways."

And if you're lucky, there might be a runway sign there too. ;)

I can think of times when it's useful.

I'm sure there's more...

Yep, and I habitually call it because if I'm landing at a new airport I probably don't know if part of the runway I just landed on is visible from another runway, or even from the whole runway I'm on. Besides, as Lance points out:

And calls from the ground don't have much impact on CTAF bandwidth since unlike airborne transmissions they generally won't carry more than 10-15 miles.

Only potential harm in habitual "clear of runway" calls is that SO many people call "clear" when they are NOT clear... usually at that moment when they realize "yes, I'll make this taxiway... better call now 'cuz I'll be busy rushing my post-landing checklist while trying to turn..." :frown2:

That's why my "clear" call comes when the tail crosses the hold short line. Probably a habit from the home drome, where after I get "Left on Charlie, contact ground 121.9" I continue to monitor tower until I'm completely across the line, and I call "Madison ground, Skylane 271G, clear of 32 on Charlie for the south ramp" so that the call ends as close as I can get it to after the tail is crossing the hold short line. As far as they're concerned, you ain't clear until the entire aircraft is across the line.

Well Joe needs to spend more time flying at airports that arent in bowls or perfectly flat. We have numerous blind spots around here, due to slight variations in elevation, and depending on the crop rotation, how tall the Corn has gotten.

I was gonna say, can a plane at the end of 19 even see a plane at the end of 13 and vice versa?
 
I make a "Clear of runway [whatever]" call when the tail crosses the hold short line, which is the legal point at which it is clear.

There is value at an uncontrolled field, at least at a bunch of the ones around here. Furthermore, if I'm sitting at the departure end, I want to hear the pilot that just landed confirm that he is off the runway and I'm good to take off.
 
I was gonna say, can a plane at the end of 19 even see a plane at the end of 13 and vice versa?

no. and from the end of 13 you really cant see the end of any of the other runways, including 31. and you also cant see where 1/19 crosses 13/31.
 
You shouldn't make "clear of runway" calls at all. Traffic that cares should be able to see the runway. :rolleyes:

I disagree. There's situations when it's needed and appreciated. If you're
in the air you can see what's going. Not always when you're on the ground. At our airport the runway rises in the center and you can't see the whole
runway. In addition on the north end there's corn between the taxiway
and runway. Also before the south parallel taxiway was built ... if someone
was back taxiing it's nice to know when they're clear. (the taxiway was
at the center of the runway).

I don't want to have to abort because Geico is out there riding around
in his little RV.

;-)
 
You shouldn't make "clear of runway" calls at all. Traffic that cares should be able to see the runway. :rolleyes:

Perhaps so, just doing as I was taught...

...which is never an excuse, is it?

It's one of those calls where CFI Joe will cut off my mic button finger.

I learned to fly at ISZ. At the time (it may be different now) there was a large grove of trees in the line of sight between one of the penalty box areas and the other end of the runway. "Clear of Runway" calls were the courteous thing to do. Likewise at runways with a bit of a hump in them that may prevent sight-line from one end to the other.

As noted elsewhere, the AIM indicates it to be a desired call.
 
You shouldn't make "clear of runway" calls at all. Traffic that cares should be able to see the runway. :rolleyes:

Not necessarily. If there is traffic holding short to depart and there is a rise in the middle of the runway, they might not be able to see your airplane at the far end, thus it's a good idea for you to make the "clear of the runway" call. "Clear of the active runway", on the other hand... :nono::nonod:

EDIT: Oops! Sorry to repeat what has already been said... guess I should have read the whole thread before responding to one post ;).
 
Last edited:
...

Well Joe needs to spend more time flying at airports that arent in bowls or perfectly flat. We have numerous blind spots around here, due to slight variations in elevation, and depending on the crop rotation, how tall the Corn has gotten.

We need the TSA combine to clear your airport of the terrist corn that's plaguing it.
 
We need the TSA combine to clear your airport of the terrist corn that's plaguing it.

watch it. our airport manager cares #1 about making the airport make money. everyone knows that cities never directly make money off their airport. except for Ames. We've nearly gotten to the point of recommending to him that we plow up the runways and plant corn...
 
Back
Top