The Flight Director as a Backup

I’ve noticed that a lot of general aviation pilots tend to ignore the flight director on the attitude indicator.  A lot of pilots don’t even know what it’s there for or how to use it.  Talk to any airline pilot, though, and he or she will tell you how important the flight director actually is.

In most high performance airplanes, the flight director comes on when the autopilot comes on.  Essentially, the autopilot is following the flight director, which tells the autopilot where to go.  The flight director can also be used with the autopilot off, when hand flying an approach, for example.  By turning the flight director on, it will show you where you need to fly to stay on course and on glide slope.

Flight Director

The flight director is most often controlled by the autopilot controller.  The same buttons you use to put the autopilot in heading mode also tells the flight director to follow the heading bug when the autopilot is off.  When you move the heading bug (or change course on the GPS, depending on which mode you have selected), the flight director will show you when you need to turn and when you need to stop turning.  It directs your flight attitude, hence the name.

I recently discovered it’s a great backup when you have some instruments on the fritz.  I went on a long flight in a steam gauge Piper Malibu and the attitude indicator started reading erratically.  While flying straight and level, it would randomly indicate that I was in a 10 degree bank to the right, swing back and show wings level, then show a 3 degree turn left.  This went on for a while.  We were in VMC conditions, so legality wasn’t a problem, but it was kind of disorienting.

After a little while of this, the autopilot started acting up.  It would start oscillating the pitch up and down, making it seem like we were going through a moguls course in the air.  I ended up turning the autopilot off and hand flying the airplane.

This led to a conundrum, since my attitude indicator was unreliable.  I could definitely look outside, since it was VMC, seeing when I was level and when I wasn’t.  That would create a higher workload for me, which on a long flight like I was on, would lead to an increase in fatigue.  The solution?  The flight director!

I turned the autopilot off, but I left the flight director up.  It wasn’t referencing the bank angle that the attitude indicator was showing since the KFC 150 goes off of the turn coordinator.  So, if I just followed the attitude indicator, I could just keep scanning the instruments and relieve a little bit of my workload.

It actually worked really well.  By just following the flight director, I was able to stay on course and on altitude with only minor attitude adjustments whenever we hit turbulence.

So, if you’re attitude indicator and autopilot decide to stop working on you, then bring up the flight director, push the same buttons you would if you were using the autopilot, and it works as a great backup.

