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.

QW 787 Bizarre FMC Issue Just Developed. Need Help

Featured Replies

Hi, keeping it short:

  • P3d V5 HF2
  • QW 787 latest Service Pack (aug 2)
  • Aircraft, while flown seldom has performed as designed at least once
  • I have been putting in some serious hours with PMDG AC FMC and I have adequate skills to fully use the FMC from takeoff to landing

Starting yesterday, after just having flown this flight plan successfully the day before (KLAXKJFK) the Aircraft repeatedly performs  a series of events which result in a spectacular crash in less than two minutes. This is how it goes:

  • Engage AT, departure roll begins as expected
  • 80 Knot callout
  • V1 callout
  • Rotate callout
  • Positive rate of climb, gear up callout.
  • Aircraft is climbing steady and passing 1000 AGL when Betty starts screaming:
  • TERRAIN ALERT. TERRAIN ALERT. PULL UP. WHOOP WHOOP
  • (we’re still climbing)
  • Airspeed remains N1+ but stall shake is now present (Betty still shouting)
  • Sometime soon after that the AT slams the throttles fully closed, the FMC is now over commanding  and the aircraft flat stalls and pancakes in some LA neighborhood 
  • And it behaves pretty much that way over and over no matter what flight plan is in FMC, it happens. When hand flying without AT it seems Ok. 

Any Ideas or suggestions?
TIA,

-Braun

PS...I remember some message appearing in FMC about landing configuration or profile, can’t exactly remember but the message definitely had the word landing in it   Also I’ve not posted in QW forum as of yet but will copy and paste this there also

Thanks again

Edited by btacon
Update

Have you uninstalled and reinstalled it?

Cheers

Steve Hall

2 hours ago, btacon said:

Hi, keeping it short:

  • P3d V5 HF2
  • QW 787 latest Service Pack (aug 2)
  • Aircraft, while flown seldom has performed as designed at least once
  • I have been putting in some serious hours with PMDG AC FMC and I have adequate skills to fully use the FMC from takeoff to landing

Starting yesterday, after just having flown this flight plan successfully the day before (KLAXKJFK) the Aircraft repeatedly performs  a series of events which result in a spectacular crash in less than two minutes. This is how it goes:

  • Engage AT, departure roll begins as expected
  • 80 Knot callout
  • V1 callout
  • Rotate callout
  • Positive rate of climb, gear up callout.
  • Aircraft is climbing steady and passing 1000 AGL when Betty starts screaming:
  • TERRAIN ALERT. TERRAIN ALERT. PULL UP. WHOOP WHOOP
  • (we’re still climbing)
  • Airspeed remains N1+ but stall shake is now present (Betty still shouting)
  • Sometime soon after that the AT slams the throttles fully closed, the FMC is now over commanding  and the aircraft flat stalls and pancakes in some LA neighborhood 
  • And it behaves pretty much that way over and over no matter what flight plan is in FMC, it happens. When hand flying without AT it seems Ok. 

Any Ideas or suggestions?
TIA,

-Braun

PS...I remember some message appearing in FMC about landing configuration or profile, can’t exactly remember but the message definitely had the word landing in it   Also I’ve not posted in QW forum as of yet but will copy and paste this there also

Thanks again

I’m not surprised the aircraft is a total disaster.

ive had many issues also.

qw is a disaster. I should have opted for a refund.

pathetic.

and don’t even bother on their forums.

they don’t respond at all.

mike

6 hours ago, btacon said:

Hi, keeping it short:

  • P3d V5 HF2
  • QW 787 latest Service Pack (aug 2)
  • Aircraft, while flown seldom has performed as designed at least once
  • I have been putting in some serious hours with PMDG AC FMC and I have adequate skills to fully use the FMC from takeoff to landing

Starting yesterday, after just having flown this flight plan successfully the day before (KLAXKJFK) the Aircraft repeatedly performs  a series of events which result in a spectacular crash in less than two minutes. This is how it goes:

  • Engage AT, departure roll begins as expected
  • 80 Knot callout
  • V1 callout
  • Rotate callout
  • Positive rate of climb, gear up callout.
  • Aircraft is climbing steady and passing 1000 AGL when Betty starts screaming:
  • TERRAIN ALERT. TERRAIN ALERT. PULL UP. WHOOP WHOOP
  • (we’re still climbing)
  • Airspeed remains N1+ but stall shake is now present (Betty still shouting)
  • Sometime soon after that the AT slams the throttles fully closed, the FMC is now over commanding  and the aircraft flat stalls and pancakes in some LA neighborhood 
  • And it behaves pretty much that way over and over no matter what flight plan is in FMC, it happens. When hand flying without AT it seems Ok. 

Any Ideas or suggestions?
TIA,

-Braun

PS...I remember some message appearing in FMC about landing configuration or profile, can’t exactly remember but the message definitely had the word landing in it   Also I’ve not posted in QW forum as of yet but will copy and paste this there also

Thanks again

Flaps?

"Airspeed remains N1+"...say what?  N1 is a power indication (compressor fan speed), not an airspeed.

Make sure you entered load (fuel and payload) in the same units FMC is set to...using lbs when the sim is set to Kgs will result in a massively overweight acft.

Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE
Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@60Hz,
3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090
Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus,
TM TCA Officer Pack
, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case

  • Author
1 hour ago, w6kd said:

Flaps?

"Airspeed remains N1+"...say what?  N1 is a power indication (compressor fan speed), not an airspeed.

Make sure you entered load (fuel and payload) in the same units FMC is set to...using lbs when the sim is set to Kgs will result in a massively overweight acft.

Flaps at 10

What I was implying was power / thrust but said airspeed

Overweight might be a contributor.  I will investigate

Thanks

  • Author
On 9/19/2020 at 8:35 PM, w6kd said:

Make sure you entered load (fuel and payload) in the same units FMC is set to...using lbs when the sim is set to Kgs will result in a massively overweight acft.

Doh!  Fuel and payload completely overlooked by me in the EFB. I am convinced based upon what I saw (fuel tanks at zero) I was running out of fuel 30 seconds after departure. 
This morning I did a fuel and payload in the EFB and Bingo...departure with no issues. 

Thanks very much for the tip. I think that was it. 
 

Best,

-Braun

Archived

This topic is now archived and is closed to further replies.

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.