Are you a Cirrus pilot with a Garmin Perspective? Still can’t figure out the use of the go around button? Read on!
When it comes to flying an instrument approach, we as pilots are assuming we are going to land. Most of the time, we won’t even take off if the ceilings or visibilities are below the minimums for an approach. 95% of the time, we do land.
There is the other 5% of the time when something unexpected happens, whether we get a full scale deflection, or we don’t see the runway at the published minimums, and we have to perform a missed approach.
When instructing, missed approach procedures are actually what I see the most deficiency in when instructing an instrument rated pilot. It’s not necessarily configuring the airplane for a missed approach procedure, it’s the button pushing involved in setting up the GPS properly. When a pilot isn’t proficient in the button pushing, that button pushing distracts the pilot from actually flying the airplane, which can lead to a dangerous situation.
I am going to spend a few articles on flying a missed approach with different GPS and different autopilot configurations. Today, I will be addressing the Garmin Perspective with a GFC 700 Autopilot, which is what all Cirrus Aircraft after 2009 are equipped with.
The Garmin Perspective Missed Approach Procedure
Once the decision to execute a missed approach has been made, here is the step by step procedure:
Full Mixture and Full Throttle
Simultaneously push the Go Around button on the underside of the throttle. This does the following:
Sets the Garmin Perspective Flight Director to Go Around Mode (7.5 degrees pitch up and wings level)
Takes the Garmin Perspective GPS out of Suspend Mode
Switches the CDI back to GPS mode if it is in a different mode
Garmin Perspective with GFC 700 Autopilot stays on
Flaps up
Confirm airplane is climbing
Set altitude bug for missed approach altitude (assuming it isn’t there already)
Set NAV mode and IAS mode on the Garmin Perspective GFC 700 Autopilot
That’s it. When Garmin and Cirrus got together to create the Garmin Perspective with the GFC 700 Autopilot, they tried to make as simple but robust system as possible. Once you have the procedure down for the right buttons to press, then the procedure is relatively straight forward.
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!
This was found in the grass by the runway at Wings Field
The gear door and strut after the accident.
If you think about the fact that I hit the deer with the wheel, but it didn’t hit the gear door, it becomes apparent just how close the airplane was to clearing the animal completely.
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.
MMOPA will be hosting it’s second Safety Standdown event at many locations across the country for Piper PA46 owners and pilots. The first iteration of MMOPA Safety Standdown in the fall of 2019 was a big hit. Each event was very well attended by MMOPA members.
What is Safety Standdown you ask? Safety Standdown was put together as a mid-year training event as part of the MMOPA Master Aviator program. It’s goal is to allow PA46 owners and pilots to fly in to a location at a reasonable time (the event starts at 10am local time), received some good quality ground training over relevant safety topics by highly experienced PA46 instructors, have a free lunch, then depart mid-afternoon to arrive back home before dark.
The event is free to all attendees. Lunch will be provided at each location. This event is not exclusive to MMOPA members, either. Any PA46 owner or pilot, or just anyone interested in the PA46 world, are invited to attend.
Texas Top Aviation is hosting the South Central Region Spring Safety Standdown at the Henrickson Jet Center at the Austin Executive Airport (KEDC). Hank Gibson and Pedro Vargas-Lebron will be presenting on the following topics:
MMOPA Operational Practices review and importance of stabilized approaches
Crosswind Takeoffs and Landings
High Density Altitude Operations
A discussion of thunderstorms, resources in the cockpit for weather avoidance, and accidents that have occurred involving thunderstorms
The MMOPA Spring Safety Standdown will take place on Saturday, April 18th, 2020. Registration is required for the event. The link for registration can be found here.
Come on out for some high quality training and free BBQ with 50 of your closest PA46 buddies!
It was a rainy Thursday afternoon and I was eating lunch with my family when my phone rang. My wife and I had just been discussing how miserable the weather was, so it was only natural that about 30 minutes later I was soaking wet and sitting in one of our Aerostars getting ready to take off for Ohio. I didn’t have much information about who I would be flying, or why, but I knew that I was going to pick someone up to fly them home; something about a missing airplane. So off I went into the muck. My biggest concern at that point being whether or not my clothes would ever dry out.
I arrived uneventfully and walked happily into the FBO, but found myself quickly in a very different atmosphere. It turned out I had two passengers to pick up, a husband and wife, and they had arrived at the FBO before me. As I walked in the door, the wife received a phone call. The person on the phone told her that search teams had found her father’s airplane crashed in the woods and that he was dead. I learned the rest of the details quickly and it was hard to stomach.
She was travelling home that day to be with family until they were able to locate her father. She was pregnant with her first baby and was in her third trimester. The baby was to be her dad’s first grandchild. He’d owned a Lake Amphibian for years and had stayed at home to work while his wife was out of town. He was last seen leaving work on Tuesday of that week and was reported missing on Thursday by his co-workers. Airport security footage showed him pulling the airplane out and taking off at 20:48 (after sunset) on Tuesday night.
After a few minutes we loaded the Aerostar and took off. It was the saddest flight I’ve ever done. Understandably, my passanger sobbed on and off from the time she got off the phone until we landed a couple of hours later. The weather seemed appropriate as we flew along through the rain and were greeted at our destination by a grief stricken family and a few reporters.
I said a sad goodbye and left, but I couldn’t help but think about their situation. It really hit close to home with me as it was easy to draw parallels between my family and theirs: she was very close in age to me and pregnant with her first child. My wife and I were new parents. Her dad had owned his airplane for about the same length of time that my dad has owned his Bonanza. Additionally, it isn’t uncommon for my parents to go a couple days without being able to reach each other because they both travel.
A Lake 250, the same type of aircraft involved in the accident.
But what happened..?
In the time since the accident, the NTSB has published their findings and unfortunately, it makes the situation sadder. It was completely avoidable.
Airport security cameras showed that after removing the airplane from the hangar, the pilot did not complete a preflight inspection or even a walkaround of any kind. He simply climbed in and left. The investigators were unable to find any traces or odor of fuel in the wreckage, nor any mechanical abnormalities with the airplane. In fact, according to the report, the engine was put on a test stand and ran perfectly. It would seem that the pilot simply never checked the fuel quantity and took off. The airport cameras captured the take off and a bright flash about 30 seconds after the aircraft departed.
Here is an excerpt from the report:
The National Transportation Safety Board determines the probable cause(s) of this accident as follows: The pilot’s attempted 180-degree return to the runway immediately after takeoff in dark night conditions, which resulted in collision with trees and terrain. Also causal was the pilot’s inadequate preflight inspection, which resulted in a takeoff with little-to-no fuel on board the airplane.
Interestingly, the report also details their ability to use logbook information and fuel receipts to show the airplane was taken on a long cross country on its last flight and likely not fueled again.
Another thing which stuck out in my mind upon learning the details of the crash was how important it is to let someone know when you’re going flying. Having another person know roughly when a flight is leaving, where it’s going and and when to expect it back could potentially save the lives of the people on board. In the case of this accident, the pilot didn’t alert anyone that he was going flying and therefore, no one realized he was missing for 2 days.
From reading the NTSB report I don’t get the impression that he survived the crash, but I can’t help thinking about the possibility that he, or others in similar circumstances, could survive a crash and then die from their injuries because no one knew to look for them. When I flew charter, we weren’t legally allowed to take off VFR without letting someone at the company know the details of the flight. I’ve adopted this as my personal policy as well. One text message could be the difference between being rescued or not.
Finally, every pilot should ensure that a proper walk around is completed! It’s easy to assume everything is okay with an airplane, especially one that no one else has access too. In addition to a thorough preflight, I like to walk all the way around the airplane and visual check fuel caps, doors, chocks, ropes, etc., immediately before getting in to ensure that everything is ready. I know a couple of pilots who have taken off with various panels and compartments open simply because they got distracted during their walk around and never closed them. (A good policy is to never walk away and leave something open). Perhaps even more mind boggling is that he apparently didn’t look at the fuel gauges after start up and before take off. I also have to wonder how much fuel he had remaining upon completion of the previous flight.
“Aviation in itself is not inherently dangerous. But to an even greater degree than the sea, it is terribly unforgiving of any carelessness, incapacity or neglect” is likely a familiar quote to just about every pilot. It is often written on a poster with a picture of an old timey bi-plane hanging out of a tree, but I think that it is absolutely on point. Carelessness in the preflight and neglecting basic pilot responsibilities (in this case fuel planning) cost this father his life and his opportunity to meet his first grandchild.
I know this article is a real downer, but it’s supposed to be. Its tragic that accidents take place which are completely avoidable. Obviously this case was beyond the normal realm of carelessness and neglect, but, we as pilots need to be extremely careful not to get so comfortable with an airplane that we stop doing the things which are so basic and important to safety. One of my professors in school used to say “aviation is fun, but it plays for keeps,” which is an effective way to remind myself how important it is to do it right.
*Out of respect to the family, I have not included any specific names, tail numbers or airports in this article.
You are at cruising altitude and your flight is going just as planned. All of that can change, sometimes without much warning, and you, the non-pilot, are now in charge. Would you know what to do?
This was a scary thought for me until I attended a seminar developed for the non-flyer at a Cirrus Owners Pilot Association (COPA) fly-in. Cirrus is the only small plane with a parachute as standard, so I thought all I had to do in an emergency was pull the chute. It’s a little more complicated than that!
I learned the vast majority of pilot incapacitation happens when the plane is at cruising altitude, so there is time to find a solution.
I was taught ten basic steps to follow to bring the plane safely to the ground.
First attempt to revive the pilot. If he is choking, it is possible to do a Heimlich maneuver from the side. This may dislodge whatever is blocking his airway and solve the problem. If he is experiencing hypoxia, turn off the heat, open all vents, and, if you have on board oxygen, use it. Also, if you can, get instructions on how to descend to a lower altitude. If the pilot is unconscious due to a heart attack or other medical emergency, there are still things you can do from the right seat.
Engage the autopilot if it isn’t already on and move the pilot off the controls. *
Ensure you are connected to the radio. If you hear ATC or other pilots, you are.
Send an electronic trouble message. Set the transponder to 7-7-0-0 to identify your plane to ATC. This will cause your plane to be highlighted on ATC radar screens.
ATC will most likely contact you asking what is your emergency. If this does not happen, you will need to transmit a Mayday call. All non-pilot passengers should know how to use the radio to get help, if they know nothing else.
With help from ATC, decide where you want to go.
Use the autopilot to fly in the direction suggested by ATC. I was taught that ultimately the choice of where to deploy the parachute is up to me because I am now the PIC, pilot in command.
Ensure that seat belts are secure and the emergency hammer is between your legs (so you have it to break a window to escape if needed).
Pull the parachute handle.
On the way down, shut down the engine and brace for impact.
After landing, move away from the plane, into the wind. Stay nearby and wait for help.
The seminar covered specific procedures to accomplish these basic steps, what to do if you don’t get a response from ATC, what to say in a Mayday transmission, how to fly a heading, how to check fuel levels, shut down the engine, etc. After the seminar, I felt much more comfortable about what to do if my pilot suddenly lost consciousness.
I was also told to practice what I had learned to avoid panicking in an emergency situation. There are so many things the person in the right seat can do under normal circumstances to practice. Learn how to set heading bugs, learn where the plane’s Electronic Locator Transmitter (ELT) is located and how to activate it. This will help rescuers locate the airplane. Learn how to assess your fuel levels. Practice making routine radio transmissions. Observe what your pilot does and ask questions if you don’t understand something.
Knowing what to do in an emergency situation will give you a sense of control over what will happen to you, your pilot, and any passengers on board your plane. If you have never considered taking a lesson or two for the non-pilot, find yourself an instructor, and learn what you need to know for your plane. Hopefully you will never have to use it, but if you do, you will be ready to be the PIC who lands the plane.
Anne and her husband Stephen are the proud owners of a Cirrus SR20. They plan to put the airplane to better use once Stephen retires. Anne has a background in desktop publishing and writing.
Drones; these technological wonders have, seemingly, come out of nowhere over the course of a few years. Although they bring with them the promise of convenience and fun, they have also brought problems and uncertainty for the government, general public, and, specifically, the aviation community. But, where did drones come from and are they really something to be worried about? Let’s take a look at Unmanned Aerial Systems (UAS) and hopefully put to bed some of the concerns which seem to be following them around.
It shouldn’t come as a surprise to anyone when I say that drones have recently become overwhelmingly popular. The military, businesses, and hobbyists are increasingly utilizing them for all kinds of purposes, which range from enemy surveillance to package delivery. Drone pilots are in high demand and several aviation universities are even offering majors designed to produce graduates which specialize in UAVs (Unmanned Aerial Vehicles).
Drones are relatively new to the landscape of unmanned flying machines. Although model airplanes have been popular since the dawn of aviation, the first “drones” didn’t start becoming commercially available until a few years ago. As electronic technology advanced, so did model aviation. Models became more and more sophisticated and could be flown remotely as long as they remained within sight of the person flying it.
It wasn’t until about 3 or 4 years ago that the technology became available to develop drones. This is due to the need for very small and light electric motors, batteries, and stabilization systems. Once these started to become popular, it didn’t take long for drones to become bigger, cheaper, and completely automated.
It is important to note that there is a difference between drones and conventional model airplanes and helicopters. Drones are defined most simply as an unmanned vehicle which can be operated without user input from the ground. Conventional model aircraft can take all shapes and sizes, but must be operated within line of sight from the operator; as they have no ability to fly, takeoff, land, or navigate without input via a radio transmitter. So, if you happen to see a model aircraft flying, don’t assume automatically that it is a drone. Most of the time, model airplanes, helicopters and even drones are being flown safely and legally.
Generally, a drone is designed with several arms which come off of a central body. Each of the “arms” typically has a motor with a rotor mounted on it to provide lift while the main body is home to the radio equipment, landing skids and camera gear. If you see a model flying that looks like a conventional airplane or helicopter, odds are it isn’t a drone. Most likely it is being flown recreationally by someone nearby.
Historically, model airplanes and helicopters have been difficult to learn to fly. Before the times of pre-built foam airplanes and ready to fly drones, a modeler had to build their flying machine and find someone to teach them how to fly it. (Otherwise, they would likely only get one short flight). New modelers would be directed toward the local model flying club and would get plugged in with a group of established fliers who could outline the rules for model aircraft as well as get them up in the air safely.
This is a classic example of a Drone. You can see the long arms which house the motor units and rotors as well as the camera and skids mounted in the center. I got this picture (this model is called a Chroma) off of HorizonHobby.com
This is one of my models, a Revolver 70. It wouldn’t be considered a drone as it cannot fly without a pilot on the ground (within eye sight) controlling it. You can see the structure of the revolver and the helicopter pictured below varies greatly from that of the Chroma drone.
This is a Blade 400 helicopter. Just like the Revolver, it requires a pilot to be present nearby and would not be considered a drone. Worth mentioning is that neither the Blade nor the Revolver have any cameras mounted anywhere on them, as their sole purpose is to be flown for fun. Picture from BladeHelis.com
However, because most everything is purchased online in today’s market, drones are bought and flown by enthusiasts who have not been taught the rules, safety protocols, and procedures necessary to safely operate their new kits. In addition, the drones incredible stability and ability to be flown without any skill means that anyone with great enough funds and an equally great lack of common sense can buy a model and program it to fly over any location they choose. Unfortunately, sometimes that includes places which cause problems.
Andrew Robinson is a 135 Charter Pilot and flight instructor who lives with his wife and 2 daughters in Pennsylvania. He flies Pilatus PC-12s and instructs in Beechcraft Bonanzas.
Texas Top Aviation is proud to announce that we now offer Piper PA46 Training in the Malibu and Mirage. Our Piper PA46 training is provided with the same excellent & professional approach that has become our hallmark.
The four-day format of this course allows time to answer all of your questions about your new airplane. The Texas Top Aviation Piper PA46 training course leaves you with a confidence and understanding that will help you enjoy your Malibu or Mirage even more.
New avionics have you scratching your head in confusion? No problem. Texas Top Aviation is well versed in the latest Garmin and glass panel instrumentation.
If you are in need of recurrent training in your PA-46, Texas Top Aviation would be proud to help with that as well. Consider us your one stop shop for Piper PA-46 training.
For more information, check out our Piper Malibu/Mirage Training page.