Microfiche records prior to 2006 have not been completely digitized and may not be available yet on PRO. If you cannot find what you are looking for please submit a records request.

Permit Number: DP13-0194
Parcel: 12313101A

Address:
2110 N 1ST AV

Review Status: Completed

Review Details: SITE and/or GRADING

Permit Number - DP13-0194
Review Name: SITE and/or GRADING
Review Status: Completed
Review Date Reviewer's Name Type of Review Description Status Comments
10/02/2013 MARTIN BROWN FIRE REVIEW Denied Please provide location of existing and/or proposed fire hydrants with dimensions to property lines. Refer to section 507 of 2012 IFC for spacing requirements.
Please provide additional details regarding rolling gates. Refer to section 503 for requirements.
Please provide proposed occupancy classification
10/02/2013 RBROWN1 ADA REVIEW Passed
10/02/2013 STEVE SHIELDS ZONING REVIEW Denied CDRC TRANSMITTAL

TO: Development Services Department
Plans Coordination Office

FROM: Steve Shields
Lead Planner

PROJECT: 2110 N. 1st Avenue - Multi-Family Development
Development Package (1st Review)
DP13-0194

TRANSMITTAL DATE: October 3, 2013

DUE DATE: October 29, 2013

COMMENTS: Please resubmit revised drawings along a response letter, which states how all Zoning Review Section comments regarding the Land Use Code and Development Standards were addressed.

This plan has been reviewed for compliance with the Unified Development Code (UDC) Administrative Manual (AM) Section 2-06. Also compliance with applicable development criteria for the proposed use as listed in the City of Tucson Uniform Development Code (UDC) and the UDC Technical Standards Manual (TSM).

The review comments include the actual standard first with the applicable Administrative Manual section number and the following paragraph is the actual comment related to the specific item that must be addressed. If you need to review the sections listed below click on the link or copy it in the address bar of your internet program. http://www.amlegal.com/nxt/gateway.dll/Arizona/tucson_az_udc/administrativemanual?f=templates$fn=default.htm$3.0$vid=amlegal:tucson_udc_az

This link will take you directly to the section used for the standards review. The UDC & TSM requirements are in the Unified Development Code and can be viewed at the same web link as above

Section 3.3.3.G.5.c UDC, An applicant has one year from the date of application to obtain approval of a site plan that complies with zoning and other development requirements in effect at the time of application, unless an ordinance adopted by Mayor and Council during this period states otherwise. A site plan application that has been in review for a period of one year and has not yet been approved is considered denied. To continue the review of a site plan for the property, a new site plan must be submitted that complies with regulations in effect at the time of re-submittal. The new submittal initiates a new one-year review period. One year Expiration date is October 11, 2014 .

2-06.3.5 - A three-inch by five-inch space shall be reserved in the lower right quadrant of each sheet for an approval stamp.

1. COMMENT: Provide the Development Package approval stamp adjacent to the title block in the lower right hand corner of all sheets, This stamp can be found @ http://cms3.tucsonaz.gov/files/dsd/CDRC/acad-cot_stamp_model_1.pdf

2-06.3.12 - An index of sheets in the development package shall be provided on the first sheet.

2. COMMENT: Provide a sheet index on the first sheet.

CONTENT REQUIREMENTS - The name, mailing and email addresses, and phone number of the primary property owner of the site, the developer of the project, registrant(s), and other person(s), firm(s), or organization(s) that prepared the development package documents shall be provided on the right half of the cover sheet. The applicable registration or license number shall be provided if prepared by or with the assistance of a registered professional, such as a surveyor, architect, landscape architect, or engineer. All sealing shall be consistent with Arizona Board of Technical Registration guidelines.

3. COMMENT: Provide the name, mailing and email addresses, and phone number of the developer of the project on the first sheet.

2-06.4.2.B - A brief legal description and a statement as to whether the project is a resubdivision are to be provided. On resubdivisions, provide the recording information of the existing subdivision plat;

4. COMMENT: Provide a brief legal description in the title block on all sheets.

2-06.4.2.D - The page number and the total number of pages in the package (i.e., sheet xx of xx).

