[jhb_airlines] Re: Descent

  • From: "Bones" <bones@xxxxxxx>
  • To: <jhb_airlines@xxxxxxxxxxxxx>
  • Date: Sun, 14 Nov 2004 20:31:02 -0000

Note that I've thrown the comments in for further discussion and I'm =
willing to be corrected on this.=20

I suggest everyone posts test results as you try further experiments..


-----Original Message-----
From: jhb_airlines-bounce@xxxxxxxxxxxxx
[mailto:jhb_airlines-bounce@xxxxxxxxxxxxx] On Behalf Of Alastair =
Sent: 14 November 2004 18:42
To: jhb_airlines@xxxxxxxxxxxxx
Subject: [jhb_airlines] Re: Descent


Very useful comments (as always).

I tried altering a few altitudes in the 'altitude crossing' in descent=20
mode, and it seemed to work o.k.

Not to sure, however, about the 'altitude after' in climb mode.

However, very useful information concerning the differences between the =



Bones wrote:

> FSNav needs a little playing with in this respect. Altitude Crossing=20
> and Altitude After do two separate but subtle things - and FSNav isn't =

> clear =3D as to what they do. The other problem I've noticed is that=20
> once you enter =3D one
> height restriction FSNav isn't kind in allowing a second change in the =
> near
> vicinity. A third issue is that selecting these boxes and then =
amending =3D
> them
> sometimes throws FSNav is a tizzy and it doesn't reset properly.
> It's a while since I used these boxes but I'll have a crack at =3D=20
> suggesting the best way to implement them. Feedback or corrections=20
> welcome!
> Altitude After is probably best used in the climb only. I say that =3D =

> because it seems to lock the remaining portion of the flight at the=20
> selected =3D height.
> I would probably only use it if you needed to cross a beacon at a =3D
> specified
> height.
> Altitude Crossing is something I would use on descent if you wanted to =

> =3D hit a beacon or fix at a target height.
> In both cases I wouldn't assign a second limitation on a second=20
> position =3D in close proximity because FSNav seems to need a bit of=20
> space to separate =3D out
> the two. For example if you dialled in to cross WCO at FL100 and BNN =
at =3D
> FL70
> FSNav might decide to ignore the first and drop you down to FL70.
> This makes SID's a bit messy but as an interim fix for this I would =
> suggest just entering the final SID altitude in FSNav. Most of the=20
> SID's out of Heathrow end up at 6000ft and I'd program this into FSNav =

> for the exit =3D fix.
> If there is an intermediate height restriction then dial this into the
> autopilot ALT box. I know FSNav tends to override this but I'm sure I =
> found
> a temporary way to bypass the FSNav alt and specify your own. This is =
> where
> my lack of using FS recently is beginning to show..
> I don't honestly know of a separate FMS package Gerry and I'd guess=20
> this isn't possible for anything other than a specific aircraft. The=20
> PMDG FMS =3D is brilliant but I am still getting to grips with it as I =

> haven't used one =3D for
> a long time - possibly Bill Grabowski's ERJ or something of that =3D
> vintage..
> bones

Other related posts: