2-SLCIA RWY 14-32 CSPP FINAL V2 Update.pdf

PDF 10 MB Posted

Attached to
Salt Lake City Airport Decommission Runway 14-32 & Taxiway Improvements
Solicitation number
SLCDA-DCM-542405
Issued by
Salt Lake County, Salt Lake City, Utah

About this file

This Construction Safety and Phasing Plan (CSPP) is prepared by HNTB Corporation for the Salt Lake City Department of Airports, detailing the decommissioning of Runway 14-32 and associated taxiway improvements at Salt Lake City International Airport. The project, identified as SLCDA Project No. 542405, involves a comprehensive phased approach to remove existing runway infrastructure, install new taxiway (Taxiway J) pavement, markings, electrical systems, and lighting, and restore areas of pavement removal through grading and seeding. The construction is planned to occur over four phases from Spring 2026, with specific durations for each phase ranging from 10 to 21 calendar days, and will involve temporary closures of various taxiways and runways to facilitate the work.

The project prioritizes aviation safety throughout the construction process, with detailed provisions for coordinating construction activities, managing airport operations, protecting navigation aids, controlling contractor access, managing wildlife and foreign object debris, and maintaining clear communication between the contractor, airport operations, and the FAA. The phasing plan includes specific safety measures such as barricading construction areas, marking and lighting hazards, maintaining emergency vehicle access, and ensuring minimal disruption to airport operations. The construction will involve removing pavement markings, deactivating runway lighting, installing new taxiway infrastructure, and restoring disturbed areas, with careful attention to maintaining airport safety standards and minimizing potential risks during the construction process.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

SALT LAKE CITY INTERNATIONAL AIRPORT

SALT LAKE CITY, UTAH

October 2, 2025

Prepared for:

Salt Lake City Department of Airports

PO Box 145550

Salt Lake City, UT 84114

Prepared By:

HNTB Corporation

910 West Legacy Center Way, 4th Floor

Midvale, UT 84047

CONSTRUCTION SAFETY AND PHASING PLAN (CSPP)

DECOMMISSION RUNWAY 14-32 AND TAXIWAY

IMPROVEMENTS

SLCDA Project No.: 542405

This page intentionally blank

Salt Lake City International Airport

Decommission Runway 14-32 and Taxiway Improvements

Construction Safety and Phasing Plan (CSPP) i

SALT LAKE CITY INTERNATIONAL AIRPORT

DECOMMISSION RUNWAY 14-32 AND TAXIWAY IMPROVEMENTS

SLCDA PROJECT NO. 542405

CONSTRUCTION SAFETY AND PHASING PLAN (CSPP)

Table of Contents

A. OVERVIEW

B. PROJECT SCOPE

C. PLAN REQUIREMENTS

1. COORDINATION

a. Predesign Conference

b. Pre-bid Conference

c. Preconstruction Conference

d. Contractor Progress Meetings

e. Scope or Schedule Changes

f. FAA ATO Coordination

2. PHASING

3. AREAS AND OPERATIONS AFFECTED BY CONSTRUCTION ACTIVITY

4. PROTECTION OF NAVIGATION AIDS (NAVAIDS)

5. CONTRACTOR ACCESS

a. Location of Stockpiled Construction Materials

b. Vehicle and Pedestrian Operations

c. Maintenance of the Secured Area of the Airport

6. WILDLIFE MANAGEMENT

a. Trash

b. Standing Water

c. Tall Grass and Seeds

d. Poorly Maintained Fencing and Gates

e. Disruption of Existing Wildlife Habitat

7. FOREIGN OBJECT DEBRIS (FOD) MANAGEMENT

8. HAZARDOUS MATERIALS (HAZMAT) MANAGEMENT

ii

9. NOTIFICATION OF CONSTRUCTION ACTIVITIES

a. List of Responsible Points of Contact

b. Notices to Airmen (NOTAM)

c. Emergency Notification Procedures

d. Coordination with ARFF Personnel

e. Notification to the FAA

10. INSPECTION REQUIREMENTS

a. Daily (or more frequent) Inspections

b. Final Inspections

c. FAA Certification Inspections

11. UNDERGROUND UTILITIES

12. PENALTIES

13. SPECIAL CONDITIONS

14. RUNWAY AND TAXIWAY VISUAL AIDS

a. General

b. Markings

c. Lighting and Visual NAVAIDS

d. Signs, Temporary and Permanent

15. MARKING AND SIGNS FOR ACCESS ROUTES

16. HAZARD MARKING AND LIGHTING

a. Purpose

b. Barricades

c. Red Hazard Marking Lights

d. Supplemental Signs

e. Air Operations Area – General

f. Air Operations Area – Runway/Taxiway Intersections

g. Air Operations Area – Other

h. Maintenance

17. PROTECTION OF RUNWAY AND TAXIWAY SAFETY AREAS

a. Runway Safety Area (RSA)

b. Runway Object Free Area (ROFA) iii

c. Taxiway Safety Area (TSA)

d. Taxiway Object Free Area (TOFA)

e. Obstacle Free Zone (OFZ)

f. Runway Protected Surfaces (Part 77)

g. Runway Approach/Departure Surfaces

18. OTHER LIMITATIONS ON CONSTRUCTION

a. Prohibitions

b. Restrictions

D. PHASING - DECOMMISSION RWY 14-32 AND TWY IMPROVEMENTS

1. PHASING PLAN

a. Phase Elements

b. Construction Safety Drawings

2. AREAS AND OPERATIONS AFFECTED BY CONSTRUCTION ACTIVITY

a. Identification of Affected Areas

b. Mitigation of Effects

3. DETAILED PHASE DESCRIPTIONS

PHASE 1A

