The Importance of Slowing Down

Technology has made our job as pilots simpler, streamlined, and safer.  With all the new GPS & autopilot technology that seems to come out every month, flying an airplane is getting easier every day (and when I say flying, I mean programming!).  I can’t tell you the last time I actually used a VOR for navigation, other than a practice approach.  The AIM even has guidance in it now allowing pilots to use the GPS overlay on a VOR or LOC approach instead of switching to the actual NavAid on the course needle (you have to WAAS in order to legally do this).

I hear the argument already.  I am young (31) and used to all the different touchscreens because I have grown up with them.  Tech is nothing new to me.  It’s not that easy for everyone, I do understand.  There is also the argument that all the tech causes pilots to not know how to fly the airplane, which is also valid. This is why I put an emphasis on hand flying in any kind of training I do.

For the sake of argument in this article, yes, I am young and I adapt to technology pretty easily.  I’m not afraid to press buttons to figure out what they do, but I usually do it while sitting on the ground with a GPU hooked up (or I go look in the manual).  And yes, all the autopilot ability has caused a decrease in base pilot skills.  I actually encourage every customer I have to go get a tailwheel rating so that they can actually learn how to fly better.  You don’t use a rudder much in a Cirrus compared to a Super Cub or a Citabria.

What I want to focus on for a few minutes is how to alleviate the frustration that comes with getting so wrapped up in the technology when it doesn’t do something that you want it to, or the wrong button gets pressed, then you end up somewhere you had no intention of being.

The biggest thing a pilot can do when it comes to technology is NEVER to get in a hurry.  Good training is first and foremost, but, after that when flying without an instructor or even in recurrent training, SLOW DOWN and think through what you are doing and what you want the system to do.  This will alleviate a ton of frustration.

It can be very easy in hot, turbulent weather to get tuned in to the GPS programming, trying to do five or six different things in the span of five or six seconds, before looking up and realizing that plane is 500 feet off altitude (without an autopilot) or you blew through the course you were supposed to be intercepting (with an autopilot).

What I teach is to slow down, whether or not you have an autopilot, and do one thing at a time.  Once that item is done, look up at the instruments or the horizon, check on things, make sure the airplane is still flying properly, then do the next thing.  Don’t try and do a bunch of things all at once or in a hurry.  It will usually get you off course and off altitude, plus it distracts the pilot from his main job:  Flying the airplane.

So, next time you want to do something on your GPS, pause, take a breath, think through what you want to do, then do one item at a time.  The outcome will be less frustrating and you’ll keep flying where you want to go.

