71
Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Embed Size (px)

Citation preview

Page 1: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Presented to: Minneapolis ATCT

Date: Summer 2009

Federal AviationAdministration

Minneapolis Runway Construction Procedures

Runway 12L/30R

Page 2: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

2MSP Runway Construction ProceduresSummer 2009

Starts 7/27 Ends by 8/17

4/22 Taxi only (except for 744 dept)

Occasional taxiway closure

Page 3: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

3MSP Runway Construction ProceduresSummer 2009

Page 4: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

4MSP Runway Construction ProceduresSummer 2009

Runway 12L/30R Construction

• August 18, 2009 - October 30, 2009• Center portion of the runway reconstructed• Taxiways at either end receive in pavement lighting

for Runway Status Lights (RWSL) program

*There will be some Taxiway P restrictions

Page 5: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

5MSP Runway Construction ProceduresSummer 2009

TWY P btwn 4/22 and C9 Restricted to B757 winglets and smaller Relocated Twy P

restricted to A320 and smaller

Twy P btwn C19 and P1 restricted to RJ85 and smaller (No E190s)

Twy Q adjacent to relocated Twy P restricted to B757 and smaller

TAXIWAY RESTRICTIONS

Gates C10-C11 CLSD

Page 6: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

6MSP Runway Construction ProceduresSummer 2009

C10/C11 CLSD

Page 7: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

7MSP Runway Construction ProceduresSummer 2009

Gates C10/11 CLSD

Page 8: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

8MSP Runway Construction ProceduresSummer 2009

Minimum Requirements to Conduct Rwy 22 LAHSO

FAA Order 7110.65S

Para. 3-10-4 Intersecting Rwy Separation

1. LAHSO (RY22) will only be conducted in VFR conditions (1,400/4).

2. Instruct the aircraft landing on Rwy 22 to hold short of K Taxiway for traffic landing Rwy 17.

3. Issue traffic information to both aircraft involved and obtain an acknowledgment from each. Request a read back of hold short instructions when they are not received from the pilot of the restricted aircraft.

4. Issue the measured distance from the landing threshold to the hold short point rounded down to the nearest 50-foot increment if requested by either aircraft (8,550 feet available).

5. Conditions of 2, 3, and 4 shall be met in sufficient time for the pilots to take other action (normally when landing clearance is issued).

Page 9: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

9MSP Runway Construction ProceduresSummer 2009

6. Land and Hold short runways must be free of any contamination, with no reports that braking action is less than good.

7. There is no tailwind for the landing aircraft restricted to hold short of the intersection. The wind may be described as “calm” when appropriate.

8. The aircraft required landing distances are listed in the current LAHSO directive.

9. LAHSO lighting in place and operational.

Page 10: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

10MSP Runway Construction ProceduresSummer 2009

MSP Facility Initiatives

10. 1,400/4 will be the weather minimum for this operation.

11. No heavy aircraft will be asked to hold short (Except B753)

12. Military aircraft will participate in a passive role only.

13. A“Local Assist” shall be in place for moderate or greater traffic during Runway 17/22 operations. As a general rule CCN main responsibility will be the “Assist” for LCN to coordinate with GC’s for runway crossings between the parallels (while monitoring LCN). CCS main responsibility will be the “Assist” for LCS to put 2 aircraft in position at one time on 12R.

Page 11: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

11MSP Runway Construction ProceduresSummer 2009

Some MSP LAHSO Non-Participants

Southwest

UPS

Air Canada

Fed Ex DC-10, MD-10, MD-11

Page 12: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

12MSP Runway Construction ProceduresSummer 2009

Converging Runway Display Aid (CRDA)

• Used on a 17-22 arrival configuration when LAHSO is not in use.

Page 13: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

13MSP Runway Construction ProceduresSummer 2009

Converging Runway Display Aid (CRDA) (South Flow No LAHSO)

• Runway 17-22 LOC / Visual operations– Runway 17 arrival spacing – 6 miles on touchdown.

• Not required when no traffic on Runway 22.

– Runway 22 arrival spacing – 6 miles on touchdown.

Page 14: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

14MSP Runway Construction ProceduresSummer 2009

LAHSO Operations – South Flow

• Runway 17-22 Visual Approach/LOC operations– Runway 17 arrival spacing – 4 miles on touchdown.

• Not required when no traffic on Runway 22.

– Runway 22 arrival spacing – 6 miles on touchdown.

Page 15: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

15MSP Runway Construction ProceduresSummer 2009

Runway Use System (RUS)

• RUS criteria for runway selection not mandatory during normal hours.

• RUS criteria shall be applied during midnight hours.

