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.
I love Lightspeed headsets. They are very comfortable, durable, and reasonably priced. Plus, when you call Customer Service, you are actually talking to someone who works for the company and knows what they are talking about.
One thing to watch out for with Lightspeed headsets is the Mono vs. Stereo option. On the Zulu 3, there is a very small control panel underneath the battery compartment to change from Mono to Stereo. If you have any kind of modern audio panel, you will definitely want to do this. Here’s why.
I was flying in a Cirrus SR22 G5 last fall with a Garmin 350 Audio Panel. Everything worked fine talking to the ground and tower controllers. Once I took off and was switched to approach, everything went quiet. I could hear the approach controller, but couldn’t transmit. I thought my headset had bit the dust. There was another set in the plane that I switched to, but I thought the transmit function of mine was out.
I sent the headset back to Lightspeed for repair. The headset was still under their 5 year warranty, which is really nice! I got it back a few days later, plugged it in to another Cirrus, and still had nothing. I was getting frustrated, but then a light went on. One of my colleagues had mentioned something about mono and stereo in the Lightspeed. I popped the batteries out, flipped the switch over to stereo, and wa-la! Everything was fully operational.
If you get Lightspeed headsets, you’ll want to make sure it is set on Stereo, as they all come from the factory on Mono. If you get a PFX, there is an easy access button on the side of the battery unit to switch from Mono to Stereo.
Are you still trying to master the Garmin 430 in your airplane? Is it giving you fits because you keep twisting the big knob instead of the small knob? Would you like a step-by-step guide to each and every part of the Garmin 430?
Pilot proficiency website PilotWorkshops.com has published a very thorough, step-by-step manual on how to use the Garmin 430. Want to load a flight plan? There’s a section for that. Want to load an approach? There is a section for that as well.
The Pilot-friendly Garmin 430 manual is a great reference to have for Garmin pilots. Pilot Workshops offers a guide for the Garmin 430 and the Garmin 430W, depending on if you have WAAS or not.
The hard copy guides are $44.95, but you can also download the PDF version of each for $19.95.
To get more information on the guide or to order one, you can visit the Pilot Workshops website. (Have another Garmin or King GPS unit? Pilot Workshops has guides for a variety of different GPS units)
A Piper PA46 partnership is being formed in the San Antonio area. Two to three partners are being sought to purchase either a Piper PA46-310P Malibu or a ’90s model Piper PA46-350P Mirage.
The Piper PA46 Malibu is the original Piper PA46 airframe. It is equipped with a Continental TSIO 520, 310HP engine (though many have been upgraded to the Continental TSIO 550C engine, which is a great upgrade), is complex, and pressurized (the best feature about the airplane!). The six seat airframe travels around 185-190 KTAS at FL200 on 16-17 GPH, giving an incredible range with 120 gallons of fuel.
The Piper Mirage is what Piper designated the PA46 when it switch to the Lycoming TIO 540 350HP engine in 1989. The airframe remained the same, but the engine eeks out a few more KTAS at 22-25 GPH depending on how high the cruise altitude is.
Both the Piper Malibu and the ’90s model Mirage are equipped with the KFC 150 autopilot. A lot of the Piper PA46 airframes still have a Garmin 530W/430W or dual 430Ws, but a large number have been upgraded to the Garmin GTN 750/650, while a few have opted for the Avidyne IFD 540/440 GPS units. There are a fair number still with steam gauges, while some have upgraded to Aspen units or the Garmin G500 or G500TXi.
If you are located in the San Antonio area and interested in a 3-4 way partnership on a Piper PA46, please Contact Us. The purchase price will be between $300,000-$450,000, so only interested parties that can afford a budget of $100,000-$150,000 please.
The plane will be based at Stinson Field (KSSF) or New Braunfels (KBAZ).
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.
Thunderstorms are not to be taken lightly. I know you have probably heard that many times in your flying career. Weather related accidents account for approximately 25% of airline and GA accidents.
The Airman’s Information Manual suggests giving a 20 mile berth around thunderstorms. If you are an experienced aviator or a newbie please take this piece of advice seriously. At one flight school where I taught, we had the policy of maintaining a 25 mile buffer around isolated thunderstorms. A bit excessive you think? Maybe, but safety is a good thing!
On this particular day, I was operating a Bell Jet Ranger helicopter during a power line patrol. Power line patrol by itself offers numerous challenges. The job consists of flying along electric power transmission lines at approximately 40 feet above the ground at 40 knots. The crew consisted of me (the pilot) and an observer. The observer is an employee of the power company and it is his job to determine which line(s) will be patrolled during the given day. As I fly along the lines, the observer is checking for anything out of the ordinary such as broken, cracked, or even shot out insulators, excessively large bird nests at the top of structures, or woodpecker holes in wooden poles. The observer knows the lines and he is also a great help in letting me know there is a crossing, and potentially higher, line in our flight path. That makes him a true safety asset! It was late afternoon during the summer and we were about to finish up for the day. We only had about another 10 miles of line to follow before calling it a day. Up ahead, I noticed an isolated thunderstorm near our power line. I could see the heavy rain falling below the anvil shaped leading clouds. It appeared to be well beyond the end of our day’s work so we pressed on.
As we drew closer to the thunderstorm, we were suddenly tossed up on our left side like a dog toy in mid-flight! It seemed like we were 90 degrees to our normal cruise attitude and, to make it worse, we had the doors off on that hot summer day. I was able to recover and we did an immediate about face and high tailed it home. Forget the rest of that line, tomorrow is another day.
The destructive force of thunderstorms cannot be overstated. In addition to extremely heavy rain, they can contain strong wind shear, large hail, and severe turbulence, each of which can damage or destroy an aircraft. Take care when one of these bad boys is near your flight path. Give it plenty of respect and a lots of room, for safety’s sake.
Alan VanDoren is a 7000 hour ATP pilot. He has flown both fixed wing and helicopters as a police pilot, missionary pilot, flight instructor, and most recently as an EMS pilot. He has flown in five countries around the world and also teaches university level aviation courses in his spare time.
Cirrus CAPS pull #55 took place at the beginning of November over Fayatteville, AR. From initial reports, it appears a clamp broke on the oil cooler, causing a loss of oil pressure. It does not appear that the engine immediately quit, but an annunciator alerted the pilot that the engine was losing oil pressure. At this point, it appears the pilot elected to do an emergency descent to an airport below him, but ended up not timing it right, missing the airport and pulling the parachute.
As an experienced Cirrus flight instructor, there appears to be some suspect decision making in handling this operation. I teach in a Cirrus that if an oil light comes on, given that a pilot has some altitude to work with, it is a better option to physically shut the engine down, leaving control of the situation in the pilot’s hands. This way, the pilot knows when the engine is stopping and is prepared for it, instead of the engine acting erratically and causing problems on the descent.
After checking the engine gauges and shutting the engine down, a pilot should establish best glide first, not nose down and descend at a high rate trying to make an airport. Best glide gives the pilot many more options and a lot more altitude to work with, further allowing him/her to plan how to make an airport directly underneath the airplane.
To pontificate, it seems that if the pilot had adjusted the plane to best glide, instead of performing an emergency descent, there is the possibility that Drake Field would have been reachable, the chute would not have been needed, and the driver of the truck would not have had to visit the hospital. Hindsight is 20-20, but this may be an overall training and decision making issue that may need further emphasis.
The initial NTSB report as well as a link to the CBS story is below.
NTSB Identification: CEN16LA026
14 CFR Part 91: General Aviation
Accident occurred Tuesday, November 03, 2015 in Fayetteville, AR
Aircraft: CIRRUS DESIGN CORP SR22T, registration: N857SW
Injuries: 3 Minor, 1 Uninjured.
This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.
On November 3, 2015, at 0950 central standard time, a Cirrus SR22T airplane, N857SW, descended under the canopy of the cirrus airframe parachute system (CAPS) and landed on a road in Fayetteville, Arkansas. The pilot, pilot rated passenger and one person on the ground received minor injuries. One passenger in the back right seat was uninjured. The airplane was substantially damaged. The airplane was registered to WG Aviation LLC, Rogers, Arkansas, and operated by a private individual under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed at the time of the accident and an instrument flight rules (IFR) flight plan was filed. The flight departed from the Bentonville Municipal Airport (VBT), Bentonville, Arkansas, at 0934 and was en route to the Waco Regional Airport (ACT), Waco, Texas.
According to the pilot, after departure from ACT he leveled off around 10,000 ft mean sea level (MSL) and was in “VFR on top” conditions. The pilot noticed that the crew alerting system (CAS) flashed a yellow caution light for oil pressure; the engine was still producing power. The pilot notified air traffic control (ATC) of the issue and received vectors to the nearest airport, Drake Field Airport (FYV), Fayetteville, Arkansas. The pilot descended and maneuvered toward FYV as the CAS indicated a red warning light for oil pressure, which had dropped below 10 psi. The engine was producing inconsistent power as the airplane descended to 3,300 ft and FYV was still not in sight due to cloud coverage. The pilot was unable to maintain altitude and the airplane’s stall warning horned sounded. The pilot deployed the Cirrus airframe parachute system (CAPS) and descended to the ground. During the landing the airplane collided with a truck and then came to rest on a four lane road.
At 0953, the weather observation at FYV reported wind from 190 at 9 knots, gusting to 17 knots, 10 miles visibility, clear sky, temperature 61° F, dew point 57° F, and altimeter setting 30.11 inches of mercury.
An initial postaccident examination was conducted on November 4, 2015, in Fayetteville. Engine oil was observed on the underside of the fuselage. The oil cooler cross fitting was broken and oil was observed in the engine compartment.
The airplane’s recoverable data module and three data cards were removed and sent to the NTSB Vehicle Recorders Laboratory for download.
The airplane has been retained for further examination.