5. COMMENT: Provide the correct page number and total number of pages within the title block. These drawing show 2 of 20 and 3 of 20 with only three (3) sheets submitted.

2-06.4.3 - The administrative street address and relevant case numbers (development package document, subdivision, rezoning, board of adjustment, DDO, MDR, DSMR, overlay, etc.) shall be provided adjacent to the title block on each sheet.

6. COMMENT: Provide the administrative street address and the development package case number, DP13-0194, adjacent to the title block on all sheets.

2-06.4.4 - The project-location map to be located on the first sheet of the development package in the upper right corner, shall cover approximately one square mile, be drawn at a minimum scale of three inch equals one mile, and provide the following information.

7. COMMENT: Provide a location map drawn at of three inch equals one mile.

2-06.4.2.C - Section, township, and range; section corners; north arrow; and the scale will be labeled.

8. COMMENT: Provide the section, township, and range, label the sections corners and scale on the location map.

2-06.4.7.A.2 s- List the gross area of the site/subdivision by square footage and acreage.

9. COMMENT: Provide a general note listing the gross area of the site by square footage and acreage.

2-06.4.7.A.4 - Identify the existing and proposed use of the property as classified per the UDC. List all UDC sections applicable to the proposed uses.

10. COMMENT: Provide a general note listing the use as classified per the UDC. List all UDC sections applicable to the proposed uses. That said the use should be listed as "MULTIFAMILY DEVELOPMENT SUBJECT TO USE SPECIFIC STANDARDS 4.9.7.B.6, .9, & .10"

11. COMMENT: Remove all Land Use Code (LUC) references, i.e. development designator K, perimeter yard indicator BB, etc. from the plan as the LUC is not applicable.

2-06.4.7.A.5 - On residential projects, list the total number of units proposed.

12. COMMENT: Revise the note under "PROJECT INFORMATION", "(6) SINGLE FAMILY RESIDENCES" to "(6) UNITS" as this is a multifamily project not individual single family homes on individual lots.

2-06.4.9.H.5 - If utilizing parking area access lanes (PAALs), they shall be designed in accordance with Section 7.4.6, Motor Vehicle Use Area Design Criteria, of the UDC.

13. COMMENT: Provide a radius dimension for the back-up spur located at the east end of the parking area access lane (PAAL), see UDC Section 7.4.6.F.4.b.

14. COMMENT: Provide a dimension for the back of the back-up spur located at the east end of the parking area access lane (PAAL) to the proposed 5' screen fence, see UDC Section 7.4.6.F.4.c.

15. COMMENT: There appears to be curbing proposed around the vehicle use areas that are not clearly labeled. Provide some type of note to clearly identify the curbing.

2-06.4.9.H.5.a - Show all motor vehicle off-street parking spaces provided, fully dimensioned. As a note, provide calculations on the number of spaces required (include the ratio used) and the number provided, including the number of spaces required and provided for the physically disabled. The drawing should indicate parking space locations for the physically disabled. A typical parking space detail shall be provided for both standard parking spaces and those for the physically disabled. For information on parking requirements for the physically disabled, refer to adopted building and accessibility codes of the City of Tucson. Design criteria for parking spaces and access are located in Section 7.4.6, Motor Vehicle Use Area Design Criteria, of the UDC.

16. COMMENT: Provide a vehicle parking space detail for both the garage and exterior parking spaces.

2-06.4.9.H.5.d - Show bicycle parking facilities fully dimensioned. For specifics, refer to Section 7.4.9, Bicycle Parking Design Criteria, of the UDC. Provide, as a note, calculations for short and long term bicycle spaces required and provided.

17. COMMENT: Provide a short & long term bicycle parking space calculation on the plan, see UDC Table 7.4.8-1 for requirements.

18. COMMENT: Show the location of the proposed short & long term bicycle parking on the plan.

19. COMMENT: Provide a detail for both short & long term bicycle parking. Demonstrate how the requirements UDC Section 7.4.9.B, .C & .D are met.

