OnCourse Software

Welcome to our Product Support Forums

Traffic Control and Co-pilot reporting wrong altitude.

PLEASE NOTE:

If you are reporting an issue with PF3 please remember to Zip and attach the Debug_Monitor.log file from your PF3\Logs folder. Thank you.

Post Reply   Page 2 of 2  [ 17 posts ]
Jump to page « 1 2
Author Message
vololiberista
Post subject: Re: Traffic Control and Co-pilot reporting wrong altitude.
Posted: Sat Dec 10, 2016 9:53 am
Offline
 
Posts: 980
Joined: Wed May 27, 2009 8:41 pm
Location: LIMZ
 
A good example of a flight plan that will never be "generated". BA when flying from Gatwick EGKK to Turin LIMF often have to fly via Zurich. For reason of traffic, time of day and French ATC strikes (which are all too frequent!). You could for instance create a fpl just to Zurich and then another to Turin. But even that would be wrong. Firstly the route to Zurich would be too far to the West. The second point and perhaps more important is that there is no direct airway to Turin from Zurich. Which means that a large part of that leg is off airway. This illustrates my point that generated fpls should never be taken as read. In the sim world perhaps some would say that it doesn't matter. But it does in the sense that it is unreal and inaccurate. It takes very little intuition really to think that a specificly generated fpl doesn't look right. Especially if it seems to take you for a tour round the houses.
Always check the fpl and see if it has any strange dog legs especially over significant water (where the rule is direct great circle). It is quite in order and normal to fly between airways ie. off-airway. You would in real life be asked to report crossing various waypoints. This is not yet a feature in PF3 but has been earmarked for consideration.
Key points to look for. Does it follow airways in the correct direction? Is it more or less direct? If not plan to go direct to the next wypt instead. How far away is the last wypt from the destination? You may need to add a wypt or two in order to take you to the relevant STAR. Another point to consider for complete accuracy would be whether the fpl overflies prohibited airspace and/or if there are altitude restrictions. This would be more likely on an approach leg.
Some generated fpls are very good but even so still need checking.
The addition of SIDs and STARs are another matter as they too are frequently wrong especially where more that one SID or STAR leads to the same wypt. The only way out of that is to check the airport charts carefully for local restrictions and then input the correct SID or STAR for that route.There are plenty of simmers who are deeply under the impression that only ATC issue SIDs and STARs. The is most definately not the case. The idea of a SID is to take me from a specific runway to a specific wypt. That wypt is the start of my fpl. Clearance delivery is nothing more than a confirmation that ATC and the crew are singing from the same hymn sheet. That ATC are talking to the "correct" crew. It is quite common to enter a SID as a specific part of a fpl. ATC would have to have good reason for sending you in a totally different direction especially if the flight was fuel critical. Likewise the last wypt on a fpl would be the start of a STAR to a specific runway. Usually you can programme alternative STARs into an FMC. If not PF3 allows you to route by yourself to the changed runway.
So creating a fpl is definately a black art and one reason why I don't spend money on certain programmes as I can easily do it manually and get a better more accurate result into the bargain.

_________________

[ img ]


Top
Profile Quote
JohnY
Post subject: Re: Traffic Control and Co-pilot reporting wrong altitude.
Posted: Sat Dec 10, 2016 10:43 am
Offline
 
Posts: 471
Joined: Mon Jul 18, 2016 3:42 pm
 
Ok thanks voliberista. Found that. Tried EGGD to EGBB and it gave me a straight route more or less north,north, east but crossing various routes running north eastwards.

I've obviously got to study it more to find how I can dream up a flight plan that is not a straight route and see how that joins up in Skyvector.

I think I'll be in my coffin before I learn all this, and learn how to work the bloody autopilot in Flysimware's Learjet! :roll:

All the best.

John


Top
Profile Quote
vololiberista
Post subject: Re: Traffic Control and Co-pilot reporting wrong altitude.
Posted: Sat Dec 10, 2016 4:02 pm
Offline
 
Posts: 980
Joined: Wed May 27, 2009 8:41 pm
Location: LIMZ
 
