Go Back  Airline Pilot Central Forums > Career Builder > Military
Help with Critical Field Length >

Help with Critical Field Length

Search
Notices
Military Military Aviation

Help with Critical Field Length

Thread Tools
 
Search this Thread
 
Old 12-20-2018, 12:01 AM
  #11  
Gets Weekends Off
 
Joined APC: Jul 2005
Posts: 249
Default

I don't disagree with you that crosswind has an effect on VMCG. All I'm stating is there is no correction in the AFM for crosswind on VMCG. It is simply a function of OAT, PA and thrust in the performance chart. As such, there is no adjustment for VMCG when AeroData computes our takeoff performance. Why there isn't a correction, I don't know.
cougar is offline  
Old 12-20-2018, 05:29 AM
  #12  
Gets Weekends Off
 
galaxy flyer's Avatar
 
Joined APC: May 2010
Position: Baja Vermont
Posts: 5,177
Default

My understanding is first, not computing the crosswind effect means sveryone’s take-off numbers look better, both in the marketing brochures and in the computations. Second, the FAA was convinced by the manufacturers that the chances any engine failure near a minimum speed scheduled take-off (V1 or Vref near Vmcg) AND having a crosswind strong enough to be a factor AND on the upwind was pretty low. Which then brings up the question why do we spend so much sim time doing V1 cuts when statistically they are low probability hazard?

GF
galaxy flyer is offline  
Old 12-21-2018, 10:49 PM
  #13  
Gets Weekends Off
 
PurpleToolBox's Avatar
 
Joined APC: Apr 2013
Posts: 1,622
Default

Originally Posted by galaxy flyer View Post
At least in the C-5, we used full rated power (TRT) for Vmcg and Vmca calculations because TRT was always available.

GF

So the C-5 never does a reduced thrust takeoff?
PurpleToolBox is offline  
Old 12-22-2018, 05:49 AM
  #14  
Gets Weekends Off
 
galaxy flyer's Avatar
 
Joined APC: May 2010
Position: Baja Vermont
Posts: 5,177
Default

Originally Posted by PurpleToolBox View Post
So the C-5 never does a reduced thrust takeoff?
No, we used reduced most of the time, but just like the FAA rules, Vmcg and Vmca were based on full rated power, which is why full thrust is available on a reduced thrust take-off.


GF
galaxy flyer is offline  
Old 12-27-2018, 03:37 AM
  #15  
Gets Weekends Off
 
sourdough44's Avatar
 
Joined APC: Sep 2013
Position: Left
Posts: 636
Default

Oh for the old days when things were simple. That is, push those throttles right to the stops, no matter the conditions.
sourdough44 is offline  
Old 01-01-2019, 12:13 AM
  #16  
Gets Weekends Off
 
PurpleToolBox's Avatar
 
Joined APC: Apr 2013
Posts: 1,622
Default

Originally Posted by galaxy flyer View Post
Which then brings up the question why do we spend so much sim time doing V1 cuts when statistically they are low probability hazard? GF
Because even though the risk is low, the probability of kill if the maneuver is performed poorly is extremely high.

On the 777 yesterday, we had driving rain and crosswinds for takeoff. The software computed a 20% reduction in thrust (TO2) but did not allow for a reduction by the assumed temperature method. My mind started thinking about this thread since we had a significant split between V1 and VR with a stop margin of less than 500 feet. I am glad FDX calculates stop margins.

That is better than previous company. There the only data points we were given for takeoff was power setting, V1, V2, VR and maximum crosswind. Smoke and mirrors to me.
PurpleToolBox is offline  
Old 01-01-2019, 03:56 AM
  #17  
Gets Weekends Off
 
Adlerdriver's Avatar
 
Joined APC: Jul 2007
Position: 767 Captain
Posts: 3,988
Default

Originally Posted by galaxy flyer View Post
No, we used reduced most of the time, but just like the FAA rules, Vmcg and Vmca were based on full rated power, which is why full thrust is available on a reduced thrust take-off.


