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.

"positive rate" call to early (in my opinion)

Featured Replies

As the title says, the FO starts immediately after Takeoff his "positive rate" call. Even before any positive rate is shown on the displays.

 

Maybe something for a next update.

Andreas

As the title says, the FO starts immediately after Takeoff his "positive rate" call. Even before any positive rate is shown on the displays.

 

Maybe something for a next update.

 

Hi

 

It's fine for me, i see the altitude increase on the RA and the VSI.

Banner_FS2Crew_Tech_Team.jpg
Damien Weekes
Captain 737NG / A319/20/21

Hi

 

It's fine for me, i see the altitude increase on the RA and the VSI.

 

Ditto

Kind regards

Peter

Ditto

 

Maybe it's something else ? What FPS do you get ? Could it be a slowdown pf some sort ? If you get low FPS at that point it could appear not to move (happened to me before)

Banner_FS2Crew_Tech_Team.jpg
Damien Weekes
Captain 737NG / A319/20/21

Maybe it's something else ? What FPS do you get ? Could it be a slowdown pf some sort ? If you get low FPS at that point it could appear not to move (happened to me before)

 

What I meant was, that it is also fine for me.

Kind regards

Peter

works fine by me too

I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card,  RM850 power supply

 

Peter kelberg

  • Author

"Positive rate" should not be called below screen height. So anything below 50ft iis an incorrect call due to ground effect.

vololiberista

 

+1

Andreas

  • Commercial Member

"Positive rate" should not be called below screen height. So anything below 50ft iis an incorrect call due to ground effect.

 

Never read that one before.... sounds like some esoteric pedantry from the JAA.

 

I think the Boeing FCOM just says altimeter increasing and VSI showing a positive rate of climb.

Never read that one before.... sounds like some esoteric pedantry from the JAA.

 

I think the Boeing FCOM just says altimeter increasing and VSI showing a positive rate of climb.

+1 as long as the alt is increasing and vsi is showing a positve rate is all you got to worry about

I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card,  RM850 power supply

 

Peter kelberg

+1 as long as the alt is increasing and vsi is showing a positve rate is all you got to worry about

 

Agree.

Kind regards

Peter

+1 as long as the alt is increasing and vsi is showing a positve rate is all you got to worry about

Sorry boys! You need to learn some piloting skills.

Let's then assume that you see the indicator show a rate of climb but are still in ground effect i.e 10-20ft agl. You call "Positive Rate" and promptly stall because you have over rotated!!

Waiting till you are above screen height and out of ground effect is good airmanship at the very least! And, to avoid any arguments It "is" the correct technique! For example in the VC10 model for Fs2004 "positive rate" is set at 50ft which also coincides with the end of the rotation manoeuvre and v2 having been passed. So the actual call is heard a little higher at about 60ft. (you would be surprised just how quickly a jet gets there!!) If you or the model in question is calling "positive rate" before v2 then it most definately is too soon. And as has been said it could also be due to lag in your PC. If the coding triggers "positive rate" above 35ft then that's ok provided that you have attained v2.

 

vololiberista

3VlzBGn.jpg?1

Super VC10 into LOWI with PF3 at a cinema near you

https://www.youtube.com/watch?v=298UDyNmgUA

 

It come right as the wheels unstick. Which, to me ( not a real pilot ), is too soon.

Kevin M. Manley

It come right as the wheels unstick. Which, to me ( not a real pilot ), is too soon.

That most certainly is too soon! It's either a quirk in your pc setup or it's coded to do that. The latter is quite incorrect and should be corrected. In a real life situation that would be an extremely dangerous manoeuvre. Again using the VC10 model. From time to time I have encountered an engine fire imediately after rotation ((sometimes a double failure) equivalent to a bird strike) "positive climb" and "Gear up" calls are still made but take into account the correct v2 speed.

 

Minium climb speed Flaps up/Slats out v2+20

Minimum Slat retraction speed v2+45

Minimum speed flaps up/Slats in v2+60

Engine fire drills secondary when convenient

 

Even in this situation you wait until you have passed your all engines v2 before calling "positive climb" etc.

vololiberista

3VlzBGn.jpg?1

Super VC10 into LOWI with PF3 at a cinema near you

https://www.youtube.com/watch?v=298UDyNmgUA

 

  • Author

At least I am an "armchair aviator" as well.

But if you compare to the countless real life videos on Youtube, in my opinion the call is way to early.

I know that this is a minor issue, but it is not like real life, period.

 

Maybe something is wrong with my setup, but I have no idea what exactly.

Andreas

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.