Aetherwing eMotorsports | Official Handbook
AETHERWING // 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 adhere to 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 have transitioned from the "BellSouth" era to the "Aetherwing" era to professionalize our approach. We compete for Constructor Championships, not just individual wins.

1.2 Chain of Command
  • Team Principal (Wispy): Final authority on roster decisions, strategy, and disputes.
  • Lead Engineers/Designers: Responsible for car setups and official liveries.
  • Drivers: Responsible for execution on track.
1.3 Respect for Leadership

Disputes regarding strategy or setups should be handled in private channels, not public voice chat. Public undermining of team leadership is a conduct violation.

1.4 Recruitment & Development

New drivers enter via the Development Roster. Promotion to the Primary Roster is earned through consistency, safe driving, and integration with the team culture, not just raw lap times.

1.5 Dispute Resolution

If a driver disagrees with a penalty or team decision, they may file a formal appeal to the Team Principal via DM 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 utilize the official 2026 vector assets (Logos, Number Fonts, Sponsors). Unauthorized modification of the "Feather" emblem or sponsor placement is prohibited.

2.2 Third-Party Paint Schemes

Drivers wishing to run a "special event" paint scheme must submit the file to the Design Team for approval 48 hours before the event to ensure sponsor obligations are met.

2.3 Streaming & Media

If a driver streams their perspective, they must use the official Aetherwing overlay or include the team logo on their broadcast layout.

2.4 Suit & Helmet Standards

Drivers are encouraged to run the official team suit and helmet files to maximize brand visibility during broadcast interviews and victory lane celebrations.

2.5 Screenshot Guidelines

When sharing race results or car photos in public channels, use high-quality screenshots. "Phone photos" of monitors are unprofessional and should not be used for social media promotion.

03. Operations & Availability

"Attendance is Currency"
3.1 Championship Commitment

Aetherwing has fully transitioned into operational status. 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 the #availability Discord channel at least 24 hours in advance.

3.3 Communication

All drivers must be in the team Discord voice channel at least 15 minutes prior to qualifying for the pre-race briefing. "Radio silence" during a race is discouraged; communication regarding pit cycles is mandatory.

3.4 Punctuality

The car must be on the grid on time. Missing the grid or starting from pit lane due to poor time management forfeits team points and will be reviewed as a performance infraction.

3.5 Post-Race Debrief

Following the conclusion of a race, drivers are expected to remain in voice chat for a brief "cool down" and debrief to discuss strategy hits and misses, regardless of the race result.

04. On-Track Conduct

"The Duty of Preservation"
4.1 Situational Awareness

Speed is secondary to intelligence. Drivers are required to demonstrate situational awareness. This includes the "Duty to Lift" during wreck avoidance. Telemetry data showing 100% throttle application through an active crash scene is grounds for immediate suspension or contract termination.

4.2 The "Badge" Rule

Your conduct follows you. Whether you are driving the Aetherwing #13, a rental seat for another team, or a public lobby truck, you are an ambassador of this brand. Reckless driving in any event is a liability to our sponsors and partners.

4.3 Data Accountability

Aetherwing operates on data, not excuses. All incidents involving contact will be reviewed via replay and telemetry. If the data shows negligence (late braking, no lift, unsafe rejoins), the driver will be held accountable regardless of their intent.

4.4 Safe Rejoins

If a driver goes off-track or spins, they must hold their brakes and wait for a clear gap before re-entering the racing surface. An "unsafe rejoin" that collects another car is considered a Major Infraction.

4.5 Blue Flag Courtesy

While we race to the end, lapped cars must respect leaders. Do not fight the leaders excessively if you are multiple laps down. Facilitate a clean pass to protect the team's reputation.

05. Media & OpSec

"Protect the House"
5.1 Social Conduct

Arguments with other teams or drivers on public platforms (Twitter/X, Reddit, League Discords) are prohibited. "If you type it, you own it." Brand damage via social media is a punishable offense.

5.2 Operational Security (OpSec)

Leaking internal team strategies, setup files, telemetry data, or private Discord screenshots is a breach of contract and results in an immediate ban and blacklist.

5.3 Sponsor Protection

Drivers shall not make disparaging remarks about team partners (e.g., Kmart, PetSmart, Simagic) or use competing branding that conflicts with team exclusivity agreements during official events.

5.4 Broadcast Interviews

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

5.5 Crisis Management

In the event of a major controversy, do not post statements without consulting Team Management. Silence is often better than an emotional reaction.

06. Disciplinary Process

"Fair but Firm"
6.1 The Strike System
Standard infractions follow a three-step process:
  • Strike 1: Verbal Warning & Coaching.
  • Strike 2: Race Suspension (Parked for 1 event).
  • Strike 3: Termination of Contract.
6.2 Major Infractions (Zero Tolerance)

Specific actions bypass the strike system and result in immediate termination. These include: Intentional Wrecking, Hate Speech/Slurs, Cheating/Hacking, or "Rage Quitting" an official event.

6.3 Probationary Period

New drivers, or drivers returning from a suspension, are placed on a 3-race Probationary Period. Any infraction during this time results in immediate termination.

6.4 Strike Reset

Minor strikes (Strike 1) expire after 90 days of clean driving. Major infractions remain on the driver's internal record permanently.

6.5 Voluntary Withdrawal

If a driver feels they cannot compete safely (anger, fatigue, equipment failure), they may voluntarily park their car. This mature decision will not result in disciplinary action.

07. Technical Standards

"Equipment Check"
7.1 Network Stability

Drivers are responsible for maintaining a stable internet connection. Consistently high ping or "netcode" issues that endanger other cars are grounds for being parked until the issue is resolved.

7.2 Hardware Requirements

While a Force Feedback (FFB) wheel is highly recommended for precision, it is not mandatory. Drivers using a controller/gamepad are permitted provided they can demonstrate smooth inputs and lane stability consistent with team standards.

7.3 Audio

A functioning microphone with "Push-to-Talk" enabled is required for all official sessions to ensure clear communication during races.

7.4 Software Updates

Drivers are expected to update their simulator (iRacing/Roblox), Windows, and GPU drivers before race night. Missing a race start due to an "unexpected update" is considered an unexcused absence.

7.5 Field of View (FOV)

Drivers are encouraged to calibrate their FOV correctly. Running a distorted "fish-eye" view creates blind spots and misjudged distances, contributing to avoidable contact.