Yup! I think this post, with it's numerous good questions and the SO perfectly-written answers by Jim and Reggie - ought to be pinned as "required reading" for all potential IMC cigar-tube jockeys!Regards,

>Yup! I think this post, with it's numerous good questions and>the SO perfectly-written answers by Jim and Reggie - ought to>be pinned as "required reading" for all potential IMC>cigar-tube jockeys!>>Regards,I second that. It is in my top five threads. Thank you Jim and Reggie.

Reggie,The only problem with using the GPS that comes with FSX is that none of the approaches offer vertical guidance. Correct?

I'm coming to this thread a little late late but would like to point out thar SuperFlightPlanner enable FS9 flight plans t be created with SIDs and STARS. (SuperFlightPlanner is freeware, has limited documentation, has some features that aren't fully implemented but remember it's free.)It incorporates quite of number of STARs and SIDs, not all of which are as accurate/up-to-date as they might be. However, the STARs and SIDs are held in a folder called dpstar with a xxxx.xml file for each airport, where xxxx is the ICAO airport code. This makes it easy to modify existing ones or create new ones by editing the .xml. Personally, I find it convenient to create variants of each STAR to include the remainder for the flight from the waypoint at the end of the STAR through the Approach Procedure/Instrument Approach Procedure to each runway. Once you've created a SID/STAR then SuperFlightPlanner lets you attach that to any subsequent flight you create using that airport. As an example, I attach my versions of the ASTRA1A STAR to EGKK (Gatwick) to runways 26 and 08 to illustrate their structure: "desription" is what appears in a drop=down list in SuperFlightPlanner when you select a SID/STAR. The other lines are self-evidentEDIT: strictly speaking the above only applies to FS9. I haven't yet got FSX.

Yes, to fly the approaches well you need to have the charts for vertical guidance.There is altitude information in the code, but it's use is limited in FS2004 - and from what I've seen also in FSX.One way it is used is for holding patterns.You select and activate an approach. Fly the approach in the NAV mode on the autopilot and have the GPS/NAV switch in the GPS position. If you are too high at a holding pattern way point, the aircraft will automatically go into a holding pattern until it descends to the correct altitude.It will then break out of the holding pattern and continue the approach.I keep coming back to this. We have to be prepared like real pilots if we want to fly 'realistically'.I've been in the jumpseat of a Challenger 604 or Gulfstream 200 for a few dozen arrivals into KADS via the FINGR THREE and JONEZ FOUR STARs and landings on Rwy 15 and Rwy 33.Every time the pilots of that KADS based jet have the approach plate for the approach they have flown over 100 times out and use it.The right seat pilot will always cross check the plates and the required or ATC assigned altitude with the waypoints. She or he always briefs the missed approach plan.Whenever possible the approach is hand flown and the landing is visual (usually they are looking for a Cessna or Piper also on approach). But they have the ILS setup, they have the missed approach ready, and they have KDAL and KTKI ready as emergency alternates.FS makes it too easy to jump in and fly. Despite the realism of the complex systems modeling in some great aircraft, FS cannot force us to do proper preparation.

SID/STARS have always been more complicated to obtain and fly, because either the navdata of the FMC/MCDU is outdated or has no information for a current SID/STAR -or- there are no downloadable plates. If either of those two are missing, it is almost impossible to fly approaches or departures.For example: European plates (on VatSim) are historically outdated and don't match up with the latest NavData from NaviGraph.As for ATC: Well, the default FSX ATC lets you "somewhat" fly SID/STARs. You can select an IAP approach and ATC just stays mute until you reach the FAF.Here is how I used to plan my flights:- Plan the route in exclusively in FSBuild, export to FSX. FSBuild can import Active Sky (I haven't tried yet with ASX) weather. The departure/arrival runway and the selection of SID/STARs is pretty accurate.- Import flight plan into Radar Contact or just use FSX ATC.- Import flight plan into FMC/MCDU- FlyPat

Very interesting, unfortunately a lot of what has been discussed applies to FS9 only. Many thanks for the useful info, good to have both FS9 and FSX installed.

I was flying into Denver (KDEN itself) and discovered that when I asked for a different approach, the only option I got was vectors to final. Is KDEN screwy like this in FSX or I did I somehow do something odd that forced to me to be vectored all over Colorado and possibly Wyoming? I don't recall doing anything I've never done before and I've never flown IFR to KDEN. And its the KDEN that comes with FSX, no sort of add-on stuff anywhere near there.