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

Permit Review Detail

Permit Number: DP15-0011
Parcel: 13705127A

Address:
4920 S 12TH AV

Review Status: Completed

Review Details: SITE and/or GRADING

Permit Number - DP15-0011
Review Name: SITE and/or GRADING
Review Status: Completed
Review Date Reviewer's Name Type of Review Description Status Comments
02/04/2015 RBROWN1 ADA REVIEW Passed
03/03/2015 LOREN MAKUS ENGINEERING REVIEW Reqs Change 1. Revise the development plan to be consistent with the last approved site plan. For example, the previously approved site plan has the correct MS&R dimensions.
2. Clearly explain all changes from the previously approved plan.
3. Include the cumulative sheet count for all sheets in the plans. (For example Sheet 1 of 15)
4. For all signs, add a notation that signs are under separate permit.
5. Ensure that all details are correct as referenced. For example 3/S-3 doesn't show the curb structure.
6. Ensure that all standard details referenced are correct per the depicted feature.
7. The detail callout for the water harvesting area describes a berm. The Landscape plan shows a depressed area. Make the plans consistent.
8. Provide spot elevations throughout the plan and show drainage patterns. Clarify, for example, whether the sidewalk along the parking areas is flush or elevated.
9. There are too many inconsistencies and problems with the plan to provide a complete review. Once the plan is complete and consistent, additional comments may
03/04/2015 RONALD BROWN H/C SITE REVIEW Reqs Change SHEET S-1
1. There is a conflict in grade elevations at the lower landing of the ramp to the office and the sidewalk ramp to the parking aisle landing. Will not work, please redesign.
2. Locate the accessible parking sign just behind the curb line in the concrete sidewalk centered on the accessible parking space.
3. Take out the strips at the accessible parking aisle landing and call out concrete finish.
4. Add a note recognizing and complying with Section 403.3 of the 2009 ICC A117.1 which calls for maximum slopes for the accessible route to be 5% running and 2% cross.
SHEET S-3
5. At detail 7: Detectable warning are required only at transportation platforms only and may be omitted.
SHEET S-4
6. At details 1, 2, 3, 6 and 7: Detectable warning are required only at transportation platforms only and may be omitted.
END OF REVIEW
03/04/2015 MICHAEL ST. PAUL ZONING REVIEW Reqs Change CDRC TRANSMITTAL

TO: Development Services Department
Plans Coordination Office

FROM: Michael St Paul
Planning Technician

PROJECT: DP15-0011
4920 South 12th Avenue
Tire Shop expansion C-2 Zone

TRANSMITTAL DATE: March 4, 2015

DUE DATE: March 4, 2015

COMMENTS: Please resubmit revised drawings along a response letter, which states how all Zoning Review Section comments regarding the Unified Development Code, The Administrative and Technical Manuals were addressed.

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

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 requirements are in the Unified Development Code and can be viewed at the same web link as above

1. 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 .

2. SECTION 2-06.0.0: DEVELOPMENT PACKAGE (TENTATIVE PLATS AND SITE PLANS)
Section

2-06.1.0 GENERAL

2-06.2.0 APPLICATION SUBMITTAL REQUIREMENTS

2-06.3.0 FORMAT REQUIREMENTS

2-06.4.0 CONTENT REQUIREMENTS

2-06.1.0 GENERAL

2-06.1.1 PURPOSE
This standard has been prepared for the purpose of informing applicants of the submittal and review requirements for development package documents to assure proper and adequate information is presented in a consistent manner, thereby providing the basis for an efficient and timely review. The development package documents are prepared in support of applications for building permits and related reviews.

The information that is requested establishes the basis upon which the project will be approved and could affect what is required of the property in the future, should there be a proposal for expansion or for a different use of the property.

This standard does not waive any applicable city regulations or codes.

2-06.1.2 APPICABILITY
This standard shall be used for all site plans and tentative plats submitted to PDSD for review.

2-06.2.1 APPLICATION SUBMITTAL REQUIREMENTS
Development Package applications are available from PDSD. Completed applications and accompanying materials shall be submitted to PDSD. Incomplete or inaccurate applications will not be accepted, nor will any application in which the pre-application conference or neighborhood meeting requirements have not been met. The types of documents and the specific number of copies required of each of the documents are on the PDSD website or may be obtained from PDSD. Resubmittals of development packages require a comment response letter that details how all previous comments have been addressed. Provide the same number of copies of the comment response letter as plans provided.
The following documents and information shall be submitted upon application:

2-06.2.1 Application Form
A completed application signed by the property owner or authorized designee;

2-06.2.2 Development Package
A development package must be prepared to the format and content requirements described herein;

2-06.2.3 Related Reviews
In addition to the plan process, a project may require review for other types of plans and documents. The applications for those processes are submitted to the appropriate department for review and approval. These related reviews can be applied for so that review can occur concurrently with the development package application. However, it must be understood that, should the related application be approved subject to conditions or denied, this may affect the;

2-06.2.4 Concurrent Reviews
The development package is designed to allow for concurrent review of any site related reviews. Concurrent review means that all plans and documents needed for the review are submitted as one package. Examples of site related reviews include but are not limited to: site plans, landscape plans, NPPO plans, water harvesting plans, grading plans, SWPPP plans, floodplain use permits, and overlay reviews. Separate applications are often required for the different site related reviews even if the plans are submitted concurrently; and,

2-06.2.5 Fees
Fees in accordance with Section 4-01.0.0, Development Review Fee Schedule.

2-06.3.0 FORMAT REQUIREMENTS

2-06.3.1 - Each sheet shall measure 24 inches by 36 inches and include a minimum one inch margin on left side and one-half inch margin on all other sides to facilitate efficient record keeping. A larger sheet format may be used with the approval of the Planning and Development Services Department (PDSD).

1) COMMENT: Provide the required margins on each sheet.

2-06.3.2 - All mapped data shall be drawn at an engineering scale having no more than 50 feet to the inch. This scale is the minimum accepted to assure the plan will be legible during review and when digitized and/or reduced for record-keeping purposes. The same scale shall be used for all sheets within the set. Smaller scales (60:1 or greater) may be used for some or all of the sheets with the prior approval of PDSD when it is determined legibility and the ability to be digitized and/or reduced for archiving will not be affected.
2-06.3.3 - All lettering and text (upper or lower case), and numbering, shall be a minimum of three-thirty-seconds inches in height to assure the plan will be legible during review and when digitized and/or reduced for archiving.

2-06.3.4 - A title block shall be provided in the lower right quadrant of each sheet.

2-06.3.6 - Provide a blank three-inch by five-inch block in the lower right corner of the plan adjacent to the title block on the first sheet of the development package for use by Pima County Addressing.

2) COMMENT: Provide the addressing block.

2-06.3.7 - A small, project-location map shall be provided in the upper right corner of the cover sheet.

3) COMMENT: That should be on the upper-right corner of the cover sheet. There are location maps on the first and second sheets. Neither is correct in scale and in the wrong location on the cover sheet.

2-06.3.8 - The north arrow, contour interval, and scale as applicable to each sheet should be placed together in the upper right corner of each sheet.

4) COMMENT: Place the "north arrow, contour interval, and scale as applicable to each sheet should be placed together in the upper right corner of each sheet" (2-06.3.8).

2-06.3.9 - The plan drawing shall be oriented with north toward the top of the sheet. If it is not practical to orient north to the top of the sheet, the plan drawing shall be oriented with north to the left side of the sheet.

2-06.3.10 - A legend that shows and describes all symbols used on the drawing is to be provided, preferably on the first sheet.

5) COMMENT: Place the legend on the first sheet.

2-06.3.11 - A key plan (if provided) shall be located on the first sheet.

6) COMMENT: Provide the key plan on the cover sheet.

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

2-06.4.0 CONTENT REQUIREMENTS

2-06.4.1 - 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.

7) COMMENT: Provide the email addresses for the owner and all the consultants (2-06.4.1).

2-06.4.2 - The title block shall include the following information and be provided on each sheet:

2-06.4.2.A - The proposed name of the project or subdivision, or if there is no name, the proposed tenant's name;

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;

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

8) COMMENT: Provide the complete numbering of the sheets on each sheet.

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.

9) COMMENT: Provide the development package number (15-0011) in the lower-right corner, next to the title block, on each sheet. Also provide reference to last approved plan number (T11CM01200) on the cover sheet.

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.

10) COMMENT: Revise the projection map from one inch equals three miles to three inches equals one mile (2-06.4.4). Place the projection map in the upper-right corner of the cover sheet.

2-06.4.4.A - Show the subject property approximately centered within the one square mile area;

2-06.4.4.B - Identify major streets and regional watercourses within the square mile area and all streets that abut the subject property; and,

11) COMMENT: Identify the major streets and routes (12th Avenue and Irvington Road) and water courses in the location map.

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

2-06.4.5 - When the development package documents consists of more than one sheet, a sheet index (a legible drawing of the site showing the area represented on each sheet) is to be placed on the cover sheet or the second sheet.

12) COMMENT: The sheet index only needs to be on the cover sheet.

2-06.4.6 - If the project is located within the boundaries of a Planned Area Development (PAD) zone, include a reduced-scale map of the PAD on the first sheet, indicating the location of the portion being developed.

2-06.4.7 - General Notes
The following general notes are required. Additional notes specific to each plan are required where applicable.

2-06.4.7.A - Zoning and Land Use Notes

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.

13) COMMENT: The use for a tire shop is "Automotive: Major Service and Repair (excluding bodywork and paint booths) with User Specific Standard 4.9.13.E (UDC Table 4.8-4).

2-06.4.7.A.6 - If a plan or plat is prepared in conjunction with other applications or overlays or the parcel being developed is subject to conditions of an application processed previously, additional information must be added to the plan. Such applications and overlays include, but are not limited to: annexations; rezonings; special exceptions; Board of Adjustment variances; Design Development Options; Technical Standard Modification Request; overlays (Airport Environs Zone, Environmental Resource Zone, Gateway Corridor Zone, Hillside Development Zone, Historic Preservation Zone, Major Streets and Routes, Rio Nuevo District, Scenic Corridor Zone, WASH); Modification of Development Regulations through the Downtown Area Infill Incentive District or Rio Nuevo District; Downtown Heritage Incentive Zone; or, Design Review Board. Provide the following information on the plan.

2-06.4.7.A.6.c - If the property includes Protected Riparian Area add a note stating that the project is designed to comply with Technical Manual Section 4-02, Floodplain, WASH, and ERZ Standard, specifying all lots impacted and including a total for the regulated area and the Protected Riparian Area.

2-06.4.7.A.8 - For development package documents provide:

2-06.4.8 - Existing Site Conditions
The following information shall be provided on the plan/plat drawing to indicate the existing conditions on site and within 50 feet of the site. On sites bounded by a street with a width of 50 feet or greater, the existing conditions across the street will be provided.

14) COMMENT: Provide the existing site condition, as described above (2-06.4.8), on the site plan.

2-06.4.8.B - All easements shall be drawn on the plan. The recordation information, location, width, and purpose of all easements on site will be stated. Blanket easements should be listed in the notes, together with recordation data and their proposed status. Should an easement not be in use and be proposed for vacation or have been abandoned, so indicate. However, should the easement be in conflict with any proposed building location, vacation of the easement shall occur prior to approval of plan unless written permission from easement holder(s) is/are provided.

15) COMMENT: Provide all existing easement information, as described above, on the site plan.

2-06.4.8.C - The following information regarding existing private or public right-of-way adjacent to or within the site shall be provided: the name, right-of-way width, recordation data, type and dimensioned width of paving, curbs, curb cuts, and sidewalks.

16) COMMENT: The future right-of-way information for 12th Avenue is incorrect.

2-06.4.9 - Information on Proposed Development
The following information on the proposed project shall be shown on the drawing or added as notes.

2-06.4.9.H - Proposed Traffic Circulation

2-06.4.9.H.1 - Proposed traffic circulation will be designed in accordance with Section 10-01.0.0, Street Technical Standards, of the Technical Standards Manual, to include streets, intersections, street names, right-of-way widths, curve radii of centerlines and curb returns, and proposed improvements, such as pavement, curbs, access points (driveways), accessible ramps, and sidewalks. Street improvements, such as sidewalks, curbs, pavement, and accessible ramps, do not need to be drawn on the plan if such information is provided on typical street cross sections.
Please be aware that, if a new street is created (for other than for subdivisions) which divides the property into two or more lots, a subdivision plat is required (refer to the definition of subdivision in Section 11.4.20 of the UDC).

17) COMMENT: The south driveway is not wide enough for two-way traffic, but the parking lot is laid out for two-way traffic.

2-06.4.9.H.2 - Show future and existing sight visibility triangles. On a designated MS&R street, the sight visibility triangles are based on the MS&R cross-section.

18) COMMENT: The future right-of-way information is incorrect. It does not take into account the intersection widening. See the last approved plan by David Garcia. That plan is correct.

2-06.4.9.H.4 - Indicate if existing streets are public or private; provide street names, widths, curbs, sidewalks, and utility locations, all fully dimensioned.

19) COMMENT: See previous comment.

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.

20) COMMENT: The south driveway is not wide enough for two-way traffic.

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.

21) COMMENT: Provide fully dimensioned plan view and details for the bicycle parking.

2-06.4.9.J - If street dedication is not required or proposed and the project site is adjacent to a Major Street or Route, draw the Major Street right-of-way lines for those streets. (Add the MS&R future sidewalk, right-of-way lines, sight visibility triangles, etc.)

22) COMMENT: The future right-of-way information is incorrect. It does not take into account the intersection widening. See the last approved plan by David Garcia. That plan is correct.

2-06.4.9.L - All proposed easements (utility, sewer, drainage, access, etc.) are to be dimensioned and labeled as to their purposes and whether they will be public or private. The easements may have to be recorded and the recordation information added to the development package prior to approval.

23) COMMENT: If there are any proposed easements provide the information on the plans as described above (2-06.4.9.L).

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).

24) COMMENT: What are the uses of each building and the covered structure?

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.

25) COMMENT: Continuous pedestrian circulation paths are required with all development (TS 7.01.3.3).

A) The pedestrian path must be connected to all public access areas of the development and to any adjacent streets (TS 7-01.3.3.A).

B) "The areas within the development which must be connected include, but are not limited to, all buildings, all bicycle and vehicle parking areas, all recreation areas, all dumpster areas, and all other common use areas" (TS 7-01.3.3.B).

C) "Within this pedestrian circulation path, an accessible route is also required in compliance with the city's adopted building codes" (TS 7-01.3.2). "Pedestrian circulation paths designed for barrier-free accessibility for the physically disabled and located within any development are regulated by the adopted building codes" (TS 7-01.3.3.C).


7-01.4.0 LOCATION AND DESIGN STANDARDS
4.1 Location Standards
Sidewalks must meet the following locational requirements:
A. At least one sidewalk is required to a project from each street on which the project has frontage, unless there is no vehicular access from a street because of a physical barrier, such as a drainageway or an unbroken security barrier (e.g., a wall or fence). The sidewalk should be located to minimize any conflict with vehicular access to the project;
B. A sidewalk is required adjacent and parallel to any access lane or PAAL on the side where buildings are located (See Figure 1);
C. A sidewalk is required adjacent to any parking space accessed by a PAAL where the space is located on the same side of the PAAL as any building and no other parking spaces or PAALs intervene (See Figure 2);
D. Sidewalks must connect all areas of the development and must also connect to the pedestrian circulation path located along any adjacent street;
E. Sidewalks shall be flood free for all storm discharges of up to and including a ten-year frequency flood event. Drainage flowing across all pedestrian circulation paths shall be conveyed under the path for up and including the ten-year frequency flood events, except at street intersections, pedestrian crossings, and PAAL pedestrian crossings;
F. Sidewalks or pedestrian refuge areas cannot be located between any motor vehicle parking space and the PAAL providing access to that space;
G. Sidewalks or crosswalks cannot cross any type of stacking areas for drive-through lanes; and,
H. In Land Use Classes where the public does not have access to certain portions of the site, a four- foot wide pedestrian refuge area must be maintained between any enclosed structure and a PAAL (See Figure 6).

2-06.4.9.S - Show existing or proposed pedestrian circulation along abutting rights-of-way. Such sidewalks must comply with accessibility requirements for the physically disabled and the design criteria in Section 10-01.0.0, Street Technical Standards, of the Technical Standards Manual.

26) COMMENT: Provide the pedestrian circulation as described above (2-06.4.9.S) on the site plan for this development package.

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.

27) COMMENT: See comments by the engineering review section.


2-06.4.9.W - Indicate the locations and types of proposed signs (wall, free-standing, pedestal) to assure there are no conflicts with other requirements and that minimal locational requirements can be met. Indicate if there are any existing billboards on site. Compliance to the Sign Code, Chapter 3 of the Tucson Code, is required.

28) COMMENT: All signs must be approved on a separate sign permit.

2-06.4.9.X - Show compliance with landscaping and screening requirements by locations, material descriptions, and dimensions. Specific plant or hardscape material shall be detailed on a landscape plan. A detailed landscape plan is required. In accordance with Section 2-11.0.0, Landscape Plan Requirements.

29) COMMENT: See comments by the landscaping review section.

If you have any questions about this transmittal, please call Michael St. Paul, (520) 837-4959.

RESUBMITTAL OF THE FOLLOWING IS REQUIRED: Revised development package site plan and any requested documents.


There is no evidence that you even looked at the Administrative Manual instructions for a Development Package (AM 2-06).

The Second sheet (Sheet S-1) has most of the information that should be on the cover sheet. The cover sheet has mostly filler, such as a reduction of the last approved site plan. The last approved site plans have been provided at full scale.

The pedestrian circulation appears to be going through a work area for the tire shop.
03/04/2015 ANDREW CONNOR NPPO REVIEW Approved
03/04/2015 ANDREW CONNOR LANDSCAPE REVIEW Reqs Change 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:

Rezoning case;

Subdivision case;

Board of Adjustment case;

Design Development Option case;

Development Review Board (DRB) case; and/or,
Any other relevant case number for reviews or modifications that affect the site.

Within a vehicular use area, one canopy tree is required for each four motor vehicle parking spaces or fraction thereof.

The canopy trees must be evenly distributed throughout the vehicular use area. Every parking space must be located within 40 feet of the trunk of a canopy tree (as measured from the center of the tree trunk).

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

Additional comments may apply
03/09/2015 PGEHLEN1 COT NON-DSD TRAFFIC Needs Review

Final Status

Task End Date Reviewer's Name Type of Review Description
03/11/2015 FERNE RODRIGUEZ OUT TO CUSTOMER Completed
03/11/2015 FERNE RODRIGUEZ REJECT SHELF Completed