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
Review Status: Completed
Review Details: SITE and/or GRADING
Permit Number - DP14-0015
Review Name: SITE and/or GRADING
Review Status: Completed
Review Date | Reviewer's Name | Type of Review | Description | Status | Comments |
---|---|---|---|---|---|
02/03/2014 | RBROWN1 | ADA | REVIEW | Passed | |
02/05/2014 | MARTIN BROWN | FIRE | REVIEW | Approved | |
02/05/2014 | STEVE SHIELDS | ZONING | REVIEW | Reqs Change | CDRC TRANSMITTAL TO: Development Services Department Plans Coordination Office FROM: Steve Shields Lead Planner PROJECT: Circle K Store #5316 - Building Expansionon Development Package (1st Review) DP14-0015 TRANSMITTAL DATE: February 5, 2014 DUE DATE: March 4, 2014 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 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 February 2, 2015. Based on a building expansion of greater than 25% this development package was review for full compliance of UDC Sections 7.4, 7.5, 7.6, and TSM Section 7-01. 2. SECTION 2-06.0.0: DEVELOPMENT PACKAGE (TENTATIVE PLATS AND SITE PLANS) Section 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.3.0 FORMAT REQUIREMENTS 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 PDSD Development Package approval stamp on all sheets. The stamp can be found at http://cms3.tucsonaz.gov/files/dsd/CDRC/acad-cot_stamp_model_1.pdf 2-06.4.0 CONTENT REQUIREMENTS 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. 2. COMMENT: Remove the street address from the title block and provide it adjacent to the title block on each sheet. 3. COMMENT: Provide the development package case number, DP14-0015, adjacent to the title block on each 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. 4. COMMENT: The location map is not to scale, provide a location map at three inch equal one miel. 2-06.4.2.C - Section, township, and range; section corners; north arrow; and the scale will be labeled. 5. COMMENT: Provide the section, township, and range under the vicinity map. 6. COMMENT: Identify the section corners on the vicinity map. 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.2 - List the gross area of the site/subdivision by square footage and acreage. 7. COMMENT: Clarify the gross site area listed under "PROJECT DATA". Based on the Pima County Assessor's information this parcel is no where near 1.98 acres. 8. COMMENT: Under "PROJECT DATA" remove the reference to "NET SITE AREA" as it is not applicable. 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. 9. COMMENT: Provide a general note stating "EXISTING USE IS GENERAL MERCHANDISE SALES, PROPOSED USE IS GENERAL MERCHANDISE SALES SUBJECT TO USE SPECIFIC STANDARDS 4.9.9.B.3 AND 4.9.13.O. 2-06.4.7.A.5 - On residential projects, list the total number of units/lots proposed. 10. COMMENT: 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. 11. COMMENT: : Provide a general note on the cover sheet stating "THIS PROJECT IS DESINGED TO MEET THE OVERLAY ZONE(S) CRITERIA, UDC SECTION 5.4 MAJOR STREETS AND ROUTES SETBACK ZONE (MS&R)." 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. 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. 12. COMMENT: Provide 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. 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.F - All existing zoning classifications on and adjacent to the project (including across any adjacent right-of-way) shall be indicated on the drawing with zoning boundaries clearly defined. If the property is being rezoned, use those boundaries and classifications. The basis for this requirement is that some zoning requirements on a project are based on the zoning classification of adjacent property. Also, in some instances, each zone has to be taken into consideration on property that is split by two or more zoning classifications, as each may have different requirements. 13. COMMENT: Provide the existing zoning for the parcels west of Prudence Road and north of 22nd Street. 2-06.4.9.H.2 - Show future and existing sight visibility triangles (SVT's). On a designated MS&R street, the sight visibility triangles are based on the MS&R cross-section. 14. COMMENT: It does not appear that the SVT's are shown correctly. Contact your engineering reviewer for correct SVT's. 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. 15. COMMENT: The required number of vehicle parking spaces is not correct. Based on UDC Section 7.4.3.G the required number should be 12. 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. 16. COMMENT: Provide a bicycle parking space calculation. This calculation should in include the require and provided number for both short & long term bicycle parking. 17. COMMENT: The Provided "BIKE RACK DETAIL" shown on sheet SP-2 does not meet the requirements of UDC Section 7.4.9.B & 7.4.9.C. 18. COMMENT: Show the required long term bicycle parking on the plan. 19. COMMENT: Provide a detail for the required long term bicycle parking that meets the requirements of UDC Section 7.4.9.B & 7.4.9.D. 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. 20. COMMENT: Per TSM 7-01.3.3.B Within all development, a continuous pedestrian circulation path is required as follows: 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. The striped "EXISTING ADA PATH" shown running down the center of the PAAL and along the edge of the curbing to the "UTILITY/RESTROOMS" does not meet requirements. Remove the striped area as this would not be considered a crosswalk. Provide a new pedestrian circulation that meets the requirements of TSM Section 7.-01 from the existing "UTILITY/RESTROOMS" to the "CONV. STORE". 21. COMMENT: Per TSM 7-01.4.1.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. That said show the required pedestrian circulation from the buildings to the sidewalk located within the ROW of Prudence Road. 22. COMMENT: Per TSM 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. That said a four (4) sidewalk is required along the southeast side of the main building. ADDITIONAL COMMENTS' 23. COMMENT: Remove the following information from sheet SP-1 as it is provided on sheet G-1, vicinity map, project data, legal description, contacts & project description. 24. COMMENT: Sheet G-1 Remove the reference to "INTERIOR REMODEL" as it is not applicable. 25. COMMENT: Sheet G-1 Remove all building code references as they are not applicable to the development package. 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 |
02/21/2014 | ANDREW CONNOR | LANDSCAPE | REVIEW | Reqs Change | UNIFIED DEVELOPMENT CODE 7.6.2. APPLICABILITY The provisions of this section apply to the following: A. All new development; and, Buildings 10,000 Square Feet or Less On sites where the gross floor area of the existing building(s) is 10,000 square feet or less, expansions in square footage of land area, floor area, lot coverage, or vehicular use area as follows. a. If the expansion is less than 50%, the standards of this section apply only to the proposed expansion. Existing development on the site is subject to the zoning standards in effect at the time the existing development received zoning approval. b. If the expansion is 50% or greater or if expansions as of February 15, 1991, cumulatively result in a 50% or greater expansion in land area, floor area, lot coverage, or vehicular use area, the standards of this section apply to the entire site. Provide previously approved site/ landscape plans for reference including accurate expansion calculations. 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 or modifications that affect the site Planting Plan Vegetation Plan and Schedules Location, size, and name of existing vegetation to remain in place Ensure that all Zoning and Engineering comments and concerns are addressed. Additional comments may apply |
02/24/2014 | ANDREW CONNOR | NPPO | REVIEW | Approved | |
02/25/2014 | LAITH ALSHAMI | ENGINEERING | REVIEW | Reqs Change | Laith Alshami, Engineering and Floodplain Review, 02/28/2014, SUBJECT: Circle K Store #5318 Building Expansion DP14-0015, T14S, R15E, SECTION 20 RECEIVED: Development Plan Package on 02/03/2014 The subject project has been reviewed. The project can not be approved at this time. Address the following comments before review can continue. Prepare a detailed response that explains the revisions that where made and references the exact location in the plan where the revisions were made: Development Package: 1. The Development Package Case number is DP14-0015. Provide, on every sheet, the correct case number (A.M. 2-06.4.3). 2. Show, on the plan, the basis of bearing and the tie between the basis of bearing and one of the corners of the parcel. Provide the basis of bearing description in the general notes (A.M. 2-06.4.8.A). 3. Show all existing onsite easements including their recordation information and dimensions (A.M. 2-06.4.8.B). 4. Provide the adjacent streets information (i.e. public or private, right of way widths, recordation data, type, dimensioned width of paving curbs, curb cuts, sidewalks, etc.) as required by A.M. 2-06.4.8.C. Verify if the streets width, provided on Sheet 3 of 5, are correct. 5. Please be advised that if any part of the existing sidewalks and wheelchair ramps are in a bad condition, they will be required to be replaced by the developer/owner. Add a general note that addresses this issue. 6. Indicate the existing ground elevations on the site based on City of Tucson Datum. Include in the note the Basis of Elevation (A.M. 2-06.4.8.E). 7. Show any existing storm drainage facilities on or adjacent to the site (A.M. 2-06.4.8.F). 8. Show existing and future sight visibility triangles, including their correct dimensions, at all driveways (A.M. 2-06.4.9.H.2). 9. Provide the width of all access driveways (A.M. 2-06.4.9.H.1). 10. Show, if applicable, all proposed easements with their dimensions and recordation information as required by A.M. 2-06.4.9.L. 11. Show the building roof drainage direction (A.M. 2-06.4.9.N.2 & 3). 12. All proposed work in the public right of way will require a right of way excavation permit or a Private Improvement Agreement. Contact Richard Leigh of Transportation Department Permit and Codes at 791-5100 for additional information. If you have any questions, I can be reached at 837-4933 or Laith.Alshami@tucsonaz.gov RESUBMITTAL REQUIRED: Revised Development Plan Package |
02/27/2014 | RONALD BROWN | H/C SITE | REVIEW | Reqs Change | 1. Most all of the existing accessibility features of this project are not code compliant. a. Rework the entire accessibility requirements as per the 2012 IBC, Chapter 12 and the 2009 ICC A117.1, this includes all accessibility parking, signage, accessible routes, marked crossings, ramps and detectable warning strips. 2. Delete the accessible route down the middle of the PAAL. 3. Relocate the accessible parking space and aisle in the middle of the parking area and run an accessible route in front of the parking spaces and connect the access routes to both public right of way streets. Provide a marked crossing from the accessible parking aisle accross the PAAL to the accessible routre in front of the store. Provide a new currb ramp with flared sides and detectable warning strips. Reference attached sketch on the site plan. 4. Delete the stripped access to the accessory building. Provide another new marked crossing starting at the East corner of the building concrete patio. Extend a concrete walkway from the existing ramp and provide a 90 degree into the marked crossing. Extend a cut through the end island of the pumps and go through the curb of the opposite end. Provide a concrete walk to the toilet area. Reference attached sketch on the site plan. 5. The above solution is a suggestion only that complies with code. It is not a mandate solution. END OF REVIEW |
03/03/2014 | ROBERT SHERRY | PLUMBING-COMMERCIAL | REVIEW | Denied | 1. Revise the site drawing to include the following information: a. The location and size of water lines, and fire hydrants. b. The location of public sanitary and storm sewers, including the pipe diameter and the invert and rim elevations of all manholes and cleanouts; along with the Pima County Wastewater Management Department (PCWMD) reference number. c. The points of connection to existing public sewers. d. The locations of gas lines, communications cables, on-ground junction boxes, and street lights. e. The first floor elevation for the building Reference: City of Tucson Administrative Manual No. 2-06.0.0, Section 4.8 and Section 107.2.13, IBC 2012. 2. Revise the site plan to remove all three of the fuel dispensing pumps that are being encroached upon by the building expansion. Reference: Section 2303.1, IFC 2012. |
03/10/2014 | ZELIN CANCHOLA | COT NON-DSD | TRAFFIC | Approved | From TDOT Permits and Codes Zelin Canchola DP14-0015 Circle K expansion No modifications required in Right of Way. Existing conditions are acceptable. |
Final Status
Task End Date | Reviewer's Name | Type of Review | Description |
---|---|---|---|
03/12/2014 | FERNE RODRIGUEZ | OUT TO CUSTOMER | Completed |
03/12/2014 | CPIERCE1 | REJECT SHELF | Completed |