I Love the Piper PA46

Simplified Instrument Approach Briefing

ByHank Gibson August 27, 2016September 12, 2016

In instrument flying, I am all about keeping things simple.  There is a ton of detail that an instrument pilot can get bogged down in.  When an instrument pilot gets bogged down, he gets distracted from flying the airplane.  When he gets distracted from flying the airplane, dangerous circumstances can happen.

I like to keep things simple.  When I first started instructing, I developed a very simple instrument approach briefing that captures everything that is necessary on an approach plate, but prevents getting bogged down in the details.

I call it the BBC instrument approach briefing.  Here it is:

Brief

First things first.  The first step of an instrument approach briefing is to brief the approach plate.  There are a bunch of acronyms out there that instructors tell their students to memorize that only cause confusion instead of helping get the plate briefed.  To keep it simple, just work your way across the plate and you’ll get all the information you need.

Start in the top left hand corner of the plate, with the approach course, then work your way right and down, as follows:

• Approach Course (or Nav frequency if flying a VOR/ILS/LOC)
• Runway information
• Notes (these are good to brief the night before as a lot are irrelevant to GA pilots
• Missed approach
• Frequencies
• Planview and MSA
• Profile View and Minimums

Simple enough, right?

Build

Now that you know what you are planning on doing, you can now take the second step in the instrument approach briefing and build the approach in your GPS.  You know your approach type, you know your transition, and you know what your minimums are.  Taking all that information, you can now build it in to your system.

Checklists

Once everything else is done, don’t forget the checklists.  The descent and before landing checklists still need to be done as part of an approach.  The best time to do these is before joining the approach so that you don’t have to worry about flying the approach and looking at a checklist at the same time.  Even better, memorize the checklist and you don’t have to look at anything!

Most importantly, you want to be configured properly for the approach by the final approach fix.  Gear, flaps set, power set, so all you have to worry about at that point is following the needles and trusting your instruments.

Oh, Deer (Part 2)

ByAndrew Robinson March 14, 2017April 13, 2017

Read Part 1 Here

Only now did I begin to realize the severity of the situation. The deer had completely broken the left main gear off of the airplane. Obviously, landing in this condition would not be ideal. Landing without a nose wheel is one thing, but landing without one of the mains would be a very dangerous and undesirable proposition.

The company’s maintenance guys arrived on the scene while I executed a few more low passes so that they could take a look. We all came to the same conclusion that the best situation for landing would be to retract the other two wheels so I could land on the belly. Unfortunately, the landing gear wouldn’t retract. Cranking the emergency gear handle didn’t work either as it is not designed to bring the wheels up, only to put them down.

I flew circles around the airport for a while as different options were all discussed. I owe a lot to the guys on the ground who were digging through the manuals coming up with solutions. Eventually, it was decided that I would try cranking the gear up by hand, even though the checklist in the airplane said that it could only be used to lower the gear. Even if we damaged the hand cranking mechanism, it would be worthwhile…plus, I’d already torn off the left main entirely, surely a little damage to the retraction mechanism wouldn’t be the end of the world!

Following the checklist, I pulled the CB for the gear motor and started cranking. To my great relief, the “in transit” light illuminated and the three green indication went away. It was difficult work to crank the gear up manually. The handle is in a very poor location in Barons and Bonanzas, plus I was working against gravity. It is also possible that there was some debris from the missing wheel causing friction or binding. While I was cranking, the rescue crews were being coordinated while extra vehicles and people had been called in from the city for support.

After some time had passed, enough to get a slightly sore arm from cranking, the lights indicated that the gear was up and locked. I lined up for one more pass hoping to verify that the landing gear was up and the landing gear doors were closed. After the final go ahead from everyone on the ground, all that was left was the landing.

I had been doing my best to keep the passengers informed of what was happening throughout the whole flight, but I felt bad for them as the news changed from the beginning of the flight: “precautionary landing” was quite different than the briefing I ended up giving them before we landed. I informed them that I was going to be “… killing the engines and landing with the gear up….” They did an impressive job of staying calm and being responsive. Before we landed, I made sure that they were all briefed on what to expect, how to unbuckle, and how to evacuate from the airplane. It is difficult to convince someone that everything is going to be fine when there are hordes of emergency vehicles (including ambulances) waiting next to the runway in anticipation of your landing.

Shortly before landing, I went through my flows and callouts, then verified by use of the checklist to ensure I hadn’t missed anything. I distinctly remember sitting in the airplane preparing for the landing, all the while being in complete disbelief that this was a real situation. I never imagined that I could be flying an airplane that was missing a wheel strut. Previously, my assumption had been that if there was an event serious enough to shear off one of my mains, the airplane wouldn’t continue flying. It all seemed like a bad dream.

I elected to use runway 26 since it was the longest. I wanted to be able to carry extra speed in order to give myself extra time between pulling the mixtures and landing so that I could feather the props and turn the fuel shut off valves to the off position (never thought I’d have to do that!) without being rushed. As I made my final approach with the engines shut off, I went through my final memory items and couldn’t help but laugh about just how backwards everything was from normal arrival procedure. GUMPS: Gas- Off (normally on the fullest tank), Under carriage- Up (Definitely not normal), Mixtures- Idle cut off (I normally save this for when I’m parked on the ramp), Props- Feathered (Again, never thought I’d have to do that in real life), Seatbelts- On (the only one that stayed the same!).

I’ve had several remarks about how quiet the airplane must have been during the final un-powered glide to the runway, and while that is absolutely true, I must confess that I never noticed. I was so focused on the task at hand that the silence in the airplane simply wasn’t something that stuck out to me. What did make an impression on me, however, was the acceleration the airplane experienced when the props were feathered. I’ve heard it preached many times the importance of feathering the propeller on a dead engine, but never truly appreciated the importance of it until I did it myself. I remember the airplane accelerating noticeably as though I had hit a boost button which was hidden somewhere in the cockpit for just such an occasion.

Although I didn’t notice the lack of noise upon killing the engines, the sickening, deafening noise which was produced during the touchdown and deceleration is something which I will never forget. Another thing that surprised me was the smoke which filled the cockpit and cabin as we slowed down. This was produced by the friction between the belly and the runway, although nothing was burning.

I don’t know how long the airplane actually slid for after touching down, but it felt like an eternity. However, when the noise subsided and the motion stopped everything returned to real time. I unfastened my seat belt, opened the door and climbed out onto the wing. I helped the passengers evacuate and we retreated to a safe distance on the side of the runway while the firefighters rushed in to do their job.

It was 8:35 am. So, from the time we took off to the time we landed was almost exactly an hour and a half. Not surprisingly, the passengers elected not to continue on to Pittsburgh and instead accepted a ride home in a car. The rest of my day was a blur of paperwork, reports, and phone calls.

To Be Continued…

Read Part 3 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.

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.

Redbird Skyport Bluebonnet Fly-In at KHYI

ByHank Gibson April 27, 2015May 5, 2015

Come out to Redbird Skyport at the San Marcos Municipal Airport on Saturday, May 30th for the Bluebonnet Fly-In.  Hank Gibson from Texas Top Aviation will be giving a safety presentation at 2pm in the large conference room entitled “Is The Approach Activate?  Flying Garmin Approaches.”

Join Texas Top Aviation and Redbird Skyport as we open the summer together at the Bluebonnet Fly-In.

To Register for the Safety Seminar, please click here.

Hold Anywhere

ByHank Gibson December 21, 2016September 24, 2018

The latest Garmin software version on the Garmin G1000 and Cirrus Perspective by Garmin has a really neat feature.  It gives the pilot the ability to create a hold at any fix, VOR, NDB, or even airport.  If the point is in the GPS database, a hold can be created over it.

How does it work?  Here are the steps.

Let’s say ATC tells you to hold over an intersection on a Victor Airway that you are already on.  Since you are tracking the airway already, the airway should be in your flight plan complete with all the waypoints on it.

Bring up your flight plan and highlight the waypoint to hold at.  Press the menu key.  Using the big knob, scroll down to highlight the hold at waypoint option at the bottom of the bottom of the menu.  Press enter.

Now you can build the hold.  You select what the inbound or outbound course will be.  Select a timed hold or a distance hold.  Then select left or right hand turns.  You can even input your expect further clearance time.  Press enter and now you have a hold as a waypoint in your flight plan.  Assuming you have a WAAS unit, the autopilot will fly the hold for you.

If you are ever told to “Hold Present Position,” Garmin has you covered.  Simply press menu on the flight plan page, scroll down to Hold Present Position, then follow the prompts on the screen to build a hold at your present position.

Synthetic Vision Technology

ByHank Gibson December 5, 2014December 5, 2014

Let’s say you’re flying in the mountains of Colorado on a cloudy day.  There’s a solid layer from the surface all the way up to 14,000 feet.  You’re inbound to Eagle (KEGE) on the RNAV (GPS) D approach.  There are mountains next to you and below you, but you aren’t concerned since you can see them all.  The base of the last reported overcast layer was 3,000 feet, so you know you’ll break out before the MDA and land no problem.

At 11,100 over AWACC, you clearly see the top of the mountain below you.  You are comfortably above it. You already have the runway in sight as well.  You pop out of the clouds on the approach at 9,700 feet, spot the airport and follow the tower’s instructions to circle north of the runway for a left base for runway 7.

How could you see the mountains inside the clouds?  You have Synthetic Vision installed on your glass panel, that’s how.

Synthetic Vision, which has actually been around since the ’70s when NASA and the US Military first developed it, was first FAA certified for the Gulfstream PlaneView flight deck in 2009.  Garmin, Avidyne, and Aspen are the main general aviation manufacturers of synthetic vision these days.  All Garmin PFDs are now equipped with Synthetic Vision while Aspen gives you the option to upgrade to Synthetic Vision when you get one of their PFDs installed.  Avidyne gives you Synthetic Vision in their R9 upgrade for the Cirrus.

What is Synthetic Vision?  Basically, it’s a 3-D picture on the primary flight display showing terrain, obstacles, traffic, and runways.  It greatly enhances situation awareness in areas of terrain or high obstacles during IFR conditions or at night.

The goal behind the development of Synthetic Vision was to decrease the amount of controlled flight into terrain (CFIT) accidents.  A CFIT accident consists of a perfectly airworthy airplane flown by a pilot (or autopilot) unintentionally into terrain. These accidents can happen in low visibility conditions or at night, but the reason is mainly due to the pilot losing track of his position in relation to obstacles or terrain (or water as was the case with JFK Jr.).

With Synthetic Vision, the goal is to enhance pilot knowledge of what is around the airplane at all times. When you’re at altitude, the terrain below you looks flat.  When you start descending down amongst the rocks, the hills or mountains start to rise up on your screen.  For those used to the coloration with the 2-D terrain feature on a GPS unit, it translates very easily to the terrain coloration on a Synthetic Vision equipped PFD. Terrain that is between 100 and 500 feet below the aircraft is shown as yellow, while terrain closer than 100 feet is depicted as red.

 

One neat feature on Garmin units is the Highway in the Sky.  When a pilot puts a course or a flight plan in the GPS, the PFD displays magenta boxes at the altitude selected displaying the route.  It’s handy when hand flying to just “fly through the boxes.”  They also display descent angles on approaches.

Synthetic Vision is still optional on Garmin and Aspen units, but I highly recommend springing for it.  It will give you a higher level of safety and keep you out of the rocks.