• Noise abatement shall be adhered to when traffic conditions permit.

Page 16: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

16MSP Runway Construction ProceduresSummer 2009

Runway Configurations

• All normal existing runway configurations are available, with the exception of Runway 12L/30R.

Page 17: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

17MSP Runway Construction ProceduresSummer 2009

All Runway Configurations

Weather Landing Departing

1400/4 or greater 17, 22 12R, 17, 22

Less than 1400/4 12R, 17 12R, 17

1700/4 or greater 30L, 35 30L &/or 35

Less than 1700/4 35 4s

Less than 1700/4 30L 17 or 22

Page 18: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

18MSP Runway Construction ProceduresSummer 2009

Runway Configurations – South Flow

• Weather 1400/4 or greater– Land 22/17 Depart 12R– Land 22/17 Depart 17

• Weather less than 1400/4 (Land 17/22 NA)– Land 12R Depart 17

Page 19: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

19MSP Runway Construction ProceduresSummer 2009

12R DEPARTURES - (Departure only Runway) (7110.65 para. 3-9-4)

• Sunrise to Sunset – You may authorize aircraft to

simultaneously TIPH on the same runway while the

“local assist” position is staffed.

Page 20: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

20MSP Runway Construction ProceduresSummer 2009

12R DEPARTURES - (Departure only Runway) (7110.65 para. 3-9-4)

• Sunset to Sunrise – You may authorize aircraft to TIPH at the intersections of Runway 12R at M, A8/W8 and A9/W9 if:– The Runway is used as a departure only runway– Only one aircraft at time is permitted to TIPH at any

intersection listed above or full length on the same runway– Do not authorize aircraft to TIPH simultaneously on

intersecting runways between sunset and sunrise– Document on 7230-4 the following: “TIPH at INT of RWY(number) and TWY(name) IN

EFFECT” when departure only runway and “TIPH at INT of RWY(number) and TWY(name) SUSPENDED when not a departure only runway”

Page 21: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

21MSP Runway Construction ProceduresSummer 2009

Spacing:

Rwy 17 = 4 miles

Rwy 22 = 6 miles

LAHSO (AR vs AR)

*Depts. from A8 & A9

A8 = 8100’

(M = 7100)

Summer 2009 (12L/30R Closed) Arrive Runways 17 & 22

Requires wx > 1,400/4 Depart Runway 12R

X

X

8550 ft

Page 22: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

22MSP Runway Construction ProceduresSummer 2009

Land 17 and 22Depart 12R, 17, 22

Departure Split

Left turn outs

All Dept. Rwys.Right turn outs

All Dept. Rwys.

G/K

E

GPZ

Page 23: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

23MSP Runway Construction ProceduresSummer 2009

Land 17 and 22Depart 12R, 17, 22

Dispersal Area

090

300

Page 24: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

24MSP Runway Construction ProceduresSummer 2009

Departures

• Runway 17/22/12R dispersal area includes heading 090°-300°.

• Assign FOD/ONL departures heading 215°-250°.

Page 25: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

25MSP Runway Construction ProceduresSummer 2009

Departures

• Assign LEINY/DWN/SMERF/FAR/BRD departures heading 270° or greater. Departure has control for turns west of the Runway 35 Localizer.

(Advise D if you turn a prop to a 300 inside a 270 jet or a similar operation, due to their control for turns.)

(Also be alert for 17/22 go arounds if you turn a prop west – northwest off RWY 12R.)

Page 26: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

26MSP Runway Construction ProceduresSummer 2009

Departures

• LEINY, DWN and SMERF traffic shall be treated as one fix, 3 MIT initial departure spacing (jet to jet, prop to prop)

• FAR and BRD traffic shall be treated as one fix, 3 MIT initial departure spacing (jet to jet, prop to prop)

• Turn HIB/DLH/WLSTN traffic east, 5 MIT initial departure spacing (jet to jet, prop to prop)

• EAU props exit M98 airspace south of TWINZ-over COULT.

*DLH traffic that will enter sector 6 will display AHH in the scratchpad.

Page 27: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

27MSP Runway Construction ProceduresSummer 2009

Land 17 and 22Depart 12R, 17, 22

Departure Split

Left turn outs

All Dept. Rwys.Right turn outs

All Dept. Rwys.

G/K

E

GPZ

Page 28: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

28MSP Runway Construction ProceduresSummer 2009

Departures

Good operating procedure –

Since EAU props exit the airspace south of TWINZ and DLH/WLSTN jets exit the airspace north of TWINZ………

Departure control would like DLH/WLSTN

jets inside COULT (EAU) props when possible.

