vZBW ARTCC
August 22, 2014, 12:08:18 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Our goal is to maintain, and grow, Boston's fine tradition of excellence. 
 
    Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: RNAV DP Discussion, Tips and Tricks  (Read 5394 times)
0 Members and 1 Guest are viewing this topic.
DO
Division Director, VATUSA
Administrator
*****
OfflineOffline

Posts: 4424



« on: August 06, 2011, 11:57:12 AM »

A pilot had asked several questions about RNAV DPs on the VATUSA forums, and I offered the following reply to the thread.  I'm reproducing it here in the hopes that it helps.

Quote
Q: Ok - flying RNAV DPs is the only way to proceed with departure without radar vectors (most of the time) correct?
A: affirm depending on the RNAV some start literally the second your in the air others they will give you vectors to the first fix before telling you to fly the what ever you have filed
Q: Do I get to choose which departure procedure I want to do, or is that something that is sort of randomly assigned by ATC?

The point behind the RNAV DPs is that you are using them the second you are in the air; no vectors required.  ATC assigns the DPs.  However, there are a few things you can do to pretty much guarantee that you'll get the RNAV DP that you want....

1. File a real world, really assigned ATC routing.  A great place to find these is fltplan.com 
2. Decide that whatever is done in the RW is what you want to fly Smiley
3. File the RNAV DP fix in the title, or if you have options, the transition that you want as your first fix

For example, Boston just added 8 new RNAV DPs in the past 9 months.  It used to be that if you wanted to fly KBOS-JFK, you would normally file:
LUCOS SEY PARCH CCC ROBER

ATC would normally assign the LOGANx (where x is the current number, e.g. LOGAN6) Departure, which is a radar vector DP.  Assuming you filed the above, your clearance would normally sound like:
"American 123, cleared to Kennedy via the LOGAN6 departure, radar vectors LUCOS, then as filed.  Maintain 5000, expect FLxxx 10 minutes after departure...." 

So even though you wouldn't file LOGAN6, ATC would assign it.

But life has changed. One of the 8 new DPs at Boston is the SSOXS DP (currently the SSOXS2).  AND, Boston now uses RNAV DPs as a standard/default.

