Update/Rearrange 172S GAIT IAP values - #323
Conversation
|
Oh cool, I really like how you’ve broken it up. And nice timing, I had just been reflecting on this table after working with a client on a Saratoga checkout. They had a pretty different framing for each of the rows, I think a little closer to what you’re suggesting. I’ll ask him for a copy of it and we can put our heads together on a best version. The original idea was more prescriptive, essentially that on an approach you pass a series of configuration changes. The gait chart would then help you remember both the timing of the configuration change, and what that new configuration was. But in practice, I end up mentally mapping it to something more like what you have. I think decoupling it from a particular view on when to make configuration changes would be much better, especially as I’ve been flying faster planes were you typically wouldn’t change to a dirty configuration until much later on the approach. There’s also a template gait chart, which would be great to update as the baseline once we like the rows. |
|
|
||
| | Topic | Details | | ||
| | ------------- |:---------------------------------------------------------- | | ||
| | [[CDFA]] | [[AC 120-108]] | |
There was a problem hiding this comment.
I think better to leave this off. Typically I have people add this to their new board, either as a printout or digital, so trying to keep it to just quick reference things
|
The color coding is super helpful...narrows in on phase-of-flight immediately. I don't have strong opinions about the "right" way to do it, but it sounds like you're configured for the entire approach whereas I'm getting training from someone who puts flaps in 2 miles from the FAF, which means flying "cruise-slow" on the approach course and after one descent is done. Anyways, see you soon! |

Give me a sanity-check on the IAP organization and values.
I was looking for numbers for my own in-flight guide and came to this page. I thought the IAP labels were too prescriptive (I might use the dirty-0FPM row at the MDA or while driving to ZOTPI) but then I created a whole prescriptive system of my own...and now I'm doubting myself. I'll measure the actual values on Thursday but I'd love your thoughts.
The "dive" rows (both on the main branch and this branch) have the dirty configuration taking less power (1500) than the clean dive (1700) while holding the same KIAS and FPM, which seems fishy.