Cirrus SR22 Partnership in Houston

Reading Weather Prog Charts

ByHank Gibson January 27, 2015July 14, 2026

There are a multitude of weather products out there today to assist pilots in preparing for a flight.  Aviationweather.gov is the best source for getting all the information a pilot needs for planning a flight.  Aviationweather.gov is the National Weather Service’s source for all aviation related weather products.  When I teach about weather and weather briefings, I recommend to my students to utilize Aviationweather.gov in the planning stages, but still call the Flight Service Station to get a full fledged weather briefing before takeoff.

When preflight weather planning, one of the best ways to get a picture of what is happening over a broad area is utilizing the Low Level Significant Weather Prog charts.  The Prog chart gives a forecasted 12 and 24 hour picture of what type of weather to expect over the US.  The Prog chart gives the expected flight rules, areas of turbulence, and where the freezing level is located.  If you’re looking at the 4 panel view, the Surface Prog chart shows fronts, pressure areas, and areas of expected precipitation.  That covers just about everything, doesn’t it?

I believe the Prog charts are underutilized in planning.  Foreflight and Garmin Pilot have given easy access to radar pictures, satellite pictures, METARs, TAFs, and several other sources of weather information.  But, a lot of the easy access data you can get from those apps is current data (with the exception of the TAF) while a lot of the forecast data takes some hunting around.  So, products like Prog charts aren’t often utilized.

The other problem arises when pilots know about Prog charts, but don’t know how to read them, then don’t know how to find the legend to decipher the chart, the chart is often set aside and quickly forgotten about just because of a lack of knowledge.  Have no fear, though, as now we will use an example 4 panel Prog chart to decipher the lines and colorations.

Just looking at the Low Level Significant Weather Prog Chart above, it can be a little confusing.  That’s why they make a legend!

Coupling the legend with the chart above, we can determine some things.  First, California, parts of the Pacific Northwest, a small part of southern Arizona, and a good portion of the Midwest and East coast are going to have marginal VFR conditions in the next 12 hours.  Wisconsin, Illinois, a good portion of the Northeast, and a small portion of the Pacific Northwest will suffer IFR from IFR conditions.  There are going to be a good amount of low level turbulence in the northern and eastern parts of the country.  Finally, the freezing level starts at the surface running in a jagged line across the midwest states and curling up into the Northeast.

That’s a good bit of information, isn’t it?  If a pilot is planning a VFR flight into the Northeast tonight, it would probably be best to wait for another day, according to this chart.

Now, to see what is causing the conditions above, we need to look at the Surface Prog Chart.

The green circular areas above show that some form of precipitation is in that area.  The circular dots with the triangle located in Mexico and Baja California are depicting moderate rain showers.  If the triangle was gone, it would just be moderate rain.  In the northeast, all those symbols are showing moderate to heavy snow showers.  Across the plains, we see a lot of high pressure, meaning visibility and nice flying weather.

These charts are invaluable when it comes to flight planning, especially over long distances when the weather could be changing a lot over the period of your flight.  Put them to use the next time you are planning a trip and you’ll learn you have a much better picture of what the weather is doing.

Thanks For Flying With Us!

ByHank Gibson December 31, 2014January 5, 2015

From our family to yours, thank you for flying with Texas Top Aviation in 2014.  We wish everyone a Happy New Year and a great 2015!

Garmin VNV

ByHank Gibson April 19, 2017

The Garmin G1000/Perspective combined with the Garmin GFC 700 Autopilot can be a great tool in descent planning.  When you want to end up at pattern altitude a certain distance from the airport or you get a clearance to cross a fix at a certain altitude, Garmin VNV is a great tool.  Here’s how to use it.

VFR Garmin VNV Use

Let’s say you want to end up at pattern altitude 3nm from your destination, but you don’t want to descend down into the bumps before you have to.  Here’s how to set it up:

