View Single Post
  #25  
Old September 18th 03, 06:42 PM
Bob Gardner
external usenet poster
 
Posts: n/a
Default

It's a local knowledge thing, Ben, but you know and I know that there is no
conflicting airspace in the vicinity of Astoria that would obviate holding
on the course on which you approach the holding fix. From what I have seen
and experienced, holding pattern airspace placement is designed to keep two
or more "reserved for holding or other ATC purposes" blocks of airspace from
overlapping.

Bob Gardner

"Ben Jackson" wrote in message
news:%Nbab.376350$Oz4.157019@rwcrnsc54...
In article ,
John Clonts wrote:

Afterwards it dawned on me that the published hold that he was talking

about
was the hold depicted on the BMQ NDB-1 approach plate. The NDB is on the
field, but my mind had been in "gps" mode since I don't have ADF in this
plane.


I don't think that's legitimate. A given navaid can have different holds
for different procedures. The AST VOR Rwy 8 (Astoria, OR) missed approach
terminates in a hold on the 115 radial of AST, left turns. The AST ILS
Rwy 26 missed approach ends in a hold on the 075 radial of AST, right
turns. I guess all the published holds have sufficient protected airspace
(in this case, mostly the Pacific ocean), but there is no hold depicted
on the enroute chart, so I don't know what the controller would expect
if they just said "hold at AST as published".

--
Ben Jackson

http://www.ben.com/