(Jet on 090 Prop on 105)

Page 29: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

29MSP Runway Construction ProceduresSummer 2009

Jets and T-props to and over “DLH”

DLH/WLSTN 5 MIT prop-prop/jet-jet

“AHH”020-040

AGUDE

TWINZ

BITLR

DLH

Jet

s/Pr

ops

WLS

TN J

ets

Page 30: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

30MSP Runway Construction ProceduresSummer 2009

WLSTN – Jets

West of AGUDE

Heading to join AGUDE

TWINZ

BITLR

WLS

TN J

ETS

DL

H P

rop

s/Je

ts

Page 31: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

31MSP Runway Construction ProceduresSummer 2009

EAU/WLSTN propsOver

TAXEE/COULT

(not included with WLSTN jets or DLH

traffic spacing)

BITLR

TWINZ

AGUDE

EAU PROPS TAXEE/COULT

WLSTN/EAU TURBOPROPS SHALL BE CLEARED VIA THE COULT2 SID

REROUTE:

MSP.COULT2.COULT..EAU (next fix/airway)

Page 32: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

32MSP Runway Construction ProceduresSummer 2009

Departures

• 17/22 and the Bemidji Push– V218,V82, BRD traffic one fix 3 MIT initial departure

spacing.– FAR, AXN, STC traffic one fix 3 MIT initial departure

spacing.– DLH, HIB, and east traffic turned eastbound.– Visual separation and diverging headings shall not

be applied between like fixes.– May APREQ with FCM Satellite the use of headings

270° and 300° during this push

Page 33: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

33MSP Runway Construction ProceduresSummer 2009

Land 17 and 22Depart 12R, 17, 22

Departure Split

Left turn outs

All Dept. Rwys.Right turn outs

All Dept. Rwys.

G/K

E

GPZ

Page 34: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

34MSP Runway Construction ProceduresSummer 2009

Departures

• All Runway 17 or 22 departures (other than 30/17 configuration) shall be approved and coordinated by the CC.

• Traffic departing full length Runway 12R should be rolling by the time Runway 22 traffic is 1.5 miles from the runway end.

• Traffic departing from Runway 12R at A8 should be rolling by the time Runway 22 traffic is 1 mile from the runway end.

Page 35: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

35MSP Runway Construction ProceduresSummer 2009

Arrivals

• When both 22 and 17 approaches in use, weather minimums are 1400 and 4.

• LAHSO is authorized for Runway 22 landing traffic to hold short of Taxiway Kilo for:– Runway 17 arrivals – Runway 17 departures using Rwy 22 DDA

*Available distance 8550 ft.

Page 36: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

36MSP Runway Construction ProceduresSummer 2009

Arrivals

• The Departure Decision Area (DDA) is in effect when we are doing LAHSO to Runway 22 and departing Runway 17.– The DDA is on Runway 22 between a ¼ mile final

and nose wheel touching the runway.– Aircraft on Runway 17 cannot depart when an

aircraft is in the DDA.

*Non - advertised Rwy operations will be coordinated in advance.

Page 37: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

37MSP Runway Construction ProceduresSummer 2009

Arrivals

• When LAHSO in use, aircraft unable to LAHSO should be assigned Runway 17.

• If traffic conditions do not permit use of Runway 17, the aircraft shall be assigned Runway 22.

• AO shall advise CC of aircraft landing Runway 22 that will not LAHSO

• During non-compliant LAHSO operations, approach shall provide 2-mile spacing ahead and behind the RWY 22 arrival with the RWY17 arrivals.

Page 38: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

38MSP Runway Construction ProceduresSummer 2009

Arrivals

• All Runway 17 or 22 go around traffic should make a right turn and return to Runway 17 regardless of the initially assigned landing runway.

• If Weather is less than 1400/4 on South Flow

12R and 17 are the only option – one for departure and one for landing.

Page 39: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

39MSP Runway Construction ProceduresSummer 2009

Arrivals

• No LAHSO to Runway 22/17 with: – Tailwind– Wet or contaminated Runway– Wind Shear – Weather less than 1400/4

Page 40: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

40MSP Runway Construction ProceduresSummer 2009

South Flow – Local Frequencies

• Weather 1400/4 or greater– LCS – 12R departures – 126.7– LCW – 17 arrivals & departures – 123.67– LCN – 22 arrivals – 123.95

• Weather less than 1400/4 (Land 17/22 NA)– LCS – 12R arrivals – 126.7– LCW – 17 departures – 123.67

Page 41: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

41MSP Runway Construction ProceduresSummer 2009

Rwy 17 = 6 miles

