Unusual AFCAD setup

[Carob 2]

Hello. I was hoping someone would be able to answer a question for me regarding the setup of an AFCAD file.I am using the KASE scenery by Todd Lucas and I was trying to make a small change to the AFCAD file. The problem is I don't know if what I'm trying to do is even possible in FS9.At KASE the takeoffs are usually on 33 and the landings are usually on 15. So, I was hoping to be able to make the AFCAD file do this. The trouble is when closing 15 for takeoffs the sim wants all aircraft to land on 33.Is it possible to generate opposite takeoffs and landings like this in FS9?Any help would be appreciated.Thanks!

[Mike... 7]

No. You can't close one end of a runway for landings/take-offs, without closing the opposite end the same way. For example, close for take-offs on both sides works. Depending on a couple of other factors, but if there are other long enough runways, it'll work.You can close one end only, but you'll have to close it for landings and take-offs. And leave the other end open completely.It's a pain to get airports like KASE working.

[Guest wji]

Thanks to Tod Lucas for his FREE Aspen scenery. It's great.Lee Swordy's AFCAD2 Readme:40. RunwaysClosed for Takeoff You can specify one end or both ends of a runway to be closed for takeoffs to prevent AI and ATC from using it. This does not prevent aircraft from landing on the runway. Note that runway closures are not absolute in FS. ATC may override a closure. See Runway Closures for details.Closed for Landing You can specify one end or both ends of a runway as closed for landings to prevent AI and ATC from using it. This does not prevent aircraft from taking off from the runway. Note that runway closures are not absolute in FS. ATC may override a closure. See Runway Closures for details.Runway Closures:The rules which FS uses to enforce runway closures are not yet fully understood, but a few things are known: Runway closures only appear to work with parallel, or very nearly parallel runways. You can close any combination of parallel runways for landing and/or takeoffs, as long as there is at least one runway open for landing and one open for takeoffs. Takeoffs and landing must be in the same direction. If you try to use closures to force takeoffs and landings to occur in different directions, or if you try to force takeoffs or landings in an unfavourable wind direction then ATC may override the closures and use the runways it prefers anyway.Active Runway Selection:The rules which FS ATC uses to decide which runways to make active are not fully understood, but here a few things we know: ATC can use two or more runways at a time for takeoff and landings, but they must be parallel. It won't use crossing runways. This is no doubt to avoid the complexities of keeping crossing arrival and departure aircraft streams separated, both on the runways and the approaches.When two separate runways are in use, ATC will not divide the load evenly between them, but instead it will assign the runway closest to the direction the aircraft is arriving from for landing. So at an airport with parallel East/West runways, all traffic arriving from the North will land on the northernmost runways, and all traffic from the South will land on the southernmost runway(s). This is also, no doubt, to prevent separation problems with crossing arrival/departure streams. For takeoff ATC will assign the closest runway to the parking spot.Propeller aircraft are often directed to shorter runways than jet aircraft. This seems to be keyed to the engine type field in the .air files.Reprinted for Educational Purposes OnlyReference cited: AFCAD2 Readme File Section 40

[RFields5421 1]

Unfortunately, this, like all the AFCAD Readme, was written before the full SDK was out and we learned so much:You can specify one end or both ends of a runway to be closed for takeoffsIncorrect - you can specify both ends of a runway to be closed for takeoffs or both ends of a runway to be closed for landings - both ends need to be set the same way, unless altered start locations are also used.Runway closures only appear to work with parallel, or very nearly parallel runways.Incorrect - runway closures can be made permanent - even on a single runway airport.FlightSim 2004 gave us several default examples of how to make a runway 'one way'.One is Rwy 5/23 at EGLL. There can be takeoffs on Rwy 23 and landings on Rwy 23, but no takeoffs or landings on Rwy 5. The key is that inaddition to setting the runway properties - there must be no start location for the 'closed' end of the runway.it will assign the runway closest to the direction the aircraft is arriving from for landing.Incorrect - the runway assignment for landing is the runway with the approach IAF point closest to the departure airport.Propeller aircraft are often directed to shorter runways than jet aircraft. This seems to be keyed to the engine type field in the .air files.Partially correct - Aircraft weight is a critical factor for jet aircraft - empty weight for AI aircraft. For landings - the key weight is 91,500 lbs - AI aircraft with an empty weight over that amount will be sent to runways longer than 7,000 ft. Unfortunately many AI aircraft flight dynamics are set to unrealistically low weights to make them fly 'more realistic' resulting in situations like KSNA where AI aircraft want to land on the short GA runway.There is an engine factor in takeoff runway selection. Piston engined aircraft can use any runway, turbo-props want a longer runway - I think the number is 4,500 ft. Jets have several factors/ lengths necessary.Back to the original question - No - additional testing and research has not found a way to make a runway 'head to head' like KASE needs - All landings on Rwy 15 and all takeoffs on Rwy 33.