Similar Posts

  • Airspace Alert: Houston Executive Tower Opens

    For those of you who frequent the Houston area, make sure to check your NOTAMs.  The Houston Executive Airport (KTME) in Katy recently opened a control tower.  The Houston Executive tower information won’t show up on the sectional chart till the new chart comes out in the spring.  The only way to get the information about the tower and the airspace will be via NOTAMs or when the new Airport/Facilities Directory comes out on November 3rd.  The tower opened October 1st.

    According to AOPA, the airspace will remain Class G around the airport, even though there is a control tower in place.  Since the Houston Executive tower is there, it will be mandatory to contact the tower when passing through the airspace.  KTME’s airspace stretches up to 2,000 feet MSL and goes out to a 4 sm radius around the airport.  It is a VFR Only tower, so the controllers do not have radar.

    The tower is open from 6am-10pm, local time, 7 days a week.

    Frequency Information

    Houston Executive Tower:  126.975

    Houston Executive Ground Control/Clearance Delivery:  132.075

    Houston Executive ATIS:  119.525

     

  • FICON Reports

    Field Condition, or FICON, reports show up in NOTAMs both during the summer time and the winter time. In the southern states, FICON reports are seen more in the summertime during and after hard rains and thunderstorms (with the exception of winter 2021 & 2022, where Texans quickly got familiar with FICON reports after some very unusual winter weather). In cold winter climates, FICON reports are a staple during the winter season, showing up during and after snow & ice storms.

    The question is, what do those codes mean in the FICON report? You could see 5/5/5, 3/3/3, 3/4/4 and any combination thereof. And why are there three numbers?

    Let’s start with the second question first. The three different numbers in the FICON report indicate the 3 different sections of the runway: the touchdown third, midpoint third, and rollout third of the runway.

    Now, what are those numbers describing? The three numbers are the indication of how slippery that portion of the runway is. This is referred to as a Runway Condition Code (or RCC). The lower the number, the more slippery the runway is. The higher the number, the dryer the runway. The scale is 0-6, with 6 being completely dry and zero being no traction at all.

    Here is the FAA table for the RCCs.

    Now, in order for those RCC codes to generate, at least 25% of the surface must be wet. If there are just spots of standing water, slush or snow, a FICON report will be issued to report the contaminants, but no codes will be generated.

    The Runway Condition Codes are only part of a FICON report. In addition to the codes, a descriptor in the NOTAM will be published describing what percentage of the portion of the runway is affected and by what.

    For example: RWY 28 FICON 3/3/3 100 PRCNT 2IN DRY SN OVER COMPACTED SN.

    Deciphered, that is saying that all sections of Runway 28 have braking deceleration that is noticeably reduced or direction control is noticeably reduced and 100% of each section has 2 inches of dry snow over compacted snow. Sounds like a runway to avoid!

    Braking action reports are separate from FICON reports, but also issued via NOTAM. Braking action reports are issued by the airport manager whereas the FICON reports are computer generated.

  • Beechcraft Flap Issues

    There has always been something that felt wrong to me about how the walkway on many models of Beechcraft extends onto the right hand flap. I have never felt right about stepping onto the flap as I make my way into and out of my dad’s E33A Bonanza and therefore I generally try to step over top of it and place my foot on the wing instead. But does this effort actually make any difference, or am I just making my self look silly for no reason?

    Nutplate Cracking 3

    Well, as it turns out, it wasn’t such a bad idea. In 2007, a pilot flying a Beech reported a split flap condition. Upon inspection, it was found that there was damage to the actuation rod attachment as well as the nose rib and nut plates. Six other aircraft were checked and found to have similar damage. These findings were submitted to Hawker Beechcraft and in 2008 and they issued a maintenance alert regarding the issue. In 2011 the FAA issued SAIB CE-11-21 (Special Airworthiness Information Bulletin) to alert owners, operators, and maintenance personnel about the problem; specifically warning of the potential for cracking in the nose flap rib (part number 35-165050-84). And while its true that this type of damage is not limited to the right hand flap, it is known to be much more common on that side. Stepping over the flap instead of on it is recommended by both the FAA and Beechcraft as a solution.

    Unfortunately, the flap cracking is known to span a wide variety of aircraft types. A 2011 “Safety Communique” issued by Hawker Beechcraft lists the affected models as:

    -Bonanza 33, 35, and 36
    -Baron 55, 56, 58, and 95
    -Duke 60

    Damage at the flap actuator point (Photo Courtesy of AOPA)
    Damage at the flap actuator point (Photo Courtesy of AOPA)

     

    According the the FAA, the cracking can been found most commonly on airframes which are between 4,000 and 6,500 hours, but has also been found on aircraft with as few as 2,000.

    So, what do we do about it?

    First off, although much of the damage is difficult to detect without dis-assembly, the paperwork from both the FAA and Beechcraft recommend taking a look at the flap yourself to see if there are any obvious signs of problems. They also suggest taking special care looking in this area during your preflight inspections.

    Next, if you have an airplane which may be susceptible to cracking, talk to who ever is doing your maintenance work and have them look carefully during your annual inspections. I talked to one of the IA’s at our shop who has dealt with this issue before and he told me that most shops will remove the flap and send it away to a repair station to have it fixed. It’s possible that if you purchased your airplane used it may have already had this issue taken care of; a quick look through the maintenance logbooks should clear up any questions.

    Repaired rib next to a damaged rib (Courtesty:  AOPA)
    Repaired rib next to a damaged rib (Courtesty: AOPA)

     

    Regardless of whether your airplane is known to suffer from this problem or not, do your best to avoid stepping on the flap when getting in and out of the cockpit. It is also a good idea to ask your passengers to do the same as this simple act could end up saving you big headaches and big money someday down the road.

    For more information regarding the flap issues discussed above, talk to your maintenance provider and visit these links:

    ABS Flight Controls, Flaps, and Trim System Inspection, Repair and Rigging Guide (See Page 17)

    ABS Information on SAIB CE-11-21

    Andrew Robinson is a 135 Charter Pilot and flight instructor in Pennsylvania.  He flies Pilatus PC-12s and instructs in Beechcraft Bonanzas.

  • Flying Through Rain

    For the most part, flying through rain is a non-event. If the NexRad or Radar is showing light green or dark green, usually there aren’t that many bumps and your plane just gets a wash. Sometimes the visibility drops down a little bit making us IFR pilots have to transition to our instruments.

    It get’s a little more exciting when the precipitation on your screen turns to yellow. This means there is a lot more precipitation echoes either in the clouds or coming out of the clouds, meaning harder rain. I usually tend to stay away from yellow unless it’s absolutely necessary to go through it.

    I had a situation a few weeks ago where I deemed it necessary to fly through some yellow NexRad returns. I was flying a G1000 Columbia into Monroe, Louisiana, KMLU. The winds were mostly light, but slightly favoring runway 04, which was the runway in use. As I got closer, a decent size rain shower with mostly yellow returns was sitting over the final approach fix for runway 04 and slowly tracking to the northeast.

    I didn’t particularly want to spend the entire approach getting beat on with rain, so I decided to fly the RNAV 14 approach at MLU and circle to land on runway 04. The rain hadn’t quite reached the airport yet, so I decided that circling to 04 should be no problem.

    I started the RNAV 14 at the FLESH IAF. Since I was approaching from the west, I did not need to do the procedure turn, so I joined the Final Approach Course (FAC) after crossing FLESH.

    In the meantime, that rain shower was inching closer to the FAC for the RNAV 14. I wasn’t concerned about my safety if I flew through some of it and I didn’t have passengers on board who would get nervous, so I elected to continue. I wasn’t seeing any lightning coming out of the clouds, so it appeared to only be moderate rain.

    Just before I got to JIVEY, the FAF, I entered the clouds and the rain. About 20 seconds later, my altimeter and airspeed started bouncing around a lot. Now, based on all I’ve said so far, what would cause that, and what would you do?

    (Jeopardy theme song playing while contestants ponder questions)

    The answers? Due to the moderate precipitation, water had gotten into my static port and caused the unusual readings on my altimeter and airspeed indicators on the G1000.

    I had experienced this before, so I knew what to do. I reached down and turned the static source from primary to alternate, which starts taking static pressure from inside the cabin in the Columbia. Instantly, everything went normal.

    The other time I had experienced this was also in a Columbia, so I’m under the impression that the way the Columbia static ports are designed, they are a little bit more susceptible to water creeping into them than other airplanes.

    Moral of the story? If your pitot/static instruments start jumping around, the first thing you do is turn your alternate static source on.

  • AOPA Air Safety Foundation Survival Seminar

    The AOPA’s Air Safety Foundation will be returning to Texas this coming week with their After the Crash:  Surviving An Aircraft Accident seminar.  Though aircraft accidents are rare to most pilots, they still happen.  It is best to be prepared with the proper knowledge and supplies in case you are stranded in a remote area while awaiting help to arrive.

    The seminar will cover the following items:

    • How and what to pack in a survival kit
    • Ways to help search parties find you
    • What to do first immediately after the off airport landing
    • How to survive will awaiting rescue

    The seminar will be put on in Houston, San Antonio, and Austin on three consecutive nights, the 20th-22nd, so everyone will get a chance to attend.  The location and times are below.

    No signup is necessary, just show up and be ready to learn.  The seminar does count for WINGs credit and there will be a sign in sheet at each event.

    The AOPA Air Safety Foundation puts on numerous seminars throughout the country during the year covering a wide variety of topics relevant to general aviation pilots.  The content is always interesting and the presenter always knowledgeable and entertaining.  Hope to see you there!

    Tuesday, January 20th

    Wyndham Hotel, Houston West
    14703 Park Row Blvd.
    Houston, TX 77079
    7:00pm-9:00pm

    Wednesday, January 21st

    Doubletree Hotel, San Antonio Airport
    37 NE Loop 410
    San Antonio, TX 78216
    7:00pm-9:00pm

    Thursday, January 22nd

    Omni Hotel, Southpark
    4140 Governor’s Row
    Austin, TX 78744
    7:00pm-9:00pm

    For more information on the event and the locations, please click here.

  • Cirrus CAPS Pull in Arkansas

    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.

    http://www.cbsnews.com/live/video/pilot-forced-to-deploy-emergency-parachute-in-arkansas/

    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.

Leave a Reply

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