Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Need assistance with go-around...

Featured Replies

I have a couple of questions regarding a go-around that I can't seem to find the answers to...

 

1) Having executed a go-around, I select the roll mode above 400 AGL (usually HDG SEL). However, when I select a vertical mode such as FLCH or V-NAV, the roll mode disconnects and the lateral bar on the FD disappears. I'm left with only the pitch command bar and I have to re-select the roll mode. Is this normal for the 737NG?

 

2) How can I ensure that the missed approach procedure in the FMC is ready to be used for the go-around? The route is always displayed with a dotted blue line and I cannot engage L-NAV as a roll mode.

 

Many thanks,

 

Martin

Martin Neep

1. Yes I have the same issue. A while ago I was practicing missed approaches with FS2Crew and I assumed it was a FS2Crew isssue, however it turns out to be some issue with the NGX and not FS2Crew as you have also noticed. Here is the thread I made about it.

 

http://forum.avsim.n...h/#entry2449032

 

 

2. I never had a issue engaging LNAV and from memory the blue dashed line turned into magenta for me. So I am not sure what is going on there.

Jay Vorkapic

 

pmdg_trijet.jpg

  • Commercial Member

Assuming you were on a coupled approach, did you try resetting the flight director during the go around (e.g. Switching it off then back on)?

Kyle Weber (Private Pilot, ASEL; Flight Test Engineer)
Check out my repaints and downloads, all right here on AVSIM

2. I think it's needed to overfly RWXXX waypoint to get go-around leg active. It might be even enough to fly in two miles from this point. I got this when selected approach to one runway and then did a circling approach to opposite.

Did you mean TO/GA to leave option for ILS approach? It's not modeled on NGX.

No, I should have been more clear: Is the LNAV on M/A option on in the FMC? If the option is on, LNAV will appear in white in the FMA.

 

You should be able to select it, either way. Also - is the LEGS page current? (i.e. Is the active waypoint in from of you?)

Matt Cee

Why would you select vnav while in heading sel. Think of VNAV as a climb via the FMC. I'll post a 737NG technique.

 

Touch and go/pattern work

Missed Approach

Note: Assumes intent for complete flap retraction to missed approach holding

pattern.

• TO/GA (A/P will kick off under single-channel operation)

• Set Go-around thrust

• Set pitch to Go-around attitude

• “Flaps 15”

• Positive climb rate - “Gear up”

• 400’ AGL - “LNAV” or “HDG SEL” (Note: for Non-Precision

approaches your probably already at/above 400’ AGL or very close if

going missed from and DA/DDA/MDA)

• Retract flaps on speed

• 1000’ AGL - Set LVL/CHG or V/S + 1500’

• After Takeoff checklist (Ops Man)

Radar Pattern Climb Out From Touch & Go

• PF rotates aircraft to 15 degrees nose high

• Positive climb rate - “Gear up”

• Flight directors - ON (if coming from VFR Pattern OR Recycle)

• 400’ AGL- “Bug Up, flaps 5, LNAV or HDG SEL ”

• 1000’ AGL - Technique: "V/S, Set 1500 fpm" or "LVL CHG"

• Retract flaps on schedule to “Flaps Up”

• After Takeoff checklist

• Maintain flaps Up for downwind

Note: PF re-establishes A/P and manually arms Autothrottles

• PM rechecks weather, installs approach and helps tune nav radios

(technique)

• PF briefs approach, tunes radios and calls for the “Approach check”

Precision Approach (use “CRAMPS” check technique)

• Arm APP if cleared approach on intercept heading

• G/S alive - “Gear down, flaps 15, Bug 15, landing checklist to flaps"

• G/S intercept - “Flaps 30/40 (final flap), Landing checklist” slow to VREF + additive

Non-precision approach (non/VNAV)

• Arm LNAV or use HDG SEL for lateral maneuvering

• 3 miles prior - “Gear down, flaps 15, Bug 15, landing checklist to flaps”

• 2 miles prior (or earlier) - Set MDA or stepdown altitude in altitude alert window

• 1 mile prior - “Flaps 30/40 (final flap), complete Landing checklist” slow to Vref + additive

