RADAR PROCEDURES Sample Clauses

RADAR PROCEDURES. Unless otherwise coordinated, the following procedures shall apply:
AutoNDA by SimpleDocs
RADAR PROCEDURES. Unless otherwise coordinated, the following procedures shall apply: a. R90 shall notify ZMP of the following: 1. Runway in Use b. Arrival Procedures 1. All Arrivals a. R90 shall have control for code changes. b. R90 may level all R90 arrivals at ZMP assigned altitude without coordination. ZMP is responsible for necessary coordination with other ZMP sectors, provided the aircraft is left on course. c. R90 Sector accepting the handoff shall be responsible for internal sector pointouts. 2. STAR Arrivals a. From 0730 to 2300 LCL all aircraft at or above 16,000 feet landing OMA or OFF shall be assigned a STAR. b. STAR arrivals shall be level at or descending to 16,000 feet (or 17,000 feet stacked on the STARs). c. R90 has control for descent on STAR arrivals 10NM from the R90/ZMP boundary. R90 has control for turns up to 30 degrees at lateral boundaries R90’s airspace or the following fixes: BECOM, XXXXX, LANTK, and MARWI provided the aircraft will not enter another controller’s airspace. d. ZMP assigned speeds on STAR inbounds do not need to be coordinated with R90. 3. All other Arrivals (satellite airports, as well as OMA & OFF during non-star periods.) a. All other R90 arrivals shall be direct destination or a destination approach fix. Aircraft descending over X00 Xxxx/Xxxx shall be at or descending to 16,000 feet or at or below 13,000 feet in level flight, and aircraft over R90 LNK shall be at or descending to 11,000 feet or in level flight below 11,000 feet. Acceptance of the handoff of an aircraft in level flight by R90 constitutes approval of inappropriate altitude for direction of flight. b. Turbojet aircraft landing OMA and OFF below 16,000 feet require an apreq. c. R90 has control for descent and turns up to 30 degrees within 10NM of the lateral boundaries of R90’s airspace at or below 15,000 feet provided the aircraft will not enter another controller’s airspace. d. During non-STAR periods, R90 has control of all R90 arrivals for descent and turns up to 30 degrees within 10 NM of the lateral boundary. x. Xxxxxxx sector arrivals from the east above 15,000 feet shall be handed off to Omaha Radar West Sector. ZMP 27 is responsible for ZMP sector 26 (i.e. point out or flash through automated information transfer).
RADAR PROCEDURES. Unless otherwise coordinated, the following procedures shall apply: a. Arrivals. 1) Arrivals shall be descending to or level at 11,000 feet MSL 2) IFR transfer of control for turns of 30 degrees either side of the aircraft’s assigned routing and descent occurs when the following conditions are met: a) After receipt of a radar handoff and completion of a frequency change; and, b) The course and/or altitude change does not affect another approach control without proper coordination; and, c) The alteration of course or altitude shall not be made within the lateral limits of Center Sectors 26 and 27, as depicted on Attachment "A". 3) When automated handoffs are used, the acceptance of a handoff by Approach Control of an aircraft with Mode C readout in level flight below 10,000 feet MSL constitutes altitude approval. Aircraft without Mode C shall be verbally coordinated.
RADAR PROCEDURES a. Radar handoff procedures between Naha ACC and Taipei ACC should be applied for aircraft at or above FL250 on Airway A1, R583, R595, G581 and RNAV route M750. BULAN, BORDO, SEDKU, IGURU and MOLKA shall be the common reference points. b. The ACC having a scheduled outage or experiencing an unexpected outage of ARSR shall inform the other ACC of the names of common reference points where radar handoff will be suspended as soon as practicable. c. Radar handoff procedures shall not exempt section 5 of this agreement. d. Minimum radar separation between aircraft at the same altitude on the same or converging route under radar handoff shall be 25NM provided that; (1) Either one or both aircraft terminate in Fukuoka or Taipei FIR. (2) Both aircraft proceed beyond Fukuoka FIR, and diverge from each other before entering the Pacific Ocean airspace. (3) Both west-bound aircraft diverge from each other in the Taipei FIR.
RADAR PROCEDURES a. Rochester Airport Traffic Control tower shall: (1) Assign the XXXXX STAR to all capable turbojet aircraft landing MSP Airport. Assign the KASPR STAR to all other turbojet aircraft landing MSP Airport. RST must verbally coordinate all turbojet aircraft on the KASPR arrival. (2) Assign the KASPR STAR to all turboprop aircraft capable of 200 knots or greater indicated airspeed (IAS) landing MSP Airport. (3) Assign the following altitudes (and frequencies) to XXXXX/KASPR STAR arrivals: (a) Landing Runways 12L/R – at 9,000 ft. (Feeder) Jets/Props (b) Landing Runways 30L/R – at 7,000 ft. (Satellite) Props (c) Landing Runway 30L/R – At 9,000 ft. (Feeder). Jets (d) Landing Runway 30L/R and when departing 17 – at 9,000 ft. (Feeder) Jets/Props (e) Landing Runway 35 – at 7,000 feet. (35 Arrival) Jets/Props (f) Landing Runway 4 – at 8,000 feet. (Feeder) All aircraft capable of 200 kts> (g) Landing Runway 17 or 22 – at 9,000 feet (Feeder) All aircraft capable of 200 kts> (h) Any other Runway configurations as coordinated.
RADAR PROCEDURES. 6.1. ZSU and MDCS must provide a minimum of 10nm separation, constant or increasing, on aircraft at the same level entering the ZSU and MDCS airspace. 6.2. A handoff must be effected on all aircraft at least 10nm prior to the TCP of common boundary. 6.3. ZSU and MDCS must handoff aircrafts to the appropriate controller according to APPENDIX 2. 6.4. In the event that a handoff cannot be completed, the transferring facility must instruct the aircraft being transferred to hold within the transferring facility. 6.5. The receiving facility must not change an aircraft current flight plan or beacon code until the aircraft has reached or has passed the TCP 7.1. Allocation of flight levels will be as follows:
RADAR PROCEDURES. Unless otherwise coordinated, the following procedures shall apply: a. Radar handoffs between facilities are mandatory as depicted on Attachment “A.” b. Arrivals/Over-flights: (1) The clearance limit for arrivals shall be the destination airport. (2) Arrivals shall be descending to or level at 8,000 feet MSL. (3) When automated handoffs are in use: (a) Acceptance of a handoff by BIS of an aircraft with Mode C readout in level flight at or below 15,000 feet MSL constitutes altitude approval on over-flight traffic and arrivals 7,000 feet MSL and below. (4) After receiving a handoff from ZMP, BIS shall have control for descent and/or control to alter the heading/route of an aircraft. The maximum turn shall not exceed 30 degrees either side of the aircraft’s ground track.
AutoNDA by SimpleDocs
RADAR PROCEDURES. This Letter of Agreement is applicable to Chicago ARTCC and Milwaukee ATCT. a.) Milwaukee Metropolitan Arrivals 1.) Clearance limit is the airport of intended landing unless MKE ATCT advises that holding will be necessary. 2.) ZAU must route arrivals to cross such entry fixes at the altitude limitations and established on headings, or via route then direct destination, as show below:

Related to RADAR PROCEDURES

  • Other Procedures To the extent not expressly provided for herein, each Discounted Term Loan Prepayment shall be consummated pursuant to procedures consistent with the provisions in this Subsection 4.4(l), established by the Administrative Agent acting in its reasonable discretion and as reasonably agreed by the Borrower.

  • New Procedures New procedures as to who shall provide certain of these services in Section 1 may be established in writing from time to time by agreement between the Fund and the Transfer Agent. The Transfer Agent may at times perform only a portion of these services and the Fund or its agent may perform these services on the Fund's behalf;

  • Transfer Procedures 1. The transfers referred to in Article 4, 5, 6 and 7 shall be effected without undue delay and, at all events, within six months after all fiscal obligations have been met and shall be made in a convertible currency. All the transfers shall be made at the prevailing exchange rate applicable on the date on which the investor applies for the related transfer, with the exception of the provisions under point 3 of Article 5 concerning the exchange rate applicable in case of nationalization or expropriation. 2. The fiscal obligations under the previous paragraph are deemed to be complied with when the investor has fulfilled the proceedings provided for by the law of the Contracting Party on the territory of which the investment has been carried out.

  • Billing Procedures The Supporting Party will xxxx the Protecting Party for actual costs incurred for Assistance by Hire. Reimbursements will be limited to the provisions of the Agreement and the applicable OP, regardless of whether or not it is authorized on the Resource Order or other documentation produced by the incident. Reimbursable costs may include transportation, salary, overtime, per diem and other approved expenses of Supporting agency personnel. Rates and conditions of use for the equipment and personnel are documented in the OP. Parties shall submit a xxxx within 90 days of the incident. Parties must use their own invoice form for billing under this Agreement to avoid any confusion with other services that may have been ordered under other agreements. Invoices must identify Supporting Party’s name, address, and Taxpayer Identification Number (Department only), fire name, order and request number, and xxxx number and amount. Invoice supporting documentation must include description of services performed, period of services performed, and any applicable cost share agreements. Supporting documentation will itemize details of billing, listing personnel, equipment, travel and per diem, aircraft, supplies and purchases as approved in the attached AOP. It will also include itemized deductions for maintenance and repair of equipment. Department invoices will include “Record of Activities” (FSLA-5) and U.S. Forest Service invoices will include transaction register. Invoices for services under this agreement must be sent to: Name: Xxxx Xxxxxx-Xxxxx, ECC Manager Address: 0000 Xxxxxxxxx Xxxxx Xxxx, Xxxxx, Xxx: Xxxxxxxxxx, XX 00000 Telephone: (000) 000-0000 FAX: (000) 000-0000 Email: xxxxxxxxxxxx@xx.xxx.xx Name: Spalding Community Service District Address: 000-000 Xxxxxxxx Xxx Xxxx, Xxxxx, Xxx: Xxxxxxxxxx, XX 00000 Telephone: (000) 000-0000 FAX: (000) 000-0000 Email: xxxxxxxxxxxxx@xxxxxxx.xxx All bills will have a payment due date 30 days upon receipt. Contested Xxxxxxxx: Written notice that a xxxx is contested will be mailed to the Party within 30 days of receipt of the invoice and will fully explain the contested items. Contested items should be resolved no later than 60 days following receipt of the written notice. Parties are responsible for facilitating resolution of contested xxxxxxxx. Billing requirements and rates are documented in the attached OP.

  • Formal Procedures Level 1: In the event the matter is not resolved informally, the grievance shall be submitted in writing to the appropriate supervisor within twenty (20) working days of the occurrence giving rise to the grievance. Such statement of grievance shall set forth the nature of the grievance, the facts on which it is based, the provisions of the Agreement allegedly violated, and the remedy requested. Any grievance not submitted in writing to Level 1 by the employee within twenty (20) working days of the occurrence shall be considered waived. Level 2: If appealed, the written grievance shall be presented by the grievant and/or the Union and discussed at an informal meeting within ten (10) working days of receipt of the written grievance, with the Superintendent of Schools or a designated representative. The Employer- designated representative shall give the Union the Employer’s answer in writing within ten (10) working days after the review meeting. A grievance not resolved in Level 2 may be appealed in writing to Level 3 by the Union within ten (10) working following the Employer-designated representative’s final answer in Level 2. Any grievance not appealed in writing to Level 3 by the Union within ten (10) working days shall be considered waived. Level 3: A grievance unresolved in Level 2 and appealed to Level 3 by the Union shall be submitted to arbitration subject to the provisions of PELRA. If a mutually-acceptable arbitrator cannot be agreed upon, the selection of an arbitrator shall be made from a list of five (5) names provided by the procedures of the Minnesota Bureau of Mediation Services, at the request of the Union. 3.1 The arbitrator shall have no right to amend, modify, or disregard the terms and conditions of this Agreement. The arbitrator shall consider and decide only the specific issue(s) submitted in writing by the Employer and the Union, and shall have no authority to make decisions on any other issue not so submitted. 3.2 The arbitrator shall be without power to make decisions contrary to, or inconsistent with the statutory rights and obligations of the parties, or modifying in any way the application of laws, rules or regulations having the force and effect of law. The arbitrator’s decision shall be submitted in writing, with copies to both parties, and to the Bureau of Mediation Services within thirty (30) days following the close of the hearing or the submission of briefs by the parties, whichever be later, unless the parties agree to an extension. The decision shall be binding on both the Employer and the Union and shall be based solely on the arbitrator’s interpretation or application of the terms of this Agreement and the facts of the grievance presented. 3.3 The fees and expenses for the arbitrator’s services and proceedings shall be borne equally by the Employer and the Union. All other expenses shall be borne by the party incurring the expense. If either party desires a verbatim record of the proceedings, it may cause such a record to be made, providing it pays for the record. If both parties desire a verbatim record of the proceedings, the cost shall be shared equally.

  • Hearing Procedures The hearing shall be held at the earliest convenient date, taking into consideration the established schedule of the Board or hearing officer and the availability of the CSEA representative, counsel and witnesses. The parties shall be notified of the time and place of the hearing after ensuring availability of all necessary parties. The employee shall be entitled to appear personally, produce evidence, and have CSEA representation. The employee shall be entitled to a public hearing if he/she demands it when the Board is hearing the appeal. 18.12.1 The complainant may also be represented by counsel. The procedure entitled "Administrative Adjudication" commencing with Government Code 11500 shall not apply to any such hearing before the Board or a hearing officer. Neither the Board nor a hearing officer shall be bound by rules of evidence used in California courts. Informality in any such hearing shall not invalidate any order or decision made or approved by the hearing officer or the Board. 18.12.2 All hearings shall be heard by a hearing officer (who shall be an attorney licensed in the State of California) except in those cases where the Board determines to hear the appeal itself. In any case in which the Board hears the appeal, the Board may use the services of its counsel or a hearing officer in ruling upon procedural questions, objections to evidence, and issues of law. However, the Board must employ separate counsel from the one presenting the case for the complainant. 18.12.3 If the appeal is heard by the Board, the Board shall affirm, modify or revoke the recommended personnel action. 18.12.4 If the appeal is heard by a hearing officer, he/she shall prepare a proposed decision in a form that may be adopted by the Board as the decision in the case. A copy of the proposed decision shall be received and filed by the Board and furnished to each party within ten days after the proposed decision is filed by the Board. After furnishing the proposed decision to each party, the Board may: 18.1.4.1 Adopt the proposed decision in its entirety. 18.1.4.2 Reduce the personnel action set forth in the proposed decision and adopt the balance of the proposed decision. 18.1.4.3 Reject a proposed reduction in personnel action, approve the disciplinary action sought by the complainant or any lesser penalty, and adopt the balance of the proposed decision. 18.1.4.4 Reject the proposed decision in its entirety. 18.12.5 If the Board rejects the proposed decision in its entirety, each party shall be notified of such action and the Board may decide the case upon the record including the transcript, with or without the taking of additional evidence, or may refer the case to the same or another hearing officer to take additional evidence. If the case is so assigned to a hearing officer, he/she shall prepare a proposed decision, as provided in item Section 18.12.4 above, upon the additional evidence and the transcript and other papers which are part of the record of the prior hearing. A copy of this proposed decision shall be furnished to each party within 10 days after the proposed decision is filed by the Board. 18.12.6 In arriving at a decision or a proposed decision on the propriety of the proposed disciplinary action, the Board or the hearing officer may consider the records of any prior disciplinary action proceedings against the employee in which a disciplinary action was ultimately sustained and any records that were contained in the employee's personnel files and introduced into evidence at the hearing.

  • Layoff Procedures Layoffs shall be administered pursuant as follows: An employee with permanent seniority in class shall have the right to displace an employee with less permanent seniority in the same class in any department. All bumping and displacement shall first occur within the department that affected the layoff in question prior to City-wide bumping.

  • Other Procurement Procedures National Competitive Bidding

  • Project Delivery Order Procedures The TIPS Member having approved and signed an interlocal agreement, or other TIPS Membership document, may make a request of the awarded vendor under this Agreement when the TIPS Member has services that need to be undertaken. Notification may occur via phone, the web, email, fax, or in person. Upon notification of a pending request, the awarded vendor shall make contact with the TIPS Member as soon as possible, but must make contact with the TIPS Member within two working days. Scheduling of projects (if applicable) may be accomplished when the TIPS Member issues a Purchase Order and/or an Agreement or Contract that will serve as “the notice to proceed” as agreed by the Vendor and the TIPS Member. The period for the delivery order will include the mobilization, materials purchase, installation and delivery, design, weather, and site cleanup and inspection. No additional claims may be made for delays as a result of these items. When the tasks have been completed the awarded vendor shall notify the client and have the TIPS Member or a designated representative of the TIPS Member inspect the work for acceptance under the scope and terms in the Purchase Order and/or Agreement or Contract. The TIPS Member will issue in writing any corrective actions that are required. Upon completion of these items, the TIPS Member will issue a completion notice and final payment will be issued per the contractual requirements of the project with the TIPS Member. Any Construction contract prepared by the TIPS Member’s Legal Counsel may alter the terms of this subsection, “Scheduling of Projects”.

  • Operational Procedures In order to minimize operational problems, it will be necessary for trade information to be supplied in a secure manner by the Subadviser to the Fund’s Service Providers, including: JPMorgan Chase Bank, National Association (the “Custodian”), Virtus Fund Services (the “Fund Administrator”) BNY Mellon Investment Servicing (US) Inc., (the “Sub-Accounting Agent”), any Prime Broker to the Series, and all other Counterparties/Brokers as required. The Subadviser must furnish the Fund’s service providers with required daily information as to executed trades in a format and time-frame agreed to by the Subadviser, Custodian, Fund Administrator, Sub-Accounting Agent and Prime Broker/Counterparties and designated persons of the Fund. Trade information sent to the Custodian, Fund Administrator, Sub-Accounting Agent and Prime Broker/Counterparties must include all necessary data within the required timeframes to allow such parties to perform their obligations to the Series. The Sub-Accounting Agent specifically requires a daily trade blotter with a summary of all trades, in addition to trade feeds, including, if no trades are executed, a report to that effect. Daily information as to executed trades for same-day settlement and future trades must be sent to the Sub-Accounting Agent no later than 4:30 p.m. (Eastern Time) on the day of the trade each day the Fund is open for business. All other executed trades must be delivered to the Sub-Accounting Agent on Trade Date plus 1 by Noon (Eastern Time) to ensure that they are part of the Series’ NAV calculation. (The Subadviser will be responsible for reimbursement to the Fund for any loss caused by the Subadviser’s failure to comply with the requirements of this Schedule A.) On fiscal quarter ends and calendar quarter ends, all trades must be delivered to the Sub-Accounting Agent by 4:30 p.m. (Eastern Time) for inclusion in the financial statements of the Series. The data to be sent to the Sub-Accounting Agent and/or Fund Administrator will be as agreed by the Subadviser, Fund Administrator, Sub-Accounting Agent and designated persons of the Fund and shall include (without limitation) the following:

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