PHASE 1B

PHASE 2

PHASE 3A

PHASE 3B

LIST OF ATTACHMENTS

ATTACHMENT A - FAA CIRCULAR – AC 150/5370-2G (Excerpts)

ATTACHMENT B - CONSTRUCTION PHASING PLANS

A. OVERVIEW

Aviation safety is the primary consideration at airports, especially during construction. This

Construction Safety and Phasing Plan (CSPP), combined with the Contractor-prepared Safety Plan

Compliance Document (SPCD), are the primary tools to ensure safety compliance when coordinating construction activities with airport operations. These documents are intended to identify aspects of the construction project that may pose a potential safety hazard to airport operations and describe associated mitigation procedures for each hazard.

The CSPP sets forth benchmarks and requirements for the project to help ensure the highest levels of safety, security, and efficiency at Salt Lake City International Airport throughout construction. The

CSPP follows the guidelines and format described in FAA Advisory Circular 150/5370-2G Operational

Safety on Airports During Construction. See the website:

<https://www.faa.gov/documentLibrary/media/Advisory_Circular/ 150_5370-2G.pdf>

The CSPP is a standalone document written to supplement and compliment the safety and security requirements of the following documents (or most current versions) and referenced codes and requirements:

Advisor Circular 150/5370-2G, Operational Safety on Airports During Construction

Federal Aviation Administration

12/13/2017

Construction Safety and Security Compliance Manual

Salt Lake City Department of Airports

March 2018 (or most current edition)

The CSPP is to be reviewed and used by all personnel involved in the construction of the project. The

CSPP covers actions of construction personnel and equipment, inspection personnel, and airport staff.

This document has been developed to maximize the performance and safety of construction activity while minimizing interruptions to airport operations. Strict adherence to the provisions of the CSPP by all personnel assigned to or visiting the construction site is mandatory for AIP-funded construction projects.

The Contractor shall also be required to prepare and submit a Safety Plan Compliance Document

(SPCD) to the Airport for review and approval prior to issuance of a construction Notice to Proceed.

The Contractor’s SPCD shall describe specifically how the Contractor will comply with the requirements set forth in this CSPP. Additional requirements for development of the Contractor’s

SPCD can be found in FAA AC 150/5370-2G.

The Airport has the authority to direct the Contractor to immediately cease any operations found to be in non-compliance with the provisions of the CSPP or the approved SPCD, or any other requirements identified in the project drawings or specifications. In the event of any violation of non-compliance issue, a safety meeting will be convened for the purpose of reviewing violations to the provisions of the CSPP/SPCD. The Contractor will not be allowed to resume any construction operations until conclusion of the safety meeting, and all corrective actions required by the Airport have been implemented to the Airport’s satisfaction. Any additional costs resulting from non-compliance, including delay costs, shall be solely the Contractor’s responsibility, and no additional payments or contract time will be allowed due to non-compliance with the provisions of the CSPP and/or approved SPCD.

B. PROJECT SCOPE

The Decommission Runway 14-32 and Taxiway Improvements Project consists of the following main elements:

• Removal of airfield pavement at the south end of existing Runway 14-32 from Taxiway M/Runway

17-35 on the south to Taxiway P/Taxiway N at the north.

• Removal of airfield pavement at existing Runway 14-32 blast pad at the north end of Runway 14-

32, north of Taxiway Q.

• Removal of existing Runway 14/32 pavement markings, guidance signs, edge and threshold lighting and electrical, PAPI, and wind cones.

• Installation of taxiway edge lighting and electrical, pavement markings, guidance signs, and pavement for new Taxiway J.

• Landscaping (topsoil and seeding) in areas of pavement removal.

The general layout of existing Runway 14-32 and proposed Taxiway J is shown in Figure 1 below, as well as on the Construction Site Plan (Drawing G0-10).

Figure 1-Construction Site Plan

Construction locations and activities have been identified on the drawings and their anticipated impact to airport operations have been assessed. Impact of construction to Airport Operations Areas (AOA) is discussed in detail in Section C. PLAN REQUIREMENTS and graphically depicted in the Construction Phasing

Plans (Drawings G1-0 to G1-6). These plans are included in the drawing set that will be issued for bidding and construction.

C. PLAN REQUIREMENTS

1. COORDINATION

All Contractors conducting construction on the airport, including any tenant lease areas, are required to attend pre-bid and preconstruction conferences to describe operational safety procedures and requirements during construction. In addition, the contactor is required to attend weekly construction progress meetings through the performance of the contract to coordinate work items, scope or schedule changes, and any needed coordination with the FAA Air Traffic

Organization (ATO).

a. Predesign Conference

A predesign conference for the Runway 14-32 and Taxiway Improvements Project was held on October 5, 2023. The initial scope of work included removal of a majority of the asphalt pavement along Runway 14-32 and modifications to the existing taxiway connections at J, M, P, and Q. During the meeting, it was decided that the majority of Runway 14-32 would be preserved and repurposed to Taxiway J.

b. Pre-bid Conference

The Airport will conduct a pre-bid conference for large projects or projects with unique features to help clarify and explain scope of work and safety measures required by the contract. The meeting will be held approximately 10 working days prior to the bid opening date.

Typical agenda items included in the pre-bid meeting are new or unique construction methods, new construction procedures (i.e. statistical acceptance testing), operational safety requirements, and Disadvantaged Business Enterprise (DBE) and other civil rights and labor requirements.

One of the focuses of the pre-bid Conference is to cover relevant information concerning the Contractor’s requirements for developing and submitting an SPCD for SLCDA review and approval. This will include an identification of elements required in the SPCD.

