Fair enough, I suppose... But notice: My assumption is that XP has access to ATIS and runway-in-use information (if XP doesn't manage this information, then who/what does? Or one assumes, at least, that this information flows through some XP interface). My question, put slightly differently, is why not utilize this information to spawn aircraft onto runways that are currently in-service? (I can't imagine the logic being too difficult: 1. Lookup first runway in service, 2. write this to the apt.dat file).
Here is my idea of an ideal solution: In addition to current options, XP's "QuickFlight Setup" dialog would offer users the option to:
1. Select airport and runway (default is a runway in use).
2. Start cold and dark, on selected/default runway or on ramp.
3. Start with engines running, on selected runway or on ramp.
4. Set date and time.
5. Load a saved situation.
Having these additional options available at startup would probably save me five minutes of manual setup before each flight.