Wikiposts
Search
Tech Log The very best in practical technical discussion on the web

V1

Thread Tools
 
Search this Thread
 
Old 24th Aug 2009, 14:06
  #1 (permalink)  
ENTREPPRUNEUR
Thread Starter
 
Join Date: Jun 2001
Location: The 60s
Posts: 566
Likes: 0
Received 0 Likes on 0 Posts
V1

I was about to answer a question on a different forum about aborting a take-off due to a passenger event. I realise I can't remember what the V speeds are for.
Looking on the Internet gives a mixture answers relating to two separate constraints. The first is the speed that allows you to take-off with a single engine failure. Below this you must stop. The second constraint is the speed which is highest you can stop within the length of the runway. When these are the same, you have the maximum weight for the runway in question, but in general they won't be unless you de-rate. So what are the two names for the two different speeds? When you call V1 what are you saying - you can continue or you must?
twistedenginestarter is offline  
Old 24th Aug 2009, 14:51
  #2 (permalink)  
 
Join Date: May 2008
Location: europe
Posts: 89
Likes: 0
Received 0 Likes on 0 Posts
A very basic answer.
The two V1's normaly called low/high speed V1. The below the low speed V1 you must stop, so the high speed V1 you can just stop......
Normaly the company decides if its a go/stop airline, either it uses hi or low or even mid way. But I think most airlines use a lower V1 and would be a GO company.

Now ducking from all the flack thats coming my way.
TckVs is offline  
Old 24th Aug 2009, 15:23
  #3 (permalink)  
 
Join Date: Dec 1998
Location: Escapee from Ultima Thule
Posts: 4,273
Received 2 Likes on 2 Posts
Like you said, V1 is selected from within range of speeds. Upper end = maximum speed where stopping is still possible & the lower end = minimum speed where a continued take-off is still possible. WAT, TODA & SDA affect those limits, reducing the gap to zero as they converge to a balanced field length.

Continuing the take-off (from a lower V1) is mutually exclusive to stopping (from the higher V1). Once you continue through Vr you're no longer in a situation covered by performance data for stopping - so a higher V1(stop) can't apply. Once you start stopping then you're no longer in a situation covered by performance data for continuing the take-off - so a lower V1(go) can't apply either. End result: a single V1.

No doubt it would be possible to have a range of V1s for each take-off, each for various criteria, but the continue & stopping performance can be so
critical that taking time to decide which applies & then acting would lead to an unacceptable risk. A significant point about using a single V1 is that it simplifies decisions at a critical time ie above you go, below you stop.
Tinstaafl is offline  
Old 24th Aug 2009, 17:05
  #4 (permalink)  
 
Join Date: Aug 2009
Location: Germany
Posts: 72
Likes: 0
Received 0 Likes on 0 Posts
V1 is called the decision speed, at which the decision to abort or to continue a takeoff must have been made.
Vmcg is the lower limit for V1 and the lower of
a) VR or
b) VMBE or
c) the speed at which the accelerate stop distance equals runway lengh available (+stopway)
the upper limit for V1.

However, V1, is critical for the length of the takeoff distance and the length of the accelerated stop distance.
A lower V1 results in a longer takeoff distance (longer acceleration with engine out) but shorter accelerate stop distance (braking starts earlier).
A higher V1 has opposite effects, takeoff distance becomes shorter and accelerate stop distance becomes longer.

In case the choosen V1 is such that takeoff distance equals the accelerate stop distance, it is called a balanced V1 or balanced field length.

Balanced field usually results in the highest takeoff weight achievable, unless a clearway or stopway is available to further increase the takeoff weight.

So generally, for an actual flight the V1 is choosen from an available range of V1 between minimum and maximum V1. During takeoff, there is only one V1 used, the choosen or calculated V1 according to the requirements for the given takeoff.

On a wet runway a lower V1 is generally more desirable as poor braking conditions may exist and increasing the available stopping distance will increase the safety margin.
TheWanderer is offline  
Old 25th Aug 2009, 02:41
  #5 (permalink)  
Registered User **
 
Join Date: Mar 2009
Location: USA
Age: 49
Posts: 480
Likes: 0
Received 0 Likes on 0 Posts
As stated above simply it is the safe speed calculated to abort a takeoff. This is at the pilot's discretion, engine failure no doubt, each aircraft has different operating limitations.

A passenger event would be an unlikely one allthough possible as it is a relitively shory piriod of time between commencing T/O and V1. Just about all aborted T/O's are due to system failures.
muduckace is offline  
Old 25th Aug 2009, 03:51
  #6 (permalink)  
 
