Aircraft noise portals and WebTrak: using flight tracks as a spotter’s tool

Every spotter knows Flightradar24. Less well known is that many airports run a map of their own on which every flight track around the airport can be seen – with altitude, aircraft type and the noise level the aircraft produced at the nearest monitoring station. These aircraft noise and flight track portals, often found internationally under the name WebTrak, are actually meant for residents. For you as a spotter they are a precise planning tool: they show not where aircraft are supposed to fly according to a chart, but where they actually flew. This guide explains how the portals work, where their limits are and how to derive better spots from them.

What aircraft noise portals actually are

Airports are under pressure to be transparent toward their neighbors. Anyone who wants to know why a jet thundered over their roof at 6:05 a.m. should be able to find out. This has led to public web applications that combine three things:

• Flight tracks: The positions of arrivals and departures around the airport, as a line on a map, usually colored by altitude.
• Flight data: Clicking on an aircraft usually brings up callsign, aircraft type, altitude, speed and departure and destination airports.
• Noise readings: Fixed or mobile monitoring stations in the surrounding communities, whose level curve you can match to an overflight.

One of the best-known systems is called WebTrak and comes from the Australian provider Envirosuite. Airports and air navigation service providers embed it into their websites as a subscription service, often multilingual and with a form for noise complaints. Besides that, there are solutions of individual airports or environmental associations. How noise is measured and assessed is described in the article Measuring aircraft noise – here the topic is what you as a spotter get out of this data.

Where the data comes from – and why that matters for spotters

Most flight tracker apps live off the reception of ADS-B signals that aircraft transmit themselves and that a worldwide network of volunteers picks up. How this works is explained in the guide Flight tracking with ADS-B for spotters. Aircraft noise portals often work differently: they use the radar data of air traffic control.

Two documented examples:

• Airservices Australia feeds WebTrak with air traffic control radar data. Aircraft within a radius of 100 kilometers around the major airports up to about 30,000 feet are covered – including Sydney, Melbourne, Brisbane, Perth, Adelaide and other airports.
• In Frankfurt, the INAA application of the Environment and Community Center (UNH) is based on data from the FANOMOS system of German air traffic control (DFS). Transponder data can optionally be shown.

For you that means: in noise portals you also see traffic that is missing from ADS-B maps or appears only patchily – for example aircraft with older transponders that transmit an identifier but no position of their own. Conversely, the view is limited: the portals only show the surroundings of an airport, not cruise flight across the continent.

Criterion	Noise portal (e.g. WebTrak)	Flight tracker app with ADS-B
Data source	mostly air traffic control radar, partly transponder	ADS-B receivers, supplemented by MLAT
Delay	deliberately delayed, minutes to hours	nearly live
Coverage	radius around one or several airports	worldwide, depending on receiver density
History	replay of past days, often free	usually limited in free versions
Noise data	yes, with monitoring stations	no
Registration	rarely shown	often shown

The delay: not a bug but a principle

Anyone opening a noise portal for the first time often wonders why the aircraft lag behind reality. The delay is intentional and has different reasons depending on the portal. Airservices Australia shows ongoing flights, by its own account, with a lag of about three minutes. In Frankfurt the range is 75 to 135 minutes, because the readings are transmitted roughly hourly and the flight tracks are only processed afterward.

For live spotting, these portals are therefore only of limited use. Another note from Australia is interesting: the data of the large airports is checked overnight, so replays from the previous day are more accurate than the live view. This is exactly where the value for you lies – in hindsight.

Five things a noise portal tells you

1. Where approaches really turn in

On paper, aircraft land along the extended runway centerline. In practice they turn onto final approach earlier or later depending on the traffic situation, and departures leave the centerline on defined routes. In the replay you see the bundles of hundreds of tracks: where they converge closely, you have a high chance of standing in the right place. The theory behind it is explained in the article SIDs and STARs, the final approach itself in the guide to the ILS approach.

2. How high the aircraft are at your spot

Clicking on a track lets you read the altitude at every point. That lets you plan the focal length before you set out: an aircraft a few hundred feet above you needs a different lens than one passing at a much greater height. In the legend, check whether the altitude is given above sea level or above ground.

3. Which runway was used when

At airports with several runways, the replay immediately shows which runway was used for takeoffs and which for landings at what time of day. This complements the basic rules from the guide Understanding the runway direction in use at an airport with real observations from the specific airport.

4. When operations rest

Night hours without tracks are immediately visible on the map. That tells you when the first approach of the day comes and from when it gets quiet in the evening. The legal background is in the article on the night flight ban at German airports.

