|
|
| (4 intermediate revisions by one other user not shown) |
| Line 354: |
Line 354: |
|
| |
|
| |-|Track Locations= | | |-|Track Locations= |
| [[File:Military-TrackLocations.jpeg|800px]] | | [[File:Military-TrackLocations.jpeg|600px]] |
|
| |
|
| Standard USAF air refueling tracks are scattered across the United States, and include several that exist all or partially within New York Center and Oceanic airspace as above. | | Standard USAF air refueling tracks are scattered across the United States, and include several that exist all or partially within New York Center and Oceanic airspace as above. |
|
| |
|
| |-|Track Elements= | | |-|Track Elements= |
| [[File:Military-AnchorPattern.png]] | | [[File:Military-AnchorPattern.png|600px]]<br> |
|
| |
|
| The aerial refueling track consists of the '''IP''' (initial point), '''CP''' (control point), and the '''EP''' (exit point). The IP is the first fix that begins the AR track. Once airborne, pilots may request to be cleared direct to this point in order to save time. The CP is where the actual rendezvous shall occur and where refueling begins. These points should be listed on the flight plans; however, if they are not specified, pick points along the requested AR that roughly correlates to the beginning and the end of the track. The CP can be any point along the AR, but is typically 20-30 NM after the IP. | | The aerial refueling track consists of the '''IP''' (initial point), '''CP''' (control point), and the '''EP''' (exit point). The IP is the first fix that begins the AR track. Once airborne, pilots may request to be cleared direct to this point in order to save time. The CP is where the actual rendezvous shall occur and where refueling begins. These points should be listed on the flight plans; however, if they are not specified, pick points along the requested AR that roughly correlates to the beginning and the end of the track. The CP can be any point along the AR, but is typically 20-30 NM after the IP. |
| Line 366: |
Line 366: |
| Military aircraft will use IFR clearances to go from airfield to AR track and vice versa. These clearances will usually be given for both receiver and tanker as follows:<br> | | Military aircraft will use IFR clearances to go from airfield to AR track and vice versa. These clearances will usually be given for both receiver and tanker as follows:<br> |
| '''DUSTY01 heavy, cleared from McGuire AFB to McGuire AFB via direct SIE direct SWL AR9 SWL and the SIE4 arrival. Climb and maintain 8,000’, expect filed altitude 10 minutes after departure. Departure on 124.15, squawk 4412.''' | | '''DUSTY01 heavy, cleared from McGuire AFB to McGuire AFB via direct SIE direct SWL AR9 SWL and the SIE4 arrival. Climb and maintain 8,000’, expect filed altitude 10 minutes after departure. Departure on 124.15, squawk 4412.''' |
| | | <br><br> |
| If the tanker or receiver is early, they may request a delay at the CP as follows: | | If the tanker or receiver is early, they may request a delay at the CP as follows:<br> |
| ''DUSTY01 requesting delay at the control point, waiting for COSMIC flight.''<br> | | ''DUSTY01 requesting delay at the control point, waiting for COSMIC flight.''<br> |
| '''DUSTY01, cleared to delay at the control point.''' | | '''DUSTY01, cleared to delay at the control point.''' |
| | | <br><br> |
| The delaying aircraft should advise the callsign(s) of the aircraft they are waiting for. As the inbound aircraft approach, prompt the lead tanker to declare MARSA: | | The delaying aircraft should advise the callsign(s) of the aircraft they are waiting for. As the inbound aircraft approach, prompt the lead tanker to declare MARSA:<br> |
| | | '''DUSTY01, advise accepting MARSA with COSMIC.'''<br> |
| '''DUSTY01, advise accepting MARSA with COSMIC.''' | | <br> |
| | | After the lead tanker accepts MARSA with the receiver aircraft/flight, clear the inbound aircraft for the AR track:<br> |
| After the lead tanker accepts MARSA with the receiver aircraft/flight, clear the inbound aircraft for the AR track: | |
| '''COSMIC flight, cleared to conduct refueling along AR9 track, mantain block FL240 through FL260.'''><br> | | '''COSMIC flight, cleared to conduct refueling along AR9 track, mantain block FL240 through FL260.'''><br> |
| ''Roger, cleared down track, FL240 to FL260, COSMIC01.''><br> | | ''Roger, cleared down track, FL240 to FL260, COSMIC01.''><br> |
| '''COSMIC01, readback correct, frequency change approved.''' | | '''COSMIC01, readback correct, frequency change approved.'''<br> |
| | | <br> |
| In general, the receivers will enter the lead tanker’s block at the lower altitude (FL240), refuel at the middle altitude (FL250), and then depart the block at the top altitude (FL260) when finished. | | In general, the receivers will enter the lead tanker’s block at the lower altitude (FL240), refuel at the middle altitude (FL250), and then depart the block at the top altitude (FL260) when finished. |
|
| |
|
| Line 395: |
Line 394: |
|
| |
|
| >'''COSMIC flight, MARSA terminated between you and DUSTY flight.''' | | >'''COSMIC flight, MARSA terminated between you and DUSTY flight.''' |
| | | <br> |
| ;Multiple Flights | | ;Multiple Flights |
| To conduct breakaway with multiple flights, instruct the lead tanker to send the receivers to their own separate altitudes within the block. If the block is large enough to accommodate all the aircraft with proper separation, then instruct the tanker to have each aircraft report level at a different altitude. | | To conduct breakaway with multiple flights, instruct the lead tanker to send the receivers to their own separate altitudes within the block. If the block is large enough to accommodate all the aircraft with proper separation, then instruct the tanker to have each aircraft report level at a different altitude. |
| Line 404: |
Line 403: |
|
| |
|
| ==Special Flight Profiles== | | ==Special Flight Profiles== |
| {{tabs
| | <tabber> |
| |uniqueid=profiles | | |-|Formation= |
| |label1=Formation | | {{Extract:Military-FormationFlights}} |
| |content1=
| |
| ===Formation Flights===
| |
| {{tabs | |
| |uniqueid=formations
| |
| |label1=Formation Basics
| |
| |content1=
| |
| All formation flying requires MARSA separation to be declared or accepted by all parties, which may be accomplished through flight plan notes or initial clearance acceptance by the pilot. ATC shall not separate MARSA flights internally, but retains responsibility for their separation as a group from other IFR traffic. There are two types of flight formations:
| |
| * '''Standard Formation''' - A formation in which a proximity of no more than 1NM laterally and 100 feet vertically from the flight leader is maintained by each wingman.
| |
| * '''Nonstandard Formation''' - A formation operating under any of the following conditions:
| |
| **ATC-approved formation proximity greater than 1NM laterally or 100 feet vertically (e.g. Marching Order operations).
| |
| **Within an authorized ALTRV (Altitude Reservation) or under special provisions of a letter of agreement.
| |
| **Within Special Use Airspace
| |
| |label2=Communications
| |
| |content2=
| |
| All ATC communications shall be with flight leaders only except for emergency conditions as required by ATC. Flights may be referred without numbers if holding unique callsigns: for instance, COSMIC01 may be the flight leader for COSMIC02 and COSMIC03, but may self-refer and be referred to as COSMIC FLIGHT while under MARSA.
| |
|
| |
|
| If aircraft significantly depart from formation separation (or joins a new formation), the flight lead of that formation must accept MARSA with that aircraft prior to breach of normal separation, and should be prompted by ATC when intentions to join are announced by the joining aircraft:
| | |-|Marching Order/MITO= |
| <div class="well">
| |
| <span style="color:blue">'''New York Center, COSMIC05 with you, request to join with COSMIC01.'''</span><br>
| |
| <span style="color:green">'''COSMIC01, will you accept MARSA with COSMIC05?'''</span><br>
| |
| <span style="color:blue">'''COSMIC01, will accept MARSA.'''</span><br>
| |
| <span style="color:green">'''COSMIC05, join COSMIC01, strangle parrot when able.'''</span><br>
| |
| <span style="color:blue">'''COSMIC05, will join and strangle.'''</span>
| |
| </div>
| |
| |label3=Transponder Use | |
| |content3= | |
| * For '''all''' formation flights, ATC shall assign one transponder code for the flight.<br>
| |
| * For standard formations, the flight leader shall squawk Mode C on assigned code, all others shall squawk Mode S on subset code. <br>
| |
| * For nonstandard trailing formations (Marching Order), flight leader shall squawk Mode C on assigned code, trailing aircraft shall squawk Mode S on subset code except last aircraft, which shall squawk mode C with subset code. <br>
| |
| * For nonstandard formations of other types (SUA, etc), flight leader shall squawk mode C on assigned code, and other aircraft shall squawk mode C on subset code. <br>
| |
| ATC may assign other variations of the above transponder use procedure as required.
| |
|
| |
|
| |label4=Breakaway
| | ====Basics, DEL/GND==== |
| |content4=
| |
| If a flight member must break away from formation and be treated individually by ATC, the flight leader shall notify ATC which callsign will depart. ATC will assign a discrete squawk code to the breakaway aircraft, which will then squawk mode C. ATC will assign vectors as necessary (directly) to breakaway aircraft and terminate MARSA for those aircraft. As below:
| |
| <div class="well">
| |
| <span style="color:blue">'''New York Center, COSMIC flight, COSMIC04 will break away for return to McGuire.'''</span><br>
| |
| <span style="color:green">'''COSMIC flight, roger. Have COSMIC04 come up this frequency on beacon code 4065.'''</span><br>
| |
| <span style="color:blue">'''COSMIC, roger.'''</span><br>
| |
| <span style="color:blue">'''New York Center, COSMIC04 with you for return to McGuire.'''</span><br>
| |
| <span style="color:green">'''COSMIC04, New York Center, radar contact. (further ATC directions here)'''</span>
| |
| </div>
| |
| }}
| |
| | |
| |label2=Marching Order/MITO
| |
| |content2=
| |
| ===Marching Order/MITO=== | |
| {{tabs
| |
| |uniqueid=marchingorder
| |
| |label1=Basics, DEL/GND
| |
| |content1=
| |
| Marching Order is a proword used to indicate that a flight has been activated and is to be launched by an Emergency War Order. While mostly a thing of the past in the real world, Marching Order flights may still be encountered on VATSIM, and have special procedures associated with them. Marching Order notice can be made either through flight plan remarks or via voice in initial contact. | | Marching Order is a proword used to indicate that a flight has been activated and is to be launched by an Emergency War Order. While mostly a thing of the past in the real world, Marching Order flights may still be encountered on VATSIM, and have special procedures associated with them. Marching Order notice can be made either through flight plan remarks or via voice in initial contact. |
| <div class="well"> | | <br><br> |
| <span style="color:blue">'''Westover Ground, Kilo Echo flight of five on the tree, IFR clearance marching order.'''</span><br> | | ''Westover Ground, Kilo Echo flight of five on the tree, IFR clearance marching order.''<br> |
| <span style="color:green">'''Kilo Echo, Westover Ground, cleared via radar vectors GLYDE then as filed. Level off 7,000, departure frequency 125.35, squawk 4011, last aircraft subset Charlie.'''</span><br>
| | '''Kilo Echo, Westover Ground, cleared via radar vectors GLYDE then as filed. Level off 7,000, departure frequency 125.35, squawk 4011, last aircraft subset Charlie.'''><br> |
| <span style="color:blue">'''As filed, level at Angels 7, squawk 4011, last aircraft subset Charlie, Kilo Echo flight. Request MITO departure when ready.'''</span><br>
| | ''As filed, level at Angels 7, squawk 4011, last aircraft subset Charlie, Kilo Echo flight. Request MITO departure when ready.'''<br> |
| <span style="color:green">'''Kilo Echo flight, MITO approved Runway 5, advise when ready for departure.'''</span>
| | '''Kilo Echo flight, MITO approved Runway 5, advise when ready for departure.''' |
| </div> | | <br><br> |
| There is a lot going on above to decipher. | | There is a lot going on above to decipher. |
| * Marching Order flights will nearly always start from an alert area known as an Alert Tree or colloquially "Christmas Tree", shown below. | | * Marching Order flights will nearly always start from an alert area known as an Alert Tree or colloquially "Christmas Tree", shown below. |
| Line 472: |
Line 424: |
| Once MITO is approved, aircraft will start engines and taxi in close order off the tree towards the runway. | | Once MITO is approved, aircraft will start engines and taxi in close order off the tree towards the runway. |
| ; A standard Alert Tree: | | ; A standard Alert Tree: |
| [[File:Tree.png|350px]] | | [[File:Military-AlertTree.png|350px]] |
|
| |
|
| |label2=Tower, Departure
| | ====Tower, Departure==== |
| |content2=
| |
| Once rolling towards the runway, controllers covering Tower should expect a fairly immediate request for MITO takeoff clearance. If all transponders are set correctly and departure airspace is clear and will remain so for the entire duration of the MITO procedure, clearance should be granted. | | Once rolling towards the runway, controllers covering Tower should expect a fairly immediate request for MITO takeoff clearance. If all transponders are set correctly and departure airspace is clear and will remain so for the entire duration of the MITO procedure, clearance should be granted. |
| | |
| ; Departure Headings | | ; Departure Headings |
| The first aircraft in a MITO formation should be given a departure heading 30 degrees offset from runway heading in the direction of flight. Second aircraft should be given 10 degrees less offset, third runway heading, and the set of intervals repeats after that with 30 degrees offset for the fourth aircraft. This is done to minimize the extreme wake turbulence created by heavy aircraft departing in short order: if departure procedures for specific airports require one single departure heading be assigned for flight safety, MITO may NOT be performed at minimum separation due to likely aircraft damage or loss. | | The first aircraft in a MITO formation should be given a departure heading 30 degrees offset from runway heading in the direction of flight. Second aircraft should be given 10 degrees less offset, third runway heading, and the set of intervals repeats after that with 30 degrees offset for the fourth aircraft. This is done to minimize the extreme wake turbulence created by heavy aircraft departing in short order: if departure procedures for specific airports require one single departure heading be assigned for flight safety, MITO may NOT be performed at minimum separation due to likely aircraft damage or loss. |
| | |
| ; Minimum Intervals | | ; Minimum Intervals |
| The basic point of a MITO departure is to get all aircraft airborne as rapidly as possible. Thus, aircraft depart under MARSA conditions with special pilot-timed separation. Below are listed the minimum timings: | | The basic point of a MITO departure is to get all aircraft airborne as rapidly as possible. Thus, aircraft depart under MARSA conditions with special pilot-timed separation. Below are listed the minimum timings: |
| Line 484: |
Line 437: |
| * '''B-52''' - 12 Seconds | | * '''B-52''' - 12 Seconds |
| * '''KC-135''' - 15 Seconds <br> | | * '''KC-135''' - 15 Seconds <br> |
| As in the example below, the first aircraft will be given the full takeoff clearance on behalf of the flight, including instruction to contact departure airborne. Subsequent aircraft will only be given their heading and "cleared for takeoff." Individual full clearances for flight members are not required due to MARSA. Runway entry is also covered by MARSA, and each subsequent aircraft will line up as the last one departs while calling for clearance, counting time between last aircraft rolling time and the time they will advance throttles. | | As in the example below, the first aircraft will be given the full takeoff clearance on behalf of the flight, including instruction to contact departure airborne. Subsequent aircraft will only be given their heading and "cleared for takeoff." Individual full clearances for flight members are not required due to MARSA. Runway entry is also covered by MARSA, and each subsequent aircraft will line up as the last one departs while calling for clearance, counting time between last aircraft rolling time and the time they will advance throttles.<br><br> |
| <div class="well"> | | ''Westover Tower, Kilo Echo 1 1, flight ready for MITO.'''<br> |
| <span style="color:blue">'''Westover Tower, Kilo Echo 1 1, flight ready for MITO.'''</span><br> | | '''Kilo Echo 1 1, Westover Tower, fly heading 080, contact departure airborne, runway 15 cleared for takeoff.'''<br> |
| <span style="color:green">'''Kilo Echo 1 1, Westover Tower, fly heading 070, contact departure airborne, runway 15 cleared for takeoff.'''</span><br>
| | ''Heading 080, runway 15 cleared for takeoff, Kilo Echo 1 1.''<br> |
| <span style="color:blue">'''Heading 080, runway 15 cleared for takeoff, Kilo Echo 1 1.'''</span><br>
| | ''Kilo Echo 1 2, lining up 5.'''<br> |
| <span style="color:blue">'''Kilo Echo 1 2, lining up 5.'''</span><br>
| | '''Kilo Echo 1 2, fly heading 060, cleared for takeoff.'''<br> |
| <span style="color:green">'''Kilo Echo 1 2, fly heading 060, cleared for takeoff.'''</span><br>
| | ''060, cleared for takeoff, 1 2.''<br> |
| <span style="color:blue">'''060, cleared for takeoff, 1 2.'''</span><br>
| | ''Kilo Echo 1 3, lining up 5.''<br> |
| <span style="color:blue">'''Kilo Echo 1 3, lining up 5.'''</span><br>
| | '''Kilo Echo 1 3, fly heading 050, cleared for takeoff.'''<br> |
| <span style="color:green">'''Kilo Echo 1 3, fly heading 050, cleared for takeoff.'''</span><br>
| | ''050, cleared for takeoff, 1 3.'' |
| <span style="color:blue">'''050, cleared for takeoff, 1 3.'''</span>
| | |
| </div>
| |
| Once departed, the lead aircraft will contact departure and advise them of flight number and status as normal. | | Once departed, the lead aircraft will contact departure and advise them of flight number and status as normal. |
|
| |
|
| <span style="color:red">'''NOTE: Due to the large airspace required, heavy wake turbulence, and complexity, this maneuver REQUIRES coordinated approval between ground, tower, and departure PRIOR to MITO being approved.'''</span>
| | '''NOTE: Due to the large airspace required, heavy wake turbulence, and complexity, this maneuver REQUIRES coordinated approval between ground, tower, and departure PRIOR to MITO being approved.''' |
| }}
| | |
| |label3=Supersonic | | |-|Supersonic= |
| |content3= | |
| ===Supersonic===
| |
| Supersonic operations may be conducted in any waters 20NM away from any shoreline, and may be conducted in properly activated Warning or Military Operating Areas. | | Supersonic operations may be conducted in any waters 20NM away from any shoreline, and may be conducted in properly activated Warning or Military Operating Areas. |
| }}
| | |
| | </tabber> |