Note: Do not arm speedbrakes or use autobrakes if accomplishing a touch & go.

VFR Pattern Climb Out From Touch & Go

• PF rotates aircraft to 15 degrees nose high

• Positive climb - “Gear up”

• Turn off FDs if not already off (technique)

• 400’ AGL - “Bug 5, flaps 5” (technique)

• 1000’ AGL - PF lowers nose to 10 degrees pitch and reduces thrust (at

Bug 5 speed) to approximately 75% N1 (technique)

• PF levels off aircraft at 1500’ AGL or pattern altitude and maintains flaps 5 on downwind

VFR Pattern

• Enter downwind at flaps 5, speed Vref 30 + 40 (Bug 5 speed)

• VFR pattern briefing - "30/40 Flap touch and go, Speed is ____"

• Approaching abeam touchdown point - “Gear down, flaps 15, bug 15

Landing checklist to flaps” slow to Bug 15

• Before turning or during turn to base - “Flaps 30/40, Bug 30/40 + ___

(additive), complete Landing checklist,” slow to Vref + additive

• Descend as required (approximately 600-800 VSI as a guide)

Note: Do not arm speedbrakes or use autobrakes if accomplishing a touch & go.

Technique for Establishing Automation After Pattern Work

Note: Technique used should be pre-briefed. Assumes the "gear up" and "flight

director’s - ON " is already called/done.

• 400’ AGL "Bug Up, Flaps 5; HDG SEL or LNAV"

• 1000’ AGL (or A/R) "Vert Speed + 1500’, Flaps 1" or "Level Change"

(Flaps 1 above F5 speed and then flaps on schedule)

• PF establishes A/P by selecting CMD and A/Ts -- ARM

 

Real NG procedures

I have had the same experience but i was way off maybe 10 degree or more of the ILS Approach when i hit the TO/GA my FD did die.

 

My procedure mistake i believe

 

Michael Moe

Michael Moe

 

fs2crew_747_banner1.png

Banner_FS2Crew_Emergency.png

No, I should have been more clear: Is the LNAV on M/A option on in the FMC? If the option is on, LNAV will appear in white in the FMA.

 

That's what I meant: TO/GA to LNAV (autocorrection has changed this word in my previous post) option, as it called in FCOM. And it's not on NGX. Maybe it will be added on SP2.

  • Author

Ok, second problem is solved. I was getting the message 'not on intercept heading'. Turns out if you're flying directly over the correct track, you'll get this message. The only remedy is to open the FMC and select 'Direct To' the next waypoint.

 

As for the issue of the roll mode disconnecting, I think this is a bug. Interestingly it only happens when flying the missed approach manually. It doesn't happen if you execute the go-around with both A/Ps engaged.

Martin Neep

 

As for the issue of the roll mode disconnecting, I think this is a bug.

 

Yep, that was my conclusion too.

Jay Vorkapic

 

pmdg_trijet.jpg

  • 3 weeks later...
  • Author

 

You can actually see the problem in this guys video. As soon as he selects LVL-CHG, he loses the roll command and has to re-select HDG SEL.

Martin Neep

  • 4 months later...

Hi.

 

I decided to jump into this a bit old topic instead open a new one since the conversion was about Go around.

I wonder what I was doing wrong during Go around. My problem is that I cannot engage VNAV during manual Missed approach (AP & AT off).   As far as I remember after above flap maneuvering speed I need to select LVL CHG or VNAV. LVL CHG works but VNAV doesn't (I had missed approach loaded in FMC). I follow all those steps mentioned above but still no luck.

Another question. Do I have to set "new" CRZ FL in Cruis page? I tried to enter any altitude/FL and it kept clearing any values. Also TOD point was missing.

 

Thanks a lot.   

I9-13900K | ASUS ROG Strix Z790-E Gaming LGA 1700 | MSI Gaming GeForce RTX 4090 24GB | CORSAIR iCUE H150i ELITE LCD Liquid Cooler | CORSAIR DOMINATOR PLATINUM 64GB (2X36) 5200MHx DDR5 | Thermaltake GF3 1650W 80+ Gold PSU | Samsung QN90C Neo QLED TV 50”

 

 

 

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.