Similar Posts

  • The RDD LX7

    Have a Lancair IV-P?

    Want to make it better than a Cirrus or a Cessna TTx?

    Meet the team at RDD creating the LX7.  Just make sure you are sitting down as you are about to be blown away.

    RDD (Research. Design. Development) is a professional building company for the Lancair line of experimental aircraft (Lancair unveiled the Mako at Osh Kosh this summer, which performs slightly less than the advertised values of the LX7, but is available as a new kit).  For those unfamiliar with the experimental world, when an experimental kit is bought, the owner/builder can build the entire aircraft himself, partially build it then send it to a completion center, or have a professional build company put it together.  This last option is what RDD did with Lancair aircraft before Lancair moved from Oregon to Uvalde, TX.

    Once Lancair was sold, RDD started thinking on how to make the IV-P better.  Boy, did they.  What resulted is the LX7.

    The LX7 is a retractable gear, single engine piston, pressurized aircraft that sits 4.  See it on the ramp and it looks like a Lancair or a Columbia.  Sit in the cockpit and you’ll know something is different.

    Starting with the power plant, RDD put a Continental TSIO 550-E engine in the IV-P airframe, giving the airplane 350 HP.  They redesigned the wing to hold 180 gallons of usable fuel and a much better stalling envelope (anyone who has looked at a Lancair IV or IV-P wing knows that there isn’t much wiggle room with angle of attack on those airplanes), lowering the stall speed to 62 knots dirty.

    The cabin is roomier and the panel is beautiful.  Equipped with 2 or 3 Garmin G3X Touch panels (the experimental equivalent of the G2000), plus a GTN 750 and a fully digital backup flight instrument from Grand Rapids, plus ESP technology built in to the autopilot, this plane seems like a pilot’s dream.

    I haven’t even gotten to the best part:  the speed.  Being pressurized, the LX7 has a 25,000 foot service ceiling where it can achieve cruise speeds of 260 knots at best power (24 GPH) and 250 knots at best economy (18 GPH).

    Yes, I did just say 250 knots at 18 GPH in a single engine piston.

    With 180 gallons of fuel.

    Make sure you bring a Travel John.

    Worried about an experimental?  The airframe is equipped with a full BRS system similar to the Cirrus SR22, keeping everyone safe and sound.

    There is one flying LX7 currently and RDD is working on 3 more.  The price tag for the full conversion is $550,000.  The kicker is, the owner has to provide the Lancair IV-P airframe.  There are currently 10 Lancair IV-Ps for sale on Controller, varying in price from $200,000-$400,000, bringing the total price of the project to $750,000-$950,000.  Owners who already have a IV-P or a IV-P kit can send it on over to RDD to get started on their project.

    Have a Lancair IV-P? Want to make it better than a Cirrus or a Cessna TTx? Meet the team at RDD creating the LX7.  Just make sure you are sitting down as you are about to be blown away. RDD (Research. Design. Development) is a professional building company for the Lancair line of experimental aircraft…

  • Checking The Stall Warning Horn

    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.

    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,…

  • Registration Now Open for the 2025 Texas Top Aviation Fly-In!

    Are you ready to take part in one of the most exciting Texas aviation events of the year? Registration is now open for the 2025 Texas Top Aviation Fly-In, happening March 26th-28th, 2025, at the stunning Lajitas Golf Resort in Lajitas, Texas.

    Whether you’re a pilot looking for a getaway, wanting to make new pilot buddies, or just seeking a one-of-a-kind adventure, the 2025 Texas Top Aviation Fly-In promises an unparalleled blend of community, aviation instruction, and scenic Big Bend recreation. Not to mention, great golf!

    Why You Should Register

    As one of the top 2025 Texas aviation events, this Fly-In features:

    • Two rounds of golf at the #1-ranked Black Jack’s Crossing Golf Course
    • Aviation seminars from industry leaders
    • Making new friends and seeing old ones at our group dinners
    • Non-golfing activities, like Jeep rentals, exploring Big Bend, or relaxing at the Resort spa

    Spaces are limited, so secure your spot now for our 6th Annual Fly-In!

    Event Highlights

    Fly-In Golf Tournament

    Enjoy two rounds of golf at Black Jack’s Crossing Golf Course:

    • Round 1: March 26th, 2025, 1:30 PM
    • Round 2: March 27th, 2025, 1:30 PM

    Aviation Seminars

    Learn from top experts on Thursday morning, March 27th, 2025:

    • Paul New: Cirrus and Cessna mechanic
    • Scott Williams: Aviation attorney
    • Travis Ulhorn: San Antonio Air Traffic Controller

    Community and Connection

    Relax and connect at evening group dinners starting at 7:30 PM.

    Pricing

    • $1,475 per person (2 nights + golf) + tax
    • $1,100 per person (2 nights, no golf) + tax
    • $475 for non-golfing spouse + tax

    Registration includes lodging and golf; food and beverages will be billed directly to the attendee.

    Key Details

    • Golfers: Arrive by noon, March 26th, 2025
    • Non-Golfers: Arrive by dinner on March 26th
    • Complimentary shuttles provided from Lajitas International Airport (T89)

    Register Today

    Don’t miss out on one of the best Texas aviation events of the year. Register now and be part of the 2025 Texas Top Aviation Fly-In. Spaces are limited, so don’t wait!

    Are you ready to take part in one of the most exciting Texas aviation events of the year? Registration is now open for the 2025 Texas Top Aviation Fly-In, happening March 26th-28th, 2025, at the stunning Lajitas Golf Resort in Lajitas, Texas. Whether you’re a pilot looking for a getaway, wanting to make new pilot…

  • Oh, Deer (Part 2)

    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!).

    On final approach for runway 26 with the gear up and the props feathered.
    Photo Credit: www.lancasteronline.com

    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.

    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…

  • Cirrus Electrical System Health

    As all Cirrus pilots know, SR20s and SR22s have 2 batteries in the Cirrus electrical system (technically, they have 3, as Battery 2 is made up of 2 12 volt batteries in series with each other).  Battery 1 provides power to the starter and is a backup for the entire Cirrus electrical system, while Battery 2 provides backup for the Essential Bus items.

    Cirrus Engine Page

    If you look on the engine page of either an Avidyne or a Garmin Cirrus, there is a section showing the Cirrus electrical system health.  With the engine running, you have voltmeters showing the voltage from Alternator 1 and Alternator 2, ammeters showing the amperage output from Alt 1 and Alt 2, and an ammeter showing the charging rate of Battery 1.  There is no indication for Battery 2.

    This brings up a question.  How does the pilot know that Battery 2 has any kind of a charge?  What happens if the whole Cirrus electrical system goes caput and all that’s left is Battery 2?  Will Battery 2 have juice then?

    The answer is actually rather simple.  As part of the pre-flight inspection, the first step in the cabin inspection is to turn the Battery 2 switch on, then check the Essential bus volt meter.  The checklist says the voltmeter should be reading between 23-25 volts.  This tells you how much voltage Battery 2 currently has. The next step (after ensuring the flap lights are out) is the turn Battery 1 on.  Battery 1 then powers the Main Bus and Essential Bus.  The voltage showing on the Main Bus shows how much voltage Battery 1 currently has.

    Easy enough right?  Now you can impress friends and family alike with your Cirrus electrical knowledge!

    As all Cirrus pilots know, SR20s and SR22s have 2 batteries in the Cirrus electrical system (technically, they have 3, as Battery 2 is made up of 2 12 volt batteries in series with each other).  Battery 1 provides power to the starter and is a backup for the entire Cirrus electrical system, while Battery…

  • Contact Approaches

    Almost all IFR pilots are familiar with visual approaches and what the requirements are in order to fly a visual approach. As a refresher, the Instrument Procedures Handbook defines a Visual Approach as “an ATC authorization for an aircraft on an IFR flight plan to proceed visually to the airport of intended landing; it is not an [Instrument Approach Procedure]” (page 4-56).

    For ATC to issue a Visual Approach, the pilot must have the airport or the traffic to follow in sight. Once the pilot reports the airport or the traffic in sight, ATC can clear the aircraft for a visual approach.

    A limiting factor for a visual approach is ATC’s Minimum Vectoring Altitude. “This altitude, based on terrain and obstruction clearance, provides controllers with minimum altitudes to vector aircraft in and around a particular location” (Instrument Procedures Handbook page 1-42). ATC has to restrict aircraft to these MVAs, which can sometimes be quite high due to terrain or obstacles in the vicinity of the airport.

    Every pilot has been in a situation with a high MVA that ATC can’t get them below, but it’s solidly MVFR or VFR at the destination airport. The MVA keeps the pilot in the clouds, so a visual approach isn’t possible since the pilot can’t see the airport or the traffic to follow. This can lead to extra time to go out and fly an approach.

    Enter a Contact Approach. A Contact Approach is different then a Visual Approach. “The main differences between a visual approach and a contact approach are: a pilot must request a contact approach, while a visual approach may be assigned by ATC or requested by the pilot; and a contact approach may be approved with 1sm visibility if the flight can remain clear of clouds, while a visual approach requires the pilot to have the airport in sight, or a preceding aircraft to be followed, and the ceiling must be at least 1,000 feet AGL with at least 3sm visibility” [Instrument Procedures Handbook page 4-57].

    Here’s the simplified explanation: A pilot does not have to have the airport in sight to request a contact approach. All that is required is for the airport to be reporting at least 1sm visibility and for the pilot to remain clear of clouds.

    When would this be helpful for an IFR pilot? Good question. Here’s a scenario.

    Pilot Smalls is about 20 minutes from his destination, which is an uncontrolled airport with only one approach to runway 17. He is approaching from the south and the initial approach fix for the approach to 17 is about 15 miles north of the airport. The airport is under Center control. When he has arrived at this destination in the past, Center usually could only vector him down to 4,000 AGL. He is very familiar with this airport and the surrounding area as he comes to this destination at least 2-3 times a month for business.

    Pilot Smalls listens to the AWOS, which is reporting a 2500 foot scattered layer and 10 miles visibility. He knows it is right traffic for 17 since there is a 2,000 foot antenna on the east side of the field. There is some hilly terrain around, but all the terrain is well below pattern altitude and doesn’t cause a safety issue.

    Looking out at the clouds, Pilot Smalls observes that the cloud layer is scattered to broken, but more scattered on the west side of the airport, with several large openings that he can see the ground through. Center asks for his approach request and Pilot Smalls requests a visual approach. Center gives him a descent to 4,000 AGL, their MVA for the area. They tell him to report the airport in sight for the visual approach.

    At 4,000 AGL, Pilot Smalls is going through the scattered layer of clouds, but can see the ground in between the clouds and deems he has room to maneuver safely between the clouds and stay clear of them. He can’t see the airport, so a visual approach seems unlikely. He can’t cancel IFR because then he would have to keep the VFR cloud clearance and visibility requirements in Class E airspace (1,000 feet above, 500 below and 2sm horizontally), which isn’t possible in this case.

    5 miles from the airport, ATC states, “N12345, I’m going to have to send you out for the approach since you don’t have the airport in sight.” Pilot Smalls then requests a Contact Approach. ATC clears him for the Contact Approach to his destination, so Pilot Smalls descends through a break in the clouds, remaining clear of clouds, until he gets below the base of the ceiling. He maneuvers onto the right downwind, lands and cancels IFR.

    Contact approaches can be useful at controlled and uncontrolled airports. The first time you request one, do so with a higher ceiling and some room to maneuver to keep your safety margins. After you’ve done a few, you can determine what your personal minimums are for a Contact Approach.

    I would not recommend doing a Contact Approach at an airport you are unfamiliar with. It’s vital to know what obstacles are around since on a Contact Approach, the pilot is now responsible for traffic avoidance and terrain avoidance, whereas on a visual approach, ATC resumes that responsibility.

    For more reading on Contact Approaches and another good scenario, check out Bold Method’s article on Contact Approaches.

    Almost all IFR pilots are familiar with visual approaches and what the requirements are in order to fly a visual approach. As a refresher, the Instrument Procedures Handbook defines a Visual Approach as “an ATC authorization for an aircraft on an IFR flight plan to proceed visually to the airport of intended landing; it is…

Leave a Reply

Your email address will not be published. Required fields are marked *