Reading conditions is the skill that separates a pilot who survives from a pilot who thrives. Anyone can learn to fly a paraglider. The physical skills of inflation, launch, and landing are teachable in days. Reading the sky — deciding whether today is a coast day or an inland day, whether it is a thermal XC day or a ground-handling day, whether the conditions will be better at 11am or at 2pm — that takes years. This article is my attempt to compress some of that into something useful.
The Night Before — Forecast Tools I Use
My weather reading starts the evening before any flying day, not on the morning drive to the site. By the time I am in the car, I want to have a clear mental model already formed — so that everything I see on the drive and at the launch is confirming or updating that model, not building it from scratch.
I use three tools, in this order. First: Windguru. For coastal flying around Sesimbra, Windguru is the most useful forecast I have found — specifically the marine forecast, not the standard one. The marine model captures the sea-breeze dynamics and the coastal gradient wind more accurately than the general forecast. I am looking at wind direction, speed, and gusts across the flying window (typically 10am to 4pm), and I am noting how the numbers evolve through the day. A forecast that shows a gradual acceleration from 12 to 20 km/h through the morning is telling me something very different from one that shows 25 km/h from 9am and holding there.
Second: Windy at the 925 hPa pressure level. This is roughly 750 metres above sea level — which is close to typical cloudbase height on a good thermal day around Sesimbra. Looking at the surface forecast alone gives you the gradient wind, but it doesn't tell you what the air is doing at the height you will actually be flying in. The 925 hPa layer shows me whether the wind at altitude is aligned with the surface wind or diverging from it, and how strong it is. A significant difference between surface and 925 hPa wind direction is often a sign that the thermal layer is capped and the day will be more compressed than it looks.
Third: Meteoblue Sounding. The atmospheric sounding gives me the full vertical picture. I am looking at three things: the CAPE value (Convective Available Potential Energy — a direct measure of how energetic the thermals will be), the convective inhibition layer (a stable layer that can suppress thermal development until the surface heats enough to break through it — a low inhibition value means thermals start early; a high one means a slow start or a blue day), and the lifted index. A lifted index below −2 on a summer afternoon in the Alentejo means the thermals will be strong and potentially rough. Above 0 means weak thermal conditions.
I look at all three the evening before and then again at 06:00. If the three tools are consistent with each other, I have high confidence in the day's character. If they diverge — Windguru saying 15 km/h while Windy shows 28 km/h at 925 hPa, for instance — I read that disagreement as uncertainty and plan for flexibility. A day I cannot confidently read the night before is one where the morning assessment at the site becomes critical.
On the Drive to the Site — What I Am Looking For
The drive to the launch is active data collection. I am watching three things from the moment I leave the city.
Vegetation movement. Trees swaying at what I estimate to be 10–15 km/h tell me the gradient wind is established and working. Completely still trees on a day that was forecast for 18 km/h means the sea breeze hasn't filled in yet — and I adjust my expected launch time accordingly. The trees in the Arrábida Natural Park along the N379 are particularly useful because they are exposed enough to respond clearly to even moderate gradient winds.
Smoke or steam from coastal industries. The direction smoke is blowing from any coastal factory or burning gives me the actual surface wind direction at that point — not a model prediction but a real observation. I check this against my forecast. Agreement is reassuring. A significant mismatch tells me to look more carefully at what else might be different.
The sea surface texture from the motorway bridge above the Tejo. Flat, glassy water means calm — under 8 km/h at the surface. A textured surface with small ripple lines tells me 10–15 km/h. Whitecaps appearing means the wind is above 15 km/h and possibly building. By the time I park at the launch, I have already updated my mental model from everything I saw on the drive. Most days I know roughly what I am going to find before I arrive.
At the Launch — The 10-Minute Assessment
I spend ten minutes at the launch before inflating anything. This is not optional — it is the most important ten minutes of any flying day. The launch is where every variable comes together: wind speed, wind direction, consistency, the quality of the air above, the state of the landing zone, and what any other pilots or birds in the air are telling me about conditions that already exist.
I watch the grass movements across the launch slope. I watch the streamers — not just the direction they are pointing, but the variation in that direction over time. A flag that is generally pointing on-shore but oscillating 30 degrees either side every few seconds is telling me the wind is variable and turbulent. A flag that is rock-steady at 15 km/h is telling me the flow is laminar and reliable. For coastal soaring especially, consistency matters more than speed. I would rather fly in a steady 20 km/h than in a gusty 12 km/h that is swinging 40 degrees.
I check the cloud base height if there are cumulus present — estimating by angle relative to a known terrain feature. I watch whether cumulus are gently bubbling (good: active but controlled) or already showing flat grey undersides and vertical height (a warning sign). I look at the horizon haze. A crisp horizon means clean, dry air. A milky horizon in summer Portugal often means humidity is building and the afternoon may develop more quickly than the morning suggests.
If there is another pilot already in the air, I watch them. Their position relative to the ridge tells me where the soaring band is. Their altitude gain rate (estimated) tells me whether the lift is smooth or punchy. If they are hopping around and making big altitude corrections, the air is textured. If they are sitting in a steady bank without dramatic up-and-down movement, it is clean.
Reading the Coastal Conditions for Ridge Soaring
For coastal soaring at Sesimbra, the sweet spot I am looking for is 10–25 km/h from N/NW — the nortada direction — with less than 30 degrees of directional variation. Below 10 km/h, the soaring band is too shallow and the wing response too soft. Above 25 km/h, the energy increases and the site becomes demanding; above 35 km/h, most coastal sites here are for experienced pilots only or are not appropriate for soaring at all.
Once I have decided conditions are suitable, I do a brief inflation check before committing to flight. I inflate the wing overhead and hold it there for 10–15 seconds, feeling it. A wing that sits steady above me with even pressure on the A-risers is telling me the air overhead is consistent. A wing that rocks, surges forward, or drops on one side is telling me the air directly above the launch is turbulent — and I take more time before deciding to fly.
Landing zone assessment is part of the launch checklist, not an afterthought. Is the beach clear of people in the approach path? Is the wind close enough to on-shore that the beach landing is straightforward? At some Sesimbra sites, the landing in light cross-wind is genuinely more demanding than any part of the soaring flight — knowing this before launch matters. For more on reading the nortada specifically, see my guides on Portugal's summer wind and what it means for paragliders and coastal soaring and ridge lift.
Reading the Inland Thermic Sky
For XC flying in the Alentejo, my primary condition indicator shifts from the wind to the cumulus development. The clouds are the visible output of a process I cannot see directly — thermals rising from the sun-heated ground, cooling as they climb, condensing into cloud at the dew point. If I can read the clouds, I can infer the thermals below them.
What I am looking for: flat-based cumuli with white, well-defined tops. Flat base means the dew point temperature is consistent across the area — the thermals are reaching the condensation level at a predictable height. Ragged, patchy cloud bases mean the dew point is variable, the thermal cycle is inconsistent, and the XC conditions will be uneven and frustrating. Flat-based clouds are the sign of a well-organised day.
Cloud base height I estimate by looking at the cloud base angle relative to a known terrain feature — a ridge at a known height, a hilltop I know the altitude of. Above 1200 metres on a summer day in the Alentejo is reliable soaring. Above 1600 metres is an excellent XC day. Above 2000 metres on the right day — a light gradient wind, good sun, stable morning — means a long XC flight is possible and the energy in the sky is substantial.
The key warning sign I watch for is towering cumulus (TCu) — individual clouds that are taller than they are wide, with tops that are no longer clean white cauliflower but starting to go grey and fibrous at the edges. TCu means the convective process has gone into a stronger phase. The thermals underneath will be powerful, possibly violent, and the sky is moving towards a state that is not safe for XC paragliding. When I see TCu anywhere in the sky, I start thinking about landing options, not climbing options.
In the Air — Real-Time Reading
Once I am flying, condition reading shifts to two channels: the variometer and the wing itself.
The variometer's audio is a continuous stream of condition data, and experienced pilots learn to read it the way a musician reads rhythm. Strong beeping that starts abruptly and stops abruptly — a sharp-edged thermal — means the thermal has a well-defined boundary and is likely punchy at the edges. Centre it carefully and it will be a solid climb; enter it badly and the edge will be turbulent. A gradual build and fade in the vario tone means a round-edged thermal — smooth, wide, forgiving. These are the ones I love on an XC day. They are easy to centre and comfortable to stay in.
The wing tells me things the variometer doesn't. A sudden rise on one wingtip is the wing entering the edge of a thermal asymmetrically — perfectly normal, and the correct response is to weight the high side brake and enter a turn in that direction. The wing is pointing me at the core. An abrupt general surge forward on both sides means I have entered the thermal from below — the thermal is already well above me. A soft, progressive inflation of the trailing edge means I am in the smooth, laminar centre of a wide thermal: stay there and climb.
Every 15 minutes in the air, I do a sky scan. I look upwind for overdevelopment. I look at the cloud base height — is it the same as when I launched, or has it risen? (Rising cloudbase means the day is strengthening.) I look at the spacing between clouds — are they getting closer together (cells merging, the sky congesting) or staying well-separated (organised and stable)? This 15-minute check is a habit built over years. It has kept me out of situations many times.
Overdevelopment — The Most Important Threat to Read Early
Overdevelopment is the most serious meteorological threat in thermic paragliding, and the most important one to read early — because by the time it is directly overhead, the decision has already been delayed too long.
How it looks in the early stages: the flat cumulus bases I was happy with an hour ago start to go grey and wet-looking on the underside. The tops are no longer clean white cauliflower — they are darker at the top, with a faintly fibrous or anvil-shaped profile beginning to appear. Adjacent cells that were separated start to share a base and merge into a larger mass. The sky, which was a collection of individual clouds with blue sky between them, is starting to become a grey ceiling.
How it feels in the air: thermals that were climbing at 2 m/s are now doing 4 m/s or more. The sink between thermals deepens noticeably. The air has more energy — and that energy is no longer organised; it is becoming chaotic. The sky upwind has a grey, wet-looking quality even if it is not yet raining.
What I do when I see any of this coming: I land. Not when the overdevelopment is overhead — well before it arrives. My personal rule, built over 25 years of flying Sesimbra and the Alentejo: if the sky upwind of me has any sign of early overdevelopment, I find a landing field and I am on the ground within 15 minutes. Not 20. Not "let me climb a bit more and reassess." Fifteen minutes, on the ground. The XC distance I lose by landing early is never worth what I risk by staying up.
The Condition Reading Checklist
This is the actual sequence I run through before and during every flying day. It is not theoretical — it is what I do, in this order, every time I fly.
- The night before: Windguru marine forecast (wind speed, direction, gusts through the flying window), Windy at 925 hPa (wind aloft alignment and strength), Meteoblue Sounding (CAPE, convective inhibition, lifted index). Note whether the three models agree or diverge.
- At 06:00: Re-check all three. Has anything changed overnight? Is the timing of the sea breeze fill-in earlier or later than expected?
- On the drive to site: Vegetation movement, smoke or steam direction, sea surface texture from any elevated viewpoint. Update the mental model. Note any significant divergence from what was forecast.
- At the launch — 10 minutes before inflation: Streamer direction and consistency (30-degree variation = acceptable; more = concern). Grass and vegetation on the slope. Any pilots already flying (altitude, stability, wing behaviour). Cloud base height if cumulus present. Horizon haze quality. Landing zone assessment (clear, wind direction safe for approach).
- At inflation: Wing overhead — steady and even pressure means go; rocking, surging, or asymmetric means wait and re-assess. If the wing is not happy, the air is not ready.
- In the air, every 15 minutes: Vario quality scan (sharp-edged or round-edged thermals?). Cloud base height check (rising, stable, or dropping?). Upwind sky scan (any grey undersides, merging bases, TCu developing?). Overdevelopment threat level assessment — green, amber, or red?
| Condition | What I See | What I Do |
|---|---|---|
| Coastal 12–18 km/h steady N/NW | Sea surface textured, streamers pointing on-shore, wing sits steady overhead | Launch, enjoy standard coastal soaring |
| Coastal 25–35 km/h steady N/NW | Whitecaps on the sea, strong wing pressure overhead, active streamers | Fly exposed sites with caution; sheltered sites fine for experienced pilots |
| Coastal 35+ km/h | Sustained whitecaps, frothy surf, wind noise constant on the launch | Dunes or ground handling only — no ridge soaring |
| Inland thermic, 1200m+ cloudbase | Flat-based cumulus with white tops building steadily from 10am | XC day — launch by 11am, plan for 4–5 hours of flying |
| Inland thermic, TCu building | Cumulus tops darkening, cells merging, thermals accelerating beyond 4 m/s | Land now — overdevelopment arriving; no delay |
Reading conditions is not a pass/fail test you do once at the launch. It is a continuous process that runs from the evening before to the moment you land. The pilots who get into trouble are almost always the ones who made one good assessment early and then stopped looking. The sky changes. Keep reading it.