Any changes or modifications recommended during the pre-bid conference may be considered for inclusion in an addendum to the bid documents. A copy of any addendums will be furnished to each registered plan holder.

The pre-bid conference agenda, sign-in sheet, questions, and responses will be furnished to registered plan holders by posting on the City’s on-line bid/proposal web site.

c. Preconstruction Conference

A preconstruction conference, convened and conducted by the Airport, will be conducted to discuss operational safety, testing, quality control, quality acceptance, security, safety, labor requirements, environmental factors, and other issues. This meeting, among all parties affected by the construction, is intended to facilitate a better understanding of potential problems and possible solutions during the performance of the construction contract.

The preconstruction conference will be conducted as soon as practicable after the contract has been awarded and before issuance of the notice to proceed.

The expected participants for this meeting include the following parties:

1) Airport Engineering.

2) Airport Operations.

3) Airport Maintenance (optional).

4) Airport resident engineer.

5) Airport management.

6) Airport’s Testing laboratory representative.

7) Airport’s Design Engineer/Consultant.

8) Contractor and subcontractor(s).

9) Contractor’s project superintendent.

10) Contractor’s project clerk.

11) Airport users impacted by the proposed construction.

12) Utility companies affected by the proposed construction.

13) Federal, state, or local agencies affected by the proposed construction.

14) FAA ADO Project Manager (for AIP projects)

15) Representative of FAA Airports regional or field office.

The FAA Airports regional or field office should ensure that appropriate FAA offices (Air

Traffic, Flight Standards, etc.), military installations, and Federal agencies that may have an interest in the project are notified of the upcoming construction.

The Airport or its authorized consultant will prepare an agenda prior to the pre-construction conference. This will include but is not limited to:

1) The scope of the project and the sequence and timing of all operations.

2) Relationship between the Airport representative and the Contractor.

3) Relationship between the FAA and the Airport (sponsor).

4) Identification of the Contractor’s superintendent and a discussion of his/her authority and responsibilities.

5) Designation of Airport (sponsor) representative responsible for coordinating

NOTAMs with the FAA Flight Service Station. Planned coordination (Airport

Management), control and communications are discussed in detail in Paragraph 9.

NOTIFICATION OF CONSTRUCTION ACTIVITIES.

6) Scheduling of work and the need to perform certain items at various stages of the project, including operational safety problems that might arise because of the proposed work.

7) Notice to proceed date.

8) Safety during construction, including the responsibility for marking and lighting of closed and hazardous areas. See AC 150/5370-2G - Operational Safety on Airports

During Construction and AC 150/5340-1M - Standards for Airport Markings, current edition, for detailed information.

9) Airport security and badging requirements.

10) FOD and dust control.

11) Temporary erosion control.

12) Protection of protected airspace surfaces.

13) Construction access, Contractor employee parking, traffic haul routes, gate guards, crossing guards, etc.

14) Schedule for weekly construction meetings.

15) Potential long-lead materials or equipment.

16) Other items as needed.

Sample agenda items for the preconstruction conference can be found in Appendix D of AC

150/5370-12B - Quality Management for Federally Funded Airport Construction Projects.

d. Contractor Progress Meetings

Weekly construction meetings will be scheduled by SLCDA to discuss work progress and to address current or potential security and safety concerns. The standing day, time, and location of the meeting shall be discussed and agreed to at the preconstruction conference.

The frequency of these meetings may be increased as determined necessary by SLCDA for specific work items or schedule recovery plans. Operational safety and security shall be a standing agenda item for discussion during these weekly construction progress meetings.

e. Scope or Schedule Changes

Changes in the scope and/or duration of the project may necessitate revisions to the CSPP.

The Airport will notify the FAA Airports District office of any proposed changes to this CSPP as appropriate. Changes to this document require review and approval by the Airport and the FAA prior to implementation. In addition, the Airport will coordinate proposed changes with applicable local and federal government agencies (i.e. EPA, OSHA, TSA, Utah DEQ, etc.), as applicable.

f. FAA ATO Coordination

Early coordination with FAA ATO is required to schedule any FAA airway facility shutdown and restart. Relocation or adjustments to NAVAIDs, or changes to grades in NAVAID critical areas may require an FAA flight inspection prior to re-commissioning the facility. Flight inspections must be coordinated and scheduled well in advance of the intended facility restart and may require a reimbursable agreement between the Airport and FAA ATO.

Reimbursable agreements should be coordinated a minimum of 12 months prior to the start of construction. See Paragraph 9.e.3.2 for required FAA notification regarding FAA owned

NAVAIDs.

2. PHASING

A detailed description of the construction phasing plan is presented in Section D. PHASING.

3. AREAS AND OPERATIONS AFFECTED BY CONSTRUCTION ACTIVITY

The intent of the construction phasing plan is to allow runways, taxiways and other airfield surfaces to remain in use by aircraft to the maximum extent possible without compromising safety, while at the same time, providing reasonable work areas for the Contractor to perform the required construction. Anticipated runway and taxiway closures and associated operational effects are described in Section D. PHASING.

4. PROTECTION OF NAVIGATION AIDS (NAVAIDS)

Before commencing construction activity, parking vehicles, or storing construction equipment and materials near any NAVAID, the Contractor shall coordinate with SLCDA Engineering and

Operations who will coordinate with the appropriate FAA ATO to evaluate the effects of construction activity and determine the required clear distances and direction from the NAVAID the Contractor must remain. (See Paragraph 9.e.3 NAVAIDS). Construction activities, materials/equipment storage, and vehicle parking near electronic NAVAIDs require special consideration since they may interfere with lines of site and signals essential to air navigation.

Stockpiling materials, and the movement and parking of equipment that may interfere with the line of sight from the FAA tower or disrupt the electronic signals is prohibited.

