Chuck’s Aircraft, the Austin Cirrus Service Center located at the Austin Executive Airport (KEDC), is celebrating it’s 10 year anniversary this month. What better what to celebrate than to fly in for Texas BBQ? That’s what they thought too!
Chuck’s Aircraft will be hosting its 10 Year Anniversary Fly In on Friday, June 25th from 1pm to 5pm on their ramp at EDC (see airport diagram below). Chuck’s Aircraft always provides quality maintenance for Cirrus and other aircraft, so come show your appreciation for them.
Recently, I assisted with the delivery of a 2007 Piper Saratoga Turbo from San Antonio to New York City. It was a very nicely equipped airplane, complete with a Garmin G1000 panel, an STEC 55x autopilot, and air conditioning. The owner joined me on the flight back to get trained in the airplane, getting him comfortable in it over our 2 day excursion back to NYC. Total flight time was 12 hours, though that did include several stops along the way and landing practice at the airports we stopped at.
The 6 seat Turbo Saratoga is a very comfortable, very capable flying machine. It is made for hauling, with a gross weight of 3,600 pounds, but that’s not to say it isn’t lacking in comfort, either. The rear cabin has 4 seats, 2 facing forward and 2 facing rear. It would be a little tight for 4 full size adults in the back seat. To avoid knee knocking, the plane is an excellent 4 person and bags aircraft (or 4 adults and 2 kids).
The really nice part about the Piper Saratoga is the baggage door. Unlike the Bonanza, the Piper Saratoga has a baggage door that opens to the baggage compartment, creating a much easier way to load and unload baggage. The nose baggage compartment, which holds an additional 100 pounds, is a very nice feature, allowing the bag load to be spread out.
We typically saw cruise speeds of 155-165 KTAS depending on altitude. The highest we went was only about 9,000 feet, so we didn’t get up real high to see what the single turbo could do. Even though the Lycoming TIO-540 engine burns about 20 gallons an hour, with 102 gallons of gas on board, the fuel consistently outlasted our desire to continue flying.
Being equipped with the G1000 was a very nice feature of this particular Piper Saratoga. The screens are nice and big, larger than the displays on a high wing Cessna or a Corvalis. That allows for easier viewing of approach plates, NEXRAD, and the engine gauges.
There are always downsides to an airplane, and the Saratoga is no exception. The STEC Autopilot leaves some to be desired as I felt it hampered the capability of the G1000 when shooting approaches because the 12 knot crosswind limitation on the autopilot. You can still use the autopilot on an approach with higher than 12 knot crosswinds, but the autopilot tends to search around for the final approach course.
The air conditioning works very nicely, though it did have a tendency to freeze up at altitude. We discovered that quickly and just decided to turn it off and leave the blower on, since it was cool enough up high anyway.
Overall, the Turbo Saratoga is a very nice airplane. The speed leaves a little to be desired (you can get 10 KTAS more out of a Bonanza with a Continental engine, about 20 knots more if it is a Turbo Bonanza), but it is very high on comfort. The Piper Saratoga makes for a good family airplane or as a hauler. I liked the airplane a lot and thoroughly enjoyed my time in it.
Ah, fall is finally here. In Texas, it arrived about a month late, but showed up with a vengeance. A strong cold front caused a 40 degree temperature drop in 12 hours earlier this week, bringing rain, lower freezing levels, and lots of wind.
Fall means cooler temps, but fall also means less light. The sun begins to set sooner, plus the fall back time change in November cause darkness to spring upon an unaware pilot.
Before getting in to too many night landings tips, just a friendly reminder, passengers can only be carried at night if the PIC has completed 3 takeoffs and landings to a full stop in the last 90 days during the time period of 1 hour after sunset to 1 hour before sunrise.
Lots of us have been landing long before sunset for most of the past couple of months, so those night flying skills might be a little rusty. The best way to remedy night flying rustiness? Call an instructor and go get some practice.
In the meantime, here are some tips as to what to expect for your next night flying experience.
Your Eyes Are Very Important. This may seem like an obvious statement, but night vision can be affected by many things. Before you takeoff, you want to make sure you can see in the dark. The FAA recommends no bright lights 30 minutes prior to takeoff. They also recommend using oxygen at night as this greatly improves night vision, even at low altitudes. Use off center viewing to help spot traffic or other objects in the air. Finally, when preflighting, use a red flashlight as much as possible, but if you do have to use a white light, close one eye to keep one eye from being blinded.
Utilize Approach Lights onLanding. Night landings are very different then day landings. It is very difficult to get the proper depth perception, not too mention see obstacles below you on your final approach to a runway. PAPI’s, VASI’s, and instrument approach glide slope’s become very important. If you are VFR only pilot, if your airport has a PAPI or a VASI, keep 2 white and 2 red (or 1 white and 1 red) lights. If you see 3 red (or 2 red), climb. If you see 4 red, definitely climb. If you are an IFR pilot, I highly recommend always flying an approach at night. What if your airport doesn’t have a PAPI, VASI, or approach with a glide slope? You might not want to utilize it at night. One side note on VFR flight: Clouds are nearly invisible at night. If you do fly into a cloud (a clue is your strobe lights start reflecting back at you), don’t panic. If you have an autopilot, turn it on and execute a 180 degree level turn. If you don’t have an autopilot, start scanning your instruments, keep your attitude indicator blue side up, and make a shallow 180 degree while maintaining altitude. Then call ATC, advise them what happened, and ask for help. One more note: I highly recommend that if a pilot finds that he/she will fly at night at lot, get an instrument rating and fly IFR at night. It’s much safer.
Practice Landings Before Carrying Passengers. The tendency when landing at night is to level off too high before flaring, causing the airplane to bleed off speed and energy too high above the runway. This can lead to a stall, a hard landing, and/or too high of a pitch attitude at touch down causing a tail strike. A good tip is start your level off when you can see the tire marks on the runway. Make sure you practice night landings, preferably with an experienced instructor who is night current and proficient, before carrying any passengers on board, even if you are night current, but haven’t landed at night in a while.
Night Emergencies. For engine failures at night, you are very limited on options. Unless you have a Cirrus equipped with a CAPS parachute system, you really have two options if an airport isn’t within gliding distance. Find a wide, lighted road that appears to be lightly trafficked. A word of caution, though: be careful of light poles, fences, concrete medians, cars, and buildings. The LA freeway would not be a good option (though there are exceptions to this rule as is evidenced by the picture below). The second option is find a dark spot and pray it’s a field (or the Hudson River). As you get closer, you can turn your landing light on to see what the ground looks like. If it looks good, keep the light on and continue. If you don’t like what you see, turn your landing light off and continue….
Flying at night can be the best time of day to fly. It’s usually smoother, cooler, and you get to see all the city lights. It is a very different environment, however, so make sure to get some training before darkness settles in on your next trip.
When I was working on my instrument rating back in 2007, my instructor and I did a lot of unpublished holds. In ground school, I heard a lot about holding for weather or holding due to a traffic delay. At my first job, my chief flight instructor was also a Continental (now United) captain and he told me a lot about having to hold for weather going into different places.
I heard all this, but I figured it would never happen to me when I’m flying GA airplanes.
Boy was I wrong!
I was flying a Piper Malibu into Phoenix with two passengers for Super Bowl weekend and the weather was awful. No thunderstorms, but moderate precipitation and low ceilings. We were coming into Deer Valley (KDVT) on the north side of Phoenix and about an hour out, ATC advised me that arrivals into DVT were having to hold and to expect a delay. The controller said the delay would be about 30 minutes, so by doing a quick calculation, I determined the delay would probably be all cleared up by the time I got in the area. At the time, I didn’t know if the delay was due to weather or traffic congestion.
Twenty minutes later, the controller advised me that there was still a delay. I queried what it was for and he informed me it was due to weather. He asked me if I wanted to hold or divert. I listened to the ATIS and heard the ceilings were variable from just below the minimums to just above. I told him I would hold as the TAF I saw predicted the ceilings to go up.
“Malibu, hold present position, hold east, expect further clearance 2140 Zulu.” Gulp.
At this point, my autopilot had gone out, it was turbulent and I was definitely in the soup. This was going to be fun.
After recovering my wits, I read back the clearance, then set about setting up this hold without getting too far from my present position. The Malibu I was flying had a Garmin 530 which I was using as my primary means of navigation. I was on V190, but I didn’t have all the fixes in my flight plan. What to do? And what to do fast?
The 530 has a rarely used function called a User Waypoint. It comes in handy in situations like these. On the moving map, you can turn the cursor on, move the cursor to any point on the map, and, by pressing enter, create a User Waypoint. This is what I did on V190. After I created it, I had to go to my flight plan, find the right spot, and input the User Waypoint just like I would any fix. Just a note here, when you create a User Waypoint, make sure you remember what you named it so you can find it again.
After I input the User Waypoint in the flight plan, I had to go back and activate the leg that the User Waypoint was the end point on. Then, to make sure the flight plan didn’t go to the next waypoint once I crossed my User Waypoint, I had to press the OBS button on the 530 in order to put the GPS in suspend mode.
Keep in mind, my autopilot wasn’t working, so this involved a lot of multi-tasking!
That’s how to do a present position hold using the Garmin 530. Got all that? Here’s a concise review:
Create a User Waypoint
Turn the cursor on by pressing the FMS knob
Move the cursor to the point where you want your User Waypoint
Press enter and name the User Waypoint
Press the Flight Plan button
Input the User Waypoint into your flight plan at the proper point
Activate the leg that the User Waypoint is the end point on
Finally, press the OBS button to put the GPS in suspend mode
After you’re cleared onward, just press the OBS button again to take the GPS out of suspend mode
Throughout the whole event, I learned quite a few things both about flying and about myself. Here are some of the lessons which I have taken away from the accident:
No flight is routine: When I took off that morning I was about as relaxed as I could have been while going to fly. I was flying an airplane that I knew well, in beautiful weather, to familiar airports and even carrying passengers which I had taken on this exact trip more than a dozen times. The accident brought into startling clarity that anything can happen at any time. I had done everything right that morning (preflight, weather briefing, planning, etc) , and none of that did anything to stop the deer from jumping out onto the runway. All we can do is ensure the items we do have control over are covered and try to be prepared to deal with anything else that arises. This ties directly into my next point:
Making sure everything is correct: When you do go fly, make sure that you have all your paperwork and personal details taken care of. I can think of a few times over the course of my flying career where something wasn’t quite right with the paperwork, or perhaps I had forgotten my wallet and I was tempted to go fly anyway. “It’s 8pm on Sunday, I’m not going to get ramp checked.” Well, I can assure you that the paperwork and questionnaires which were required to be submitted to the FAA, NTSB, and Insurance companies would have uncovered any discrepancies in my logbooks, currency, or legality. It isn’t worth the risk of flying without having everything in place just in case something happens. It isn’t just a random ramp check which can get a pilot into trouble.
Ask for help: The story of my collision with a deer would have had a very different outcome if it weren’t for the help that I received from countless the people on the ground. If you’re ever in a situation where you could use a hand, don’t be afraid to ask for help. If I had simply turned around and landed back at Wings, I wouldn’t even have had any idea that my landing gear was missing! The people in the control tower, the maintenance guys, the approach controllers in Philly, the emergency responders, and many more people all played their part in orchestrating a successful outcome.
Airplane sitting on the runway after the firefighters had checked it out Photo credit: www.lancasteronline.com
Dealing with the Paperwork: I have had dealings with the FAA before, but never for an accident. I was afraid that the investigation would be a witch hunt and I would have to defend myself while someone poured over all my planning and paperwork looking for potential errors. But, my fears were totally unfounded. Although I did have to answer many phone calls, write many reports, and fill out much paperwork, the FAA, NTSB, and Insurance companies were very patient in waiting for my responses and even complimentary in how the situation played out. I really enjoyed working with all of them and appreciated their encouragement and help.
Emotional Response: After the dust had settled and the smoke had cleared, I was left standing on the side of the runway with the passengers and my boss. I offered to fly them back to Philadelphia or continue to Pittsburgh and assured our Chief Pilot that I was feeling fine and ready to fly again. Fortunately, there wasn’t a need. Over the next week or two, I noticed a change in myself. I wasn’t fine. I have never had headaches, but shortly after I landed I developed a headache that didn’t go away for days. I had trouble focusing on anything and I had trouble finding motivation to do much but sit and stare at a wall. I wasn’t sharp and I caught myself making silly mistakes in my normally routine activities. I wasn’t depressed, or sad, it was just an unwanted mental and physiological response to the stress and shock of what happened that morning in the Baron. I didn’t feel like myself for quite some time and I even found myself a little on edge whenever I lined up for takeoff on subsequent charters for while afterward. Eventually I started to feel normal again, but it was a slow process.
Feather the Props: I can’t tell you what a difference it makes when those props go from wind milling to feathered. It became clear to me that feathering a prop could make a huge difference in deciding the outcome of an emergency situation.
Good training and checklists usage: This one is pretty straight forward, but it’s worth mentioning. Good training and proficiency make all the difference when the odds are against you. Make sure that you use all your resources when your back is against the wall, and that includes the checklists. Under the stress of the flight I had forgotten to close the cowl flaps and would likely have landed with them open without the aid of the Emergency Procedures Checklist. This would have resulted in unnecessary damage to the airframe.
No need to rush: There is no denying that I had things stacked in my favor that day. I had nice weather, extra gas, daylight hours, and even the luxury of landing at my home airport. But, regardless of all those variables, there is no need to rush into anything. Ask questions, find answers and come up with a plan. Obviously not all emergencies present the pilot with the luxury of time, but use all time and resources you have to your advantage.
Polish up those procedures: The deer accident really made me want to go out and brush up on all the emergency procedures which I hadn’t performed since my last checkride. The realization that I could need any of them at any time was really hit home after I hit that deer. Additionally, make sure you know who to call if something ever does happen.
Know the systems: Familiarity with the systems on the airplane makes it easier to troubleshoot and solve issues on the fly and makes it easier to spot a problem in the first place. Knowing how systems work and what their normal indications should be helps make decisions regarding when to divert and where to land easier.
The irony isn’t lost on me that the last article that I wrote for this newsletter dealt with how to avoid making gear up landings and the high cost required to repair one. I never would have imagined when I wrote that article last fall that I would be writing one only a few months later detailing my own gear up landing.
The bottom line is that there is nothing a person can do to prepare for every situation which might arise throughout the course of a flight, and it’s also impossible to know which emergency you may have to deal with if a situation arises. All we can do is stack odds in our favor by making sure that we address the things within our control such as aircraft maintenance, careful flight planning, checking weather, and having personal minimums set in place to keep us from flying outside of our skill sets and comfort zones.
Additionally, ensuring that you are knowledgeable and proficient in your aircraft’s procedures will give you the best chance for success. When things start going wrong, keep calm, and ask for help. Work the problem instead of guessing or rushing into a less than desirable solution. No one wants to be caught in an emergency like a deer in a landing light!
Andrew Robinson is an airline pilot for Piedmont Airlines. He is a former 135 Charter Pilot and flight instructor who lives with his wife and 2 daughters in Pennsylvania. He instructs in Beechcraft Bonanzas.
My first chief flight instructor had an addage he would impart to his flight instructors when we began working at that flight school. “Pitch + Power = Performance” he would tell us. Then he’d glare at us and follow up with, “nobody teaches that right, so make sure your students know it.”
Now, having been a CFI for seven years, I would tend to agree with him. I have moved on from doing mostly primary training to transition training. Transition training is taking someone who is already a pilot and teaching them how to fly a different type of airplane. In jets, you get a type rating. In piston engine airplanes, there is no FAA requirement to go through any type of extra training as long as you are rated in category and class (eg. single engine piston). But, insurance companies know that Mr. Fresh Private Pilot can’t just hop from a Cessna 172 into a Cirrus SR22 or a Bonanza, so they require transition training before insuring those pilots.
What did my chief instructor mean when he imparted his wisdom? He was speaking about a particular phase of flight, the final approach phase, regardless of whether it’s a VFR approach or an IFR approach. The pitch of the airplane and the power setting of the airplane have to be utilized together to achieve the proper speed and descent rate (performance).
VFR
On the final approach leg of a VFR pattern, most piston engine aircraft are configured with landing gear down and flaps down in the landing position. This puts the airplane on the back side of the power curve in the region of reverse command. In the region of positive command, in cruise, for example, the more power you add, the faster you are going to go and, if you pitch up, you will go up and you pitch down, you will go down. But, they work together (if you point the nose down, you will accelerate unless you reduce the power); remember, Pitch + Power = Performance.
In the region of reverse command, the pitch controls the airspeed and the power controls your rate of descent, but, again, they work together. Let’s say the airplane is 5 knots above it’s approach speed on final. Initially, the pilot will need to pitch up slightly to bleed off that airspeed. The airplane will want to climb, so as he is pitching up, he’ll need to make a slight power reduction to stay on glide slope.
Alternatively, let’s say the airplane is high, but is on speed. The pilot will make a power reduction to descend to the glide path, but he’ll also need to pitch down to maintain the proper airspeed.
What you don’t want to do is this: if the airplane is high on final, don’t push the nose down to try and get down. This does cause the airplane to lose altitude quickly, but the airspeed increases quickly. With a higher airspeed, the airplane has a lot more energy to dissipate when it gets to the runway, meaning you’ll float longer which can lead to forcing the airplane down or using up too much runway and not being able to get the airplane stopped in time.
IFR
On an instrument approach, you are on the front side of the power curve. When trying to stay on glide slope, the power is controlling the speed of the airplane and the pitch is keeping the airplane on glide slope. This can be a little bit confusing for VFR pilots transitioning to instrument approaches as they are not used to being on the front side of the power curve.
Keeping in mind that Pitch + Power = Performance, let’s put the airplane above the glide slope on an ILS approach. In order to get down to the glide slope, the pitch needs to be lowered as much as needed (it’s always better to pick a pitch attitude to fly and see if it is working to bring the glide slope back to center. If it doesn’t work, pick a new one. Don’t just push the nose down until the glide slope moves) and the power needs to be reduced to maintain airspeed (again, pick a specific power setting). Once the glide slope centers, then the pitch will be raised slightly and the power will need to be increased to hold glide slope and speed respectively.
Figuring out the pattern altitude at an airport should be pretty simple, right? But, in this day of helpful technology, most pilots actually get it wrong. How can you always get it right? Well, it just takes about an extra 15 seconds. Here’s how.
John Wayne Airport Traffic Patterns
As outlined in the Aeronautical Information Manual, section 4-3-3, “traffic pattern altitudes for propeller-driven aircraft generally extend from 600 feet to as high as 1,500 feet above the ground.” Further, in the Pilot’s Handbook of Aeronautical Knowledge on page 13-10, it states: “1,000 AGL is recommended pattern altitude unless established otherwise.”
Okay, so for piston driver’s, we’ve got it narrowed down to 1,000 AGL (Above Ground Level for those who don’t like acronyms). But wait! There’s that very important phrase at the end of the last quote: “unless established otherwise.” That means not all airports have traffic pattern altitudes of 1,000 AGL, or else they wouldn’t put that line in there!
How do you find out what the TPA (Traffic Pattern Altitude) is for a certain airport if it’s not 1,000 AGL? Great question! Your first guess is probably to look on Foreflight. Though this is a good start, it is not the full answer.
Let’s use an example. Look up KAQO, the Llano Airport on Foreflight. At the top of the page, the airport elevation is stated as 1,101′ MSL and the pattern altitude is stated as 1,902′ MSL. From what we just learned, 1,902′ MSL is not 1,000 AGL, so is 1,902′ MSL otherwise established?
On the Airports page with KAQO pulled up, tap the A/FD tab, second to last on the left. Scroll down to Llano Muni. Read the whole entry. Does it state in the entry that pattern altitude is different than 1,000 AGL? It sure doesn’t. So, because it is not otherwise established, pattern altitude at KAQO is 2,102′ MSL not 1,902′ MSL.
Where did Foreflight get that? I have no idea. Too often, though, pilots look at the Foreflight pattern altitude and don’t actually check the Airport Facilities Directory (A/FD). Then, they get the pattern altitude wrong.
What does it look like when pattern altitude is otherwise established? Look up KSGR, Sugar Land Regional, on your Foreflight app. Foreflight states the elevation as 82′ MSL and the Pattern Altitude as 1,000′ MSL. Is this correct? Well, tap that A/FD button again and let’s find out.
On the second line of the A/FD entry, it says TPA-See Remarks. Down in the remarks section, we find the following:
TPA-1000 (918) single engine piston acft, TPA-1500 (1418) for twin and turbojet acft, TPA-500 (418) for helicopters within 2NM.
Foreflight got it right this time for single engine pistons, but if you are in a twin, the pattern altitude is different. What’s the lesson here? Always check the A/FD and don’t always go by what Foreflight says. The A/FD is always right and usually has a little more detail to help set you straight.
One last thing. Both the AIM and the Pilot’s Handbook of Aeronautical Knowledge, when talking about pattern altitude, state, “When operating at an airport, traffic pattern altitudes should be maintained unless otherwise required by the applicable distance from cloud criteria in…section 91.155.” 91.155 defines basic VFR weather minimums. So, to fully interpret what the AIM is saying, we have to take into account the type of airspace we are in to determine if we can safely and legally operate at pattern altitude at a particular airport.
For example, let’s say we are at KCVB, the Castroville Airport. Pattern altitude there is 1,602 feet, which is 829 AGL. CVB is Class G airspace up to 700 AGL, then Class E above that. Let’s say there is a 700 AGL broken cloud layer. Pattern altitude is 829 AGL, so you won’t be able to get up that high with a broken ceiling. What altitude can you do pattern work at to stay legal?
Class G VFR weather minimums during the day below 1,200 AGL is 1 SM visibility and clear of clouds. So, legally, you could fly at 699 AGL (which at CVB would be 1,472 MSL) while in the pattern and be legal. Safe? Maybe, but probably not if you are skimming the base of the clouds. Is 1300 MSL a safer pattern altitude in this example? Well, that is 527 AGL, so probably not, since towers tend to stick up that high sometimes.
Let’s go back to KSGR and put a 1,000 AGL overcast ceiling there. SGR is Class D airspace and we already determined pattern altitude there was 1,000 MSL for piston singles. VFR visibility and cloud clearance requirements in Class D airspace are 1,000 feet above clouds, 500 feet below clouds, and 2,000 feet horizontally from the clouds with 3 SM visibility. In order to stay 500 feet below the clouds, you would be flying a 582 MSL pattern. Safe? Probably not, though it is legal.
To summarize, don’t take Foreflight’s word for pattern altitude. Cross reference the A/FD (it only takes 15 seconds at the most) to verify. If it’s cloudy, it’s really best to stay on the ground, but if you want to find out your legal pattern altitude with a cloud deck, cross reference 91.155. I don’t recommend flying below pattern altitude because it is there for a reason.
