Updated: 2024-01-13 --- %% >[!todo] >Initial >Pattern rules >Deck operations >LSO coordination %% # Tower As per vCSG-3 SOPs, Tower is in control of the CCA, and will also act as the "Deck Boss", whom is in charge of movement on the deck. Tower will be responsible for the following: - CASE I & II Departure and Recoveries - CASE III Departures - Flight Deck movement ## Deck layout ![[Flight Deck Layout.png]] *Image of the flight deck layout.* --- ## CASE I & II Recovery Communications with Tower during CASE I and II recoveries will be identical. Pilots will make the following reports to Tower: - On initial - In the break - Abeam ### Initial Pilots will report to tower once they are on the 3NM initial. >[!quote]+ 3NM Initial > `A/C`: "Rough Rider Tower, 203 3NM initial." Tower will then respond with the following: >[!example]+ Contact > "`[Modex]`, `[Carrier Callsign]` Tower, contact." > >[!quote] Example > > ==Marshal==: "203, Rough Rider Tower, contact." > >[!note] > We are saying "contact" in place of "radar contact" as we are simulating tower having visual contact with the aircraft on initial. ### In the break Pilots will report "in the break" to tower as they start breaking. >[!quote]+ In the break > `A/C`: "203, in the break." ### Abeam Pilots will report "abeam" as they are abeam the LSO station. >[!quote]+ Abeam > `A/C`: "203, abeam." ### Waveoff If tower deems that the aircraft in the groove is unsafe, they can instruct pilots to waveoff. >[!example]+ Waveoff > "`[Modex]`, waveoff." > >[!quote] Example > > ==Tower==: "203, waveoff." > > `A/C`: "203." >[!note] > Tower has a higher authority than the LSO. Therefore if Tower instructs pilots to waveoff but the LSO does not, the pilot must waveoff and enter the bolter pattern. ### Extend upwind Pilots may need to extend their upwind leg to give priority to others. For example, a pilot in the bolter pattern will give priority to those waiting to break. >[!example]+ Extend Upwind > "`[Modex]`, extend upwind." > >[!quote] Example > > ==Tower==: "203, extend upwind." > > `A/C`: "203." ### Spin it If the pattern is full, aircraft on initial will be instructed to spin it. >[!example]+ Spin it > "`[Modex]`, spin it." > >[!quote] Example > > ==Tower==: "203, spin it." > > `A/C`: "203." ### Depart and re-enter There may be many reasons for a depart and re-enter. See [[03 - Case I Stack and Pattern#Depart and Re-enter|here]] for more information >[!example]+ Depart and re-enter > "`[Modex]`, depart and re-enter." > >[!quote] Example > > ==Tower==: "203, depart and re-enter." > > `A/C`: "203." ### Delta Easy Delta Easy is a way to fix certain pilot errors on the downwind leg. >[!example]+ Delta Easy > "`[Modex]`, Delta Easy." > >[!quote] Example > > ==Tower==: "203, Delta Easy." > > `A/C`: "203." >[!danger]+ Important > Pilots cannot be instructed to extend downwind due to safety of flight. ### CASE I Recovery Comms Flow >[!quote]+ Example 1 > *Pilot reaches 3NM initial* > `A/C`: "Rough Rider Tower, 203 3NM initial." > ==Tower==: "203, tower contact." > *Pilot reaches break point* > `A/C`: "203, in the break." > *Pilot is abeam the carrier* > `A/C`: "203, abeam." >[!quote]+ Example 2 >*Pilot reaches 3NM initial* > `A/C`: "Rough Rider Tower, 203 3NM initial." > ==Tower==: "203, tower contact." > *Pattern becomes full because of bolters* > ==Tower==: "203, spin it." > `A/C`: "203." > *203 reaches the 3NM initial after exiting the spin pattern.* > `A/C`: "203, 3NM initial." > *203 reaches break point* > `A/C`: "203, in the break." > *203 is abeam the carrier.* > `A/C`: "203, abeam." - - - ## CASE I Departure As stated above, the Tower controller will be in charge of flight deck movement. Deck Boss will provide pilots looking to launch the following information during CASE I departures: - Mother's altimeter - BRC ### Taxi to Catapult Pilots looking to launch from the carrier will contact Deck Boss. >[!quote]+ Request Taxi to Catapult > `A/C`: "Rough Rider Deck Boss, 203, at elevator 1, request taxi to cat." Deck boss will then respond with the following: >[!example]+ Taxi to Catapult > "`[Modex]`, `[Carrier Callsign]` Deck Boss, mother's altimeter `[QNH]`, BRC `[BRC]`, cleared to taxi to CAT `[#]`. " > >[!quote] Example > > ==Deck Boss==: "203, Rough Rider Deck Boss, mother's altimeter 2992, BRC 090, cleared to taxi to CAT 1." > > `A/C`: "203, altimeter 2992, BRC 090, cleared to taxi to CAT 1." If all available CATs are taken, pilot can be instructed to hold short of a CAT. >[!example]+ Hold Short > "`[Modex]`, `[Carrier Callsign]` Deck Boss, mother's altimeter `[QNH]`, BRC `[BRC]`, hold short CAT `[#]`." > >[!quote] Example > > ==Deck Boss==: "203, Rough Rider Deck Boss, mother's altimeter 2992, BRC 090, hold short CAT 1." > > `A/C`: "203, altimeter 2992, BRC 090, hold short CAT 1." > ### Launching Pilots will request launch when they are ready. >[!quote]+ Request launch > `A/C`: "Rough Rider Deck Boss, 203 request launch." Deck Boss will either clear the pilot for launch if there is enough separation, or instruct them to hold position. >[!example]+ Cleared to launch > "`[Modex]`, cleared to launch, CAT `[#]`, switch Marshal, button `[#]`." > >[!quote] Example > > ==Deck Boss==: "203, cleared to launch, CAT 1, switch Marshal, button 3." > > `A/C`: "203." >[!example]+ Hold Position > "`[Modex]`, hold position." > >[!quote] Example > > ==Deck Boss==: "203, hold position." > > `A/C`: "203." > ### CASE I Departure Comms Flow >[!quote]+ Example 1 > `A/C`: "Rough Rider Deck Boss, 203, at elevator 1, request taxi to CAT." > ==Deck Boss==: "203, Rough Rider Deck Boss, mother's altimeter 2992, BRC 090, cleared to taxi to CAT 1." > `A/C`: "203, altimeter 2992, BRC 090, cleared to taxi to CAT 1." > *203 is ready for launch* > `A/C`: "Rough Rider Deck Boss, 203 request launch." > ==Deck Boss==: "203, cleared to launch CAT 1, switch Marshal, button 3." > `A/C`: "203." >[!quote]+ Example 2 > `A/C`: "Rough Rider Deck Boss, 203, at elevator 1, request taxi to CAT." > ==Deck Boss==: "203, Rough Rider Deck Boss, mother's altimeter 2992, BRC 090, cleared to taxi and hold short CAT 1." > `A/C`: "203, altimeter 2992, BRC 090, cleared to taxi and hold short CAT 1." > *203, holds short of CAT 1 and will take it when available.* > `A/C`: "Rough Rider Deck Boss, 203 request launch." > ==Deck Boss==: "203, cleared to launch CAT 1, switch Marshal, button 3." > `A/C`: "203." - - - ## CASE II & III Departures Flight deck movement is identical to what is mentioned under the [[07 - Tower & Approach Control#CASE I Departure|CASE I Departures]] section. The only difference is when clearing aircraft to launch: >[!example]+ Cleared to Launch CASE II/III Departures > "`[Modex]`, CASE `[II/III]` departure, cleared to launch CAT `[#]`, switch Marshal button `[#]`" > >[!quote] Example > > ==Deck Boss==: "203, CASE III departure, cleared to launch CAT 1, switch Marshal button 3." > > `A/C`: "203." - - - # Approach Approach will be responsible for the following: - CASE II & III approaches ## CASE III Approach ### Check in After pilots start commencing in accordance to their push time, they will check in with approach. >[!quote] Check-in > `A/C`: "Rough Rider Approach, 203 checking in." Approach will look for the pilot, and will respond accordingly. >[!example]+ Initial Check-In > "`[Modex]`, `[Carrier Callsign]` Approach, radar contact, altimeter `[QNH]`, final bearing `[FB]`." > > or > > "`[Modex]`, `[Carrier Callsign]` Approach, negative contact. `[discuss next steps]`." > >[!quote] Radar Contact > > ==Approach==:"203, Rough Rider Approach, radar contact, altimeter 2992, final bearing 081." > > `A/C`: "203." > > >[!quote] Negative Contact > >==Approach==: "203, Rough Rider Approach, negative contact, ident." > >`A/C`: "203." ### Platform When pilots reach 5000 feet, they will call platform >[!quote]+ Pilot reaches platform > `A/C`: "203, platform." ### ACLS/ICLS/TACAN/Needles/Bullseye/Father Once aircraft are within 6 DME of the aircraft, they should start seeing needles on their HUD. >[!example]+ ACLS lock on at 6 miles >"`[Modex]` `[#]` miles, ACLS lock on, say needles." > >[!quote] Example >==Approach==: "203, 6 miles ACLS lock on, say needles." >`A/C`: "203, Up and on." >*Approach checks if 203 is up and on as mentioned* >==Approach==: "203 concur, fly mode 2." In case pilots do not have ACLS information, Approach will ask pilots for their ICLS. > [!example]+ ACLS Sour > "`[Modex]`, say bullseye." > >[!quote] Example > >==Marshal==: "203, 6 miles ACLS lock on, say needles." > >`A/C`: "Needles sour." > >==Marshal==: "203, say bullseye" > >`A/C`: "203, Up and on" > >==Marshal==: "203, fly bullseye" If all else fails, Approach will instruct pilots to fly TACAN. >[!example]+ ACLS & ICLS Sour > "`[Modex]`, fly father." > >[!quote] Example > >==Marshal==: "203, 6 miles ACLS lock on, say needles." > >`A/C`: "Needles sour." > >==Marshal==: "203, say bullseye" > >`A/C`: "203, bullseye sour" > >==Marshal==: "203, fly father." > > At this point, Approach will give DME callouts every mile. >[!example]+ DME Callouts > "`[Modex]`, `[#]` miles." > >[!quote] Example > > ==Approach==: "203, 5 miles" > > At 3 miles, Approach will inform the pilot that they are approaching glideslope. >[!example]+ Approaching glideslope > "`[Modex]`, 3 miles, approaching tipover." > >[!quote] Example > >==Approach==: "203, 3 miles, approaching tipover." Depending on the type of approach used, Approach should be aware of the respective minima. | Approach Type | DA - Dist | | ---- | ---- | | ACLS | 260 - N/A | | ICLS | 360 - 3/4 | | TACAN | 600 - 1-1/4 | *Table of minima. [[CV-1 Approach.png|Click for CV-1 Approach plate]]* >[!example]+ Approaching Minima > "`[Modex]`, approaching minima." > >[!quote] Example > > ==Approach==: "203, approaching minima." > > >[!note] >The call does not need to be made if the pilot calls the ball before they reach minima, or if LSO is available. ### CASE III Approach Comms Flow >[!quote]+ Example > `A/C`: "Rough Rider Approach, 203 checking in." > ==Approach==: "203, Rough Rider Approach, radar contact, altimeter 2992, final bearing 081." > *203 reaches platform altitude* > `A/C`: "203, platform." > *203 reaches 6 DME* > ==Approach==: "203, 6 miles, ACLS lock on, say needles." > `A/C`: "203, up and on." > *Approach verifies up and on with their information* > ==Approach==: "203, concur, fly mode 2." > *203 reaches 5 miles* > ==Approach==: "203, 5 miles." > *203 reaches 4 miles* > ==Approach==: "203, 4 miles." > *203 reaches 3 miles* > ==Approach==: "203, 3 miles, approaching tipover." > *203 reaches 2 miles* > ==Approach==: "203, 2 miles." > *203 reaches 1 mile* > ==Approach==: "203, 1 mile." > *203 approaches ACLS minima* > ==Approach==: "203, 3/4 of a mile, call the ball." > `A/C`: "203, hornet ball, 6.5." > ==Approach==: "Roger ball." > - - - ## CASE II Approach CASE II Approach communications are similar to a CASE III approach, except pilots get handed off to Tower when they report the carrier in sight. ### CASE II Comms Flow >[!quote]+ Example > `A/C`: "Rough Rider Approach, 203, checking in." > ==Approach==: "203, Rough Rider Approach, radar contact, altimeter 2992, BRC 090." > `A/C`: "203." > *203 reaches platform* > `A/C`: "203, platform." > *203 reaches 1200 feet and will attempt to look for the carrier* > `A/C`: "203 see you at 10." > ==Approach==: "203, switch tower, button 3." > `A/C`: "203."