I’m seeing a lot of blind 1000 feet turnback briefings too. I guess the assumption is that we have lots of choices at pattern altitude. When giving instruction, when I hear this, I’ve begun to ask, “how do you know 1000’ will work?”
Generally, we don't. It's just an easy rule of thumb. There are a LOT of variables:
Aircraft climb performance vs. glide performance - And even on the same airplane, this will be affected by variables like DA.
Headwind
Crosswind
I’ve had the scenario with a strong headwind and very low cold DA, turning crosswind by the end of the runway. If I have a complete fail there, I don’t know how one would maneuver for an impossible turn at that point, considering a short runway.
Exactly. The "Wow" moment in Mark's video above shows that. If you have a strong headwind and you can crank the plane around fast enough, you may end up overshooting if you try to land back on the departure runway. It's not out of the realm of possibility to have a strong enough headwind that it's best to make a full pattern by the time you get to 1000' AGL.
As far as the variables above, a plane that climbs really well (speaking of angle here, not just rate) should be able to turn back sooner than one that climbs at a lower angle. Same for a plane that glides really well. The more headwind you have, the sooner you can turn back since you won't have gone as far from the runway and you'll have a tailwind when you get turned around. The more crosswind you have, the less of a turn you need to make - Assuming you turn into the wind, you may be able to make only a 180 and have the wind blow you back to the runway centerline.
One other thing to note: If you're flying a glass panel - Anything that has the Flight Path Marker - You have a GREAT reference for where to point the plane. Generally speaking, with a decent crosswind you will NOT want to point your nose at the runway, as you'll fly a curved path to it due to the crosswind. If you put the FPM right on the runway threshold, you'll fly straight there, which is a slightly shorter path. In addition, if you put the FPM on the threshold and you're maintaining speed, you'll make it to the runway, whereas if you put the FPM on the threshold and you're slowing down, you're going to come up short. Knowing that so far in advance is incredibly useful and lets you come up with a new plan while you still have other options. "Bad news early is good news."
Recently, I decided to play with this a bit…
Cool! I'm a fan of doing some of your own test piloting.
I'm curious how much an idling engine affects things on various aircraft. I know that when we were doing the initial testing of the glide ring in ForeFlight, I pulled my engine to idle when I was at about 10,000 feet and the glide ring hit the airport. I ended up putting my gear out at 6,000 feet and flying a complete traffic pattern because of how high I ended up. I'm sure that my plane isn't THAT much better than the book when the fan is really off!
I really would like to do some actual engine out testing somewhere with a huge runway surrounded by lots of fields and no people. Take it up to 14,000 repeatedly. Test out things like whether it's better to hold altitude until Vg or pull up to bleed the speed off quicker and get a little extra altitude out of it, effect of prop and throttle levers on actual glide performance, effect of windmilling prop, glide ratio in various configurations to determine when it's safe to add flaps and gear, etc... But I'm not going to bother doing this until I've got the right avionics to log EVERYTHING (including engine data, which my plane currently logs separately).
In addition, some testing related to the impossible turn would be informative with some math to start out. First, calculate the theoretical amounts of time to turn 180 degrees and maybe every 10 degrees after that up to 220, the stall speeds and turn radii at different angles of bank, and how much time it really takes to roll in and out of those turns. Then, go up and see whether performance matches expectations, and finally figure out how the variables above affect it all. Maybe even put together a spreadsheet where you could input wind speed and direction, runway heading, and maybe runway performance as calculated in ForeFlight. Then, calculate when it's best to stop on the runway, when you'll need to keep going ahead, what altitude is the minimum for the impossible turn, and the optimum bank angle and rollout heading to achieve the best performance on the turnback.
Yes, I'm a nerd.
ultimately, this is the best we can do. And to remember that the “best” place to put down may not be av”good” place to put down,
Sticking to your guns when the best option is non-ideal is difficult. Gotta be Sully and put it in the river anyway.