Modern autopilots can reduce workload and help you stay ahead of the airplane, but only when you understand what they’re doing—and what they might do next. An incomplete checkout or misunderstanding of the system can add workload when you least need it.
Join PilotWorkshops’ Ryan Koch for Beyond the Buttons: Mastering Your Modern Autopilot, a webinar exploring the habits pilots need to get more from today’s autopilots, stay ahead of changing modes, and recognize when the system isn’t doing what they intended.
Ryan leads the development of PilotWorkshops’ online training courses and pilot-friendly manuals. An active instrument flight instructor and flight simulator expert, he has developed courses including Instrument Rating Accelerator, Private Pilot: The Missing Lessons, Garmin GTN: Next Level, and Advanced IFR.
https://media.ifrfocus.com/wp-content/uploads/2026/08/26155317/You-Know-How-to-Use-Your-Autopilot.-But-Do-You-Understand-It.png10001250IFR Focus Teamhttps://media.ifrfocus.com/wp-content/uploads/2025/07/14115136/IFR-Focus-Logo_White_Blue_Web-01.pngIFR Focus Team2026-10-23 07:45:352026-10-22 09:16:38Webinar Video: Beyond the Buttons — Mastering Your Modern Autopilot
I fly out of a small, nontowered airport (KLDJ) tucked under the New York Area Class B. If I can depart Runway 27, I can get my clearance and release in about 5 minutes. However, if I tell them I’m departing Runway 9, I’ll get an indefinite hold for release because of landing traffic at Newark. By indefinite, I mean “infinite.” It will never happen.
I know I could depart and pick up an IFR clearance in the air. But that creates a dangerous scud-running scenario if the weather is marginal. And I’ve found it’s essentially impossible to pick up a clearance airborne near NYC.
Is there a remedy for this when I must depart Runway 9 due to winds?
— Arian R.
It’s easy to see why Runway 9 departures from Linden (KLDJ) are basically a non-starter. There’s no way Newark will create the gap to make a space for you. If Newark is using the Runway 4 group, it would be a gap in their arrivals for your departure. If it’s the Runway 22 group, you could interfere with normal departures and a potential missed approach from a Newark arrival. Fuhgeddaboudit.
That’s why your best option for an IFR departure from Linden is off Runway 27. You’re pointing away from Newark. Sure, there’s other airspace out there that has to be clear for you, but New York area controllers handle that kind of airplane Tetris all day.
However, there are two other options besides departing VFR and attempting an IFR clearance in the air. One of them is routinely approved for airports near Linden. I know because I have friends who fly there. But it requires at least marginal VFR weather. The other would require some willingness from Newark, but could work in weather that’s lower than the minimum for VFR flight in Class E airspace.
IFR Clearance, VFR Departure
If you feel confident you can remain safely VFR for several minutes after departure, you can request your IFR clearance on the ground with a request for a VFR departure to activate IFR in the air. You’d get the clearance in the normal CRAFT format, plus a release to depart VFR. You would depart squawking your assigned transponder code (not 1200) and comply with any restrictions ATC imposed on heading and altitude (if any). Once airborne, you contact Departure, radar identify, and get an acknowledgment that you can now “consider yourself IFR.” At that point, you can enter IMC and be on your way. You must remain VFR until then.
HAVE YOUR CLEARANCE BEFORE TAKEOFF
Departing VFR to pick up an IFR clearance in the air isn’t the same as departing VFR with your IFR clearance already issued. In the latter case, ATC has your clearance information, and you can activate IFR once airborne and in contact with the appropriate controller. You must remain VFR until then.
This is different from getting the clearance in the air as you already have all the information in the clearance, Departure is expecting you, and your airplane will tag up on radar right away because you’re already squawking a discrete code.
Some say this technique is a grey area. I’d say it’s more off white. The relevant part of the controller bible (J.O. 7110.65) is 4-3-9. VFR RELEASE OF IFR DEPARTURE.
When an aircraft which has filed an IFR flight plan requests a VFR departure through a terminal facility, FSS, ARTCC Flight Data Unit, or air/ground communications station:
After obtaining, if necessary, approval from the facility/sector responsible for issuing the IFR clearance, you may authorize an IFR flight planned aircraft to depart VFR. Inform the pilot of the proper frequency and, if appropriate, where or when to contact the facility responsible for issuing the clearance.
PHRASEOLOGY—
VFR DEPARTURE AUTHORIZED. CONTACT (facility) ON (frequency) AT (location or time if required) FOR CLEARANCE.
If the facility/sector responsible for issuing the clearance is unable to issue a clearance, inform the pilot, and suggest that the delay be taken on the ground. If the pilot insists upon taking off VFR and obtaining an IFR clearance in the air, inform the facility/sector holding the flight plan of the pilot’s intentions and, if possible, the VFR departure time.
If read exactly as worded, it would mean you planned to depart VFR and pick up the clearance in its entirety once airborne. You actually don’t need any permission to do that—people do it all the time. You depart on a 1200 squawk and call ATC soon after. You get your entire clearance while flying, radar ID, and are immediately active IFR because you’re already flying. But, as you mentioned, ATC may be too busy.
That said, there is a small advantage to calling ATC on the ground and giving them a heads up that you’re departing VFR and planning to get your clearance once you’re underway. There is some coordination that might be needed between facilities. And if you were departing a towered airport with a flight plan on file but you didn’t get the clearance, they might cancel it. At the very least it would be confusing.
What I’m talking about, and have done successfully myself, is this approved FAA procedure with “Since we’re already talking to each other, let’s get a few things out of the way before you actually depart.” Departing with your clearance already issued—but not activated—makes life much easier for you, and nominally easier for ATC. Once you contact them airborne, the only thing remaining to do is radar ID. This also shortens the time you must remain VFR.
Some ATC facilities won’t play ball on this, either by local procedures or culture. I’ve heard that Las Vegas isn’t so keen on activation in the air. But then, it’s often sunny there, so maybe it doesn’t come up much.
IFR Clearance, IFR Departure in Class G
If the ceilings and visibility are high enough, you could depart Runway 9 and turn around to get heading 270 before you climb above 700 AGL.
The other option could work when you have sub-VFR conditions, but it’s good enough to depart visually and turn around. Linden is Class G airspace from the surface to 700 AGL. ATC can’t dictate what you do in that airspace. So if the ceilings and vis are high enough that you could depart Runway 9 and turn around to get heading 270 before you climb above 700 AGL, you would be doing the same thing from an ATC perspective as departing Runway 27.
The advantage here is that you’re IFR from takeoff, so you could go IMC as soon as you’re turned around and clear of obstacles. The catch is ATC would have to play along. Worth asking though. It might even vary controller to controller.
You would request your IFR clearance saying you can “enter controlled airspace heading 270.” If the controller asks what runway you’d be departing … well, I might try and avoid saying “departing Runway 9” in case the very words give someone hives. I’d answer with, “I’ll have to depart and turn around right away before entering controlled airspace, but I can definitely enter controlled airspace heading 270 off Linden.”
I don’t know if the system would see you lifting off Runway 9 and anticipate a conflict with Newark traffic before you could make the 180. Of course, there could be some local procedures that preclude one or both of these options off Linden, even if it is allowed only a few miles away.
One last thought: The only approach to Linden has a circling minimum of 600 feet AGL (basically). The departure procedure for Linden says NA for both runways due to obstacles. That certainly hints there are obstacles out there you’d best be able to avoid visually until you climb 600 feet.
But if this is your home airport, presumably you know the local hazards well.
https://media.ifrfocus.com/wp-content/uploads/2026/08/04112916/New-IFR-Mastery-Scenario-Which-Approach-Would-You-Request.png10001250Jeff Van Westhttps://media.ifrfocus.com/wp-content/uploads/2025/07/14115136/IFR-Focus-Logo_White_Blue_Web-01.pngJeff Van West2026-10-20 07:45:592026-10-16 12:45:28Practical IFR: Activate in the Air
Visual Descent Points, or VDPs, help pilots determine when they can begin a normal descent from the minimum descent altitude on a nonprecision approach. In this video tip, we’ll look at how to identify a VDP on an approach chart, when to begin the descent, and why the VDP is different from the missed approach point.
This video tip is from Sporty’s Instrument Rating Course. If you want to sharpen your skills and build more confidence in the system, Sporty’s Instrument Rating Course covers these required reports in detail—along with real-world scenarios and ATC audio to help you sound like a pro on every flight.
ForeFlight continues to add features designed to make preflight planning easier and give pilots more information when it matters most in the cockpit.
Join Thomas Daugherty, Head of ForeFlight Training Solutions, for a look at the latest updates to ForeFlight, including ClearNOTAMs and Mobile Clearance Delivery, along with new safety features such as Emergency Glide.
Whether you’re a longtime ForeFlight user or just getting familiar with the app, this webinar is a chance to see what’s new and learn how these features can help you fly smarter.
https://media.ifrfocus.com/wp-content/uploads/2026/10/05103021/Webinar-Whats-New-With-ForeFlight.png10001250IFR Focus Teamhttps://media.ifrfocus.com/wp-content/uploads/2025/07/14115136/IFR-Focus-Logo_White_Blue_Web-01.pngIFR Focus Team2026-10-14 14:00:552026-10-14 16:40:05Webinar Video: What’s New With ForeFlight
Modern avionics can make an instrument approach remarkably predictable. But every once in a while, the airplane does something you aren’t expecting and that’s when your instrument skills still matter. I was reminded of that recently while flying a Challenger into Jackson, Wyoming (JAC).
Jackson Hole isn’t an airport we visit frequently, and it’s not an approach you want to treat casually. The airport sits at a high elevation (6400′), surrounded by mountainous terrain, so we spent more time than usual briefing the arrival and approach. The weather was officially VFR, but it wasn’t exactly clear. As we approached the initial approach fix, we were in and out of layers.
We were also flying an approach that we had thoroughly briefed, so we had a pretty good idea of what the airplane should be doing and when. Then the needles went green transferring the nav input source from FMS to LOC. The autopilot had captured the approach and began an unexpected turn toward the final approach course which wasn’t what we were expecting at that point in the procedure.
We didn’t spend much time trying to figure out why. We disconnected the automation and went back to hand-flying. With two pilots in the cockpit and a thoroughly briefed approach, we were able to quickly get the airplane back where we wanted it, reestablish the automation, and continue the approach. It wasn’t a dramatic event, but it was a good reminder of several fundamentals that can get overlooked when we’re accustomed to letting the automation do the flying.
The Automation Wasn’t the Problem
Tim Decker recently wrote about the importance of cross-checking automation and offered three simple rules for doing it. Those rules came to mind as I thought about what happened at Jackson Hole. The important event to recognize was that the airplane was doing something we didn’t expect.
Modern avionics are very good at following instructions, but they don’t know what you intended unless you’ve given them the right instructions—and even when everything is programmed correctly, the airplane can sometimes behave differently than you anticipated. That’s why an instrument pilot can’t simply monitor whether the autopilot is engaged or whether the appropriate annunciation is displayed. You have to monitor the resulting flight path.
Where is the airplane?
Where is it going?
What should it be doing next?
And does what you’re seeing match what you expected? At Jackson Hole, the answer was no. We caught it quickly because we were looking.
Fly First, Troubleshoot Later
Fly First, Troubleshoot Later
When an automated system does something unexpected, it’s natural to want to understand why. Which mode is active? Did we miss something in the set-up? Why did it capture? Those are all reasonable questions, but they don’t necessarily need to be answered immediately.
The immediate question is whether the airplane doing what I need it to do? If the answer is no, disconnecting the automation may be the quickest way to eliminate uncertainty and get back to the fundamentals. Fly the airplane first and then figure out what happened.
That doesn’t mean every unexpected automation event requires immediately turning everything off. It means the pilot needs to remain comfortable enough with the airplane to recognize when automation is no longer helping and to take control by any means available without hesitation.
Are You Ready to Hand-Fly?
That’s where instrument proficiency comes in. There’s a difference between practicing hand-flying and being ready to hand-fly. You don’t need to turn off the autopilot on every IFR flight just to prove that you can fly an approach. Automation is one of the great tools available to an instrument pilot, and using it appropriately can reduce workload and increase safety.
But if the autopilot suddenly disconnects—or you disconnect it because the airplane isn’t doing what you expect—you shouldn’t suddenly feel like you’ve lost your primary flight-control system. The basic skills still need to be there.
Can you maintain heading and altitude?
Can you control the airspeed without chasing it?
Can you intercept and track a course?
Can you configure the airplane for landing while maintaining control?
Can you fly the approach while also thinking about what comes next?
Those aren’t skills that should disappear just because the airplane has an autopilot. But like any skill, they can get rusty if they’re rarely used.
The Briefing Was a Big Part of the Solution
One of the things that helped us at Jackson Hole happened before we ever got to the approach was that we had briefed it carefully. That wasn’t just about checking the minimums or reviewing the missed approach (although we did that too). We talked through the procedure and the environment because this was an airport we don’t fly into regularly, at high elevation, in mountainous terrain and with conditions that weren’t as straightforward as the VFR designation might suggest.
That preparation made the surprise much easier to recognize. And that’s an important part of instrument flying. You can’t recognize that something is unexpected unless you have some idea of what you expected in the first place. A good approach briefing creates that mental picture.
Use All the Resources You Have
I also had another advantage that day: another pilot in the cockpit. Crew resource management is a major part of professional flying, and having a second set of eyes makes it easier to monitor the airplane, the automation and the approach at the same time, but the underlying discipline applies to single-pilot flying, too.
Brief the approach out loud. Think about what the airplane should do at each major point. Know what the important modes and transitions should look like. And when something doesn’t make sense, don’t simply assume the airplane must be right.
Automation is an incredible tool. Use it. Trust it when appropriate. But keep your instrument skills sharp enough that you’re ready for the moment when you have to take back the airplane.
https://media.ifrfocus.com/wp-content/uploads/2026/10/07142821/Be-Ready-to-Take-Back-the-Airplane.png10001250Eric Radtkehttps://media.ifrfocus.com/wp-content/uploads/2025/07/14115136/IFR-Focus-Logo_White_Blue_Web-01.pngEric Radtke2026-10-13 07:45:562026-10-07 14:28:47Be Ready to Take Back the Airplane
What would you do if weather, darkness, and geography left you with several imperfect choices for an IFR flight?
That’s the dilemma in this month’s IFR Mastery scenario from PilotWorkshops. You’re flying your Cirrus from Buffalo to Iron Mountain, Michigan and the easy route is anything but easy.
The shortest IFR option takes you north across Michigan and then over Lake Michigan, including about 50 miles of overwater IMC. The alternative around Chicago adds nearly 100 miles and pushes your arrival toward sunset. You could also try filing directly through Chicago’s Class B, or fly VFR along the Chicago shoreline and pick up an IFR clearance farther north.
Each option has its own set of risks, complications, and unknowns.
Which route would you choose?
Watch the scenario below and make your decision.
It’s more than picking the shortest route
Instrument flying often means choosing between imperfect options. Weather, terrain, airspace, daylight, fuel, and workload can all change the risk profile and sometimes the route that looks best on paper isn’t the one that makes the most sense in the air.
That’s the decision-making skills that IFR Mastery is designed to develop. Each month, PilotWorkshops presents a new real-world IFR scenario that puts you in the pilot’s seat. You’ll evaluate the situation, make your decision, and then compare your thinking with experienced instructors as they explain the factors that influenced their choices.
Think you’ve made the right call?
Watch the free scenario briefing above, then sign in or start a free 30-day trial to access the complete scenario, instructor analysis, and the complete library of nearly 200 IFR scenarios.
https://media.ifrfocus.com/wp-content/uploads/2026/10/07122759/ifr-imc-enroute-cruise-clouds-scaled.jpeg19202560Eric Radtkehttps://media.ifrfocus.com/wp-content/uploads/2025/07/14115136/IFR-Focus-Logo_White_Blue_Web-01.pngEric Radtke2026-10-09 07:45:352026-10-07 12:28:31New IFR Mastery: No Easy Way North
Webinar Video: Beyond the Buttons — Mastering Your Modern Autopilot
/by IFR Focus TeamJoin PilotWorkshops’ Ryan Koch for Beyond the Buttons: Mastering Your Modern Autopilot, a webinar exploring the habits pilots need to get more from today’s autopilots, stay ahead of changing modes, and recognize when the system isn’t doing what they intended.
Ryan leads the development of PilotWorkshops’ online training courses and pilot-friendly manuals. An active instrument flight instructor and flight simulator expert, he has developed courses including Instrument Rating Accelerator, Private Pilot: The Missing Lessons, Garmin GTN: Next Level, and Advanced IFR.
Practical IFR: Activate in the Air
/by Jeff Van WestI fly out of a small, nontowered airport (KLDJ) tucked under the New York Area Class B. If I can depart Runway 27, I can get my clearance and release in about 5 minutes. However, if I tell them I’m departing Runway 9, I’ll get an indefinite hold for release because of landing traffic at Newark. By indefinite, I mean “infinite.” It will never happen.
I know I could depart and pick up an IFR clearance in the air. But that creates a dangerous scud-running scenario if the weather is marginal. And I’ve found it’s essentially impossible to pick up a clearance airborne near NYC.
Is there a remedy for this when I must depart Runway 9 due to winds?
— Arian R.
It’s easy to see why Runway 9 departures from Linden (KLDJ) are basically a non-starter. There’s no way Newark will create the gap to make a space for you. If Newark is using the Runway 4 group, it would be a gap in their arrivals for your departure. If it’s the Runway 22 group, you could interfere with normal departures and a potential missed approach from a Newark arrival. Fuhgeddaboudit.
That’s why your best option for an IFR departure from Linden is off Runway 27. You’re pointing away from Newark. Sure, there’s other airspace out there that has to be clear for you, but New York area controllers handle that kind of airplane Tetris all day.
However, there are two other options besides departing VFR and attempting an IFR clearance in the air. One of them is routinely approved for airports near Linden. I know because I have friends who fly there. But it requires at least marginal VFR weather. The other would require some willingness from Newark, but could work in weather that’s lower than the minimum for VFR flight in Class E airspace.
IFR Clearance, VFR Departure
If you feel confident you can remain safely VFR for several minutes after departure, you can request your IFR clearance on the ground with a request for a VFR departure to activate IFR in the air. You’d get the clearance in the normal CRAFT format, plus a release to depart VFR. You would depart squawking your assigned transponder code (not 1200) and comply with any restrictions ATC imposed on heading and altitude (if any). Once airborne, you contact Departure, radar identify, and get an acknowledgment that you can now “consider yourself IFR.” At that point, you can enter IMC and be on your way. You must remain VFR until then.
Departing VFR to pick up an IFR clearance in the air isn’t the same as departing VFR with your IFR clearance already issued. In the latter case, ATC has your clearance information, and you can activate IFR once airborne and in contact with the appropriate controller. You must remain VFR until then.
This is different from getting the clearance in the air as you already have all the information in the clearance, Departure is expecting you, and your airplane will tag up on radar right away because you’re already squawking a discrete code.
Some say this technique is a grey area. I’d say it’s more off white. The relevant part of the controller bible (J.O. 7110.65) is 4-3-9. VFR RELEASE OF IFR DEPARTURE.
When an aircraft which has filed an IFR flight plan requests a VFR departure through a terminal facility, FSS, ARTCC Flight Data Unit, or air/ground communications station:
After obtaining, if necessary, approval from the facility/sector responsible for issuing the IFR clearance, you may authorize an IFR flight planned aircraft to depart VFR. Inform the pilot of the proper frequency and, if appropriate, where or when to contact the facility responsible for issuing the clearance.
PHRASEOLOGY—
VFR DEPARTURE AUTHORIZED. CONTACT (facility) ON (frequency) AT (location or time if required) FOR CLEARANCE.
If the facility/sector responsible for issuing the clearance is unable to issue a clearance, inform the pilot, and suggest that the delay be taken on the ground. If the pilot insists upon taking off VFR and obtaining an IFR clearance in the air, inform the facility/sector holding the flight plan of the pilot’s intentions and, if possible, the VFR departure time.
If read exactly as worded, it would mean you planned to depart VFR and pick up the clearance in its entirety once airborne. You actually don’t need any permission to do that—people do it all the time. You depart on a 1200 squawk and call ATC soon after. You get your entire clearance while flying, radar ID, and are immediately active IFR because you’re already flying. But, as you mentioned, ATC may be too busy.
That said, there is a small advantage to calling ATC on the ground and giving them a heads up that you’re departing VFR and planning to get your clearance once you’re underway. There is some coordination that might be needed between facilities. And if you were departing a towered airport with a flight plan on file but you didn’t get the clearance, they might cancel it. At the very least it would be confusing.
What I’m talking about, and have done successfully myself, is this approved FAA procedure with “Since we’re already talking to each other, let’s get a few things out of the way before you actually depart.” Departing with your clearance already issued—but not activated—makes life much easier for you, and nominally easier for ATC. Once you contact them airborne, the only thing remaining to do is radar ID. This also shortens the time you must remain VFR.
Some ATC facilities won’t play ball on this, either by local procedures or culture. I’ve heard that Las Vegas isn’t so keen on activation in the air. But then, it’s often sunny there, so maybe it doesn’t come up much.
IFR Clearance, IFR Departure in Class G
If the ceilings and visibility are high enough, you could depart Runway 9 and turn around to get heading 270 before you climb above 700 AGL.
The other option could work when you have sub-VFR conditions, but it’s good enough to depart visually and turn around. Linden is Class G airspace from the surface to 700 AGL. ATC can’t dictate what you do in that airspace. So if the ceilings and vis are high enough that you could depart Runway 9 and turn around to get heading 270 before you climb above 700 AGL, you would be doing the same thing from an ATC perspective as departing Runway 27.
The advantage here is that you’re IFR from takeoff, so you could go IMC as soon as you’re turned around and clear of obstacles. The catch is ATC would have to play along. Worth asking though. It might even vary controller to controller.
You would request your IFR clearance saying you can “enter controlled airspace heading 270.” If the controller asks what runway you’d be departing … well, I might try and avoid saying “departing Runway 9” in case the very words give someone hives. I’d answer with, “I’ll have to depart and turn around right away before entering controlled airspace, but I can definitely enter controlled airspace heading 270 off Linden.”
I don’t know if the system would see you lifting off Runway 9 and anticipate a conflict with Newark traffic before you could make the 180. Of course, there could be some local procedures that preclude one or both of these options off Linden, even if it is allowed only a few miles away.
One last thought: The only approach to Linden has a circling minimum of 600 feet AGL (basically). The departure procedure for Linden says NA for both runways due to obstacles. That certainly hints there are obstacles out there you’d best be able to avoid visually until you climb 600 feet.
But if this is your home airport, presumably you know the local hazards well.
Video Tip: Visual Descent Points
/by IFR Focus TeamVisual Descent Points, or VDPs, help pilots determine when they can begin a normal descent from the minimum descent altitude on a nonprecision approach. In this video tip, we’ll look at how to identify a VDP on an approach chart, when to begin the descent, and why the VDP is different from the missed approach point.
This video tip is from Sporty’s Instrument Rating Course. If you want to sharpen your skills and build more confidence in the system, Sporty’s Instrument Rating Course covers these required reports in detail—along with real-world scenarios and ATC audio to help you sound like a pro on every flight.
Webinar Video: What’s New With ForeFlight
/by IFR Focus TeamForeFlight continues to add features designed to make preflight planning easier and give pilots more information when it matters most in the cockpit.
Join Thomas Daugherty, Head of ForeFlight Training Solutions, for a look at the latest updates to ForeFlight, including ClearNOTAMs and Mobile Clearance Delivery, along with new safety features such as Emergency Glide.
Whether you’re a longtime ForeFlight user or just getting familiar with the app, this webinar is a chance to see what’s new and learn how these features can help you fly smarter.
Be Ready to Take Back the Airplane
/by Eric RadtkeModern avionics can make an instrument approach remarkably predictable. But every once in a while, the airplane does something you aren’t expecting and that’s when your instrument skills still matter. I was reminded of that recently while flying a Challenger into Jackson, Wyoming (JAC).
Jackson Hole isn’t an airport we visit frequently, and it’s not an approach you want to treat casually. The airport sits at a high elevation (6400′), surrounded by mountainous terrain, so we spent more time than usual briefing the arrival and approach. The weather was officially VFR, but it wasn’t exactly clear. As we approached the initial approach fix, we were in and out of layers.
We were also flying an approach that we had thoroughly briefed, so we had a pretty good idea of what the airplane should be doing and when. Then the needles went green transferring the nav input source from FMS to LOC. The autopilot had captured the approach and began an unexpected turn toward the final approach course which wasn’t what we were expecting at that point in the procedure.
We didn’t spend much time trying to figure out why. We disconnected the automation and went back to hand-flying. With two pilots in the cockpit and a thoroughly briefed approach, we were able to quickly get the airplane back where we wanted it, reestablish the automation, and continue the approach. It wasn’t a dramatic event, but it was a good reminder of several fundamentals that can get overlooked when we’re accustomed to letting the automation do the flying.
The Automation Wasn’t the Problem
Tim Decker recently wrote about the importance of cross-checking automation and offered three simple rules for doing it. Those rules came to mind as I thought about what happened at Jackson Hole. The important event to recognize was that the airplane was doing something we didn’t expect.
Modern avionics are very good at following instructions, but they don’t know what you intended unless you’ve given them the right instructions—and even when everything is programmed correctly, the airplane can sometimes behave differently than you anticipated. That’s why an instrument pilot can’t simply monitor whether the autopilot is engaged or whether the appropriate annunciation is displayed. You have to monitor the resulting flight path.
Where is the airplane?
Where is it going?
What should it be doing next?
And does what you’re seeing match what you expected? At Jackson Hole, the answer was no. We caught it quickly because we were looking.
Fly First, Troubleshoot Later
Fly First, Troubleshoot Later
When an automated system does something unexpected, it’s natural to want to understand why. Which mode is active? Did we miss something in the set-up? Why did it capture? Those are all reasonable questions, but they don’t necessarily need to be answered immediately.
The immediate question is whether the airplane doing what I need it to do? If the answer is no, disconnecting the automation may be the quickest way to eliminate uncertainty and get back to the fundamentals. Fly the airplane first and then figure out what happened.
That doesn’t mean every unexpected automation event requires immediately turning everything off. It means the pilot needs to remain comfortable enough with the airplane to recognize when automation is no longer helping and to take control by any means available without hesitation.
Are You Ready to Hand-Fly?
That’s where instrument proficiency comes in. There’s a difference between practicing hand-flying and being ready to hand-fly. You don’t need to turn off the autopilot on every IFR flight just to prove that you can fly an approach. Automation is one of the great tools available to an instrument pilot, and using it appropriately can reduce workload and increase safety.
But if the autopilot suddenly disconnects—or you disconnect it because the airplane isn’t doing what you expect—you shouldn’t suddenly feel like you’ve lost your primary flight-control system. The basic skills still need to be there.
Can you maintain heading and altitude?
Can you control the airspeed without chasing it?
Can you intercept and track a course?
Can you configure the airplane for landing while maintaining control?
Can you fly the approach while also thinking about what comes next?
Those aren’t skills that should disappear just because the airplane has an autopilot. But like any skill, they can get rusty if they’re rarely used.
The Briefing Was a Big Part of the Solution
One of the things that helped us at Jackson Hole happened before we ever got to the approach was that we had briefed it carefully. That wasn’t just about checking the minimums or reviewing the missed approach (although we did that too). We talked through the procedure and the environment because this was an airport we don’t fly into regularly, at high elevation, in mountainous terrain and with conditions that weren’t as straightforward as the VFR designation might suggest.
That preparation made the surprise much easier to recognize. And that’s an important part of instrument flying. You can’t recognize that something is unexpected unless you have some idea of what you expected in the first place. A good approach briefing creates that mental picture.
Use All the Resources You Have
I also had another advantage that day: another pilot in the cockpit. Crew resource management is a major part of professional flying, and having a second set of eyes makes it easier to monitor the airplane, the automation and the approach at the same time, but the underlying discipline applies to single-pilot flying, too.
Brief the approach out loud. Think about what the airplane should do at each major point. Know what the important modes and transitions should look like. And when something doesn’t make sense, don’t simply assume the airplane must be right.
Automation is an incredible tool. Use it. Trust it when appropriate. But keep your instrument skills sharp enough that you’re ready for the moment when you have to take back the airplane.
New IFR Mastery: No Easy Way North
/by Eric RadtkeWhat would you do if weather, darkness, and geography left you with several imperfect choices for an IFR flight?
That’s the dilemma in this month’s IFR Mastery scenario from PilotWorkshops. You’re flying your Cirrus from Buffalo to Iron Mountain, Michigan and the easy route is anything but easy.
The shortest IFR option takes you north across Michigan and then over Lake Michigan, including about 50 miles of overwater IMC. The alternative around Chicago adds nearly 100 miles and pushes your arrival toward sunset. You could also try filing directly through Chicago’s Class B, or fly VFR along the Chicago shoreline and pick up an IFR clearance farther north.
Each option has its own set of risks, complications, and unknowns.
Which route would you choose?
Watch the scenario below and make your decision.
It’s more than picking the shortest route
Instrument flying often means choosing between imperfect options. Weather, terrain, airspace, daylight, fuel, and workload can all change the risk profile and sometimes the route that looks best on paper isn’t the one that makes the most sense in the air.
That’s the decision-making skills that IFR Mastery is designed to develop. Each month, PilotWorkshops presents a new real-world IFR scenario that puts you in the pilot’s seat. You’ll evaluate the situation, make your decision, and then compare your thinking with experienced instructors as they explain the factors that influenced their choices.
Think you’ve made the right call?
Watch the free scenario briefing above, then sign in or start a free 30-day trial to access the complete scenario, instructor analysis, and the complete library of nearly 200 IFR scenarios.