FLYING LESSONS Weekly

FLYING LESSONS for January 18, 2024

Download this report in a pdf.

FLYING LESSONS uses recent mishap reports to consider what might have contributed to accidents, so you can make better decisions if you face similar circumstances.  In most cases design characteristics of a specific airplane have little direct bearing on the possible causes of aircraft accidents—but knowing how your airplane’s systems respond can make the difference in your success as the scenario unfolds. So apply these FLYING LESSONS to the specific airplane you fly.  Verify all technical information before applying it to your aircraft or operation, with manufacturers’ data and recommendations taking precedence.  You are pilot in command and are ultimately responsible for the decisions you make.

©2024 Mastery Flight Training, Inc. 

     

This week’s LESSONS:

We’ll go straight this week to your insightful inputs and my hopefully equally useful responses in this week’s Debrief.

Questions? Comments? Supportable opinions? Let us know at [email protected]

Debrief 

Readers write about recent FLYING LESSONS:

Reader and new monthly donor Johannes Ascherl writes:

That’s a great way to avoid complacency and expectation bias on the part of the controller as well as the pilots. Thank you, Hannes. Best regards from the very cold U.S. as well.

Reader Martin Sacks adds:

That’s an outstanding point, Martin. Leave cell phones turned on and active; put them in silent mode to avoid distraction as much as possible, and keep them in a zippered pocket or otherwise in a place they might not be thrown out of reach if you’re still in the seat and cannot extricate yourself after a crash. Any other recommendations? 

Reader Ed Stack addressed the “door pop” that was the impetus for last week’s LESSONS on estimating the amount of runway remaining if you elect or need to land immediately after takeoff:

FLYING LESSONS is independent of my work at ABS, and Beech owners represent a minority of FLYING LESSONS readers. So the LESSON here is to seek out the resources and experts available to the type of aircraft you fly, and learn from their experiences before you experience something for the first time yourself…as you did, Ed. Thank you.

Reader Art Utay continues:

I suspect the position of her arm and most likely the pattern of impact injuries on her body are what suggest, but do not confirm, that she was trying to secure the door when the airplane hit terrain. Open doors and other distractions sometimes tempt us to take heroic measures to deal with the problem, when they really should cause us to focus our efforts on flying the airplane. Thank you, Art.

Reader and new donor this week Jerry Magnoni relates his experience:

I consider a door (or window) that’s ajar in a manner that does not materially degrade airplane performance to be an abnormal condition not requiring priority handling to get me on the ground before anyone else. So I would not declare an emergency but simply tell controllers what I need (at a tower-controlled airport) and make a normal landing (or approach and landing if conditions require).

Exceptions would be if I was having any difficulty with airplane control (for example, a side window opened, ripped off in the slipstream and hit the tail on its way) or if I had a seriously panicked passenger I couldn’t get calmed down. So there’s the possibility I might declare an emergency if the situation warrants, but in general I’d not. Thanks, Jerry. 

Reader Stanley Stewart offers another takeoff distraction experience:

I do the same thing with the seat belt in unoccupied seats adjacent to doors. I’ve heard that flapping noise myself. 

Another belt-related distraction happened on my first solo flight, in a U.S. Air Force T-41A (1965 Cessna 172). My instructor had me taxi to the RSU (Runway Supervisory Unit), a non-tower observation station between the runways at Hondo, Texas where the USAF Flight Screening Program was then based. Without us shutting down the engine (!) he took off his headset and unfastened his four-point harness, climbed out of the airplane, then leaned back to tell me to make three touch and go landings. He fastened the right-seat belt and harness and tucked his (pre-noise canceling) headset under the lap belt, then slammed the door shut. I made the proper advisory calls using my callsign (“Stomp,” indicating I was using the west runway, as opposed to “Hang” used by east runway traffic—it’s funny what you remember) and the last two digits of the airplane registration to warn everyone I was doing this alone, then taxied. 

About the time I lifted off, the instructor’s headset shifted just right so wind whistling through the right-side “soup can” wing root air vent blew directly on its microphone sticking up from behind the khaki lap belt. It was extremely distracting and prevented me from hearing anything from the RSU or three or four other T-41s in the circuit. Focusing on continuing to fly the airplane as my Flight Screening Program instructor Joe Oswalt had always emphasized, I reached over and pulled his headset jacks out of the panel, making the noise stop. Good thing I did; after my first crash-and-go while I was downwind for the second time with three or four others in the same pattern, the RSU changed the pattern from landing south to landing north. We had a trained procedure for flying a box pattern to reverse direction at whatever point in the pattern we were at for a runway change, and I did that before my second landing. But I never would have heard the command had I not removed the distraction. Thanks for relating your experience also, Stanley.

