JBCAS (KNAV) ATC Frequencies

ATIS: 127.075

AWOS: 122.15

Ground: 121.9

Tower: 131.9

CTAF/UNICOM: 124.755

Base OPS 133.855

Squadron OPS

Prattsville AFB (KPVS) Comms

ASOS: 126.725

ATIS: 122.975

Ground: 134.125

Tower: 130.445

UNICOM: 136.7

Base OPS 132.000

Ramona Live Firing Range

JTAC: 126.5

UNICOM: 133.2

JBCAS / PRATTSVILLE AFB — ATC PROCEDURES & COMMUNICATION GUIDANCE

(For MSFS 2024: In-Sim ATC, SayIntentions AI, and Online ATC Platforms)

1. General Overview

JBCAS and Prattsville AFB are fully functional inside MSFS 2024, but they are not part of the simulator’s default airport database. Because of this:

• In-Sim ATC will recognize both airfields normally (Ground, Tower, CTAF, ASIS, etc).
  
  

• SayIntentions and online networks like VATSIM will not.
  They do not detect custom scenery, custom ICAOs, or custom nav facilities.
  
  

For this reason, aircrews should follow the procedures below to ensure smooth transitions between base operations and real-world-style ATC services.

2. Departure Procedures From JBCAS or Prattsville AFB

A. Use In-Sim ATC While On the Ground

• Contact JBCAS Ground or Prattsville Ground as normal for:
  
  

  • Clearance (IFR or VFR)
    
    

  • Taxi instructions
    
    

  • Runway assignment
    
    

• Switch to Tower when instructed.
  
  

B. After Takeoff

Once airborne, simulator ATC will handoff to the regional controller just like at a real base.

• Expect handoff to Little Rock Approach: 119.5
  
  

• Depending on route/altitude, expect further handoff to Memphis Center.
  
  

This portion works normally because MSFS uses regional airspace boundaries rather than airport data.

3. Enroute ATC Using SayIntentions or VATSIM-Style Tools

SayIntentions/VATSIM will:

• Provide vectors
  
  

• Provide traffic advisories
  
  

• Provide IFR routing support
  
  

…but they cannot:

• Recognize “JBCAS,” “Prattsville AFB,” or their ICAO identifiers
  
  

• Recognize custom runway data
  
  

• Assign SID/STAR or approaches associated with custom airports
  
  

Therefore, pilots should treat JBCAS and Prattsville as off-network fields, using the nearest real-world airport as a reference.

4. Arrival Procedures Back to JBCAS or Prattsville AFB

A. Navigation to the Field

Because SayIntentions and VATSIM don't know the airbase location, pilots should use the real landmark:

19AR – Naylor Field

• Located approximately 5 NM south of JBCAS
  
  

• Serves as a reliable reference point for inbound navigation
  
  

Once established over or north of Naylor Field, pilots may:

B. Cancel Flight Following / IFR

• Cancel IFR or flight following with SayIntentions or Memphis Center
  
  

• Squawk 1200
  
  

• Resume self-navigation to the base
  
  

C. Switch to In-Sim ATC for Pattern Entry

• Tune JBCAS Tower or Prattsville Tower using the standard in-sim ATC menu
  
  

• Request pattern entry, landing clearance, or straight-in as instructed
  
  

• After clearing the runway, contact Ground for taxi to parking
  
  

The simulator ATC handles these final phases correctly because they’re local to the scenery package.

5. Summary of Preferred ATC Workflow

DEPARTING

1. Use in-sim Ground/Tower at JBCAS or Prattsville.
   
   

2. After takeoff, follow Approach/Center via default MSFS ATC.
   
   

3. Optionally switch to SayIntentions/VATSIM for enroute handling.
   
   

RETURNING

1. Navigate using 19AR Naylor Field as the initial fix.
   
   

2. Cancel external ATC (IFR, Flight Following, SayIntentions, VATSIM).
   
   

3. Squawk 1200 and switch back to in-sim ATC.
   
   

4. Use Tower/Ground for final approach, landing, and taxi.