Off-Topic replies have been moved to this Topic.

Engine Start EGT issue:
When starting the RB535E4 (also happens with the "normal" RB535) the EGT only rises after the rest of the engine is stabilized.
EGT should rise the moment fuel is introduced into the engine and ignition occures (common sense, isn't it?).

See this screenshot:

TERR RANGE DISAGREE message with left and right ND set to different zoom levels.

This is an annoying one, when using the TERR display on the right ND the above message always displays if a different scale is selected on the left and right ND's.
See this picture:



A similar issue exists with the weather radar.
The range of the systems seems to be set by the left ND only, the right ND will show simply the same copied returns as the left ND, even if the ranges are different.

AIIR#4

Scholli04 wrote on Jan 25^th, 2019 at 9:58am:


Alright, so, several ones in here while I'm on the AIIR.

1) Manual Part II, page 275: The WXR RANGE DISAGREE message is missing.

A little bit of background information for you as to when these messages show as I feel you might misunderstand their meaning. They do not at all indicate a difference between the Captains and FO's instruments as they do in your 757.
In real life, when switching the range of the ND, it sometimes takes the system a bit of time to respond. The longest I've seen so far was 12 seconds. After a couple of seconds the range disagree messages show to indicate that the map is no longer in agreement with the EFIS selector. This is particularly important on those aircraft which do not have range rings installed on the ND. That's the purpose of these messages.

2) Manual Part II, page 321: "The radar display range is set by the HSI range selected on the EFIS control panel."

This confirms that the range of the WXR is set by the respective range selector on the EFIS control panel. There is no mention whatsoever that the captains EFIS control panel would set the FO's display. In face it confirms the opposite, "the radar display range is set by the HSI range selected on the EFIS control panel". So if I set 40NM I get a 40NM radar image on my ND.

3) Terrain Display Range on the FO's side. You're asking me for a proof that they would not be synced between the captains and fo's side. I'm asking you where it would say that they ARE synced. The manual does not mention any syncing between the ranges. Therefore you are assuming something here which is not in the manual. Any of your real 757 pilots will confirm to you that they are independant and match the range on the respective sides range selector. This is simply a common sense thing so please either ask your pilots or show me where it says that they are in sync. Page 575 in the manual explains the system in detail and does not mention any syncing.
Page 552 explains the switches and messages and reads the folloing:
"TERR RANGE DISAGREE (amber) -
[...]
terrain output range disagrees with the HSI range selector MAP/TERR"
Using reverse logic this means the HSI range selector and the map display must usually be synced.
Please ask your reference pilots and they will confirm it to you.

If you disagree with me on this one please respond with a full sentence and not just 6 letters again so that we can discuss it.

Thanks, on the list.

Alessio_Calandrella wrote on Jan 27^th, 2019 at 9:13pm:


According to the manual part 2:
page 54:
"3. Cabin Altitude Rate
Feet per minute (fpm x 1,000)."

page 64:
"DESCENT AND LANDING

During descent, cabin altitude decreases to slightly below the selected landing
altitude. This ensures that the airplane lands pressurized. Landing altitude
barometric pressure correction comes from the captain’s altimeter.
At touchdown, the outflow valve opens to depressurize the airplane."

Thanks, just re-checked, works OK.

In VNAV PTH mode with the aircraft descending below the profile the AP should aim for 1000fpm until intercepting the profile.

Yours will simply try to climb back to the profile.

VNAV CLB page only shows altitude constraint of the active waypoint, not of future waypoints if the next waypoint does not have a constraint.

The VNAV CLB page should show the next altitude constraint that is included in the route (until the T/C to avoid descent constraints displayed).
In your simulation the constraint is only shows if it belongs to the current active inbound waypoint and only when they are hard altitudes. Above restrictions do not seem to be shown either in yours.

Let me give you an example with pictures:
Here you see that there is an altitude restriction at FL70 at DP551. The inbound waypoint DESAN has a 3000A restriction. Neither show in the CLB page.
In the first pic 3000A should be shown.


Once DESAN is overflown and DP551 becomes active it then shows FL70 which is correct.


Please note that the next CLIMB altitude constaint should ALWAYS be shown, even if it belongs to a later waypoint and not the current inbound waypoint!

Refer to the manual, page 412 and 413.