KORD has been added to my SIDSTAR collection of KATL, KBOS and KBWI. Add these to your sidstar folder after updating with Navigraph procedures, and keep for next cycle because I am following the FAA 56-day cycle (includes 28-day cycles 1202-1203)Since O'Hare only has one vectors-only departure, I've added departure procedures that mimic closely the vectored departures to 13 departure gates (fixes) including BAE, DUFEE, EBAKE, PETTY, etc. If you are using something like VATSIM you don't need this feature so the basic ORD5 departure is included.Comments/suggestions or questions are always welcome. This collection is available in the AVSIM library with detailed readme in the FS X Flight Plans section

Haven't tested it, but from looking at the KBWI, it looks like it's all in order. The NOATC is an interesting addition for the sim crowd. Inventive. I'm not sure how I feel about it, but it's inventive.

Dear Kyle-Dan has been writing SID/STARS for YEARS and I'd venture to guess no one else does it any better. Let us know how outstanding it really is once you actually fly it.

Edited February 11, 201214 yr by lasnubes

I didn't pay Carl or approve that annoucement. The noatc feature has it's fans but the original "as published" procedure is there too. KDFW is next.

LOL ;)

I had just completed my first NGX flight into KBOS and noticed the default didn't have the 33L ILS or a number of others. I was little surprised, but managed to get by. Then I come to the forum to research my options, and see this thread that includes KBOS. Installed it and everything looks top notch now. Thanks Dan for providing the exact file I needed.

Dear Kyle-Dan has been writing SID/STARS for YEARS and I'd venture to guess no one else does it any better. Let us know how outstanding it really is once you actually fly it.

I have my Navigraph stuff, so I have my RW SID/STARS all taken care of. Without flying it, though, I looked into the actual text of the files (which is where I saw the NOATC stuff), and it all looks very well done. It wasn't meant as a knock or anything. I'm just not sure how I feel about the NOATC stuff as a virtual controller (reasons below).

I didn't pay Carl or approve that annoucement. The noatc feature has it's fans but the original "as published" procedure is there too. KDFW is next.

Haha. Well you certainly have some fans. I saw all the real stuff aside from the NOATC stuff, too. It wasn't a knock so much, and I'm really not sure how I feel about it in a fully neutral way. As a pilot, when I fly without ATC, I tend to just vector myself around, so that could make it easier; as a controller on VATSIM, my worst enemies are the pilots who are a slave to the magenta line, and around here I have to do my share of "a break in the magenta line isn't the end of the world." I see why you'd put it in there, though.Either way, the work is appreciated and it looks very well done.

Edited February 13, 201214 yr by scandinavian13

Hi DanI was looking at one of these and noticed you used a "colocated" fix definition. It was my understanding that this type of fix definition does not work with the NGX. Do you know otherwise? I really could not get it to work no matter what I did, so would be interesting to find out if there are conditions under which it works.Thanks

Colocated fixes definitely work for the NGX. The Colocated fix has to be from another fix from within the sidstar file itself.

The COLOCATED fix(es) in my files are left over from a couple of years ago, I'm slowly getting rid of them and using a geodesic calculator to come up with lat/lon positions. Sure they work. I prefer the lat/lon so there is no dependency on the MSFS magnetic variations, which can vary from user to user depending on if they are updating declination. The referenced fix also needs to be before the colocated statement, or for programmers, no forward references allowed. They dropped the NAV key word which would refer to an external reference, but I rarely used that.

The COLOCATED fix(es) in my files are left over from a couple of years ago, I'm slowly getting rid of them and using a geodesic calculator to come up with lat/lon positions. Sure they work. I prefer the lat/lon so there is no dependency on the MSFS magnetic variations, which can vary from user to user depending on if they are updating declination. The referenced fix also needs to be before the colocated statement, or for programmers, no forward references allowed. They dropped the NAV key word which would refer to an external reference, but I rarely used that.

Interesting, will try that. I had tried placing the reference fix before the colocated fix lines, but it still did not work. Will have to try it again. But as you mention, the colocated reference changes when you update your magnetic variation. Had not thought about that, seems like even more reason not to use the colocated reference.

Hey, 177 downloads for the AVSIM library file. I'm back!

Edited February 16, 201214 yr by downscc

Did you by chance happen to make, the Visual Arrival into KDCA famously known as the "River Visual?" I tried to copy the waypoints off a chart but the FMC wasn't aware of all of them.

Did you by chance happen to make, the Visual Arrival into KDCA famously known as the "River Visual?" I tried to copy the waypoints off a chart but the FMC wasn't aware of all of them.

The RNAV (RNP) 19 approach is almost exactly the River Visual. I think the problem you might be having is that each waypoint referenced in a procedure at an airport needs to be identified in the FIXES section at the top of the file.

I haven't added KDCA, yet; it was in my collection that I maintained through cycle 1007, which is still in the AVSIM library. I did spend time getting the RNP arcs just right.You would not normally see a charted visual approach in the FMS; I've built them for KDCA, PANC, KSFO and a few others but I don't think I'll be keeping them since I decided that there's not much use in trying to create a visual approach that usually refers to landmarks that often don't exist in MSFS.Steve has the solution, fly the RNP approach.