IFR checkride in fs2004

[Amit Dhingra]

This is the one based in Seattle when you have to make a missed approach on
runway 34R. I make the missed approach at altitude 900 ft. But still I am
announced failed as a went 'below' the missed approach height of 840 ft.
Done it multiple times now. A little frustrating. Any ideas?

Thanx
Amit

[Greasy Rider]

"Amit Dhingra" > wrote in message
...
> This is the one based in Seattle when you have to make a missed approach
> on
> runway 34R. I make the missed approach at altitude 900 ft. But still I am
> announced failed as a went 'below' the missed approach height of 840 ft.
> Done it multiple times now. A little frustrating. Any ideas?



Fly somewhere else?

[Matthew Chidester]

make sure your alt setting is correct.. press M and then B during flight..
one will fix the DG and the other will fix the alt -

then try it again and make sure you don't go below mins. you should be able
to do it - I think 1ft under and you busted.

good luck

Matthew

[Icebound]

"Amit Dhingra" > wrote in message
...
> This is the one based in Seattle when you have to make a missed approach
on
> runway 34R. I make the missed approach at altitude 900 ft. But still I am
> announced failed as a went 'below' the missed approach height of 840 ft.
> Done it multiple times now. A little frustrating. Any ideas?
>
> Thanx
> Amit
>
>

There are some bugs in the checkride and some peculiarities. The first bug
is that the track from FACTS to SEA is actually 340 not 338, but the checker
is checking against 338.


1. You have to set the VOR to SEA and turn the OBS to 338 within 30
seconds.
2. You have to stay within 50 feet below and 100 feet above the required
altitude. Try to stay at or above the requested altitude.
3. You have 2 minutes to turn to 338 and head north.
4. Once the 2 minutes are up, you cannot correct more than 10 degrees off
338
5. You must pass each of the checkpoints at the published altitude (+ or -
tolerance). The key DMEs from SEA are 17.0, 11.0, and 4.4. You cannot cross
"high", which would normally be acceptable in real life, I believe.
6. you must climb out on the go-around at 500 feet per minute. If you drop
below 200 fpm, you fail.
2. You cannot correct more than + or - 10 degrees off 339 on the way up on
the missed approach.

Then the fun really starts when you go to the next task: the hold.

[Matthew Chidester]

> Then the fun really starts when you go to the next task: the hold.
>
>


good grief.. I've never tried the lesson but sheesh i'm instrument rated in
real life and I bet i'd fail that dumb thing..

[Benny Jørgensen]

Hi'
I wonder if the limit is + - 50 feet ????
Happy Landings
Benny

"Amit Dhingra" > skrev i en meddelelse
...
> This is the one based in Seattle when you have to make a missed approach
on
> runway 34R. I make the missed approach at altitude 900 ft. But still I am
> announced failed as a went 'below' the missed approach height of 840 ft.
> Done it multiple times now. A little frustrating. Any ideas?
>
> Thanx
> Amit
>
>

[James Hodson]

On Fri, 24 Sep 2004 23:04:31 GMT, "Matthew Chidester"
> wrote:

>make sure your alt setting is correct.. press M and then B during flight..
>one will fix the DG and the other will fix the alt -

Hi Matthew

I'm aware of the effects of pressing the key "B" but what does
pressing "M" achieve?

Cheers
James

[Matthew Chidester]

M or B (I can't remember which) resets the heading indicator - sometimes
you have to set it every 15 min. because it replicates the pressision or
whatever you call it that the gyro.. depends on your realism setting but it
could mess up your IFR test if you're heading in the wrong direction, even
though you think you're lined up correctly. The other of course sets your
alitmeter to the correct setting for alt.

ok this isn't making sense but "m" resets the heading indicator to the true
heading (compass heading) so ususally I hit M, and B

hope that made sense,

Matthew

[James Hodson]

On Mon, 27 Sep 2004 16:23:20 GMT, "Matthew Chidester"
> wrote:

>hope that made sense,

I certainly did, I think. I've achieved the same by twiddling the knob
and wasn't aware of a keyboard shortcut.

James

[Matthew Chidester]

> I certainly did, I think. I've achieved the same by twiddling the knob
> and wasn't aware of a keyboard shortcut.
>
> James

glad to help :) wish I knew all the shortcuts.

Matthew