Final Approach Speed

RobertB said:
Just wait until Wake RECAT starts and guys start complaining about being 2.5 MIT with a heavy behind a heavy whether they see them or not...
Click to expand...
That's going to be huge for the early morning DHL push out of CVG off 27.
 
RobertB said:
"We'll reduce to our final approach speed, like the guy in front of us and probably the the guy behind us as well, because you turned us too tight on our traffic." Again, 2.5 MIT was resulting in 1.5-2.0 as the preceding aircraft was crossing the threshold so they had to be tight to see each other, hit gaps off the middle final (on ILS approaches), etc. The separation would've been the same had they gone out for ILS PRMs with a monitor plugged in and the tower seeing them at the FAF...
Click to expand...
I would have spun him a few times for that. Dick.
 
GypsyPilot said:
If that's the case, he's also bad at math!

Here's a rough example... Let's say you're 10 nm out. The difference between 120 kts vs 200 kts is exactly 2 minutes. Realistically, it's going to be more like a minute or less by the time they get slowed up for flaps, stabilized at 1,000 ft, etc.

Every time I'm next to a guy freaking out about being slowed down a little, I wonder if they flunked high school algebra.
Click to expand...

So I guess you've never gotten to a gate just seconds after they closed the door or pulled the jetway? Every second counts for someone trying to catch a flight. I don't commute and I understand that.
 
Last edited:
Rocketman99 said:
So I guess you've never gotten to a gate just seconds after they closed the door or pulled the jetway? Every second counts for someone trying to catch a flight. I don't commute and I understand that.
Click to expand...

Yes, add a bunch of stress to a flight for your commute, just to save a few secs. Pretty selfish.
 
I've never gotten a complaint for being as early as possible on the last leg, from my pax or FOs. Believe what you want. Either way I'm done discussing it.
 
In a prop (turbo or otherwise) 1000' or once on final (for a pattern) and I will probably be as fast as possible prior to that. In the T38, once on final or at the FAF. Could we go faster? Hell yeah, but we are already going faster than anything we are trying to mix in with that it is pointless. Radar vectors are at 300kts and we slow to ~165-180 once at the FAF. With the exception of Fort Worth, controllers seem to have a hard time not overshooting the turn onto the localizer.
 
flyboy6585 said:
In a prop (turbo or otherwise) 1000' or once on final (for a pattern) and I will probably be as fast as possible prior to that. In the T38, once on final or at the FAF. Could we go faster? Hell yeah, but we are already going faster than anything we are trying to mix in with that it is pointless. Radar vectors are at 300kts and we slow to ~165-180 once at the FAF. With the exception of Fort Worth, controllers seem to have a hard time not overshooting the turn onto the localizer.
Click to expand...

You do much flying around Corpus? If so, how do you like it and how are the controllers?
 
They're awful. Just awful.

I'm kidding. Sort of.

flyboy6585 said:
In a prop (turbo or otherwise) 1000' or once on final (for a pattern) and I will probably be as fast as possible prior to that. In the T38, once on final or at the FAF. Could we go faster? Hell yeah, but we are already going faster than anything we are trying to mix in with that it is pointless. Radar vectors are at 300kts and we slow to ~165-180 once at the FAF. With the exception of Fort Worth, controllers seem to have a hard time not overshooting the turn onto the localizer.
Click to expand...

Yeah, standard rate turns at 340kts ground speed tend to swing you guys through a zip code or two. The standard 4-5 mile radar downwind just doesn't work. Even 1 turn to final at that distance causes you to go through the localizer.
 
You must log in or register to reply here.
Back
Top