Draft:Training:JFK Sweatbox

JFK Training Files

All of the files necessary to teach Kennedy students – and the proper usage of those files – are described below.

ATCTrainer files:

Multiple files are available for S1 training. The student does not need to progress through all files as long as they demonstrate proficiency and meet the standards for certification. For students requiring multiple training sessions, a different file should be used for each session so they are gain experience with a new set of flight plans. There are no 'easier' or 'harder' flight plans. The difficulty selection only affects the number of aircraft that load in.

On the 13s configuration, 13 L/R + 22L overflow configuration should be used.

JFK - GND - Initial: Easy has a limited selection of aircraft but provides VFR and 1 aircraft for each gate. It is suitable for an introductory session. Medium loads the full file.

JFK - GND - Secondary: This file loads an alternate set of aircraft.

JFK - GND - Supplemental: This file is available for use with students who have had multiple sweatbox sessions and provides an additional set of flight plans.

The following should be discussed and/or demonstrated in the Sweatbox before certification is granted.

General

CRC Setup
Dot commands and common aliases
METAR
View flightplan
Aircraft Select

Theory

Movement vs non-movement areas
PRD usage (vTDLS)
Common amendments
CRAFT
Valid alititudes (NEODD, LUFL, non-RVSM altitudes)
Climb via SID vs Maintain
Equipment suffix
Coordination

General JFK Considerations

Belmont and Coney conditional airspaces
Coordination with LGA when setting up the airport and after any configuration change
ILS 13L vs RNAV Z 13L
VFR operations
NY Class B airspace
NY Heli routes, Skyline Route

Clearance Delivery

Determine configuration using Runway Selection table
Simulate briefing
Must run 4s, 13's, and 31's configurations, including at least 1 aircraft for each gate on the 13 and 31 configurations
When changing configuration, aircraft still at the ramp should be re-cleared and the new configuration should be coordinated with LGA.
For 31L/R configuration include SKORR5, DEEZZ5 and JFK5 climbs including Idlewild climb
At least 1 VFR flight following and 1 VFR non-FF
Concorde
Voice clearance must be demonstrated with proper phraseology
Attention to pilot readbacks and correction of readback errors.
PDC use: The student should give at least 1 PDC to demonstrates that they are able to issue PDCs

Ground

Taxiway ownership per config
Runway crossings
When changing configuration, coordinate which aircraft will be the last departures and arrivals on the previous configuration
Transponder Mode C and correct squawk set
Taxi at least 1 aircraft to each departure runway (including 31R / 13L)
Proper phraseology must be used
Standard Taxiway A and B flow
Direction of turn onto taxiway A or B
Scan, conflict avoidance
Sequencing should be discussed (why / how / where) but does not need to be demonstrated
Prioritization of tasks and frequency management

ATCTrainer files:

JFK - TWR - 4s

JFK - TWR - 31s

JFK - TWR - 13s+22L

Scripting within each file manages aircraft tracking, handoffs and pathing into JFK TWR airspace. All 3 files must be completed for certification.

Easy, Medium and Hard difficulties are included in each file.

Easy provides limited aircraft for an introductory session.

Hard should be used for certification.

Medium is available for students who require a stepwise progression between Easy and Hard.

Certification

The following should be discussed and/or demonstrated in the Sweatbox before certification is granted.

Theory

JFK Tower airspace, including adjacent sectors
NY Class B airspace
Management of VFR traffic along the shoreline
NY Heli routes
NY22 operations
Techniques for managing VFR traffic
Traffic call phraseology
Wake turbulence separation
MIT requirements
Same runway separation and the application of diverging headings
Intersection departures
Taxiway ownership and parallel runway crossing instructions
Overflow operations
Management and coordination of missed approach or go arounds

Practical

It is not required to run all aircraft as long as the competencies are demonstrated.

Simulate briefing
Proper phraseology must be demonstrated consistently
Proper scan and airspace awareness
VFR departures, arrivals and at least 1 VFR transition should be included
At least 1 Missed Approach should be included
On the 31s configuration, all aircraft holding short 31R must depart. It is not required to depart all aircraft holding short 31L
On the 13s configuration, efficient use of same runway separation should be demonstrated.
On the 4s configuration, arriving aircraft must be given taxi instructions and cross Runway 4L. The student should be able to efficiently cross several aircraft at once using multiple taxiways.
All departures from JFK are automatically tracked by Departure. To drop the track (for VFR), use the command drop.
For N314PD inbound NY22, use the command land @ny22

Students are expected to have studied the JFK SOP and watched the JFK TRACON CBT videos prior to their first session.

Theory

Airspace Awareness and key altitude blocks
Adjacent sectors
Flash the tags early
Liberty Departure
Approach flows and Pre-arranged Coordination
Scratchpads
MIT requirements
Creating space (vectors, speed control)
Positive separation
ISP departures to North exits
LGA departures to DIXIE, WHITE, SHIPP, WAVEY
V16, T224, V1 traffic
Go arounds
FRG arrivals

