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.

Black Square Duke Released!

Featured Replies

2 hours ago, martinboehme said:

What would a typical approach speed be in the Turbine Duke? I've looked in the manual but wasn't able to find anything immediately relevant

It does give a Vs0 of 70 knots, which by the typical rule of 1.3 Vs0 would give an approach speed of 91 knots, but sometimes individual types deviate from this rule. 

100KNOTS - info listed on the wall placard - co pilots side.

Jase

Jaseman. Lovin it up here........

Catch us over at MassieSim32 -> https://discord.gg/B4buuHGhcr

  • Replies 636
  • Views 112k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • Guys, just to let everyone know that a few hours ago new official simbrief profiles have been added, for all the dukes they are named BE60, BE6G and B60T https://forum.navigraph.com/t/b60t-s

  • MattNischan
    MattNischan

    I'm not totally sure where this information comes from, but that is not accurate. At the core is, the sim does not support hot swapping avionics. We have advised developers against utilizing hot

  • I'd say FlySimWare Cessna 414 if it can't be the Duke.

Posted Images

4 minutes ago, precog said:

You probably need to be in beta for taxing

I admit, my turbine experience is minimal, so I understand that's below idle, i.e towards reverse? That will probably do the trick.

[MSI MPG X870E Carbon | 9800X3D (PBO +200Mhz / -20 Offset) | Corsair 64GB DDR5 (Custom Timings) | RTX 4090 Founders Edition (Undervolted) | WD SNX 850X 4TB + 4TB | Antec Flux Pro]

 

3 hours ago, sloppysmusic said:

Ignore this if irrelevant, just a shot in the dark as I've occasionally forgot this myself. You DO have VLOC selected on TDS before ILS intercept yes? 

I thought so, but I'll check again. I think the issue might be that I didn't change the mode in the plane, from GPS to NAV. 

Generally, the TDS switches that automatically.

 

With no disrespect at all to the former title holder of King of the MSFS Prop Twins, but... "The C414 is dead, long live the Duke!"

(Although I know I'll be flying the C414 quite a bit in the future too, just because it's still great).

"That's what" - She

3 hours ago, Stoopy said:

I only had time for one trip around the pattern at KSBA last night but hand-flew the ILS approach for runway 7 just fine.  I was in the basic piston version for starters, configured with the KLN90 and TDS for maximum fun.  After setting the ILS frequency I just selected VLOC on the upper left corner of the panel and everything tracked perfectly on the HSI.

Very first landing with this bird was a gentle kiss of the tires at -48fpm right at the touchdown marker.  Love this thing already!

Thanks, I think that button and the combination with the TDS CDI selection might be where I went wrong.

Hand flying it is SO easy and it slows down SO easily, that, while I love it, I wonder if it's "real"? This is with the Turbine version.

17 minutes ago, Sethos said:

What's the correct way of taxiing this thing smoothly? I don't use rudder pedals, so I don't have the smooth breaking axis and rely on my old trusty joystick trigger to apply brakes, which works in most planes. However, this thing taxis like a scolded proverbial, so it's just this constant rocking motion of picking up speed and slamming brakes 😅

Taxi in beta thrust.  You shouldn't need to even touch the brakes unless maybe in a sharp corner or approaching a hold short line.  So basically put your throttles a bit under the detent in tht cockpit.youll hear a little click sound when you do.

My Liveries | FAA ZMP | PPL ASEL |
| Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |

 

 

Anyone know where the Beta indicator is that is referred to in the manual? I might have missed it, but I want to be sure I know when I'm in Beta and I can't find the indicator. As I understand it, Beta will be the lowest 15% of the throttle range and then reverse is activated as regular reverse range?

1 minute ago, ryanbatc said:

Taxi in beta thrust.  You shouldn't need to even touch the brakes unless maybe in a sharp corner or approaching a hold short line.  So basically put your throttles a bit under the detent in tht cockpit.youll hear a little click sound when you do.

I'll give it a try, thank you.

[MSI MPG X870E Carbon | 9800X3D (PBO +200Mhz / -20 Offset) | Corsair 64GB DDR5 (Custom Timings) | RTX 4090 Founders Edition (Undervolted) | WD SNX 850X 4TB + 4TB | Antec Flux Pro]

 

8 minutes ago, mmcmah said:

Anyone know where the Beta indicator is that is referred to in the manual? I might have missed it, but I want to be sure I know when I'm in Beta and I can't find the indicator. As I understand it, Beta will be the lowest 15% of the throttle range and then reverse is activated as regular reverse range?

There’s small red lights in the top left/right of the prop rpm gauges that lights up when in beta.

Gary

 

i9-13900K, Asus RTX 4080, Asus Z790 Plus Wi-Fi, 32 GB Ram, Seasonic GX-1000W, LG C1 48” OLED 4K monitor, Quest 3 VR

 

