General Control Clause Samples
The General Control clause establishes the overarching authority or management rights of one party over certain aspects of the agreement or project. Typically, this clause outlines the scope of control, such as decision-making power, oversight responsibilities, or the ability to direct specific activities or processes. For example, it may grant a client the right to approve key deliverables or allow a contractor to manage subcontractors as needed. Its core function is to clarify which party has ultimate authority in specified areas, thereby reducing ambiguity and potential disputes over control during the course of the agreement.
General Control. Notwithstanding any other provision of this Agreement, the Insurers shall have ultimate control and responsibility of the functions delegated to AIM under this Agreement. The Insurers shall own and have custody of their general corporate accounts and records.
General Control. (1) It shall be unlawful for the owner of any animal to permit such animal to be out of his immediate control and restraint, or to be left unattended off the premises of the owner, or to be upon the property of another person without the permission of the owner or person in possession of such other property. For the purposes of this chapter, condominium and apartment common property shall not be considered to be the premises of the animal owner. Voice control may constitute control of an animal.
(2) Restraint of dogs and/or animals shall be maintained as follows:
a. When upon the premises of the owner, all animals shall be kept indoors or in a primary enclosure as defined by this chapter in such a manner as to contain the animal within the bounds of the owner's premises, or on a leash in the hands of a person that possesses the ability to restrain the animal.
b. When off the premises of the owner, all animals shall at a minimum be maintained on an appropriate chain, leash or tie not exceeding 12 feet in length, and in the hands of a person who possesses the ability to restrain the animal.
General Control. 5.1. Radar Handoffs
General Control. 5.1. The clearance limit shall be the destination airport unless otherwise coordinated.
5.2. The Transfer of Control Point (TCP) is considered to be the common airspace boundary. Controllers shall not issue changes of altitude or heading prior to crossing the common airspace boundary, unless previous coordination has taken place.
5.3. Interfacility coordination may be accomplished through private message, ATC messages, Discord, TeamSpeak or similar.
5.4. Controllers shall clear aircraft scratchpads prior to initiating a radar handoff. Controllers shall not use the scratchpad to forward route information-- this must be accomplished by updating the tag, flight plan route, or through manual coordination.
5.5. Kingston FIR and Havana FIR shall assign transponder codes allocated under the regional SSR allocation plan and use discrete SSR codes previously assigned to aircraft entering their FIR/CTA.
5.6. Unless otherwise coordinated on an individual basis, same-altitude aircraft on routes which are not laterally separated shall be delivered to the receiving facility at least 10 miles in trail, constant or increasing. If speeds must be assigned to achieve the in trail spacing, those speeds shall be stated in the aircraft tag.
5.7. Controllers of both facilities should initiate a radar handoff for aircraft which will enter the other’s airspace no later than 10 NM from the common airspace boundary. The transfer of control and communications shall be completed before the aircraft crosses the common airspace boundary.
5.7.1. Prior to initiating a radar handoff, the transferring controller shall ensure that any changes to the assigned routing occurring at or after the common boundary are reflected in the aircraft’s flight plan.
5.7.2. Unless otherwise coordinated, all aircraft shall be transferred between facilities routed over one of the fixes along the common boundary, as listed in Table 1. Aircraft shall be delivered at altitudes correct for direction as described by Table 1.
5.7.3. If aircraft are requesting a different altitude than the altitude currently assigned, then the assigned altitude shall be entered in the data tag as a temporary altitude, and the flight plan shall reflect the requested altitude.
5.8. Kingston FIR and Havana FIR shall issue routes and altitudes in accordance with Tables 2 and 3, issuing routings in the following order of preference: RNAV STAR, Conventional STAR, NAVAID routing.