Planning Application Details

P04/E0076Application Type: No Type (Show Map - opens in new window)
Status Bar
 
 Completed stage
 
 Current stage
 
 Next stage
Application registered
Consultation period
Application under consideration
Decision made
Description
Erection of fencing to perimeter of rear garden.
Location
63 Shiplake Bottom, Peppard Common (In the Parishes of Rotherfield Peppard & Sonning Common).
Grid Reference
470405/181027
Applicant
Mr & Mrs J Armitage
63 Shiplake Bottom
Peppard Common
HENLEY-ON-THAMES
Agent
Mr & Mrs J Armitage
63 Shiplake Bottom
Peppard Common
HENLEY-ON-THAMES
Case Officer
Mrs H Moore
Telephone: 01235 422600
Email: planning@southoxon.gov.uk
Consultation / Notification
No further Representations on this application will be accepted.

Consultations / Notifications to date are shown below.

Name / Number
Date Sent
Response Date
 
c/o Ms B Marston
Manscombe
Cox's Lane
Stoke Row
HENLEY ON THAMES
RG9 5QG
17 02 2004
 
c/o Ms S Jenkins
Village Hall
Wood Lane
Sonning Common
Oxon
RG4 9SL
 
The Well House
61 Shiplake Bottom
Peppard Common
HENLEY-ON-THAMES, Oxon
RG9 5HJ
 
65 Shiplake Bottom
Peppard Common
HENLEY-ON-THAMES, Oxon
RG9 5HJ
 
Tech.Dir, Monson Ltd
30 01 2004
 
Westwood
85 Shiplake Bottom
Peppard Common
HENLEY-ON-THAMES
Oxon
RG9 5HJ
 
Tudor Cottage
37 Shiplake Bottom
Peppard Common
HENLEY-ON-THAMES
Oxon
RG9 5HJ
 
Application Type
Other
Application Progress
Date Received  
22nd January 2004
Registration Date  
22nd January 2004
Start Consultation Period  
22nd January 2004
End Consultation Period  
20th February 2004
Target Decision Date  
18th March 2004
Decision
Planning Permission on 18th March 2004
Conditions / Refusal Reasons
That the development must be begun not later than the expiration of five years beginning with the date of this permission and if this condition is not complied with this permission shall lapse. Reason: By virtue of Sections 91 to 95 of the Town and Country Planning Act 1990.
Appeal
No appeal lodged.
Updates
These Planning Application Details were returned live from our back office database, and as such are as up to date as when the page was retrieved.