High Airspace

[Chappie88 2]

Created a flight from KORD to KATL (about 550 nm) in Auto mode and selected High Airspace as my desired planning airspace and it chose two Victor routes to file on and built the altitudes to remain below FL180 to do it during the departure and arrival phases. It remained below FL180 for 100 miles to get to a point where it picked up the starting point for a J-route. Highly unrealistic it seems to me. Used version 1.11.

Steve

[Pierre95 14]

Hi Steve,

Maybe a altitude restriction on airway used

Could you send us you plan, please.

Best Regards

Pierre

[dougsnow 50]

Ive seen it on multiple US routes when I autobuild.

[DLRK 2]

This is a very frustrating problem I also have with PFPX. It will happen with almost any U.S. route.

Would it be possible in the future for someone from the U.S. or Canada to be included in the development or testing process?

[dougsnow 50]

I'm in the US, and I have been involved in dev since the earliest inceptions of PFPX...

Autorouters work wonders, except when they dont. PFPX doesnt do anything different from an autorouting respect that professional flight planning systems dont do. I've seen crazy ass routings in real world flight planning systems as well when you let it autoroute.

Thats why I, at my airline, rarely let the thing autoroute - I'll let it do something oceanic, but, overland (and especially over the US), I'll do the routing...

[Chappie88 2]

Hi Steve,

Maybe a altitude restriction on airway used

Could you send us you plan, please.

Best Regards

Pierre

Here you go: (I did not choose the 17,000 altitude, it was set to OPT and it called for the climb to go above 17,000 at BVT which was 100nm into flight). I also checked and this route does not exist in the route database as far as I can tell.

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="AceXML" version="1,0">

<Descr>AceXML Document</Descr>

<FlightPlan.FlightPlan>

<Title>KORD to KATL</Title>

<FPType>IFR</FPType>

<RouteType>HighAlt</RouteType>

<CruisingAlt>17000</CruisingAlt>

<DepartureID>KORD</DepartureID>

<DepartureLLA>N41° 58' 45.61",W087° 54' 26.59",672</DepartureLLA>

<DestinationID>KATL</DestinationID>

<DestinationLLA>N33° 38' 12.12",W084° 25' 40.31",1026</DestinationLLA>

