After Market Ice Protection

A Complex Clearance?

ByHank Gibson August 25, 2017August 29, 2017

I was flying in the Rio Grande Valley in south Texas a few weeks ago and heard an IFR clearance given to a King Air that pricked my ears up.  It was a clearance from CRP to LRD, but the routing was one you don’t hear too often anymore.  Because of active military airspace, the routing was via a radial and DME off the CRP VOR (so a point defined by the radial and DME) to another radial and DME point off the LRD VOR.

It took me a second to think about how to do this the easiest (without setting up the VOR and watching the DME).  After a moment’s thought, it’s actually a snap with the G1000.  You create 2 user waypoints, one for each Radial/DME spot, then put those 2 user waypoints in your Flight Plan.

Here’s how.

Step 1

Using the big knob, go to the Waypoint chapter.  Once there, scroll down to the User Waypoint page using the small knob.

Step 2

Press the New soft key.  If you want to name the waypoint something specific, you can do that at the top of the page.  If not, it will default to something like VOR 1 or VOR 2.

Step 3

Under Waypoint Type, use the small knob to select RAD/DIS (stands for Radial/Distance).

Step 4

Under Reference Waypoints, again using the small knob (or your keypad), type or dial in the VOR identifier, the radial from that VOR, and the DME distance.  Press enter and you are done.

Once you have both User Waypoints created, then just put them in your flight plan (if you forget what you named them, you can just go back to the User Waypoint page), and off you go.

Cirrus Announces The New Cirrus G6 SR20 & SR22

ByHank Gibson January 12, 2017

Earlier this month, Cirrus announced the new Cirrus G6 SR20 and SR22.  To the naked eye, they look like incredible airplanes.  There is new lighting and the updated Cirrus Perspective+ avionics in both models, plus the SR20 is now a Lycoming powered airplane.

The Perspective+ in the Cirrus G6 is based on Garmin’s G1000 NXi platform.  The keypad is updated to a QWERTY keypad, allowing for quicker inputting of data since our fingers are already used to the setup.  A home button was added to the center stack to get back to the map page without having to hold down the CLR key.  The bug knobs were moved down to the autopilot, while the display of the GFC 700 was altered slightly to match the Vision Jet setup.

The Perspective+ also boasts a 10-fold increase in processor speed, allowing the system to move quicker than the standard Perspective.  The ability to wirelessly update databases has also been included.

The exterior of the Cirrus G6 SR22 and SR20 models has changed as well.  Cirrus has added the Spectra wing tip lighting system to the Cirrus G6.  It incorporates an entire light panel that runs the length of the wing tip.  The LED dual strobe setup helps with aircraft visibility and ramp appeal.

The SR20 engine has been changed to the Lycoming IO-390, 215 HP engine.  The Continental IO-360-ES 6 cylinder engine comes out of the SR20 and the 4 cylinder Lycoming goes in.  2 less cylinders will help with useful load and the extra 15 HP will help with takeoff and climb performance.

The new Cirrus G6 is available for order and delivery immediately.  To read all the details and specs on the Cirrus G6, you can check out Cirrus’ website.

Aircraft Purchase: The Logbook & Pre-Purchase Inspections

ByHank Gibson July 10, 2014July 14, 2026

Your about to make your dream aircraft purchase.  The plane has low time on the engine, is reasonably priced, and, according to the seller, has no damage history.  You are overjoyed!  Your dream of making an aircraft purchase is finally coming true.  You prepare your offer for the seller, set up the escrow account, and start all the paperwork.

Two weeks later, the airplane is yours!  You start flying it, though, and the engine starts to have some strange vibrations.  After several flights, it starts to get worse.  You take it to your mechanic to get it looked at and you find out the airplane needs three new cylinders along with some other engine work that is going to total a lot of money.  Plus, your airplane is now going to be in the shop for several weeks.

All that excitement you just had?  It just went out the window.

Could this have been prevented?  Probably so, with a logbook inspection and a pre-purchase inspection.

Aircraft Purchase: Logbook Inspection

Inspecting a logbook can be very daunting when making an aircraft purchase, especially for older airplanes.  This is, however, one of the most vital steps in making a new aircraft purchase.  You can find out many things from looking at the maintenance logs of an airplane.  First, you can check the compression levels of the engine.  Typically, you want compression levels in the 70’s, with it still being okay in the high 60’s.  Anything below 65 and there could be potential problems.

Second, you can find out if there has been any odd maintenance done pointing to possible unreported damage history.  This is rare, as most aircraft owners are honest and up front when talking about damage history.  But, if there is an entry detailing a prop overhaul after only 50 hours on that prop, you may start to ask some questions.

