Hi everyone,

I followed the sample flight, but the Altitude/Speed section in flight plan just look empty apart from the STAR and Approach way points with restrictions. Is there a place to key in cruise altitude information in the FMS so that it can fill in all the altitude and speed for the way points automatically?

Thanks

Zicheng

No, the Dash does not work that way.

The Dash is a very manual aircraft. The FMS is useful for computing flight data such as winds, times, fuel estimates, etc.. and for having the autopilot fly the lateral flight plan, but the altitude and speed management is entirely manual.

 

It has a limited VNAV capability in descent only, but requires a lot of input from the pilot and requires that you stay ahead of the aircraft.

 

Best regards,

Robin.

 

It has a limited VNAV capability in descent only, but requires a lot of input from the pilot and requires that you stay ahead of the aircraft.

 

Best regards,

Robin.

 

I'm not sure where you got that from?! It's just a simple matter of clicking VNAV and selecting a waypoint which has an altitude restriction on it (or one that you have added a crossing restriction to)

It has a limited VNAV capability in descent only

I mean the VNAV is restricted to descent only. I missed the brackets.

but requires a lot of input from the pilot and requires that you stay ahead of the aircraft.

It requires input in that you have to tell it which waypoint(s) to use, altitude constraints for those waypoints (if they are not present), then once VNAV is active, you need to monitor the vertical profile closely, ensure you are on target, and manage the speed.

 

Compared to the Boeing where it will smartly descend based on flight plan altitude constraints, will manage the speed for you (due to auto-thrust) and will tell you if it is unable to make the next constraint, I'd say there is more required of the pilot in VNAV mode, yes.

 

IMHO IAS mode is easier to manage for descent in the Dash, with vertical speed being controlled with power and a reasonable assurance that the speed will remain sensible.

 

Best regards,

Robin.

Dash 8 VNAV fun:

 

Take your altitude above your desired airfield elevation:

 

So, Cruise Alt = 24000 ft - 4000 ft (airport elevation) = 20000 ft.

X by 3 = 60000.

Drop some zeros = 60. So start your decent 60 NM out.

 

Determine your ft/min down by taking your ground speed and dividing it in half:

GS = 340 knots/2 = 170

Which translates to 1700 ft/min down.

 

You can use your discretion to adjust accordingly; IE, starting your decent a bit later and keeping your speed up in the decent.

Great help.

Dash 8 VNAV fun:

 

Take your altitude above your desired airfield elevation:

 

So, Cruise Alt = 24000 ft - 4000 ft (airport elevation) = 20000 ft.

X by 3 = 60000.

Drop some zeros = 60. So start your decent 60 NM out.

 

Determine your ft/min down by taking your ground speed and dividing it in half:

GS = 340 knots/2 = 170

Which translates to 1700 ft/min down.

 

You can use your discretion to adjust accordingly; IE, starting your decent a bit later and keeping your speed up in the decent.

My brain doesn't like computing 20000. Drop the zeroes early.

Easy to remember how many zero's too... 3

 

drop 3 zeros, times by 3.

 

Havn't seen the ft/min decent rate done as divide by 2 before. I usually use times by 5.

oddly 340 x 5 = 1700

340 / 2 = 170 (add a 0) = 1700

 

same answer !

If you divide by a fraction, it is the equivalent of multiplying by its recipricol.

 

(x / 1) / (2 / 1) * (10 / 1)

 

Recipricol of 2 is 1/2, or 0.5.

 

= (x / 1) * (1 / 2) * (10 / 1)

 

= x * 0.5 * 10 << commutative (see note). Solving for x we get:

 

= x * 5.

 

QED.

 

Note: x * y * z is the same as (y * z) * x.

 

(1 / 2) * (10 / 1)

 

Multiplying out the brakets:

 

(1 * 10) / (2 * 1)

 

= 10 / 2

 

= 5

 

Best regards,
Robin.