33 minutes ago, sloppysmusic said:

Some interesting details on all variants in this page:

Beech Duke (Aviation Consumer)

TLDR Addition 😄

A Grand Duke fully modded has lower stall speeds-78 knots compared to 82 knots on a stock airplane in the clean configuration, and 70 knots compared to 76 knots on a stock airplane in the dirty configuration. The short-field approach speed is drastically lowered to 77 knots with a BLR-modded Duke, compared to 99 knots for a stock airplane, according to the BLR. You’ll see better climb, too, when equipped-nearly 350 FPM better when both engines are making best power. The new gross takeoff weight of a fully equipped Grand Duke is 7000 pounds, compared to 6775 on a stock airplane.

Great! Of course you can fly below Vmc and see how it playout in case when critical engine quit and you have to do go around

Life time flight sim enthusiast, current airplane owner 172P (past C182F). FAA CP/IR ASEL/AMEL, FI ASEL

My System: AMD Ryzen 9 9950X3D , MSI X870 GAMING PLUS, 64G RAM, ASUS RTX5090, 4T SSD

Put my hands on (pic/dual/given)

7GCAA, 8KCAB, BE24, BE76, BE35-C33, BE35, C150, C152, C172B/N/P/R/SP, 182F, M20E,M20C, M20J, AT6(SNJ4), PA28-140,PA28-151, PA28-161,PA28-181,PA28RT-201,PA28R-180/201T, PA24-250, PA32-300R, PA44, AC114, YAK-18T, YAK-52, SR22

 

15 hours ago, regis9 said:

I'm using the TQ6, but I found that by changing the assignment in FSUIPC to send as a directly MSFS axis (probably don't have that wording exactly right) and then assigning my levers to mixture, I could get them to contrl the mixture, but the levers in the aircraft wouldn't actually move.

I'm not sure why it's always the mixture levers if there's going to be a problem with addon planes and FSUIPC assignments...

I have the same issue, using the Bravo and AAO. The mixture axes mentioned in the manual are actually in my default template but they don't work, at least not visually.
The variable also does not seem to work. For now I have assigned the mixture within MSFS but I hope a better solution comes up.

I also had issues with my PMS50 GNS: the flightplan from within MSFS did not appear in the GNS nor could I manually add it. When switching to the default WT 530, the flightplan was listed twice (KGSP-KMYR KGSP-KMYR). the stations in between those airports were gone and both legs were active.

Edited by orchestra_nl
GNS

Flightsim rig:
CPU: AMD 5900x  | Mobo: MSI X570 MEG Unify | RAM: 32GB G.Skill Trident Z Neo | GPU: Gigabyte RTX 3090 | Storage: M.2 (2 & 4 TB) | PSU: Corsair RM850x | Case: Fractal Define 7 XL
Display: Acer Predator x34 3440x1440 | Speakers: Logitech Z906 
Controllers: Fulcrum One Yoke | MFG Crosswind v2 pedals | Honeycomb Bravo Quadrant |Thrustmaster TCA Quadrant | Stream Deck XL & Plus | TrackIR 5 Tobii eye tracking

Same here - mixture works but the levers don't move visually except for full rich or cut off. I don't use FSUIPC. 

 9950X3D - X870E Aorus Master- TUF 5090 OC - 64GB DDR5 - 1500W HXi - Titan 360 RX LCD - 9100 Pro x 2  - LG 45GX950A - HOTAS Warthog with Ava Base

From the videos I watched I was just a bit perplexed with the rocket climb rate ???

Is that realistic ??? At a given instance it was climbing in excess of 3000 FPM after takeoff and trying to mantain 120 KIAS ???

Edited by jcomm

Flying gliders since 1980

Flightsimming since 1992

AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)

10 minutes ago, jcomm said:

From the videos I watched I was just a bit perplexed with the rocket climb rate ???

Is that realistic ??? At a given instance it was climbing in excess of 3000 FPM after takeoff and trying to mantain 120 KIAS ???

Plane has a maximum climb rate of 4000, they are absolute rocket ships.

[MSI MPG X870E Carbon | 9800X3D (PBO +200Mhz / -20 Offset) | Corsair 64GB DDR5 (Custom Timings) | RTX 4090 Founders Edition (Undervolted) | WD SNX 850X 4TB + 4TB | Antec Flux Pro]

 

12 minutes ago, jcomm said:

From the videos I watched I was just a bit perplexed with the rocket climb rate ???

Is that realistic ??? At a given instance it was climbing in excess of 3000 FPM after takeoff and trying to mantain 120 KIAS ???

Yes it is.. yeeees it is. The turbine duke is a rocket

Juan Ramos
 

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.