2-06.4.9.O - All applicable building setback lines, such as erosion hazard, floodplain detention/retention basins, and zoning, including sight visibility triangles, will be shown.

20. COMMENT: Along the south property line the "LOWER" and "UPPER" level setback lines are labeled backwards.

21. COMMENT: Per UDC Section 6.4.5.B.1 The width of the perimeter yard is the distance measured horizontally from a specified point to the face of each exterior building wall at the wall's highest point. That said the required street perimeter yard would be based on the exterior wall height measured from grade to where the wall meets the eave. Base on the elevations shown on sheet SD2 18'-3" from top of bearing to finished floor plus 6" to grade the exterior wall height would be 18'-9". Per UDC Section 6.4.5.C.1.a Within established areas, the minimum required front street perimeter yard is 20 feet or one and one-half the height of the proposed wall (H), measured from the street property line, whichever is greater. With an exterior wall height of 18'-9" x 1.5, the required front street perimeter yard setback is 28.125'. Based on the "27.37'" shown on the plan a Design Development Option (DDO) to reduce the required street perimeter yard will need to approved prior to approval of this development package. Contact Michael Taku, phone 837-4963 or email Michael.Taku@tucsonaz.gov for DDO process and requirements.

22. COMMENT: Per UDC Section 6.4.5.B.1 The width of the perimeter yard is the distance measured horizontally from a specified point to the face of each exterior building wall at the wall's highest point. That said the required street perimeter yard would be based on the exterior wall height measured from grade to where the wall meets the eave. Base on the elevations shown on sheet SD2 18'-3" from top of bearing to finished floor plus 6" to grade the exterior wall height would be 18'-9". Per UDC Table 6.3-2.A: DIMENSIONAL STANDARDS FOR THE R-1, R-2, R-3, MH-1, & MH-2 ZONES, Nonres Use to Res Zone, the required perimeter yard setback is based on 10 or ¾ the height of the building exterior wall measured from grade. The required perimeter yard for the "UPPER LEVEL" to the north and south property lines would be, 18.75' x 0.75, or 14.0' not 13.67'. It appears that the proposed buildings along the north property line may meet perimeter yard setbacks. But based on the "13.67'" shown on the plan a Design Development Option (DDO) to reduce the required south perimeter yard will need to approved prior to approval of this development package. Contact Michael Taku, phone 837-4963 or email Michael.Taku@tucsonaz.gov for DDO process and requirements.

2-06.4.9.Q - Provide the square footage and the height of each commercial, industrial, or business structure and the specific use proposed within the footprint of the building(s).

23. COMMENT: Provide the square footage and the height of each structure and the specific use proposed within the footprint of the building(s)

2-06.4.9.R - Show on-site pedestrian circulation and refuge utilizing location and the design criteria in Section 7-01.0.0, Pedestrian Access, of the Technical Standards Manual.

24. COMMENT: Per TSM 7-04.3.A All sidewalks must be a minimum of four feet wide. Provide width dimension for all sidewalks shown on the plan.

25. COMMENT: Per TSM 7-04.1.B A sidewalk is required adjacent and parallel to any access lane or PAAL on the side where buildings are located. That side a sidewalk is required on the south side of the proposed PAAL between the proposed buildings and the PAAL.

2-06.4.9.T - Show refuse collection areas, including locations of dumpsters, screening location and materials, and vehicle maneuverability, fully dimensioned, and access route. If dumpster service is not proposed, indicate type of service. For specific information on refuse collection, refer to Section 8-01.0.0, Solid Waste and Recycle Disposal, Collection, and Storage, of the Technical Standards Manual. Refuse collection on all projects shall be designed based on that section, even if collection is to be contracted to a private firm.

26. COMMENT: Show the refuse collection area on the plan.

If you have any questions about this transmittal, please Steve Shields, (520) 837-4956 or Steve.Shields@tucsonaz.gov

RESUBMITTAL OF THE FOLLOWING IS REQUIRED: Revised development package
10/18/2013 JASON GREEN ENGINEERING REVIEW Reqs Change DATE: October 21, 2013
SUBJECT: ZACK 2110 Development Plan Package- Engineering Review
TO: Rhonda Rawson, RA
LOCATION: 2110 N 1st Ave; T143S R14E Sec06
REVIEWERS: Jason Green, CFM
ACTIVITY: DP13-0194