<Descr>KORD to KATL created by PFPX - Professional Flight Planner X (http://www.flightsimsoft.com/pfpx)</Descr>

<DeparturePosition>10L</DeparturePosition>

<DepartureName>CHICAGO-OHARE INTL</DepartureName>

<DestinationName>HARTSFIELD - JACKSON ATLANTA I</DestinationName>

<AppVersion>

<AppVersionMajor>10</AppVersionMajor>

<AppVersionBuild>61472</AppVersionBuild>

</AppVersion>

<ATCWaypoint id="KORD">

<ATCWaypointType>Airport</ATCWaypointType>

<WorldPosition>N41° 58' 45.61",W087° 54' 26.59",+000672.00</WorldPosition>

<ICAO>

<ICAOIdent>KORD</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="ORD">

<ATCWaypointType>VOR</ATCWaypointType>

<WorldPosition>N41° 59' 15.68",W087° 54' 17.36",+000000.00</WorldPosition>

<ICAO>

<ICAOIdent>ORD</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="CGT">

<ATCWaypointType>VOR</ATCWaypointType>

<WorldPosition>N41° 30' 36.02",W087° 34' 17.57",+000000.00</WorldPosition>

<ICAO>

<ICAOIdent>CGT</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="COKED">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N41° 25' 15.11",W087° 31' 25.69",+000000.00</WorldPosition>

<ATCAirway>V97</ATCAirway>

<ICAO>

<ICAOIdent>COKED</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="LUCIT">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N41° 13' 56.43",W087° 25' 25.40",+000000.00</WorldPosition>

<ATCAirway>V97</ATCAirway>

<ICAO>

<ICAOIdent>LUCIT</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="ZORRO">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N41° 04' 47.88",W087° 20' 35.14",+000000.00</WorldPosition>

<ATCAirway>V97</ATCAirway>

<ICAO>

<ICAOIdent>ZORRO</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="OXFAT">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N40° 47' 19.35",W087° 11' 25.08",+000000.00</WorldPosition>

<ATCAirway>V97</ATCAirway>

<ICAO>

<ICAOIdent>OXFAT</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="BVT">

<ATCWaypointType>VOR</ATCWaypointType>

<WorldPosition>N40° 33' 22.04",W087° 04' 09.55",+000000.00</WorldPosition>

<ATCAirway>V97</ATCAirway>

<ICAO>

<ICAOIdent>BVT</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="MACES">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N40° 00' 13.25",W086° 43' 22.63",+000000.00</WorldPosition>

<ATCAirway>J89</ATCAirway>

<ICAO>

<ICAOIdent>MACES</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="KURTZ">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N38° 58' 19.89",W086° 05' 33.54",+000000.00</WorldPosition>

<ATCAirway>J89</ATCAirway>

<ICAO>

<ICAOIdent>KURTZ</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="IIU">

<ATCWaypointType>VOR</ATCWaypointType>

<WorldPosition>N38° 06' 12.46",W085° 34' 38.78",+000000.00</WorldPosition>

<ATCAirway>J89</ATCAirway>

<ICAO>

<ICAOIdent>IIU</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="GQO">

<ATCWaypointType>VOR</ATCWaypointType>

<WorldPosition>N34° 57' 40.54",W085° 09' 12.15",+000000.00</WorldPosition>

<ICAO>

<ICAOIdent>GQO</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="DUMBB">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N34° 33' 18.80",W085° 08' 09.52",+000000.00</WorldPosition>

<ATCAirway>V333</ATCAirway>

<ICAO>

<ICAOIdent>DUMBB</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="JIXGU">

<ATCWaypointType>Intersection</ATCWaypointType>

<WorldPosition>N34° 16' 45.73",W085° 07' 27.64",+000000.00</WorldPosition>

<ATCAirway>V333</ATCAirway>

<ICAO>

<ICAOIdent>JIXGU</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="RMG">

<ATCWaypointType>VOR</ATCWaypointType>

<WorldPosition>N34° 09' 45.21",W085° 07' 09.84",+000000.00</WorldPosition>

<ATCAirway>V333</ATCAirway>

<ICAO>

<ICAOIdent>RMG</ICAOIdent>

</ICAO>

</ATCWaypoint>

<ATCWaypoint id="KATL">

<ATCWaypointType>Airport</ATCWaypointType>

<WorldPosition>N33° 38' 12.12",W084° 25' 40.31",+001026.00</WorldPosition>

<ICAO>

<ICAOIdent>KATL</ICAOIdent>

</ICAO>

</ATCWaypoint>

</FlightPlan.FlightPlan>

</SimBase.Document>

[Chappie88 2]

I guess this is identical to this thread: http://forum.aerosoft.com/index.php?/topic/75685-cruise-altitude-what-am-i-doing-wrong/

Steve

[becas 53]

I'm in the US, and I have been involved in dev since the earliest inceptions of PFPX...

Autorouters work wonders, except when they dont. PFPX doesnt do anything different from an autorouting respect that professional flight planning systems dont do. I've seen crazy ass routings in real world flight planning systems as well when you let it autoroute.

Thats why I, at my airline, rarely let the thing autoroute - I'll let it do something oceanic, but, overland (and especially over the US), I'll do the routing...

And how do you do the route yourself? Does prpx simulates this way? I imagine a thing like skyvector where you have the great circle line and drsg the route along the airways

[dz111 11]

Look at the map view with the great circle route on it and type out suitable airways that you see near it. I normally do it progressively since every time you have a DCT segment, that segment will also be a great circle between the two points.

[becas 53]

Look at the map view with the great circle route on it and type out suitable airways that you see near it. I normally do it progressively since every time you have a DCT segment, that segment will also be a great circle between the two points.

That makes sense hehe Thank you!