News

Cirrus CAPS Saves Lives Again

ByHank Gibson September 9, 2015

In July, a Cirrus SR22 suffered an engine failure in Houston after departing KIAH. The CAPS system was deployed and the airplane came to rest in a neighborhood on the north side of Houston. This makes CAPS save number 53 for Cirrus and no fatalities. The initial NTSB report is below.

14 CFR Part 91: General Aviation
Accident occurred Tuesday, July 07, 2015 in Houston, TX
Aircraft: CIRRUS DESIGN CORP SR22, registration: N422PB
Injuries: 2 Minor.
This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.

On July 7, 2015, about 1137 central daylight time, a Cirrus SR-22 single-engine airplane, N422PB, descended under the canopy of the cirrus airframe parachute system (CAPS) and landed in a residential neighborhood at Houston, Texas. The pilot and passenger sustained minor injuries, and the airplane was substantially damaged. The airplane was registered to and operated by AIRCCS, LLC; Humble, Texas, as a 14 Code of Federal Regulations Part 91 business flight. Day visual meteorological conditions (VMC) prevailed and a flight plan had not been filed. The airplane departed George Bush Intercontinental/Houston Airport (IAH), Houston, Texas, at 1133 and was destined for Austin Bergstrom International Airport (AUS), Austin, Texas.

The pilot reported that during initial climb, he noticed the engine temperatures began increasing and he reduced power in an attempt to lower the engine temperatures. When the airplane was about 900 feet above ground level (agl) the engine began detonating, and soon after there was a complete loss of engine power. With no suitable forced landing areas the pilot deployed the CAPS ballistic parachute system and the airplane impacted terrain and came to rest upright next to a residence.

An initial on-scene wreckage examination showed there was adequate fuel on-board. At the facility where the airplane had most recently been refueled, refueling unit records and a review of security camera video showed that the airplane had been refueled with aviation gasoline and not with jet fuel. Postaccident fuel quality checks of that fuel facility were satisfactory.

The wreckage was moved to a different location and will be further examined. Several avionics components containing non-volatile memory (NVM), including engine performance data, will then be removed from the wreckage for examination and an extraction of useful data is expected.

At 1053 the Automated Surface Observation System at IAH reported wind from 160 degrees at 15 knots gusting to 20 knots, visibility 10 miles, scattered clouds at 3,000 feet agl, broken clouds at 25,000 feet agl, temperature 31 degrees Celsius (C), dew point 24 degrees C, and an altimeter setting of 30.03 inches of Mercury.

IM SAFE: Are You Really?
ByHank Gibson February 16, 2016

As pilots, we are all familiar with the IM SAFE acronym that the FAA puts out. It comes up as part of the ground training over Human Factors during private pilot ground school. We all memorize it, spit it out for our check rides, then most of us promptly forget about it.

When I was training for my pilot’s licenses, I was at a Part 141 school that was very standardized (LeTourneau University, who has a fabulous aviation school). Before each flight, we had to do a self evaluation based on the weather and the IM SAFE checklist. Based on our answers, we would then determine if the conditions were conducive to flying as well as if I was physically okay to fly.

This was a great tool because not only do pilots have to pre-flight the airplane, they also need to pre-flight themselves. It’s very easy to fall into one of the “Hazardous Attitudes” if there is a pressing meeting or you haven’t flown in a while and it’s a beautiful day, but maybe you aren’t physically fit to control an airplane.

Let’s break down the IM SAFE checklist to dig a little deeper into the physically fit side of flying.

Illness

This one is pretty easy. Are you sick? If so, how sick? If you can’t hardly talk or your body feels like it was hit by a truck, then flying probably isn’t in your best interest.

The tricky area can become if you are only a little sick. Maybe you have a cough or a little cold or a headache is starting to form. You probably could go fly, but is it really a good idea? It could be something worse, or it may be nothing. You have to know yourself and put limits on yourself before you wake up on the day of your big meeting two states over. Set illness personal minimums and stick to them.

Medication

There are a slew of drugs, both prescription and over the counter, that pilots cannot take and fly. AOPA has a hotline to call for pilots to find out if they can fly with the medication they are taking, or what meds they can take to give them relief and still operate an aircraft.

Another great resource is your medical examiner. Just give him/her a call and they will be more than happy to let you know what you can and can’t take. They’ve been educated in the area of aviation so they are very knowledgeable.

Stress

This is a huge one that pilots ignore a lot. Maybe it was a stressful day at work, maybe you are running late to the airport, your meeting got moved up, whatever. Stress can jump on you and mess up a pilot’s thinking very quickly. If you have a lot of other things on your mind and you aren’t able to focus just on flying, it might be a good idea to stay on the ground.

