SOM Flashcards
IFR aircraft FL 230 and below, not landing within the YEZ terminal area…
IFR aircraft FL 230 and below, not landing within the YEZ terminal area, shall be routed so as to use the appropriate inbound and outbound gates.
AIRCRAFT TRANSITING TERMINAL AIRSPACE
- EE and WW will route aircraft FL230 and below, transiting Martin Terminal airspace via entry fixes KYLER, WHITE, and BLACK.
- Martin Terminal will route aircraft FL230 and below transiting Martin Terminal airspace via exit fixes ANGEL, BANJO, WEST GATE, and DEXTER.
- Transiting aircraft entering Martin Terminal Airspace will be handed off to Martin Terminal Departures Sector (DD).
SOM 212 Traffic Flow between Terminal and WW/EE Sectors
A. Terminal shall issue climb to FL230 or flight planned altitude (if lower)
1. Vertical separation in lieu of surveillance may be used as required.
2. For aircraft that are stopped below FL230 Terminal shall use the REMARK field to indicate the cleared altitude of the aircraft.
B. Aircraft landing CYEZ shall be issued descent to 10 000 unless vertical separation is being applied between non-similar type aircraft.
1. Verbal coordination is required for all aircraft not issued descent to 10 000 ft
C. Aircraft landing at CYEZ shall not be cleared below 10 000 ft.
D. Terminal shall route aircraft direct the appropriate exit fix:
1. BANJO
2. DEXTR
3. ANGEL
4. Aircraft exiting the West Gate will be cleared on a track direct or assigned a heading between YBB and YWW
E. WW/EE shall ensure aircraft are established on the appropriate arrival at the following fixes prior to entering Terminal’s airspace:
1. WHITE
2. KYLER
3. BLACK
Agreement between Martin ACC and MSP Air Route Control Center
Minneapolis must ensure aircraft landing Martin are routed via…
A.4 Minneapolis must ensure aircraft landing Martin are routed via HML BLACK BLACK Arrival and issue descent to 10000 feet. Minneapolis will hand-off aircraft landing Martin to East Low and point-out to Martin High as required. Minneapolis will provide 10 mile spacing between similar type aircraft arriving Martin Terminal Airspace.
A.5 For all flights prior approval is required for all flight plan amendments if the aircraft is less than 30 NM by route of flight from the common control boundary.
A.6 WW/EE must ensure that southbound aircraft departing Martin/Sandy airport will not be cleared above FL280 prior to the handoff.
Martin Terminal Star Restrictions
KYLER Runway 27 is active:
Kyler at 10,000 feet and 220 KIAS (Props and Jets single stream)
KYLER - Runway 9 is active:
JETS –> KYLER 10,000 - 16,000 feet and slowing to 250 KIAS
PROPS –> KYLER 10,000 feet
2 streams (stacking props and jets)
For White, the KYLER runway 9 restrictions apply, pistons 9,000 feet (or lower if flight planned lower). Coordinated altitude box required for props going in at 9,000 or below
For Black, the KYLER runway 9 restrictions apply
SOM 204 – Transfer of Control
Within Martin ACC, transfer of control for climb, descent, speed changes and turns shall be coincident with the handoff. Verbal coordination of control transfer is required prior to the handoff when there is conflicting traffic.
SOM 202 – Spacing
A. Martin Enroute Specialty sectors shall provide adjacent sectors 10NM constant or increasing spacing between similar-type aircraft landing within the YEZ Terminal Area.
B. Vertical separation in lieu of the 10-mile spacing may be used for non-similar type aircraft.
C. Spacing shall be accomplished in reference to the following fixes:
a. MARTIN HIGH sector
i. TROUT ii. BRADY
b. WEST LOW / EAST LOW sectors
i. KYLER ii. WHITE iii. BLACK
A. ARRIVALS
(West low from HH)
a. HH shall route aircraft landing CYEZ between YAR and YBB direct BRADY or established on J515.
B. DEPARTURES
a. WW and EE shall route departing aircraft on the FPR or direct the first fix past the out bound gate.
d. WW shall route aircraft that depart CYEZ via ANGEL on a route ANGEL direct YQV or north.
e. WW shall route aircraft that depart CYEZ via the SW gate direct YBB or YWW or between.
C. Aircraft landing CJE3
- 10-mile spacing is required between similar type aircraft.
- Aircraft may be descended to FL290 prior to accomplishing the hand off.
- Aircraft shall be handed off to Mountain sector.
- It is Mountain sector’s responsibility to coordinate with West Low if further descent will infringe on West Low’s airspace.
V327
Northbound = Westbound, Even altitudes
Southbound = Eastbound, Odd altitudes
We do not switch altitude for aircraft between dusty and lumpy when the track changes direction.
(Note we still may get aircraft that are at wrong way altitudes according to the rule above that we may have to fix altitutde)
Arrangement between Martin Area Control Centre and Sandy Control Tower - C. DESCRIPTION OF AIRSPACE
( sandy control zone)
C.1 The Sandy control zone is the airspace to 5700 feet (5000 feet AAE) within the area bounded by a circle of 5 miles radius centered on: N49°30’00.00” W099°45’00.00”
boundary estimate tip for procedural airspace
while the aircraft is still within radar coverage, RBL them to the boundry to get a boundary estaimate. Put in the notes section of the FDE “BNDRY @TIME” you can add a minute or 2 to the estimate to air on the side of caution if you’d like
if you miss this, then you have to wait for their dusty report and then extrapolate a boundary estimate using the true airspeed
we can pull the strip BOUNDARY ESTIMATE PLUS 10 MINUTES
block 4 aircraft types
C208 - Caravan, its a prop, but we treat it as a piston
PA31 - Navajo - Piston
BE9L - King Air - turboprop
DH8D - Q400 dash 8, turboprop
Arrangement between Martin Area Control Centre and Sandy Control Tower
B. RESPONSIBILITIES
B.1 SANDY CONTROL TOWER
B.1.1 Provide Airport Control Service within the Sandy Class D airspace to VFR, Special VFR, and IFR Aircraft for which the responsibility for control has been transferred to the Tower.
B.1.2 Assume control of arriving IFR aircraft in accordance with MATS and the operating procedures detailed in this arrangement.
B.1.3 Authorize Special VFR (SVFR) flights within the Sandy Control Zone and ensure that SVFR flights shall remain clear of the flight paths of IFR flights operating in the control zone.
B.1.4 Update OIDS system as follows:
- Current ATIS code
- - Active runway
B.1.5 Inform Martin ACC as soon as practicable of a No Transponder IFR departure so they may affect the appropriate coordination.
B.1.6 Inform Martin ACC when the Tower Radar Display, OIDS system, or EXCDS are unserviceable.
B.1.7 Advise Martin ACC of any aircraft without a functioning transponder operating within the Sandy Control Zone if a possibility of conflict exists with IFR traffic.
