Hank Gibson Earns ABS Instructor Designation

Icon A5 Thought to Have Crashed in California

ByHank Gibson November 3, 2015November 5, 2015

Most pilots have seen the Icon A5 light sport amphibious aircraft.  It’s a neat design that can land on water or on a runway.  The high wing design with a pusher prop has foldable wings that allow it to be put on a trailer and towed behind a vehicle, allowing it to be offloaded at boat ramps (it also begs the question can you wakeboard behind it?).

Apparently, not all non-pilots know about the Icon A5.  Last week, one landed in the water near a beach in Southern California, but most of the beach goers and local authorities believed it had crash landed in the water.  Emergency crews were dispatched, but everyone was surprised when the two occupants crawled out on the wings, had a cup of coffee, and took back off.

You can read the full article on the Flying Magazine’s website.

Checking The Stall Warning Horn

ByHank Gibson April 27, 2019April 30, 2019

When a pilot first glances at the title of this article, the first thought that probably goes through that pilot’s head is, well that’s easy.

And it is, if you are flying a high wing Cessna. On other airplanes, there are a few tricks to checking the stall warning horn. If you get them wrong, you’re liable to get a bill from your maintenance shop for an hour of labor for a problem they couldn’t duplicate.

Cirrus SR22

Let’s start with the Cirrus. On the pre-FIKI Cirrus aircraft, there was a small little hole in the wing that contained a diaphragm. That diaphragm sensed a change in airflow at a certain angle of attack just below the critical angle of attack and set off the stall warning horn. Unfortunately, the only way to check that is to suck on the hole during pre-flight.

I don’t. I verify the hole is clear and that’s about it.

On the FIKI Cirrus aircraft, there is actually a stall warning vane. It looks like a high wing Cessna vane, but if you turn the batteries on and try and get it to come on during your light and pitot heat check, nada.

Here’s the trick, and the checklist doesn’t do a good job of describing this.

• Turn on the Avionics Master
• Turn on the speaker
• Put the flaps to full
• Then move the stall warning vane and you’ll hear the horn

The speaker and the Avionics Master are so you can actually hear the horn (if you had the headset on while you were doing this, the speaker would be unnecessary). The flaps have to be full because the pitch attitude for the critical angle of attack is lower with the flaps down, so the horn goes off when at a different angle. You then don’t have to use as much force to push the vane.

Piper PA46

The early -310P Malibus are pretty simple and straight forward. Move the vane, get the horn.

In the -350P, you can’t get the horn to come on by moving the vane. So, Piper put a stall test button that’s hidden underneath the upper left side of the instrument panel. Push that to test the horn. On the G1000 PA46, it is located directly above the PFD. On the Avidyne, it’s below and to the left of the pilot’s yoke.

Testing the stall warning horn is a very important part of pre-flight. A pilot needs to know if the aircraft is close to a stall. The advent of Angle of Attack indicators in small, GA aircraft, have added a greater awareness to the angle of attack during all phases of flight to avoid those stall spins.

If the stall warning horn goes off or the AOA shows yellow, lower that nose immediately.

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.

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.