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.

How to find out what's causing the warning beep during takeoff

Featured Replies

  • Author

How do I check for calibration? In windows? or FSUIPC?

Mehmet Yatan

  • Replies 34
  • Views 6.4k
  • Created
  • Last Reply

Top Posters In This Topic

Could you perhaps post a screenshot showing from the annunciator panel down to the fuel cutoff levers in the VC while you are getting this warning? It will make things a bit easier to diagnose.

Bryan Richards

 

"People depend so much on automation that they forget how to get the automation to work." B.W.

Toe brakes should not be setting off the T/O config warning.

Banner_FS2Crew_Tech_Team.jpg
  • Author

Could you perhaps post a screenshot showing from the annunciator panel down to the fuel cutoff levers in the VC while you are getting this warning? It will make things a bit easier to diagnose.

 

I'm sorry, I dont know what panel you are asking. I dont see any warning panels by the fuel cutoff levers. The only panel I know of consists of red and yellow lights on the MCU.

Mehmet Yatan

I'm sorry, I dont know what panel you are asking. I dont see any warning panels by the fuel cutoff levers. The only panel I know of consists of red and yellow lights on the MCU.

 

yes thats the panel i am talking about, include that plus the flap indicator all the way down to the fuel cutoff levers all in one shot if you can, but before you do that, try reloading one of the default panel states and see if the problem persists, if it still does then take the screenie.

Bryan Richards

 

"People depend so much on automation that they forget how to get the automation to work." B.W.

It's a long shot but if you are using Accufeel the stall warning setting might be doing it.

Supporter.png

 

John

You're hearing the t/o configuration warning horn. The four things that cause this are:

1) speedbrake level not fully down

2) parking brake on

3) Not within t/o trim limit (green band)

4) Not a take of flap selected (1-25). I don't actually know if flap 2, which is not a t/o flap, will actually cause a config warning.

Nobody read this post... it is the only correct answer here.

No FD, no autopilot, no fmc, no other strange things like doors.

Only the basic things needed for a safe take off.

The 5th point are the throttles.

If advancing throttles you get the warning for sure you have a wrong setup of the plane (or a failure in the flap/slat systems).

It sounds if

1) Flaps must be in the range of 1 to 25 (2 included). Slats/LE flaps must be all green.

2) Parking brake must be released

3) Spoilers must be stowed (no ARMED or DO NOT ARM lights)

4) Stab trim must be in the take off range, green band area.

5) Throttles in one of the above conditions must be at idle.

 

Flap asymmetry, flap skew, slat transit or similar failures will also trigger the warning.

If sound is played also with all the above working and configured, and is played with throttles at idle, the only remaining thing is the cabin altitude aboe 10000fts, but this means that either your wheater and/or your airport has a ground pressure equal or above the pressure you have at10000ft of altitude.

All those things can be easily checked on the panels.

TAKE OFF WARNING or CABIN ALTITUDE WARNING WILL NOT TRIGGER ANY LIGHT ON THE MASTER CAUTION.

Regards

Andrea Daviero

If you are starting on the runway it could also be the chocks are still set. Just releasing the parking brake will not remove the chocks. You must do it in the FMC.

Make sure that your APU bleed switch is turned off and your engine bleed switches (1 and 2) are turned on. This is found at the middle right of the overhead panel. Also don't forget at the bottom right of the overhead panel, you should see this knob ALTN, make sure that the knob is selected to AUTO.

 

As other people said before check flaps, trim etc.

Anthony

 

 

pmdgngxpilot.png

Boeing777_Banner_Pilot.jpg

 

If you are starting on the runway it could also be the chocks are still set. Just releasing the parking brake will not remove the chocks. You must do it in the FMC.

 

Think if you read the op question hes rollng down the runway for takeoff when he hears the beep beep so the chocks are removed already and he mentions it again in another post it stops at 80

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

 

Peter kelberg

Don't wanna be Mr. Know-it-all, but it's what Vagabondo or davierosoft said. Nothing more, nothing less.

 

Sometimes I wonder if people actually read the input they get here... ;-)

 

If you can exclude any one of those points, you might have a bug and should probably open a support ticket.

 

Regards,

 

Oli

 

 

Oliver Branaschky

Oliver Branaschky

 

hrdk65U.jpg

If you set the flaps *just* before T/O, then the LE devices may still be in transit. It sometimes takes a few seconds for them to reach their 'extended' detente. Watch for the orange "LE Devices" annunciator in the middle of the main panel. Wait for that to go out before your roll.

 

HTH,

 

n.

Dr. Nick Walton

DBA/IT Specialist

Durham, UK

  • Author

No actually I found out what the problem is. When I load NGX, it has flaps 1 setup, engines are running, etc. When I load the cold and dark panel, the flaps 1 stays the same, it never goes to retract, but the flaps are retracted. So if you look at the flaps indicator circle panel thing, it will show 1 and even the flap lever shows as 1. You have to extend the flaps to 5 or 10, then retract all the way, then extend them back to 1. Then no more warning sounds. I have confirmed that this is the behavior 5-6 out of 10 times. It does not always happen. I did the same steps over and over again, there is a 50% chance it happens, but when it happens, this is the cause.

 

I'm no pilot or an aviation expert, but have been flying with payware addons in FSX for years now in VATSIM and trust me, I know the right configuration for takeoff - I just thought with NGX, there may be some weird setting that I missed somewhere that is causing a glitch which is why I asked here.

Mehmet Yatan

How long does it last? This also happens to me sometimes when I set to/ga for takeoff. But it eventually goes away. I would make sure you have everything set up properly.

You are obliged to abandon your take-off if the TOCW horn sounds.

3VlzBGn.jpg?1

Super VC10 into LOWI with PF3 at a cinema near you

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

 

I'm no pilot or an aviation expert, but...

Nor am I, but I am pretty sure that one of the configuration steps from a cold and dark cockpit involves verifying that the flaps indicated matches the flap lever position.

Paul Smith.

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.