September 3, 201411 yr Author Still get that flashing A on the mcp even when the command bug is not in the amber band on the speed tape? Vernon Howells
September 3, 201411 yr Commercial Member Still get that flashing A on the mcp even when the command bug is not in the amber band on the speed tape? FCOM 4.20.22:- Minimum Speed Reversion The AFDS and A/T do not control to a speed which is less than minimum speed for the current flap configuration. This speed is approximately 1.3 Vs. Minimum speed, FMC speed, or selected speed, whichever is higher, becomes the AFS commanded speed. If actual speed becomes equal to or slightly less than the minimum speed, the underspeed limiting symbol appears in the MCP IAS/Mach Display, and if operating in the V/S mode, the AFDS reverts to LVL CHG. The AFDS will also revert to LVL CHG from VNAV PTH, except when flying a level segment. The AFS commands a speed 5 knots greater than minimum speed. Reaching a speed 5 knots greater than minimum speed reactivates normal MCP speed selection control. The AFDS commands nose down pitch to increase airspeed if the thrust levers are not advanced. When actual speed becomes 5 knots greater than minimum speed, the underspeed limiting symbol disappears. The A/P disengages and the F/D command bars retract when in a LVL CHG climb with a command speed equal to minimum speed and a minimum rate of climb cannot be maintained without decelerating. Minimum speed reversion is not available when the A/T is OFF. Emphases mine - it's a separate concept from the amber speed band, though it's somewhat related. Kyle Rodgers
September 3, 201411 yr Author Yes i read all that but still not sure why this is happening i have everything set and configured right! Well surely i have, if i haven't i want to find out what i'm doing wrong (human error) haha!! Kyle maybe you could do a takeoff without VNAV and report back and take screen shots for me? Thanks. I found this - http://www.pprune.org/archive/index.php/t-365090.html Vernon Howells
September 3, 201411 yr Commercial Member Kyle maybe you could do a takeoff without VNAV and report back and take screen shots for me? Thanks. I've done plenty of them, and I don't see what you're reporting if I've configured the aircraft properly. The speed bug should be the V2 speed for the takeoff flaps set. As you depart, you're supposed to roll the speed bug up to the next appropriate speed prior to selecting the next flap setting (if you want the proper procedure, watch VNAV do it, or read the manual). You sure you're not flying a plane that's expecting KGs and entering weights as LBS? That could cause it, too. Kyle Rodgers
September 3, 201411 yr Author Hmm am i right in setting the V2 from the FMC into the MCP ias window? ie FMC V2 147 i set 147 into the IAS window? Everything is set as KG Vernon Howells
September 3, 201411 yr Commercial Member Hmm am i right in setting the V2 from the FMC into the MCP ias window? ie FMC V2 147 i set 147 into the IAS window? Correct. Kyle Rodgers
September 3, 201411 yr Author I only roll the speed up to 230 once at AA untill flaps are retracted. Only when i'm accelarating i retract flaps on schedule. Well still not sure why i have a flashing A. It only extuingishes once i roll the speed up like 10 or 20 kts Seems like a hidden minimum speed margin on the speed tape Vernon Howells
September 3, 201411 yr Commercial Member I only roll the speed up to 230 once at AA untill flaps are retracted. Only when i'm accelarating i retract flaps on schedule. Well still not sure why i have a flashing A. It only extuingishes once i roll the speed up like 10 or 20 kts Seems like a hidden minimum speed margin on the speed tape Quite honestly, I still think it's a problem with your procedure because I'm not seeing it, flying it by the FCTM procedure (more specifically, NADP modifications of it). Just to be clear, you're rolling the speed up to 230 prior to moving the flap lever, correct? Kyle Rodgers
September 3, 201411 yr Author Yeh once at 3000 i move the speed bug to 230 and retract flaps on schedule! All my procedures are from the FCOM ryanair! Vernon Howells
September 3, 201411 yr Author Watched a few youtube 737 ngx takeoffs and seen it flashing! Flashing when the speed bug was set at FMC V2 speed And when it wasn't flashing the V2 speed bug was set at V2 + 20 So i think there is a minimum speed margin inbetween V2 and V2 + 20 Vernon Howells
September 3, 201411 yr Commercial Member Watched a few youtube 737 ngx takeoffs and seen it flashing! YouTube NGX takeoffs or NG takeoffs? If you're basing your workflow off of what people are doing in the sim (NGX), it might not be right. For clarification, the real thing is the "NG." Kyle Rodgers
September 3, 201411 yr Author I only base my procedures from the FCOM provided by ryanair always have always will. Also the FCTM but thats just standard. I don't follow anyones work on youtube videos was just looking for that flashing A and seeing if it was occuring else where which it was if VNAV isn't armed on the ground. Yep NG is the real thing Vernon Howells
September 3, 201411 yr Having the correct procedure is only part of the mix. The proof is in the excecution. I think some videos is the only way we can diagnose the problem. Matt Cee
September 4, 201411 yr Author Ok i found the problem i have provided a snapshot. The flashing A only happens at thrust reduction height 1500 and when N1 engages. its seems the command V2 speed bug (154) is in the yellow strip and this causes the A to flash. i done another takeoff this time setting the speed bug at (160) and at 1500 no flashing A as the speed bug 160 wasn't in the yellow tape. https://www.dropbox.com/s/f8dmgktd88d7ojg/2014-9-4_10-46-27-9.BMP?dl=0 Vernon Howells
Create an account or sign in to comment