flood · KenyaNairobi · signal: tail

Nairobi River flash flood — March 2026

  1. Act I — Understanding the eventWhat is happening?
  2. Act II — Belief updating & riskWhat do we think is happening?
  3. Act III — Decision & reflectionWhat should we do and why?

Round 1 / 3: Early monitoring (T-5) (2026-03-01)

Event window: 2026-03-012026-03-06 (daily)

Engine state: Moderate risk / Evaluate (Yellow) — saturated ground, mean forecast still modest

Nairobi admin-1, early March long-rains onset. Dense informal settlements along the Nairobi/Mathare/Ngong river corridors are exposed to flash flooding. Ground is already wet from late-February rain. You are the DOC duty analyst on Mar 1.

Evidence

  • Soft evidence 7-day antecedent rainfall (IMERG)
    135 mm -> Saturated [scripted]
    BN node: antecedent_rainfall
  • Soft evidence Ensemble-mean exceedance prob (ECMWF P_heavy)
    Low [scripted]
    BN node: exceedance_prob
    The MEAN looks benign. Do not stop here.

Act I quiz — build the evidence inventory

Every answer becomes an input to the risk model: evidence → classification → confidence → belief update → decision. Not scored.

Q1. The rainfall outlook for Nairobi comes from the ECMWF ensemble (many parallel model runs, updated daily). First, the basics: what is a DETERMINISTIC forecast?

BN purpose: Forecast literacy — why a single number is not enough for risk decisions.

Q2. And what is an ENSEMBLE prediction system (EPS)?

BN purpose: Why forecasts are SOFT evidence in the BN — the spread is the confidence.

Q3. What is the strongest evidence currently available?

On your desk this round: 7-day antecedent rainfall (IMERG) · Ensemble-mean exceedance prob (ECMWF P_heavy)

BN purpose: Determines which BN node receives the highest weight.

Q4. Classify that evidence.

Check the tags on the evidence cards: 7-day antecedent rainfall (IMERG) · Ensemble-mean exceedance prob (ECMWF P_heavy)

BN purpose: Determines confidence weighting — hard = observation (one-hot), soft = probability vector, virtual = likelihood message.

Q5. How reliable is this evidence?

Nairobi is a TAIL-risk case — the ensemble mean can look benign while a few members carry the danger; weigh the tail, not the average. Reliability sets how hard the BN leans on it.

BN purpose: Evidence likelihood weighting.

Q6. What hazard condition does this evidence support in Nairobi, Kenya?

Which mechanism fits Nairobi — slow river rise, sudden flash runoff, or urban-drainage overload? The mechanism decides which impacts follow.

BN purpose: Updates the hazard node.

Q7. Which impact pathway is most likely here?

Nairobi admin-1, early March long-rains onset. Dense informal settlements along the Nairobi/Mathare/Ngong river corridors are exposed to flash flooding. Ground is already wet from late-February rain. You are the DOC duty analyst on Mar 1.

BN purpose: Updates the impact node.

Q8. What evidence would you request next?

Still off the table this round: Ensemble-max / 2-yr RP, pixel p95 · Spatial coverage of heavy-rain pixels · Yesterday's risk posterior carried forward (DBN, alpha=0.6) · Observed rainfall / river response. Which would most reduce your uncertainty before you decide?

BN purpose: Real DOC operations seek more evidence — watch which cards the Act II rounds reveal.

Q9. On 1 March 2026 the 7-day antecedent rainfall over Nairobi is about 135 mm and the ground is saturated, while the ensemble-mean forecast still looks modest. Why does the antecedent evidence alone justify stepping up vigilance?

The brief notes the ground is already wet from late-February rain.

BN purpose: Why the antecedent_rainfall node shifts the flood prior before any forecast node fires.

Q10. At T-2 (4 March 2026) the ensemble mean is only about 18 mm, but the worst ensemble member gives 131 mm and the p95 ensemble-max ratio crosses the 2-year return period (1.11). What is the correct reading of this split?

Mean and tail are answering different questions.

BN purpose: Why the tail_risk node, not exceedance_prob alone, is the decisive evidence for tail-forecastability events.

Q11. Your current risk estimate — before the model runs?

Nairobi is a TAIL-risk case — the ensemble mean can look benign while a few members carry the danger; weigh the tail, not the average. No model has spoken yet — commit your own read so Act III can compare it to the engine.

BN purpose: Your pre-BN estimate. Act III compares it against the engine risk indication.

Q12. Recommended DOC status — commit now, before seeing the BN output.

At T-2 (Mar 4) the ensemble MEAN is benign but the tail crosses the 2-yr RP. What DOC level do you set, and why? A 'Watch + 24h re-check + note the tail uncertainty' is a strong answer.

BN purpose: Your pre-BN decision. Act III compares it against the CRMA state.

Q13. The risk model you are about to work with was built from expert rules, not calibrated against decades of events. How much should you trust it?

No right answer — your stance is revisited in Act III against what the model actually did, and what history recorded.

BN purpose: Hold this question. Act III returns to it.

DroughtEM-DAT Disaster Events

Monthly Event Frequency (Daily, 2026-03-01 → 2026-03-06, KEN only)

Affected Regions

Admin1 Frequency Choropleth

scroll / pinch to zoom · drag to pan