Reader/instructor Mike Friel delved deeper into last week’s LESSON, which began with a door opening in flight but which was really about initial climb and determining how much runway remaining in actually usable as you climb:

I was referring to the performance charts and how to determine you have sufficient runway remaining in the first place. But you’re right, I should make this distinction. Thanks, Mike.

Mike replied:

You, too, are correct about performance charts and other recommendations in the handbook: the takeoff performance chart “associated conditions” are required if you hope to get something close to calculated performance, there is a certain marketing value in performance charts in that they present the “best” performance under given conditions, in the case of takeoff and landing performance being short field techniques; and other suggestions may include techniques that will result in some other performance not calculable using handbook data. Recall that only Section II, Limitations, of a Pilot’s Operating Handbook (POH) or Airplane Flight Manual (AFM) is “approved” by the FAA and therefore is required to be observed. The remainder of the handbook is the manufacturer’s best recommendations as to how to fly the airplane, but you’re free to use any technique you like as long as you do not violate Limitations. It’s up to you to predict how the airplane will perform, and to give yourself enough of a margin to fly safely. 

As to your final paragraph, Mike, thank you. I’d like to think I’m doing some good. The same may be say for a lot of other people, including you. Thanks for your insights into performance.

And from reader and well-known Australian flight instructor Edgar Bassingthwaighte:

There are a few things I normally do that are not strictly by the book. I smoothly apply power and let the airplane roll for takeoff, then establish a Vattitude for initial climb and accelerate to a faster-than-book cruise climb. For landing I fly at “book” final approach speed but don’t establish the Beech handbook’s 900 foot per minute rate of descent passing through 50 feet above ground on final approach. And I don’t apply maximum braking during the landing roll.

But, I add a minimum 100% margin above charted takeoff and landing performance. If I don’t have that buffer I’ll either land somewhere else or, if I have at least a 50% margin, I then use the book procedures. And I practice them often enough I can do it correctly when I’ve decided.

Thank you, Edgar. I’ll see you at Cowra in March. 

Reader Mark Sletten comments on “clearance confusion” as discussed in last week’s Debrief:

Excellent point, Mark. Thanks for the emphasis. Air Traffic Controllers provide essential information, aid and services. But the pilot-in-command is responsible for the safe outcome of each flight.

Instructor and frequent Debriefer Brian Sagi brings this week’s Debrief to a stop with his observations on an under-taught aspect of takeoff aborts:

That is indeed an under-taught and under-practiced skill, Brian. I need to practice it more myself. Thanks!

More to say? Let us learn from you, at m[email protected]

Share safer skies. Forward FLYING LESSONS to a friend

Please help cover the ongoing costs of providing FLYING LESSONS through this

secure PayPal donations link. Or send a check made out to Mastery Flight Training, Inc. at 247 Tiffany Street, Rose Hill, Kansas USA 67133.

Thank you, generous supporters.  

Thank you to our regular monthly financial contributors:

Johannes Ascherl, Munich, Germany. Bruce Dickerson, Asheville, NC.

And thanks to these donors for helping with the Mastery Flight Training website rebuild and FLW costs in 2023:

2024 Donors


Thomas P. Turner, M.S. Aviation Safety 

Flight Instructor Hall of Fame Inductee

2021 Jack Eggspuehler Service Award winner

2010 National FAA Safety Team Representative of the Year 

2008 FAA Central Region CFI of the Year

FLYING LESSONS is ©2024 Mastery Flight Training, Inc.  For more information see www.thomaspturner.com. For reprint permission or other questions contact [email protected].  

Disclaimer

FLYING LESSONS uses recent mishap reports to consider what might have contributed to accidents, so you can make better decisions if you face similar circumstances. In most cases design characteristics of a specific airplane have little direct bearing on the possible causes of aircraft accidents—but knowing how your airplane’s systems respond can make the difference in your success as the scenario unfolds. Apply these FLYING LESSONS to the specific airplane you fly.

Verify all technical information before applying it to your aircraft or operation, with manufacturers’ data and recommendations taking precedence. You are pilot in command, and are ultimately responsible for the decisions you make.