{"id":158077,"date":"2024-09-23T14:44:59","date_gmt":"2024-09-23T12:44:59","guid":{"rendered":"https:\/\/hifivem.com\/?p=158077"},"modified":"2026-06-24T17:40:39","modified_gmt":"2026-06-24T15:40:39","slug":"disable-airplanes-and-helicopters","status":"publish","type":"post","link":"https:\/\/fivemx.com\/pl\/disable-airplanes-and-helicopters\/","title":{"rendered":"How to Disable AI Planes and Helicopters in FiveM"},"content":{"rendered":"

How to Disable Airplanes and Helicopters in FiveM<\/strong><\/p>\n

FiveM servers can become bogged down by artificial intelligence (AI) aircraft that randomly spawn at airports and airfields. Whether you\u2019re running a realistic utopia or a post\u2011apocalyptic sandbox, those AI planes and helicopters can degrade performance, interfere with gameplay, and clash with your server\u2019s theme. This guide walks you through a quick, easy script you can add to your server that disables all unwanted AI airplanes and helicopters, giving your players a smoother experience.<\/em><\/p>\n

Why Disabling AI Planes and Helicopters Matters<\/h2>\n

– Improved Server Performance<\/strong> \u2013 Fewer entities mean less CPU and memory usage, freeing resources for other scripts and assets.
\n– Cleaner Gameplay<\/strong> \u2013 Protect missions and role\u2011play scenarios from unplanned air traffic.
\n– Thematic Coherence<\/strong> \u2013 A sandbox set in a destroyed city can feel more authentic when no airplanes drift overhead.
\n– Reduced Lag<\/strong> \u2013 AI aircraft are resource-intensive. Knocking them out of the equation can lower ping and increase frame rates for your players.<\/p>\n

Disabling AI Planes and Helicopters with the gd_airport_ai_begone Script<\/h2>\n

The gd_airport_ai_begone<\/em> resource is a lightweight solution that removes a broad set of scenarios, models, and spawn points around all major San Andreas airports. Once injected into your server, the script automatically stops jets, turboprops, and various ground vehicles from appearing on the tarmacs. It also guards against remote spawn requests from distant sky locations.<\/p>\n

Step\u2011by\u2011Step Implementation<\/h3>\n

1. Create a Resource Folder<\/strong>
\n Navigate to your server\u2019s `resources` directory and create a new folder named `gd_airport_ai_begone`.<\/em><\/p>\n

2. Add a Manifest File<\/strong>
\n Inside that directory, create either `__resource.lua` (for legacy servers) or, better yet, `fxmanifest.lua` if you use the latest server version:<\/em>
\n “`lua
\n fx_version ‘cerulean’
\n game ‘gta5’
\n client_script ‘client.lua’
\n “`<\/p>\n

3. Write the Client Side Script<\/strong>
\n Create `client.lua` and paste the following:<\/em>
\n “`lua
\n Citizen.CreateThread(function()
\n local SCENARIO_TYPES = {
\n WORLD_VEHICLE_MILITARY_PLANES_SMALL,
\n WORLD_VEHICLE_MILITARY_PLANES_BIG
\n }
\n local SCENARIO_GROUPS = {
\n 2017590552, — LSIA planes
\n 2141866469, — Sandy Shores planes
\n 1409640232, — Grapeseed planes
\n ng_planes — jets \u201chigh\u201d in the sky
\n }
\n local SUPPRESSED_MODELS = {
\n SHAMAL, LUXOR, LUXOR2, JET,
\n LAZER, TITAN, BARRACKS, BARRACKS2,
\n CRUSADER, RHINO, AIRTUG, RIPLEY
\n }<\/p>\n

while true do
\n for _, type in pairs(SCENARIO_TYPES) do
\n SetScenarioTypeEnabled(type, false)
\n ko\u0144cu
\n for _, group in pairs(SCENARIO_GROUPS) do
\n SetScenarioGroupEnabled(group, false)
\n ko\u0144cu
\n for _, model in pairs(SUPPRESSED_MODELS) do
\n SetVehicleModelIsSuppressed(GetHashKey(model), true)
\n ko\u0144cu
\n Citizen.Wait(10000) — Re\u2011evaluate every 10 seconds
\n ko\u0144cu
\n end)
\n “`
\n The script revolves around three arrays: <\/em>SCENARIO_TYPES (small and large military planes), <\/em>SCENARIO_GROUPS (airport\u2011based spawn pools), and <\/em>SUPPRESSED_MODELS (specific aircraft and support vehicles). Adjust these lists if you wish to re\u2011enable particular models.<\/em><\/p>\n

4. Load the Resource<\/strong>
\n Open `server.cfg` and add:<\/em>
\n “`
\n start gd_airport_ai_begone
\n “`
\n Save and close.<\/em><\/p>\n

5. Zrestartuj<\/strong>
\n Reboot the server or run the console command `restart gd_airport_ai_begone` to activate the new script.<\/em><\/p>\n

Customizing the Script<\/h2>\n

If you\u2019re on a mixed\u2011traffic server and want a few aircraft left in the sky, edit the `SUPPRESSED_MODELS` array. Comment out or remove any model you wish to return. For example, to keep jets alive, delete the `JET` line. After adjusting, restart the resource to see the changes take effect.<\/p>\n

Best Practices<\/h2>\n

– Back Up<\/strong> \u2013 Before touching any server files, make a copy of your current configuration and scripts.
\n– Test Thoroughly<\/strong> \u2013 Once the server is running, hop into each airport area to confirm no unwanted aircraft appear.
\n– Monitor Resource Usage<\/strong> \u2013 Use tools like the FiveM console\u2019s `stats` command or external monitoring software to verify that CPU usage has decreased after disabling AI planes.
\n– Keep Scripts Updated<\/strong> \u2013 If FiveM changes the underlying spawning mechanics, you may need to tweak scenario names or model hashes.<\/p>\n

Podsumowanie<\/h2>\n

By adding the gd_airport_ai_begone<\/em> script to your FiveM server, you effortlessly disable AI airplanes and helicopters that can otherwise clutter the sky, drain performance, and disrupt your desired gameplay atmosphere. This small change frees up computing power, delivers a cleaner experience, and keeps your server\u2019s world cohesive. If you run into any hiccups or want to share additional tweaks, drop a comment below or participate in the FiveM community forums for support.<\/p>\n

<\/p>\n

Practical checklist<\/h2>\n

Use this guide as a staging checklist before changing a live FiveM server. Confirm the current server artifact version, framework version, resource dependencies, database changes, and any client-side files before you apply the change.<\/p>\n