Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Balanced Field Length & V1

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web

uwochris

Flightinfo's sexiest user
Joined
Dec 21, 2001
Posts
381
Hey guys,

It's my understanding that BFL is the point where your accelerate-go and accelerate-stop distance are equal (i.e. the distance required to experience an engine failure at Vef and come to a complete stop= the distance required to experience an engine failure at Vef, continue the takeoff, and be 35 ft above the departure end of the runway). First of all, is this correct? I'm also under the asumption that it is very good to have runway length in excess of your BFL, as this increases your safety-margin; what happens, however, when you must takeoff from an airport where the TODA is less than your BFL?

Secondly, how exactly is BFL related to V1? The definitions seem similar, except that V1 is defined in terms of airspeed, while BFL is the distance.

Finally, can anyone give examples of how you calculate BFL and what factors affect it?

Thanks in advance,

Chris.
 
Replace your term Vref with V1 and you may have answered your question. Vref is an approach speed and not relevant, V1 is the speed you should have been using. BFL is the length where aborting or going AT V1 are the same distance. V1 is the decision speed. BFL garuntees if you abort prior to V1 you have enough room to stop (usually limited by brake energy) or after V1 continue continue the TO to be 35' above threshold when you cross it.

Calculating BFL (sometimes called TO Field Length) is usually done by looking at tabulated numbers (tab data) that are in the airplane. It's simple. In our plane you go to the section that has your flap setting and altitude for the day. Then you go down the first column to your weight go across the chart to your temp and the book gives you the numbers (V1, Vr, V2, Vref, TOFL). It looks sort of like, and works like, the multiplication tables you studied in grade school

Then there are graphs to correct these numbers for non standard factors like runway slope, anti-ice on, wind, etc because the tab data is calculated on dry, no slope, anti-ice off, no wind, etc.

Also important to remember that the tab data only garuntees meeting certification climb gradient 1.6% which is only good for VFR. If the wether is IFR you may have to lower weight or temps even more to meet the 3.3% required by Terps. Or even MORE for mountainous terrain.

If you find your BFL or TOFL is more than the available runway you can not legally take off. Part 25 certified aircraft HAVE to be able to make it under any circumstance. So you either change flap settings, lower weight, wait for cooler temps, or wait for lower pressure altiude.

Yes, a safety margin is always nice so longer runways are great. But during certification the FAA takes into account that the airplane is not new and you're not a test pilot. So they actually buffer it for you. If your BFL is shown to be 4000' the test pilots may have actually proved it to be 3750'.

Hope that helps.
 
Last edited:
Here's a good overview of part 25 takeoff performance.
http://www.airplanedriver.net/study/part25.htm
V1 is the speed at which you can abort and stop before you run off the end of the runway, or continue the departure on one engine and make the 35-foot screen height at the end.
If you don't have balanced field, and you're in a part 25 airplane, you wait for it to cool off, leave some folks (or golf clubs) behind, or offload fuel.
Every part 25 airplane will have perfomance charts for BFL and second segment climb, and yes, we do the calcs for every takeoff.
 
guido411 said:
Replace your term Vref with V1 and you may have answered your question.

Hope that helps.

The term he used was "Vef" (speed @ engine failure) and not "Vref" (approach speed). He is using the term correctly. The definition he quoted is exactly word for word from the official FAA definition. The same definition apprears word for word in our company manuals.
 
Yank McCobb said:
The term he used was "Vef" (speed @ engine failure) and not "Vref" (approach speed). He is using the term correctly. The definition he quoted is exactly word for word from the official FAA definition. The same definition apprears word for word in our company manuals.

Whoops,

Thanks Yank. Little dylexic this morning I guess.
 
Hey, not a problem. The first time I saw that in the book I had to do a double-take, as well.

Then again, when you get to be my age, schmalzheimer's disease is a daily battle.:p
 
It's my understanding that BFL is the point where your accelerate-go and accelerate-stop distance are equal (i.e. the distance required to experience an engine failure at Vef and come to a complete stop= the distance required to experience an engine failure at Vef, continue the takeoff, and be 35 ft above the departure end of the runway). First of all, is this correct?


Pretty much the standard definition, yes. Going a little bit further though and to help answer some of the other questions you have posed. The present day definition acknowledges that if there is an area beyond the runway over which an aircraft could safely fly after becoming airborne, ( the clearway ), then it would become unnecessarily restrictive to stipulate that the airborne distance to the screen height should be accomlished within the runway length. Also, if there should be a suitable area beyond the runway, that the aircraft could use for stopping in the event of an aborted take off ( a stopway ) then it again becomes restrictive to stipulate that the aircraft should be able to stop within the actual runway length.

