Rowanbank aviation report — September 2026, 9–30 September
Coverage begins at 17:48 on 9 September and ends at 23:20 on 30 September: 22 days, not a full calendar month. The 3,124 merged visits are a deliberately selected set of interesting sightings, with routine scheduled traffic and much ordinary Heathrow and Luton activity excluded. Percentages therefore describe this collection, not all aviation around Rowanbank. Route labels are tracking-service enrichment and may be inferred rather than filed flight plans.
September’s strongest story began with an absence: RAF Brize Norton’s runway was closed, and Britain’s air-mobility fleet was operating through a dispersed network of alternative airfields. Against that altered background, Rowanbank recorded a conspicuous stream of Voyagers, Atlas A400Ms, C-17s and other military or government aircraft.
Closer to home, another pattern was just as persistent. Light aircraft threaded the constrained space between Heathrow and Luton, often around 1,800–2,000 feet and within little more than a kilometre of the reference point. Business jets supplied the largest category numerically, but the most revealing sightings were those that broad database labels obscured: command-support Envoys, a signals-intelligence RC-135W, specialist survey aircraft and a government Boeing 767 with an unusual history.
Air mobility without Brize Norton’s runway
Military-tagged traffic accounted for 348 visits, or 11.1% of the selected sightings, and involved 144 aircraft. The numbers included 44 Airbus A330 visits, 36 A400M visits and 34 C-17 visits. These were not isolated curiosities but a recurring layer of heavy transport activity across the period.
The wider explanation is Project MACE. RAF Brize Norton’s runway was unavailable from 25 July until 15 November for resurfacing, requiring roughly 40 Air Mobility Force aircraft to continue operating from elsewhere. Prestwick and Boscombe Down were the principal alternatives, with East Midlands, Stansted and Bournemouth also supporting operations, according to the Royal Air Force’s account of Project MACE and its Brize Norton passenger information.
That does not make every Rowanbank military track a Project MACE flight, nor does it establish an individual aircraft’s temporary base. It does, however, explain why the normal operating geography of the fleet was unusually fluid throughout the observation period. Aircraft habitually associated with Brize Norton were moving within a broader network, making familiar types appear in less familiar flows.
Exercise activity added another possible influence. Cobra Warrior 26-2 ran from 14 September to 2 October, with official descriptions including Voyager and wider Air Mobility Force participation, as well as A400M capability. It is reasonable context for some second-half movements, but there is no public serial-by-serial sortie list connecting individual Rowanbank tracks to the exercise. The exercise dates and participants are described in the RAF’s homeland-defence exercise report and Cobra Warrior overview.
The same restraint applies to an overseas deployment announced during the period. On 13 September, the RAF reported that a 70 Squadron A400M had deployed to Powidz in Poland for tactical low-level flying, temporary-runway operations, airdrops and vehicle loading with the Polish Air Force. That supplies useful contemporary context for the type, but no published tail number links any particular Rowanbank Atlas to the deployment (Royal Air Force).
One late-period match is unusually persuasive. At 22:15 on 30 September Rowanbank recorded Voyager ZZ332 using the callsign RRR2232. The official Brize Norton listing showed RR2232 at 21:00 that evening as the South Atlantic schedule under Project MACE. The matching date and flight number strongly support that scheduled-airbridge context, although they do not establish the complete route, cargo or anyone aboard.
Voyager itself is more than a generic A330. It is the RAF’s multi-role tanker transport, operated with 10 and 101 Squadrons; the KC2 has two underwing refuelling pods, while the KC3 adds a centreline hose. The RAF also states that AirTanker owns, manages and maintains the fleet under the service arrangement (Royal Air Force). That documented structure is more informative than an “unknown owner” field and should not be replaced with speculation.
The low-level river between Heathrow and Luton
The heavy transports were the period’s strategic story, but the most immediate local pattern belonged to much smaller aircraft. Rowanbank recorded 844 visits that came within 2.5 kilometres while below 6,000 feet. Their median closest horizontal offset was 1.246 kilometres and their median altitude at that point was 1,875 feet.
Two origin labels dominated this flow. “London QKE”, associated in the dossier with Elstree, appeared on 237 visits by 64 aircraft; those tracks had a median closest offset of 1.249 kilometres and a median closest altitude of 1,800 feet. Denham accounted for 216 visits by 52 aircraft, with corresponding medians of 1.182 kilometres and 1,875 feet.
This is consistent with the geography of local general aviation. A Civil Aviation Authority planning document describes the narrow Heathrow–Luton gap containing Elstree and Denham as important both for local flying and east–west transit, beneath a nearby London Terminal Manoeuvring Area base of 2,500 feet. Elstree advertises general-aviation, rotary and flying-school activity, while Denham hosts aeroplane and helicopter training, maintenance and aerial-filming businesses. Together, those sources explain why so much legitimate general aviation may be concentrated into a relatively confined slice of sky (CAA airspace assessment, London Elstree Aerodrome, Denham Aerodrome).
They do not prove that every movement was instructional. Private travel, positioning, maintenance and other work can create similar tracks. Even so, recurrence among recognisable training types was striking. Piper PA-28 variants produced 165 visits and Cessna 152s another 131. Individual aircraft repeatedly followed the same broad local pattern: Denham-based Cessna G-BNSN appeared 18 times, while G-BRBP appeared 15 times. G-OLEA, a Piper associated in the data with the London School of Flying, made 11 visits with a median closest offset of one kilometre and median altitude of 1,800 feet.
The secondary origin clusters tell a similar story. Oxford contributed 36 visits, Turweston 26, North Weald 19, Stapleford 13 and Wellesbourne 12, generally passing at median altitudes of roughly 1,750–2,100 feet. CAA records and airfield material confirm substantial training infrastructure across those locations, making training and cross-country flying credible contributors without assigning that purpose to every flight (CAA flying-school directory, Turweston Flying Club, Wolverhampton Airport flight schools).
Some tracks passed exceptionally near the reference point in plan view. Twenty-one came within 100 metres horizontally, 177 within 500 metres and 363 within one kilometre. On 20 September, a Cessna 152 track’s closest offset rounded to zero at 2,825 feet; earlier that afternoon, a Discus-2cT glider passed within about six metres horizontally at 1,375 feet. These are horizontal offsets, not slant-range measurements, and ADS-B geometry alone says nothing about compliance with flying rules.
One aircraft neatly embodied the repeated local pattern. Diamond DA42 G-OATK was seen 30 times—second only to a Pilatus PC-24 in the recurrence table—with a median offset of 1.196 kilometres and altitude of 1,862.5 feet. Its enriched origin labels included Elstree, Oxford and Turweston. That combination suggests repeated use of the same constrained regional airspace, but not the purpose of any individual sortie.
Northolt, the Envoys and mixed-purpose traffic
Northolt-origin labels formed a smaller but distinct cluster: 28 visits involving 26 aircraft. Their median closest offset was only 300 metres, though at a substantially higher median altitude of 5,737.5 feet. Two Challenger 350 tracks illustrate the geometry, passing within roughly 29 and 45 metres horizontally at 4,925 and 5,850 feet respectively.
Northolt should not be treated as shorthand for ministerial or royal transport. The RAF describes it as its strategic London site and the home of Command Support Air Transport, but also explicitly says that it serves military and civilian aircraft and that commercial movements are a significant part of its traffic (RAF Northolt). The diversity—26 aircraft across 28 origin-labelled visits—supports that mixed picture.
The period did, however, include repeated appearances by the two government-operated Falcon 900s G-ZABH and G-ZAHS: 21 and 19 visits respectively. Calling them merely business jets misses their actual role. They are RAF Envoy IV CC1 aircraft, the service designation for Falcon 900LX airframes operated from Northolt by 32 (The Royal) Squadron. Their published task is Command Support Air Transport: the secure and timely movement of high-priority military personnel and small quantities of mission-critical freight (RAF Envoy IV CC1 and full-service capability announcement).
That role is important context, not a passenger list. Rowanbank establishes that the aircraft were observed; it does not establish who or what was aboard. The two Envoys also demonstrate why classification totals need interpretation: their 40 combined visits sit within the “business jet” category even though their service role belongs in the government and military story.
Business aviation as the statistical foreground
Business jets made up 1,625 visits, or 52% of the selected dataset. Bombardier Global-family and Gulfstream codes occupied four of the six leading type positions: GLEX recorded 244 visits, GLF6 177, GLF5 145 and GL7T 116. Dassault Falcon 7X and 900 types added 87 and 78 respectively.
Those numbers are substantial, but they primarily reveal the design of the collection. LADD-tagged aircraft accounted for 1,957 visits, or 62.6%. LADD is a privacy and display status, not evidence of suspicious activity. Because privacy-filtered and otherwise interesting aircraft are deliberately retained while much routine airline traffic is not, business aviation inevitably occupies more of this report than it does of the complete local sky.
The same caution applies to ownership fields. “Unknown”, “private owner” and “unknown owner” together covered most visits with operator information, while trustee registrations appeared prominently among the named entries. A trustee shown in registration data is not necessarily the beneficial owner, and the report does not attempt to look through such structures.
The most frequently recorded individual aircraft, Pilatus PC-24 M-ARNZ, appeared 31 times, but its median closest point was 21.1 kilometres away at 15,725 feet. By contrast, the repeatedly seen DA42 G-OATK was normally close and low. Recurrence alone therefore says little about local prominence: an aircraft may repeatedly cross the receiver’s wider coverage area without becoming part of the immediate Rowanbank soundscape.
Helicopters supplied another 236 visits. The AW139 was the leading helicopter type with 69, including 24 visits by T7-LSS at a median altitude of 1,737.5 feet and median offset of 6.6 kilometres. Sikorsky S-76 G-FXVA appeared ten times much closer, with medians of 682 metres and 1,262.5 feet. As elsewhere, these observations establish aircraft and tracks, not occupants or mission purpose.
Specialist aircraft hidden by broad labels
Some of the most interesting September records were aircraft whose roles were poorly conveyed by generic classifications.
On 17 September, Rowanbank observed ZZ666. The database’s “other aircraft” label conceals an RC-135W Rivet Joint, one of three in RAF service and operated by 51 Squadron from Waddington. The type intercepts and analyses signals across the electromagnetic spectrum to provide strategic and tactical intelligence (RAF type profile and fleet identification). Its appearance identifies a specialist intelligence platform; it does not reveal what it was doing, where it had been operating or any collection target.
The Bioflight aircraft OY-VPE and OY-VPS require a different correction. They appeared under the dataset’s warbird or historic grouping, but Bioflight operates P.68 aircraft for visual and digital surveys, environmental monitoring, mapping and inspection. Their low, slow tracks and Oxford enrichment are compatible with survey operations, though no customer, contract, sensor payload or surveyed feature can be established. Bioflight currently lists OY-VPE as a P.68 Observer 2 and OY-VPS as a P68C, while an earlier brochure described VPS as an Observer 2, so its precise sub-variant remains uncertain (Bioflight overview, fleet page, survey operations, 2021 brochure).
That correction matters to the reported total of 15 “warbird / historic” visits. At least some entries in that category were working survey aircraft rather than heritage machines, so the headline count should not be read literally as 15 historic-aircraft movements.
Notable sightings
A9C-HMH appeared only once and at cruise altitude, but its history makes it one of the period’s more unusual airframes. It is a VIP-configured Boeing 767-400 operated by Bahrain Royal Flight rather than an ordinary airline service. Fleet records identify it as construction number 34205, formerly N526BA—the commercial 767-400ER acquired as the intended test airframe for the subsequently abandoned US E-10A surveillance programme (Planespotters.net, US Government Accountability Office). Nothing in the sighting identifies its occupants or journey purpose.
At the opposite end of the scale, 24 September brought a Piper J-3 Cub within 100 metres horizontally at 1,100 feet. Its presence alongside modern Globals, Voyagers and intelligence platforms captured the extraordinary technological spread within this selected traffic: aircraft separated by role, speed and operating environment sharing the same broad patch of sky.
One visit by 9H-VCE carried the dataset’s sole emergency 7700 marker. The available evidence does not establish the cause, seriousness or outcome, so no narrative has been constructed around it.
What this period suggests
The 22-day record shows two overlapping aviation landscapes.
The first was local and repetitive: light aircraft from Elstree, Denham and a wider network of training airfields moving through constrained airspace, commonly around 1,800–2,000 feet. This layer produced most of the genuinely close passes and many of the aircraft that residents could encounter repeatedly.
The second was strategic and more geographically fluid. Project MACE changed the normal pattern of RAF air mobility for the entire period, while Cobra Warrior and overseas A400M training supplied relevant—but not aircraft-specific—context. Voyagers, A400Ms, C-17s, Envoys and the Rivet Joint gave the period an unusually strong government and military character.
Between those layers sat the selected dataset’s statistical foreground: privacy-displayed business jets, helicopters and specialist civil aircraft. Their prominence is real within Rowanbank’s chosen sightings, but it is not a census of all traffic. The value of the record lies less in ranking categories than in seeing how different aviation systems converged: local training and transit below controlled airspace, government movements from Northolt, dispersed military logistics, survey work and long-range business aviation.
About the data
The report is based on 3,124 distinct visits after merge-window processing, representing 1,233 registrations and 1,127 ICAO hex codes. Local ADS-B supplied 2,310 visits, 443 were present in both local and FR24-derived data, and 371 came from FR24 alone. Reasons can overlap, so their percentages do not sum to 100%.
External context is limited to the linked research sources above. Origin and destination labels are enrichment rather than confirmed flight plans; zero telemetry values were not interpreted as landings or ground stops. Closest distances are horizontal offsets from the Rowanbank reference point, and tracked positions alone do not demonstrate breaches of flying rules. This remains a selected, partial-period report—not a count of all local aviation during September.