Direct handoffs to ZBW when Liberty not covered
- East gate exits: 11-17k, on course
- BDL: 10k
Direct handoffs to ZDC when N66 not covered
- WHITE Q409: FL240, on course
- WAVEY EMJAY: Q167 - FL230, on course

Practical

The student should sign in as Kennedy Departure. The scenarios should be completed in the order listed. There is a stepwise progression of difficulty. Include in the training note which scenarios have been completed.

Each scenario is scripted. All airborne aircraft will be tracked automatically by the appropriate sector and handed off or pointed out when appropriate. If the scripting fails, the following commands will work:

AAL121 track N2K -> aircraft will be tracked by ROBER
AAL121 ho -> will hand off to the student
AAL121 po N2J -> point out to Kennedy Departure
If the student points out, you can acknowledge the point out with the command po
If the student hands off a track, it should automatically be accepted after a few seconds. If this does not work, verbally coordinate the handoff and delete the track.

31 L/R Configuration

ATCTrainer file: JFK - DEP - 31s
For the handoffs from LGA DEP, ensure positive separation and proper MIT to the respective fixes.
PACA for Southwest departures 11k. LENDY is responsible for separation

13 L/R + 22L Overflow Configuration

ATC Trainer file: JFK - DEP - 13s

It should be noted and briefed that the 13L/R + 22L overflow configuration is used and aircraft will depart on the modified headings.
- Prop departures to North or East will depart heading 140
- Jet departures to North or East will depart heading 155
- All other departures will fly the usual headings.
Inbound traffic for RNAV X 22L will be pointed out by APP.
PACA for LENDY arrivals
For the handoffs from LGA DEP, ensure positive separation and proper MIT to the respective fixes.
This scenario includes an overflight on T224

4 L/R Configuration

ATCTrainer file: JFK - DEP - 4s
LGA owns the Belmont and Coney airspace.
PACA for LENDY arrivals
For the handoffs from LGA DEP, ensure positive separation and proper MIT to the respective fixes.
This scenario includes VFR FF through the airspace and an overflight on T224
This scenario includes an FRG arrival via V1

22 L/R Configuration

ATCTrainer file: JFK - DEP - 22s
LGA owns CONEY airspace
For the handoffs from LGA DEP, ensure positive separation and proper MIT to the respective fixes.
PACA for Southwest departures 11k. LENDY is responsible for separation.
This scenario includes VFR FF through the airspace and an overflight on T224.
This scenario includes an FRG arrival via V1

Students are expected to have studied the JFK SOP and watched the JFK TRACON CBT videos prior to their first session.

Theory

Airspace Awareness (Vertical and lateral boundaries, adjacent sectors)
Satellite airspace
General overview of the arrival flows
Prearranged coordination and point outs
Merging the flows, making a plan
Creating and closing gaps (why, where, how)
Sequencing of aircraft (for efficiency, group heavies when you can)
Speed control
Positive separation
LOAs and control for turns
RECAT Wake turbulence separation awareness
Final box management
- PTACs
- Desired spacing on Final (4 miles in absence of wake requirements)
- Parallel approaches,
  - Required stagger (instrument, visual)
  - Vertical separation
Management of satellite arrivals
Coordination - controllers should be encouraged to ask for what they need

General advice for students:

Planning the sequence early is the key to success. If LENDY, CAMRN and ROBER aircraft always fly the path on the ‘Arrival Flow Diagram’, the final box will become overly congested and difficult to manage.
‘Follow the leader’ will not always work and aircraft will need to be given headings that create or close gaps.
LOA control for turns can help with spacing.
Group heavies together for maximum efficiency.
Speed control is critical.
Tightening up gaps to create a more efficient sequence will free up airspace. Sometimes making a larger gap and putting another aircraft in that space is the most efficient way to tighten up the sequence.
Be aware of descending aircraft through the altitude of other aircraft. Ensure positive separation.
For the LENDY / CAMRN merge, encourage the student to identify their sequence, including whether they are trying for tight spacing or gaps. Encourage them to assign headings for the CAMRN or LENDY flow to accomplish that objective. A similar process should occur when merging the LENDY/CAMRN flow with the ROBER flow.
Use small vectors to refine spacing.
Stay within your airspace.

Practical

ATCTrainer files:

JFK - APP - 4s
JFK - APP - 31s
JFK - APP - 22s Combined (1)
JFK - APP - 22s Feeder (2)
JFK - APP - 22s Final (3)

The scenarios should be run the in the order above. There is a stepwise progression in difficulty and complexity. Students should be encouraged to establish 4 MIT on final (in the absence of wake turbulence requirements). This separation is not a requirement for certification but should be a goal. Most of the scenarios have an Easy and a Medium version. The Easy version is an abbreviated version of the file, meant to introduce the concepts and the flows before moving on to the full Medium file. For certification, the scenario should be completed on Medium. Specify in the training note which files have been run during the session.

At the beginning of the scenario, wait for the beacon codes to be assigned by vNAS, then the student should track all aircraft visible on the scope. The remainder of the scenario is scripted. All aircraft should automatically be tracked by the appropriate controller, fly the correct path, and get handed off to student at the appropriate time. If the scripting fails, the following commands will work:
AAL121 track N2K -> aircraft will be tracked by ROBER
AAL121 ho -> will hand off to the student
AAL121 po N2J -> point out to Kennedy Departure
If the student points out, you can acknowledge the point out with the command po.
If the student hands off a track, it should automatically be accepted after a few seconds. If this does not work, verbally coordinate the handoff and delete the track.

Students can use reasonable discretion to assign aircraft to the second runway. When the aircraft are on final for the second runway, Mentors should assess the whether the required separation is present and that the decision is appropriate given the traffic flow. The student should not use the 2nd runway to bail themselves out due to poor planning.
Some aircraft may go around instead of landing. These should be deleted. Management of go-arounds is not required.

4 L/R Configuration

The ATCTrainer file JFK- APP - 4s should be used.

Brief:

The student should sign in as ROBER. They will be working the combined APP sectors. At the beginning of the scenario, wait for the beacon codes to be assigned by vNAS, then the student should track all visible aircraft.
LGA owns the Coney airspace.
Aircraft already in the airspace are on the arrivals:
- SKW3910 heading 130, level at 13000
- EJA798 is descending to 16000 but has not been given an approach to expect yet.
- JBU8302 departing CAMRN heading 040
- AAL121 descending to 5000

ATCTrainer Approach Clearance Commands

JF 4L -> Join final 4L, will not descend until cleared for the approach
CAPP I4R, CAPP I4L
Visual Approaches EF 4R, EF 4L
FRG RNAV 1 = CAPP R01

31s L/R Configuration

The ATCTrainer file JFK - APP - 31s should be used.

Brief:

The student should sign on as ROBER. They wiill be working the combined APP sectors. The student should track all aircraft visible at the start of the session. Subsequent aircraft will be handed off automatically.
Aircraft in the airspace:
- EDV5011 heading 180, descending to 13000
- DAL1064 heading 180, descending to 16000
- SKW3712 departing CAMRN heading 040
- SIA26 descending to 9000 on the arrival

ATCTrainer Approach Clearance Commands

CAPP I31R, CAPP I31L
Visual approaches EF 31R, EF 31L

22's L/R Configuration (3 files):

JFK - APP - 22s Combined (1)

Brief:

The student is working the combined APP sector. The should sign in as ROBER. At the beginning of the session, wait for the beacon codes to be assigned by vNAS, then the student should track all visible aircraft.
LGA owns the Coney airspace

ATCTrainer Approach Clearance Commands

CAPP I22L, CAPP I22R
Visual approaches EF 22L, EF 22R

JFK - APP - 22s Feeder (2)

Brief:

The student should sign in as CAMRN. They will be working LENDY/CAMRN and feeding Final.
The feed from ZNY will be at 250 kts over LENDY and CAMRN. This should be fed to Kennedy Final Vector (2A) at 4000', 210 kts, 5 MIT.
RPA4587 flying heading 180, descending 16000
JBU670 flying heading 180, descending 13000
EDV5429 departing CAMRN heading 040

JFK - APP - 22s Final (3)

Brief:

The student should sign in as Kennedy Final Vector. The initial aircraft will be tracked by adjacent sectors and handed off automatically.
The feeds from ROBER and CAMRN will be at 210 kts.
Final has control for turns on contact.
The student can use reasonable discretion to assign aircraft to the second runway. When the aircraft are on final for the second runway, Mentors should assess the whether the required separation is present and that the decision is appropriate given the traffic flow.
Ensure aircraft stay within the airspace.

ATCTrainer Approach Clearance Commands

CAPP I22L, CAPP I22R
Visual approaches EF 22L, EF 22R

After completion of all sweatbox files, a brief review of ISP airspace and ISP traffic flows should be conducted and JFK APP certification granted.

ISP Notes

Airspace overview. Due to altitude constraints, Rwy 24 departures should make the initial turn northbound.
North exits should pass through the JFK gate at 8000, handoff to JFK DEP.
East exits should pass through the East gate on appropriate heading, handoff to LIB (or NY CTR if LIB not staffed). If LIB uncovered, climb to 17000, direct their fix, handoff to BOS CTR.
Traffic on V1, V16, T224 westbound at 6000, handoff to JFK DEP. Aircraft departing ISP can be vectored onto the airway rather than joining at CCC.
Aircraft inbound JFK/FRG via DPK: JFK APP should point out. Acceptance of pointout gives JFK APP control for descent to 4000. ISP responsible for separation.
BOUNO# arrival into HPN. Handoff comes from BOS CTR. Descend through your airspace. Pointout to ROBER. Coordinate the approach in use with HAARP (some approaches begin in your airspace). Handoff early. HAARP will clear for the apprach.
Satellite fields: Be aware initial fixes for RNAV 20 (HVN) are in BDL APP airspace and should be pointed out.