September 2012

Low Moor How update

I have recently had correspondence with the Countryside Access Adviser at LDNPA who has thrown a bit more light on the reason problems at Low Moor How. This is what he told me: Unfortunately you have come across a long standing issue that we have been trying to resolve for some years, albeit unfruitfully.
 
The situation at Moor How is rather complicated – although nothing is actually legally wrong, it is just confusing and, to a lay walker, illogical – which is why we are trying to sort something out with the various landowners in the area.
 
The attached map shows the legal line of the footpaths in the vicinity.  It also shows the extent of the public road (U5252), which are the brown squares along the road running to the north-east. 
 
You can see that there is no legal link between the two (footpath and public road).  This does, at first sight, seem totally illogical – because you would think that the footpath must have led from the road end through the farm yard.  But there is an explanation.  And that is that the footpath was there first - it was claimed in the early 1950s when the definitive map was first drawn up, and at that time the road to Moor Howe had no public status at all, it was merely a private farm track.  It was then improved under the Agricultural Improvement Acts from 1955 onwards.  Basically, these Acts were to improve agricultural efficiency after the war by improving access to farms for things like milk tankers and other heavy plant.  The deal was that the County Council would substantially contribute to the road being tarmacked, but on the condition that it then became public.  The other side of the coin was that the landowner contributed at the time, but then had future maintenance done by the County.
 
So – the road was improved just to the farm because that was what was needed for access – with no link made to join the public footpath to it.  'High_Moor_How_footpath.jpg

He goes on to say that they have tried several times to get a link established and are still working on it.

We would suggest therefore that until this is resolved one of the alternative routes is used instead.