Third, you can find out how well the airplane has been maintained.  If a lot of maintenance was completed at each annual, even if it was a lot of small things, then the airplane has been maintained by a good mechanic who is very thorough.  This also involves a check of the ADs, Mandatory SBs, SBs, and SLs that have been issued for the airplane.  If all that has been kept up with, it’s a well maintained airplane.

Finally, it gives you a good idea of how much the airplane has been flown.  Sure, the ad online will have the total time and time since overhaul, but you can look at the year by year breakdown of how much the airplane has been flown.  It may have been flown a lot earlier in it’s life, but not quite as much recently.  That’s not necessarily a bad thing, but airplanes like to be flown.

Aircraft Purchase: Pre-Purchase Inspection

Before making an aircraft purchase, it is extremely vital that whenever you are buying an airplane that you get a pre-purchase inspection done on the airplane.  Even better is getting one done by a mechanic who specializes in that type of airplane (eg. Piper Service Center for Pipers, Cirrus Service Centers for Cirrus, Kevin Mead for PA-46s).  A pre-purchase inspection can save you a lot of money in the end.

There is always going to be some kind of maintenance issue with an airplane being purchased, whether it is big or small.  Once a pre-purchase inspection is completed, you can take the findings to the seller and negotiate for a lower price based on those findings, or just have the seller fix the items before the sale is completed.

I would recommend having the seller fix the problems before the sale is completed.  Even though it may take a little longer for the sale to be completed this way, you’ll get to enjoy your airplane right away instead of it being in the shop the next several weeks after you complete the purchase.

There is the circumstance where the  pre-purchase inspection reveals some serious airworthiness issues which would cause the deal to be voided.  Always put this clause in a purchase agreement, giving you, the buyer, an out if there are serious airworthiness issues.

When it comes to making an aircraft purchase, it is not a process to be rushed.  Slow and steady usually gets the best airplane for the money, giving you years of enjoyment in the future.

Looking to make an aircraft purchase?  Daunted by all the work that’s involved to find a good, quality airplane?  Let Texas Top Aviation do your aircraft search for you!  To learn more, visit Texas Top Aviation’s Aircraft Purchase Consultations page.

Oh, Deer (Part 1)

ByAndrew Robinson March 7, 2017April 5, 2017

As far as I knew when I woke up, October 26, 2016 would be an ordinary day for me. It was a Wednesday, and I was scheduled to fly our Company’s BE58 Baron on a charter from Wings Field (KLOM), a non-towered airport just north of Philadelphia, to Pittsburgh International Airport (KPIT) and spend the day there waiting for my 3 passengers to finish up their meetings. The plan was to fly them back to Wings that evening and then make the short hop back to home base at Lancaster, PA. (KLNS).

It was a flight that I had done countless times, and I was comfortable with the airports, the passengers, and the airplane. Everything went smoothly that morning and my short flight from Lancaster to Wings was uneventful. I even made it there in time to spill coffee all down the front of my pants before my passengers arrived. The weather was clear, calm and beautiful as we loaded into the Baron and the sun was just starting to come up as I taxied toward runway 24 for departure. I was departing VFR and had an IFR plan on file which I intended to pick up with Harrisburg Approach once we were airborne. According to my calculations, I was on schedule to be drinking my coffee at the Pittsburgh FBO right around 8:30.

At 7:05, I advanced the throttles for departure. A few moments later, I received a very unpleasant surprise. I was quickly approaching rotation speed when 2 deer ran onto the runway directly in front of the aircraft. It was still dark enough that I was relying on my landing/ taxi lights to illuminate the runway for take-off.  As a result, I was unable to see the animals before it was too late. I don’t remember making a conscious decision to pull back on the yoke, but it was that or plow directly into them at about 85 knots. I pulled up as quickly as I could and the airplane rotated immediately.  A fraction of a second later I heard and felt a sickening THUD.

There was no doubt that I had hit one of them, but, somewhat unbelievably, the airplane was climbing as though nothing had happened. I put the nose down to get the airspeed back up and began to try and piece together what damage the airplane had sustained. Based on the noise and the feeling of the impact, my suspicion was that I had hit the deer with the left main landing gear. A review of the instrumentation showed no abnormalities and the airplane was behaving normally, so I didn’t suspect any damage to the airframe/ flight controls. I couldn’t see anything out the windows that looked unusual, and somewhat unbelievably I still had 3 green lights.

After gaining a safe amount of speed and altitude, I turned around and told the passengers that we had hit a deer. It was obvious that we had hit something and I was sure that they wanted to know what was going on. Then, I checked all my indications again and satisfied with what I was seeing, tried to bring up the landing gear. No dice. When I pulled the gear lever to the up position, the master “GEAR UP” warning light came on and I got a horn. There was never any change in the 3-green indication and the gear motor never came to life at all.