Alcohol

Out of the whole IM SAFE list, the alcohol limitations are very clearly defined. 8 hours bottle to throttle, no more than 0.04% BAC, no operating an airplane while under the influence, and no carrying passengers who are visibly intoxicated. For your personal minimums, it’s a good idea to increase that time to 12, 18 or even 24 hours bottle to throttle.

Fatigue

Learning to fly while a college student led to a fair share of canceled flights due to fatigue. I operate best on 8 hours of sleep in the past 24 hours. I can function on 6, but anything less than 6 hours, my performance drastically drops off, sometimes to a point where I wouldn’t be safe. I discovered this while with my flight instructor attempting to do a holding pattern and completely botching it up.

I observed this as a CFI quite often. If I was doing ground with a student and they were struggling, my first question would be, how much sleep did you get last night? More often than not, if I had to ask that question, I would get an average answer of 3 to 4 hours (I even had one guy show up for a flight block on 2 hours sleep. I sent him back to the dorm).

Fatigue is very easily overlooked because it’s not measurable. Needing to get a flight lesson done or needing to get somewhere when you are obviously fatigued is not a good idea. Make sure you get a good night’s sleep before a flight and don’t be afraid to cancel if you didn’t. Set some sleep personal minimums and make them hard and fast.

Eating

Don’t skip meals and fly. Performance greatly decreases when a pilot is hungry. At the very least, stick a couple of food bars in your flight bag to give you some nourishment.

Also, stay hydrated, especially in the summer time. I carry a huge bottle of water with me on all my flights because I get headaches if I don’t drink enough. Getting dehydrated on a long flight can lead to all sorts of performance problems (over hydration is also a problem in the air, but that’s what Gatorade bottles are for, right?).

All this to say, have some personal minimums when it comes to you and your body. Check the plane, check the weather and check yourself. If anything falls in the “red” area in any one of those three categories, stay on the ground and don’t press your luck.
Texas Top Aviation Now Offers Piper PA46 Training
ByHank Gibson August 15, 2017July 14, 2026

Texas Top Aviation is proud to announce that we now offer Piper PA46 Training in the Malibu and Mirage. Our Piper PA46 training is provided with the same excellent & professional approach that has become our hallmark.

The four-day format of this course allows time to answer all of your questions about your new airplane. The Texas Top Aviation Piper PA46 training course leaves you with a confidence and understanding that will help you enjoy your Malibu or Mirage even more.

New avionics have you scratching your head in confusion? No problem. Texas Top Aviation is well versed in the latest Garmin and glass panel instrumentation.

If you are in need of recurrent training in your PA-46, Texas Top Aviation would be proud to help with that as well. Consider us your one stop shop for Piper PA-46 training.

For more information, check out our Piper Malibu/Mirage Training page.

Contact us today to schedule your Piper PA46 Training!
Flying WAAS GPS Approaches
ByHank Gibson August 30, 2021August 30, 2021

When flying a WAAS GPS approach, there are several different levels of WAAS signal that a GPS receiver can get. The most precise is an LPV signal. LPV stands for Localizer Performance with Vertical guidance. An LPV approach has the lowest minimums of all the WAAS GPS approaches, typically in the range of 200-300 feet AGL. A GPS glide path (GP) is guaranteed with an LPV approach and the minimum altitude is a decision altitude (DA).

Just like a localizer, an LPV course width get’s tighter and the CDI becomes more sensitive the closer the plane get’s to the runway. Even though the LPV approach minimums are so low and the approach is down to a DA, they still aren’t considered precision approaches by the FAA (which leads to some extra planning when selecting an airport as an alternate that only has GPS approaches, since the AIM specifies only the LNAV minimum are to be considered if an alternate airport only has GPS approaches, bringing the 800 foot ceiling requirement to bear)

An LNAV/VNAV approach is still a WAAS approach that has a GPS glidepath, but is slightly different than an LPV approach. An LNAV/VNAV final approach course does not get more sensitive the closer the plane gets to the runway. The smallest course width on an LNAV/VNAV approach is 0.3 miles either side of center. LNAV/VNAV approaches will, most of the time, have higher minimums than LPV approaches and can have minimums no lower than 250′ AGL.

The third type of WAAS approach is strictly a non-precision approach with a Minimum Descent Altitude (MDA). These are designated LP approaches, which stands for Localizer Performance. These are like old school Localizer only approaches that, similar to the lateral portion of an LPV approach, the course width tightens the closer to the runway that a pilot is. There is no glide path by definition of an LP approach, though there is a caveat.

