Kitplanes Feature

the static pressure data for altitude capture and hold. It turns out ... analyze flight data. Another way to .... into a bit of marvelous scientific method and rigorous ...
562KB taille 2 téléchargements 356 vues
Static Port Location and Altitude Calibration Often a challenge, accuracy depends on three things: location, location, location.

By Reinhard Metz

When you build an RV, the instructions include the location and specify the material (simple POP rivets) for your static ports. From what I have heard, in most cases the static system works perfectly right away. That is to say, the altitude and airspeed are correct within some acceptable bounds. That’s a fortunate situation, one that many builders of other craft, especially one-of-a-kind designs, don’t find themselves in. Furthermore, I suspect that many homebuilts fly without the owners really knowing how accurate their airspeed and altitude are. Altitude indication depends only on the static system. Airspeed indication, and thus accuracy, on the other hand, depends on both the pitot and static systems, since indicated airspeed is derived from the difference between the pitot ram and static port pressures. Airspeed and altitude accuracy correction and calibration both begin with basic system checks, such as airspeed indicator and altimeter error checks, 26

KITPLANES October 2017

and ensuring that there are no leaks in either system. Several articles detailing manometer methods for performing these checks may be found online, including a spreadsheet (https://tinyurl. com/m4vsbeh) by KITPLANES® contributor Kevin Horton. As measurement and indication systems migrate to electronic ADAHRS sensors, indication errors are diminishing. Also, the pitot-delivered ram pressures are generally accurate and relatively independent of pitot alignment, though the pitot must still be located well out of the propwash and spaced below the wing sufficiently to avoid any disturbance by airflow over the wing— which are both relatively easy to achieve. Therefore, airspeed errors are likely dominated by static pressure errors, just like altitude errors. Optimal static port location is clearly important, but in practice is not easy. Our goal here is to hopefully simplify the process.1 The key to an accurate static system is the location of the port(s) in a place

that ideally provides a stable rendition of the (static) air pressure at that altitude. Pressure on the outside of the fuselage varies substantially with position, and often unexpectedly. An ideal location should therefore be in a neutral pressure area, relatively invariant with airspeed, angle of attack, and altitude. Practical static ports may be included in the pitot mast itself, placing them presumably in neutral air. More typically, they are a pair of ports on either side of the fuselage somewhere between the trailing edge of the wing and tail. A typical variation of pressure along the side of a fuselage is shown in the figures. There’s a transition from high pressure (above ambient pressure) to low pressure from wing to tail, and the neutral pressure area is most desirable for port placement. In reality, the neutral pressure zone is a line, as we will explore later, and port placement on that line will be the goal to achieve the best compromise for all important flight regimes. www.kitplanes.com & www.facebook.com/kitplanes

Subsonic Static Pressure Distribution

Regulations

While you would like to know your altitude and airspeed as accurately as possible, altitude is clearly the more important for separation safety reasons. The FAA requirements are scattered in a few places and a bit challenging to resolve as to the static port accuracy by itself, but here are the pieces: 14 CFR Part 23—“Airworthiness Standards: Normal, Utility, Acrobatic, and Commuter Category Airplanes,” 23.1325 Static Pressure System, states: “(e) Each static pressure system must be calibrated in flight to determine the system error. The system error, in indicated pressure altitude, at sea level, with a standard atmosphere, excluding instrument calibration error, (my emphasis) may not exceed ±30 feet per 100 knot speed for the appropriate configuration in the speed range between 1.3 VSO with flaps extended, and 1.8 VS1 with flaps retracted. However, the error need not be less than 30 feet.” Furthermore, per 14 CFR Part 43, Appendix E to Part 43—“Altimeter System Test and Inspection,” the altimeter error limits shall be according to the provided table, ranging from 20 to 130 feet, corresponding to 0 to 20,000 feet of elevation. Finally, the altimeter/transponder correspondence test requires the transmitted altitude to be within +/- 125 feet of the altimeter indicated altitude. For an ADAHRS-based system this error will be near zero. So, to some extent, it

Figure 1: Surface pressure typical lateral distribution. The numbers in the circles (1–6) indicate places where neutral pressure exists, i.e., surface pressure is the same as static pressure at that altitude.

is up to the aircraft “manufacturer”— us—to decide how to add all these up and what tolerance to attribute to the port location. Having an ADAHRSbased system and a correspondence test error for the Garmin G3X Touch system near zero, I set a goal of being within +/- 50 feet at 3000 feet, and +/125 feet for the range of altitude from 0 to 10,000 feet and the airspeed range of 1.2 VSO to cruise. It may be a bit surprising that the biennial altimeter/transponder correspondence test does not verify overall altitude reporting accuracy. The test applies pressures to the static port(s) corresponding to the standardized model of atmospheric pressure vs.

N49EX and Surface Pressure Model

Figure 2: Yellow and green areas depict zero pressure. Magenta is low pressure, and blue is high pressure. Photos: Reinhard Metz



altitude, and verifies that the system— altimeter and transponder—indicate and report altitude accurately with respect to the applied standard pressures only, independent of whether or not the static ports are accurate in flight. The static ports must be located optimally and supply neutral pressure (within tolerances).

How My Trouble Started

Our Wheeler Express N49EX was originally built with a combined pitot/ static probe, which when calibrated was sufficiently accurate for both altitude and airspeed. All was fine until my recent glass panel upgrade, including a Garmin autopilot, which uses the static pressure data for altitude capture and hold. It turns out that the pressure supplied by the static port on the pitot is slightly sensitive to angle of attack, which while not noticeable in the altitude display, makes the autopilot hunt some +/- 30 feet, a nauseating experience! So, a more stable static port location was needed. A quick trial with cabin static pressure stabilized the autopilot, but was substantially off in altitude, as is typical due to lower pressure in the cabin, not to mention variations from the air vents. After several failed attempts to improve the pitot probe static performance, I decided to move the ports to the fuselage. KITPLANES October 2017

27

Static Port Locations First Fuselage Static Ports

I hate to admit the naiveté with which I first installed static ports on the fuselage: I simply looked at a number of factory-built planes, such as the Cirrus and Bonanza, and measured the relative distance from tail and trailing edge of the wing, and chose a similar location on my plane. Completing the installation, which of course included making holes in the fiberglass, I was dismayed that, although the autopilot was now stable, the altitude and airspeed were substantially off (by about 130 feet and 10 mph respectively, cruising at 3000 feet). That’s when it became clear that the location of the static ports requires more than guesswork, or even good intuition. After extensive investigation and discussions with several experts, I learned that finding the best location was not easy and, even with commercially produced airplanes, involves a significant amount of trial and error—hundreds of hours as Paul Dye has put it. The prospect of turning my plane into Swiss cheese did not sit well; there had to be a better way! The process, in any case, assumes and requires a starting point set of static ports, which as described below, may be done with something better than guesswork hole drilling. Then, the next

➋ STA 152, ~ 80 – 120 ft. high, i.e. low pressure

➊ STA 180.5, Location of installed static ports ~ 92 - 128 ft. low, i.e. high pressure

➍ STA 163, Best/chosen trial location, +18/-3 ft. altitude error ➌ STA 157.5, ~ 50 ft. high, low pressure Figure 3: Tests were conducted with the moveable static port plates in several different locations on the aft fuselage.

challenge is to determine the error in altitude for any particular port location and how to improve it.

Determining Altitude Error

With an initial pair of static ports (which may be the “moveable trial static ports” described later) and then further trial locations, the first thing is to determine the altitude error (which correlates with port position error). One approach is by inference from airspeed error, since airspeed may be relatively accurately determined with GPS, as described by Kevin Horton in “Flight Testing: Static System Error, Theory and Practice,” which appeared in

KITPLANES® in October and November 2009. Kevin also provides a spreadsheet at http://tinyurl.com/jwp9r5a to analyze flight data. Another way to determine altitude error is to derive it from WAAS GPS altitude. The WAAS specification requires a position accuracy of 25 feet or better, for both lateral and vertical measurements, at least 95% of the time. Actual performance has been shown to be better than 5 feet vertical. That makes it an acceptable source of true altitude for static port evaluation, assuming one has a WAAS-enabled GPS. That said, it is well known that the indicated altitude will generally not be

GPS Altitude Error Calculations Inputs 1

2

Field Elev. Ft.

3

4

5

hT ind

Ind. Temp.

Field Press. Field OAT F Test Alt. Ft. In HG

6

7

11

12

Test Alt. OAT F

GPSA

TAS kts

hT Feet

Ind. Alt. Error, Ft.

Date and Test

758

30.15

42.8

3000

35

3000

161

3092.5

92.5

2/27/2017 STA 180.5

758

30.54

36

3000

19

2874

161

3018.5

18.5

3/3/2017 STA 163

758

30.38

24.6

4000

17

3768

161

4016.3

16.3

3/15/2017 STA 163

758

30.39

32

6000

8

5666

164

6000.0

0.0

3/12/2017 STA 163

758

30.38

24.6

8000

7

7526

162

7996.6

-3.4

3/15/2017 STA 163

758

29.67

66

3000

58

2995

161

2948.6

-51.4

2/22/2017 STA 157.5

758

30.17

40

3000

30

2828

161

2933.0

-67.0

3/9/2017 STA 152

758

30.17

40

6000

28

5760

161

5938.4

-61.6

3/9/2017 STA 152

Figure 4: Test flight ground and altitude temperatures and altimeter setting were used with atmospheric pressure and altitude equations to adjust the GPS (true altitude) to what the altimeter should indicate for the test flight atmospheric conditions. This made it possible to calculate indicated altitude error.

28

KITPLANES October 2017

www.kitplanes.com & www.facebook.com/kitplanes

(Left) The relocatable static port plate is made from 1/16-inch thick polycarbonate and is attached to the fuselage with aluminum foil tape. (Right) When the moveable plate is in the same location as the existing static ports, the altitude and airspeed errors are the same as the ports by themselves.

the same as the GPS altitude unless you have standard atmospheric conditions: temperature, pressure, and lapse rate. Indicated altitude is the universal reference used by all, whether or not it happens to be the same as true altitude—for separation it matters most that everyone is using the same relative altitudes. However, test flight ground and altitude temperatures and altimeter setting can be

used with the atmospheric pressure and altitude equations to adjust the GPS (true altitude) to what the altimeter should indicate for the test flight atmospheric conditions, which then allows one to calculate the indicated altitude error. Caveats are that the method will not work with a temperature inversion, and your OAT measurement capability must be accurate. A spreadsheet for the approach



is included on the KITPLANES® website at www.kitplanes.com/staticports and is shown in Figure 4. Now, the problem remains: How to correct the port position error? The assumption by some is that may be achieved by placing dams ahead of or behind existing ports, but I have found that often does not work adequately, especially if the port is too far from

KITPLANES October 2017

29

the actual neutral pressure zone. It also does not make for a very aesthetically neat solution.

Moveable Trial Static Ports

What if one had a moveable static port—one that could be placed in multiple locations, gathering data to converge on the best location? There are two challenges in creating such a tool: First, it needs to be thin and flexible enough to conform to the fuselage at the area of attachment and not materially affect the local airflow as regards the pressure at its port. Second, a tube must be able to be routed from it into the plane and connected to the rest of the static system. This was accomplished with an approximately 4x4-inch, 1/16-inch thick polycarbonate plate with a 0.035-inch hole for the static port. The hole was in turn routed near to the edge of the plate with a 1/8-inch-wide milled channel on the back side, with a depth about half the plate thickness. At the edge of the plate, a ½-inch-wide piece of contoured

Altitude and Airspeed Errors Port Location

Indicated Altitude

GPS Method Altitude Error

Airspeed Method Altitude Error

TAS Error

➊ STA 180.5

3000 ft.

+ 93 ft.

+ 129 ft.

- 9.8 mph

3000 ft.

+ 18 ft.

+ 4 ft.

+ 0.3 mph

4000 ft.

+ 16 ft.

+ 6 ft.

+ 0.4 mph

6000 ft.

0

+ 1 ft.

0

8000 ft.

- 3 ft.

+ 9 ft.

+ 0.6 mph

➌ STA 157.5

3000 ft.

- 54 ft.

­—



➋ STA 152

3000 ft.

- 67 ft.

- 98 ft.

+ 8.3 mph

STA 163 with installed port

3000 ft.

- 0.8 ft.

- 13 ft.

- 1 mph

6000 ft.

+ 26 ft.

+ 40 ft.

+ 0.2 mph

➍ STA 163

Figure 5: Through trial and error, STA 163 was determined to be the best location for the static ports. The bottom rows show the data for STA 163 with the actual ports installed there.

Plexiglass is glued to provide a place for a ¼-inch access hole that in turn connects to the channel with a small perpendicular hole. The channel is covered and sealed with a piece of Kapton tape. The plate assembly is attached to the

fuselage with aluminum foil tape, with the Plexiglass piece parallel to the airflow. Connection from the port plate to the static system is accomplished with a length of ¼-inch nylon pitot/static tubing, contoured along the side of

Pressure, Altitude, Temperature, and Airspeed Math Here is the atmospheric and airflow physics used in the spreadsheet to determine altitude error. Pressure as a function of altitude can be calculated with the equation Ph = P0 × [1 + (L × h)/T0]-0.03416/L where: Ph is pressure at altitude h in Pascals (Pa) P0 is the pressure at sea level in Pascals h is altitude above sea level in meters T0 is the temperature at sea level in °K (= °C + 273.15) L is the temperature lapse rate per meter (negative number) If the conditions are standard, T0 is 288.15 °K = 15 °C, the lapse rate is -0.0065 °K/meter, and P0 is 101325 Pascals (= 29.92 in. Hg). An error-free static system in standard atmospheric conditions would then indicate actual height above sea level. With typically non-standard conditions, the altimeter setting will offset the difference from standard pressure, and the indicated altitude difference from actual altitude will be dominated by the difference of the temperature and lapse rate from standard, for which altimeters are not compensated. The temperature component will typically dominate, as, except for days with inversions, the lapse rate does not vary so much. Complementary to the pressure equation, the height above sea level is given by: h = (T0/L) × [(P/P0)-0.19026×L – 1] OAT at altitude and airspeed may be calculated as: OAT = OATI / [1 + 1.6 x (TAS/750)2] 30

KITPLANES October 2017

Where TAS is in mph and OATI is the indicated OAT at the test altitude. The sensor recovery factor is assumed as 0.8, and the speed of sound at the altitudes we fly is assumed as an average of 750 mph. Airspeed may be calculated as: CAS = a0 × [5 × (qc /P0 + 1)2/7 – 1]1/2 where: a0 is the speed of sound at 15°C qc is impact pressure P0 is standard pressure at sea level. Finally, pitot impact pressure may be calculated as: qc = P × [(1 + 0.2M2)7/2 – 1] where: P is static pressure M is the Mach number, which in turn is CAS/Speed of Sound (at altitude). The pressure and altitude equations are used in Figure 4, the error calculation spreadsheet, to adjust GPS altitude to what the indicated altitude should be for a given set of test-time atmospheric conditions. They may also be applied to calculate the rate of change of pressure per change of altitude, and then predict the error in airspeed for a given error in altitude. For example, at 3000 feet the change in pressure is about 3.35 Pa per foot, and change in airspeed for a given change in pressure is 0.022 mph/Pascal, so the airspeed error for a given altitude error is 0.074 mph/foot. In other words, if the altitude is off by 100 feet, the airspeed will be off by about 7.4 mph and vice versa. —R.M. www.kitplanes.com & www.facebook.com/kitplanes

the fuselage, held in place with a cover of foil tape, and entering the cabin through an available location. The latter, in my case, was at the gear leg, following the route of the brake lines. Now, one obvious concern might be, can this arrangement fly without fear of it coming off at cruise speed? Well, the answer to that came to me while walking under the Airbus A330 at Oshkosh a few years ago where I saw a bunch of aluminum foil tape on the wings. Talking to the Airbus folks, I was told, “Oh yeah, we do that all the time in development, no problem.” If it works for them, it will certainly work at 160 knots!

Pressure Profile Modeling

Relocatable static ports in hand, the first test was to place them directly over the existing installed ports and verify that they delivered the same incorrect altitudes and airspeeds, which they did. This looks like it might work! Just before proceeding with more guesswork placements of the newly crafted moveable static ports, I lucked into a bit of marvelous scientific method and rigorous engineering that anchored the process in some real data. In an email discussion of my problem and mission with Peter Garrison, who writes the “Technicalities” column for Flying magazine, Peter mentioned to me that he had the CAD model for the Express aircraft and would gladly run a surface pressure analysis for me. That predicted where the areas of zero error should be, providing a starting point for locating the ports. You can see in the pictures the line where this is expected to be, back of the wing. Superimposing the model on a picture of the plane provided guidance for new trial port locations.

in between, and in fact can be approximately predicted by interpolation of data points. Of course, it’s never quite that simple. The pressure gradient is not linear, and in addition a vertical position needs to be found that minimizes the effects of angle of attack, altitude, and airspeed, while avoiding any significant errors in landing configuration with flaps down.

Data/Analysis

After three new trial locations using the moveable port plates, I found what looked like an acceptable final location. Figure 5 shows the altitude and airspeed errors at 3000 feet cruise for the four

...and leave your engine monitoring to EIS. Trusted with everything from 2-strokes to turbines for over two decades.

Trial Results

Starting with the predicted neutral pressure zone, the first test flight data made my day! Whereas the original ports were in a slightly high pressure area, resulting in airspeed 9 knots low and altitude indication 129 feet low, the new location was now in a slightly low pressure area. The model was not perfect, but I knew the best location was somewhere

port positions as shown in the pictures, and at 3000, 4000, 6000, and 8000 feet for STA 163. From the data, it looks like a slightly better position might have been about 1 or 2 inches forward, but that would have put the right port in the baggage door, so I decided that within a few feet and less than 1 mph error was good enough. The bottom rows show the data for STA 163 with the actual ports installed there. Additional tests at lower and higher altitudes, lower speeds, and in landing configuration all confirmed errors within the original goals. One insight is that the pressure gradient is not linear. With multiple points, a curve fit could be created, but you may find an acceptable location with

FLY IT

like you stole it... www.grtavionics.com • (616) 245-7700

Proud sponsor of Tiger Airshows and airplane “thief” extraordinaire, Hotwire Harry!



KITPLANES October 2017

31

a few iterations. Note that whereas the plates delivered nearly identical data when installed over my original ports, when the STA 163 ports were installed, there was some difference, though probably acceptable. One refinement may be to make the plates with ports that are more like the contour of the port to be installed.

Summarized Procedure

To recap, here’s the process in review: 1. Verify that your pitot/static system does not have any leaks. 2. Determine any calibration errors in the altitude and airspeed indicators. 3. Establish a set of test conditions, including various combinations of airspeed/power settings, altitudes, and flaps extended/retracted for the slow speeds. 4. If a surface pressure model is available for your plane, use it to determine the initial placement of the static trial plate. If not, pick a location roughly 1/3 of the distance from the trailing edge of the wing root to the tail. For vertical position, locate roughly at the vertical tangent point.

5. Preferably on smooth days, fly your test combinations holding at each of the altitudes (easiest if you have an autopilot), and record indicated altitude, GPS altitude, indicated airspeed, true airspeed, OAT on the ground and at altitude (and some intermediate altitudes to verify there is no inversion). 6. Determine the altitude errors for the various tests using either the inference from airspeed error or adjusted GPS altitude method. If you use the airspeed inference method, your test flights need to include a three course pattern, as described in Kevin Horton’s spreadsheet. 7. If the altitude error is such that the actual altitude is higher than indicated, then the static port pressure is lower than standard for that altitude and likely the port is too far forward, and vice versa. Relocate the trial port in the direction appropriate for a correction. 8. Use the data from the second port to determine a rate of correction per inch of port relocation to predict a

better location. The pressure gradient may not be linear, but within just a few locations, the altitude and airspeed errors will likely be reduced into the range of +/- 30 feet and +/- 1 mph. 9. Determine the trial location that provides the best compromise overall results. Once you’ve found your best locations, it’s time to take the plunge and put holes in the fuselage. One last thought: You may wish to start with just the first port on one side and make sure nothing has changed before proceeding with the second port on the other side. J 1 NASA Technical Memorandum 104316, Airdata Measurement and Calibration, Edward A. Haering, Jr., 1995

NASA Reference Publication 1046, Measurement of Aircraft Speed and Altitude, 1980

2

Final Report, FAA Contract No. FA64WA-5025, Project No. 320-205-02N, Flight Calibration of Aircraft Static Pressure Systems, 1966

3

Does This Really Work? OK, I know what some of you are thinking! Having read most of the pitot/ static system threads on the Van’s Air Force forum (www.vansairforce.net), there are many tales of extraordinary sensitivity to minor variations of the static ports. Narratives abound of 10-knot airspeed errors or variations associated with minor static port features/changes, even due to N-number decals or paint interfaces in the vicinity of the ports. Given such discussions, I can imagine you might have serious doubts about how well a moveable static port on a plate structure like I have described might work. Can it really perform like a fuselage port at the same location? To address that concern, I offer the following: 1. Bernoulli’s principle says that the static pressure at any location along the fuselage is inversely proportional to the velocity of the air at that location. That is why, per the figure, the static pressure has a low to high gradient as it moves from the fuselage area behind the wing to farther back; it was moving faster to get past the wider portion of the fuselage and slows down as the fuselage gets thinner. So, for the relative part of locating a static port, one that delivers a lower altitude and airspeed than actual needs to be moved forward and vice versa. 2. While I am not a fluid dynamics expert, it appears that pressure at any given location will be the same on the surface of the thin plate port described because it maintains essentially the same contour of the underlying surface, and being thin enough, it maintains the same flow velocity and thus the same static pressure. 32

KITPLANES October 2017

3. When I have placed the moveable plate in the same location as the existing static ports, the altitude and airspeed errors are the same as the ports by themselves. Further, when I finally determined the best port location and took drill to the fuselage, the final ports again provided the same altitude and airspeed results as the plates. The nagging and remaining question then is how and why have some RV owners had such radical differences in altitude and airspeed resulting from minor port changes, particularly at the same location? Perhaps it is that the rivet ports are not actually at the best neutral pressure location, but their particular shape and hole entry curvature have local flow altering effects that result in good measurements? I am using Cleaveland Aircraft Tool (www.cleavelandtool.com) aluminum ports bonded into the fiberglass, which have a minor outward curvature, but otherwise are generally flush. Their holes are flush and sharp, similar to what NASA testing showed to be ideal hole shaping.2,3 Perhaps the moveable plates would not perform the same as the Van’s rivets. The general method is still applicable even if the first static location ends up not quite right on. The difference from the moveable plate and other plate positions can then be used to calculate a new, and hopefully final, location. It’s still better than the many trial and error holes! —R.M. www.kitplanes.com & www.facebook.com/kitplanes