V-12
February 2008
Legacy
V-13
February 2008
Legacy
TAKEOFF DISTANCES
Takeoff distances are a function of pressure altitude, gross weight, wind component
and outside air temperature. Runway slope and surface type (grass, slush, etc.)
can lengthen your required takeoff distance significantly. Takeoff flaps reduce the
number slightly. Takeoff distance is broken into two segments, ground roll and
distance to clear a 50 foot obstacle. Significant differences can result from both
aircraft and pilot technique so it is recommended that you fly your aircraft and
determine these “numbers” specifically. If your test runway has any significant
slope, obtain some data in both directions to determine the effect of that factor.
The latter is best checked at heavy weights.
These data can be obtained as described below. They should be obtained after the
static source, the airspeed and the stall speed tests have been accomplished.
Be
sure to make any corrections to your indicated speeds when you define your
“Vr” and “V” for these tests (65 and 102 KCAS respectively).
Pick a time when airport traffic is minimal, the wind is calm and a “brakes release”
point. Coordinate with the “tower” personnel and obtain the necessary support
personnel. Station them down the runway (with distance markers on it) such that
one can pick off the lift-off point along the runway and the other can estimate
your distance at the 50 foot altitude. (This will take some practice to judge, and a
copilot calling “Mark” based on your indicated altitude can help the ground spotter
pick your “50ft” distance. Estimate your gross weight for each takeoff and make
multiple runs to define the scatter. It is suggested that you plot each point on a
chart to show the data scatter, then enter the data on the chart.
Summary of Contents for Legacy
Page 6: ...Legacy ...
Page 8: ...I 2 February 2008 Legacy Intentionally Left Blank ...
Page 20: ...I 14 February 2008 Legacy NOTES ...
Page 21: ...I 15 February 2008 Legacy NOTES ...
Page 22: ...I 16 February 2008 Legacy NOTES ...
Page 24: ...II 2 February 2008 Legacy Intentionally Left Blank ...
Page 34: ...II 12 February 2008 Legacy NOTES ...
Page 35: ...II 13 February 2008 Legacy NOTES ...
Page 36: ...II 14 February 2008 Legacy NOTES ...
Page 38: ...III 2 February 2008 Legacy Intentionally Left Blank ...
Page 47: ...III 11 February 2008 Legacy NOTES ...
Page 48: ...III 12 February 2008 Legacy NOTES ...
Page 50: ...IV 2 February 2008 Legacy Intentionally Left Blank ...
Page 69: ...IV 21 February 2008 Legacy NOTES ...
Page 70: ...IV 22 February 2008 Legacy NOTES ...
Page 72: ...V 2 February 2008 Legacy Intentionally Left Blank ...
Page 90: ...V 20 February 2008 Legacy NOTES ...
Page 91: ...V 21 February 2008 Legacy NOTES ...
Page 92: ...V 22 February 2008 Legacy NOTES ...
Page 94: ...VI 2 February 2008 Legacy Intentionally Left Blank ...
Page 108: ...VI 16 February 2008 Legacy NOTES ...
Page 110: ...VII 2 February 2008 Legacy Intentionally Left Blank ...
Page 134: ...VII 26 February 2008 Legacy NOTES ...
Page 135: ...VII 27 February 2008 Legacy NOTES ...
Page 136: ...VII 28 February 2008 Legacy NOTES ...
Page 138: ...VIII 2 February 2008 Legacy Intentionally Left Blank ...
Page 158: ...VIII 22 February 2008 Legacy NOTES ...
Page 160: ...IX 2 February 2008 Legacy Intentionally Left Blank ...
Page 168: ...IX 10 February 2008 Legacy Emergency Procedures ...
Page 169: ...IX 11 February 2008 Legacy Emergency Procedures ...
Page 170: ...IX 12 February 2008 Legacy Emergency Procedures ...
Page 171: ...IX 13 February 2008 Legacy Emergency Procedures Continued ...
Page 172: ...IX 14 February 2008 Legacy Normal Procedures ...
Page 173: ...IX 15 February 2008 Legacy Normal Procedures Continued ...
Page 174: ...IX 16 February 2008 Legacy Performance System Description ...
Page 176: ...IX 18 February 2008 Legacy NOTES ...
Page 178: ...X 2 February 2008 Legacy Intentionally Left Blank ...