VATUSA Forums
Login
  1. VATUSA
  2. VATUSA Forums
  3. Profile of Tim Roden
  4. Show Posts
  5. Messages

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Tim Roden

Pages: [1]
1
The Classroom (Controller Tips) / Controlling the Arrivals
« on: March 14, 2012, 11:11:11 AM »
5-6-1 a.  In controlled airspace for separation, safety, noise abatement, operational advantage, confidence maneuver or when a pilot requests.  Allow aircraft operating on an RNAV route to remain on their own navigation to the extent possible.

That said I watched an LA controller last night take a pilot of a STAR in a very dangerous area.  When you take the responsibility of vectoring a pilot, then you take the responsibility to making sure he gets to his destination.  By allowing the pilot to fly the star he gets there via the route which he spent so much time meticulously planning into his FMC.  Giving direct FIX is not a problem when it comes to flying over an airspace.   I'll take the shortcut.  But when my RNAV arrival leads me directly to the IAF, and you give me a vector you then have to give me a vector to join the approach and many controllers are missing that.  In the Case of LA. There are mountains that you have to navigate through and around to reach airports  you start vectoring and the next thing you know, you vector someone into a mountain.  Of course as a pilot, I have to right to say "unable" to any direction given by ATC.  The final decision for safety is in the hands of the pilot.

2
The Classroom (Controller Tips) / Controlling the Arrivals
« on: February 28, 2012, 06:44:24 PM »
Where I have the problem is RNAV arrivals.  I have more and more controllers who want to give me a vector instead of having me fly the arrival as published that would would take me straight into the approach.  The 7110.65 says that you are not to take someone off of an RNAV until the last minute.  There is a list of reasons why you don't do it including traffic, noise etc.  Controllers need to read the arrivals before they are certified on approach.  They need to allow pilots to fly as published unless there is an problem such as traffic.  

Example.   Flying into Fort Lauderdale.  Jingle1 RNAV arrival.  Approach consistently gives me a 090 heading off of JINGLE for 9L.  You don't have to give any vectors cause the arrival brings you direct to HOLID from JEREM which is the inital fix on the 9L ILS.   All you have to do is tell the pilot which runway and what the altitude to fly.  If the pilot doesn't fly it then he can be given vectors.  

Any Arrival, you should not take them off until at least the crossing point.  I have not seen that problem anywhere in VATSIM.

Pages: [1]