Hi,

I'm having an unusual problem that just crept up, What is happening is that when I create a flight plan using Victor (V) or Jet (J) routes, I no longer get an airway route. It is only happening on one computer and across v 2.03 and the latest version 2.2.2. The flight plan being created was KGCN - KSAF, but it also occurs when try to create other plans as well. When pressing the Victor route I'm only getting the Gallup (GUP) VOR for a route. I tried creating the same flight plan on another computer with Little Nav Map and I received V210-V68 for the airways. I was wondering is there something I'm missing or doing wrong?  I tried deleting the Nav Map folder, and copying the folder from the computer where the flight plan gave me the correct routing, but the same thing happened again. Any help is appreciated.

Thanks again for a great product, and Happy Holidays,

 

Tony J 

Update:

 

Solved. Found my problem. Under Tools, Options, Flight Plan, I had "Use VOR stations as transition checked. I'm seeing what I'm used to seeing.

 

Tony J

 

 

Yup. This setting can turn the route into a direct if there are no VOR or NDB nearby.

Happy holidays to you too!

Alex

Hi

 

I am  however having another anomaly. I use PF3 for my ATC program and I was doing a departure from KGCN (field elevation 6609') and I was given a clearance to climb to 5000'. I contacted PF3 about it and they found the flight plan I created showed an initial field elevation of 0'. Subsequently I went through a lot of flight plans that I've created in Nav Map and I have found a lot of them where the  field elevation does not seem to be saving correctly. Here are two examples of the same flight plan created (obviously not the full flight plan) . I was wondering is there something I may be doing wrong when saving the flight plan that may be causing the problem. The problem does not seem to be consistent, meaning sometimes the field elevation shows correctly and sometimes it doesn't. I typically save my flt plans as ICAO - ICAO.PLN for uniformity in my flight plan folder, but the problem seems to occur regardless of how I save it. 

Again, Thanks for your help and support,

Tony J

 

<Title>KGCN to KSAF</Title>
<FPType>IFR</FPType>
<RouteType>LowAlt</RouteType>
<CruisingAlt>15000</CruisingAlt>
<DepartureID>KGCN</DepartureID>
<DepartureLLA>N35° 57' 32.48",W112° 8' 11.28",+000000.00</DepartureLLA>
<DestinationID>KSAF</DestinationID>
<DestinationLLA>N35° 37' 1.59",W106° 5' 21.93",+006348.00</DestinationLLA>
<Descr>KGCN, KSAF</Descr>
<DeparturePosition>PARKING 7</DeparturePosition>
<DepartureName>Grand Canyon Natl Park</DepartureName>
<DestinationName>Santa Fe Mun</DestinationName>


<ATCWaypoint id="KGCN">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N35° 57' 8.50",W112° 8' 49.10",+006609.00</WorldPosition>
<ICAO>
<ICAOIdent>KGCN</ICAOIdent>


<ATCWaypoint id="KSAF">
<ATCWaypointType>Airport</ATCWaypointType>
<WorldPosition>N35° 37' 1.59",W106° 5' 21.93",+006348.00</WorldPosition>
<ICAO>
<ICAOIdent>KSAF</ICAOIdent>

 

 

 <FlightPlan.FlightPlan>
        <Title>KGCN to KSAF</Title>
        <FPType>IFR</FPType>
        <RouteType>LowAlt</RouteType>
        <CruisingAlt>15000</CruisingAlt>
        <DepartureID>KGCN</DepartureID>
        <DepartureLLA>N35° 56' 35.85",W112° 9' 23.54",+006609.00</DepartureLLA>
        <DestinationID>KSAF</DestinationID>
        <DestinationLLA>N35° 37' 1.59",W106° 5' 21.93",+006348.00</DestinationLLA>
        <Descr>KGCN, KSAF</Descr>
        <DeparturePosition>03</DeparturePosition>
        <DepartureName>Grand Canyon Natl Park</DepartureName>
        <DestinationName>Santa Fe Mun</DestinationName>
        <AppVersion>
            <AppVersionMajor>10</AppVersionMajor>
            <AppVersionBuild>61472</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="KGCN">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N35° 57' 8.50",W112° 8' 49.10",+006609.00</WorldPosition>
            <ICAO>
                <ICAOIdent>KGCN</ICAOIdent>
 

 

 

 

Hi Tony,

thank you for the error report. I can reproduce this and it is clearly a bug.

This seems to happen when a parking position is set for departure.

Alex

Alex,

 

Thanks for looking into it.

 

Tony