A Balanced Field Length, then, is the distance within which an aircraft can;

a. Accelerate to V1 and then execute a stop within the Accelerate Stop Distance Available ( ASDA ), where ASDA = TORA + Stopway and;
b. With an engine failure at V1 continue the take off and cross the screen within the Take Off Distance Available ( TODA ), where TODA = TORA+Clearway.

In other words, Balanced Field Length exists whenever ASDA = TODA

When ASDA is greater than TODA ( i.e. with a Stopway only ); or when ASDA is less than TODA ( i.e. with a clearway only) then you have an Unbalanced condition that is still legal.

That brings us to:

Secondly, how exactly is BFL related to V1? The definitions seem similar, except that V1 is defined in terms of airspeed, while BFL is the distance.

Take a situation where you have a clearway. With the clearway you have more distance in which to reach your 35 foot screen height. It would make sense then that you could take off with a heavier weight. But, wait a second, if we are heavier it would take longer to stop on the available pavement, right ?. In this case, you could reduce the V1 by using a higher flap setting. The higher flap setting allows you to reduce the V1 and get airborne a little earlier, but it also increases your distance to reach 35 feet since the climb rate is slower.

Does that help ?


TP


p.s. some of this was plagiarized from a book on performance.
 
Last edited:
Thanks for all the responses guys!

TP- just one comment here: I the definition I have seen for TODA is TORA+Clearway (i.e. no stopway). I'm not sure if this makes much of a difference or not, but I have never seen TODA defined to include the stopway.
 
typhoonpilot said:
p.s. some of this was plagiarized from a book on performance.

Hey, Typhoon, what's the name of the book? I'm looking for something like that.
 
TP- just one comment here: I the definition I have seen for TODA is TORA+Clearway (i.e. no stopway). I'm not sure if this makes much of a difference or not, but I have never seen TODA defined to include the stopway.

Oops, right you are. I was referencing an Australian diagram and it was written on there so I just wrote it down without thinking. Perhaps what they were thinking is that stopway may be part of the area designated as clearway.


Found this in some further research, you might find it handy:

http://www.wingfiles.com/files/GTG_perfo.pdf

Hey, Typhoon, what's the name of the book? I'm looking for something like that.

Understanding Performance by A.J. Walters


TP
 
Last edited:
The only thing I'd like to add is that your balanced field length does not have to equal the runway length. So..to refine the definition, you have a balanced field length if your accelerate stop/accelerate go distance is equal. If you lose an engine and reject at V1, you will stop within the balanced field length. If you continue, you will reach a 35' screen height at the end of the balanced field length. That explains the second part of your statement that it is good to have excess runway beyond your BFL. An example would be taking off on a 10K long runway. At max power, in a light aircraft, your balance field length may only be 5000'. That would leave an excess of 5k of runway. You could elect to utilize the extra runway, by making a derated takeoff, change flap settings etc. You may need to use it for a contaminated takeoff, or some other non-normal situation. Of course, you will also recalculate your V1, thereby extending your BFL. You can do that untill your BFL equals the runway available. (Some operators will also use clearways and stopways, don't want to speak for them). Didn't mean to be longwinded, that's how we teach it at our company.
 
Not meaning to totally muddy the waters, but as the previous posting (and others) implied most tabbed data that gives you a V1 number is a balanced field length number (go dist = stop dist at that v1) and indeed knows nothing about actual field length. Most tabbed data also gives you the balanced field length or runway required. But....in case of say contaminated runways V1 may be adjusted, ie reduced, thus giving you an UNbalanced field length. go dist > stop dist. But then there is a corresponding adjustment to runway required also.

Manufactors seem to always publish balanced field length in their brochures. Its a marketing ploy because it implies the shortest runway you can use for takeoff. They usually leave out things as gross weight, temperture, field elevation, etc used to compute the balanced field length.
 
Balanced-field numbers in the manufacturers' brochures are generally based on MAx takeoff weight, ISA, sea level, dry pavement. But they do sometimes fudge in creative and interesting ways, like having a published max takeoff weight of 35,800#, which gives good balanced-field/second-segment numbers whilst leaving you room for only 5 pax with a full tank of gas. Then, they offer an 'upgrade' to bump your takeoff weight to 36,500, making the airplane almost capable of taking full fuel an full seats. This 'upgrade' consists of sending the manufacturer a check for $2,500 and receiving an insert for the AFM (!)
Your plane is now a lot more useful, and they can advertise good takeoff performance 'at gross weight' without being called liars.
 
Last edited:
Uwochris

