This document specifies the standards that all Sweatbox scenario files must follow. This only concerns those users who create and/or update the training scenario files.
If you are a member of training staff, the general rule of thumb is to use existing scenarios. Any sweatbox scenario must be approved by the TA before being used for training.
- Aircraft callsigns must have the following characteristics:
- Realistic. Do not use Air France callsign in a scenario used for a minor field.
- Unique. No callsign should be used in more than one scenario file for the same facility. This is to avoid callsign conflicts when a top-down session is being conducted.
- Flight plans
- Only delivery scenarios can contain mistakes in flight plans (such as wrong cruise altitude for direction, etc).
- For all other scenarios, the flight plans must be realistic and error-free.
- Approach flows:
- Arrivals should have a speed of 250 to 300 knots. Arrivals that are handed off to the approach positions at or below 10,000' must have a speed of 250 knots or less.
- For each flow, two files should be created: 15 mile-in-trail and 20 MIT.
- Final approach scenarios should use realistic speeds, such as 210 or 230 knots.
- For heavy traffic, use the
H/prefix in their aircraft type, so that the controlling software would correctly show them as heavy. - Preferably, use callsigns that are easy to distinguish by their number part. That is, do not use DAL121, UAL121 and AWE121 in the same scenario.