Aircraft Flyover Details Sample Clauses

Aircraft Flyover Details. ACTs will ensure the following information is used for planning events, briefing flight crews, and included in the Smart Pack.
AutoNDA by SimpleDocs

Related to Aircraft Flyover Details

  • AIRCRAFT CONFIGURATION The guarantees defined below (the “Guarantees”) are applicable to the A319-100 Aircraft as described in the Standard Specification Ref. J 000 01000 Issue 6 dated 1st March 2007 equipped with:

  • Aircraft Basic Price The Aircraft Basic Price is listed in Table 1 and is subject to escalation in accordance with the terms of this Purchase Agreement.

  • Aircraft Maintenance Operator shall, at its own expense, cause the Aircraft to be inspected, maintained, serviced, repaired, overhauled, and tested in accordance with FAR Part 91 so that the Aircraft will remain in good operating condition and in a condition consistent with its airworthiness certification and shall take such requirements into account in scheduling the Aircraft hereunder, including but not limited compliance with applicable airworthiness directives and service bulletins. Performance of maintenance, preventive maintenance or inspection shall not be delayed or postponed for the purpose of scheduling the Aircraft unless such maintenance or inspection can safely be conducted at a later time in compliance with applicable laws, regulations and requirements, and such delay or postponement is consistent with the sound discretion of the pilot-in-command. In the event that any non-standard maintenance is required during the term and will interfere with User’s requested or scheduled flights, Operator, or Operator’s pilot-in-command, shall notify User of the maintenance required, the effect on the ability to comply with User’s requested or scheduled flights and the manner in which the parties will proceed with the performance of such maintenance and conduct of such flight(s). In no event shall Operator be liable to User or any other person for loss, injury or damage occasioned by the delay or failure to furnish the Aircraft under this Agreement, whether or not maintenance-related.

  • Aircraft This peril includes self-propelled missiles and spacecraft.

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • Operational Support Systems (OSS The terms, conditions and rates for OSS are as set forth in Section 2.13 of this Attachment.

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

  • DELIVERY, STORAGE, AND HANDLING The Contractor shall be responsible to inspect all components on delivery to ensure that no damage occurred during shipping or handling for furnish and installation projects. For equipment only purchases, the ordering entity shall be responsible to inspect all components on delivery. Materials must be stored in original undamaged packaging in such a manner to ensure proper ventilation and drainage, and to protect against damage, weather, vandalism, and theft until ready for installation.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.

  • BOEING PROPRIETARY Attachment B to Letter Agreement No. 6-1162- SKC-975

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!