A common practice when ATC is setting an aircraft up for a visual approach is giving a clearance direct to the Final Approach Fix (FAF) for the approach for that runway. The theory is, the pilot will fly to the FAF, then he’ll pick up the airport and fly visually in. It is a handy way of setting the pilot up for a 5 mile straight in visual approach.
For anyone who flies with a Garmin GPS, whether is be a 430, a G1000, or a GTN 750, you have probably discovered a little nuance with going direct to the FAF. Once an approach is loaded into the flight plan, whether is is loaded via vectors or via an IAF, all the waypoints on the approach go into the flight plan. If the FAF is selected in the flight plan and the direct to command is given, the plane turns to the FAF and flies direct to it.
The fun starts once the plane gets to the FAF. The Garmin doesn’t sequence to the next waypoint. It just keeps the FAF as the active waypoint and the airplane just continues on the course it had to get to the FAF. This has probably caused some stress and frustration as the pilot is expecting the airplane to turn inbound (if the autopilot is engaged), but then it keeps flying, usually away from the runway.
How to fix this? If a Garmin GPS is closely inspected once the direct to the FAF command is selected, the pilot will notice that the GPS goes into Suspend mode. The Garmin programers thought this was a good idea to do.
How to get it to sequence properly? Well, once the FAF is the active waypoint and the airplane is flying direct to it, simply unsuspend the GPS, then the airplane will turn inbound on the final approach course and track inbound and the glide slope will pop up. On the 430 or 530, just press the OBS key. On the G1000, press SUSP. On the GTN 750, tap UNSUSP on the bottom of the unit.
Hopefully, this will lead to reduced frustration on what otherwise should be a simple approach to an airport.
Looking for somewhere to take a trip this fall? Sedona, Arizona should warrant strong consideration. Just shy of 100 miles north of Phoenix, Sedona is one of the most beautiful areas in the southwest United States. From Texas, depending on how fast your airplane travels, you could make it to Sedona in a day, with a couple of stops in between. You’d definitely want to spend a few days to enjoy the scenery and maybe jump over to the Grand Canyon while you’re in the area.
The Airport
As you approach the Sedona Airport (KSEZ), you become somewhat distracted by the scenery around you. Don’t be too distracted as the approach is a little tricky. If you are landing north, on Runway 3, the calm wind runway, don’t let the surroundings fool you. Stay on that PAPI and don’t be short, as the runway is on a 500 foot mesa. In instrument conditions, the MDA for the RNAV approach to Runway 3 dumps you out about 1,300 feet above the airport elevation, giving you plenty of time to set up to land.
When using runway 21, don’t make your pattern too wide as there are some pretty tall rocks (around 7,000 feet) north of the field. The Airport/Facilities Directory gives a warning to pilots in strong southwesterly wind conditions. Be aware of strong downdrafts coming in on final for runway 21.
The runway itself is in excellent condition, and plenty long at just over 5,000 feet. The FBO is a little dated, but the folks there are great. They were redoing the ramp this summer, so beware of that. Airplane parking is no problem, but actually getting to the FBO is a little tricky. The Mesa Grill is a very nice good restaurant just a short walk from the FBO. When I was there, I chowed down on a buffalo burger. It definitely hit the spot.
What To Do
Sedona is the outdoorsman’s paradise. Starting off, to get a great overview of the area, hop on the Red Rock Scenic Byway (SR 179) about an hour before dusk. You’ll get to see some spectacular views while it’s still light, then you can’t beat the sunsets in Sedona.
For hiking, you have a myriad of options, from the Cathedral Rock, to the Oak Creek Canyon, to the Devil’s Bridge Trail, all are beautiful, though most are not for the faint of heart (especially the Devil’s Bridge). Even though the fall is cooler, make sure you pack plenty of water for the hikes.
Want something to do in the evening? Go up to the Chapel of the Holy Cross to watch the sunset. After the sun goes down, go do some stargazing. You’ll get to take a tour of the stars at the Sedona Star Gazing location in Oak Creek. You are shown all the constellations and stars by professional astronomers, and blankets and chairs are provided.
Art connoisseur? You’ll find plenty of art galleries around town with a ton of beautiful, original artwork. There are also several theaters and golf courses around Sedona, giving everyone a little bit of everything.
If you’re up for it, the Grand Canyon is about a 2 hour drive north of Sedona, or a quick flight up to the Grand Canyon Airport (KGCN).
In search of a good getaway? Try Sedona. You’ll be sore from lots of hiking and sight seeing, but it will definitely have been worth it.
Looking for somewhere to take a trip this fall? Sedona, Arizona should warrant strong consideration. Just shy of 100 miles north of Phoenix, Sedona is one of the most beautiful areas in the southwest United States. From Texas, depending on how fast your airplane travels, you could make it to Sedona in a day, with…
Earlier this month, Eclipse Aerospace and Kestrel Aircraft merged to form ONE Aviation. Most pilots are familiar with Eclipse, who makes the Eclipse 550 jet, but not many have heard of Kestrel Aircraft.
Kestrel Aircraft is run by Alan Klapmeier, co-founder of Cirrus Aircraft and brother to Dale Klapmeier, who still runs Cirrus. Klapmeier joined Kestrel in 2010 and brought innovation to the K350 Turboprop design that Kestrel was developing. Kestrel has been lacking in investors to further their project, but the merger will help a lot in getting more funding. Klapmeier assumed the CEO role for ONE Aviation.
The merger will also help bring more innovations to the Eclipse 550. The original Eclipse Jet was a miserable failure and the company went into bankruptcy in 2009. The Eclipse Jet came back to market in 2013 as the Eclipse 550 with many much needed improvements, including making GPS a standard amenity.
Klapmeier and his genius will lead ONE Aviation in good directions. The K350 will come to market a lot sooner as more investors will be drawn to the company, while the Eclipse 550 will continue to see new and innovative developments.
Earlier this month, Eclipse Aerospace and Kestrel Aircraft merged to form ONE Aviation. Most pilots are familiar with Eclipse, who makes the Eclipse 550 jet, but not many have heard of Kestrel Aircraft. Kestrel Aircraft is run by Alan Klapmeier, co-founder of Cirrus Aircraft and brother to Dale Klapmeier, who still runs Cirrus. Klapmeier joined…
In July, a Cirrus SR22 suffered an engine failure in Houston after departing KIAH. The CAPS system was deployed and the airplane came to rest in a neighborhood on the north side of Houston. This makes CAPS save number 53 for Cirrus and no fatalities. The initial NTSB report is below.
14 CFR Part 91: General Aviation
Accident occurred Tuesday, July 07, 2015 in Houston, TX
Aircraft: CIRRUS DESIGN CORP SR22, registration: N422PB
Injuries: 2 Minor.
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 July 7, 2015, about 1137 central daylight time, a Cirrus SR-22 single-engine airplane, N422PB, descended under the canopy of the cirrus airframe parachute system (CAPS) and landed in a residential neighborhood at Houston, Texas. The pilot and passenger sustained minor injuries, and the airplane was substantially damaged. The airplane was registered to and operated by AIRCCS, LLC; Humble, Texas, as a 14 Code of Federal Regulations Part 91 business flight. Day visual meteorological conditions (VMC) prevailed and a flight plan had not been filed. The airplane departed George Bush Intercontinental/Houston Airport (IAH), Houston, Texas, at 1133 and was destined for Austin Bergstrom International Airport (AUS), Austin, Texas.
The pilot reported that during initial climb, he noticed the engine temperatures began increasing and he reduced power in an attempt to lower the engine temperatures. When the airplane was about 900 feet above ground level (agl) the engine began detonating, and soon after there was a complete loss of engine power. With no suitable forced landing areas the pilot deployed the CAPS ballistic parachute system and the airplane impacted terrain and came to rest upright next to a residence.
An initial on-scene wreckage examination showed there was adequate fuel on-board. At the facility where the airplane had most recently been refueled, refueling unit records and a review of security camera video showed that the airplane had been refueled with aviation gasoline and not with jet fuel. Postaccident fuel quality checks of that fuel facility were satisfactory.
The wreckage was moved to a different location and will be further examined. Several avionics components containing non-volatile memory (NVM), including engine performance data, will then be removed from the wreckage for examination and an extraction of useful data is expected.
At 1053 the Automated Surface Observation System at IAH reported wind from 160 degrees at 15 knots gusting to 20 knots, visibility 10 miles, scattered clouds at 3,000 feet agl, broken clouds at 25,000 feet agl, temperature 31 degrees Celsius (C), dew point 24 degrees C, and an altimeter setting of 30.03 inches of Mercury.
In July, a Cirrus SR22 suffered an engine failure in Houston after departing KIAH. The CAPS system was deployed and the airplane came to rest in a neighborhood on the north side of Houston. This makes CAPS save number 53 for Cirrus and no fatalities. The initial NTSB report is below. 14 CFR Part 91:…
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.
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…
When I was doing my instrument and multi-engine training, we did a lot of circle to land approaches. As a student, I could never figure out why these types of approaches would ever be practical when you could an approach straight in to another runway. But, as a good student, I never asked my instructors the purpose of them, I just did them to the best of my ability.
Now, having been flying in the IFR system for almost a decade, I’m finally beginning to fully understand the practical purpose of a circle to land approach. I have actually elected to do an approach where I had to circle to land on several occasions in actual IMC conditions.
One important note to remember on circle to land approaches is that the minimum descent altitude (MDA) is always higher than on a straight in approach. The reason for this is that you are basically joining the pattern for a different runway and you have to be able to visually keep yourself clear of towers and other obstacles. So, you need a higher visibility and a higher ceiling than if you were just lining up to come straight in.
Here are a couple of practical circumstances where it would make sense to do a circle to land approach.
Airports with only 1 straight in approach
This one is easy. There are a number of airports scattered around the US that have only 1 straight in instrument approach published for it. Around my part of Texas, the first one that pops into my mind is the RNAV 31 at T85 in Yoakum, TX. Most of the year, the prevailing wind is out of the south, so 13 is the favored runway at T85. During the winter is when most of the IMC weather happens in South Texas, so that is why the approach is for 31.
Of course, especially this year during the summer, there are some IMC days where an approach to T85 would be necessary. When there is a strong wind out of the south, landing on 31 is impractical, so a pilot would fly the approach to 31, then circle to land on 13.
Approaching from the opposite direction
Take a look at the RNAV 19 at KBMQ, Burnet, TX. The two initial approach fixes (IAF) are IXANY and JIBAJ. If a flight is approaching BMQ from the west or north, this is an easy approach to join. If a flight is coming from Austin (directly the the east and a little south) or San Antonio (almost directly south), it would be a bit of extra flying to get configured properly for the approach. Especially coming from Austin, because the degree of turn to join at JIBAJ wouldn’t make the approach practical.
Well, how about vectors? Unfortunately, Houston Center doesn’t have this approach depicted so vectors aren’t a possibility. Center can give you vectors north to make the angle a little easier to join at JIBAJ, but they can’t vector you onto the approach.
Direct DLORA to join is another option, but again, if you are approaching from the southeast, the angle is wrong.
Insert the RNAV 01 approach with a circle to land. AMUSE is right on V163, so it’s really easy to join the approach there coming from the south. Coming from Austin, joining the approach at SUBIE works out great. Fly down to the MDA, join the left downwind for 19, and everyone is happy.
VOR Circle to Land Approaches
Every instrument pilot has had an instructor “force” them to do a VOR A or VOR B approach and no one enjoys them. I personally think they are good practice. With the number of RNAV systems and RNAV approaches out there, though, VOR approaches are becoming a bit archaic.
They do have a place in this discussion, though. A VOR approach is given an A or B designation when the angle of the final approach course is greater than 30 degrees to the runway (VOR A KLZZ), or the final approach course is lined up with the runway, but the MDA is too high to practically descend and land (VOR A KGRK or the VOR/DME C KASE).
So, there are practical uses for a Circle to Land approach. The next time you do some IMC work with an instructor, ask him/her if you can include one.
When I was doing my instrument and multi-engine training, we did a lot of circle to land approaches. As a student, I could never figure out why these types of approaches would ever be practical when you could an approach straight in to another runway. But, as a good student, I never asked my instructors…
Ever wanted to be a Cirrus owner, but the economics of being a single owner just don’t make sense for you? If you’re in the San Marcos/New Braunfels/Austin area, you now have a chance to join a Cirrus SR20 partnership at the San Marcos Municipal airport, KHYI.
The Cirrus SR20 partnership group is looking for 2-4 more members to buy in to a 2006 or 2007 Cirrus SR20 GTS. The plane will be kept at KHYI and the group already has a hangar for it.
Ever wanted to be a Cirrus owner, but the economics of being a single owner just don’t make sense for you? If you’re in the San Marcos/New Braunfels/Austin area, you now have a chance to join a Cirrus SR20 partnership at the San Marcos Municipal airport, KHYI. The Cirrus SR20 partnership group is looking for…
2 Comments
Thanks! I was flying some practice approaches and the last approach got lazy and decided to go direct FAF instead of IAF. What a surprise! At first I thought it may have been due to the direct route was 90° From final and might have exceeded some limit. Now I know!
Thanks! I was flying some practice approaches and the last approach got lazy and decided to go direct FAF instead of IAF. What a surprise! At first I thought it may have been due to the direct route was 90° From final and might have exceeded some limit. Now I know!
Thank you. I have fussed over this for 20 years and not understood it.