26/0565/TPOUndecided

245 Barkerhouse Road Nelson Lancashire BB9 9NL

Undecided

This application is awaiting a decision from the council.

Consultation period ended 11 days ago

The standard 21-day consultation window has passed. Late comments may still be accepted at the council's discretion.

Proposal

The proposed works are to remove an ash tree affected by ash dieback. The tree is showing signs of decline and is shedding/dropping limbs, presenting a potential safety risk to people and property. Removal is therefore considered necessary to address the risk posed by the tree as its condition deteriorates. It is also proposed to remove the adjacent Leylandii, which has become excessively large and dominant. Its dense growth is restricting light and resources, preventing other vegetation from establishing and growing effectively in the surrounding area. Removal of the Leylandii will improve light levels and allow the space to be replanted or naturally regenerate. Both trees are proposed for removal on the grounds of safety, tree health and the management of the surrounding vegetation. Happy to discuss if more information or clarification is required.

Received

23 August 2026

First tracked

31 August 2026

Last checked

04 September 2026

Location

BB9 9NL

Source & Council Register

Data source: PlanIt. The council register destination is shown separately from this data-source label.

Open council website
Open council register to comment

How to Comment on This Application

1

Find the application on the council portal

Use the "View original on council portal" button above to open the official planning register entry for this application.

2

Click "Make a Comment" or "Comment on this application"

Most council portals have a comment tab or button on the application page. You'll need to provide your name and address — anonymous comments are generally not accepted.

3

Write a material planning consideration

Comments must relate to planning matters — e.g. impact on neighbours, traffic, parking, design, or the local area. Personal objections (e.g. "I don't like the owner") are not considered. Be specific and factual.

4

Submit before the consultation deadline

The standard consultation period is 21 days from the application's received date. Late comments may still be accepted at the council's discretion, but are not guaranteed to be considered.

💡 Tip: Even if the consultation period has passed, you can still contact your local councillor or attend the planning committee meeting if the application is referred to committee. Check the council portal for meeting dates.

Open council register to comment →

Application Timeline

Loading history…
  1. Application received by council

  2. First tracked by Planning Alerts

Documents & Plans

Updated 4 Sept 2026
Loading documents from council portal…

Documents remain with Pendle Borough Council. External links open in a new tab.

Status alerts

Toggle on to get notified when 26/0565/TPO changes status.

Council

Pendle Borough Council

PEN

unknown portal

Save for Later

to save applications

Share

Share with Neighbours

Let your neighbours know about this application before the consultation deadline.

My Notes

to add private notes

Community Discussion

to join the discussion

No comments yet. Be the first to share your thoughts.

Data Sources & Attribution

Official UK government planning data platform. Planning applications, listed buildings, conservation areas, flood risk zones, and more.

PlanIt.org.ukRights review

UK planning applications aggregator covering 420 local authorities. Used as a fallback data source for councils not yet on the official feed.

Planning application information accessed from council portals. Individual councils and portal providers may have separate reuse terms.

Listed buildings and scheduled monuments data via PlanningData.gov.uk.

Planning Alerts combines Planning Data records with information from council portals and other sources. Planning Data-sourced records are used under Open Government Licence v3.0 attribution. Other sources may have separate terms and are not enabled for commercial API, export, paid-alert or professional workflows until their rights are verified.