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.

High fuel flow...

Featured Replies

Hi,Is 6000 pph normal for cruise at 30,000 ft (combined 2 engines of course)? I've looked around and can't find much data on this. Just curious..regards,Macs :)

Macs, That looks about right for two engine std ops at that cruise altitude and normal loading...accoding to the performance charts by Matt Zagoren. They are available on avsim.

first flight hour, above 109,000 of AGW, you burn 9,400 to 10,200 pounds.the next flight hour, in the range above 109,000lbs, at FL320 M.72, 6400 pph.below 109,000 and above 95,000lbs , 6000 pph,below 95,000 and above 89,000lbs, 5400 pph..regards

Gustavo Rodrigues - Brazil

  • Author

Mnay thanks to both for the info! :)regards,Macs :)

>first flight hour, above 109,000 of AGW, you burn 9,400 to>10,200 pounds.>the next flight hour, in the range above 109,000lbs, at FL320>M.72, 6400 pph.>below 109,000 and above 95,000lbs , 6000 pph,>below 95,000 and above 89,000lbs, 5400 pph>..>regardsGreetings.Not sure where you are getting your information, but first hour burn is just over 6000 lbs. Second hour is just under 6000 lbs. and decreasing by approximately 500 lbs/hr. thereafter.I too notice high indicated fuel flow on takeoff and climb. Because of the battery related problem I have yet to fly for a full hour and have not actually checked the burn vs. gauge indications.Take care,Sean

See the FAQ re: the battery bugRegardsBob ScottATP IMEL Gulfstream II-III-IV-V L-300Santiago de Chile

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

the first hour you must add the fuel burned in climb

Gustavo Rodrigues - Brazil

My numbers DO include climb as this will happen in the first hour.

my numbers for climb is 3000 to 3400 lbs burn to climb from MSL to FL300, and than for 3100 - 3200pph per engine.so... 6200 + 3000 = 9200pph in the first hour.next hour is 2900 - 3000 pph per engine...

Gustavo Rodrigues - Brazil

>>my numbers for climb is 3000 to 3400 lbs burn to climb from MSL to FL300, and than for 3100 - 3200pph per engine.so... 6200 + 3000 = 9200pph in the first hour.next hour is 2900 - 3000 pph per engine...<

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.