Simulator
ABR flights are operated in X-Plane 12. Microsoft Flight Simulator is not an ABR operating platform.
STANDARD OPERATING PROCEDURES / REV. 2026-08-29
More procedure.
Still a hobby.
ABR is Cascade Air Group's higher-fidelity X-Plane 12 operation. Published routes, approved aircraft, and a tighter operating standard matter here, but good judgment always outranks an immaculate virtual spreadsheet.
XP12X-Plane 12 only
04 HRbooking window
40%maintenance floor
3 TYPESE175 / 146 / A319
ABR SOP / CURRENT
Sharper standards without inventing reasons to punish people.
ABR asks for a little more preparation and aircraft fidelity than CAT. It does not ask pilots to continue a bad approach, ignore weather, or protect a booking at the expense of common sense.
Fleet and aircraft standards
The current ABR fleet is the Embraer E175, BAe 146, and Airbus A319. Use the approved X-Plane aircraft for the assigned type. ABR is built around higher-fidelity aircraft, so freeware, default, or substitute aircraft are not automatically considered equivalent unless specifically approved.
Published routes
ABR operates published airport pairs. Do not create ad-hoc ABR destinations or file an unpublished airport pair as an ABR flight unless specifically authorized. The route between the published airports may be changed for weather, ATC, runway configuration, or operational necessity.
Bookings
ABR bookings are held for four hours. Book when you reasonably expect to fly and release the booking when plans change. Repeated expirations may prompt a check-in or review, but three expired bookings do not mechanically become a disciplinary strike.
Aircraft maintenance
FlightLinq's aircraft-health status is authoritative. An ABR aircraft at or below 40% health is grounded until maintenance returns it to service. Do not dispatch a grounded aircraft simply because the route is convenient.
PIREPs
File an accurate PIREP and explain significant simulator, weather, diversion, or operational issues when useful. A rejected PIREP is not a disciplinary strike by itself. Deliberately falsified flight data is a separate conduct issue.
Approaches, go-arounds, and diversions
An unstable approach should be discontinued. Go around, divert, hold, or change the plan when appropriate. There is no one-time "unstable approach freebie" because a go-around is the expected response, not a failure.
Online ATC
VATSIM and SayIntentions are welcome. Follow the rules of the network or service you are using and comply with controller instructions when practical and safe. Network-account or community conduct issues are handled separately from routine flight operations.
Progressive enforcement
Ordinary mistakes start with coaching. Repeated noncompliance may progress to a warning or operating restriction and then removal when necessary; serious misconduct may skip intermediate steps. A pilot removed for operational or conduct reasons may normally request reapplication after 90 days unless the removal decision states otherwise.