Rwy 22 = 6 miles

CRDA -

Staggered Arrivals

Requires weather criteria > 1,400/4

Depts from M, A8 & A9

A8 = 8100’

M = 7100

Summer 2009 (12L/30R Closed) Arrive Runways 17 & 22

No-LAHSO / Wet Rwys / Tailwind Depart Runway 12R

X

X

Page 42: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

42MSP Runway Construction ProceduresSummer 2009

ILS WX < 1,400/4

Summer 2009 (12L/30R Closed) Arrive Runway 12R

ILS Configuration (South Flow) Depart Runway 17

X

X

Page 43: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

43MSP Runway Construction ProceduresSummer 2009

Arrivals/Departures

• Land Runway 12R, depart Runway 17– Use 12/17 configuration

(Must be used when weather is less than 1400/4 on South Flow)

Page 44: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

44MSP Runway Construction ProceduresSummer 2009

Runway Configurations – North Flow

• Weather 1700/4 or greater– Land 30L/35 Depart 30L– Land 30L/35 Depart 35

• Weather less than 1700/4– Land 35 Depart 4 @ S– Land 30L Depart 17– Land 30L Depart 22 (using 30/17 procedures)

Page 45: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

45MSP Runway Construction ProceduresSummer 2009

*CRDA and ADW will be used.

Rwy 30L = 8 miles

Rwy 35 = 4 miles

(eventually down to 3.5/7)

LAHSO 30L/A9 for crossings.

Summer 2009 (12L/30R Closed) Arrive Runways 30L & 35

Requires weather > 1,700/4 Depart Runway 30L

X

X

Page 46: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

46MSP Runway Construction ProceduresSummer 2009

Rwy 35 = 6 miles

Rwy 30L = 4 miles

LAHSO - crossings 30L

Summer 2009 (12L/30R Closed) Arrive Runways 30L & 35

Requires weather > 1,700/4 Depart Runway 35

X

X

Page 47: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

47MSP Runway Construction ProceduresSummer 2009

Departure numbers

S = 9,450’

C2 = 8,250’

C3 = 7,350’

*Be alert for Rwy 35 Go Arounds if you turn traffic left off Rwy 4.

Summer 2009 (12L/30R Closed) Arrive Runways 35

ILS Configuration < 1,700/4 Depart Runway 4

X

X

Page 48: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Presented to: Minneapolis ATCT

Date: Summer 2009

Federal AviationAdministration

Tower AirspaceLand 35 Depart 04

Tower AirspaceLand 35 Depart 04

Page 49: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

49MSP Runway Construction ProceduresSummer 2009

Summer 2009 (12L/30R Closed) Arrive Runway 30L

ILS Configuration < 1,700/4 Depart Runway 17

X

X

Page 50: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

50MSP Runway Construction ProceduresSummer 2009

Departures

• Airspace, including departure dispersal airspace shall be the land 30 & 35, depart 30s configuration (when using any combination of 30L/35).

• All Runway 4 departures (other than 4/35 configuration) shall be approved and coordinated by the CC.

• Departure has control for turns on initial contact of aircraft departing Runway 35 and turned left.

Page 51: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

51MSP Runway Construction ProceduresSummer 2009

Arrivals/Departures

• Land Runway 30L, depart Runway 17– Use 30/17 configuration– COULT traffic departing 17 shall be assigned to

North Departure and issued right turns.– North Departure has control for turns of COULT

traffic on initial contact.

Page 52: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

52MSP Runway Construction ProceduresSummer 2009

North Flow – Local Frequencies

• Weather 1700/4 or greater– LCS – 30L arrivals & departures – 126.7– LCW – 35 arrivals & departures – 123.67

• Weather less than 1700/4– LCS – 30L arrivals & departures, 4 departures – 126.7– LCW – 35 arrivals & 17 departures – 123.67

Page 53: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

53MSP Runway Construction ProceduresSummer 2009

Local Control Assist (LCA)

• Coordinates and relays traffic info between GC-N and GC-S. Other positions as needed.

• Authority to approve runway crossings of Runway 22 between the parallels without coordination from the Runway 22 Local Controller.

• LCA shall not approve a RWY22 crossing in front of a departure holding in position or in front of RWY22 traffic at a 1 mile final or less without coordinating with the Local controller.

• Combined with CCS when not staffed.

Page 54: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

54MSP Runway Construction ProceduresSummer 2009

Taxi Procedures

• Normal Runway 22 crossing points:– Main terminal: P, Q, C6/M6, A, B– Humphrey terminal: S

• When LCA is open, all runway crossings of Runway 22 between the parallels should be coordinated by LCA.

