Helicopter pilot Sample Clauses

The 'Helicopter pilot' clause defines the requirements and responsibilities related to the provision of a qualified helicopter pilot for services under the agreement. Typically, this clause specifies the necessary certifications, experience, and compliance with aviation regulations that the pilot must possess, and may outline who is responsible for hiring, paying, and insuring the pilot. Its core function is to ensure that any helicopter operations conducted under the contract are performed safely and legally by a competent professional, thereby mitigating risks associated with aviation activities.
Helicopter pilot. The eighteen (18) month time limit shall start when the member accepting the assignment is released to fly after completing commercial rating and five hundred (500) hours of flight time in a Division aircraft.
View SourceView Similar (17)
Helicopter pilot. Pilots are defined as those employees who are certified by the FAA as commercial helicopter pilots and are approved by the ASTREA lieutenant to act as “pilot in command” of a patrol or firefighting/rescue helicopter. The ASTREA lieutenant’s status as “pilot in command” must be approved by the Emergency Services Captain.
View SourceView Similar (4)
Helicopter pilot. Employees who are assigned to ASTREA on a full-time basis in the following classes: 005746 – Deputy Sheriff 005790 – Sheriff’s Sergeant 005780 – Sheriff’s Lieutenant Employees who are assigned to ASTREA on a full-time basis in the following classes: 005746 – Deputy Sheriff 005790 – Sheriff’s Sergeant 005780 – Sheriff’s Lieutenant
View SourceView Similar (4)
Helicopter pilot. This Section establishes additional compensation for a properly qualified employee who is assigned to operate a Sheriff's Department helicopter as its pilot.
View SourceView Similar (3)
Helicopter pilot. Technician: Shall be paid 104.45% of annual Technician pay
View Source
Helicopter pilot 
View SourceView Similar (4)

Related to Helicopter pilot

  • Mastectomy Services Inpatient

  • Preconstruction Services During the Design & Preconstruction Phase, the Design-Builder shall provide such design and preconstruction services as are necessary to properly advance the Project. Without limiting the generality of the foregoing, during the Preconstruction Phase, the Design-Builder shall: (i) work with its Architect and any design consultants to advance the design for the Project in consultation with Client Agency, the Department and its Program Manager; (ii) obtain bids from trade subcontractors to perform the work described in the Design Development Documents and provide bid tabulations to the Department; (iii) engage in any Value Engineering and scoping exercises necessary to return the cost of the work to the Project Budget; (iv) engage in preconstruction activities, including identifying any long-lead items; (v) develop a GMP proposal for the Project; and (vi) enter into a GMP for the Project. Throughout the Design & Preconstruction Phase, the Design-Builder shall schedule and attend regular meetings with the Department, the Program Manager and the Architect. A list of preconstruction deliverables is set forth in Exhibit C.

  • Ambulance Services Ground Ambulance Air and Water Ambulance

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, KDL, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, KDL shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, KDL shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that KDL anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between KDL and Verizon. KDL’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Verizon and KDL shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three