Requesting help with building an approach

[Boeing_Driver 76]

Hi,

I've been working on constructing some RNP-like approaches for the 737 NGX.

After experimenting around, I was able to successfully modify an existing approach by placing additional fixes in it (I also used ADEX to create the fixes for the airport file in the sim), but when I went to create an entirely new approach (RNVV26), I get the following error message on the FMC

 

LN:18 ERR at FIXES 

 

Having gone over it a million times, I can't see where I've gone wrong but maybe some one here savvier than I am can see it. 

Here is the relevant airport file;

 

//PAJN (JUNEAU INTL)
//Worldwide Navigation Database
//Exported via DFD v1.0 18.1006
//Software copyright (c) 2018 Richard Stefan, NAVData-Service
//Support available via forum at http://forum.navigraph.com
//
//Data provided by Navigraph - www.navigraph.com
//Source data copyright (c) 2018 Jeppesen
//This data may be used for ground based recreational computer game
//simulation software only, and may not be recompiled, interpreted,
//or distributed for any purpose without the written consent of Navigraph.
//The contents of this database is dated and must not be used for real
//world navigation as it is unlawful and unsafe to do so.
//
//------------------------------------------------------
//AIRAC Cycle : 1812 (08/NOV/2018 - 05/DEC/2018) - Ver.1
//------------------------------------------------------
FIXES
FIX ASORT LATLON N 58 21.760834 W 135 49.2535
FIX BARLO LATLON N 58 21.627334 W 134 53.354666
FIX BERGS LATLON N 58 31.1575 W 136 18.4375
FIX CFFJW LATLON N 58 21.7145 W 135 17.332333
FIX CGLNB LATLON N 58 21.5595 W 134 41.967
FIX CHILL LATLON N 58 36.902 W 135 19.8245
FIX CINGA LATLON N 58 21.99 W 134 39.52
FIX CUSHI LATLON N 58 21.7285 W 135 27.306334
FIX CUSOV LATLON N 58 26.563667 W 135 18.1185
FIX DENIS LATLON N 58 21.44 W 134 36.38
FIX DIBOL LATLON N 58 21.7025 W 135 12.34
FIX EEFNB LATLON N 58 10.258 W 135 15.475
FIX FAF26 LATLON N 58 15.47 W 134 21.49
FIX FOVBI LATLON N 58 41.130334 W 135 48.0415
FIX GASTI LATLON N 58 18.50 W 134 26.27 
FIX GUMLE LATLON N 58 35.3115 W 135 2.974333
FIX IAF26 LATLON N 58 08.15 W 134 07.88
FIX JIKUN LATLON N 58 21.730333 W 135 35.120167
FIX LACEG LATLON N 58 32.438666 W 135 38.657167
FIX LEMON LATLON N 58 20.07 W 134 28.51
FIX LVD LATLON N 56 28.0625 W 133 4.986833
FIX LYNNS LATLON N 58 21.677833 W 135 4.747333
FIX MAP26 LATLON N 58 20.90 W 134 31.61
FIX MARMN LATLON N 58 11.57 W 134 13.19
FIX MENAE LATLON N 58 21.4385 W 134 51.038333
FIX MILAN LATLON N 58 21.63 W 134 37.94
FIX MOLRE LATLON N 58 21.468667 W 134 39.976667
FIX MUGGZ LATLON N 58 31.381834 W 135 2.307167
FIX NAMSE LATLON N 58 21.45 W 134 47.00
FIX NIMLE LATLON N 58 13.6025 W 135 3.092666
FIX OGEME LATLON N 58 21.4 W 135 0.5285
FIX PI001 LATLON N 58 21.736025 W 135 11.418748
FIX PI002 LATLON N 58 18.74674 W 135 17.307268
FIX PI003 LATLON N 58 21.828757 W 135 23.809414
FIX RADKY LATLON N 58 8.0065 W 134 29.9255
FIX SQMNB LATLON N 56 27.874834 W 133 5.8425
FIX SSR LATLON N 58 10.659667 W 135 15.531833
FIX TIDAL LATLON N 58 20.68 W 134 29.94
FIX ZULIL LATLON N 58 21.533333 W 134 41.975666
ENDFIXES

RNWS
RNW 08
RNW 26
ENDRNWS

SIDS
SID ASORT2
 RNW 08 TRK 085 UNTIL 430 TURN RIGHT DIRECT FIX CGLNB AT OR ABOVE 1000 FIX BARLO FIX LYNNS FIX CUSHI AT OR ABOVE 10000 FIX ASORT
 RNW 26 TRK 265 UNTIL 430 FIX CGLNB FIX BARLO FIX LYNNS FIX CUSHI AT OR ABOVE 10000 FIX ASORT
SID JNU5 FIX BARLO
 RNW 08 TRK 085 UNTIL 430 TURN RIGHT DIRECT FIX CGLNB AT OR ABOVE 1000
 RNW 26 TRK 265 UNTIL 430 FIX CGLNB
  TRANSITION EEF FIX EEFNB
  TRANSITION LVD HDG 140 INTERCEPT RADIAL 076 TO FIX RADKY FIX RADKY FIX SQMNB FIX LVD
  TRANSITION SQM HDG 140 INTERCEPT RADIAL 076 TO FIX RADKY FIX RADKY FIX SQMNB
  TRANSITION SSR FIX SSR
ENDSIDS

APPROACHES
APPROACH RNVT08 FIX LYNNS AT OR ABOVE 5600 FIX BARLO 3500 FIX OVERFLY ZULIL 1273 RNW 08 TURN RIGHT DIRECT FIX BARLO AT OR ABOVE 2800 FIX OVERFLY SSR AT OR ABOVE 5400 HOLD AT FIX SSR RIGHT TURN INBOUNDCOURSE 347 LEGDIST 5
 TRANSITION ASORT FIX ASORT FIX DIBOL AT OR ABOVE 6300
 TRANSITION CHILL FIX CHILL FIX CUSOV AT OR ABOVE 7500 FIX DIBOL AT OR ABOVE 6300
 TRANSITION SSR FIX SSR

APPROACH RNVV08 FIX OGEME AT OR ABOVE 3400 FIX MENAE 2700 FIX NAMSE 2000 FIX MOLRE 1000 FIX MILAN 600 FIX OVERFLY DENIS 375 RNW 08 TURN LEFT DIRECT FIX MUGGZ FIX OVERFLY CHILL AT OR ABOVE 9000 HOLD AT FIX CHILL LEFT TURN INBOUNDCOURSE 155 LEGDIST 7
 TRANSITION EEF FIX EEFNB FIX CHILL AT OR ABOVE 7500 FIX GUMLE AT OR ABOVE 7500
 TRANSITION SSR FIX SSR FIX NIMLE AT OR ABOVE 3400

APPROACH LDAX08 FIX LYNNS AT OR ABOVE 5600 FIX BARLO 3700 FIX CGLNB 1347 RNW 08 HDG 310 INTERCEPT RADIAL 251 TO FIX BARLO FIX OVERFLY BARLO FIX SSR AT OR ABOVE 5600 HOLD AT FIX SSR RIGHT TURN INBOUNDCOURSE 347 LEGTIME 1
 TRANSITION BERGS FIX BERGS FIX SSR AT OR ABOVE 7000 TRK 007 UNTIL 8.4 FROM FIX SSR
 TRANSITION CGL FIX CGLNB FIX LYNNS AT OR ABOVE 7000 FIX PI001 AT OR ABOVE 6300 SPEED 210 FIX OVERFLY PI002 AT OR ABOVE 6300 SPEED 210 FIX PI003 AT OR ABOVE 6300 SPEED 210 FIX DIBOL AT OR ABOVE 6300
 TRANSITION EEF FIX EEFNB AT OR ABOVE 5600 TRK 006 UNTIL 8.8 FROM FIX EEFNB

APPROACH LDAZ08 FIX LYNNS AT OR ABOVE 5600 FIX BARLO 3500 FIX CGLNB 1276 RNW 08 HDG 280 INTERCEPT RADIAL 251 TO FIX BARLO FIX OVERFLY BARLO AT OR ABOVE 3000 FIX SSR AT OR ABOVE 5600 HOLD AT FIX SSR RIGHT TURN INBOUNDCOURSE 347 LEGTIME 1
 TRANSITION BERGS FIX BERGS FIX ASORT AT OR ABOVE 10000 FIX JIKUN AT OR ABOVE 10000 FIX CUSHI AT OR ABOVE 9000 FIX DIBOL AT OR ABOVE 6300
 TRANSITION CGL FIX CGLNB FIX LYNNS AT OR ABOVE 7000 FIX PI001 AT OR ABOVE 6300 SPEED 210 FIX OVERFLY PI002 AT OR ABOVE 6300 SPEED 210 FIX PI003 AT OR ABOVE 6300 SPEED 210
 TRANSITION CHILL FIX CHILL FIX CUSOV AT OR ABOVE 7500 FIX CFFJW AT OR ABOVE 6300 FIX DIBOL AT OR ABOVE 6300
 TRANSITION CUSHI FIX CUSHI FIX DIBOL AT OR ABOVE 6300
 TRANSITION DIBOL FIX DIBOL
 TRANSITION EEF FIX EEFNB AT OR ABOVE 5600 TRK 006 UNTIL 8.8 FROM FIX EEFNB
 TRANSITION FOVBI FIX FOVBI FIX LACEG AT OR ABOVE 15000 FIX CUSHI AT OR ABOVE 9000 FIX DIBOL AT OR ABOVE 6300
 TRANSITION SSR FIX SSR AT OR ABOVE 5600 TRK 007 UNTIL 8.4 FROM FIX SSR

APPROACH RNVV26 FIX IAF26 AT OR ABOVE 5000 FIX MARMN 4000 FIX FAF26 2700 FIX GASTI 1800 FIX LEMON 1000 FIX TIDAL 750 FIX OVERFLY MAP26 500 RNW 26 TURN LEFT DIRECT FIX LYNNS HOLD AT FIX OVERFLY LYNNS AT OR ABOVE 5000 LEFT TURN INBOUNDCOURSE 290 LEGDIST 4
 TRANSITION IAF26 FIX IAF26 AT OR ABOVE 5000
ENDAPPROACHES
 

 

[scandinavian13 5,192]

Look at another existing approach file in the navdata folder and compare. That, or look up Dan Downs' guide in the AVSIM file library.

[downscc 1,327]

17 hours ago, XLS_DRiver said:

APPROACH RNVV26 FIX IAF26 AT OR ABOVE 5000 FIX MARMN 4000 FIX FAF26 2700 FIX GASTI 1800 FIX LEMON 1000 FIX TIDAL 750 FIX OVERFLY MAP26 500 RNW 26 TURN LEFT DIRECT FIX LYNNS HOLD AT FIX OVERFLY LYNNS AT OR ABOVE 5000 LEFT TURN INBOUNDCOURSE 290 LEGDIST 4
 TRANSITION IAF26 FIX IAF26 AT OR ABOVE 5000

I think your transition is the error.  In this case since IAF26 is the IAF and there are no other fixes used as an IAF the transition is redundant is the parser is probably throwing the FIXES error because of it.  At least try it with it remarked out and see if it works.

[Stearmandriver 2,274]

As Kyle said.  I've built several of these, into JNU and other Southeast airports, and it was a fun but sometimes frustrating exercise.  Syntax is critical.  Without comparing your file to another, the only idea that comes to mind is that your fixes are defined to varying levels of precision.  I thought fix coords in a default file were all defined to the same number of decimal points.  Maybe I'm remembering wrong, but take a look. 

 

EDIT: Dan's idea is good too. 

[scandinavian13 5,192]

2 minutes ago, Stearmandriver said:

