[jhb_airlines] Re: Descent

  • From: gwinsk@xxxxxxx
  • To: jhb_airlines@xxxxxxxxxxxxx
  • Date: Sun, 14 Nov 2004 19:23:56 -0000

It works im mysterious ways.
If I try to plan an EGCC to EGKK, the Manchester HON1R SID, dictated by 
then the highest cruise alt I can get FSNav to accept, by HON, is 19500. This 
is in the 
CRJ700, with its climb set at an unrealistic 2200 fpm. If I try for 20000' then 
it settles on 
a max of 5000'! The only way is to creep up on the by HON altitude entry. It 
ignores the cruise alt set in the Aircraft section.
For me, the easiest way round the problem might be to have FSNav's FMS follow 
track and enter the altitudes manually, as each point is passed. Eg, set 
3000'and hold 
until HOND58, then reset to 5000', until SANBA, then reset to an achievable 
20000', etc.

Gerry Winskill

On 14 Nov 2004 at 18:02, Bones wrote:

> FSNav needs a little playing with in this respect. Altitude Crossing
> and Altitude After do two separate but subtle things - and FSNav isn't
> clear = as to what they do. The other problem I've noticed is that
> once you enter = 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 = 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 =
> suggesting
> the best way to implement them. Feedback or corrections welcome!
> Altitude After is probably best used in the climb only. I say that =
> because it seems to lock the remaining portion of the flight at the
> selected = height. I would probably only use it if you needed to cross
> a beacon at a = specified height.
> Altitude Crossing is something I would use on descent if you wanted to
> = hit a beacon or fix at a target height.
> In both cases I wouldn't assign a second limitation on a second
> position = in close proximity because FSNav seems to need a bit of
> space to separate = out the two. For example if you dialled in to
> cross WCO at FL100 and BNN at = 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
> SID's out of Heathrow end up at 6000ft and I'd program this into FSNav
> for the exit = 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
> this isn't possible for anything other than a specific aircraft. The
> PMDG FMS = is brilliant but I am still getting to grips with it as I
> haven't used one = for a long time - possibly Bill Grabowski's ERJ or
> something of that = vintage..
> bones
> -----Original Message-----
> From: jhb_airlines-bounce@xxxxxxxxxxxxx
> [mailto:jhb_airlines-bounce@xxxxxxxxxxxxx] On Behalf Of gwinsk@xxxxxxx
> Sent: 14 November 2004 09:36 To: jhb_airlines@xxxxxxxxxxxxx Subject:
> [jhb_airlines] Re: Descent
> Jumping slightly sideways, trying to enter a height profile into FSNav
> = is not easy. In=20 theory, its facillities for Altitude Crossing and
> Altitude After, should allow the heights=20 specified in SIDs and
> STARs to entered. In practice, it seems to  have a life of its own,=20
> which reduces its FMS attraction. I used to have a Shareware FMS
> package = but seem to=20 recall its designer dropping out, before
> FS2002. Is there an alternative around? Better=20 still, is there an
> external hardware lump that will interface with FS9? Pipedream?
> Gerry Winskill
> gwinsk@xxxxxxx
> On 14 Nov 2004 at 3:58, Bones wrote:
> > Careful using the word London as I don't know whether you mean
> > London=20 as in Heathrow Approach or London Centre..
> >=20
> > >From Glasgow to Heathrow you would change from Scottish Centre
> > >to=20 London
> > Centre around 55N. You won't go to Manchester as they only have=20
> > control up to FL150 in real life but FPI might differ on this.
> >=20
> > If only Heathrow Approach is active this can be trickier but plan=20
> > ahead to sort out your descent to be at BNN VOR at FL70. Approach
> > may=20 very well take you on early enough to give you a descent but
> > if he=20 gets too busy with his stack traffic its going to be up to
> > you to get=20 down in time.
> >=20
> > bones
> >=20
> > -----Original Message-----
> > From: jhb_airlines-bounce@xxxxxxxxxxxxx=20
> > [mailto:jhb_airlines-bounce@xxxxxxxxxxxxx] On Behalf Of Alastair=20
> > McIntyre Sent: 13 November 2004 21:23 To: jhb_airlines@xxxxxxxxxxxxx
> > Subject: [jhb_airlines] Descent
> >=20
> >=20
> > A 'quick' one for John.
> >=20
> > John, assuming I am on a IFR flight from EGPF to EGLL.
> >=20
> > Only one controller on line at, say, London centre.
> >=20
> > Q. on reaching abeam Trent VOR, do I start my descent from F350=20
> > WITHOUT contacting the London controller? (As I am out with his=20
> > controlled airspace at that point).
> >=20
> > I am thinking that it is not too good to leave the descent too late.
> >=20
> > Unlike the real world, at this point I would be under the control
> > of=20 Manchester, who in turn would hand over to London control.
> >=20
> > Thanks, again.
> >=20
> > Alastair
> >=20
> >=20
> >=20

Other related posts: