Planning Atlas
Planning Atlas›Bexley›…ST.MARY'S (HISTORIC 2018) ward›09/01200/FUL
Planning application · Bexley

09/01200/FUL.

361 Hurst Road Bexley Kent DA5 3DU

Full / Other Planning at 361 Hurst Road Bexley Kent DA5 3DU, received 7 Sep 2009 — approved on 15 Oct 2009 (delegated, Richard Turek).

Bexley›ST.MARY'S (HISTORIC 2018)›DA5 3DU›09/01200/FUL
ApprovedRefusedOther
At a glance · this applicationBexley profile →
Approved
Outcome
15 Oct 2009
5 wks
Decision time
inside the 8-week target
—
Conditions
not captured
0
Documents
on the council file
—
Objections
not captured
No
Appeal
none recorded
Record from the Bexley planning register as captured; documents link to the council's own files. Nearby applications are context, not part of this application.
Application

What is it?

First floor rear extension and alterations to front elevation.

Reference
09/01200/FUL
Type
Detailed Planning Application
Site
Applicant
Agent / consultant
Case officer
Postcode
DA5 3DU
Ward
Council
Received
7 Sep 2009
Target date
2 Nov 2009
Decision date
15 Oct 2009
Decision route
Delegated (officer)
Council register
Reference
09/01200/FUL
Type
Detailed Planning Application
Site
Show all 14 rows
Applicant
Agent / consultant
Case officer
Postcode
DA5 3DU
Ward
Council
Received
7 Sep 2009
Target date
2 Nov 2009
Decision date
15 Oct 2009
Decision route
Delegated (officer)
Council register
Documents

What was filed?

No documents are recorded for this application.

Documents open on the Bexley portal (the portal needs its documents tab opened first — the link handles that). View the application page ↗

Decision

What happened?

Approved on 15 Oct 2009, delegated decision by Richard Turek — 5 weeks from submission.

Timeline

Date
Event
7 Sep 2009
Application received
2 Nov 2009
Statutory target date
15 Oct 2009
Delegated decision: Approved · Richard Turek
7 Sep 2009
Application received
2 Nov 2009
Statutory target date
15 Oct 2009
Delegated decision: Approved · Richard Turek

Public response

Comment counts were not captured for this application.

People

Who is involved?

Name
Role
Applicant — the party who applied, not necessarily the owner
Agent · consultant profile
Case officer — delegated decision
Applicant — the party who applied, not necessarily the owner
Agent · consultant profile
Case officer — delegated decision
Place

What affects it?

Context around the site — not part of this application. Designations over the site: use the map's designations filter (conservation areas, listed buildings, Article 4, flood risk …). Decisions within 250 metres of the site are listed below — context, not this application.

Other applications within 250 metres (context — nearby, not this application)

No other geocoded decision is recorded within 250 metres.