SUMMARY: Engineering Division of Planning & Development Services Department has received and reviewed the proposed Development Plan Package. Engineering Division does not recommend approval of the Development Plan Package at this time. This review falls under the Unified Development Code (UDC), Administration Manual (AM) and Technical Standards Manual (TSM). Refer to the links for further clarification:
http://www.amlegal.com/nxt/gateway.dll/Arizona/tucson_az_udc/administrativemanual?f=templates$fn=default.htm$3.0$vid=amlegal:tucson_udc_az

The following items need to be addressed:


SITE PLAN:

1) AM Sec.2-06.3.5: Revise the development plan document to include the approval stamp in the lower right quadrant of each sheet. The link to the stamp can be found here: http://cms3.tucsonaz.gov/pdsd/cdrc-rezoning/cdrd-stamp

2) AM Sec.2-06.3.12: Revise the development plan document to include a Sheet Index on Sheet 1 that describes all 3 sheets in the package.

3) AM Sec.2-06.4.1: Revise the development plan document to provide the name, mailing and email addresses, and phone number of the developer of the project on the first sheet. Include the phone number for the property owner in the Owners Section.

4) AM Sec.2-06.4.2.B: Revise the development plan document to include a brief legal description of the property and a statement as to whether the project is a resubdivision. On resubdivisions, provide the recording information of the existing subdivision plat.

5) AM Sec.2-06.4.2.D: Revise the development plan document and the Title Block to include the page number and the total number of pages in the package (i.e., Sheet XX of XX). The proposed sheets call out Sheet 2 and 3 of 20 however there are only 3 Sheets in the package and two of them are labeled Sheet 2 without a Sheet 1, revise.

6) AM Sec.2-06.4.3: The relevant Development Plan Package case number (DP13-0194) may be added to the lower right hand corner of the plan on all sheets.

7) AM Sec.2-06.4.4.C: Revise the development plan document and project location map to provide the section, township, and range, label the sections corners and scale on the location map.

8) AM Sec.2-06.4.7.A.2: Revise the development plan document to include a General Note listing the gross area of the site by square footage and acreage.

9) DS Sec.2-06.4.7.B.1: Revise the development plan document to include a Drainage Note per the referenced standard specifically; "The developer, any successors and assigns, will hold the City of Tucson, its officers, employees, and agents harmless from any and all claims for damages related to the use of this development as shown hereon, now and in the future, by reason of flooding, flowage, erosion, or damage caused by water, whether surface flood or rainfall."

10) DS Sec.2-06.4.7.B.3: Revise the development plan document to include a Drainage Note per the referenced standard specifically; "Drainage will remain in its natural state and will not be altered, disturbed, or obstructed other than as shown on this development plan."

11) DS Sec.2-06.4.7.C.2: Revise the development plan document to include a General Note per the referenced section; "No structure or vegetation shall be located or maintained so as to interfere with the sight visibility triangles in accordance with Section 10-01.5.0, Sight Visibility, of the Technical Standards Manual."

12) DS Sec.2-06.4.7.D: Revise the development plan document to include a General Note per the referenced section; "Any relocation or modification of existing utilities and/or public improvements necessitated by the proposed development will be at no expense to the public."

13) AM Sec.2-06.4.8.C: Revise the development plan document to label existing curbing within the right-of-way of 1st Avenue. Label and dimension all existing curb cuts.

14) AM Sec.2-06.4.9.H.1: Revise the development plan document to label all existing driveway entrances that are to be closed off. All entrance must be clearly labeled and provide a Keynote to label the curbing and sidewalk dimensions along with a reference to the Standard Detail for Public Improvements to match existing. Or verify if the proposed driveway is at the existing curb cut location.

15) AM Sec.2-06.4.9.H.1: Revise the development plan document to label the required standard driveway apron per TSM Sec.10-01.4.3. The proposed driveway must meet the minimum PC/COT Standard Detail for Public Improvement #200; provide a Keynote reference or a separate detail for construction purposes.