GF
When we use derated (10% or 20%) power as determined by our performance software by itself or in combination with an assumed temperature method (reduced thrust takeoff), Vmcg and Vmca are computed using maximum derated thrust. So, in those situations (such as the one Purpletoolbox described above), we don’t have assurance of full control authority should we select full rated thrust. The flight manual cautions that a thrust increase during a derated takeoff following an engine failure could result in loss of control. In fact, Boeing recommends not advancing the throttles during an engine out when using the combined derate and assumed temp because the derated max limit the Vmcg and Vmca is based on is not displayed.
Adlerdriver is offline  
Old 01-01-2019, 05:46 AM
  #18  
Gets Weekends Off
 
tomgoodman's Avatar
 
Joined APC: Feb 2006
Position: 767A (Ret)
Posts: 6,248
Default

Sneaky sim IPs would give a V1 cut, wait until you are all trimmed up but have not yet retarded the throttle, then suddenly restore the engine. Nobody expected that, because it’s a checkride and an engine-out approach is always next, right? Flailing & wailing could ensue when the “bad” engine came roaring back at full power.
tomgoodman is offline  
Old 01-01-2019, 06:21 AM
  #19  
Gets Weekends Off
 
galaxy flyer's Avatar
 
Joined APC: May 2010
Position: Baja Vermont
Posts: 5,177
Default

Originally Posted by Adlerdriver View Post
When we use derated (10% or 20%) power as determined by our performance software by itself or in combination with an assumed temperature method (reduced thrust takeoff), Vmcg and Vmca are computed using maximum derated thrust. So, in those situations (such as the one Purpletoolbox described above), we don’t have assurance of full control authority should we select full rated thrust. The flight manual cautions that a thrust increase during a derated takeoff following an engine failure could result in loss of control. In fact, Boeing recommends not advancing the throttles during an engine out when using the combined derate and assumed temp because the derated max limit the Vmcg and Vmca is based on is not displayed.
No disagreement here. By “full rated” it means at the selected rating, not the maximum without the derate.


GF

Last edited by galaxy flyer; 01-01-2019 at 06:44 AM.
galaxy flyer is offline  
Old 01-01-2019, 09:18 AM
  #20  
Gets Weekends Off
 
Joined APC: Jul 2005
Posts: 249
Default

Originally Posted by PurpleToolBox View Post
On the 777 yesterday, we had driving rain and crosswinds for takeoff. The software computed a 20% reduction in thrust (TO2) but did not allow for a reduction by the assumed temperature method. My mind started thinking about this thread since we had a significant split between V1 and VR with a stop margin of less than 500 feet. I am glad FDX calculates stop margins.
The stop margin of <500' is likely an example of Derated thrust (TO2) being the only viable solution for takeoff as the TO or TO1 VMCG V1 would result in an Accel-Stop beyond the runway available. Assumed Temperature Method is not allowed for contaminated runways, but is available if the runway is wet.

In my view, on dry or wet runways, TO should be used with an assumed temperature. There is diminishing returns on engine wear below approx 20% thrust reduction. This would allow for full thrust (firewall) if needed throughout the takeoff. Also, assumed temperature is inherently conservative. Due to the differences in TAS, the accel-stop and accel-go distances will be less than what is calculated. Further, the most fuel efficient takeoff profile is maximum thrust, full climb thrust to altitude. At some given thrust setting there is an ideal intersection of fuel economy and engine wear.

TO1 and TO2 should be reserved for contaminated runways for the reasons addressed previously.
cougar is offline  
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
USMCFLYR
Safety
118
03-27-2014 11:02 AM
FlyHigh423
Technical
3
12-13-2011 06:18 PM
AZFlyer
Hangar Talk
18
08-23-2009 07:27 PM
DANCRJ
Regional
36
07-30-2008 05:14 PM
SWAjet
Major
0
02-19-2005 03:14 PM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



Your Privacy Choices