• Go to the Flight Plan page on the MFD
• Press the ATK OFST soft key on the bottom of the MFD.  It stands for Along Track Offset, which, in laymen’s terms, means you are setting a point along your track a certain distance from your destination.  In this case, it will be 3nm
• Input the distance using either the keypad or the small FMS knob and press enter
• Select the altitude you want to be at (in this case pattern altitude) and press enter
• You will see a point 3nm before you destination appear on your magenta line and a Top Of Descent (TOD) appear where you need to start your descent
• 1 minute before the Top Of Descent, an indicator will appear next to your altimeter
• To have the GFC 700 Autopilot fly the descent for you, you have to do two things
  • Set the Altitude bug for the desired altitude
  • Press VNV on the autopilot
• All you have to do now is manage power

IFR Garmin VNV Use

Let’s say you are told to cross a fix at a specific altitude.  Here’s how to use Garmin VNV to plan it out.

• Go to the Flight Plan page on the MFD
• Turn the cursor on and highlight the altitude blank next to the fix in the flight plan
• Input the desired altitude
• You will see a Top Of Descent (TOD) point appear along your course where you need to start your descent
• 1 minute before the Top Of Descent, an indicator will appear next to your altimeter
• To have the GFC 700 Autopilot fly the descent for you, you have to do two things
  • Set the Altitude bug for the desired altitude
  • Press VNV on the autopilot
• All you have to do now is manage power

Flying the RDD LX7

ByHank Gibson October 10, 2022October 10, 2022

I get to fly a lot of different airplanes in my chosen career. There aren’t many airplanes that I take off in, then say “Wow,” and have a big smile on my face. The RDD LX7 was definitely one of those.

I wrote about the RDD LX7 in the past, bragging about everything I read about it. The blogs all advertised 250 KTAS and 17 GPH and FL250, all of which are eye popping numbers.

Lo and behold, those numbers are true.

I got to go up to RDD’s Redmond, Oregon facility in April 2021 to get my initial training in the RDD LX7 and I couldn’t wipe the smile off my face. The 3 screen G3X Touch layout is very impressive and not crowded like I thought it would be. Being familiar with the G500TXi, there are some G3X specifics that take a little getting used to, but overall, it’s a good system. The main GPS and number 1 radio is a GTN 750Xi.

We took off from RDM and proceeded to climb at 140 KIAS, which equated to 2,000 FPM. We only had half tanks (which is still 90 gallons of fuel!), but it climbed with no problem. It’s extremely responsive as I learned while doing the basic flight maneuvers. The stall speed of the airplane (the biggest problem with the Lancair 4P, the airframe that the RDD LX7 is derived from, was the terrible wing design and extremely high stall speed), was in the low 60s or high 50s, with the stall being extremely docile.

The airplane handled very similarly to a Columbia 400, but seemed even more responsive. The glide ratio isn’t as good as some, but it’s still better than a Cirrus (plus it still has a BRS system to boot).

The big test was the flight to San Antonio from Redmond to bring the plane home. The new owner and I departed RDM with the tanks full of Avgas (180 gallons), then got up to a cruise altitude of FL210. After setting power and leaning, the numbers came out true to spec: 252 KTAS, 17.5 GPH.

The greatest part? We stopped in Santa Fe to stretch our legs and we didn’t need fuel. We still had 100 gallons left! That left us plenty to get to San Antonio with 40-50 gallons left over. Another RDD LX7 owner flew his piston direct from Redmond, OR to Jacksonville, FL, non-stop. It was over 9 hours. That’s impressive.

You can’t beat the purchase price, either. A new Cirrus SR22T runs a little north of $1.2m. A piston engine LX7, that is pressurized, 70 KTAS faster with a much longer range, and still has a BRS, is between $850,000-$900,000. An LX7 starts to make a whole lot of sense when you weigh all that. There is also a PT6 option with several different sizes and horsepowers to choose from, which costs more, but you see 300 KTAS.

To learn more about the RDD LX7, check out the company’s website: RDD LX7.

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.