Balanced field length is more applicable to transport category aircraft type certificated under Part 25. Looking at your data by your name, most of your expeirence has been and probably will be for the next while in Part 23 aircraft. Most part 23 airplanes don't have any balanced field data published, and for the single engine aircraft, most don't have accelerate-stop data published either (and certainly not accelerate go...;) ).

Balanced field length occurs by manipulating V1, or your decision speed. This speed represents the point at which you either stop or go, in a nutshell, or more specifically, the point at which you have decided to stop or go. My manipulating this number, the distances for accelerating and going, or accelerating and stopping can be adjusted. That's the theoretical world.

Reality is that the aircraft needs a certain amount of speed or steam to get off the ground, period. Manipulating the decision speed doesn't change that...it's still going to require that amount of room to get off the ground and go. One could merely call this rotation speed.

Prior to any departure in a turbine airplane, Takeoff and Landing Data is calculated. This includes the distances discussed in this thread, as well as several different airspeeds. V1 will be the decision speed, Vr will be the rotation speed, and V2 will be the speed that we first seek right after coming off the ground to ensure our initial climb performance.

If we reduce V1 to a lesser value (manipulate it) to come up with a "balanced field length," we are saying that by aborting sooner, we will use less distance to get stopped, because we have less energy to stop. We are also saying that we will need to accelerate longer on one engine, because we still need to reach that rotation speed and that initial climb speed, V2.

The numbers tell us that we can do it within the balanced field distance given, and that we'll reach a height of 35' at the end of that distance if we continue. In a part 25 airplane, the numbers have to work...sometimes folks like to say the performance is gauranteed. While that's not entirely true, the numbers in the Part 25 airplane have been demonstrated and verified in testing. In a part 23 airplane, this is not the case. Most of the numbers in your performance charts are theoretical, interpolated from some testing and some calculations. You are not gauranteed any particular performance after takeoff, or in a light twin, even in acceleration-go data. What you have before you is theory.

Manipulating down the decision speeds on takeoff may make the airplane legal, but may not do a darn thing but lull you into putting the airplane into an undesirable condition in a place where you don't want it.

Particularly in a Part 23 airplane, you should always plan on book performance plus your own margin of safety, at a minimum. I like to call that your own PFR's, or personal flight rules. The book says you can get off the ground with an accelerate go performance of 3,500', but you won't accept anything less than five thousand feet. Nothing wrong with that.

Once you've decided to set and stick by your own personal minimums, you need to consider the other factors that affect your performance. Once you do accelerate and go, how is the climb performance today, based on density altitude, and what kind of terrain do you have around you, and how comfortable are you climbing out on one engine...or executing a forced landing off the end of the runway? If you're not comfortable with that idea, if the density altitude won't allow you the climb performance, or if terrain and obstacles are too great to allow you safe passage out of the area or back around for another landing, what difference does it make if you have enough runway to takeoff? What you really have is adequate runway to crash off field. No performance chart tells you about that...it's something you have to consider under the circumstances.

Tabular data is great, but it's seldom if ever available for part 23 airplanes. You need to look at multiple charts and combine the results to decide if you can take off, and what you can do after you take off.

Switching back to the runway again, consider your accelerate-stop. The book states that you can get stopped within a certain distance, balanced field or not. So what? Can you do it, and would you want to? One of the most dangerous things you can do is accelerate and then do a high speed abort. The fact that the book says you can do it within a certain distance may be misleading.

If you're in a propeller airplane, turbine or piston, the numbers you get will be based on a feathered climb to get away from that runway if you decide to go. Some aircraft, turbine airplanes, utilize autofeather systems that are supposed to be checked before each takeoff, be operational, and turned on, each time. but what if one fails, or if you are unable to feather? I've certainly experienced that...and once in a four engine airplane, was unable to feather and do much more than stay at tree top level while getting the airplane turned around and landed. It caused enough consternation that once we disappeared from site, the base called out crash rescue because it was presumed we had crashed.

With all four turning for all they could and one doing it's darndest to hold us back, we could hardly maintain altitude. We couldn't feather because we'd lost our oil, which was covering the engine and wing, and had nothing left in that system to drive the prop to feather. You're probably taught in whatever you're flying that loss of oil pressure will cause the prop to feather, but don't count on it, and not all aircraft will do that.

The point is that there's more to the equation that merely playing with V1 to get numbers you want. Artificially moving the decision numbers down a little doesn't change the fact that the aircraft still requires a certain amount of airspeed and energy to go flying, and to get around and over whatever might be out there once it does. One can crunch the numbers all day to make the paying public feel good, but those numbers mean very little where the rubber stops meeting the road and the wing meets the air, especially in a part 23 airplane.
 
Bfl

And for what it's worth, all data for part 25 accelerate-stop calculations do not include the use of thrust reversers.
 

Latest resources

Back
Top