So, nowadays you'd file:
SSOXS LUCOS SEY PARCH CCC ROBER (note you're just filing the fix, not SSOXS2)

Your clearance would normally sound like:
"American 123, cleared to Kennedy via the SSOXS2 RNAV Departure, LUCOS transition, then as filed.  Expect FLxxx 10 minutes after departure...." 

So again, even though you wouldn't file SSOXS2, ATC would assign it.


Also note that in the first example, your clearance specifically told you to expect 5000 initially, but the second clearance did not state that.  That's because, in most RNAV DPs, the initial altitude to maintain is written right into the DP.


Other example.  Nowadays, for airports that now use RNAV DPs as a standard, even pilots who file an "old" route but indicate that they are advanced navigation capable (GPS, RNAV, INS, etc.) will likely receive an RNAV DP in their clearance.

For example, JOE123 files KBOS-KJFK with a route of LUCOS SEY PARCH CCC ROBER and is flying a H/B744/G.  Guess what.  His clearance will be via the SSOXS2 RNAV Departure, LUCOS transition, then as filed.

These RNAV DPs are springing up across the country fast and furious.  Since many pilots are still using default aircraft and/or GPSs with default navigation fixes, it's entirely possible that many pilots may not be able to navigate to all the new fixes on all these new RNAV DPs.  The FAA recommends that pilots who cannot, or do not wish to, fly STARs and/or DPs file "No DP/STAR" in their flight plan.  My suggestion for pilots who cannot, or do not wish to, fly RNAV DPs is to include "No RNAV DPs" in their flight plan, or at least verbally tell the clearance delivery controller that they do not wish an RNAV DP.  This practice would greatly aid the controller who is trying to figure out quickly and efficiently which DP to assign.  Because if you don't, here's what could happen (happens every day at KBOS nowadays....):

1. Pilot files KBOS-KJFK with a route of LUCOS SEY PARCH CCC ROBER and is flying a H/B744/G. 
2. Pilot is cleared via the SSOXS2 RNAV Departure, LUCOS transition, then as filed.
3. Pilot reads back his clearance (and therefore accepts the RNAV DP!!!)
[some intermediate steps omitted for brevity]
4. Pilot takes off and heads straight out, or turns directly toward LUCOS, or does some other wacky thing....
5. Controller asks AAL123 where he's going
6. Pilot says, "Straight out" or "Direct LUCOS" or "The controller never gave me a heading" or "Gee, I dunno...."
7. Controller gently reminds pilot that he was cleared for the RNAV DP and therefore should be following it
8. Pilot complains loudly that he can't fly the RNAV DP and the controller screwed up by giving it to him....
Yadda yadda yadda


A fellow VATSIM pilot, Graham Mitchell, has graciously developed and shared with the community updates for the default MSFS GPS.  These can be found on his website: https://www.btinternet.com/~gb.mitch/index.html  A discussion can be found on the VATSIM forums: https://forums.vatsim.net/viewtopic.php?f=28&t=30992  With these updates, it is possible to fly the RNAV DPs (and STARs as well) by using the GPS.  It's a bit of plugging in direct-to waypoints fast and furious right after takeoff, but it can certainly be done. 


We're all in this together, and we all want to have a good time.  Situations like the above are frustrating for everyone.  That said, hopefully the explanation and tips and tricks provided here help a little bit!
« Last Edit: February 09, 2012, 01:00:55 AM by DO » Logged

Don Desfosse
Division Director, VATUSA
ATM Emeritus, Boston ARTCC
GT
Mentor
vZBW Controller+
**
OfflineOffline

Posts: 199


« Reply #1 on: August 06, 2011, 03:54:47 PM »

Thanks for the excellent explanation, DO. I always file the RNAV when it's available - however, departing from Boston, it appears that the pilot is not always required to fly the entire RNAV procedure. The controller often issues "proceed direct LUCOS" before or after reaching the first RNAV waypoint. That's fine with me because the faster I can get a more direct route to my destination, the faster I can reach that destination. Regardless, it's important that the pilot program the entire RNAV procedure in the FMS when issued. If traffic's heavy, the controller may be too busy to issue a shortcut so the next best thing is to fly the procedure as published.

Most RNAV departures I've encountered at ARTCCs other than Boston are adhered to. When a good Center controller gets a hold of you while still flying the RNAV departure, a "cleared direct to" some waypoint is often issued to expedite the departure.

There's some confusion for me about which RNAV procedure to file when departing Boston to a particular destination. For example, if GLYDE is in your manifest, and you're heading to Atlanta, which RNAV departure makes most sense? Or MHT, PSM, BOSOX, etc.?

With a mix of sophisticated and not so sophisticated pilots, the challenge is to remain patient while attempting not to neglect the pilot who knows how to fly RNAV while being consumed by one that doesn't.

The simple answer is to file as you suggested to avoid the confusion later.
Logged

Jack Gilbert
FR
vZBW Controller
*
OfflineOffline

Posts: 189

Boston +11 hrs in VFR paradise


WWW
« Reply #2 on: August 09, 2011, 10:39:52 PM »

Thanks for the info Don
Logged



Stephan Faessler (FR) // vZBW Controller S2
AI Repainter // Occasional VATSIM Crash Pilot
Edward Glidden

OfflineOffline

Posts: 41


Private Pilot/IFR Certified. 185 Total Time


« Reply #3 on: September 17, 2011, 06:34:31 PM »

I can add some to this. If you pilots dont want to input point by point while flying.
1. while on the ground before taxi, pull up the chart and look at what points you need.
2. open the 1st tab in the menu options and click the flight planner.
3. Assuming you've downloaded the bgls, you can zoom in to the KBOS area and see the RNAV points usually depicted as a blue triangle or magenta triangle. (Normally the magenta are actual fixes of of vors). Drag the red line to each point along your DP.
4. Before taking off make sure your Autopilot Nav mode is set to GPS. Normally there is a switch in the cockpit marked NAV/GPS. If there isnt one set it in the options under key assignments.
5. Fly the DP adhering to Altitude Restrictions.

Hope this helps
Logged

GT
Mentor
vZBW Controller+
**
OfflineOffline

Posts: 199


« Reply #4 on: October 20, 2011, 07:13:34 PM »

Excellent tutorial, DO. I'm a bit shy about controlling these days because I'm uncertain about which RNAV departure to assign based on the pilot's direction of flight. When I do get back into controlling, I'll ask for an OTS or some training. I'd rather be comfortable and correct. Flying them is a different story - I fly them online all the time - and prefer them to the old departures. And as mentioned, several senior controllers from other ARTCCs issue shortcuts to waypoints after the RNAV waypoints which makes it convenient to be on course to your destination.
Logged

Jack Gilbert
DO
Division Director, VATUSA
Administrator
*****
OfflineOffline

Posts: 4424



« Reply #5 on: October 21, 2011, 01:22:30 AM »

Ah, I certainly understand.  I was quite gunshy at first as well.  I created a small cheat sheet on a 3x5 card and have it resting on the windowsill next to my computer.  It looks something like:

BLZZR     WEST     CTR/BAF/BDL/NELIE     ONEPS..BAF
BRUWN     S/SE     ACK
CELTK     E/SE     FRILL
HYLND     NW       MHT
LBSTA     NE       ENE
PATSS     W        BDL/NELIE             PATSS..BDL/NELIE
REVSS     W        CTR/BAF/BDL/NELIE     SPENO..CTR
SSOXS     S        LUCOS


It is good enough of a cheat sheet that I get by just fine with it.  The only one that throws me sometimes is BLZZR vs. PATSS vs. REVSS.  If I have time, I look it up on flighaware.  For example:

https://flightaware.com/live/findflight/KBOS/Kxxx  (replacing xxx with the destination, of course) and then clicking on one of the flights

https://flightaware.com/live/findflight/KBOS/KDFW
BLZZR ONEPS BAF Q406 BWZ J6 LIT BYP5

https://flightaware.com/live/findflight/KBOS/KLGA
PATSS BDL BDL255 VALRE HAARP1

https://flightaware.com/live/findflight/KBOS/KSDF
REVSS SPENO CTR HNK PSB APE RDSTN2

Hope this helps!
Logged

Don Desfosse
Division Director, VATUSA
ATM Emeritus, Boston ARTCC
KN
vZBW Controller
*
OfflineOffline

Posts: 208



« Reply #6 on: October 21, 2011, 09:15:19 PM »

From a real world pilot perspective, I can tell you there are quite a few of the RNAV SIDS that have overlapping departure gates. Our company (the dispatchers, specifically) do not file us on a particular SID.  Rather, they just file the first departure fix.  When we get out ATC clearance, we have our RNAV SID assigned, that contains the appropriate transition.

Also of note, yesterday was day 1 of the FAA's NYC/PHL airspace redesign project. A big change I overheard yesterday was the change from J routes to Q routes enroute.  Q routes are basically just RNAV airways, so they can design the airspace to work more efficiently.  A lot of the NYC departures changed. There are a few new departure gates.  I don't think any of them change routing up to Boston. 

Can post a follow up tomorrow.  Flying JFK-BOS-JFK-BOS-JFK-ORD.  I wonder if we'll get assigned one of these Q routes or not.

Things that make you go hmmm...
Logged

Mike Kaplan
Purdue '10
CRJ-700 FO
DO
Division Director, VATUSA
Administrator
*****
OfflineOffline

Posts: 4424



« Reply #7 on: October 21, 2011, 11:30:59 PM »

Cool, thanks for the insight, KN!
Logged

Don Desfosse
Division Director, VATUSA
ATM Emeritus, Boston ARTCC
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!