JohnY wrote:
Ok thanks voliberista. Found that. Tried EGGD to EGBB and it gave me a straight route more or less north,north, east but crossing various routes running north eastwards.

I've obviously got to study it more to find how I can dream up a flight plan that is not a straight route and see how that joins up in Skyvector.

I think I'll be in my coffin before I learn all this, and learn how to work the bloody autopilot in Flysimware's Learjet! :roll:

All the best.

John
Well yes that's a prime example of the sh one t that can be generated.
BCN DIKAS GAVGO KENET CPT DIGUT KIDLI HON
Because these programmes insist on flying airways.
Instead
POMAX GAVGO KIDLI IXURA HON would be better and also avoids Brize Norton mostly. You would normally be able to contact Brize and cross their airspace at a specified altitude. Though if you stay above FL100 you wouldn't need to as you would be above their airspace anyway.
Quote:
I've obviously got to study it more to find how I can dream up a flight plan that is not a straight route and see how that joins up in Skyvector.
Entering only the origin and destination gives you the straight line. Then enter the waypoints with a space in between, in the box below (either one by one or all together) to create the actual route. I can do it and I am not planning at least to be using a wooden box just yet!

_________________

[ img ]


Top
Profile Quote
JohnY
Post subject: Re: Traffic Control and Co-pilot reporting wrong altitude.
Posted: Sun Dec 11, 2016 11:08 am
Offline
 
Posts: 471
Joined: Mon Jul 18, 2016 3:42 pm
 
Trouble is mate I don't know the bloody waypoints! :lol:

John


Top
Profile Quote
vololiberista
Post subject: Re: Traffic Control and Co-pilot reporting wrong altitude.
Posted: Sun Dec 11, 2016 11:56 am
Offline
 
Posts: 980
Joined: Wed May 27, 2009 8:41 pm
Location: LIMZ
 
JohnY wrote:
Trouble is mate I don't know the bloody waypoints! :lol:

John
POMAX GAVGO KIDLI IXURA HON
You do now!

_________________

[ img ]


Top
Profile Quote
ThomasAH
Post subject: Re: Traffic Control and Co-pilot reporting wrong altitude.
Posted: Sun Dec 11, 2016 12:33 pm
Offline
 
Posts: 986
Joined: Tue Dec 24, 2013 12:27 pm
 
vololiberista wrote:
POMAX GAVGO KIDLI IXURA HON
These always sound like names of magic scrolls in Nethack :)

Some other examples:
JUYED AWK YACC
LEP GEX VEN ZEA
VERR YED HORRE

_________________

[ img ]


Top
Profile Quote
vololiberista
Post subject: Re: Traffic Control and Co-pilot reporting wrong altitude.
Posted: Sun Dec 11, 2016 3:58 pm
Offline
 
Posts: 980
Joined: Wed May 27, 2009 8:41 pm
Location: LIMZ
 
ThomasAH wrote:
vololiberista wrote:
POMAX GAVGO KIDLI IXURA HON
These always sound like names of magic scrolls in Nethack :)

Some other examples:
JUYED AWK YACC
LEP GEX VEN ZEA
VERR YED HORRE
Marco Ravanelli (designer of the CIVA INS) is remodelling it in XML. There are some that are protesting that it should have all the waypoints of a flightplan instead of the nine waypoints that its memory could cope with. This of course completely ignores the fact that when CIVA INA was in use waypoint fixes were few and far between. And therefore applying modern attitudes would be as unrealistic as not having it at all. Nowadays you would need a crew member just to permanently keep updating it.
Tip: As long as you are on the same airway you can do away with intervening fixes. Unless they indicate where a turn is necessary.
This point and those discussed above are one reason why all these flightplan generator programmes say "For Simulation use only." In other words they rarely represent an actual flightplan!!!!

_________________

[ img ]


Top
Profile Quote
Display: Sort by: Direction:
Post Reply   Page 2 of 2  [ 17 posts ]
Return to “PF3-ATC at its best” | Jump to page « 1 2
Jump to: