AETHERWING eMOTORSPORTS // OPS
← Return to Base
DOCUMENT ID: AW-2026-HB

Driver Standards
& Team Handbook

The operational guidelines for Aetherwing eMotorsports. All contracted drivers across iRacing and Roblox RoRacing are expected to follow these protocols during the 2026 season.

01. Organization & Hierarchy

One Team, One Mission
1.1 Team Identity

Aetherwing eMotorsports is a competitive simulation racing organization. We operate under the Aetherwing identity, competing across iRacing and Roblox RoRacing with a focus on team performance, clean execution, and professional presentation.

1.2 Chain of Command
  • Team Principal: Final authority on roster decisions, strategy, and disputes.
  • Lead Engineers/Designers: Responsible for setups, official liveries, and technical preparation.
  • Drivers: Responsible for execution on track and representing the team properly.
1.3 Respect for Leadership

Disputes regarding strategy, setups, roster decisions, or team direction should be handled privately. Public undermining of team leadership is considered a conduct violation.

1.4 Recruitment Path

Drivers rarely sign directly to the primary roster. Talent is scouted and filtered through the Driver Development Program.

1.5 Dispute Resolution

If a driver disagrees with a penalty or team decision, they may file a formal appeal to team management via direct message within 24 hours. Arguing in general chat channels is prohibited.

02. Branding & Livery

Look Elite, Feel Elite
2.1 Official Assets

All Aetherwing entries must use approved team assets, number styles, sponsor placement, and design direction. Unauthorized modification of the feather identity or partner branding is prohibited.

2.2 Third-Party Paint Schemes

Drivers wishing to run a special event paint scheme must submit it for approval at least 48 hours before the event to ensure sponsor obligations and visual standards are met.

2.3 Competitor Branding

To protect team partnerships, drivers should not display conflicting or competitor branding during official team events unless specifically approved by management.

2.4 Suit & Helmet Standards

Drivers are encouraged to run official team suit and helmet files whenever applicable to maximize team presentation during broadcasts, screenshots, and victory lane celebrations.

2.5 Screenshot Guidelines

Race results and car photos shared publicly should use clean, high-quality screenshots. Phone photos of monitors should not be used for official team media.

03. Operations & Availability

Attendance Is Currency
3.1 Championship Commitment

Drivers accepting a seat for a championship series are committing to the full schedule. Cherry-picking races is not permitted for points-paying entries.

3.2 Absence Protocol

If a driver cannot attend a scheduled league race, they must notify management via Discord at least three hours in advance.

3.3 Communication

Drivers should be in team voice chat at least 15 minutes before qualifying for pre-race briefing. Race communication regarding pit cycles, incidents, and strategy is expected.

3.4 Punctuality

Cars must be on the grid on time. Missing the grid or starting from pit lane due to poor time management will be reviewed as a performance issue.

3.5 Post-Race Debrief

Following the conclusion of a race, drivers are expected to remain available for a brief debrief to review strategy, incidents, and team performance.

04. On-Track Conduct

The Duty of Preservation
4.1 Situational Awareness

Speed is secondary to intelligence. Drivers must demonstrate awareness during wreck avoidance, restarts, pit entry, and pack racing. Failing to lift through an active crash scene may result in discipline.

4.2 The Badge Rule

Whether driving an Aetherwing entry, a rental seat, or a public lobby car, your conduct follows you. Reckless driving in any event is a liability to the team.

4.3 Data Accountability

Incidents involving contact may be reviewed via replay, timing, and telemetry where available. If the data shows negligence, the driver will be held accountable regardless of intent.

4.4 Safe Rejoins

If a driver spins or leaves the racing surface, they must hold their brakes and wait for a clear gap before rejoining. Unsafe rejoins are considered major safety infractions.

4.5 Blue Flag Courtesy

Lapped cars must respect leaders. Do not fight the lead pack excessively if multiple laps down. Facilitate clean racing and protect the team’s reputation.

05. Media & OpSec

Protect the House
5.1 Social Conduct

Arguments with other teams or drivers on public platforms are prohibited. If you type it, you own it. Brand damage via social media may result in discipline.

5.2 Operational Security

Leaking internal strategies, setup files, telemetry, private screenshots, or team messages is prohibited and may result in removal from the organization.

5.3 Sponsor Protection

Drivers must not make disparaging remarks about team partners or present conflicting branding during official events.

5.4 Broadcast Interviews

If interviewed by a league broadcaster, mention the team name and key partners when appropriate. Avoid blaming other drivers on-air; save frustration for internal debrief.

5.5 Crisis Management

In the event of a major controversy, drivers should not post public statements without consulting team management.

06. Disciplinary Process

Fair But Firm
6.1 Strike System
  • Strike 1: Verbal warning and coaching.
  • Strike 2: Race suspension or temporary parking.
  • Strike 3: Termination of contract or roster removal.
6.2 Major Infractions

Major infractions may bypass the strike system. These include intentional wrecking, hate speech, cheating, exploiting, or rage quitting an official event.

6.3 Probationary Period

New drivers or drivers returning from suspension may be placed on probation. Any infraction during probation may result in immediate removal.

6.4 Strike Reset

Minor strikes may expire after an extended period of clean driving. Major infractions remain on the internal record.

6.5 Voluntary Withdrawal

If a driver feels they cannot compete safely due to anger, fatigue, equipment failure, or connection issues, they may voluntarily park the car. This mature decision will not result in discipline.

07. Technical Standards

Equipment Check
7.1 Network Stability

Drivers are responsible for maintaining a stable internet connection. Consistent lag, high ping, or connection issues that endanger other cars may result in being parked until resolved.

7.2 Hardware Requirements

A force feedback wheel is recommended but not mandatory. Controller users are permitted provided they can demonstrate smooth inputs, lane stability, and safe racecraft.

7.3 Audio

A functioning microphone with push-to-talk is strongly recommended for official sessions.

7.4 Software Updates

Drivers are expected to update their simulator, Roblox, iRacing, Windows, and GPU drivers before race night.

7.5 Field of View

Drivers are encouraged to calibrate their field of view correctly to avoid blind spots and misjudged distances.

7.6 Setup Transparency

Aetherwing operates with a team-first mindset. Fast setups, useful discoveries, or strategy information should be shared with teammates when applicable.

08. Driver Development

The Path Forward
8.1 Driver Development Program

The Driver Development Program serves as the entry point for new talent looking to join the Aetherwing primary roster.

8.2 What We Look For
  • Consistency: Finishing races matters more than one fast lap.
  • Availability: Showing up without being chased is valuable.
  • Attitude: How you handle losses, wrecks, and criticism matters.
8.3 Promotion Path

Drivers who demonstrate consistency, pace, availability, and maturity may be offered reserve or primary roster opportunities.

8.4 Performance Reassignment

Primary drivers who consistently miss events or violate conduct policies may be reassigned to development status to rebuild consistency.

8.5 Mentorship Access

Development drivers are encouraged to ask questions, review replays, and learn directly from primary roster drivers.

8.6 Code of Conduct

Development drivers must meet the same conduct expectations as primary drivers. Toxicity, intentional wrecking, or poor communication can result in removal.

09. General iRacing

The Simulation
9.1 Oval & Stock Car

Bump drafting is permitted on straightaways where appropriate. Bump drafting in corners is prohibited unless league rules explicitly allow it. The trailing car assumes responsibility for resulting incidents.

9.2 Formula & Open Wheel

Open-wheel cars require extra spacing. Drivers must avoid moving under braking and should respect the one-move defensive rule.

9.3 Sports Car & Road Racing

In multi-class traffic, faster cars are responsible for passing safely while slower cars must remain predictable. Track limits should be respected.

9.4 Dirt Racing

Slide jobs must be executed cleanly. Using up another driver or sliding into their door is considered avoidable contact.

10. iRacing Endurance

First, You Must Finish
10.1 Fair Share & Drive Time

Drivers must follow the event’s fair share and drive-time requirements. Failure to meet minimum drive time can disqualify the entire team.

10.2 Handoff Procedures
  • Heads Up: Let the next driver know when you are pitting.
  • The Swap: Confirm the driver change is active before leaving.
  • Don’t Ghost: Stay available until the team confirms the car is under control.
10.3 Stint Logic

Tire strategy should prioritize consistency and safety. Fatigue-related mistakes are avoidable and must be managed.

10.4 Disconnect Protocol

If the active driver disconnects, the next available driver should be ready to enter the car as quickly as possible.

10.5 Sleep & Availability

For endurance events, drivers must be awake and ready before their scheduled stint. Oversleeping a stint is a serious issue.

11. Roblox RoRacing

Roblox Operations
11.1 Platform Integrity

Drivers must follow anti-exploit rules. Glitching, lag-switching, or abusing game systems can result in immediate removal.

11.2 Wall-Riding Protocol

Wall-riding is prohibited by default. It may only be used for recovery if league rules allow it. Wall-riding to pass or defend position is prohibited.

11.3 Pit Stop Protocol

Drivers must follow league-specific pit rules. Exploiting pit timing, stalls, or service glitches is prohibited.

11.4 Spawn Safety

Drivers must ensure the track is clear before spawning or resetting a vehicle. Dropping into live traffic is a major safety issue.

11.5 Account Security

Drivers should use their primary verified accounts for league races. Alt accounts used to evade penalties are prohibited.

11.6 Conduct & Maturity

Aetherwing drivers must treat league admins, officials, and competitors with professional courtesy. Chat toxicity, raids, and spam are prohibited.

11.7 Lapped Traffic & Lead Lap Protocol

Drivers who fall laps down must avoid impeding leaders. Battling to remain on the lead lap is permitted, but intentional blocking, brake-checking, or malicious slowing is prohibited.