Maybe I'm remembering wrong, but take a look. 

Yeah, I thought at least one of the files needed to be fixed width...I wasn't sure though...

[Boeing_Driver 76]

So I tried eliminating this entire line:

 TRANSITION IAF26 FIX IAF26 AT OR ABOVE 5000

But still got the same error message. :o/

I'm pretty sure the fixes themselves are accurate, as I've double checked them. Also, my modified RNVV08 approach works with the additional fixes I've added...

 

[downscc 1,327]

15 minutes ago, Stearmandriver said:

Without comparing your file to another, the only idea that comes to mind is that your fixes are defined to varying levels of precision.  I thought fix coords in a default file were all defined to the same number of decimal points.  Maybe I'm remembering wrong, but take a look.

I've used all manner of precision with those Lat/Lon values... makes no difference.

4 minutes ago, XLS_DRiver said:

I'm pretty sure the fixes themselves are accurate, as I've double checked them. Also, my modified RNVV08 approach works with the additional fixes I've added...

Agree... I looked real close and do not see a FIX declaration error.  You don't need to delete a line, just insert //  and all else on that line is ignored by the parser.  I use this to troubleshoot.  First I would rem out the RNVV26 approach and verify there is no error to make sure I'm looking in the right place.  Check fix spelling to make sure it is the same in the declaration and the procedure.  Rem out the missed approach segment.  Please post what you find... I'm interested.

The FIX errors can come from anyplace in the file.

[Boeing_Driver 76]

Okay--First--thank you everyone for offering their suggestions.

Using Downscc's point of putting '//" before a line, I took everything out, including the fixes, and then one by one, began putting them back in until I got another error message.

I ended up removing the Missed Approach dialogue and the transition line which makes the approach functional now.

 

I'm not sure why the wording of those two lines doesn't seem to be working but as long as I can fly the approach in the sim, it's not a big deal.

[HiFly 16]

On 11/20/2018 at 6:58 PM, XLS_DRiver said:

Hi,

I've been working on constructing some RNP-like approaches for the 737 NGX.

After experimenting around, I was able to successfully modify an existing approach by placing additional fixes in it (I also used ADEX to create the fixes for the airport file in the sim), but when I went to create an entirely new approach (RNVV26), I get the following error message on the FMC

 

LN:18 ERR at FIXES 

 

Having gone over it a million times, I can't see where I've gone wrong but maybe some one here savvier than I am can see it. 

Here is the relevant airport file;

 

