NOTAM: Clarification of the Bail Out Rule
(5-17-13)
We have a bail out rule to allow pilots to lead normal lives during the event. We understand that there will be times when the real world unexpectedly intrudes on the flight simulation event and that pilots will have to put first things first.
Thus, if the real world unexpectedly intrudes on your flight you may simply declare a "bail out" and terminate the flight. At your convenience, you may restart the flight and continue on as though nothing had happened. In the Western Roundup, a pilot may use this bail out provision once without penalty. On each subsequent bail out, the cost is a five minute penalty. Rookies may freely use the provision as many times as necessary.
We want to clarify how the rule is meant to be used. A pilot may actively bail out by terminating his flight when he is in control of the aircraft. The rule does not apply to a situation when the pilot has put the aircraft on autopilot and walked away from the computer. The original language was not clear because our own intent was not clear.
(What has always been clear is that the provision addresses a "real world" intrusion – not something in the simulator. If you run out of gas or become lost or find your destination socked-in, you may not declare a "bail out" – that would be inappropriate.)
Elaboration.
We do want pilots to take advantage of this rule because we want pilots to be able to fly in the context of busy lives. If the phone rings and it is a long-distance call from your brother in Namibia, then you will have to concentrate on the call and not on the simulation. You should quickly declare a "bail out" on the forum thread and that will suffice. A longer explanation can come later. If you spouse starts a "meaningful" conversation, or if your kids come into the room and demand your attention, or if the flames of your burning house enter your study, you simply declare a bail out.
The bail-out provision is not intended to apply to occasions when you put the aircraft on autopilot and walk away from your computer. If you choose to fly on unattended autopilot (and everyone will have times to do this), you leave the aircraft at your own risk. You may not return to the computer and declare a bail-out after you discover your plane has crashed! So the decision point is when you decide to put the aircraft on autopilot.
To be sure, there may be ambiguous situations. You may have the aircraft on autopilot when you get that phone call or discover the flames in your kitchen and then be unable to return to the computer to declare the bail-out. Doing so later would be ok – but you certainly want to give a full explanation so that everyone understands that you are not taking advantage of the rule. Normally, the expectation is that you will return to the computer and issue a "bail out" when your routine autopilot break turns into something more serious. So anything else would be a special exemption, one likely to be granted. Ms. Murphy will provide a ruling. (You might send your explanation to the organizers via Personal Message if you want to keep your privacy. No need to say everything in public.)
Note that you might put the aircraft on autopilot so that you can go to the kitchen for a snack – and then linger a moment talking with your spouse or kids. You are doing this at your own risk. Similarly, if you get an interruption and decide to keep flying on autopilot while you handle the interruption, then you do so at your own risk. If something goes wrong, you accept responsibility.
The organizers' goal here is both to accommodate these unexpected intrusions and also to maintain the "pilot in command" nature of the event. Some intrusions are unexpected and unavoidable, others are not. It is the former that we wish to handle.
The bail-out is a conscious decision to terminate a flight made while under control and when it appears danger may become imminent. Encountering a potential situation and letting it run (under human control or while on autopilot) until a crash occurs is a also a decision but should it result in a destructive event it must be recorded as a "crash" and scored as such.
(This rules clarification will apply from this point forward. Previous usage is not affected.)