ICAO Justification Material Sample Clauses

ICAO Justification Material. Planning to accommodate future aircraft developments ADM Pt1 P6 - Impossible to confirm existence of the “1981 study” - NASA Xxxx study on 747 RTO not conclusive No specific justification material available on rwy shoulders to AACG AACG Agreement A minimum central 45m of pavement of full load bearing strength shall be provided. * - Compliance with the minimum 75m ICAO Code F runway + shoulders width - Minimum of 2x15m wide shoulders on existing 45m wide rwys: * . At least 2x7.5m wide “inner” portion of rwy shoulders (definitions according to ICAO documents – see above) . Additional “outer” portion of rwy shoulders prepared for jet blast protection, engine ingestion protection, and for supporting ground vehicles. - Minimum of 2x7.5m wide “outer” portion of rwy shoulders on existing 60m wide rwys - Depending on local conditions, decision on the composition and thickness of rwy shoulders by each national authority and/or airport operator. - If relevant to local conditions, snow removal and ice control as recommended by ICAO (Doc 9137-AN/898)
Sample 1Sample 2
AutoNDA by SimpleDocs
ICAO Justification Material. Twy width = 2 x clearance distance from wheel to pavement edge + max wheel track Code E: 23m = 2x4.5m+14m Code F: 25m = 2x4.5m+16m ADM Pt2 p1.2.7+ table 1-1 - Origin of the 4.5m clearance distance unknown to AACG - Origin of the 4.5m clearance distance unknown to AACG - No specific justification material available on taxiway shoulder width to AACG AACG Agreement - Minimum of 23m - Wheel-to-edge minimum clearance of 4.5m for code E and F aircraft - On straight portions, Code F compliant: 60m wide strip to be protected against shoulder erosion and engine ingestion (paved or natural surface) - Depending on local conditions, decision on: . the width for curved portions, . the composition and thickness for straight and curved portions by each national authority and/or airport operator AACG Justification Material - Twy deviation statistics on straight section, based on existing and on going studies - A380 Landing gear wheel span and cockpit visibility - No specific justification needed (same rules as more critical aircraft such as A340-600 and 777- 300ER) - A380 Engine position - A380 Jet blast velocity & temperature contours at break- away thrust
Sample 1Sample 2
ICAO Justification Material. Separation = ½ wing span + ½ strip width: Code E:182.5m = ½x65m+½x300m Code F:190m = ½x80m+½x300m for instrument rwy ADM Pt2 p1.2.19+ table 1-5 - Origin of the 300m rwy strip width unknown to AACG - No justification material in ICAO official publications - Justifications in OCP meetings materials: 155m (Code F) = 120m (Code E) + 20m (wingspan increase from initial Code E 60m to Code F 80m) + 15m (rwy width increase from code E 45m to code F 60m) - 107.5m based on Code F OFZ definition and on an aircraft with 24m tail height, 62.2m distance nose-highest tail part, 10m nose height, 45° or more holding Collision risk: - For non-instrument runways, ICAO SARPs to be followed (115m for code F). - For instrument runways, no generic operational agreement. * 190m regarded as conservative ILS effects: - Need for specific runway studies to evaluate ILS interference risks in all cases. Collision risk: AACG Pending on-going studies - For take off, non-instrument & Agreement (OCP), possibility of reduced non-precision approach Code F OFZ width (155m) for runways, minimum ICAO A380 operations on 45m wide SARPs to be followed (75m). In runways. * some complex airport layouts (parallel runways, intermediate taxiways used to cross runways,...), rwy holding positions may be specifically studied when rwys are used by A380. - Possibility of reduced Code F minimum holding point distances for collision risk reasons (OFZ). * ILS effects: - Need for specific runway studies to evaluate ILS interference risks in all cases AACG Justification Material Collision risk: - Common Accident/Incident database (ICAO, NTSB, Airbus, Boeing, Airlines, Press) - NCAA/AEA report for code F rwy strip width: “90m+aircraft half span” (only relevant to collision risk, not to ILS interference) ILS effects: - ADP study - Park Air Systems study (based on an A380 vertical tail in metal) - ICAO OCP - OFZ study, preliminary 747 results in autoland mode - ADP investigation on OFZ for A380 operations on 45m wide rwy - St Petersburg formula for A380 ops on 45m wide rwys - NCAA/AEA report Collision risk: - Investigation by ADP on OFZ for A380 ops on 45m wide rwy ILS effects: - ADP study - Park Air Systems study (based on an A380 vertical tail in metal) * See §I.3.b)
Sample 1Sample 2
ICAO Justification Material. Information and formula used to elaborate ICAO SARPs and ADM (applicable to Code Letter F aircraft as defined in Annex 14 Chapter 1).
Sample 1

Related to ICAO Justification Material

  • Handling Sensitive Personal Information and Breach Notification A. As part of its contract with HHSC Contractor may receive or create sensitive personal information, as section 521.002 of the Business and Commerce Code defines that phrase. Contractor must use appropriate safeguards to protect this sensitive personal information. These safeguards must include maintaining the sensitive personal information in a form that is unusable, unreadable, or indecipherable to unauthorized persons. Contractor may consult the “Guidance to Render Unsecured Protected Health Information Unusable, Unreadable, or Indecipherable to Unauthorized Individuals” issued by the U.S. Department of Health and Human Services to determine ways to meet this standard.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Interconnection Customer's data is materially different from what was originally provided to the Participating TO and the CAISO for the Interconnection Studies, then the Participating TO and the CAISO will conduct appropriate studies pursuant to the LGIP to determine the impact on the Participating TO’s Transmission System and affected portions of the CAISO Controlled Grid based on the actual data submitted pursuant to this Article 24.3. The Interconnection Customer shall not begin Trial Operation until such studies are completed and all other requirements of this LGIA are satisfied.

  • Third Party Proprietary Data The Disclosing Party's Third Party Proprietary Data, if any, will be identified in a separate technical document.

  • - CLEC INFORMATION CLEC agrees to work with Qwest in good faith to promptly complete or update, as applicable, Qwest’s “New Customer Questionnaire” to the extent that CLEC has not already done so, and CLEC shall hold Qwest harmless for any damages to or claims from CLEC caused by CLEC’s failure to promptly complete or update the questionnaire.

  • Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.

  • Confidentiality of Contractor Information The Contractor acknowledges and agrees that this Contract and any and all Contractor information obtained by the State in connection with this Contract are subject to the State of Vermont Access to Public Records Act, 1 V.S.A. § 315 et seq. The State will not disclose information for which a reasonable claim of exemption can be made pursuant to 1 V.S.A. § 317(c), including, but not limited to, trade secrets, proprietary information or financial information, including any formulae, plan, pattern, process, tool, mechanism, compound, procedure, production data, or compilation of information which is not patented, which is known only to the Contractor, and which gives the Contractor an opportunity to obtain business advantage over competitors who do not know it or use it. The State shall immediately notify Contractor of any request made under the Access to Public Records Act, or any request or demand by any court, governmental agency or other person asserting a demand or request for Contractor information. Contractor may, in its discretion, seek an appropriate protective order, or otherwise defend any right it may have to maintain the confidentiality of such information under applicable State law within three business days of the State’s receipt of any such request. Contractor agrees that it will not make any claim against the State if the State makes available to the public any information in accordance with the Access to Public Records Act or in response to a binding order from a court or governmental body or agency compelling its production. Contractor shall indemnify the State for any costs or expenses incurred by the State, including, but not limited to, attorneys’ fees awarded in accordance with 1 V.S.A. § 320, in connection with any action brought in connection with Contractor’s attempts to prevent or unreasonably delay public disclosure of Contractor’s information if a final decision of a court of competent jurisdiction determines that the State improperly withheld such information and that the improper withholding was based on Contractor’s attempts to prevent public disclosure of Contractor’s information. The State agrees that (a) it will use the Contractor information only as may be necessary in the course of performing duties, receiving services or exercising rights under this Contract; (b) it will provide at a minimum the same care to avoid disclosure or unauthorized use of Contractor information as it provides to protect its own similar confidential and proprietary information; (c) except as required by the Access to Records Act, it will not disclose such information orally or in writing to any third party unless that third party is subject to a written confidentiality agreement that contains restrictions and safeguards at least as restrictive as those contained in this Contract; (d) it will take all reasonable precautions to protect the Contractor’s information; and (e) it will not otherwise appropriate such information to its own use or to the use of any other person or entity. Contractor may affix an appropriate legend to Contractor information that is provided under this Contract to reflect the Contractor’s determination that any such information is a trade secret, proprietary information or financial information at time of delivery or disclosure.

Time is Money Join Law Insider Premium to draft better contracts faster.