Any traffic in the area, please, advise.

[avbug]

Wallawallabingbang traffic, Uncle Monkey Titibar Sugar Niner is thirteen point two miles out over the chicken farm on a really wide left base for the one runway that goes north. I am a green airplane with yellow stripes. I am wearing a plaid shirt with long sleeves. My turnons are turtles that eat lettuce, and electricity. I'm a Leo and answer to the name of "Chuckles" on Wednsdays at the Met. Any inbound traffic advise, please.


Land uphill takeoff down, wind notwithstanding. Except Wednsdays.

 

[UndauntedFlyer]

SO? Discuss.

The problem here with "Any traffic in the area please advise" is only that of frequency congestion. The solution, in my opinion, is not to stop this effective technique of soliciting reports of pilots that pose a potential collision hazard, the solution to the problem should be to simply add more frequencies. 122.7, 122.8, 122.9 & 123.0 are just not enough in busy areas. What about quarter spacing all of those frequencies?

 

[MauleSkinner]

The problem here with "Any traffic in the area please advise" is only that of frequency congestion. The solution, in my opinion, is not to stop this effective technique of soliciting reports of pilots that pose a potential collision hazard, the solution to the problem should be to simply add more frequencies. 122.7, 122.8, 122.9 & 123.0 are just not enough in busy areas. What about quarter spacing all of those frequencies?

I would venture that even if you were at the only airport on that frequency and used "this effective technique of soliciting reports", and all 3 of the airplanes on downwind decided to advise all at once, you'd STILL have frequency congestion.

Personally, I think monitoring the CTAF for a couple of minutes before making your initial call is a better technique, and unless you fly IFR with a single comm radio, it's possible.

Fly safe!

David