//PAJN (JUNEAU INTL)
//Worldwide Navigation Database
//Exported via DFD v1.0 18.1006
//Software copyright (c) 2018 Richard Stefan, NAVData-Service
//Support available via forum at http://forum.navigraph.com
//
//Data provided by Navigraph - www.navigraph.com
//Source data copyright (c) 2018 Jeppesen
//This data may be used for ground based recreational computer game
//simulation software only, and may not be recompiled, interpreted,
//or distributed for any purpose without the written consent of Navigraph.
//The contents of this database is dated and must not be used for real
//world navigation as it is unlawful and unsafe to do so.
//
//------------------------------------------------------
//AIRAC Cycle : 1812 (08/NOV/2018 - 05/DEC/2018) - Ver.1
//------------------------------------------------------
FIXES
FIX ASORT LATLON N 58 21.760834 W 135 49.2535
FIX BARLO LATLON N 58 21.627334 W 134 53.354666
FIX BERGS LATLON N 58 31.1575 W 136 18.4375
FIX CFFJW LATLON N 58 21.7145 W 135 17.332333
FIX CGLNB LATLON N 58 21.5595 W 134 41.967
FIX CHILL LATLON N 58 36.902 W 135 19.8245
FIX CINGA LATLON N 58 21.99 W 134 39.52
FIX CUSHI LATLON N 58 21.7285 W 135 27.306334
FIX CUSOV LATLON N 58 26.563667 W 135 18.1185
FIX DENIS LATLON N 58 21.44 W 134 36.38
FIX DIBOL LATLON N 58 21.7025 W 135 12.34
FIX EEFNB LATLON N 58 10.258 W 135 15.475
FIX FAF26 LATLON N 58 15.47 W 134 21.49
FIX FOVBI LATLON N 58 41.130334 W 135 48.0415
FIX GASTI LATLON N 58 18.50 W 134 26.27 
FIX GUMLE LATLON N 58 35.3115 W 135 2.974333
FIX IAF26 LATLON N 58 08.15 W 134 07.88
FIX JIKUN LATLON N 58 21.730333 W 135 35.120167
FIX LACEG LATLON N 58 32.438666 W 135 38.657167
FIX LEMON LATLON N 58 20.07 W 134 28.51
FIX LVD LATLON N 56 28.0625 W 133 4.986833
FIX LYNNS LATLON N 58 21.677833 W 135 4.747333
FIX MAP26 LATLON N 58 20.90 W 134 31.61
FIX MARMN LATLON N 58 11.57 W 134 13.19
FIX MENAE LATLON N 58 21.4385 W 134 51.038333
FIX MILAN LATLON N 58 21.63 W 134 37.94
FIX MOLRE LATLON N 58 21.468667 W 134 39.976667
FIX MUGGZ LATLON N 58 31.381834 W 135 2.307167
FIX NAMSE LATLON N 58 21.45 W 134 47.00
FIX NIMLE LATLON N 58 13.6025 W 135 3.092666
FIX OGEME LATLON N 58 21.4 W 135 0.5285
FIX PI001 LATLON N 58 21.736025 W 135 11.418748
FIX PI002 LATLON N 58 18.74674 W 135 17.307268
FIX PI003 LATLON N 58 21.828757 W 135 23.809414
FIX RADKY LATLON N 58 8.0065 W 134 29.9255
FIX SQMNB LATLON N 56 27.874834 W 133 5.8425
FIX SSR LATLON N 58 10.659667 W 135 15.531833
FIX TIDAL LATLON N 58 20.68 W 134 29.94
FIX ZULIL LATLON N 58 21.533333 W 134 41.975666
ENDFIXES

RNWS
RNW 08
RNW 26
ENDRNWS

SIDS
SID ASORT2
 RNW 08 TRK 085 UNTIL 430 TURN RIGHT DIRECT FIX CGLNB AT OR ABOVE 1000 FIX BARLO FIX LYNNS FIX CUSHI AT OR ABOVE 10000 FIX ASORT
 RNW 26 TRK 265 UNTIL 430 FIX CGLNB FIX BARLO FIX LYNNS FIX CUSHI AT OR ABOVE 10000 FIX ASORT
SID JNU5 FIX BARLO
 RNW 08 TRK 085 UNTIL 430 TURN RIGHT DIRECT FIX CGLNB AT OR ABOVE 1000
 RNW 26 TRK 265 UNTIL 430 FIX CGLNB
  TRANSITION EEF FIX EEFNB
  TRANSITION LVD HDG 140 INTERCEPT RADIAL 076 TO FIX RADKY FIX RADKY FIX SQMNB FIX LVD
  TRANSITION SQM HDG 140 INTERCEPT RADIAL 076 TO FIX RADKY FIX RADKY FIX SQMNB
  TRANSITION SSR FIX SSR
ENDSIDS

APPROACHES
APPROACH RNVT08 FIX LYNNS AT OR ABOVE 5600 FIX BARLO 3500 FIX OVERFLY ZULIL 1273 RNW 08 TURN RIGHT DIRECT FIX BARLO AT OR ABOVE 2800 FIX OVERFLY SSR AT OR ABOVE 5400 HOLD AT FIX SSR RIGHT TURN INBOUNDCOURSE 347 LEGDIST 5
 TRANSITION ASORT FIX ASORT FIX DIBOL AT OR ABOVE 6300
 TRANSITION CHILL FIX CHILL FIX CUSOV AT OR ABOVE 7500 FIX DIBOL AT OR ABOVE 6300
 TRANSITION SSR FIX SSR

