OnCourse Software

Morning,

I'm trying to do a flight from PHKO to NFFN, with NFNA as the alternate.

When I load the flightplan, there are XXX boundary points after NFFN, which then fails PF3 because XXX is not a valid destination airport.

It happens weather or not I use the alternate.

I've attached my flightplan. There are no logs as PF3 does not even start the flightplan.

Thanks!

There is no attachment.
(if the forum rejected it, put it into a .zip file)

DOH!!

Thanks... looks like another Meridian line problem. We're looking at it now.

Update: Strange this is if you create a flight plan in FS9 for that departure and destination it works just fine!

Routefinder has generated this fpl.

Quote:

Computed route from KONA INTL AT KEAHOLE (PHKO, PH) to NADI INTL (NFFN, NF): 10 fixes, 2800.8 nautical miles

Cruise altitude between FL340 and FL340
PHKO (0.0nm) -DCT-> CARRP (204.3nm) -A579-> CHEEM (277.0nm) -A579->
CROBY (825.2nm) -A579-> CEBUR (1363.8nm) -A579-> CUFFY (1902.2nm) -A579->
IDEMU (2252.9nm) -A579-> KABAR (2693.6nm) -A579-> NN (2794.1nm) -DCT->
NFFN (2800.8nm)

PF3 generates two control boundaries. One between CHEEM and CROBY
and the other between IDEMU and KABAR. The first is correct as being the boundary for Honolulu.
However there is a discrepancy. The PF3 flight plan seems to be ok but the .json file ends at the last XXX after IDEMU with no destination and also the wypts KABAR and NN are missing from the json file. I suspect because the fpl goes from the Northern Hemisphere to the Southern.

dmarch wrote:

Thanks... looks like another Meridian line problem. We're looking at it now.

Update: Strange this is if you create a flight plan in FS9 for that departure and destination it works just fine!

Since I don't have FS9 installed, I tried using PFPX to generate a FS9 flight plan. I still get the same behavior.

I've included the FS9 plan if you want it to compare.

Devin

netshadoe wrote:

dmarch wrote:

Thanks... looks like another Meridian line problem. We're looking at it now.

Update: Strange this is if you create a flight plan in FS9 for that departure and destination it works just fine!

Since I don't have FS9 installed, I tried using PFPX to generate a FS9 flight plan. I still get the same behavior.

I've included the FS9 plan if you want it to compare.

Devin

Interestingly that fpl has no XXX boundaries at all!! That said the json file splits it in two. So there is a North South Hemisphere glitch even though the fpl itself seems ok.

Dave, this is the FPP zip of this latest fpl.

vololiberista wrote:

netshadoe wrote:

dmarch wrote:

Thanks... looks like another Meridian line problem. We're looking at it now.

Update: Strange this is if you create a flight plan in FS9 for that departure and destination it works just fine!

Since I don't have FS9 installed, I tried using PFPX to generate a FS9 flight plan. I still get the same behavior.

I've included the FS9 plan if you want it to compare.

Devin

Interestingly that fpl has no XXX boundaries at all!! That said the json file splits it in two. So there is a North South Hemisphere glitch even though the fpl itself seems ok.

Dave, this is the FPP zip of this latest fpl.

FPP.zip

Hmm..Weird. I get XXX boundaries after NFFN.