16) AM Sec.2-06.4.9.H.1: Revise the development plan document to dimension the existing Alleyway.

17) AM Sec.2-06.4.9.H.2: Revise the development plan document to label and correctly dimension the existing sight visibility triangles (SVTs) in plan view. Correctly label and dimension the near and far side SVT per the Sight Matrix, TSM.10-01.5.3, the Near Side dimension for a driveway to a Local Street is 20'x185' and the Far Side dimension is 20'x110', revise.

18) AM Sec.2-06.4.9.H.4: Revise the development plan document to label 1st Avenue as "Public" on the plan sheets. Fully dimension the existing widths, right-of-way, curbs, sidewalks and utility locations.

19) AM Sec.2-06.4.9.H.5.a: Revise the development plan document to label in plan view and to provide a Keynote call out for the proposed 6-inch curbing within the vehicle use area. Either provide a reference to a PC/COT Standard Detail or provide a separate detail for construction purposes.

20) AM Sec.2-06.4.9.H.5.a: Revise the development plan document to provide a typical parking space detail for both standard parking spaces and those within the garage.

21) AM Sec.2-06.4.9.H.5.a: Provide approval from Fire and TDOT for the proposed rolling gate across the new PAAL. Verify on the plan set the minimum 24-foot clear when the gate is open.

22) AM Sec.2-06.4.9.H.5.a: Revise the development plan document to label the minimum dimensions for the proposed back-up spur at the end of the PAAL per UDC Sec.7.4.6.F.4, specifically the 3-foot radii.

23) AM Sec.2-06.4.9.N.2: Revise the development plan document to label and dimension curb cuts into the landscape areas to alleviate offsite flows due to the increase in impervious area of the site. Provide a detail for construction purposes. Or provide a Drainage Statement showing that post offsite flows do not exceed the existing conditions.

24) AM Sec.2-06.4.9.N.2: Revise the development plan documents to clearly label that the new water harvesting areas in the 10 foot landscape border is to be depressed minimum 6-inches.

25) AM Sec.2-06.4.9.R: Revise the development plan document to label and dimension all onsite pedestrian access lanes. Per TSM Sec.7-01.4.3 the minimum width for a sidewalk is 4-feet, revise. Provide a Keynote reference to the PC/COT Standard Detail for Public Improvement for all proposed sidewalks or a separate detail for construction purposes.

26) AM Sec.2-06.4.9.R: Revise the development plan document to label and dimension the minimum gate width for the proposed pedestrian access path adjacent to the mail boxes to meet ANSI requirements.

27) AM Sec.2-06.4.9.R: Revise the development plan document to provide for a pedestrian circulation path along the north side of Units 4, 5 and 6. Per TSM Sec.7-01.4.1.B a sidewalk is required adjacent and parallel to any access lane or PAAL on the side where buildings are located, revise.

28) AM Sec.2-06.4.9.R: Revise the development plan document to provide for a pedestrian circulation path to the required onsite refuse containers. Per TSM Sec.7-01.3.3.B all areas of development must be connected to the refuse areas. If ES approves the use of APC this comment will not be applicable.

29) AM Sec.2-06.4.9.R: Refer to comments from Ron Brown, RA Structural Plans Examiner for all handicap accessibility comments that may be associated with this project.

30) AM Sec.2-06.4.9.S: Revise the development plan document to label and dimension the required pedestrian circulation along the abutting right-of-way. Such sidewalks must comply with accessibility requirements for the physically disabled and the design criteria in TSM Sec.10-01.4.0.

31) AM Sec.2-06.4.9.S: Revise the development plan document to label the PC/COT Standard Detail for Public Improvement #203 for the connection of the new to existing sidewalk located at the north portion of the site in the right-of-way.

32) AM Sec.2-06.4.9.T: Revise the development plan document to provide for centralized onsite solid waste and recycle collection service pick up per TSM Sec.8-01.5.1.A, Utilization of individual containers (APCs) for six or more new dwelling units requires approval by ES on a case by case evaluation (provide written approval from ES). Provide a construction detail for the refuse enclosures. The detail must match TSM Sec.8-01 and Figure 3a for the required enclosure walls, gates, concrete thickness and compressive strength, concrete approach apron dimensions, 14'x40' clear approach for each container, etc.


GENERAL COMMENTS:

Please provide a revised Development Plan Package that addresses the comments provided above. Include a comprehensive response letter addressing in detail responses to all of the above comments.

For any questions or to schedule meetings call me at 837-4929.



Jason Green, CFM
Senior Engineer Associate
Engineering Division
Planning & Development Services Department
10/22/2013 ROBERT SHERRY PLUMBING-COMMERCIAL REVIEW Denied 1. An approved development plan is not to be used for construction of on-site utilities (e.g. water service to the building, building sewer, site lighting, or electrical service to the building). The construction of the on-site utilities may be included with the permit for constructing the building or as a separate permit.
2. The maximum demand flow that is allowed by Tucson Water for the specified 5/8"water meter is 15 GPM. Based on the submitted floor plans, the demand for each building will be approximately 21 GPM (not including the additional demand caused any hose bibbs).
3. The total flow for the private sewage collection system for this project is in excess of 3000 gallons per day. The design for the system must be submitted to the Pima County Department of Environmental Quality for their approval prior to obtaining a permit for constructing the sewage collection system from the City of Tucson. Reference A. R. S. 49-104 (B) (13).
10/23/2013 ANDREW CONNOR LANDSCAPE REVIEW Reqs Change ADMINISTRATIVE MANUAL SECTION 2-10.0.0: LANDSCAPE PLAN REQUIREMENTS

Identification and Descriptive Data

All improvements and site information, such as adjacent rights-of-way and property lines, shown on the landscape plan will be identical in size and location to those shown on the base plan (site plan or tentative plat). Should amendments be required to the base plan through the review process, the same amendments will be made to the landscape plan which will then be resubmitted along with the base plan.

The landscape plan will contain the following identification in the lower right corner of each sheet:

Relevant case number for reviews.

Provide square footage of the vehicular use area; number of parking spaces, including the required and provided parking space calculations; and the calculation of the required number of canopy trees. Within a vehicular use area, one canopy tree is required for each four motor vehicle parking spaces

Fifty percent or more of the area of the street landscape border must be covered with shrubs or vegetative ground cover. The required ground coverage must be achieved within two years from the date of planting. Provide calculations for coverage.

Interior landscape borders are required to screen multifamily use from residential zoned properties per DS TABLE 7.6.4-1.

Submit NPPO plan as determined by A.M. Section 2-11 or provide acceptable documentation, which clearly indicates that the project will not impact Protected Native Plants. Such documentation includes photographs of the site taken from all sides of the property.

Ensure that all Zoning and Engineering comments and concerns are addressed.

Additional comments may apply
10/25/2013 ANDREW CONNOR NPPO REVIEW Reqs Change Submit NPPO plan as determined by A.M. Section 2-11 or provide acceptable documentation, which clearly indicates that the project will not impact Protected Native Plants. Such documentation includes photographs of the site taken from all sides of the property.
10/25/2013 RONALD BROWN H/C SITE REVIEW Denied 1. Change project information title description from 6 Single Family Residences (2012 IBC Classification R-3 to R-2 Apartments) to 6 Residential Rental Units.
2. Provide 1 Van Accessible parking space including signage, access to accessible route, aisle and markings.
3. Insure and note that all slopes of the accessible routes are to comply with 2009 Edition, ICC A117.1, Section 403.3; 5% maximum running slope and 2% maximum cross slope.
4. For all marked crossings:
a. Only 1 marked crossing is required
b. Provide a large scale detail of the different types of marked crossings showing all accessible requirements i.e.: dimensions, widths, slopes, ramps with slope direction arrows, markings, detectable warning strips, 6" curb and flush curbs.
END OF REVIEW

Final Status

Task End Date Reviewer's Name Type of Review Description
12/12/2013 CPIERCE1 REJECT SHELF Completed