5. CONTRACTOR ACCESS

Contractor access to the construction site(s), haul routes, locations of disposal/stockpile areas are shown in the drawings. Contractor employee vehicles are not allowed within the AOA.

a. Location of Stockpiled Construction Materials

Stockpiled materials and equipment storage are not permitted within the Runway/Taxiway

Safety Areas (RSA/TSA) Obstacle Free Zones (OFZ) or Runway/Taxiway Obstacle Free Areas

(ROFA/TOFA) of an operational runway or taxiway. All demolished pavement materials and unclassified excavation materials shall be removed and legally disposed of off airport property and not stockpiled on airport property, unless the material is approved by the

Airport for recycling and reuse. Stockpiling material shall be constrained in a manner to prevent movement resulting from both aircraft jet blast and wind conditions. Stockpile height shall not penetrate runway primary surfaces, transitional surfaces, or other protected airspace. (See Paragraph 17 for the dimensions and restrictions regarding pertinent protected airspace and surface areas at SLC.)

The Contractor shall ensure that stockpiled materials and equipment adjacent to these areas are prominently marked and lighted during hours of restricted visibility or darkness.

(Refer to Paragraph 16 for hazard lighting and marking requirements.) This includes determining and verifying that materials are stabilized and stored at an approved location so as not to be a hazard to aircraft operations and to prevent attraction of wildlife and

Foreign Object Debris/Damage (FOD). (Refer to Paragraphs 6 and 7 below for wildlife management and FOD.) Stockpiled material shall be protected by silt fence surrounding the material to prevent FOD from moving onto the active airfield pavements or polluting watercourses.

b. Vehicle and Pedestrian Operations

Vehicle and pedestrian access routes for airport construction projects must be controlled to prevent inadvertent or unauthorized entry of persons, vehicles, or animals onto the AOA.

The Airport will coordinate requirements for vehicle operations with the affected airport tenants, other Contractors and the FAA air traffic manager.

All personnel operating a motor vehicle on airport property shall have a valid driver’s license. Utah state motor vehicle laws will be observed when operating a motor vehicle on the airport. Aircraft traffic will continue to use existing runways, aprons, and taxiways of the Airport during the time that work under a contract is being performed. The Contractor shall, at all times, conduct the work as to create no hindrance, hazard, or obstacle to aircraft using the Airport. The speed limit on all airside roadways is 20 miles per hour unless otherwise posted.

Vehicle and pedestrian requirements are as follows:

i. Training requirements for vehicle drivers. To ensure compliance with SLCDA’s vehicle rules and regulations, all personnel who drive a vehicle or operate equipment on the

AOA shall take the “Airfield Ramp Driving” computer-based training before operating on the AOA, unless properly escorted. The training includes proper vehicle operations on various areas under normal, lost communications, and emergency conditions.

Contractors and their personnel will not have unescorted access to the AMA.

ii. Employee Vehicle Parking. Employee vehicle parking will be designated on the drawings. The contract drawings show a vehicle parking area for Contractor employee personal vehicles. Employee personal vehicles are not allowed inside the AOA, and the

Contractor shall be responsible for transport of workers from the employee vehicle parking area to the work sites via ramp-permitted vehicles. Project work area(s) shall be bounded by the approved barricades construction vehicle area operation limits.

Refer to Paragraph 16 of this document for details on approved barricades.

iii. Construction Equipment Parking. Contractor employees must park and service all construction vehicles in an area designated by the Airport outside the OFZ and never in the safety area of an active runway or taxiway. Contractor parking and equipment staging areas will be identified as the Contractor Staging Area and are graphically identified in the drawing set. Inactive equipment shall not be parked on a closed taxiway or runway unless a complex setup procedure makes movement of specialized equipment infeasible. If it is necessary to leave specialized equipment on a closed taxiway or runway at night, the equipment shall be well lighted. Employees shall also park construction vehicles outside the OFA when not in use by construction personnel

(for example, overnight, on weekends, or during other periods when construction is not active). Parking areas must not obstruct the clear line of sight by the ATCT to any taxiway or runway under air traffic control, nor obstruct any runway visual aids, signs, or navigation aids. SLCDA will ensure construction equipment parking locations do not effect airport design criteria, surfaces established by 14 CFR Part 77, Safe, Efficient Use, and Preservation of the Navigable Airspace (Part 77), and on NAVAIDs and Instrument

Approach Procedures (IAP). See Paragraph 9 below for further information.

iv. Access and Haul Roads. All construction vehicles and personnel shall be restricted to the immediate work areas specified for each construction phase. These areas include the haul routes into the work area, the designated Contractor staging area and the area under construction. Use of alternate haul routes or staging areas by the Contractor shall not be permitted without prior notification and approval by airport engineering and airport operations. Access or haul routes used by Contractor vehicles must be clearly marked to prevent inadvertent entry to areas open to airport operations. Construction traffic must remain on the haul roads, never straying from the approved paths.

Maintenance and upkeep of the haul roads are the responsibility of the Contractor. A mechanical vacuum-sweeper shall be used to remove FOD and contaminants from paved haul routes. Application of water on dirt or gravel haul routes must be provided as often as necessary to control dust. Haul roads in any airport traffic areas must be especially monitored for dust and debris to prevent any potential FOD situations. The

Contractor is responsible for any damage caused by construction traffic on the haul roads, regardless of whether in an approved or un-approved traffic area. Special attention shall be given to ensure that if construction traffic is to share or cross any

Aircraft Rescue Fire Fighter (ARFF) routes that ARFF right of way is not impeded at any time, and that construction traffic on haul roads does not interfere with NAVAIDs or approach surfaces of operational runways. Following construction completion, the

