"Ron Rosenfeld" wrote in message
...
On Thu, 6 Nov 2003 22:45:15 -0500, "Robert Henry"
wrote:

The instruction was terrible, but
technically/procedurally correct as far as I have been able to establish

That removes the controller training level from the risk equation.


I thought you said that ATC was not protecting the ODP for an IFR
departure. If so, there is an ATC training issue that will affect other
pilots who do things by the book.

No, sorry for the confusion. In the discussions that followed, the tower
suggested that I inform them of my intentions to fly the ODP (which is
similar to the circumstances originating this thread, right?), so that they
could coordinate better. The implication was that in vmc RAPCON could
vector arriving aircraft on the visual approach further away from the ODP so
that there would not be a head to head situation. There was nothing to
imply that the ODP was not being protected.

Now, it is my position that the safer procedure would be for the tower to
automatically issue departure heading instructions that are consistent with
the ODP. I think we agree on that. (Frankly, I know now that my error was
in expecting this to happen - AGAIN, a misconception (that I believe
non-scientifically could be fairly common about the level of service one can
expect at a towered airport in a radar environment on an IFR flight plan.)
Now, when the pilot contacts departure, he can say, "...can we get on
course?" Departure can say, "radar contact, but I cannot turn you on course
until you reach MVA." If conditions warrant, the pilot can come back and
say, "We will maintain our own terrain clearance, request on course." All
things being equal, that could be approved as requested with an instruction
to maintain visual terrain clearance.