737 Go-Around question
If you press one of the TO/GA buttons within the criteria for engagement of go-around mode during a singe-channel ILS approach when you are still above the missed approach altitude, as set in the altitude window on the MCP - what would happen? I have searched through FCOM and FCTM without finding any satisfactory answers. I know what I would do if I end up in a situation like that, but I'm interested in a technical perspective.
Best regards |
Exactly the same as with the normal go-around, except that the AFDS will stay in TO/GA mode until you change the pitch mode yourself or reset the MCP altitude to something above your current altitude. In simple terms, the aircraft will climb until it reaches it's performance-limited altitude.
|
Originally Posted by FlyingStone
(Post 10224323)
Exactly the same as with the normal go-around, except that the AFDS will stay in TO/GA mode until you change the pitch mode yourself or reset the MCP altitude to something above your current altitude. In simple terms, the aircraft will climb until it reaches it's performance-limited altitude.
|
It's documented, sort of, in System Description ch. 4. Read it as; in the abscense of ALT ACQ or pilot selected pitch mode, the F/D Go-Around mode isn't terminated. |
Why should one dial in a M/A altitude in the MCP if above?
|
Perhaps with a platform altitude of 3000 and a missed approach altitude of 2000 for example. |
Originally Posted by gearlever
(Post 10224773)
Why should one dial in a M/A altitude in the MCP if above?
|
One way around this is to press TO/GA, followed by FLCH. If done without too much pause, the Approach mode will terminate, the thrust levers will advance slightly, then reduce to a low setting compatible with the remaining descent altitude and the aircraft will continue descent to the MAP alt. Depending on the installed FMS/APFD, the lateral mode may need to be selected to LNAV or HDG SEL. |
One way around this is to press TO/GA, followed by FLCH. If done without too much pause, the Approach mode will terminate, the thrust levers will advance slightly, then reduce to a low setting compatible with the remaining descent altitude and the aircraft will continue descent to the MAP alt. You can do it nicely by retuning the Nav receivers and then engaging V/s and whatever lateral mode you think is best at the time. |
Originally Posted by Skyjob
(Post 10224886)
Look at LEMG/AGP charts for runway 13: MISAP 2000' but platform 12nm at 4200'
Oor SOP was (retired) to set 2.000 ft, or whatever G/A altitude, when below. |
SOP in our company is to set the M/A altitude when when the GS is captured. I often fly in to Stockholm (ESSA) where the missed approach is 1500 ft and the platform altitudes at the highest 4000 ft. That’s why this question have been a particular interest of mine. Thanks for all answers! |
This is why you brief on how you will perform the go around. Simple way of doing it.
1. Press CWS (this will take it out of APP mode) 2. LVL CHG 3. CMD A/B This keeps the aircraft in an automatic mode and you wont need to rush when doing it. |
Hallelujah and praise Father Dick! |
Originally Posted by Father Dick Byrne
(Post 10225630)
Or you can simply fly the aircraft. |
If you want to do it simply. Why not just deselect the ILS frequency then re-select it. That will put you in raw modes. You can then select LNAV and V/S. Far smoother than LVL CHG which is a crude thing when you're near the ground. You've probably got some power on and don't want to drop onto the MA platform like a stone do you?
|
Originally Posted by RVF750
(Post 10227792)
If you want to do it simply. Why not just deselect the ILS frequency then re-select it. That will put you in raw modes. You can then select LNAV and V/S. Far smoother than LVL CHG which is a crude thing when you're near the ground. You've probably got some power on and don't want to drop onto the MA platform like a stone do you?
|
On 777 it will go into an unrestricted climb, 737 and 777 are pretty similar.
Easiest way is if your given a missed approach, before you press TOGA check the altitude selected. The is very rarely a rush to do a go around. If your above the missed approach altitude (on 777 anyway) so long as your above 1500ft if you deselect approach it will default to V/S and decent to and capture the missed approach altitude. When its level then select TOGA and follow the normal procedure. |
Originally Posted by felixthecat
(Post 10231323)
On 777 it will go into an unrestricted climb, 737 and 777 are pretty similar.
Easiest way is if your given a missed approach, before you press TOGA check the altitude selected. The is very rarely a rush to do a go around. If your above the missed approach altitude (on 777 anyway) so long as your above 1500ft if you deselect approach it will default to V/S and decent to and capture the missed approach altitude. When its level then select TOGA and follow the normal procedure. BTW: only selected autopilot needs deselecting, eg NAV 2 with CMD B |
Originally Posted by felixthecat
(Post 10231323)
On 777 it will go into an unrestricted climb, 737 and 777 are pretty similar.
Easiest way is if your given a missed approach, before you press TOGA check the altitude selected. The is very rarely a rush to do a go around. If your above the missed approach altitude (on 777 anyway) so long as your above 1500ft if you deselect approach it will default to V/S and decent to and capture the missed approach altitude. When its level then select TOGA and follow the normal procedure. So you are saying you allow it to capture the missed approach altitude, then select TOGA? I'd say that's a bit dramatic.. Why not just wind a bit of speed on and clean up smoothly? |
It sequences the checks and systems but does nothing else.
|
Why not just wait until you’re below the MAA? |
Because the question was what would happen if you were above it. Not particularly tidy if you were given a missed above the maa then decided to continue down below it before you decided to do the missed (a hundred feet above maybe) but just pushing the app button makes life easy.
|
And that has been answered. The discussion has moved on to the best way to achieve a go around from above the MA. |
Why not just wait until you’re below the MAA? |
Well yes that’s the context of the thread. So, if you have to go around why not wait until you’re below the MAA before you press TOGA? |
Because you might be asked to go around in the example at Stockholm above at say 3000 ft. Why would you descend below the 1500ft missed approach altitude? There is no need to, you would just ensure 1500ft was set and disengage the app mode. Job done.
In a climb when ATC tell you to climb 350 and your at 330 do you go through 350 and then descend back to 350?? Would make no sense would it. ATC might have words to say as well. |
Originally Posted by felixthecat
(Post 10232392)
Because you might be asked to go around in the example at Stockholm above at say 3000 ft. Why would you descend below the 1500ft missed approach altitude? There is no need to, you would just ensure 1500ft was set and disengage the app mode. Job done
2, if you go around above a lower MAA then you’ll be descending anyway. 3, I’m sure ATC won’t mind if I descend to 1499’ before I go around to 1500’, would they? In a climb when ATC tell you to climb 350 and your at 330 do you go through 350 and then descend back to 350?? Would make no sense would it. ATC might have words to say as well. |
Originally Posted by TangoAlphad
(Post 10232465)
So you are going to marginally descend through just so you can press Toga and have the autopilot disconnect and a momentary large increase in commanded thrust? Cancel the disconnect alarm potentially the autothrottle now probably require PM to change a few modes on the MCP so you can select what you want on CMD A. It probably went into ALT AQC at some point so the MCP speed could be somewhere you don't want nor now potentially configured for... I'm sorry but in this case 'keeping it simple' would actually be making an arse of it.
|
The AP disconnects whenever you press TOGA. Not sure how being closer to the MAA is a problem. How do you cope when ATC surprises you and sends you around just below, at or slightly above MAA? |
Originally Posted by Chesty Morgan
(Post 10232436)
1, you’ve already been told that you cannot just disengage approach mode in the 737. 2, if you go around above a lower MAA then you’ll be descending anyway. 3, I’m sure ATC won’t mind if I descend to 1499’ before I go around to 1500’, would they? Stupid comment. 2, if you go around above a lower MAA then you’ll be descending anyway...... your descending slightly in a g/a (50ft or so if that), in the example above it was talking about more than slight a decent. A go around from way above the MAA and then descending hundreds of feet only to pass through through it, disconnecting the AP, large increase in thrust, cancelling any oral warnings, to climb back up, level off, re-engage AP etc etc doesn't make sense to me. 3, I’m sure ATC won’t mind if I descend to 1499’ before I go around to 1500’, would they?...... your going to push the GA at 1499....impressive, then next time when you miss by 2 feet and you press it at 1501ft and you go to an unrestricted climb they might mind, and before you say you will do it slightly lower than that....how much slightly? Is there an SOP in company X that says push g/a at x number of feet below ? I would be surprised. Then there is the A/P disconnecting in the 737 because of the G/A and the large increase in thrust etc etc, why? You can do it much more efficiently and much more smoothly. As for the stupid comment.... its the same thing, I was using that argument as a hyperbole. You don't bust levels for the sake of it. That would be stupid. How do you cope when ATC surprises you and sends you around just below, at or slightly above MAA?........ The operative words there are just above or just below. Then you deal with it as you describe. This discussion was about when you have plenty of time. |
No it wasn’t. You’ve just made that up. It’s not a level bust if you go below a MAA or we’d be having level busts every day. |
I made it up? :D:D And no its not a 'level bust' because its less than 300ft. Not great handling though is it. Do it any way you want, I don't really care :)
|
Originally Posted by felixthecat
(Post 10233055)
I made it up? :D:D And no its not a 'level bust' because its less than 300ft. Not great handling though is it. Do it any way you want, I don't really care :)
Fits your argument doesn’t it? If you don’t care why are you posting? |
Perhaps with a platform altitude of 3000 and a missed approach altitude of 2000 for example
In Stockholm you capture the G/S at 4000 ft and MAA is 1500 ft. Because you might be asked to go around in the example at Stockholm above at say 3000 ft. Yup, all made up:rolleyes:. We don't always go around at exactly the minima or at the MAA in the examples above. Usually in a descending go around it ATC directed and in the above examples there is a long way between 3000 and 2000 in the first point say 1min approx that example, or 4000 and 1500 in second say 2 mins approx. I would say thats 'plenty of time'. If your unable to manage to get the aircraft to smoothly intercept a given altitude and level off in that period without going through selecting TOGA etc etc then you have more problems to worry about. As I said above: How do you cope when ATC surprises you and sends you around just below, at or slightly above MAA?........ The operative words there are just above or just below. Then you deal with it as you describe. This discussion was about when you have plenty of time. |
Long post for someone who doesn’t care. :rolleyes: Good maths though. If your unable to manage to get the aircraft to smoothly intercept a given altitude and level off in that period without going through selecting TOGA etc etc then you have more problems to worry about. |
Ad hominem per chance?.:rolleyes:
|
No, that would be an attack on your character. I just pointed out that you intentionally misrepresented my position because it was easier to defeat. But you still dont care... |
Originally Posted by Chesty Morgan
(Post 10235197)
No, that would be an attack on your character. I just pointed out that you intentionally misrepresented my position because it was easier to defeat. But you still dont care... |
Yes, your argument was a straw man argument which I pointed out. That is not an attack on you. If if I was to say, for example, you’re a moron that would be ad hominem. I didn’t, ergo, it wasn’t. Oooh that’s a good one - how do I fly an approach?! |
I never misrepresented your position at all, I, in fact agreed with your GA from close to the MAA, but you appear to be unable to see that there are more sides than your one to this problem.
Insulting me just proves your ignorance...QED ad hominem. |
All times are GMT. The time now is 15:38. |
Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.