Contractor shall grade, reseed, clean or otherwise restore the haul route areas to their original conditions prior to construction activities. Work necessary in maintaining the haul roads and compliance with safety and security requirements is considered incidental to the project, and therefore, shall not be directly paid for.

v. Marking and lighting of vehicles. All vehicles and equipment operating on the Airport and in the general vicinity of the safety area or in aircraft movement areas must be marked with flashing yellow/amber beacons or orange and white flags during daylight hours in accordance with AC 150/5210-5D - Painting, Marking, and Lighting of Vehicles

Used on an Airport. In addition, the vehicles and equipment shall have identifying symbols at a minimum of 2-inch block-type characters of contrasting color that are easily legible. During hours of darkness or low visibility they shall be marked with at least flashing yellow/amber beacons. Beacons and flags must be maintained to standards and in good working and operational condition. Beacons must be located on the uppermost part of the vehicle structure, visible from any direction, have peak intensity within the range of 40 to 400 candelas, and flash 75 +/- 15 flashes per minute.

Flags shall be 3’ by 3’ with alternating 1’ by 1’ international orange and white squares and shall be replaced by the Contractor if they become faded, discolored, or ragged as determined by SLCDA.

vi. Required Escorts. At no time will vehicles or personnel enter portions of the secure AOA outside the contract area unless permitted and accompanied by an airport approved escort. All construction-related activity taking place within any active area of the AMA requires the presence of a SLCDA escort having radio communication with the FAA control tower unless prior approval is obtained from Airport Operations Manager (OPS

60). Spotters and/or flaggers having radio or telephone contact with the SLCDA may be used with the approval of the on-duty Airport Operations Manager (OPS 60). Any command or instruction given by the control tower, the SLCDA, flaggers, or spotters shall be immediately obeyed by the equipment/vehicle operator.

vii. Situational Awareness. Vehicle drivers must confirm by personal observation that no aircraft is approaching their position (either in the air or on the ground) when given clearance to cross a runway, taxiway, or any other area open to aircraft operations. In addition, it is the responsibility of the escort vehicle driver to verify the movement/position of all escorted vehicles at any given time.

viii. Two-way Radio Communication Procedures. All communication with the Air Traffic

Control Tower or other elements of the Airport shall be through the SLCDA engineer and/or airport operations. Operations personal or SLCDA Engineer will monitor air traffic control frequencies at all times. Contractors and their personnel do not have unescorted access to the AMA and therefore must coordinate with the project engineer for an escort to access the AMA. At no time shall active taxiways or runways be crossed by construction equipment without notification and proper approval/clearance from

SLCDA Operations and air traffic control.

Operations personal or SLCDA Engineer shall maintain radio communication with air traffic control and monitor air traffic control frequencies at all times. Air traffic control frequencies are as follows:

ATIS: 124.75 MHz / 125.625 MHz

UNICOM: 122.95 MHz

SLC GROUND: 121.9 MHz / 133.65 MHz / 348.6 MHz

SLC TOWER: 118.3 MHz / 119.05 MHz / 132.65 MHz

c. Maintenance of the Secured Area of the Airport

Salt Lake City International is subject to 49 CFR Part 1542, Airport Security, and must meet standards for access control, movement of ground vehicles, and identification of construction Contractor and tenant personnel. The Contractor and its personnel shall be familiar with the security requirements and policies of the Airport.

i. Fencing and gates. The Airport and the Contractors must also maintain a high level of security during construction when access points are created in the security fencing to permit construction vehicle access. Temporary gates shall be equipped and/or staffed by construction personnel to prevent unauthorized access by vehicles, animals or people. Procedures conforming to SLCDA security protocols shall be in place to ensure that only authorized persons and vehicles have access to the AOA and to prohibit

“piggybacking” behind another person or vehicle. Access shall be made available at all times to all airport emergency vehicles traveling to operations areas within the proximity of the construction work zone. The Department of Transportation (DOT) document DOT/FAA/AR-00/52, Recommended Security Guidelines for Airport

Planning and Construction, provides more specific information on fencing. A copy of this document can be obtained from the Airport Consultants Council, Airports Council

International, or American Association of Airport Executives.

ii. Badging and other security requirements can be found in the “Security

Requirements” Chapter of the SLCIA Construction Safety and Security Compliance

Manual.

6. WILDLIFE MANAGEMENT

Construction Contractors must carefully control and continuously remove waste or loose materials that could attract wildlife. Contractor personnel shall be aware of and avoid construction activities that have the potential to create wildlife attractants on the airport.

a. Trash

Food scraps from construction personnel shall be collected and properly disposed of.

b. Standing Water

Water shall not be allowed to collect and pool for more than any single 24-hour period.

c. Tall Grass and Seeds

The use of millet seed in turfing and seeding operations shall not be permitted. Turf within the construction site shall be maintained by the Contractor in such a manner that the height will not constitute an attraction to wildlife.

d. Poorly Maintained Fencing and Gates

The Contractor shall protect and maintain existing and Contractor-installed fencing and gates, and immediately repair any damage to fences or gates caused by Contractor’s operations.

e. Disruption of Existing Wildlife Habitat

The Contractor shall notify the airport engineering representative or airport operations immediately if personnel recognize a disruption to wildlife habitat. The Airport has small burrowing mammals that live within the AOA, and these mammals will attract more hazardous birds of prey when their habitats have been disrupted.

7. FOREIGN OBJECT DEBRIS (FOD) MANAGEMENT

Special care and measures shall be taken to prevent Foreign Object Debris / Damage (FOD) when working in an airport environment. The Contractor shall be held responsible for implementing the approved FOD Management Plan in accordance with the Contractor’s approved SPCD. The

