FF Questions - Departure Procedures

nj-pilot

Pre-takeoff checklist
Joined
Aug 17, 2015
Messages
243
Location
Maine
Display Name

Display name:
josh_me
Sorry if this has been answered somewhere, but I couldn't find anything in the manual or their searchable FAQ site.

2 Questions:
1) Can you insert a departure procedure to flight plan, as you can with approach procedures?
2) Does FF support georeferenced departure procedures?

Thank you
 
1. Yes
2. No because SIDS and STARS are not drawn to scale. But the fixes will be drawn on the map page so you can still follow the magenta lines.
 
Sorry if this has been answered somewhere, but I couldn't find anything in the manual or their searchable FAQ site.

2 Questions:
1) Can you insert a departure procedure to flight plan, as you can with approach procedures?
2) Does FF support georeferenced departure procedures?

How do you insert an approach procedure to a flight plan?
 
No because SIDS and STARS are not drawn to scale
And every once and a while, the SID/STAR plate has a major mistake.

For a while, there was Arrival plate that had KDTO (Denton, TX, my home base) on the wrong side of KDFW on the graphical side. The Text description was correct, but someone move the airport over near Mesquite,TX without informing us locals.
 
Ok - so using the proper terminology (thank you), is there a way to add a departure procedure to one's route/nav log (as you can with approach procedures)?
 
Yes, you can always edit the waypoints by typing the name of the fix or procedure.

For example, if you had started with KDTO KHOU, just "insert in front" of KHOU and type JPOOL7.CLL and it will insert the Joe Pool Seven departure, College Station Transition.

Then add CLL.BLUBL3 and it will insert the Bluebell Three arrival, starting at College Station.

Or you can just tap the correct buttons starting with the PROCEDURES on like shown post #4
 
Ok - so using the proper terminology (thank you), is there a way to add a departure procedure to one's route/nav log (as you can with approach procedures)?
Still yes. You an input it as KDEP SIDNAME.TRANSITION NEXTFIX. or go to the route advisor and pull it up.
 
Usually takes me a reply or three to know if "FF" is Flight Following or Foreflight. Would be great if Foreflight was abbreviated differently since the product name is a single word.
 
Usually takes me a reply or three to know if "FF" is Flight Following or Foreflight. Would be great if Foreflight was abbreviated differently since the product name is a single word.

We could just call foreflight "F"
 
Usually takes me a reply or three to know if "FF" is Flight Following or Foreflight. Would be great if Foreflight was abbreviated differently since the product name is a single word.
Single word, single letter. Foreflight should be just F.
 
For example, if you had started with KDTO KHOU, just "insert in front" of KHOU and type JPOOL7.CLL and it will insert the Joe Pool Seven departure, College Station Transition.

Then add CLL.BLUBL3 and it will insert the Bluebell Three arrival, starting at College Station.

Or you can just tap the correct buttons starting with the PROCEDURES on like shown post #4
Thank you @AggieMike88. For some reason, neither works for me.
For a different route (out of Morristown, NJ - KMMU), I tried to add MMU6.MMU (the Morristown Six departure procedure), and it said that departure was not found. When I click the PROCEDURES button as you noted above, it only gave me choices for approach (not departure) procedures. I'm using the latest F pro version, but wonder if you have something unlocked in your version that I don't? Oh well, thanks for the help.
 
Make sure to read the pilots guide. And email the support team after doing that.
 
Single word, single letter. Foreflight should be just F.

Steven, you know that makes too much sense to be applicable anywhere on this board.

People get their IFR rating here and talk about how many RPMs their plane has and how things come from together.
 
Thank you @AggieMike88. For some reason, neither works for me.
For a different route (out of Morristown, NJ - KMMU), I tried to add MMU6.MMU (the Morristown Six departure procedure), and it said that departure was not found. When I click the PROCEDURES button as you noted above, it only gave me choices for approach (not departure) procedures. I'm using the latest F pro version, but wonder if you have something unlocked in your version that I don't? Oh well, thanks for the help.

The problem isn't Foreflight or your subscription. Take a look at the plate for the Morristown Six SID. What is the route to any of the transitions?

As you can see there are none. The Morristown Six in a pure vector SID. The only routing is radar vectors to the assigned transition. What do you propose Foreflight put in for the magenta lines? You won't find this SID even in a certified box like the latest Garmin 750.

Try it with a SID that has a routing. It will work exactly like the STARs you saw.
 
The Morristown Six in a pure vector SID
wow.... looking at that makes me sorta glad the local SID's are much simpler...

Except if you're a mooney guy trying to find the Equipment transition.
 
Steven, you know that makes too much sense to be applicable anywhere on this board.

People get their IFR rating here and talk about how many RPMs their plane has and how things come from together.

Youse gotta problem wid dat?
 
wow.... looking at that makes me sorta glad the local SID's are much simpler...

Except if you're a mooney guy trying to find the Equipment transition.
Actually, the are very easy to fly. ATC clears the SID and the transition and the route after that. You put the transition and the rest of the route in the GPS (and EFB) and fly the vectors until at some point, ATC just says, proceed direct to it.

Edit: and yes, love that video!
 
Last edited:
Actually, ForeFlight Mobile is abbreviated as FFM within ForeFlight.

Regarding including SIDs and STARs within the route editor on the Map view, that can be accomplished if they are in the database. If not, the entry will generate an error. Many SIDs in particular, can't be filed in a flightplan route. Most common are SIDs that are vector SIDs where the descriptive text indicates the route is a vector. Some can't be filed, because they are only assigned by ATC. Most of these, but not all will have a note to that effect. Others will have a note on the chart to just file the first fix on the route and not to file the SID. Still others specify a code that if used will be rejected by the ATC computer. When you do file a SID, you always need to also file a transition fix. Usually the last common fix on the SID route can be used if you don't wish to file with a transition, but not always. With a STAR, you usually file with a transition or a fix on the common route. Again, not all STARs can be filed, particularly if they have the note "Assigned by ATC Only".

A SID is coded as SIDNAME.TRANSITION. A STAR is the opposite, TRANSITION.STARNAME. The TRANSITION must be a fix on the procedure and for a SID, it must be preceded by the departure airport and for a STAR, it must be followed by the destination airport on the FFM route editor. Although you can load an approach using the route editor in FFM, you don't want to file it. It is OK to file the IAF fix, but your clearance limit is going to be to the destination. When you use the FFM function to send the route to File&Brief, the approach will be deleted.
 
Back
Top