At this point it was obvious that, minimally I was going to have to divert to Lancaster and have the maintenance guys look at the airplane to see if anything was broken. I figured that they would either give me the green light to continue or I would just jump into one of our PC12s and complete the trip while they worked on the Baron.

The landing gear’s refusal to come up was my first indication that there was substantial damage. I set course for Lancaster and called our Chief Pilot. After explaining the situation to him, we agreed that KLNS was the best option and that he would let the maintenance guys know that I was coming.

The logic was that proceeding to Lancaster would allow a visual check of the landing gear by maintenance people as well as the tower and result in the safest outcome if an emergency landing were required. Lancaster would likely have better services available in terms of emergency responders and, not to mention, I was fairly certain that there was a dead deer on the only runway at Wings that I didn’t feel like hitting for a second time. In addition, the relatively long runway at Lancaster combined with light traffic at that time of day made it the ideal option to divert to.

I again turned around to brief the passengers. I told them that we were going to have to make precautionary landing before continuing to our intended destination and that I would be performing a few low passes for the tower.

Due to the drag from the landing gear, the flight to Lancaster seemed to take forever. The long cruise home, however, gave me time to try and reach someone on the ground at Wings in hope of having the runway inspected and cleaned off before other traffic tried to use it. After several attempts to raise anyone on the Unicom/ CTAF frequency, I called Philadelphia Approach for help instead. Philly answered right away and I explained to them what had happened. I requested that they call over to Wings on the phone or send someone out to check the runway. They told me that they would get it done and asked if there was any other way that they could assist me. I told them I was headed to Lancaster and that I appreciated their offer, but didn’t require any further assistance. I then switched over to Lancaster Tower and let them know that I was about 15-20 minutes out, but I would need to perform a couple of passes to have them check my gear. The tower cleared me for a low approach over runway 26.

I arrived at LNS at about 7:30. I performed my first low pass by the tower, not really expecting anything to appear out of place. I figured I had bent something or damaged the squat switch, but not much more. I climbed to pattern altitude and awaited the good word. Shortly after the fly-by, Tower reported that the left main gear didn’t appear to be down and locked. They suggested that I make another pass. The airport maintenance personnel chimed in, reporting the same. We had just started discussing whether cranking the gear a little by hand might help when Philly approach called the Lancaster tower on the phone.

Philly informed Lancaster that someone had inspected the runway at Wings and found the left main strut and wheel in the grass. I quickly concluded that cranking the gear down probably wouldn’t help!

To Be Continued…

(Read Part 2 Here)

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.

Garmin 530/430 Missed Approaches

ByHank Gibson May 25, 2016May 29, 2016

Flying a missed approach can be stressful enough.  When you haven’t done one in a while and your GPS isn’t showing you how to get to the missed approach point and you can’t remember which button to press, that adds a lot more stress.  Recipe for disaster?  Quite possibly!

No need to fear, we are here to help.  The procedure for getting a Garmin 530 or 430 to give you missed approach guidance is actually simple and straightforward, if you know what to do!

Note: Because of the variety of different autopilot configurations in different airplanes, this article will focus solely on the GPS.

What the GPS is Thinking

The way Garmin designed the Garmin 530 and Garmin 430 is to be as helpful to pilots as possible.  Their thinking was, 95% of the time, a pilot will make a landing on an instrument approach.  This is pretty accurate as most of the time, this is what happens.  Most general aviation pilots don’t fly approaches to minimums all that often, thus negating the need for a missed approach.

Garmin designed their software with this in mind.  When an airplane crosses the missed approach point, the GPS will go into what’s called suspend mode (a SUSP annunciation appears above the OBS key).  It will keep the missed approach point as the active waypoint because it assumes the pilot is going to land.

This can be confusing to pilots.  This is what happens when software engineers and pilots come together. Engineers often believe they are smarter than pilots! (See the Airbus fly by wire roll out)

The Procedure

In the case of a missed approach, the button pushing on the GPS is actually relatively simple.  There is no SUSP key to take the GPS out of SUSP mode (thanks Garmin!).  Instead, you press the OBS key.  This will take the GPS out of SUSP mode, making the first waypoint on the missed approach procedure the active waypoint.  Your GPS will now give you guidance on the missed approach procedure.

If you are going missed off an ILS, LOC, or VOR approach, then there is one more key you’ll have to press. Your CDI needle (whether it is digital or analog, an HSI or just a CDI gauge) will be reading off the NAV radio and your CDI indication on the GPS will be VLOC.  After you press the OBS key, press the CDI key on the GPS so you will start getting course guidance from the GPS again.

That’s it.  Button pressing on the different autopilots will vary, but if you are familiar with yours, you’ll be able to tell it to follow the GPS and climb to the proper altitude.