• Ground control shall maintain heightened awareness to keep runway turnoffs clear of traffic.

Page 55: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

55MSP Runway Construction ProceduresSummer 200955

Can you spot the potential for a Runway Incursion?

Can you spot the potential for a Runway Incursion?

Page 56: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

56MSP Runway Construction ProceduresSummer 200956

HIGH POTENTIAL FOR RUNWAY INCURSION

If you guessed here, you are Correct!

Page 57: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

57MSP Runway Construction ProceduresSummer 200957

HIGH POTENTIAL FOR RUNWAY INCURSION

If you are taxiing on Romeo towards the R3 entrance, You MUST STOP and Contact Ground PRIOR to Entering R3

Romeo Taxiway Hold Short Lines for Runway 22

Page 58: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

58MSP Runway Construction ProceduresSummer 2009

Runway 35 Reduced Separation

• When Runway 35 is the only arrival runway, spacing on the final may be reduced to 2.5 NM.

Page 59: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

59MSP Runway Construction ProceduresSummer 2009

CRDA - ADW

30L/35

Page 60: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

60MSP Runway Construction ProceduresSummer 2009

Runway 30LArrivals &

Departures

Runway 35Arrivals Only

August 17 thru

October 24

Page 61: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

61MSP Runway Construction ProceduresSummer 2009

1.9 NM

.4 NM

ADW

ADW DOES NOT APPLY TO SMALL AC.

Page 62: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

62MSP Runway Construction ProceduresSummer 2009

AREA OF GREATEST RISK

0.40 0.61 0.83 1.05 1.26 1.48 1.69 1.91 Distance from Runway 35 Threshold

Page 63: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

63MSP Runway Construction ProceduresSummer 2009

Arrival Distance Window

• Arrival Distance Window (ADW)– A tool used by the tower to determine when a departure on

Runway 30L may be released so as to reduce the likelihood of a collision at the convergence of Runway 35 and 30L, IFIF the Runway 35 arrival executes a go around.

– Runway 30L departure may be released until Runway 35 arrival ENTERS the ADW (1.9 NM final).

– In this case, the departure will cross the convergence point approximately 15 seconds ahead of an arrival that executes a go around on Runway 35.

Page 64: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

64MSP Runway Construction ProceduresSummer 2009

Page 65: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

65MSP Runway Construction ProceduresSummer 2009

Arrival Distance Window

• Arrival Distance Window (ADW)– Runway 30L departure may be released when the Runway 35

arrival EXITS the ADW (.4 NM final).– In this case, the arrival on Runway 35 will cross the

convergence point approximately 15 seconds ahead of a departure that executes a go around on Runway 35.

Page 66: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

66MSP Runway Construction ProceduresSummer 2009

Page 67: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

67MSP Runway Construction ProceduresSummer 2009

Arrival Distance Window

• Runway 30L/35 Dependency – In order to provide the tower with useable departure gaps on

Runway 30L• Converging Runway Display Aid (CRDA)

• Provides “ghost target” on Runway 30L based on the position of the “real target” on Runway 35

• Position of the “ghost” is staggered with respect to the “real target” to provide departure opportunities on Runway 30L.

• Planned spacing to start with:– Runway 35…………….4 NM in-trail at touchdown– Runway 30L……………8 NM in-trail at touchdown

(eventually down to 3.5/7)

Page 68: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

68MSP Runway Construction ProceduresSummer 2009

RETIREMENTS

FM – NO retirements until after construction!

Page 69: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

69MSP Runway Construction ProceduresSummer 2009

Estimated Arrival/Departure RatesNorth Flow During ConstructionNorth Flow During Construction

With ADW

• Arrivals– VFR 40-46– ILS 40-46

• Departures– VFR 30*– ILS 30*

Without ADW

• Arrivals– VFR 56-60– ILS 56-60

• Departures– VFR 40*– ILS 40*

•1700’ & 4 NM

Page 70: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

70MSP Runway Construction ProceduresSummer 2009

Estimated Arrival/Departure RatesNorth Flow After ConstructionNorth Flow After Construction

With ADW• Arrivals

– VFR 70-75*– ILS 40-46

• Departures– VFR 60– ILS 60

Without ADW• Arrivals

– VFR 90– ILS 44-76

• Departures– VFR 66– ILS 66

•1700’ & 4 NM

Page 71: Presented to: Minneapolis ATCT Date: Summer 2009 Federal Aviation Administration Minneapolis Runway Construction Procedures Runway 12L/30R

Federal AviationAdministration

71MSP Runway Construction ProceduresSummer 2009

THE END