APPROACH RNVV08 FIX OGEME AT OR ABOVE 3400 FIX MENAE 2700 FIX NAMSE 2000 FIX MOLRE 1000 FIX MILAN 600 FIX OVERFLY DENIS 375 RNW 08 TURN LEFT DIRECT FIX MUGGZ FIX OVERFLY CHILL AT OR ABOVE 9000 HOLD AT FIX CHILL LEFT TURN INBOUNDCOURSE 155 LEGDIST 7
 TRANSITION EEF FIX EEFNB FIX CHILL AT OR ABOVE 7500 FIX GUMLE AT OR ABOVE 7500
 TRANSITION SSR FIX SSR FIX NIMLE AT OR ABOVE 3400

APPROACH LDAX08 FIX LYNNS AT OR ABOVE 5600 FIX BARLO 3700 FIX CGLNB 1347 RNW 08 HDG 310 INTERCEPT RADIAL 251 TO FIX BARLO FIX OVERFLY BARLO FIX SSR AT OR ABOVE 5600 HOLD AT FIX SSR RIGHT TURN INBOUNDCOURSE 347 LEGTIME 1
 TRANSITION BERGS FIX BERGS FIX SSR AT OR ABOVE 7000 TRK 007 UNTIL 8.4 FROM FIX SSR
 TRANSITION CGL FIX CGLNB FIX LYNNS AT OR ABOVE 7000 FIX PI001 AT OR ABOVE 6300 SPEED 210 FIX OVERFLY PI002 AT OR ABOVE 6300 SPEED 210 FIX PI003 AT OR ABOVE 6300 SPEED 210 FIX DIBOL AT OR ABOVE 6300
 TRANSITION EEF FIX EEFNB AT OR ABOVE 5600 TRK 006 UNTIL 8.8 FROM FIX EEFNB

APPROACH LDAZ08 FIX LYNNS AT OR ABOVE 5600 FIX BARLO 3500 FIX CGLNB 1276 RNW 08 HDG 280 INTERCEPT RADIAL 251 TO FIX BARLO FIX OVERFLY BARLO AT OR ABOVE 3000 FIX SSR AT OR ABOVE 5600 HOLD AT FIX SSR RIGHT TURN INBOUNDCOURSE 347 LEGTIME 1
 TRANSITION BERGS FIX BERGS FIX ASORT AT OR ABOVE 10000 FIX JIKUN AT OR ABOVE 10000 FIX CUSHI AT OR ABOVE 9000 FIX DIBOL AT OR ABOVE 6300
 TRANSITION CGL FIX CGLNB FIX LYNNS AT OR ABOVE 7000 FIX PI001 AT OR ABOVE 6300 SPEED 210 FIX OVERFLY PI002 AT OR ABOVE 6300 SPEED 210 FIX PI003 AT OR ABOVE 6300 SPEED 210
 TRANSITION CHILL FIX CHILL FIX CUSOV AT OR ABOVE 7500 FIX CFFJW AT OR ABOVE 6300 FIX DIBOL AT OR ABOVE 6300
 TRANSITION CUSHI FIX CUSHI FIX DIBOL AT OR ABOVE 6300
 TRANSITION DIBOL FIX DIBOL
 TRANSITION EEF FIX EEFNB AT OR ABOVE 5600 TRK 006 UNTIL 8.8 FROM FIX EEFNB
 TRANSITION FOVBI FIX FOVBI FIX LACEG AT OR ABOVE 15000 FIX CUSHI AT OR ABOVE 9000 FIX DIBOL AT OR ABOVE 6300
 TRANSITION SSR FIX SSR AT OR ABOVE 5600 TRK 007 UNTIL 8.4 FROM FIX SSR

