No crew callouts
-
-
@eker Try pressing the STEW CALL button on the overhead panel during taxi for take off to advise the cabin crew to take their seats for take off, you should hear an announcement. Once the throttles are set to take off power, you should hear the other callouts.
-
@slado Sorry- no cigar.......
Both Comms volumes are Ok.
Checked keyboard bindings. Found annunciator switch to set to on - did not help. Tried reset EFB option before saving...
GPWS and cabin works OK. Only copilot is dead The same with both version 1.01.
Have a vanilla PC setup - nothing fancy.
Noted most youtubers are OK, a couple does not - probably not aware of it. -
@eker Sorry to hear that. It was just I had noticed the same thing at one point and I'm sure that after I got into the habit of making sure to trigger seats for take off, it never happened again. Hopefully someone from the JustFlight team will have suggestions.
-
I noticed I don't get the "retract flaps" callout unless I pitch to 15 degrees in initial climb after retracting landing gear. I've stuck at 10 degrees a couple times.
-
Here is some information on what conditions trigger the take-off and climb phases for the callouts, and then what triggers each callout during that phase:
Take-off phase:
-
Aircraft is on the ground
-
Throttle levers set to greater than 40%
-
Strobe lights switched on
-
Landing lights switched on
"Thrust set" - throttles in detent position or thrust indicator at 100%
"80 knots" - ASI reading 80 KIAS or greater
"Rotate" - ASI reading VR speed or greater (as shown on speeds card)
"Positive rate of climb, gear up" - Above 50ft AGL, vertical speed greater than 500ft/min, gear down
Climb phase:
-
Gear up
-
Above 50ft AGL
-
Vertical speed greater than 500ft/min
"Flap 11" - Above 600ft AGL, flaps set to greater than 11 degrees
"Flaps up" - Above 800ft AGL, flaps set to greater than 0 degrees, ASI reading greater than VFTO speed (as shown on speeds card)
"Set power" - Above 1000ft AGL, flaps up, ASI reading greater than VFTO speed (as shown on speeds card)
-
-
Approach phase:
- ASI reading less than 250 KIAS
- Less than 6000ft AGL
- Vertical speed less than -500ft/min
- Or BEAM mode engaged and localiser captured
- Or GLIDE mode engaged and glideslope captured
"Course bar active" - localiser alive, course bar moving
"Localiser" - localiser captured
"Glideslope" - glideslope captured
"Speed" - ASI reading less than VREF - 5 KIAS and above 150ft AGL
"100 feet to minimums" - 100ft above radio altimeter bug height
"Minimums" - At radio altimeter bug height
"Flaps 11" - Less than 3000ft AGL, ASI reading less than 190 KIAS, flaps set to less than 11 degrees
"Flaps 25" - Less than 2000ft AGL, ASI reading less than 160 KIAS, flaps set to less than 25 degrees
"Flaps 42" - Less than 1500ft AGL, ASI reading less than 150 KIAS, flaps set to less than 42 degrees
"Gear down" - Less than 2500ft AGL, ASI reading less than 170 KIAS, gear not down -
@martyn
Thanks Martyn, great information.Curious to why you have the less than -500 fpm as a condition.
I sometimes have to descend greater than that if ATC keeps me high.
Might explain why sometimes I get the landing call-outs and sometimes I don't.I would think once your ASI is less than 190 KIAS, you should be bringing out your flaps regardless of what your vertical speed is.
I don't expect you to change your program just for me but is there a "tweak" that I could apply to remove the vertical speed condition?
Might give me more reliable landing call outs. -
@lancealotg Apologies, I do mean greater than -500fpm, e.g. -700fpm, -1500fpm etc
-
I have always heard sounds including music during boarding, cabins crew, FO, etc.
Except today, when I started my flight C&D at EGCC I didn’t hear any of these standard calls, except that I did get calls during the approach and landing phase, as well as taxiing in.
What are the triggers from a C&D state to get the ball rolling in terms of crew calls?
Thanks.
