← All articles
Student pilots
23 September 20269 min read

Kisumu and Mombasa share the runway with scheduled jets. Wake turbulence is the bill your C172 pays.

Kenyan flying schools have moved training to Kisumu and Mombasa for calmer skies, but both aerodromes put light singles on the same runway as Kenya Airways and Jambojet. Here is what the wake behind those aircraft actually does, and how to fly around it.

A runway at first light, the same paved surface a light training aircraft shares with scheduled jets at Kisumu and Mombasa
John Murphy (CC BY-SA 2.0) via wikimedia

Wilson Airport and Jomo Kenyatta International sit close enough on a map that new students assume the two share traffic as well as weather. In practice Nairobi's two airports run almost separate operations, and a Wilson-based student can complete an entire course without meeting a jet on the same runway.

Kisumu and Mombasa give you no such shelter. Both put a Cessna 152 or a Piper Cherokee on the exact runway a Kenya Airways 737-800, an Embraer E190, or a Jambojet Dash 8 used ten minutes earlier, and that arrangement carries a hazard most Kenyan ground schools mention once and never revisit.

What a wake vortex actually is, and why it outlasts the aircraft that made it

Every aircraft generating lift sheds a pair of counter-rotating vortices off its wingtips. The heavier the aircraft and the slower it flies, the stronger those vortices roll, which means a jet in the landing configuration, gear down and flaps out, close to its maximum weight, produces close to the worst case right where you also happen to be flying.

The FAA Aeronautical Information Manual's wake turbulence guidance describes vortices sinking at roughly 300 to 500 feet per minute in the first thirty seconds behind the generating aircraft. They then level off, typically 500 to 900 feet below the flight path that produced them by the time they are several miles behind it, and can remain dangerous in the air for minutes rather than seconds in calm wind.

An aircraft the same size class as Kisumu's jets already killed people this way

It is tempting to assume only a true widebody is dangerous, and that assumption has already cost lives. Between December 1992 and 1994, five separate light and mid-size aircraft on approach encountered the wake of a preceding Boeing 757, with losses of control severe enough to be unrecoverable in a Cessna Citation, a Cessna 182, and an Israel Aircraft Industries Westwind, and thirteen people died across two of those accidents, according to NTSB Safety Recommendations A-94-42 through A-94-60.

The 757 is not a widebody. Its maximum take-off weight sits around 116,000 kilograms, in the same broad size class as the 737-800 Kenya Airways flies into Kisumu and Mombasa, yet post-accident testing found it generated stronger vortices than aircraft that outweighed it.

The FAA's response, effective from 1996, was to make controllers treat the 757 as if it were a Heavy for separation purposes, widening the following distance required for a light aircraft from 4 to 5 nautical miles.

The lesson for a Kenyan student is specific rather than general. A jet does not need to look enormous on the apron for its wake to roll a light single past its control authority.

The ICAO categories behind every jet you will share a runway with

ICAO sorts aircraft into wake turbulence categories by maximum certified take-off mass. Light covers 7,000 kilograms or less, which includes every training aircraft this article concerns.

Medium runs from above 7,000 kilograms to below 136,000 kilograms, Heavy sits at 136,000 kilograms and above, and Super is reserved for a short list of the largest aircraft flying.

Kenya Airways' 737-800s and Embraer E190s, and Jambojet's Dash 8-Q400 turboprops, all sit comfortably inside Medium. That classification alone tells you nothing about how strong an individual encounter feels from the cockpit of a C172, as the 757 case above proves.

Time-based separation minima built around these categories exist to protect the traffic ATC is actively sequencing, and they give you a sense of how seriously controllers already take the hazard. A light aircraft landing behind a Medium or Heavy aircraft needs three minutes of separation where no radar distance standard is applied, and a light aircraft departing behind a Medium aircraft needs two, figures drawn from the wake turbulence separation standards in FAA Order JO 7110.126A.

Those minutes belong to ATC's sequencing job, not to a warning system built specifically around your aircraft.

Kisumu and Mombasa are exactly where this stops being theoretical

Kenyan flight training has been quietly moving west and to the coast for a genuine reason. Kisumu International has drawn flying schools specifically because training flights there move faster and the sky stays clearer than Nairobi's congested basin usually allows.

What that relocation does not remove is the runway itself. Kisumu and Moi International at Mombasa both run scheduled Kenya Airways and Jambojet services over the same paved surface a training aircraft uses that same morning, and Moi International's long main runway, 03/21, is long enough to take a Boeing 747, a genuine Heavy by any classification, when a widebody charter or freighter needs it.

Wilson gives Nairobi-based students an unusual comfort: almost no jet traffic to plan around, because Nairobi's two main airports share very little operational overlap. Move your training or a cross-country leg to Kisumu or the coast and that comfort disappears, whether or not anyone briefs you on it.

Landing behind something heavier: the touchdown point rule

The single most useful piece of technique in the FAA's guidance is also the simplest. Note where the aircraft ahead of you touched down, then plan to land beyond that point rather than before it, because the vortices sink and drift from that aircraft's flight path, not from yours.

