DUAT

There's no reason to put an altitude in when you're OTP. ATC knows you
may need to change altitudes for clouds, winds, etc.



Stan Prevost wrote:
I tried it and OTP is accepted. However, I then tried OTP/125, and that was
also accepted, as was VFR/125 (for FF). I just had the order of the
subfields switched in my head. Apparently nothing has changed.

Stan


"Newps" wrote in message
...

Try just OTP. The actual altitude is not needed.



Stan Prevost wrote:

I used to use DUAT to file flight plans for VFR Flight Following and VFR
On Top. Not long ago, they changed their software. Now I can't get it
to accept an OTP flight plan. Haven't tried FF.

Example: Yesterday I filed an IFR plan having altitude field of 125/OTP.
It rejected it. It accepted 125 for altitude, but I had to put "VFR On
Top" in Remarks.

Anyone else have this problem with DUAT? I haven't tried DUATS.

Stan

If I put the desired altitude in the plan, then the controller knows that I
want 12500 and can tell me to "maintain VFR On Top at or below 12500". If I
don't put it in, then he has to ask me what altitude I want or just
arbitrarily assigns me something and then if it's not what I want we have to
go through more radio exchange.

How is it better to not include the altitude?


"Newps" wrote in message
...
There's no reason to put an altitude in when you're OTP. ATC knows you
may need to change altitudes for clouds, winds, etc.



Stan Prevost wrote:
I tried it and OTP is accepted. However, I then tried OTP/125, and that
was also accepted, as was VFR/125 (for FF). I just had the order of the
subfields switched in my head. Apparently nothing has changed.

Stan


"Newps" wrote in message
...

Try just OTP. The actual altitude is not needed.



Stan Prevost wrote:

I used to use DUAT to file flight plans for VFR Flight Following and VFR
On Top. Not long ago, they changed their software. Now I can't get it
to accept an OTP flight plan. Haven't tried FF.

Example: Yesterday I filed an IFR plan having altitude field of
125/OTP. It rejected it. It accepted 125 for altitude, but I had to put
"VFR On Top" in Remarks.

Anyone else have this problem with DUAT? I haven't tried DUATS.

Stan

Include what you *think* the weather conditions *might* allow your VFR
cruising altitude to be if you feel like it but "VFR-On-Top" alone is your
*requested/assigned* IFR altitude.

Once you report reaching VFR-On-Top and the controller reclears to to
"Maintain VFR-On-Top" he isn't responsible for separation. After that he
doesn't really care much what your actual altitude is now or might be later
(beyond verifying your Mode C for traffic or idle curiosity).

Any altitude restrictions issued *before* you reach VFR-On-Top are a
different matter.

"Stan Prevost" wrote in message
...
If I put the desired altitude in the plan, then the controller knows that
I want 12500 and can tell me to "maintain VFR On Top at or below 12500".
If I don't put it in, then he has to ask me what altitude I want or just
arbitrarily assigns me something and then if it's not what I want we have
to go through more radio exchange.

How is it better to not include the altitude?


"Newps" wrote in message
...
There's no reason to put an altitude in when you're OTP. ATC knows you
may need to change altitudes for clouds, winds, etc.



Stan Prevost wrote:
I tried it and OTP is accepted. However, I then tried OTP/125, and that
was also accepted, as was VFR/125 (for FF). I just had the order of the
subfields switched in my head. Apparently nothing has changed.

Stan


"Newps" wrote in message
...

Try just OTP. The actual altitude is not needed.



Stan Prevost wrote:

I used to use DUAT to file flight plans for VFR Flight Following and
VFR On Top. Not long ago, they changed their software. Now I can't
get it to accept an OTP flight plan. Haven't tried FF.

Example: Yesterday I filed an IFR plan having altitude field of
125/OTP. It rejected it. It accepted 125 for altitude, but I had to
put "VFR On Top" in Remarks.

Anyone else have this problem with DUAT? I haven't tried DUATS.

Stan

Once you report reaching VFR-On-Top and the controller reclears to to
"Maintain VFR-On-Top" he isn't responsible for separation. After that he
doesn't really care much what your actual altitude is now or might be later
(beyond verifying your Mode C for traffic or idle curiosity).

Maybe so, but you're required to report changing altitudes when flying
VFR-On-Top (at least, per the AIM)...

--
Cheers,
John Clonts
Temple, Texas
N7NZ

"John Clonts" wrote in message
oups.com...

Maybe so, but you're required to report changing altitudes when flying
VFR-On-Top (at least, per the AIM)...


The AIM says pilots SHOULD advise ATC prior to any altitude change when
operating OTP.

On 7/12/2005 07:47, Steven P. McNicoll wrote:

"John Clonts" wrote in message
oups.com...

Maybe so, but you're required to report changing altitudes when flying
VFR-On-Top (at least, per the AIM)...


The AIM says pilots SHOULD advise ATC prior to any altitude change when
operating OTP.



Sorry if I'm missing something, but aren't we talking about two different
flight modes here?

Over the Top is a VFR flight mode. You are not under IFR restrictions.

VFR On Top is an IFR clearance. You are under IFR restrictions and must
report changes in altitude (among other IFRs).


--
Mark Hansen, PP-ASEL, Instrument Student
Sacramento, CA

The AIM says pilots SHOULD advise ATC prior to any altitude change when
operating OTP.

Sorry if I'm missing something, but aren't we talking about two different
flight modes here?

No, just one.

Over the Top is a VFR flight mode. You are not under IFR restrictions.

Not this one.

VFR On Top is an IFR clearance. You are under IFR restrictions and must
report changes in altitude (among other IFRs).

This is the one we're talking about. I think Steve is pointing out the
distinction
between my use of the words "required to", your use of the word "must",
and the AIM's use of the word "should" (AIM 5-3-3).

--
Cheers,
John Clonts
Temple, Texas
N7NZ

"Mark Hansen" wrote in message
...

The AIM says pilots SHOULD advise ATC prior to any altitude change when
operating OTP.

Sorry if I'm missing something, but aren't we talking about two different
flight modes here?

Over the Top is a VFR flight mode. You are not under IFR restrictions.

VFR On Top is an IFR clearance. You are under IFR restrictions and must
report changes in altitude (among other IFRs).


OTP is the contraction for "On Top". It is what ATC enters in an IFR flight
plan for aircraft that are operating VFR-on-top.

"KP" nospam@please wrote in message
...
Include what you *think* the weather conditions *might* allow your VFR
cruising altitude to be if you feel like it but "VFR-On-Top" alone is your
*requested/assigned* IFR altitude.

Once you report reaching VFR-On-Top and the controller reclears to to
"Maintain VFR-On-Top" he isn't responsible for separation. After that he
doesn't really care much what your actual altitude is now or might be
later (beyond verifying your Mode C for traffic or idle curiosity).


I have never received a clearance for just "VFR On Top" without further
restrictions, although I understand it is permitted. Restrictions can be
"Maintain VFR On Top at or below xxx", "....at or above xxx", or "... at or
between xxx and yyy".

I understand that the controller is not responsible for separation, so I
wonder why I always get an altitude restriction, usually "at or below".

Stan

Stan Prevost wrote:



I have never received a clearance for just "VFR On Top" without further
restrictions, although I understand it is permitted.

I can't understand why you'd restrict an aircraft, outside of a class B.

Restrictions can be
"Maintain VFR On Top at or below xxx", "....at or above xxx", or "... at or
between xxx and yyy".

Yes, but what's the point? I don't have to separate you so why restrict
you?



I understand that the controller is not responsible for separation, so I
wonder why I always get an altitude restriction, usually "at or below".

Ask next time.