![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#6
|
|||
|
|||
![]()
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 |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Duat Graphics | Slick | Piloting | 0 | January 23rd 05 01:35 PM |
NAS and associated computer system | Newps | Instrument Flight Rules | 8 | August 12th 04 05:12 AM |
DTC DUAT | Matt Whiting | Instrument Flight Rules | 0 | June 5th 04 03:23 PM |
Picking Optimal Altitudes | O. Sami Saydjari | Instrument Flight Rules | 20 | January 8th 04 02:59 PM |