My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
06-23-2003 Council Minutes
Orono
>
City Council
>
Minutes
>
2000-2009
>
2003
>
06-23-2003 Council Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
5/16/2012 10:23:56 AM
Creation date
5/16/2012 10:23:56 AM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
15
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
MINUTES OF THE <br />ORONO CITY COUNCIL MEETING <br />Monday, June 23, 2003 <br />7:00 o'clock p.m. • <br />*8. #03 -2899 TIMOTHY PELLIZER, 520 NORTH ARM DRIVE — VARIANCE — <br />RESOLUTION NO. 4999 <br />Murphy moved, Sansevere seconded, to adopt RESOLUTION NO. 4999, a Resolution <br />granting an average lakeshore setback variance to allow construction of a 1,228 s.f. attached <br />garage addition encroaching 68' into the average lakeshore setback for the property located <br />at 520 North Arm Drive. VOTE: Ayes 3, Nays 0. <br />*9. #03 -2900 WM. YALE SMILEY HI AND TIMOTHY J. MAHONEY, 2730 AND 2760 <br />PHEASANT ROAD — REARRANGEMENT OF COMMON PROPERTY LINE — <br />RESOLUTION NO. 5000 and 5001 <br />Murphy moved, Sansevere seconded, to adopt RESOLUTION NO. 5000, a Resolution <br />approving a lot line rearrangement between the two developed residential lots located at <br />2730/2760 Pheasant Road; and to adopt RESOLUTION NO. 5001, a Resolution approving <br />the vacation of a dedicated drainage and utility easement within Lot 2, Block 1, Yale Smiley <br />Addition. VOTE: Ayes 3, Nays 0. <br />10. #03 -2901 DENALI CUSTOM HOMES, INC. ON BEHALF OF MELINDA LEE AND <br />THOMAS DEVEAU, 680 TONKAWA ROAD — VARIANCES — RESOLUTION NO. 5002 <br />Gaffron reported that the applicants have proposed to remove the existing house and construct a <br />new home on the property and are requesting variances to permit new construction on an <br />undersized lot (.54 acre where 1 acre is required) having a lot width of 64' where 140' is required. <br />Gaffron indicated that the applicants had provided a revised plan, proposing 75 -250' hardcover at <br />3,249 s.f. or 28.6 %, slightly less than the original proposal, and a revised grading plan that had not <br />been reviewed as of yet. <br />Generally, Gaffron noted that the Council accepted the Planning Commission's recommendation <br />regarding hardships that support the hardcover variance. He acknowledged that, after visiting the <br />site, the neighbor has significantly impacted the applicants' lake views. <br />Gaffron stated that the revised proposal suggests that hardships supporting the 75 -250' zone <br />hardcover of 28.6% could be quantified as follows: <br />- 80 s.f. credit for boulder walls needed to support steep slopes in the 75 -250' zone <br />- 127 s.f. credit for stairways needed to traverse steep slopes in 75 -250' zone <br />- 192 s.f. of driveway needed in 75 -250' zone due to inability to move house closer to road <br />in order to preserve lake views due to neighboring house location allowed by variance <br />The total credit is 399 s.f. which equates to 3,249 — 399 = 2,850 s.f. /11,360 s.f. = 25% <br />With regard to staff recommendations, Gaffron noted that while the City has rarely ever attempted <br />to quantify credit that should be granted for a specific site factor that is considered a hardship, the <br />method used here seemed reasonable. A method that might be, cautiously, applied to the City's <br />advantage in future applications. Despite the fact that staff originally recommended denial of the <br />application, Gaffron pointed out that the variance request as presented, appears to be supported by <br />a hardship. He stated that the resolution approves the lot area, lot width, and 75 -250' variance • <br />PAGE 10 of 15 <br />
The URL can be used to link to this page
Your browser does not support the video tag.