I have no idea what a stabilized approach is supposed to be
The airlines have a program called FOQA, it stands for flight operations quality assurance. Data from flight data recorders is evaluated to see how much deviation there is from what has been established as standard procedures and situations or published procedures that create high levels of deviations are analyzed to figure out why they are problematic. We used to be able to do just about anything with the planes and if there wasn't an incident, we were good. I won't/can't type examples!
Something that came from the analysis of this data, over the years since the program was started, is that when a pilot makes an approach that is well planned and well executed so as to be "stable" by a certain point on the approach, the landing is usually uneventful; on speed and in or near the touchdown zone. When you are exposed to this training and the data that supports it, it is
!!!CRAZY!!! to see just what some approaches look like and what happens over the runway as the pilots attempt to land.
Where I work we try to be at certain configurations and airspeeds by certain altitude "gates" above the ground and if we aren't fully configured and on speed by 500 ft, we call "unstable, going around". Where go-arounds used to be considered a non-normal event that required a report to be filed, we now view them as a part of operating large airplanes into busy airports. The stigma surrounding go-arounds as a failure has been removed so pilots won't feel pressured to continue bad approaches. Today's airline pilots are much more aware that perfect doesn't exist and that being able to recognize deviations from standard and call them out in real time is part of the job.
When it comes to general aviation, haven't you ever noticed that when you've nailed a stable continuous descent to the runway the landing just seems to fall into place on its own? How many of you carry power to a certain point and then pull it to idle for the last few hundred feet when the runway is made? I guess "stable" for GA might be to have airspeed stabilized by a certain altitude above the runway and to then try to fly the final glide path without large changes in pitch or power to the touchdown point and to land within a certain distance from what you have been shooting for. For us we aim to land within 3000' of the touchdown zone (the fixed distance markers on an instrument marked runway) or the first third of the runway, whichever is less, and are technically required to go around if we miss it. Watching computer re-creations of bad landings with transport category airplanes is gut wrenching, at least for me it is!! You should see me squirm!
So the idea of a "stable" approach has been a very successful story with the airlines and, like a lot of things, it's percolated down to corporate flight departments and now the FAA is trying to put it into the conversation with general aviation pilots.
You're probably reading this and laughing that it's overkill for GA. Hot dogging a taildragger to the runway with all of that rudder and no flaps is fun! Right? I think it is! But what's best for a student? Or for an instrument rated pilot who regularly flies to instrument procedure minimums in more stressful conditions? Isn't it reasonable to discuss what is optimum for even us each time we fly? There are things that might be fun to do but we shouldn't necessarily accept the need to do them in each and every approach. We should be able to recognize when we're out of our own safety zones and recognize that a good go-around is a better decision than a bad landing and that
a good landing begins earlier than the flare. Maybe the FAA will come up with standards that could be applied in some reasonable way to GA planes, maybe just having this conversation will encourage a few of you to think about how good landings and well executed approaches to the runway seem to go hand in hand. We should certainly be having this conversation with students so that it's baked into their pilot mindset from the beginning.
Sorry for the thread drift
@BrianW !!!


