The Fine Print
We all learned to run before we learned to dance, and this subject is no exception. Soin this article we will restrict ourselves to steady flight performance of fixedpitchpropellerdriven airplanes with a single normallyaspirated engine (properly leaned formaximum power) running either at full open throttle or gliding with closed throttle, atone flaps/gear configuration, with wings level in calm air. Followup articles will takeup the performance of constantspeed propeller aircraft, maneuvering, partialthrottleoperations, light twins, turbocharged engines, wind and updraft/downdraft effects, andtakeoff and landing operations.
Like many of us, the Bootstrap Approach has some builtin limitations. We assume thethrust line is directed along the flight path (certainly no Ospreys or other poweredliftaircraft need apply!) and that the flight path is not too steep, inclined less than 15degrees from the horizontal. The airplane’s movement is assumed ‘steady’ in the sense thatit is not being accelerated along the flight path. (Later on in the series, steady turnswill be allowed.) So the bootstrap approach spreadsheet can’t tell you what your father’sJ3 Cub would do halfway through a tail slide. (Not recommended!) But it can come up withalmost all the performance numbers most of us need.
Bootstrap Goals
Our current aim is to come up with two kinds of performance figures. First, we’d likeour airplane’s interesting Vspeeds, and performance numbers associated with those speeds,for any desired altitude and gross weight. See Table 1 for specifics and examples. Noticethat the bootstrap approach does not produce the airplane’s stall speeds, or anystructurallimitation Vspeed such as maneuvering speed V_{a}; you can get thosefrom the POH or by flying separate tests. Secondly, we’d like to know the airplane’sthrust and drag and its detailed flight path – its angle or rate of climb or descent for any desired speed, weight, and altitude. See Table 2.

Table 1. Bootstrap Vspeeds, and corresponding performancenumbers, for a particular Cessna 172 weighing 2200 lb. at an altitude of 7000 feet.

Table 2. Bootstrap performance numbers for a particular Cessna 172weighing 2200 lb. at altitude 7000 feet at 80 KCAS.
Since implementing the bootstrap approach is a detailed formulabased numericalprocedure, and because spreadsheets are an easy way to do repetitive lengthy calculations,at this point you should consider downloading a copy of the companion spreadsheet whichcan do the calculations for you.
NOTE: You may want to download the spreadsheet now, because it’ll make it easier for you to follow the rest of this article. The spreadsheet is available for download in two formats:
There are no macros or menus or anything fancy – just input, output, and formulas in between. 
The next three sections of this article will correspond to the spreadsheet’s threemajor sections – Parts A, B, and C.
Part A: Obtaining Your Airplane’s Bootstrap Data Plate
You’ve seen those little aluminum data plates riveted onto the fuselage beneath thehorizontal tail, giving the airplane model, gross weight, serial number, etc. Think of theBootstrap Data Plate as something similar, but invisible. It’s a data plate which once you decode it – tells you a lot about your airplane’s performance. But first wemust “develop” the airplane’s Bootstrap Data Plate, rendering it visible. Table3, from cell block A39:C47 of the spreadsheet, is a typical Bootstrap Data Plate.
BDP Parameter  Value  Units 
Wing area, S 
174 
ft^{2} 
Wing span, B 
35.83 
ft 
Rated engine power, P_{0} 
160 
hp 
Rated engine speed, N_{0} 
2700 
RPM 
Propeller diameter, d 
6.25 
ft 
Parasite drag coefficient, C_{D0} 
0.037 

Airplane efficiency factor, e 
0.72 

Slope of propeller polar, m 
1.70 

Intercept of propeller polar, b 
0.0567 
Table 3. Bootstrap Data Plate for a particular Cessna 172, flapsup.
The first five numbers in Table 3, the “easy” ones, come straight from yourPOH. The last four “hardertoget” numbers come from – tough work, butsomebody’s got to do it – flying the airplane! See Figure 1.
Figure 1. The five “easy” BDP items come from the POH orcommon knowledge; the four “hardertoget” items come from the sawtooth climband glide tests.
Now let’s focus on the sawtooth climbs and glides. See Figure 2. The object is to find,by trial and error, the airplane’s speed for best angle of climb V_{x} withcorresponding AOC_{max} (best or maximum angle of climb) and its speed for bestglide V_{bg} with corresponding BGA (best glide angle). POH values should give youfirst good guesses, but if you’re lighter than the standard weight used in the POH bothtrue V_{x} and true V_{bg} will be lower than their book counterparts.
Figure 2. Sawtooth climbs and glides (perhaps five or ten ofeach), give you sufficient test data to calculate the four “hardertoget”Bootstrap Data Plate items.
You will need stabilized airspeed (hopefully within a knot) during each run. So thatmeans starting high on the glides, and low on the climbs, to give yourself time tostabilize at your chosen target airspeed. The measured sawteeth need not be large;altitude excursions of about 500 feet are usually sufficient. Table 4 shows the datayou’ll jot down during each climb or glide. Figure 3 shows the kinds of graphs which mightresult. As you can see, V_{x} here is approximately 61 KCAS and V_{bg} isabout 69 KCAS.

Table 4. Data collection form with entries for two climbs and twoglides. We’ve assumed the ASI has no calibration error. Gross weight can be filled inlater. The nexttolast column is calculated, and plotted against the airspeed (as inFigure 3) to help pinpoint the minimum of the climb values and the maximum of the glidevalues.
Note that when doing these climb/glide tests, each climb and glide for which you recordKCAS and deltat must be conducted between the exact same upper and lower altitude limits.It doesn’t really matter what the altitude change is (300 feet or 800 feet) so long asit’s the same for all the data points. The climb/glide tests should also be made during arelatively short elapsed time so that the atmospheric temperature doesn’t changesignificantly between the first test and the last one.
For the best results, you should use a different (stabilized) airspeed for each climband each glide, covering a range from well under the expected V_{x} and V_{bg}to well above it. Your final test should be made at your provisional best guess at V_{x}and V_{bg}.
Either during the test flight (assuming you have an assistant along) or when you’redone recording your climb and glide test results and are safely back on the ground,calculate the seventh column of your data collection form (Table 4 above) by multiplyingthe recorded KCAS by the recorded deltaT for each test. Then plot these values of (KCAS *deltat) against KCAS on a piece of graph paper, and try to draw a smooth curve throughall your data points. I prefer to do this inflight (using an asistant) so that I’m surewe’ve honed in on V_{x} and V_{bg}. When you’ve graphed the values, youshould come up with something that looks like Figure 4 below:
Figure 3. Graphs of (KCAS * deltat) vs. KCAS for both the climband glide series of points. The climb minimum shows V_{x} = 61 KCAS and the glidemaximum shows V_{bg} = 69 KCAS.
What equipment does it take to collect and process this flight data? Besides theairplane, paper, graph paper, and a pencil, you will need:
 Calibrated airspeed indicator (and the calibration curve needed to get from KIAS to KCAS);
 Calibrated altimeter (set to 29.92 in. Hg, so that it reads pressure altitude);
 Stop watch (and a calibrated thumb to operate it);
 Calculator (to get the seventh column in Table 4;
 Ordinary watch (to later figure fuel burn and hence gross weight); and
 OAT thermometer (to later help the spreadsheet correct pressure altitude to density altitude).
Part A of the downloadable spreadsheet will hold the experiment’s identifiers, the five”easy” BDP numbers, and will also process your collected flight test data toproduce the four “hardertoget” BDP items. All the numbers you need to input gointo green cells in the spreadsheet. A millisecond after finishing your input you willhave the corresponding Bootstrap Data Plate output. Phase I of the Bootstrap process – aonetime job – is now complete.
That last, about the onetime job, is important. To some, even to a fewengineers who’ve heard about the bootstrap approach, the process seems circular. Theythink “Get V_{x} to later find out what V_{x} is? That’s a bigadvance? What’s wrong with this picture?” What they fail to realize is that (stillfocusing on V_{x}) it’s more like: Get V_{x} once, for one knownweight and altitude, to be able to get V_{x} (and much more) later, for anyweight and for any altitude. It’s somewhat like your pilot training. You first takelessons, say for forty hours, to then later be able to fly around the countryside for 400hours. Or for 4000 hours.
You’ve got your Bootstrap Data Plate. The training wheels are off.
Part B: Calculating Your Airplane’s VSpeeds and VSpeed Performance
Think for a minute about your flight controls. Since we’ve restricted ourselves in thisfirst article to fully open or fully closed throttle, you have no choices there. Wingsstay level, and flight stays coordinated, so there’s nothing creative to do with eitherailerons or rudder. Flaps stay fixed, probably up. All you have left in your control bagis the ability to change airspeed, using the elevator control, and the freedom to move toa different altitude. Only airspeed V and altitude h are at your disposal. And those onlywithin limits. In a sense you can also choose the airplane’s gross weight, W, but you’dbest do that on the ground, while fueling. Passengers strongly protest being ejected fromthe airplane in midflight. So in our current scenario the “operating” variables,those somewhat under the pilot’s control, consist of only airspeed V, density altitude h,and gross weight W.
In the spreadsheet’s Vspeed section, Part B, speeds are outputs. Here you’re down toonly the two operating variables h and W. Further, since a set of altitudes h has alreadybeen provisionally chosen for you (see Table 5, though you are perfectly free tosubstitute your own altitude choices), the only free choice left is gross weight W. Youmay want printouts of Part B for three or four different gross weights. Stash them away inyour airplane’s glove box or in your map case.

Table 5. Part B of the accompanying spreadsheet Bootstp1.xls for aCessna 172 weighing 2000 pounds.
Part C: Calculating Thrust, Drag, and Rate or Angle of Climb/Descent
In this “any speed” section, Part C, you must choose a (density) altitude hand a gross weight W. Then thrust and drag and rate of climb, etc. – all the data itemsof Table 2 – are given for a range of airspeeds V. Again, feel free to tailor thosesuggested speeds to your faster or slower airplane. If you want readilyavailable printedoutput for say three altitudes and three gross weights, you’ll end up with nine differentPart C performance sheets.

Table 6. Part C of the accompanying spreadsheet Bootstp1.xls for aCessna 172 weighing 2200 pounds at 5000 feet.
AVweb readers may prefer to turn this kind of tabular material (their ownversions of Tables 5 and 6) into graphs. Figures 4, 5, and 6 below are examples. Usingvarious spreadsheet techniques (or by simply recalculating and jotting down changedresults) one can also put together graphs which do not come directly from the spreadsheetcells. For example see Figure 7 for how maximum rate of climb depends on altitude forthree different gross weights.
Figure 4. Major powered Vspeeds vs. altitude for a Cessna 172weighing 2400 pounds.
Figure 5. ROC vs. V for a Cessna 172 weighing 2400 pounds at threealtitudes.
Figure 6. Thrust and drag vs. airspeed for the Cessna 172, flapsup, at MSL weighing 2400 pounds.
Figure 7. Maximum rate of climb vs. altitude for the Cessna 172 atthree gross weights.
Since no one can (or should!) do these calculations in the cockpit, not even afterthey’ve had time to absorb what they mean and how to do them, you’ll want to sit down witha cup of coffee and think through which graphs or charts you really want. That includesselecting density altitudes at which you normally (and perhaps abnormally!) fly, at whichweights, and what the most appropriate ranges of featured airspeeds should be. Figure outthe least amount of most important information before you construct the final outputspreadsheets and graphs. Less is more, so start small. You can always add another graph ortable later on.
Next Bootstrap Steps
In the next article of this series,we’ll shift gears to the constantspeed propeller aircraft, the type flown by most AVwebreaders. In the meantime, those of you wanting more background on the bootstrap approachcan find it in books and articles, at selected Web sites, or in feedback comments here on AVweb.The following references were all written by the author:
 Performance of Light Aircraft, AIAA 1999, available for purchase from AIAA at www.aiaa.org, from Amazon at www.amazon.com, or from Barnes and Noble at www.bn.com. The mathematics level is mostly that of early college with an occasional (but optional) bout of heavy lifting.
 Computing Airplane Performance with The Bootstrap Approach: A Field Guide, M Press 1995, available from the author at jlowry@mcn.net. Lots of bootstrap formulas but almost no derivations. There is a companion disk of spreadsheet templates.
 Aircraft Performance at High Density Altitude, USAF 1999, is a short book written for Civil Air Patrol mountain search and rescue teams. Graphics instead of algebra. I’m uncertain whether the Air Force version will be available other than to CAP members.
 Several professional engineering bootstrap articles have appeared in such publications as Journal of Aircraft, Journal of Aviation/Aerospace Education and Research, and Journal of Propulsion and Power. Contact the author, by email, for specific citations.
 The author’s Web site, www.mcn.net/~jlowry will have rotating articles on aircraft performance (some bootstrap, some not), and has a link to four bootstrap articles on the AllStar Network (supported by NASA and hosted by Florida International University).
The best and simplest way to get your bootstrap questions answered is to ask them righthere on AVweb, through the article feedback facility (see buttons below). And tostay tuned for future articles.