On the KORD 4R ILS approach, real world ATC typically instructs to cross DEGAN at or above 8000

i wish i could handle/model every single approach, to every single runway, to every single airport in the world. i probably could if i had the data. but at the moment i can'ti can attempt to provide realistic approached to every runway at every airport with a genreic approach.off the top of my head, i don't know the msa at kord. maybe you are higher than you expect because of that.you sound like a very knowledgable user, wanting to fly a very realistic approach. i suggest asking for a ils iap approach to 4R when you contact approach. and then fly it exactly like the chart says.when you are 7 miles out, you will be told to contact tower.jd

jd,Thx for the reply. Was not really questioning the DEGAN altitude constraint relative to vectoring to 4R ILS within RC (BTW I think RC4 is a great add-on and I enjoy it immensely and use it consistently for that real world feel-offline)but was assuming there may be some RW ATC controllers in this forum who may provide some insight into the 8000A DEGAN crossing altitude and the consequent need for (dive) entry into the 4R ILS from above the GS, particularly from a somewhat straight in approach from the BDF4 STAR. And was wondering how common it is for entry into an ILS from above the GS? Thx again for a GREAT product and the great support.

I'm not a controller but am a bit familiar with the area. I'll get the star from www.flightaware.com - resources.I'm pretty sure it is for vertical separation due to Midway and that other (momentarily forgot the name) of that large Wisconsin area airport that acts as a feeder for Chicago. I think it is Billy Mitchell field.The _8000_ the older plate I have shows is right on the GS at DEEGAN and the GS is the normal three degrees. The straight in RAHNN IAF 31 DME ORD is at _11000_ on the GS and should be on the STAR. Note that the vertical profile _ altitudes on the plate have a notation on that heading that ATC can direct an altitude of 2600 which is the MSA from everywhere but the SE quadrant at 3400. No diving should be required.On the Controller page of RC adjust the MSA if required to 3400 which should be good enough for 360o coverage, or fly under NOTAMS with vectors or elect the IAP. RAHNN should be in your flight plan.

One other thought:In FS8 and 9 by default if a runway shares the same localizer frequency at each end, it is possible until right in the center of the beam your equipment could lock onto the wrong localizer displaying the incorrect information. You might have been looking at the wrong glideslope. I did not check the plate for the frequencies. If it is be sure to use AFCAD to get to the runway navaid properties and turn off the backcourse on each.