APPROACH RNVV26 FIX IAF26 AT OR ABOVE 5000 FIX MARMN 4000 FIX FAF26 2700 FIX GASTI 1800 FIX LEMON 1000 FIX TIDAL 750 FIX OVERFLY MAP26 500 RNW 26 TURN LEFT DIRECT FIX LYNNS HOLD AT FIX OVERFLY LYNNS AT OR ABOVE 5000 LEFT TURN INBOUNDCOURSE 290 LEGDIST 4
 TRANSITION IAF26 FIX IAF26 AT OR ABOVE 5000
ENDAPPROACHES
 

 

 

[HiFly 16]

Sorry about the previous post. I had a power failure before I could construct my comments.  Let's try again.  Your syntax for the missed portion of your approach sequence implies that you want to hold at a fix named "overfly".  Of course that is not what you mean.  What you need to construct is:  HOLD AT FIX LYNNS AT OR ABOVE 5000...  The word OVERFLY is totally unnecessary.  It would have to be constructed as a separate command and again followed by the fix name (LYNNS).  I construct these occasionally and sometimes I have to leave it for a day and come back before I can spot my error.  Hope this observation helps. 

14 minutes ago, HiFly said:

 

Craig

[downscc 1,327]

I looked at that OVERFLY too but only the first one.. and wondered why. I think the second one is the buzz kill and agree with Craig.

You generally do not use OVERFLY unless you want inhibit FLYBY for specific reasons, such as fly a heading until passing a fix then change heading but these cases are infrequent. 

Dang Craig... your eyes are younger than mine.  XLS DRIVER you should be posting your full name on all posts.... I want to thank you for using the rem-out method to isolate the problem I only wish I would have suggested remming out the missed approach first LOL.

[HiFly 16]

Hi Dan!

 

    FYI:   Putting the word "overfly" where the OP did caused a FIX error because the compiler thought that the word represented the name of a fix and it could not be found in his list of fixes.  

 

Craig

[downscc 1,327]

4 hours ago, HiFly said:

Hi Dan!

 

    FYI:   Putting the word "overfly" where the OP did caused a FIX error because the compiler thought that the word represented the name of a fix and it could not be found in his list of fixes.  

 

Craig

OVERFLY is a valid key word and can be used such as NAVAID OVERFLY LAX or FIX OVERFLY NOEND.  I think the glitch was using with with the HOLD keyword.  In practice one does not need to fly over the hold fix on entering the holding pattern.

Edited November 22, 2018 by downscc

[HiFly 16]

That is true.  It is a redundancy. But the error was ERROR AT FIXES which has always indicated something amiss with one of the fixes being called for a procedure.  OVERFLY is indeed a valid action but the compiler needs a related fix to be inserted after each action.  The error occurs after the expression HOLD AT FIX.  The syntax requires that the next word be the name of a fix so it interprets it that way.  We know that it refers to LYNNS since LYNNs was the object of the preceding action but the compiler is not that sophisticated.  It sees that word OVERFLY and, because it immediately follows the action HOLD AT FIX. it is interpreted as the name of a fix.  Of course since no fix by that name has been predefined for that airport the compiler grinds to a halt and generates the error message.  What is the error?  The name of the fix needs to be inserted after the expression HOLD AT FIX (the compiler says, "what fix?") and the answer should be LYNNS. So the correction would be HOLD AT FIX LYNNS and then the parameters of the hold should be inserted.  If indeed the OP wants to overfly the fix, it obviously would be done before entering the hold so the expression would be OVERLY LYNNS HOLD AT FIX LYNNS AT OR ABOVE 5000 LEFT TURN INBOUNDCOURSE 290 LEGDIST 4.  Now I really don't know if the compiler can make sense of an overly and then a hold but syntax wise it should compile.  Notice that LYNNS has to be mentioned after each action that relates to it or the compiler has a conniption fit.  Hope that adds more clarity than confusion!

 

Craig

Edited November 23, 2018 by HiFly

[downscc 1,327]

16 hours ago, HiFly said:

The error occurs after the expression HOLD AT FIX.

 

17 hours ago, downscc said:

I think the glitch was using with with the HOLD keyword. 

We agree.