Join Date: Nov 2008
Location: In the torpedo tube above!
Posts: 212
Likes: 0
Received 0 Likes on 0 Posts
So with the above in mind,what would be the V1 for my single engine Cessna 172.....
Flaperon777 is offline  
Old 25th Aug 2009, 05:02
  #7 (permalink)  
Moderator
 
Join Date: Apr 2001
Location: various places .....
Posts: 7,183
Received 93 Likes on 62 Posts
So with the above in mind,what would be the V1 for my single engine Cessna 172

V1 is not defined for and, from a certification point of view, irrelevant to light aircraft operations.

The generally accepted definition these days is along the lines of "if you have not already commenced stopping by V1, keep going". This assumes, of course, that the aircraft is within the accepted certification parameters and capable of flight.
john_tullamarine is offline  
Old 25th Aug 2009, 09:52
  #8 (permalink)  
 
Join Date: Jul 2001
Location: Australia
Posts: 4,955
Likes: 0
Received 1 Like on 1 Post
V1 is called the decision speed, at which the decision to abort or to continue a takeoff must have been made.
Folks,
This is a very common misconception, see a very useful little book:

http://www.faa.gov/other_visit/aviat...off_safety.pdf

In particular, page 2.10. V1 is the speed at which the takeoff should be continued if the abort has not already been commenced.(unless is a catastrophic failure and the aeroplane will not become safely airborne -- cf; PANAM on 34 (L) in Sydney, multiple engine failure at gross weight)

The effect of this has been incorporated, with a number of useful amendments, from the original SFAR 422B through to the present amendment level of FAR 25. The words in italics appear elsewhere in FAA Docs. Not withstanding all of the above, in many other FAA Docs., they persist in calling V1 the "takeoff decision speed" ---- confusing, unless you accept it for what it is, the decision to take off ---- what it is NOT, is the stop/go decision speed.

Despite the best efforts of airline training departments, and I can speak of three on this subject, United, Delta and Qantas, V1 being referred to as the stop/go decision speed persists, including being incorrectly defined in several well known training texts, and many training school course notes.

Tootle pip!!
LeadSled is offline  
Old 25th Aug 2009, 13:54
  #9 (permalink)  
 
Join Date: May 2000
Location: Glorious West Sussex
Age: 76
Posts: 1,020
Likes: 0
Received 0 Likes on 0 Posts
From a recent EASA amendment to something..... they seem to agree with the FAA..
"the speed V1 (at which the pilot is either continuing the take-off or is initiating the first action to abort the take-off)".
That's the important bit - initiate the first stopping action by V1.

Or in simpler terms... Happiness is V1 at Lagos ....
TyroPicard is offline  
Old 25th Aug 2009, 16:52
  #10 (permalink)  
 
Join Date: Aug 2009
Location: Germany
Posts: 72
Likes: 0
Received 0 Likes on 0 Posts
Boeing has a fantastic training video for this, the video is called "The Go - No Go decision" as far as I remember.
Unfortunately I don't know where the video is available except from Boeing.
But maybe you can ask your training department if you like to see this video?
TheWanderer is offline  
Old 26th Aug 2009, 01:28
  #11 (permalink)  
 
Join Date: Jul 2001
Location: Australia
Posts: 4,955
Likes: 0
Received 1 Like on 1 Post
Folks,
As a quick PS to this thread, it is instructive to look at the record of high speed aborts, caused by engine failures --- the conclusion I draw is, don't get too worked up about runway remaining at V1, in the event of an engine failure, you are going off the side due to loss of of directional control.

Getting the thrust levers back on the stops is, based on the statistics, even more important than getting on the brakes, to achieve a successful rejected takeoff. An abort brief: "Thrust off, brakes on" --- in that order ---- separated by milliseconds --- any more than that, either psychologically or in practice, and the statistics say you are a candidate for off the side.

As for the arguments about "autobrake" versus good old feet ----- that's a whole area of inadequate consideration, but I know my decision in advance, I am not going to wait to see if the autobrakes work as advertised.

Tootle pip!!

PS: V1 at Lagos ---- couldn't agree more, having several times slept on the floor of a freighter, because it was the best accommodation available at the time. V1 at Luanda is much the same.
LeadSled is offline  
Old 26th Aug 2009, 12:36
  #12 (permalink)  
 
Join Date: Apr 2005
Location: Australia
Posts: 1,414
Likes: 0
Received 0 Likes on 0 Posts
but I know my decision in advance, I am not going to wait to see if the autobrakes work as advertised
By that convoluted logic I guess you don't use autothrottle in case it doesn't work - you don't use a flight director in case it gives you wrong directions.
But I bet you use the autopilot even though it may not work.

