Updated: 2024-01-10 --- %% >[!todo] >Marking moms >Approaches and phrasing >Special carrier procedures %% # CASE I Recovery There are 3 ways aircraft can be guided to land on the carrier during CASE I conditions: 1. Regular CASE I recovery. 2. Vectors to initial 3. Vectors to final Vectors to initial/final will usually only be used on special case scenarios. For example, if TACAN isn't working. #### Inbound As aircraft reach the CCA, they will contact Marshal and make their inbound call with the following information: - Modex/holding hands with modexes - Radial from the carrier - Distance from the carrier - Altitude in angels - Fuel state > [!example]+ Inbound as single > "`[Carrier callsign]` marshal, `[Modex]`, marking mom's `[radial from carrier]`, for `[distance from carrier]`, angels `[current altitude]`, state `[fuel state]`" > >[!quote] > >`A/C`:"Rough Rider Marshal, 203, marking mom's 090 for 50, angels 25, low state 8.0" > [!example]+ Inbound as a flight > "`[Carrier callsign]` marshal, `[Modex]`, holding hands with `[all other modexes in your flight]`, marking mom's `[radial from carrier]`, for `[distance from carrier]`, angels `[current altitude]`, low state `[fuel state]`" > >[!quote] > >`A/C`:"Rough Rider Marshal, 203, holding hands with 204, 205, and 206, marking mom's 090 for 50, angels 25, low state 8.0" > [!note] > 1. The inbound call is the same for CASE I, II, and III recoveries. > 2. "Low state" is used when checking in as a flight meaning the lowest fuel state in the flight. Marshal will respond to their call with the following information: - Radar/Negative contact - Type of recovery (CASE I in this case) - Mother's altimeter - Mother's Base Recovery Course (BRC) - The flight's assigned marshal stack - When the flight should contact Marshal again >[!example]+ Radar Contact > "`[Modex]`, `[Carrier callsign]` Marshal, radar contact, CASE I recovery expected, mother's altimeter `[QNH]`, BRC `[carrier's magnetic course]`, marshal at angels `[#]`, report `[when they should report back]`." > > [!quote] > > ==Marshal==: "203, Rough Rider Marshal, radar contact, CASE I recovery expected, mother's altimeter 2992, BRC 180, marshal at angels 2, report see me at 10." > > `A/C`: "203. Altimeter 2992, BRC 180, marshal angels 2." >[!example]+ Negative Contact > "`[Modex]`, `[Carrier callsign]` Marshal, negative contact, `[discuss next steps to achieve radar contact]`" > > [!quote] Example > > ==Marshal==: "203, Rough Rider Marshal, negative contact, say current position from mother." > > `A/C`: "Rough Rider Marshal, 203 marking mom's 090 for 50, angels 25." When the flight reaches their reporting point, they will contact Marshal. >[!example]+ Flight reaches reporting point > "`[Carrier Callsign]` marshal, `[Modex]`, `[repeat report point]`" > >[!quote] Example > > `A/C`: "Rough Rider Marshal, 203, see you at 10." > > >[!quote] Example 2 > > `A/C`: "Rough Rider Marshal, 203 established angels 2." At this point IRL, Marshal will usually instruct the flight to switch Tower. However as per vCSG-3 SOPs, we keep flights on Marshal's frequency until they commence. ### Marshal Stack If for any reason, Marshal needs a flight to climb/descend in the marshal stack, they can say the following: >[!example]+ Climb/Descend in Stack > "`[Modex]`, take angels `[altitude]`." > >[!quote] Example > > ==Marshal==: "203, take angels 3." > > `A/C`: "203." > When Marshal is happy for a flight to commence, they will say the following: > [!example]+ Commence > "`[Modex]`, your signal is Charlie." > > [!quote] Example > > ==Marshal==: "203, your signal is Charlie." > > `A/C`: "203." When a flight reaches POS 3 and starts commencing, Marshal will hand the flight over to tower. >[!example]+ Hand over to Tower > "`[Modex]`, switch tower, button `[#]`" > >[!quote] Example > > `A/C`: "Rough Rider Marshal, 203 commencing." > > ==Marshal==: "203, switch Tower, button 1." > > `A/C`: "203." ### Vectors to Initial In case vectors to initial is the preferred way to recover aircraft, a marshal stack my not be required. The entire process is similar to recovering aircraft at an airfield. >[!quote]+ Vector to initial > `A/C`: "Rough Rider Marshal, 203 marking mom's 090 for 50, angels 20, low state 7.0" > ==Marshal==: "203, Rough Rider Marshal, radar contact, CASE I recovery expected. Mother's altimeter 2992, BRC 270. Maintain heading, descend maintain angels 2. Expect vectors to initial for the overhead break." > `A/C`: "203, maintain heading, descend maintain angels 2. Will expect that." ### Vectors to Final Just like vectoring aircraft into the initial. The process for vectoring aircraft to final is similar to a straight in approach at an airfield. >[!quote]+ Vectors to Final > `A/C`: "Rough Rider Marshal, 203 marking mom's 090 for 50, angels 20, low state 7.0" > ==Marshal==: "203, Rough Rider Marshal, radar contact, CASE I recovery expected. Mother's altimeter 2992, final bearing 261. Maintain heading, descend maintain angels 2. Expect vectors to final." > `A/C`: "203, maintain heading, descend maintain angels 2. Will expect that." ### CASE I Recovery Comms Flow >[!quote]+ > `A/C`: "Rough Rider Marshal, 203 marking moms 090 for 50, angels 28, low state 7.0." > ==Marshal==: "203, Rough Rider Marshal, radar contact. CASE I Recovery expected, mother's altimeter 2992, BRC 180, marshal angels 2, report see me at 10." > `A/C`: "203, altimeter 2992, BRC 180, marshal angels 2." > *203 reaches 10DME* > `A/C`: "Rough Rider Marshal, 203, see you at 10." > ==Marshal==: "203, marshal angels 2." > `A/C`: "203." > *When Marshal is ready for 203 to commence* > ==Marshal==: "203, your signal is Charlie." > `A/C`: "203." > *203 gets to POS 3* > `A/C`: "203, commencing." > ==Marshal==: "203, switch tower." > `A/C`: "203." >[!note] Notes > 1. Marshal does not have to instruct flights to switch tower only when they start commencing. Controllers have the option to include the instruction to switch tower on the "Signal is Charlie" call. > 2. Pilots are only required to acknowledge information and instructions given. Readbacks are not mandatory. - - - # CASE III & II Recovery There are two ways aircraft can be guided to land at the aircraft under CASE III conditions: 1. Regular CASE III recovery 2. Vectors to final Vectors to final will usually only be used in special case scenarios. ### Inbound After receiving an inbound call from a flight, Marshal will respond with the following information: - Radar/Negative contact - CASE III recovery - Type of approach in use - Mother's altimeter - Mother's FB - The assigned holding radial - Each flight member's assigned holding altitude - When the flight should contact Marshal again >[!example]+ Responding to one ship > `[Modex]`, `[Carrier's callsign]` Marshal, radar contact, CASE III recovery expected, CV-1 Approach. Mother's altimeter `[altimeter]`, final bearing `[final bearing]`. `[Modex]`, marshal on the `[holding radial]`, angels `[altitude]`, report established. > >[!quote] Example > >==Marshal==: "203, Rough Rider Marshal, radar contact. CASE III recovery expected, CV-1 approach, mother's altimeter 2992, final bearing 270. 203, marshal on the 090, angels 6, report established." > > `A/C`: "203, mother's altimeter 2992, final bearing 270, marshal on the 090, angels 6, wilco." > >[!example]+ Responding to a flight > "`[Modex]`, `[Carrier's callsign]` Marshal, radar contact, CASE III recovery expected, CV-1 approach, mother's altimeter `[altimeter]`, final bearing `[final bearing]`. `[Modex]`, marshal on the `[holding radial]`, angels `[altitude]`, `[Modex]`, angels `[altitude]`, report established. > >[!quote] Example > > ==Marshal==: "203, Rough Rider Marshal, radar contact, CASE III recovery expected, CV-1 Approach, mother's altimeter 2992, final bearing 270. 203, marshal on the 090, angels 6, 204 angels 7, report established." > > `A/C`: "203, final bearing 270, marshal on the 090, angels 6." > > `A/C`: "204, final bearing 270, marshal on the 090, angels 7." >[!note] Notes > 1. Unlike CASE I recoveries, pilots are required to readback the FB, holding radial, assigned marshal altitude, and expected commence time. > 2. If it is preferred that a wingman commence before the flight lead, the flight lead can check in with Marshal with the wingman's Modex instead. ### Marshal Stack After pilots reach their IAF, they will call established. >[!quote]+ Pilots established at IAF > `A/C`: "203, established angels 6." At this point, Marshal will either clear the aircraft to commence, or assign an expected commence time to the pilot. >[!example]+ Cleared for immediate commence > `[Modex]`, your signal is Charlie, switch approach, button `[#]` > >[!quote] Example > > ==Marshal==: "203, your signal is Charlie, switch approach, button 6" > > `A/C`: "203, commencing." >[!example]+ Assigning commence time > `[Modex]`, expected approach time `[minutes past the hour]`, approach button `[#]` > >[!quote] Example > > `A/C`: "203, established angels 6." > > ==Marshal==: "203, expected approach time 45, approach button 2." > > `A/C`: "203." >[!note] Note on approach times > We do not need to include the hour when assigning approach times. For example if 203 is expected to commence at 2045z, we only need to mention 45. ### Commence When pilots reach their IAF at their expected push times, they will inform Marshal that they are commencing. This is when Marshal will hand them over to their assigned approach button. >[!quote]+ Pilot commencing > `A/C`: "203, commencing." > ==Marshal==: "203, switch approach." > `A/C`: "203." Pilots must inform Marshal if they fail to commence within their 30 second window. >[!quote]+ Pilots failed to reach their 30 second window > `A/C`: "203, commencing, 20 seconds late." > ==Marshal==: "203, switch approach." > `A/C`: "203." ### CASE III Recovery Comms Flow >[!quote]+ > `A/C`: "Rough Rider Marshal, 203, marking mom's 090 50, angels 28, state 7.0." > ==Marshal==: "203, Rough Rider Marshal, radar contact, CASE III recovery, CV-1 approach, mother's altimeter 2992, final bearing 081. 203, marshal on the 261, angels 6, report established." > `A/C`: "203, final bearing 081, marshal on the 261 angels 6." > *203, arrives at IAF* > `A/C`: "203, established angels 6, state 6.2." > ==Marshal==: "203, expected approach time 05, approach button 2" > `A/C`: "203, expected approach time 05, approach button 2." > *203 arrives at IAF at their expected commence time* > `A/C`: "203, commencing, state 5.5." > ==Marshal==: "203, switch approach." > `A/C`: "203." ### CASE II Recovery The CASE II recovery communications will be the same as that of the [[06 - Marshal & Departure Control#Inbound|CASE III recovery.]] With the exception that the BRC will be given instead of the FB. - - - # CASE I Departure During CASE I departures, pilots will report the following: 1. Airborne 2. Mission readiness ### Check-in >[!quote]+ Airborne >`A/C`: "203, airborne." >==Departure==: "203, Rough Rider Marshal, radar contact." ### Mission readiness If pilots are happy with their aircraft's performance, they will report "kilo", otherwise they will communicate with Marshal on their situation. >[!quote]+ Mission readiness > `A/C`: "203, kilo." ### Hand off Once pilots reach 7 DME and Marshal is happy for them to switch frequencies, Marshal will hand them off. >[!example]+ Hand off > "`[Modex]`, leaving my airspace, cleared to switch." > >[!quote] Example > > ==Departure==: "203, leaving my airspace, cleared to switch." ### CASE I Departure Comms Flow >[!quote]+ >`A/C`: "203, airborne." > ==Departure==: "203, Rough Rider Marshal, radar contact." > *203 checks their aircraft's mission readiness* > `A/C`: "203, kilo" > *203 reaches 7 DME* > ==Departure==: "203, leaving my airspace, cleared to switch." > `A/C`: "203, switching." - - - # CASE III Departure During CASE III departures, pilots will give Marshal regular reports: 1. When aircraft are airborne 2. Passing 2500 3. Mission readiness 4. When they start to intercept the 10 DME arc 5. When established on the outbound radial 6. When they first penetrate the cloud ceiling 7. When they are on top of the cloud ceiling ### Check-in After an aircraft is airborne, they will contact Marshal. Marshal will respond with the following: >[!example]+ Aircraft check-in after airborne > "`[Modex]`, `[Carrier Callsign]` Marshal, `[radar/negative]` contact, departure radial `[briefed radial]`." > >[!quote] Example > > `A/C`: "Rough Rider Marshal, 203 airborne." > > ==Departure==: "203, Rough Rider Marshal, radar contact, departure radial 090." ### Passing 2500 feet Aircraft will report that they are passing 2500 feet. >[!quote]+ Passing 2500 feet > `A/C`: "203, passing 2.5" ### Arcing Pilots will report when the start turning to intercept the 10 DME arc. >[!quote]+ Arcing > `A/C`: "203, arcing." ### Established outbound Pilots will report that they are leaving the 10 DME arc on their assigned radial. >[!quote]+ Established Outbound > `A/C`: "203, established outbound." ### Reporting cloud bases Pilots will report the base of the first layer of clouds they penetrate through. >[!quote]+ Reporting cloud bases > `A/C`: "203, popeye angels 7." > `A/C`: "203, on top angels 9.5." ### Hand over Once aircraft are established on their outbound radial, marshal can clear them to switch. >[!quote]+ Hand over > ==Departure==: "203, cleared to switch." > `A/C`: "203, switching." ### CASE III Departure Comms flow >[!quote]+ > `A/C`: "Rough Rider Marshal, 203 airborne." > ==Departure==: "203, Rough Rider Marshal, radar contact, departure radial 090." > `A/C`: "203." > *203 passes angels 2.5 and has a good jet.* > `A/C`: "203, passing 2.5, kilo." > *203 reaches reaches 7 DME and starts to intercept 10 DME arc.* > `A/C`: "203, arcing." > *203 is established on their outbound radial* > `A/C`: "203, established outbound." > ==Departure==: "203, cleared to switch." > `A/C`: "203, switching." - - - # CASE II Departure During CASE II departures, pilots will report the following to Marshal: 1. When pilots are airborne 2. Mission readiness 3. When arcing to intercept 10 DME arc 4. When established on the outbound radial ### CASE II Departure Comms Flow >[!quote]+ > *203 is airbrone* > `A/C`: "Rough Rider Marshal, 203 airborne." > *Marshal looks for 203 on radar* > ==Departure==: "203, Rough Rider Marshal radar contact, departure radial 090." > `A/C`: "203." > *203 has a good jet* > `A/C`: "203, kilo." > *203 reaches 7 DME* > `A/C`: "203, arcing." >