As in will it properly vector me around them or does it not even recognize them?

As in will it properly vector me around them or does it not even recognize them?

sorry, i have no idea where protected airspace is, so i can't vector you around it. if something like that is important, you can request an iap approach, and fly a published approach without rc vectors.jd

As in will it properly vector me around them or does it not even recognize them?

HelloNo I don't think it does, but Flightsim commander has the option of checking your plan and warningyou of airspace transgressions.So you can modify your plan to avoid restricted airspaces.

Keep in mind NOTAMS and IAP approaches are the two things you'll want to do for prohibited airspace considerations. At Regan National Airport, I make sure I check the NOTAMS box for departure, and if I'm arriving, I'll request an IAP published approach as soon as possible so I can take the required visual approaches to avoid prohibited airspace.

Got it, thanks JD.

Keep in mind NOTAMS and IAP approaches are the two things you'll want to do for prohibited airspace considerations. At Regan National Airport, I make sure I check the NOTAMS box for departure, and if I'm arriving, I'll request an IAP published approach as soon as possible so I can take the required visual approaches to avoid prohibited airspace.

Ah, I see. I was actually asking specifically for Reagan's P56 area, so this is perfect.Thanks a lot everybody.

Keep in mind NOTAMS and IAP approaches are the two things you'll want to do for prohibited airspace considerations. At Regan National Airport, I make sure I check the NOTAMS box for departure, and if I'm arriving, I'll request an IAP published approach as soon as possible so I can take the required visual approaches to avoid prohibited airspace.

i didn't think of using notams for this. good idea. i'll still vector you, but preface everything with "...when able... fly heading/descend and maintain..." and for the prohibited areas, you can ignore the instructions.i think an iap approach would be more challenging and more realistic. in v5 i plan to use any checkpoints i find in your plan inside approach as a guide to tell you what to do, or what not to say.jd

Well what I did this morning was during departure I used the "No Altitude Restr" option on the DP as not for the ATC to badger me for going off course laterally while I was flying around the restricted airspace. Runway 1 departures in KDCA are pretty iffy if you're trying to get things right:http://www.faa.gov/ats/dca/dcaweb/p56.htmFor approach I utilized the IAP option so no problems there. The STAR positioned me perfectly to Rwy 1 ILS while vectoring me around the P56. However now I'm wondering whether for departure would NOTAMs be a better choice than the "No Altitude Restr" option?

Well what I did this morning was during departure I used the "No Altitude Restr" option on the DP as not for the ATC to badger me for going off course laterally while I was flying around the restricted airspace. Runway 1 departures in KDCA are pretty iffy if you're trying to get things right:http://www.faa.gov/ats/dca/dcaweb/p56.htmFor approach I utilized the IAP option so no problems there. The STAR positioned me perfectly to Rwy 1 ILS while vectoring me around the P56. However now I'm wondering whether for departure would NOTAMs be a better choice than the "No Altitude Restr" option?

that might be a good use for the no altitude restriction sid. put your first checkpoint about 30 miles from departure airport, and rc will leave you alone as you navigate to the first checkpoint via your sid plate.then at the first checkpoint, rc will take over, hand you off to center, and away you go.jd

i didn't think of using notams for this. good idea. i'll still vector you, but preface everything with "...when able... fly heading/descend and maintain..." and for the prohibited areas, you can ignore the instructions.i think an iap approach would be more challenging and more realistic. in v5 i plan to use any checkpoints i find in your plan inside approach as a guide to tell you what to do, or what not to say.jd

How about making a star checkbox similar to the one that already exists for SID's? That way there's an option to let control know in advance and make things happen a bit more smoothly.

i didn't think of using notams for this. good idea. i'll still vector you, but preface everything with "...when able... fly heading/descend and maintain..." and for the prohibited areas, you can ignore the instructions.i think an iap approach would be more challenging and more realistic. in v5 i plan to use any checkpoints i find in your plan inside approach as a guide to tell you what to do, or what not to say.jd

JD's idea is great and realistic.. exactly how are you going to design this feature?PS.. How's with the swine flu..I took the vaccine and got a hellish fever for a day...