5. Which types fly over which place

Because many portals show the aircraft type, you can check whether widebodies take a different departure route than short-haul jets. That often happens because long-haul flights have different destinations and therefore use different departure routes.

Examples: portals at well-known airports

The landscape is varied, and names, addresses and functions keep changing. The following examples reflect the state as of October 2026, as far as it could be verified on the official pages.

Frankfurt: INAA and the runway direction forecast

Around Frankfurt Airport, the Environment and Community Center (UNH) is the first address. Its application INAA shows arrivals and departures on the map, with callsign, speed, altitude and departure and destination airports on click. The track is colored by altitude. In addition there are monitoring stations of Fraport, municipalities and the UNH itself, whose level curve you can match to an overflight. The UNH expressly points out that the application serves demonstration purposes.

Almost more valuable for spotters is the forecast of the runway direction in use on the same website. It shows whether Frankfurt is operating westbound (runway direction 25) or eastbound (runway direction 07) and gives probabilities for the coming days in eight-hour blocks. The forecast is based on the GFS weather model and is updated three times a day. According to the UNH, the first three days are mostly very reliable, the last two a tendency. That way you know early whether the trip to the Zeppelinheim viewing platform or a spot at the other end of the runways is worth it.

Munich: Fluglärmüberwachung-Online

Munich Airport offers current readings and traffic data under the name Fluglärmüberwachung-Online (aircraft noise monitoring online). In addition, the website has an archive of measurement results from past years and an overview of mobile monitoring stations in the region. What is mainly interesting for spotters is which monitoring stations register overflights at which runway direction – that shows you where the routes run close to public paths. It naturally does not replace the local classic, the Munich Airport visitors’ hill (Besucherhügel), but supplements it with spots outside under the approaches.

Independent: Deutscher Fluglärmdienst

Besides the airports there is the Deutscher Fluglärmdienst (DFLD), a nonprofit association that publishes noise measurements and flight tracks and whose archive goes back to 2002. The network comprises hundreds of stations in several countries, including regions around Frankfurt, Berlin, Munich, Hamburg, Cologne/Bonn and Düsseldorf. The association sees itself as an advocacy group against aircraft noise – the data is still viewable by anyone and helpful for route analysis.

Australia: WebTrak nationwide

WebTrak is especially extensively developed in Australia. Airservices Australia runs it for numerous airports, from Sydney Airport through Melbourne and Brisbane to Perth. Besides live view and replay, it has so-called flight track swaths: they show typical routes filtered by weekday or weekend and by day, evening or night, over a month, a quarter or a year as desired. For a spotting trip to Sydney, that tells you in advance when the approaches run over Shep’s Mound and when they probably do not.

More airports

Numerous airports in Europe and North America also use WebTrak or comparable systems, for example London Heathrow Airport. The fastest way to find the right portal is to search the airport’s website in the environment, community or noise section. Terms such as “flight tracks,” “aircraft noise monitoring,” “flight tracking” or “noise” usually lead straight there.

From noise portal to spot: step by step

Here is how to use a flight track portal very concretely to find a new spot outside the airport fence.

For step 5, the guide to the sun position at the photo spot helps. For step 6 you will find suitable tools in the comparison of flight tracker apps and the unfiltered community trackers.

Limits and pitfalls

A few more points you should keep in mind:

• Not every flight is visible. Depending on the portal and data source, individual flights can be missing or incomplete. Airservices Australia, for example, hides police, rescue and military flights for security and operational reasons. What does not show up may still have flown.
• Callsign is not registration. To match a specific aircraft, you compare the time with a flight tracker history. How that works is explained in the article Matching sightings with ADS-B.
• Under the route is not automatically a spot. Many areas under approaches are private land, nature reserves or restricted zones. What is allowed is in the article Is plane spotting allowed?, and what to watch for directly under the approach in the guide Spotting under the approach path.
• Noise is everyday life for others. The portals exist because people live under these routes. Don’t park in front of driveways, be quiet in residential areas and protect your own hearing too – more under Aircraft noise and your hearing.

Conclusion

Aircraft noise and flight track portals such as WebTrak are made for residents but are a small treasure for spotters. Based on radar or transponder data, they show where aircraft actually fly around an airport, how high they are and which runways are used at what time. They do not replace live spotting because of the built-in delay. In hindsight, though, they are ideal for finding new spots under arrival and departure routes and for planning the focal length in advance. Combined with runway direction, light planning and live map, this makes for preparation that leaves little to chance.