Contractor’s FOD Management Plan shall have procedures for prevention, regular cleanup, and containment of construction material and debris.

FOD prevention aims to stop objects from becoming FOD. This is a proactive approach to eliminating FOD before it becomes a hazard. Some measures for FOD prevention include: a tool control program, FOD identification incorporated into pre-operational and post-operational inspections of equipment, and FOD recognition incorporated into Point of Entry (POE) inspections.

The Contractor will ensure all vehicles related to the construction project using paved surfaces in the AOA shall be free of any debris that could create a FOD hazard.

Regular cleanup ensures that FOD is picked up before it causes damage or injury. Special attention shall be given to the cleaning of cracks and pavement joints. All taxiways, aprons, and runways must remain clean. Contractors shall provide their own equipment for vehicle and equipment washing and clean up. Immediate access to a vacuum-sweeper is required when construction occurs on any pavement area inside the AOA, unless an appropriate alternative has been approved by the Airport Operations Manager (OPS 60) and Engineer.

FOD containment ensures waste and materials do not become FOD during wind and jet blast conditions, or attract wildlife. Waste containers with securely attached lids are required on construction sites and the staging area. Waste container lids must have a securing mechanism or be made of a material that will not allow the lid to be blown open in high winds. Special attention shall be given to securing lightweight construction material (such as concrete insulating blankets, tarps, insulation, etc.). Specific securing procedures and/or chain-link enclosures may be required.

8. HAZARDOUS MATERIALS (HAZMAT) MANAGEMENT

Contractors operating construction vehicles and equipment on the airport must be prepared to expeditiously contain and clean-up spills resulting from fuel, hydraulic fluid, or other chemical fluid leaks. Transport and handling of other hazardous materials on the airport also requires special procedures. The Contractor is required to develop and implement spill prevention and response procedures for vehicle operations. The Contractor shall incorporate these procedures into their SPCD. This includes maintenance of appropriate MSDS data and appropriate prevention and response equipment on-site. The Contractor shall notify the Engineer immediately in the event of any spill.

9. NOTIFICATION OF CONSTRUCTION ACTIVITIES

a. List of Responsible Points of Contact

Telephone Hours

Emergency:

Police/Fire/Rescue (801) 575-2911

Information, Compliance, and Assistance:

Airport Operations Manager

(Ops 60)

(801) 575-2460 24 hrs/day, 7 days/wk

Airport Control Center (801) 575-2401 24 hrs/day, 7 days/wk

Additional Information, Contacts:

Airport Engineering (801)575-2900 Mon-Fri, 8:00am – 4:30pm

Airport Badging (801) 575-2423 Mon-Wed, 8:00am-6:00pm;

Thur, 9:00am-6:30pm;

Fri, 8:00am-6:30pm;

Sat, Sun, Holidays, CLOSED

Security (801) 575-2373 (Mon-Fri, 8:00am – 4:30pm)

b. Notices to Airmen (NOTAM)

Airport Operations is the only entity that may initiate or cancel any NOTAM and open oclose or close a runway or taxiway. The Airport will coordinate the issuance, maintenance, and cancellation of NOTAMs about airport conditions resulting from construction activities with tenants and the local air traffic facility (control tower, approach control, or air traffic control center), and will provide information on closed or hazardous conditions on airport movement areas to the FAA Flight Service Station (FSS) so it can issue a NOTAM. The Airport is responsible for filing and maintaining a list of authorized representatives with the FSS.

Only the FAA may issue or cancel NOTAMs on shutdown or irregular operation of FAA owned facilities.

Any airfield closures required for construction shall be coordinated through the Airport

Operations Manager and the Airport’s duly appointed construction management representative. The Airport will notify the Contractor once the NOTAM becomes effective in order to initiate the airfield closure. See Section D. PHASING for planned closures for this project which require issuance of a NOTAM.

Notes:

i. The Contractor shall provide a written request for all closures of taxiways or runways at least 72 hours in advance of the closure. This request shall include the times requested and the Contractor’s proposed detailed schedule of operations within the area.

ii. The Contractor shall notify the Engineer at least 72 hours in advance of using any equipment that may penetrate the runway primary surface or associated surfaces (14

CFR Part 77).

c. Emergency Notification Procedures

In the event of an emergency, the Contractor shall be required to contact emergency services by calling (801) 575-2911.

In the event of an aircraft emergency, severe weather conditions, or any issue as determined by SLCDA that may affect aircraft operations, the Contractor’s personnel and/or equipment may be required to immediately vacate the area(s) affected. Points of contact for the various parties involved with the project shall be identified and shared at the pre-construction meeting among the various parties. (See Paragraph 1.c Pre-construction

Conference.) Specific emergency notification procedures shall be incorporated into the

Contractor’s SPCD.

d. Coordination with ARFF Personnel

The Contractor shall coordinate, through the duly appointed airport representative, with

ARFF personnel, mutual aid providers, and other emergency services if construction requires the following:

• The deactivation and subsequent reactivation of water lines or fire hydrants, or

• The re-routing, blocking and restoration of emergency access routes, or

• The use of hazardous materials on the airfield.

Procedures and methods for addressing any planned or emergency response actions on the airfield concerning this project shall be established and implemented prior to the start of construction.

e. Notification to the FAA

1) Part 77. Any person proposing construction or alteration of objects that affect navigable airspace, as defined in 14 CFR Part 77, must notify the FAA. This includes construction equipment and proposed parking areas for this equipment

(i.e. batch/crushing plants, cranes, and other equipment) on airports. FAA Form

7460-1, Notice of Proposed Construction or Alteration can be used for this purpose and submitted to the appropriated FAA Airports Regional or District

Office.

