Okay, before I pull my hair out, someone (I beg you) please help me!

 

I have the FMC 90% mastered (for the most part)--I can set it up and appreciate its functionality. But, my issue comes with the mix of SIDs/STARs ... I've used Flightaware for routes. Let's, for example, use MCO-->ATL.

Flightaware suggests: ENDED5 CTY HONIE8. A SID-transition-and STAR, correct? But I always end up with some sort of discontinuity, or vector near the end that leaves me stranded. So, I used the free trial of FS Commander, and with their maps I was able to create this: KMCO JAG4. DBN CANUK1. DBN OSTRR KATL.

From the mapping etc. on FS Commander, this set me up perfectly for 08L at ATL. The OSTRR was a 'transition' that led right to the ILS feather. But, without paying for FS Commander-how can I insert this into the FMC? Do I select the SID? Then the DBN (or CTY) trans-then the STAR? And fill in-between? I'm dumbfounded and clueless here. If I try to insert those 5 points manually, it doesn't 'take', and what goes in To & Via? Is there just some foolproof way to set up a route? Where it leads right into the ILS feather? Or how to decide which runway coincides with each STAR? I have too many questions and probably sound like a babbling idiot. Please, how on earth do I set up a route???

 

Many, many thanks if you had the patience to read that brutal mess.

Well, really all you need to do (or at least what is what I do) is select ENDED5 with the CTY transition out, then go right to the STAR page and pick HONIE8 with the CTY transition in. If you get discontinuities, just clear them out of the flightplan.

We all had issues going up the learning curve, part of the thrill!

First of all very few people actually fly the full STAR all the way down to the FAF. There are usually vectors involved at some point, especially at a busy airport. Don't think you're doing something wrong if you cannot connect the route and having to use Heading Select.

 

The CANUK1 STAR plate states that arrivals to all runways will end with radar vectors, either at WOTRA, HESPI or ZAMAS. A route discontinuity to OSTRR should be expected while under radar vectors.

 

Or how to decide which runway coincides with each STAR?

 

Look at the plates. Didn't the FAA used to have them for free on the internet a while ago?

Okay. I'm going to give it another shot. And correction up there, it was Tampa-not Orlando. Fingers crossed..

I'm not sure I understand your problem well, as it's the morning and I'm still buzzed from waking up, but..

 

I understand you have a problem with discontinuities?

 

Like this?

 

WUR

PSA

_____

DF262

 

If so, just press the left key next to DF262 and then press the one left of the empty space, it should have filled the discontinuity. Same for (VECTORS) just treat them as empty spaces.

 

Hope this was your problem.

I'm not sure I understand your problem well, as it's the morning and I'm still buzzed from waking up, but..

 

I understand you have a problem with discontinuities?

 

Like this?

 

WUR

PSA

_____

DF262

 

If so, just press the left key next to DF262 and then press the one left of the empty space, it should have filled the discontinuity. Same for (VECTORS) just treat them as empty spaces.

 

Hope this was your problem.

 

On a side note, that's awesome that you're just waking up--meanwhile I'm getting ready for bed!

Thanks for the response. I know I have read and seen this before about 'clearing' the discontinuity. Will def try once I wake up...LOL!

I could help you, but explaining the FMC over text is harder than it sounds. If it has Vectors on the STAR it means it's up to you to vector yourself if no ATC is available. It's because that's the way it is in the real world. You can close "Route Discontinuity" easily in the LEGS page. Many tutorials out there, also probably in the PMDG tutorials themselves.

 

The FMC is complex at first, but once you get it, you'll get it forever. I had all these problems at first. Now my flow around the FMC is flawless! ;-)

Note that few STARs end at the Final approach, most of them include vectors at some point. If they do there is no straight-forward way to get a continuous route to the final approach, simply because the system isn't designed to let you do that. You're supposed to get vectors.

 

 

Also be carefull when deleting discontinuities, I'm not saying it's wrong to do so but they are there for a reason and you should always understand that reason before deleting them (I leave most of mine as they're supposed to be there, most of the time they appear since I'm supposed to be vectored).

Okay. That all makes sense then. It leaves me with more questions: can I use my FMC route in conjunction with FSX ATC? Where it would let me follow my SIDs/STARs, and then vector me in? Or just stick to doing it manually?

I can't answer that because I haven't used FSX ATC in years, from what I remember though it is absolutely useless.

 

What I would do is sign up for online flying, it's what I did years ago and I've never looked back, check out www.vatsim.net

 

Or if online flight isn't your cup of tea then maybe a program such as VOXatc or radar contact would be something for you? I can't comment on how good they are though since I've never used them but I've heard they're a lot better than fsx default ATC.

There has to be a way to manually import the FS Commander route. Because that lead me right to FAF

There has to be a way to manually import the FS Commander route. Because that lead me right to FAF

 

You're fighting a losing battle trying to use realistic routes with FSX's ATC. Even if you put the waypoints in, it's still going to give you bad vectors at the end of the STAR and inappropriate altitudes.

 

On a different note, I'd stop using route builders in favor of real routes off of FlightAware until you get a grasp of how routing works. Route builders have varying levels of inaccuracy.

 

There's a lot more to routes than I'm going to write here, but the gist of it is that SIDs bring you from the vicinity of the airport to your route. The route brings you towards your destination. The STAR takes you from your route to the vicinity of the airport. From there ATC normally vectors you to the field. While there are some SID/Route/STAR combinations that bring you from runway to runway, in the United States, you don't often see these. Dulles Airport (IAD) is a good example, along with the airports in and around NYC.

 

SIDs and STARs are developed to place people onto, or take people off of frequently-used routes, so unless you know what those routes are, trying to build your own routes will be like trying to find a needle in a haystack with the lights off.

 

As I mentioned before, use a site like FlightAware to see what the real guys and gals are doing, and mirror that until it starts to make sense. From there, you'll get a feel for how it works and can start doing it on your own.

There has to be a way to manually import the FS Commander route. Because that lead me right to FAF

 

Kyle has posted an excellent answer above, I just have to comment quickly.

 

Not there is no reason for there to be a way to import an FS Commander route (I don't actually know if there is or not, just saying there doesn't have to be a way).

 

The NGX is modelled around the real world system, in your case you want to bend the entire ATC system, not the NGX. In other words it's not a problem with the FMC or the PMDG product, it's your expectation of what the RW system the NGX is modelled around will do that is the source of the problem.

 

Just my thoughts on the issue, but I felt it had to be said

Your "problem" is normal and not a problem.

 

Like already said, just clear it up. US procedures often involve vectors to the final approach course - hence the discon. European procedures have a lot less of that.

Not really, there are tons of airports in Europe that have vectored arrival procedures.