Flying a visual approach on or above the glidepath of the aircraft you are following, instead of cutting inside it to save time, keeps you above the level the vortices are sinking to rather than descending into them. Moi International's runway is long enough that landing well past a jet's touchdown point still leaves plenty of runway remaining, so use the length that is there.

Departing behind something heavier: the rotation point rule

The same principle runs in reverse for departure. Note the rotation point of the aircraft ahead of you, then plan to lift off before it, and keep your own climb path above its climb path until you can turn clear of its track.

This matters more than it sounds at a shared-runway aerodrome, because a training circuit often means turning crosswind close in, and that turn can carry you straight into a vortex still sinking from a jet that departed a few minutes earlier. Ask for extra spacing, or take it, rather than accepting the earliest possible departure clearance behind a jet that has just rolled.

Crosswind does not clear the runway, it just relocates the problem

A wind straight down the runway helps, because it tends to carry vortices off the extended centreline and to one side over time. A crosswind does something less helpful: it can hold the upwind vortex almost stationary directly over the runway while carrying the downwind vortex clear, which is precisely the trap for a pilot who assumes wind alone has already done the job.

Near the ground, vortices also spread apart and drift laterally at only a few knots, so a modest crosswind will not sweep them off the runway quickly. Treat any wake as still present until you have actually planned your own flight path around where it will have sunk to, rather than around where you hope the wind has carried it.

What ATC gives you, and what it does not

Kenyan controllers at Kisumu and Mombasa apply the same wake turbulence separation standards used everywhere, because Kenya's air traffic procedures follow ICAO practice. That separation protects the sequencing between aircraft ATC is actively spacing, which is not automatically the same protection a training aircraft doing circuits, or a cross-country arrival slotted between airline movements, receives.

If you are unsure how tightly you are being sequenced behind a jet, ask. A specific request, confirming spacing behind a departing 737, costs nothing and tells the controller you understand the hazard rather than assuming someone else is managing it for you.

Here is the opinion worth stating plainly. ATC separation exists to protect the aircraft the system is actively sequencing, not to personally protect your particular C172, and treating radar spacing as a safety net built around you is the laziest assumption a light-aircraft pilot can make at a shared-runway aerodrome.

If you fly into one anyway

The FAA's guidance is consistent on one point: if you encounter wake turbulence with enough altitude to work with, let the aircraft ride through the encounter rather than fighting it with full opposite aileron, then recover from whatever attitude results. Aggressive control input against a roll upset can worsen an encounter rather than end it.

Near the ground, on approach or shortly after take-off, that spare altitude does not exist, which is exactly why avoidance beats recovery every time at low level. A wake encounter at 500 feet on short final is not a scenario you fly your way out of through technique alone.

It is a scenario you avoid entirely by not being where the vortex sank to in the first place.

What pilots admit on the forums

Wake turbulence threads on pilot forums follow a predictable pattern. Nobody posts casually about a serious encounter, but plenty of pilots eventually admit to a moment when the aircraft rolled or dropped harder than gusty air alone explained, usually on approach behind something bigger they had not thought much about beforehand.

The common thread in those admissions is not ignorance of the concept. It is the gap between knowing wake turbulence exists in principle and actually clocking the touchdown or rotation point of the aircraft ahead in the moment, which is the one habit that turns theory into an avoided encounter.

The Short Version

  • Wake vortices sink and drift rather than simply vanishing, and they can persist for minutes behind a jet in the landing or take-off configuration.
  • A jet's ICAO weight category, Medium rather than Heavy, tells you nothing about how strong an individual encounter can feel. The Boeing 757 proved that with fatal accidents in the 1990s.
  • Kisumu and Mombasa both put light training aircraft on the same runway scheduled jets use, unlike Wilson's relative isolation from JKIA.
  • Land beyond a heavier aircraft's touchdown point and take off before its rotation point, staying on or above its flight path in both cases.
  • A crosswind will not clear a runway of wake quickly. It can park one vortex almost stationary over the centreline.
  • ATC separation protects the system's sequencing, not your aircraft specifically. Ask for clarification if spacing behind a jet feels tight.

AngaBrief's Environment section of a PAVE assessment asks a pilot to think through the specific hazards of a departure and arrival aerodrome rather than tick a generic weather box, and a shared runway with scheduled jet traffic is exactly the kind of factor that belongs there. The tool only records the assessment; it is not a dispatch authority, and the go or no-go decision always rests with the pilot in command and their instructor.

Key Takeaways

  • Note the touchdown or rotation point of any heavier aircraft ahead of you, then land beyond it or lift off before it.
  • Stay on or above the flight path of the aircraft you are following, never below and behind it.
  • Kisumu and Mombasa share runways with scheduled jets in a way Wilson does not, so brief for it specifically at those aerodromes.
  • If you do encounter wake with room to spare, let the aircraft ride through it rather than fighting the roll with full control input.
Tagged:wake turbulenceKisumuMombasarunway operationsjet trafficKenya

Ready to streamline your pre-flight risk process?

AngaBrief gives your flight school a structured PAVE/IMSAFE assessment workflow with an immutable KCAA-compliant audit log.