edit the flight plan files SID STAR

[brylka 0]

Hello,
I have the PMDG 737 NGX, PMDG 777-200LR/F, PMDG 747-400X, PMDG MD-11X
and the ifly 737 NG.

With the ifly 737 I can edit the flight plan files f.e. zbaa.FLTPLAN with a text editor (Notepad)
And i can edit the SID STAR files.

Like that I can insert conditional waypoints.
This procedure is documented in the manuals of ifly:

FlightPlan Introduction.pdf
and
Procedures Introduction.pdf

excerpt:
Line #17.6:
It is a flag which specify whether the airplane needs to fly over this waypoint.
0: No need to fly over.
1: Need to fly over.
Line #17.7:
It is a flag which stands for the property of the route associated with this waypoint.
0: Track to Fix.
1: Direct to Fix.
2: Course to Fix.
3: Arc to Fix.
4: Radius to Fix.
Line #17.8:
Heading of waypoint in degree. If the current waypoint and previous waypoint are not the condition point, the FMC
automatically calculates the heading.
If value in 17.9 is “0” and value in 17.7 is “3”, it indicates the radial when finish the leg.
If value in 17.9 is “0” and value in 17.7 is “4”, the universal data item 6 must be set.
The prefix “L” or “R” can be added to specify the direction of turn.
“L”: Turn left
“R”: Turn right
Line #17.9:
It is a flag which indicates whether this waypoint is a conditional point.
0: It is not a conditional point.
1: It is a conditional point.
Line #17.10:
It is a flag which indicates whether this waypoint needs speed constraint.
0: It does not need speed constraint.
1: It need speed constraint.


Is there also a description for the PMDG 737 NGX ?
For .rte files.
SID STAR files
Can the  PMDG 737 NGX do this:
It is a conditional point.
In the PMDG-737NGX-Tutorial-2.pdf it is written, that PMDG
is the best implementation of the CDU in the FMC.

Best Regards

Peter Brylka

[downscc 1,327]

Sure, many missed approach procedures and lots of pre-RNAV SIDs use conditional waypoints. It is much easier to edit the sidstar file than it is the .rte files. I've not found an explanation of data fields in the .rte file, and don't have the need to decompile it manually.  Enroute conditional waypoints are pretty rare..., I've never seen one.

[brylka 0]

Thank you Dan,

 

but how i can edit the sidstar files.

 

i need a explanation of data fields in the SID STAR .txt files

 

Edit with notepad.

 

SID LAM4M RNW 26L FIX OVERFLY IWW23 AT OR ABOVE 702 HDG 351 INTERCEPT RADIAL 081 TO FIX DET31 FIX DET31 FIX DET29 AT OR BELOW 4000 FIX ACORN 5000 FIX OVERFLY DET10 TURN LEFT DIRECT FIX LAM15 5000 FIX LAM10 6000 FIX LAM 6000

 

so

HDG 351 INTERCEPT RADIAL 081 TO FIX DET31

TURN LEFT DIRECT FIX LAM15 5000

 

Best Regards

Peter Brylka

[pcubine 143]

I would highlight everything after 702 and delete it. Then paste HDG 351... All of this is in the SIDSTARS Folder EHAM file SID section. To be on the safe side you might want to backup the EHAM file if something goes wrong. What is the purpose of this editing?. This edit has defeated the purpose of the SID which I would think is traffic separation both in the lateral and horizon direction.

[downscc 1,327]

 

 

i need a explanation of data fields in the SID STAR .txt files

 

Look for "Making 737NG Procedures" in the AVSIM library.  Agree with Michael, not sure what you are trying to achieve.

[Mike777 163]

 

 

HDG 351 INTERCEPT RADIAL 081 TO FIX DET31

TURN LEFT DIRECT FIX LAM15 5000

 

Hi, Peter,

 

Why can't you just do this on the CDU screen?  Just move LAM15 up so it comes after DET31.  Unless LAM15 is in some strange location relative to DET31, the aircraft will turn left to get to it.

 

Mike

[Mike777 163]

Just tried using CDU -- slightly older Airac but went from DET31 to LAM, including left turn.  BTW this is EGKK.

 

Only time I've found it necessary to program such procedures is with the old PSS 777 which didn't have real final or missed approaches. 

 

Mike

[pcubine 143]

BTW this is EGKK.

Don't know where I got the idea that this EHAM. I apologize.

[Mike777 163]

 

 

Don't know where I got the idea that this EHAM. I apologize.

 

No problem at all, Michael.  Still would like to know what the OP is trying to accomplish  -- After spending many "fun filled" (??) hours years ago editing PSS approach files, because at the end of a STAR it just threw in a couple of generic waypoints and no missed approach procedure,  I'm happy not to have to do it anymore (even though  the PMDG SIDs & STARs look much more intuitive).

 

Mike