RADAR PROCEDURES Sample Clauses

RADAR PROCEDURES. Unless otherwise coordinated, the following procedures shall apply:
View SourceView Similar (4)
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.
View Source
RADAR PROCEDURES a. Rochester Airport Traffic Control tower shall: (1) Assign the ▇▇▇▇▇ 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 ▇▇▇▇▇/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.
View Source
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.
View Source
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:
View Source
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:
View Source
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.
View Source
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, ▇▇▇▇▇, 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 ▇▇▇ ▇▇▇▇/▇▇▇▇ 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. ▇. ▇▇▇▇▇▇▇ 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).
View Source

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 bill 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 bill 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 bill 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 OP. 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: ▇▇▇▇▇ ▇▇▇▇▇▇▇, FFMO ▇▇▇▇ ▇▇▇▇▇▇▇▇▇ ▇▇▇▇▇ ▇▇▇▇▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇ Telephone: ▇▇▇-▇▇▇-▇▇▇▇ FAX: ▇▇▇-▇▇▇-▇▇▇▇ Email: ▇▇▇▇▇▇▇▇@▇▇.▇▇▇.▇▇ ▇▇▇ ▇▇▇▇▇▇▇▇, FIRE CHIEF ▇.▇. ▇▇▇ ▇▇▇ ▇▇▇▇▇▇▇, ▇▇ ▇▇▇▇▇ Telephone: ▇▇▇-▇▇▇-▇▇▇▇ FAX: ▇▇▇-▇▇▇-▇▇▇▇ Email: ▇▇▇▇▇▇▇▇▇▇▇.▇▇▇▇@▇▇▇▇▇▇▇▇.▇▇▇ All bills will have a payment due date 30 days upon receipt. Contested ▇▇▇▇▇▇▇▇: Written notice that a bill 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 ▇▇▇▇▇▇▇▇. Billing requirements and rates are documented in the attached OP.

  • Formal Procedures 1. Upon presentation to the academic ▇▇▇▇ of a petition signed by one–third (1/3) of the full–time members of the department/work area, excluding the department chair, stating specific reasons for recalling the department chair, the academic ▇▇▇▇ shall promptly give fourteen (14) calendar days' written notice to all department/work area members setting forth the time, date and place of a meeting to consider the recall petition and to vote on either a motion that the department/work area chair continue in office or a motion to recommend to the President of the College that the President declares a vacancy to exist in the department/work area. The department chairperson/work area may be present at this meeting. 2. The academic ▇▇▇▇ and an impartial person from the faculty at large, who shall be elected by members of the department/work area, shall conduct the recall meeting, and if the academic ▇▇▇▇ and the members of the department/work area shall have so decided, shall conduct successor meetings for the same purpose. The academic ▇▇▇▇ and such impartial person from the faculty at large shall record any subsequent vote(s) taken within the department/work area on this matter. 3. A vote by secret ballot of the majority of all full–time department/work area members shall be required to recommend to the President of the College or the President’s designee that the President declares a vacancy to exist in the department chair position. If a majority of the department/work area members so vote, the results of the balloting with reasons shall be forwarded to the President of the College or the President’s designee. The President of the College shall determine the recall or continuance within ten (10) calendar days and so notify the department/work area with reasons. The President's decision shall be final.