Blocked Drains in Midhurst
Midhurst's separate sewer system presents unique drainage challenges compared to towns with combined networks. Surface water drains and foul drains run independently across most of Midhurst, meaning misconnections—such as washing machine outlet pipes discharging into the surface water network—create serious blockages. This configuration is particularly common in Midhurst's Victorian and Edwardian properties (GU29 and GU30 postcodes), where original drainage layouts haven't been updated to account for modern appliances.
In Midhurst, blocked drains often result from misconnections in the separate sewer system, where washing machines or waste pipes are incorrectly plumbed into surface water drains. Diagnosis requires inspection of both foul and surface water networks to isolate the source and restore correct discharge pathways.
Drainage in Midhurst — what local engineers know
Thames Water supplies Midhurst and the surrounding West Sussex area. Chichester District Council's drainage enforcement team regularly investigates misconnection complaints in Midhurst, as cross-connections between foul and surface water systems can trigger environmental action. The separate sewer configuration is efficient when correctly installed, but Midhurst's mix of Victorian terraces, Edwardian villas, and newer developments means individual properties vary significantly in their drainage setup. Properties in GU31 and GU32 often have rural characteristics, with longer drainage runs that collect debris and root intrusion more readily than denser urban areas.
- Hard water supply causes limescale accumulation in boilers, radiators and soil pipe joints — powerflush and descaling demand is high across Midhurst
- Separate sewer system across most of Midhurst: misconnections (e.g. washing machines plumbed into surface water drains) are a known local issue and can result in environmental enforcement action
- Ageing infrastructure in parts of Midhurst means drain blockages from grease, wipes and root ingress remain the most common call-out reasons
- With 34% of properties built before 1920, salt-glazed clay drainage and lead-solder copper pipework are common — pipe collapse, root ingress and joint failure are recurring call-out drivers.
What happens when you call us in Midhurst
- 1 Immediate dispatch. We find the nearest available engineer covering GU29/GU30 and confirm the ETA before the call ends.
- 2 On-site diagnosis — no guessing. The engineer inspects using professional-grade equipment including CCTV where needed and quotes a fixed price before work starts.
- 3 Job complete, report issued. You receive a written completion report. All work is guaranteed — same fault returns within the guarantee period, we come back free.
Who's responsible for drains in Midhurst?
In Midhurst, responsibility for a blocked or damaged drain depends on where the fault sits. As a homeowner you are responsible for the drains within your property boundary that serve only your home. Since the 2011 private sewer transfer, Thames Water is responsible for shared sewers and lateral drains beyond your boundary — even where they run under private land. Road gullies and highway drainage are maintained by Chichester.
This matters because it determines who pays. If our engineer's CCTV inspection shows the fault is in a shared sewer, we'll tell you — and you can report it to Thames Water rather than paying for the repair yourself. The separate sewer layout that dominates Midhurst affects where these boundaries typically fall, and our local engineers know the GU29, GU30, GU31 networks well enough to identify ownership quickly.
Blocked Drains prices in Midhurst
Every Midhurst job is quoted as a fixed price before work starts — what we quote is what you pay, with no call-out fee for providing the quote. The final price depends on access (an external inspection chamber is quicker than internal-only access), the pipe material and condition , and how established the blockage or fault is. Request your free quote and we'll confirm the price and your engineer's ETA in the callback.
