Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instrument Procedures with Vectors & Holds #439

Closed
jpeterson1346 opened this issue Apr 12, 2016 · 4 comments
Closed

Instrument Procedures with Vectors & Holds #439

jpeterson1346 opened this issue Apr 12, 2016 · 4 comments

Comments

@jpeterson1346
Copy link
Contributor

Is there a way to incorporate radar vectors between a departure's climb and the departure itself (e.g., DEEZZ4 departure at KJFK:

"TAKEOFF RWYS 22L/R: Climb heading 225° or as assigned by ATC, thence . . . .

. . . . expect vectors to DEEZZ, then on track 296° to HEERO. Maintain 5000. Expect clearance
to filed altitude/flight level within ten (10) minutes after departure."

instead of having a departure fly from say "YNKEE" directly to DEEZZ and then continue as filed?

ref: http://flightaware.com/resources/airport/KJFK/DP/all/pdf

@erikquinn
Copy link
Collaborator

Currently not, but since this is such common practice, it would definitely be a good addition to the SID functionality.

@jpeterson1346
Copy link
Contributor Author

Most definitely agree; as it stands now, I cannot issue vectors after an initial climb out of JFK through the JFK3 departure (#440). Thus, the JFK3 departure is unusable at this time.

@erikquinn erikquinn changed the title SIDS with radar vectors SIDs & STARs with radar vectors May 14, 2016
@erikquinn erikquinn changed the title SIDs & STARs with radar vectors Instrument Procedures with Vectors & Holds Nov 20, 2016
@erikquinn
Copy link
Collaborator

See #651 (closed as dupe).

@erikquinn
Copy link
Collaborator

The ATC repository is being migrated to it's new home at https://github.com/openscope/openscope,
and thus, all issues are being closed. If this is still an issue with the latest version of the sim
(accessible at http://www.openscope.co), or is a feature you still think we are lacking,
please reopen the issue at the new repo.

Please note that the vast majority of these issues have been copied to the new repository, or else are covered by other issues created there. See the below screenshot for what it looks like when your issue is known in the new repo:

image

Thank you!

Closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants