100 - Sim Procedures Flashcards
Flight Plan Information Forwarding
Flight plan information will be forwarded to adjacent sectors via electronic methods. Changes to route and/or altitude are permitted until an aircraft is within 30 miles of the receiving sector’s boundary with the exception noted in article 206 (North West Procedural Corner)
North West Procedural Corner
For aircraft transiting the North West Procedural Corner, verbal coordination is required with the Mountain sector for all route, altitude, and flight plan changes when an aircraft is within 15 minutes flying time of the common boundary.
Flight Data Exchange
A.1 The primary method of flight data exchange must be via automated means.
A.2 The preferred format for automated flight data exchange must be in accordance with established protocols.
A.3 Should the automated means be unavailable, control estimates must be passed at least fifteen (15) minutes prior to the common boundary.
COMM/NAV Equipment Codes
INSERT one letter as follows:
N - if no COM/NAV approach aid equipment for the route to be flown is carried, or the equipment is unserviceable or S - if standard COM/NAV/approach aid equipment for the route to be flown is carried and serviceable and/or INSERT one or more of the following letters to indicate the serviceable COM/NAV/approach aid equipment and capabilities available:
D DME
G (GNSS)
R PBN approved
S Standard Equipment
W RVSM approved
X MNPS approved
Wake Turbulence Categories
/H – HEAVY, to indicate an aircraft type with a maximum certificated takeoff mass of 136,000 kg (300,000 lbs) or more.
/M – MEDIUM, to indicate an aircraft type with a maximum certificated takeoff mass of less than 136,000 kg (300,000 lbs) but more than 7,000 kg (15,500 lbs).
/L – LIGHT, to indicate an aircraft type with a maximum certificated takeoff mass of 7,000 kg (15,500 lbs) or less.
Cocking FDEs
Leave active FDEs in a “cocked” position if any one of the following conditions exists:
* Flight data and control information requiring relay to adjacent sectors/units or aircraft;
* Traffic estimates requiring integration into a sector;
* Estimates (pilot or controller) requiring verification; or
* Other potential situations requiring investigation or further action.
Note 1 The “cocking” of FDEs is an essential control technique used to remind controllers that some type of further action must be performed.
Note 2 The “cocking” of FDEs is optional when a mnemonic on the data tag performs the same function.
Removing FDEs
Do not remove an FDE from EXCDS until all appropriate action for that FDE has been executed and one of the following conditions has been met:
* For aircraft in ATS surveillance coverage:
◦ You observe that the aircraft has passed the fix posting and is clear of all possible conflicts at that posting.
◦ You have observed the aircraft leave your area of responsibility.
◦ All conflict resolution has been resolved and an electronic hand-off has been accomplished indicating successful transfer of control.
* A subsequent position report has been received or the aircraft has been observed passing a subsequent fix posting.
* The aircraft has been estimated to have passed the first fix outside your area of responsibility.
* The aircraft has been estimated to have crossed the control boundary by the appropriate longitudinal minimum.
* The unit accepting control has indicated that the aircraft is within its area of responsibility.
* Control of the aircraft has been transferred to the tower.
* The aircraft has cancelled or closed its IFR flight plan or itinerary and any subsequent traffic information has been issued.
Handoffs
A handoff shall be initiated not less than 10 NM or 2000 feet prior to the common boundary.
Surveillance Procedures - MSP Handoffs
Non-automated handoffs should normally be made in reference to southern most NAVAIDS/fixes.
Transfer of Control and Communications
Transfer of radio communication must be affected before an aircraft enters the receiving unit’s area of responsibility
Surveillance Procedures - Point Outs
Each unit must provide point-outs to the other on identified traffic operating within 2.5 NM of the common boundary.
Transfer of Control Within Martin ACC
Within Martin ACC, transfer of control for climb, descent, speed changes and turns shall be coincident with the hand-off. Verbal coordination of control transfer is required prior to the hand-off when there is conflicting traffic.
Transfer of Control - Martin and MSP
1 The transferring unit must ensure that potential conflicts with other aircraft have been resolved prior to transferring control.
2 The receiving unit will assume control of an aircraft only after the aircraft is within their area of responsibility or control has been released by the transferring unit
3 Transfer of radio communication must be affected before an aircraft enters the receiving unit’s area of responsibility.
Traffic Flow Between HH and WW/EE > Arrivals
- HH shall route aircraft landing CYEZ between YAR and YBB direct BRADY or established on J515.
- HH shall route aircraft landing CYEZ between YGS and PAKIT direct TROUT or established on J596.
Traffic Flow Between HH and WW/EE > Descent Handoffs
For aircraft landing within Martin Enroute, HH shall issue descent to FL290 and handoff to the appropriate sector.