Now, by looking at an approach plate that is a WAAS approach, but only has LP minimums listed, a pilot would assume there would be no glide path. Depending on what type of GPS unit the airplane has, that pilot could be wrong. Garmin Perspective units (Cirrus G1000), all GTN 750s and GTN 650s, All G1000 NXi units, most Garmin 430W and 530W, and all Avidyne IFD 550/540 and 440 units will display an advisory glide path on an LP approach, designated LP+V.

What does LP+V indicate? An advisory glide path is just advisory, but it is totally legal to follow down on a non-precision LP approach. The kicker is obstacle clearance is not guaranteed and the pilot needs to keep an eye on minimum altitudes at the different waypoints on the approach. The big thing I tell people is, when you arrive at the MDA and the runway is in sight, following the advisory glide path below the MDA could get you in trouble with obstacles. Don’t just hone in on your instruments when you break out of the clouds. Look out the windscreen and make sure you won’t hit anything.

If you arrive at the MDA on the advisory glide path and the runway isn’t in sight, DON’T GO BELOW THE MDA! Most autopilots won’t level off at the MDA, even if that altitude is set in the altitude pre-select, so this will involve turning off the autopilot before the MDA and manually leveling off, or engaging the altitude mode of your autopilot at the MDA.

One other type of GPS approach that you will encounter is an LNAV approach. This is a non-WAAS approach down to an MDA, but your GPS unit may still give you a +V. Most modern ones will.
Determining Pattern Altitude
ByHank Gibson October 23, 2015October 23, 2015

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.
PIREP: IFR Clearances at Uncontrolled Airports
ByHank Gibson June 17, 2019June 17, 2019

There is great news coming for all IFR pilots who utilize the multitude of uncontrolled airports across the US.

From the beginning of aviation time, the process of getting an IFR clearance at an uncontrolled airport has been arduous. For airports under Center controlled airspace, you had to dial the Clearance Delivery line, which ported you to Flight Service. Then you sat on hold till someone picked up, gave them your information, then sat on hold again while they called the Center. Finally, after what seemed like an eternity, the briefer came back with your clearance and departure instructions.

On a busy day, this could take ten to fifteen minutes, which can be really annoying when a pilot is trying to take off and get somewhere.

In my opinion, this also led to a lot of unsafe (and probably illegal) VFR departures when conditions were either clearly IFR or unsafe if buzzing around at low altitudes and high speeds in Class G airspace.

RCO’s (Remote Communications Outlet, 2nd column, halfway down) and Clearance Delivery Frequencies are in place at some airports, but by and large, the above process was how you got your clearance.

Departing from a TRACON controlled airport usually was easier and quicker. The TRACON has a direct line that is available for pilots to call to speak directly with a controller, but not all these phone numbers are published.

As of June 20th, the FAA is implementing this at all uncontrolled airports. On the chart supplement for all IFR charts across the US (not including Alaska), the FAA will publish the Center phone numbers and remaining TRACON phone numbers for pilots to call directly to receive their IFR clearances and departure instructions, and to cancel their IFR flight plans (A lot of TRACONs already have their phone number published).

Flight Service will no longer be taking IFR flight plan cancellations. Pilots will still be able to cancel with Center or TRACON in the air, but will now need to call the number on the chart supplement on the ground for cancellation.

Now that the FAA is modernizing this process, hopefully more pilots will decide to call on the ground for their clearance on a MVFR or IFR day instead of taking off and trying to pick it up in the air.

Finding the Chart Supplement on Foreflight

Where is the Chart Supplement? I’m so glad you asked.

Before iPads, everyone carried around the green book, officially known as the Airport/Facilities Directory, or A/FD. With the advent of Foreflight & Garmin Pilot & others, all the information in the A/FD is now easily accessible in each of the Apps.

Foreflight may integrate the clearance delivery phone number for each airport into their airport information page, but in the meantime, here is how to find the Chart Supplement.

On Foreflight, go to Documents along the bottom of the App. In the Catalog on the left, tap FAA. Chart Supplement will be about 1/3 of the way down the page. Tap that, then tap the region you need and it will download into your Documents Library.

Once it is downloaded, check the Table of Contents for FAA Telephone Numbers and NWS. Go to that page and scroll through to find the Center or TRACON you are needing, then dial the number.

Happy Flying!
Oh, Deer (Part 3)
ByAndrew Robinson March 21, 2017April 13, 2017

Read Part 1 & Part 2

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:
1. 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:
2. 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.
3. 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
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. 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.