GTA V ships with three civilian airfields and a military base, and on most roleplay servers all four sit dead. A FiveM aviation server — or a serious aviation lane inside an existing city — turns that wasted tarmac into scheduled airline routes, cargo contracts and player-run air traffic control. The concept is proven: dedicated flight servers have held loyal communities for years, yet almost nobody writes down how to actually build one. This is the build, from airfield roles to license wiring.
Why the sky is the emptiest niche on the platform
Walk through Los Santos International on a typical 128-slot city and you’ll find a taxi spawn, maybe a locked door, and nothing else. Sandy Shores airfield hosts the occasional stolen Duster; McKenzie Field at Grapeseed exists only in smuggling scripts that treat planes as delivery vans with wings. Meanwhile the handful of servers that committed to aviation — full flight-sim conversions with custom avionics and trained controller teams — retain players for years, because the gameplay loop has no substitute anywhere else in FiveM.
That leaves a wide-open middle: you don’t need a total conversion. An aviation department inside an RP city, run like a proper concept with jobs, licenses and airspace rules, gives pilots a home without rebuilding your whole server. Everything below works for either version.
Airline passenger RP: check-in, boarding and a timetable
Passenger flying is the social anchor of the concept. The loop is simple to wire: a check-in desk at the terminal (an ox_target or qb-target zone that sells a ticket item), a gate zone that validates the ticket and teleports or walks the passenger to the apron, and a pilot who actually flies the leg. What makes it roleplay instead of a bus ride is the staffing — a gate agent calling boarding groups, a co-pilot reading a safety brief over the cabin, a delay announced because the inbound aircraft hasn’t landed.
Run scheduled routes, not on-demand hops. Three fixed departures a night — LSIA to Sandy Shores, Sandy Shores to McKenzie, McKenzie back to LSIA — beats a “fly me anywhere” taxi because a timetable creates anticipation and lets non-pilot players plan around it. Publish it in your Discord like a real airline board and cancel flights publicly when weather scripts turn the wind up. Cancellations are content too.
Cargo runs: a job loop with weight, value and risk
Freight is the grind loop that pays pilots when no passengers are online. Build it as tiered contracts rather than one flat delivery mission. Light freight — medical supplies, mail — pays little, fits in a Cuban 800, and carries no risk. Mid-tier machinery cargo needs a Titan-class airframe, pays triple, and applies a weight penalty to takeoff performance if your handling setup respects it. Top-tier contracts carry declared value: crash or ditch and the loss is deducted from the pilot’s company account, which is the single best incentive for careful flying you can script.
Off-the-shelf pilot job scripts (qb-pilotjob, esx_pilotjob, the GFX pilot job) give you the skeleton — XP, waypoints, payouts — but nearly all of them treat cargo as a teleporting prop. The upgrade worth an evening of Lua is physical loading: pallet props moved by forklift or carried to the ramp before departure clears. Ground crew becomes a job, and a job becomes a department.
ATC roleplay: positions, clearances and radio discipline
Air traffic control is the role that turns flying into a multiplayer activity. Start with two positions, not five: Ground (taxi and pushback clearance) and Tower (takeoff, landing, pattern sequencing). Your voice resource already supports this — pma-voice and SaltyChat radio channels make perfectly good frequencies, so dedicate channel 121 as Ground and 118 as Tower and require every departing pilot to call in. The phraseology doesn’t need to be FAA-perfect; it needs to be consistent. Write a one-page script — request, readback, clearance — and train controllers on it before they sit the position.
The tooling gap is radar. There’s no dominant off-the-shelf ATC scope for FiveM, so most builders either script a simple one — a server-side loop that collects aircraft coordinates and pushes them to an NUI map for the controller — or run tower operations visually from an MLO with a view of the runway. Visual-only tower work is genuinely fun and costs nothing; save the radar script for when your controller team outgrows it.
Building the fleet around roles, not size
Every airframe you stream should answer to a job. General aviation trainers (Duster, Mammatus, or an add-on Cessna equivalent) are your flight-school fleet and should outnumber everything else. One or two mid-size cargo aircraft cover the freight tiers. Helicopters earn their slots through tourism loops — a paid sightseeing circuit over Vinewood is an easy civilian job — and through EMS air support, which gives your medical department a reason to care that aviation exists. A single airliner is a set piece for scheduled routes; five airliners are a texture budget disaster, because detailed add-on jets routinely run 80–150 MB each with liveries.
Test every aircraft under OneSync before it goes live. Fast, high-altitude entities stress sync distance, and a plane that flies beautifully solo can rubber-band badly with thirty players spread across the map. Keep resmon on during test flights, and cut any model that misbehaves — no cockpit is worth frame drops for people on the ground.
Map assets: terminals, hangars and an FBO
Vanilla LSIA has no usable interior, so an airport MLO is the one map purchase the concept genuinely requires. You’re looking for three things: a terminal with check-in counters and a boarding gate (this is where passenger RP physically happens), a tower interior with a runway view for your controllers, and hangar space that scripts can treat as aircraft garages. For the rural strips, a small FBO office — one desk, one whiteboard, coffee machine — does more for GA roleplay than another hangar, because it gives pilots somewhere to stand around and talk flying. That loitering is the culture forming.
Wiring the economy: licenses, flight school, fuel and upkeep
Gate everything behind a license progression. Store it where your framework already keeps driving licenses — player metadata in QBCore, a license table in ESX — with three tiers: student (instructor must be aboard), private (GA aircraft only), commercial (paid passenger and cargo work). The checkride is the important part: a staff instructor or senior pilot rides along, and either grades it by eye or lets a script score the landing by vertical speed at touchdown. Failing people is essential. A license everyone passes is a loading screen.
Fuel needs one config touch: most fuel scripts ignore vehicle classes 15 and 16 (helicopters and planes) by default, so enable them and place fuel points only at airfields, priced two or three times road fuel. Maintenance closes the money loop — persist engine damage between sessions and route repairs through a hangar mechanic at a real cost, so cowboy flying shows up on the balance sheet instead of vanishing on respawn.
Rules of the sky, events, and buy versus build
Publish airspace rules before the first public flight: a minimum altitude over the city (low passes over downtown get old within a week), a hard no-fly zone over the military base with disabled AI jets replaced by staff enforcement, and a crash rule — new life rule applies, the airframe is written off, and any declared cargo value is gone. Consequences are what separate an aviation concept from a plane spawner.
Events keep the department visible to the rest of the server. A Saturday airshow at Sandy Shores fills the desert with spectators, and a staged crash-response drill hands your fire and EMS departments their best scene of the month. On spending: buy your MLOs and aircraft models — modelling is a different profession — and buy a pilot job script for the mission skeleton. Script the server-specific 20% yourself: check-in zones, license gates, fuel classes, cargo value. That split is a few hundred dollars and two weekends, and it buys you the least-contested niche in FiveM.
Stock the concept from the fleet’s stores: working helicopters and support vehicles at cars-tebex.io, airport MLOs, hangars and uniforms at assets-tebex.io, and job scripts for pilots, cargo and dispatch at marketplace-tebex.io.
