Again, this paragraph as well as 9.11.4 address practice instrument approaches, not necessarily general ops. But people who have read the AC commonly assume, as you have, that it's reasonable for all ops.
Again, this paragraph as well as 9.11.4 address practice instrument approaches, not necessarily general ops. But people who have read the AC commonly assume, as you have, that it's reasonable for all ops.
Paragraph 9.11.4 addresses "Practice Instrument Approaches", specifically as delineated by the Heading, along with 3 sub-paragraphs, al;so specific to Practice Instrument Approaches.
Conversely, Paragraph 9.11.5, a separate Paragraph, falls under Paragraph 9, entitled "General Operating Practices", e.g. Major Heading, but a Sub-Heading, "Traffic Flow". Paragraph 9.11.4 is specific (to practice instrument approaches), while Paragraph 9.11.5 is non-specific under the Major Heading and Sub-Heading.
No assumption, just statutory construction, FAA-style.
The entirety of Paragraph 9.11.5 refers to IFR pilots making radio calls with respect to instrument approach procedures.
That said, it doesn't matter which one of us is "right". The fact we're debating at all shows that many readers of the AC are going to conclude that self-announcing T&G vs. full-stop vs. missed is good practice in all cases. In short, the OP isn't going to find much support for his thesis.
I have abandoned the word "traffic" at uncontrolled airports as being just more unnecessary words. The only time it seems to be useful is when someone calls up a controlled airport thinking it's uncontrolled.
I don’t have a problem with the use of the AIM-standard “Podunk traffic” at the beginning of the transmission to indicate it’s a position report and not a request for FBO services.. I do wince a bit at the not-AIM-standard use of the word “traffic” at the end of the transmission.
Does this paragraph from the AIM help resolve the question whether the recommendation announcing touch & go vs full stop is limited to practice instrument approaches?
8. Recommended self-announce broadcasts: It should be noted that aircraft operating to or from another nearby airport may be making self-announce broadcasts on the same UNICOM or MULTICOM frequency. To help identify one airport from another, the airport name should be spoken at the beginning and end of each self-announce transmission. When referring to a specific runway, pilots should use the runway number and not use the phrase “Active Runway.”
(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.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.