Newbe here...I was receiving vectors for an approach in KATL. My position was almost on the ILS course (maybe past it) but to far out to receive. I was vectored away from the ILS. I don't rememeber if I was "cleared" for the approach but I didn't get the formal long hand-off. I flew the vector and didn't here from ATC so I did a 360 back to intercept and landed. The summary at the end didn't scold me.1) What should I have done after I was vectored away from the ILS?2) Is the answer to the above applicable in the real world or was it just a simulation problem?3) Is it legit if your are flying the approach to do 360's, within the confines of the approach plate's MSA, to get into position or to lose alt or speed? Or is your only option to declare a missed approach even if your are 10 or more out? I suppose in the real world you could ask permission from approach.

1) what i do, i wait until i'm lined up with the runway heading, and then turn to the runway heading, until i received the localizer. then i fine tune from there2) doug question3) doug question, but i seriously doubt itjd

Neub!>>1) What should I have done after I was vectored away from the ILS?<>2) Is the answer to the above applicable in the real world or was it just a simulation problem?<>3) Is it legit if your are flying the approach to do 360's, within the confines of the approach plate's MSA, to get into position or to lose alt or speed?<>Or is your only option to declare a missed approach even if your are 10 or more out?<>I suppose in the real world you could ask permission from approach.;)

I flew the route again (2nd half of the tutorial that ends at KATL) and what I discovered is that I did get a formal notice it was just that I was passed the localizer before ATC stopped speaking - or at least before I had noted the vector and altitude and acknowledged the transmission. I'm just used to FS9 ATC that does the handoff before the localizer is even alive. I don't think I was too fast at that point (slowing from 180 to 160 on the crosswind). I was flying a B737-400 so it doesn't slow down real fast.Any way - I guess what I need to do is to start turning to capture the localizer if even I haven't finished (or started) with ATC. Or get good at turning back!The program could start the turn to intercept instructions a little eariler IMHO. The combo turn and altitude change on the intercept is a bit much as well - is that typical with vectors to final even in the flatlands?I like the RC hint with localizer freq and rnwy heading. Any chance you could squeeze in the indetifier too? Maybe add it to the flight plan page once it has been assigned? I haven't seen the problem with RC yet but in the LA basin it is common to tune to the expected ILS and pick up another airport's ILS. Seems to happen coming in from the south east and heading for the 6/7 runways at KLAX. I think PDZ.PDZ4 from other than TNP has the same problem. Seems like the positive ID of the localizer should be made a big deal of for training purposes. Great program! Keep up the good work!

>>The combo turn and altitude change on the intercept is a bit much as well - is that typical with vectors to final even in the flatlands?<>I like the RC hint with localizer freq and rnwy heading. Any chance you could squeeze in the indetifier too?<<"The marker" is by-the-book so to speak.>>Great program! Keep up the good work!<