2) Part 157. With some exceptions, Title 14 CFR Part 157, Notice of Construction, Alteration, Activation, and Deactivation of Airports requires that the Airport notify the FAA in writing whenever a non-Federally funded project involves the construction of a new airport; the construction, realigning, altering, activating, or abandoning of a runway, landing strip, or associated taxiway; or the deactivation or abandoning of an entire airport. Notification involves submitting FAA Form

7480-1, Notice of Landing Area Proposal, to the nearest FAA Airports Regional or

District Office.

3) NAVAIDS. For emergency (short-notice) notification about impacts to both airport-owned and FAA-owned NAVAIDs, contact: (866) 432-2622.

1. Airport Owned/FAA Maintained. If construction operations require a shutdown of more than 24 hours, or more than 4 hours daily on consecutive days, of a NAVAID owned by the airport but maintained by the FAA, provide a 45-day minimum notice to FAA ATO/Technical

Operations prior to facility shutdown.

2. FAA Owned. The Airport must notify the appropriated FAA ATO Service

Area Planning and Requirements (P&R) Group a minimum of 45 days prior to implementing an event that causes impacts to NAVAIDs. (Impacts to FAA equipment covered by a Reimbursable Agreement (RA) do not have to be reported by the Airport). Coordinate work for an FAA owned

NAVAID shutdown with the local FAA ATO/Technical Operations office, including any necessary reimbursable agreements and flight checks.

Detail procedures that address unanticipated utility outages and cable cuts that could impact FAA NAVAIDs. In addition, provide seven days’ notice to schedule the actual shutdown.

10. INSPECTION REQUIREMENTS

a. Daily (or more frequent) Inspections

Inspections shall be conducted by the Contractor at least daily, but more frequently if necessary, to ensure conformance with the CSPP. A sample checklist is provided in

Attachment A of this document. In addition to Contractor’s required inspections, Airport

Operations will inspect the construction site up-to three (3) times per day to ensure compliance with the CSPP and the Contractor’s SPCD.

b. Final Inspections

Areas that have been closed for construction must have a final inspection from Airport

Engineering and/or Airport Operations prior to being opened to aircraft or vehicle operations. Airport Operations shall inspect runways, taxiways, safety areas, or areas where aircraft operate prior to that area being opened to aircraft, as well as roadways prior to opening to vehicle traffic. Discrepancies to Part 139 requirements discovered during the inspection shall be corrected by the Contractor prior to the area being opened.

c. FAA Certification Inspections

Extended runway closures may require safety inspections at certificated airports prior to resuming air carrier service. The Airport will coordinate with the FAA Airport Certification

Safety Inspector (ACSI) to determine if a certification inspection will be necessary.

11. UNDERGROUND UTILITIES

Special attention shall be given to preventing unscheduled interruption of utility services and facilities. Where required due to construction purposes, the FAA shall locate all of their underground cables. The Contractor shall locate and/or arrange for the location of all the underground cables and shall pothole all buried utilities prior to excavation. When a known underground cable is damaged due to the Contractor’s negligence the Contractor shall immediately repair the cable affected at their own expense. Full coordination between airport staff, field inspectors, and construction personnel will be exercised to ensure that all airport power and control cables are fully protected prior to any excavation. Locations of known cabling shall be marked by the Contractor prior to beginning excavation.

12. PENALTIES

Failure on the part of the Contractor to adhere to prescribed requirements may have consequences that jeopardize the health, safety or lives of customers and employees at the airport. The Airport may issue warnings on the first offense based upon the circumstances of the incident. Individuals involved in non-compliance violations may be required to surrender their

Airport ID badges and/or be prohibited from working at the airport, pending an investigation of the matter.

• Penalties for violations related to airport safety and security procedures include the following:

• Warning citation, airport ID badge confiscation, (if applicable) retraining, and a letter from the employer stating what action if any has been taken to prevent this from happening again.

• Project shutdown and/or removal of personnel involved from the AOA.

• Class B Misdemeanor citation – Salt Lake City Ordinance Title 16.

Note: Project shutdown or misdemeanor citations may be issued on a first offense. When construction operations are suspended, activity shall not resume until all deficiencies are corrected to the satisfaction of the Airport.

13. SPECIAL CONDITIONS

In the event of an aircraft emergency, the Contractor’s personnel and/or equipment may be required to immediately vacate the area. The Contractor will receive notification from Airport

Operations and/or Airport Engineering when special conditions require the construction site to be vacated. In any event, extreme care shall be exercised should construction personnel identify any ARFF (Airport Rescue and Fire-Fighting) vehicle moving toward the runway with emergency lights displayed. This will generally mean that an emergency is imminent. See Paragraph 9.c.

14. RUNWAY AND TAXIWAY VISUAL AIDS

Areas where aircraft will be operating shall be clearly and visibly separated from construction areas, including closed runways. Throughout the duration of the construction project, the

Contractor shall inspect and verify that these areas remain clearly marked and visible at all times and that marking, lighting, signs and visual NAVAIDs remain in place and operational.

a. General

Airport markings, lighting, signs, and visual NAVAIDs must be clearly visible to pilots, not misleading, confusing, or deceptive. All markings, signs and barriers must be secured in place to prevent movement by prop wash, jet blast, wing vortices, or other wind currents and constructed of materials that will minimize damage to an aircraft in the event of inadvertent contact.

b. Markings

All taxiway centerline markings leading into the project work site shall be blackened out prior to the start of each phase of construction, including runway leadoff lines. Locations of centerline markings to be blackened out are graphically illustrated in the project drawings.

These markings are to be re-applied at the completion of construction operations. Markings must be in compliance with the standards of AC 150/5340-1M - Standards for Airport

