NZFF

Hi all,

I thought I would share this short story which I think will be familiar for all of you.
Usually I don't use IFR ATC in FS9 because it just makes things harder... I had to realize that I got the same dramatic results with VFR ATC... I had a perfect take off from Timaru for Dunedin with my Mount Cook Airlines HS748. The flight was fantastic, nice weather it was a bit foggy though. I requested full stop landing (that was about 20nm from NZDN) and ATC replied : Fly straight in blabla... OK.. After 2 minutes ATC goes : Cleared to land. It just seemed to be perfect. About 0.5 nm before the runway I've realized one of the worst nightmare of every pilot. There was an ATR on the runway (I haven't seen it because I have that stupid red AI labeling turned off - again realism, realism and realism). It's already started the take off. ATC goes : Go around! Of course, what else can I do - I thought. Flaps back, gears back, full throttle. I almost had to pass the ATR, but he finaly accelerated so I managed to avoid the impact. After the go around I had a nice landing, and heard the applause of the passangers (one of my favourite features in FSPassenger ). According to the flight report (still FSPassenger) the flight was perfect. Hmmmmm. Maybe I was lucky this time but the flight surely wasn't perfect... The other thing is that I still couldn't make the Approach function work on Autopilot. It doesn't give a damn about my altitude. It only controls my heading. Do you know if I do something wrong?

So..That's all. I know, the best solution would be to get a payware ATC add-on, but I have to take care of my FPS as well. It's already low enough...

Daniel

Hmm, a common story for people who use AI I suppose...

With the APP AP function there... got both Nav radios tuned into the ILS in Dunedin? Intercepting from below the glideslope?

Alex

Wow...I have to tune both NAV radios? That's new to me...

Alex wrote:

QUOTE (Alex @ Jun 11 2008, 05:20 PM) <{POST_SNAPBACK}>

Hmm, a common story for people who use AI I suppose...

Oh my...life without AI...like not breathing, dude.
Don't know that you'd need both NAV tuned, but I was also going to suggest ILS intecept from below...

gojozoom wrote:

QUOTE (gojozoom @ Jun 11 2008, 08:18 PM) <{POST_SNAPBACK}>

Wow...I have to tune both NAV radios? That's new to me...

Charl wrote:

QUOTE (Charl @ Jun 11 2008, 09:25 PM) <{POST_SNAPBACK}>

Don't know that you'd need both NAV tuned, but I was also going to suggest ILS intecept from below...

Oh, I thought you needed both tuned for the Autopilot to pick it up - but I haven't really tried using one or the other...

Alex

Yeah the way I do it is I go to the map and find the ILS freq for the runway I'm landing at, put that into NAV1 and activate it. When I press the APP button it will lock my heading but not my ALT, how am I supposed to know how high I should be? Will it be on one of the EFIS screens or something?

Alex wrote:

QUOTE (Alex @ Jun 12 2008, 06:23 PM) <{POST_SNAPBACK}>

Oh, I thought you needed both tuned for the Autopilot to pick it up - but I haven't really tried using one or the other...

Alex

I think having both tuned in is just a precautionary thing, not necessary

Probably worth a shot entering it in both - works well for me...

Alex

So enter the same ILS freq into both of them?

victor_alpha_charlie wrote:

QUOTE (victor_alpha_charlie @ Jun 12 2008, 09:08 PM) <{POST_SNAPBACK}>

So enter the same ILS freq into both of them?

If you want, yeah. I think its more a "real life thing". If the nav1 dies, nav2 is already tuned in, so no drama if its wild weather with not much vis, (not sure about cat1,2,3.... so i'll leave it up to you to tell me a 737 can't land in no vis......or whatever is the case.....bla bla bla )

So if you want to be realistic, then enter them both, unless your using the other one to measure your distance to somewhere or whatever....

Nick

Actually you were right. I have to enter the ILS about 2800 feet and it works. I also like the idea of having both NAVs tuned to ILS. REALISM, REALISM AND AGAIN REALISM! Thanks for the useful answers guys!

If you have FSNavigator, have a look at the runway in the map mode (move your mouse cursor over the end of the runway you are intending to use) it'll come up with all the details you need - Length, width, elevation, ILS frequency and range, Glideslope angle and altitude.
Failing that, see if you can get your hands on a copy of the VFG (Visual Flight Guide) - small, spirax bound book that the CAA puts out for pilots. I remember blasting around NZ in the Learjet flying every approach I could get my hands on using only the VFG to tune the NAV radios and find the various approach altitudes... and that was in FS5!

Flightsim.com: ILSguide.zip
FS2004/FSX Guide For The ILS Approach. A detailed step-by-step guide to the Instrument Landing System (ILS)

Alfashark wrote:

QUOTE (Alfashark @ Jun 13 2008, 08:16 AM) <{POST_SNAPBACK}>

Failing that, see if you can get your hands on a copy of the VFG (Visual Flight Guide) - small, spirax bound book that the CAA puts out for pilots.

VFG has been replaced by AIP... and you can get the electronic versions (PDF) for free from:

www.aip.net.nz

All the plates (VFR and IFR) for NZ...