I don't know about other aircraft but the autobrake system in the 737 using RTO position will give you maximum braking. On countless occasions during simulator training we have seen pilots over-riding the RTO (either deliberately or inadvertently) even though it is operating correctly. In nearly all cases the stopping distance using manual braking was significantly greater.

This was especially on an abort due to engine failure where the combination of yaw prevention as reverse thrust is actuated and the slightest delay in correcting the initial asymmetric yaw on the runway when an engine fails, does not affect the RTO braking which is equal on both sets of brakes. Try that with manual braking and it is obvious from the instructor's panel read-out of individual pedal pressures that pilots often have varying brake pedal deflections when coping with an engine failure and abort - especially if a crosswind is present.

Presumably if you do not trust the RTO system you ensure it is selected off before take off? If so, how does that accord with your company SOP's.
A37575 is offline  
Old 26th Aug 2009, 14:52
  #13 (permalink)  
 
Join Date: Jul 2005
Location: Somewhere between MSL and the Stratosphere
Posts: 231
Likes: 0
Received 0 Likes on 0 Posts
Very good question,Flaperon777.
Although I seriously doubt that it was intended to be a question.Rather some issue you'd like to have discussed!
As you pointed out,V1 is a very unique function of a multi engined aeroplane ONLY.That is, an aeroplane (jet or otherwise),with MORE than one engine.Imagine trying to work out the V1 of a single engine jet.Hmmmm....!! No engine no go...simple as that.
So as far as the V1 on your C-172 is concerned,I got a good feeling that you wont be going far without that prop turning bro......
Cheers now....
I have a feeling i'm going to start a whole new thread here.Whether or not a single engine jet can/should have a V1...??
Sorry for this deviation,if at all...

Last edited by boeingdream787; 26th Aug 2009 at 14:56. Reason: Typo(s)
boeingdream787 is offline  
Old 26th Aug 2009, 15:24
  #14 (permalink)  
 
Join Date: Jul 2001
Location: Australia
Posts: 4,955
Likes: 0
Received 1 Like on 1 Post
A375757575,

I guess that the B737 must be the odd one out in the Boeing family, in fact Boeing (in the 767 and 744) state that max manual braking will actually produce as good or better (depending on how you read the English expression) as autobrakes.

As the actual braking depends entirely on the brake hydraulic pressure ported to each brake ( as may be modulated by the anti-skid) there is no engineering reason why max. manual braking will not produce exactly the same results as autobrake in a rejected takeoff, once the brakes are applied--- Check with Boeing.

It is more than likely that the sim. result you have seen is a characteristic if the sim, not the aeroplane -- sims are great devices for what they are good for, aircraft certification or operations at the margins of the envelope are not what they are good for, representational, but not precisely accurate. In a real abort, you better be precisely accurate.

Instead of making a string of rather silly and sarcastic remarks, have a close look at the time sequence to activate the autobrake, in a rejected takeoff, compared to applying max. manual braking as the thrust levers are being retarded. Do you have figures for MTBF for the autobrake system?

As to company SOPs, and it is made very clear that it is Captain's choice, they are all quite capable of making that choice. RTO is always armed.

The same goes for the rest of the equipment, unless it's down to low weather minima procedures, and, as most of us understand, that's where it gets very specific. Unlike other companies I could name, keeping thoroughly current on hand flying is also regarded as a good idea. In fact, being competent and current throughout all the combinations and permutations of operating is a requirement --- to be demonstrated during cyclic training.

It sound to me like you work for an "automatic" company, I'm sure you understand what I mean. More than likely, that's why some of your pilots produce the results you have observed on the instructor panel.

Have you ever been involved in a maximum effort abort --- I have, twice, both major engine breakups within a couple of knots of V1, around 150kt, with little in the way of surplus runway in each case ---- Let's just say it is a lot more "realistic" than the sim, or any sim I have been in, and that is quite a few --- the sim. visuals just don't get the big flash out past the front of the aircraft from a massive compressor surge --- both were at night, quite spectacular. All cause by compressor stages turned into something that looked like a well chewed cob of corn.

Tootle pip!!
LeadSled is offline  
Old 26th Aug 2009, 20:39
  #15 (permalink)  
 
Join Date: Apr 2004
Location: Planet Earth
Posts: 2,087
Likes: 0
Received 8 Likes on 7 Posts
Think you are a little confused here. RTO Autobrakes will always give you maximum available braking with minimal delay.


Maximum MANUAL braking is more than maximum selectable autobraking for landing.


RTO Autobrakes are absolutely invaluable and will nearly always outperform a human Pilot.

Last edited by stilton; 26th Aug 2009 at 22:08.
stilton is offline  
Old 27th Aug 2009, 05:05
  #16 (permalink)  
 
Join Date: Nov 2008
Location: 日本
Posts: 456
Likes: 0
Received 0 Likes on 0 Posts
I'm with Stilton on this one. From the Boeing manual:

Rejected Takeoff
Selecting RTO prior to takeoff arms the autobrake system. The RTO mode can be
selected only on the ground. The RTO autobrake setting commands maximum
braking pressure if:
• the airplane is on the ground
• groundspeed is above 85 knots, and
• both thrust levers are retarded to idle
Maximum braking is obtained in this mode. If an RTO is initiated below 85 knots,
the RTO autobrake function does not operate.

Landing
Five levels of deceleration can be selected for landing. However, on dry runways,
the maximum autobrake deceleration rate in the landing mode is less than that
produced by full pedal braking
So, from this we can see that max manual braking does not exceed the braking efforts of RTO, only 'Max Auto' when landing. Sorry, LeadSled, but I reckon you should set RTO, let it do its job and concentrate on keeping straight etc, as opposed to seeing if your feet are quicker than Boeing's systems. Of course, max manual braking should be used if RTO is not doing its job (and, from my experience, you know full well when it's working )
Fratemate is offline  
Old 27th Aug 2009, 20:45
  #17 (permalink)  
 
Join Date: Aug 2009
Location: Luton
Age: 49
Posts: 13
Likes: 0
Received 0 Likes on 0 Posts
Slight deviation guys but if you have a same side (presumably there would be a yaw as well as a bang) double tyre failure in a 737 at just over 80 knots (approx 50 knots below V1) on a 2,500 Metre runway what would be your decision?

(a) Contine trying to drag the aircraft into the air because you do not have your normal wheel braking.

(b) Assume the aircraft is unsafe to fly as you are not confident of accelerating to V1 before running out of runway.

As you would not be more than 500 Metres into the take off roll in still air I would favour (b). There are an increasing number of people in my company insisting we only stop for fire/ eng failure/ or predictive windshear (and don't like thinking about the variable unsafe to fly area).
CFMFan is offline  
Old 27th Aug 2009, 22:00
  #18 (permalink)  
Hardly Never Not Unwilling
 
Join Date: Aug 2000
Location: USA
Posts: 481
Likes: 0
Received 0 Likes on 0 Posts
I've always been uncomfortable with V1 as the decison speed.

Old engines, old airplanes reach V1 speed as calculated at a point x feet beyond where the pristine engine and airplane might have reached that speed.

Also, when you have 14,000 feet of runway, for example, you might reach V1 at 10,000 feet remaining and plenty of time to stop, yet you're committed to go, even with an engine fire/failure.

USAF used to calculate Refusal Speed, the calculated speed at which you could no longer stop. While having its drawbacks, I think that is a better substitute for V1 under some circumstances.

The best tool to have on board is an old, gray haired pilot when the unexpected happens. He will have thought of all that.
BenThere is offline  
Old 27th Aug 2009, 22:28
  #19 (permalink)  
ENTREPPRUNEUR
Thread Starter
 
Join Date: Jun 2001
Location: The 60s
Posts: 566
Likes: 0
Received 0 Likes on 0 Posts
Incidentally - I understand the event was a passenger having a serious fit during the take-off run. The take-off was aborted. The passenger may have died - my information is unclear on the final outcome.
twistedenginestarter is offline  
Old 27th Aug 2009, 22:59
  #20 (permalink)  
Moderator
 
Join Date: Apr 2001
Location: various places .....
Posts: 7,183
Received 93 Likes on 62 Posts
There are an increasing number of people in my company insisting we only stop for fire/ eng failure/ or predictive windshear (and don't like thinking about the variable unsafe to fly area).

The problem I see is the inference that we can set up the RTO planning in anticipation of a guaranteed outcome - ie black and white.

Not the case.

MOST times, if the T/O is rejected up to a margin below V1, the RTO will be successful. MOST times, if the T/O is continued beyond V1, the T/O will be successful.

The bit in the middle has a LOT of caveats attached to its successful outcome. For routine civil airline operations we don't have the time luxury to discuss and try to memorise a tome of information for this takeoff .. we work on the basis of reasonable historical probabilities skewed to the most likely means of achieving a successful outcome.

.. but that doesn't mean that the operation cannot come unstuck if you are near to the tail of the distribution curve on the day ...
john_tullamarine is offline  


Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.