Markings, or most current edition, and the drawings and technical specifications of the project.

Temporarily Closed Taxiways. Place barricades outside the safety area of intersecting taxiways. For runway/taxiway intersections, an “X” pavement marking shall be placed at the entrance to the closed taxiway from the runway.

c. Lighting and Visual NAVAIDS

All taxiway edge lights in those sections of taxiways closed to aircraft traffic shall be either de-energized or blacked out by use of an appropriately cut length of PVC pipe. Centerline lighting that conflicts with the temporarily relocated or closed taxiway routing shall be either de-energized, removed from the circuit by use of jumpers or as detailed in the project drawing set. This work shall be completed by the Contractor.

d. Signs, Temporary and Permanent

All airfield lighted and unlighted signs in those sections of taxiways closed to aircraft traffic will be de-energized and blacked out by use of plastic sheeting or other approved black-out method.

15. MARKING AND SIGNS FOR ACCESS ROUTES

Location of haul routes on the airport site shall be as shown in the project drawings. It shall be the Contractor’s responsibility to coordinate off-site haul routes with the appropriate owner who has jurisdiction over the affected route. The haul routes, to the extent possible, shall be marked and signed in accordance with FAA airfield signage requirements, the Federal Highway

Administration Manual on Uniform Traffic Control Devices (MUTCD) and/or state highway specifications. Signs adjacent to areas used by aircraft shall meet the airfield general frangibility requirements as required by the Airport and subsequent approval by the Owner. Meeting airfield frangibility requirements may require modification to size and height guidance in the MUTCD.

16. HAZARD MARKING AND LIGHTING

a. Purpose

Hazard marking and lighting prevents pilots from entering areas closed to aircraft and prevents construction personnel from entering areas open to aircraft. To that end, comprehensible warning indicators for any area affected by construction that is normally accessible to aircraft, personnel, or vehicles shall be installed and maintained by the

Contractor for the duration of construction operations.

b. Barricades

All airside construction sites shall be barricaded and lighted to delineate the work areas.

Projects on aircraft operating areas in which aircraft or unapproved vehicles may not enter shall be defined by approved barricades. The three approved styles of barricades for airfield construction are Low Profile Portable Plastic Barricades, Flat Panel Barricades, and Candle

Stick Barricades. Details and spacing requirements of each type of barricade are shown in the Construction Phasing Drawings. Low Profile Portable Plastic Barricades used on the airfield shall be placed end-to-end and connected together to form a continuous barrier around the work areas. Candle Stick Barricades, where used, shall be linked together through the use of a flag rope having alternating orange and white flags that are securely attached to prevent them from becoming a FOD hazard. Provisions shall be made for ARFF access if necessary.

c. Red Hazard Marking Lights

Barricades shall have solar/battery powered red flashing lights that meet the luminance requirements of the State Highway Department to identify hazards at night and in low visibility. Lights must be mounted on barricades and spaced at no more than 10 ft. Lights must be operated between sunset and sunrise and during periods of low visibility whenever the Airport is open for operations. They may be operated by photocell, but this may require that the Contractor turn them on manually during periods of low visibility during daytime hours.

d. Supplemental Signs

Construction areas adjacent to active portions of the Aircraft Movement Area (AMA) shall have vehicle warning signs that warn Contractor personnel not to enter the restricted area.

The signs shall read “Active Taxiway Do Not Enter” or “Active Runway Do Not Enter” and will meet the specifications provided in the Construction Phasing Drawings.

e. Air Operations Area – General

Barricades are not permitted in any active runway or taxiway safety area. Airside construction sites shall be barricaded and lighted to delineate the work areas. Projects on aircraft operating areas in which an aircraft or unapproved vehicles may not enter shall be defined by approved barricades with red flashing hazard marking lights and flags. The barricades shall be weighted to prevent displacement from jet blast or surface winds.

Approved barricades shall be used to close each entrance to the construction area in order to prohibit aircraft and unapproved vehicles from entering the area. For specifications on approved barricades refer to the Construction Phasing Drawings.

Closures greater than 10 hours shall use the approved Low Profile Portable Plastic

Barricades marked with diagonal, alternating orange and white reflective stripes, and signs to separate paved construction/maintenance areas from the movement area. Barricades shall be supplemented with alternating orange and white 20” by 20” square flags that are securely fastened to eliminate FOD. Barricades must be of low mass; easily collapsible upon contact with an aircraft or any of its components; and weighted or sturdily attached to the surface to prevent displacement from prop wash, jet blast, wing vortex, or other surface wind currents. If barricades are affixed to the surface, they must be frangible at grade level or as low as possible, but not to exceed 3 in (7.6 cm) above the ground.

Closures less than 10 hours shall use barricades approved by SLCDA. The Contractor may use the approved Flat Panel Barricades with red flashing hazard marking lights spaced no more than 10’ apart on paved surfaces to define the boundaries of the construction area closed to aircraft. Candle Stick barricades are not approved to delineate construction boundaries on paved surfaces.

f. Air Operations Area – Runway/Taxiway Intersections

Approved highly reflective barricades with lights shall be used to close taxiways leading to closed runways when hazards or unusable pavement exist on the runways.

Runway/Taxiway intersection closures greater than 30 minutes shall be barricaded with approved barricades. Approved barricades shall be used at each entrance to prohibit aircraft and unapproved vehicles from entering the closed area. The use of approved Flat

Panel Barricades is appropriate for short duration closures.

g. Air Operations Area – Other

The unpaved areas of the construction boundaries shall be marked with approved candle stick barricades or flat panel barricades connected with a flag rope with alternating orange and white flags. A setback line shall be maintained in an approved manner at all times if the construction site is within the TOFA of an active taxiway.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .