Vector4fun
Well-known member
- Joined
- Jul 25, 2003
- Posts
- 796
NJA Capt said:This is where a nationwide standardization policy would help out. Approach controllers work "their" area, while we are flying into 500 areas. Each controller wants it done the "local way." If you come into the NYC area and slow below 240 kts you get yelled at. Then you go to CLE or IAD and they think people are still flying DC-3s (170 kts???) You enter NYC airspace at +/-2000 AGL. At places like MCO and ATL they vector a downwind at >9000 MSL and give a 20 mile final in VMC.
I understand all of the above, and you have a point. It's the really egregious examples that get me. The guys who come sailing onto a midfield downwind at 10,000' and 300 kts gs, (when they were assigned 3000' 20 miles back), at a measely 1500 fpm descent, and then start chippin for the visual. "We got the field in sight" Yeah, I heard you the first time, and when you get that puppy down to about 4000' and slowed up to about 210 kts, and I know approximately what county you're going to be able to turn base leg in, I'll figure out who you're gonna follow.
The other problem I have is, since we don't exclude many of the GA overflights, I've got them from 6000' to 12,000, and also piston and turboprop arrivals to neighboring facilities descending through parts of my airspace. It helps if I can hustle you down through all that. The longer you're above around 6000', the longer you're a potential conflict with all that traffic not even landing at this airport. You're a conflict with the overs and the departures climbing and crossing. It would be nice to segregate all that traffic, but we can't do that without a lot more airspace.