I’m a former professional pilot.
IRL, you’re under ATC control from origin to destination where you receive a series of handoff’s between controllers from begining to end. Additionally, there is clearance delivery which provides you with an IFR clearance.
As you go through handoff’s between controllers, you’re under positive control - this includes both speeds and altitudes - with IF, pilot speeds are all over the place. I regularly see pilots at the same altitude, on the same flight plan (i.e. group flights) doing anywhere between Mach .76 and Mach .90.
As much as it pains for me to say this, as an IFATC controller, many of the flight plans I see are severely deficient, incomplete, and/or contain bad data such as waypoint crossing altitudes. In addition to altitudes, STARs also have speed restrictions; pilots are required to adhere to crossing altitudes and speed restrictions, unless advised otherwise by ATC. This would require pilots to not only obtain arrival and approach charts, but be able to read, understand, and follow them.
As much as I’d love to see this, I’d say it’s asking a bit much.
Flight plans must follow established procedures with correct speeds and altitudes to work.
Similar to Arrival (STARs) and Approach procedures, Departure Procedures (DP’s) have published waypoint crossing altitudes and speeds. Altitudes must not only be correct, but pilots need to follow them, including on departure. Published altitudes are designed to keep departures from conflicting with arrivals. Pilots have skin in this game too.
Many ES pilots have no knowledge or interest in following airport departure procedures. At JFK, as an example, less than 5% pilots (I’m being very generous here) actually fly a valid departure procedure. When I have the JFK departure frequency open and attempt to vector pilots onto a valid departure procedure:
- Some pilots UNABLE the instructions,
- Many leave LNAV engaged and ignore them,
- Some attempt to follow, but are so slow in complying that it becomes pointless.
- A small percentage promptly follow the instructions or attempt to, to the best of their ability.
This is on top of all the requests I get for Flight Following or Radar Vectors, which are VFR services. I can’t report every pilot who fails to follow vector instructions onto a departure procedure, it’s simply too many.
When traffic volume exceeds an airport’s arrival rate, you can’t just tell pilots to continue as filed in constrained airspace with severely deficient, incomplete or incorrect flight plans – you’ll have a collasal mess with pilots everywhere. IRL, when airports/airspace become constrained (with pilots following valid IFR cleared flight plans), an approach facility will contact the appropriate center to request 10 or 15 miles in trail (MIT) separation between arrivals on a specific STAR. Center then slows traffic and makes further requests downstream.
If demand is too high, a ground stop or ground delay program is initiated, delaying departures on the ground to the constrained airport.
I control airports and airspace I’m familiar with, but as a former professional pilot, there’s also a lot of airports and airspace I know inside out – at a level I would not expect other controllers to know.
On a final (gasp), closing remark, in the same way you suggest controllers should take time to get familiarized with airports, how about asking pilots do the same? As said above, I think that’s a bit much to ask, but it would go a long way – important thing is finding the balance.