FS2004 ATC denying landing clearance? Find what blocks clearance, how AI traffic and AFCAD files cause it, and when you must go around.
FS2004 ATC usually denies or delays landing clearance because its active runway is occupied or another AI aircraft has priority on final or departure. Stay in sequence and expect “continue” or a go-around. If the refusal never clears, excessive AI traffic or faulty AFCAD airport data is normally blocking the runway logic.
Why does FS2004 say it cannot clear me to land?
Microsoft Flight Simulator 2004 withholds clearance when its ATC engine predicts a runway conflict. This is usually temporary: an aircraft may be landing, departing, crossing the runway or taking too long to vacate it.
FS2004 does not judge your approach stability, landing weight, gear position or pilot skill. Being too high or fast will not normally cause the refusal. It is primarily traffic sequencing and runway-occupancy logic.
An IFR approach clearance is also not a landing clearance. “Cleared for the approach” authorises the published or assigned approach; tower must still explicitly clear you to land. Our overview of the normal ATC sequence from approach clearance to touchdown explains that distinction.
| Likely cause | What you will notice | Best response |
|---|---|---|
| Aircraft ahead on final | ATC tells you to continue or follow traffic | Maintain spacing and wait for clearance |
| Runway occupied | An aircraft is landing, departing or crossing | Continue only while a safe go-around remains possible |
| Excessive AI traffic | Repeated queues, late clearances or several go-arounds | Reduce airline and general aviation traffic density |
| Wrong runway or sequence | You are aligned with a runway other than the one assigned | Use the assigned runway or request another when the ATC menu permits |
| Faulty AFCAD data | The problem repeats at one airport, sometimes with no visible traffic | Test the default airport and check for conflicting airport files |
How do I get landing clearance in FS2004?
The quickest fix is to follow the assigned sequence, then isolate AI traffic and scenery if clearance still never arrives.
- Confirm the frequency and runway. Accept the hand-off to tower and check the complete runway designator, including left, centre or right. A visual approach to the wrong parallel runway does not transfer your clearance.
- Acknowledge every instruction. If tower says to continue, remain in the pattern or on final as instructed. Repeatedly asking does not remove the traffic conflict.
- Look for the blocking aircraft. Use an external or spot view to inspect the runway, final approach and departure end. An AI aircraft may be difficult to see at night or in poor visibility.
- Go around if clearance does not arrive. Do not cross the threshold at a towered airport without an explicit landing clearance. Fly the missed approach or pattern and contact ATC as directed.
- Test without AI traffic. Set both airline and general aviation traffic density to zero, reload the flight or airport area and repeat the approach. If clearance works, restore traffic gradually. Our guide to FS2004 AI schedules, density and airport parking covers the settings that create arrival queues.
- Test the default airport layout. Disable the airport’s add-on scenery area, reload the scenery and try again. If the default airport works, inspect the add-on AFCAD and remove any duplicate airport-layout files after making backups.
For installations suffering from poor AI spacing at many busy airports, the FS2004 AI traffic separation utility is another option to investigate. Read its included instructions and keep backups before changing an established traffic setup.
Why does this happen only at one add-on airport?
A persistent refusal at one airport usually points to its AFCAD or another airport-layout file rather than the global ATC system. FS2004 relies on that data to identify runways, taxi links, hold-short points, parking positions and which runways accept arrivals or departures.
Common faults include duplicate AFCAD files, disconnected taxi routes, incorrect hold-short nodes and runway-use settings that do not match the visible scenery. Weather changes can also trigger an active-runway switch while AI aircraft are still queued for the previous runway.
A mistake we see constantly is leaving an older AFCAD active after installing replacement scenery. Search the active scenery folders for files covering the same airport, but do not delete uncertain files immediately—move them temporarily outside the simulator and test one change at a time.
How long should I continue without clearance?
FS2004 has no reliable distance or time at which landing clearance is guaranteed. Tower may issue it very late, but you should continue only while the approach remains stable and there is enough room to execute a safe go-around.
If tower instructs you to go around, comply even when the runway appears clear. The conflicting aircraft may be departing, crossing or hidden by scenery, and FS2004’s ATC engine may already have reserved the runway for it.
Can I land without ATC clearance in FS2004?
You may physically land, but doing so at a towered airport is not correct procedure and FS2004 may record or announce the violation. At an uncontrolled airport there is no tower clearance to obtain; use the traffic frequency and make position calls instead.
The exact requirement depends on whether the airport and runway are tower-controlled, not simply on whether the flight is VFR. See our explanation of when VFR pilots need tower clearance before landing for the procedural difference.