Cycle 0704 KATL STARS

[downscc 1,327]

Agreed... I misunderstood the thread. Sorry.

[vonmar 121]

Terry,Pechy is one I have flown on AVSIM.The entire STAR is expected to be loaded up to from CLUME all the way to WOTBA.Depending on the landing runway, Approach will tell you what you can expect. They can break you off the STAR whenever they want to.For example: Approach says, like when you are at SOT : Expext vectors at WOTBA ILS 8L, cross PECHY at 12000. They expect you will continue the route per the published procedure. Works great with PECHY.But, ERLIN is missing the 3 RNAV way points to accomplish the samt type of thing for a 26R. The procedure ... says continue to IGEBE but it is not in the procedure!Why is PECHY missing the three waypoints?Are you adding the VECTOR command to the STARs?

[vonmar 121]

Dan,Thanks .. just wanted to know if I was missing something.Note:I got the FAA Digital Aero. CD today.Can't wait to check it out later.I also got a full set of USA IFR ENROUTE LOW charts ... now I cansee all the RNAV waypoints for the first time. My old set was about 12 years old.

[vonmar 121]

Terry,I looked up PECHY on my new FAA CD.I see that the STAR actually starts at PECHY waypoint just like the plate (the thick black line connecting the waypoints) says it should. Everything before that are STAR transitions.Your procedure, starting it at CLUME means you do not have to program in the same waypoints (CLUME ....to ... SHANE) for each of the STAR transitions. Saves a few steps and megabytes!I also noted the duplication of waypoints in the listed waypoints for the STARS. Too bad they do it that way ... lot of duplication but I guess the idea there is to, by show the last waypoint listed, is to tell you where it is supposed to "connect" to in the next procedure.But, it (the dupe) is actually not part of the final "plate" procedure.IMO, it (the dupe) should not show up in the final procedure we use. Each waypoint in the procedure should be in the procedure only once and will link on the FMC properly when selected and loaded.

[Guest staang]

>The entire STAR is expected to be loaded up to from CLUME all>the way to WOTBA.Let me ask this then. Once you have selected the STAR do you not know what runway group you will land on IE East or West? So if you are landing to the West for example you don't need DOEVR through WOTBA loaded in. Plus there are the Lost Comm procedures to consider for all those people that do not fly on-line. They provide the closest thing to ATC guidance possible since they take the place of vectors.>For example: Approach says, like when you are at SOT : Expext>vectors at WOTBA ILS 8L, cross PECHY at 12000. They expect you>will continue the route per the published procedure. Works>great with PECHY.Sure but then you have a bunch of useless waypoints loaded if landing to the West. This is the problem I continually run into. Procedures that have vectors create all sorts of programming problems. On one hand you want as much as possible included in a procedure. On the other hand throw in vectors and one no longer can put waypoints in the procedure because there are none to add.>But, ERLIN is missing the 3 RNAV way points to accomplish the>samt type of thing for a 26R. The procedure ... says continue>to IGEBE but it is not in the procedure!>>Why is PECHY missing the three waypoints?What waypoints?>Are you adding the VECTOR command to the STARs?If required I should but without knowing specifics I have to generalize here.How about a break here. I'm losing track of what's what. Some of the things we are discussing I have fixed but not yet put up for DL. How about I fix up the procedures at KATL, put them on my site and then we can go at them again once you all DL them and test.Terry

[vonmar 121]

>The entire STAR is expected to be loaded up to from CLUME all>the way to WOTBA.Let me ask this then. Once you have selected the STAR do you notknow what runway group you will land on IE East or West? So if you are landing to the West for example you don't need DOEVR through WOTBA loaded in. Plus there are the Lost Comm proceduresto consider for all those people that do not fly on-line. They provide the closest thing to ATC guidance possible since theytake the place of vectors.****************************************************************The arrival STAR is included the the pilot's flight plan, approvedby ATC, and loaded into the FMC proir to departure. At that timeyou have no idea (for sure) what the landing runway or approachwill be at the destination airport.You just fly the filed flight plan. When you contact the destinationapproach controller he will give you the approach to be used.At that time you load the approach into the FMC and then selectthe first waypoint in the assigned approach and "overwrite" overthe first unusable waypoint in the current STAR you are flying.It is really only two steps here and the FMC is ready to fly theremainder of the assigned STAR waypoints and the assigned approach.The main point here is, the entire STAR is assumed to be flownuntil the approach controller tells you to ammend it.***************************************************************>For example: Approach says, like when you are at SOT : Expext>vectors at WOTBA ILS 8L, cross PECHY at 12000. They expect you>will continue the route per the published procedure. Works>great with PECHY.Sure but then you have a bunch of useless waypoints loaded if landing to the West. This is the problem I continually run into. Procedures that have vectors create all sorts of programmingproblems. On one hand you want as much as possible included in a procedure. On the other hand throw in vectors and one nolonger can put waypoints in the procedure because there are none to add.************************************************************Vectors are used on departure and arrival. But, they are notpart of your filed flight plan. When you depart it is normal tobe issued vectors by the departure controller to get you safelyaway from the airport. During departure vectors you are not flyingthe filed flight plan (departure procedure).At some point the controller will tell to continue your filed flight plan. At that point you may have already passed a waypiontor two in the original plan/departure procedure.So you just select the next assigned waypoint and "overwite"the obsolete FMC waypoint and go back to autopilot on GPS.Now you fly your filed flight plan until the anothercontroller gives arrival vectors. Vectors in this sensemeans the FMC plan has ended and you are being told what todo until you capture the localizer for landing.************************************************************>But, ERLIN is missing the 3 RNAV way points to accomplish the>samt type of thing for a 26R. The procedure ... says continue>to IGEBE but it is not in the procedure!>>Why is PECHY missing the three waypoints?What waypoints?************************************************************I said ERLIN by mistake, didn't I ! I was originally discussing ERLIN with missing waypoints.Now, I did not know at the time if they had been deletedfrom the FAA procedure or what? That is why I asked.I pointed out a similiar (Pechy) procedure that had thefull STAR per FAA plate.The FAA plate I was looking at for ERLIN had three morewaypoints than you procedure .. thus, my question.I had the feeling you were looking for feedback here?Now, to this minute, I am not sure that the threemissing waypoints should be there or not! When you find outand tell me then I will know for sure.I am not a programmer, I do not download FAA data andcompile it to generate procedures. The only thing I can do is fly the procedure and providewhatever feedback I see at the time.************************************************************>Are you adding the VECTOR command to the STARs?If required I should but without knowing specifics I have to generalize here.How about a break here. I'm losing track of what's what.Some of the things we are discussing I have fixed but notyet put up for DL. How about I fix up the procedures at KATL, put them on my site and then we can go at them again once you all DL them and test.********************************************************If an issue is posted and you fixed it just reply witha one worder like DONE. Then we know it will be in thenext update.When I do not hear a reply on an item then I ask again, assuming you may not have seen it. It could be fixed already, right?Anyway, no problem testing the update when it is ready.********************************************************

[Guest staang]

>Anyway, no problem testing the update when it is ready.Whoooa. I got so caught up in this conversation and correction frenzy that I overlooked a problem. I can't find any reference to the Level-D being able to do STAR runway transitions. Putting in STAR runway transitions may not be possible. I've got to verify this with a Level-D programmer in order to proceed unless some examples are around that I can read. Terry

[vonmar 121]

>Anyway, no problem testing the update when it is ready.Whoooa. I got so caught up in this conversation and correction frenzy that I overlooked a problem. I can't find any reference to the Level-D being able to do STAR runway transitions. Putting in STAR runway transitions may not be possible. I've got to verify this with a Level-D programmer in order to proceed unless some examples are around that I can read. *************************************************************You are corrent.Level-D does not do STAR runway transitions.Level-D uses standard procedures.The approach transition for whatever runway you select for landingin the FMC is "made available" for all STARS that are in yourprocedure file.If you have an approach transition in the procedure filethat connects to an approach name (RNAV26L) e.g. thenthe Level-D can use it (attach it) automatically to and STAR.The pilots selection may not be "logical" but the FMC will hook the two together on the FMC and fly it.A quick example will show you what I see on the FMC display.It will also show how the Level-D matches up the STAR with theyour approach procedures.Before departure we selected/loaded the FMC with the following:Flight plan waypoints to KATLBNA STAR transition for ERLIN2ERLIN2 STARILS 26RSMLTZ transition for ILS 26RYou can use the ERLIN TWO ARRIVAL (RNAV) plateand the ILS 26R plates for reference and follow along.(FMC selections)Phase of flight What's happening/FMC display*************** ****************************Enroute phase No problem, following waypointsDescent No problem, descent continues to first BNA transition waypoint What's displayed on the FMC display ***********************************STAR transition BNA DRAKK NEUTO RMG (duplicate here) STAR RMG ERLIN DALAS STUTZ NOFIVApproach transition SMLTZApproach FREAL BALLI AJAAY I226RM RW26RMissed approach (1400) (INTC) TROYS HOLD AT ATLYour procedure file for KATL worked perfect as programmed.Except for the duplicate waypoint.And, except for the fact it did not follow the FAAERLIN2 STAR .. assuming there have been no changesto it that I do not know about.Now, what is missing from the the FMC display?These three RNAV waypoints.FANEWHAVADIGEBEIf it looked like the following it would be perfectexcept for the duplicate waypoint.STAR transition ****** BNA DRAKK NEUTO RMG (duplicate here) STAR ***************** RMG ERLIN DALAS STUTZ NOFIV FANEW (corrected) HAVAD (corrected) IGEBE (corrected)Approach transition *** SMLTZApproach ************** FREAL BALLI AJAAY I226RM RW26RMissed approach ******* (1400) (INTC) TROYS HOLD AT ATLIf you wanted to use the Vector(s) you could.But, really not necessary.Insert the (.VEC) as part of the above procedure anywherebut leave all the waypoints in. Then. if you did not get the vector it could then be deleted from the FMC prior toreaching it in the flight plan and you would continueon the normal route.If for example the controller started giving vectorsjust prior to reaching DALAS waypoint.No, problem.That trashes all of the other waypoints up to SMLTZSo, in the Level-D, I would select SMLTZ and copy itover top of DALAS and the FMC automatically eraseseverything between DALAS and SMLTZ.The idea here is to have all of the waypoints in the procedure there and available for use. It takes notime to delete several waypoints if they are not needed but takes much more time to enter new ones.

[vonmar 121]

Hi Terry,I did a short SID from KBNA to show the lat/lon used with the .VEC command.I used BNA as the anchor point.Wrote the .VEC line command then deleted the BNA waypoint used as the anchor point.Turns out the VEC used the LAT/LON from the preceeding waypoint LENON, which is correct.The FMC will use this heading profile until the VECTOR is deleted in the FMC by the pilot, then, the FMC waypoint sequencing continues as normal.During vectors by ATC the FMC can be manually updated per ATC instructions.BNANormal36.136961-86.684772000atFly-byAutoLENONNormal36.282642 ****************** -86.199536 ************ 000atFly-byAuto********* Vectors Start **************** VECTORSVectors36.282642 ********** -86.199536 ************ 000at193Auto ************ Vectors end ************ So, you could try using any nearby LAT/LON to enter theVECTORS into your procedure.It should end up looking like the above example anyway when completed.