IFR Communications
Introduction to IFR, clearance procedures, position reporting, and building on VFR communications from Block 1
OBJECTIVE
Provide trainees with a comprehensive understanding of Instrument Flight Rules (IFR) communications, including what IFR is and why it's used, standard phraseology, obtaining clearances (including pop-up IFR), mandatory position reports, interactions with air traffic control (ATC) across various flight phases, emergency protocols, and lost communications procedures, to ensure safe and effective radio operations in the T-38 Talon during instrument conditions, building on foundational VFR communications from Block 1.
CONTENT
What is IFR and Why Do We Use It?
Instrument Flight Rules (IFR) govern flight operations when pilots cannot rely solely on outside visual references. Understanding IFR is essential for military pilots who must operate in all weather conditions.
IFR DEFINED
Instrument Flight Rules (IFR) are regulations and procedures for flying aircraft by reference to cockpit instruments alone, without visual reference to the ground or horizon. IFR flights operate under positive ATC control with assigned routes, altitudes, and clearances.
WHEN IS IFR REQUIRED OR USED?
- • Instrument Meteorological Conditions (IMC): When visibility or cloud clearances are below VFR minimums (clouds, fog, rain, haze)
- • Night operations: Many military operations require IFR at night for safety
- • High-altitude flight: Class A airspace (FL180+) requires IFR regardless of weather
- • Mission requirements: Tactical operations often mandate IFR for predictability and ATC services
- • Pilot preference: Even in VMC, pilots may file IFR for traffic separation, workload reduction, or flight following
IFR vs VFR: KEY DIFFERENCES
| Aspect | VFR | IFR |
|---|---|---|
| Flight Plan | Optional (recommended) | Required |
| ATC Clearance | Not required (except in certain airspace) | Required before departure |
| Separation | Pilot responsibility ("see and avoid") | ATC provides separation |
| Weather Minimums | Must maintain VFR conditions | Can fly in IMC |
| Altitude | Pilot selects (with hemispheric rules) | ATC assigned |
| Position Reports | Not required | Required at compulsory points (non-radar) |
| Communications | Advisory/informational | Mandatory clearances & readbacks |
IFR Phraseology and Standards Review
- • FAA/DoD standards: Reinforcement of ICAO phonetic alphabet for clear spelling (e.g., Tango-Three-Eight for T-38) and basic etiquette like concise transmissions and proper acknowledgments ("Roger," "Wilco," "Affirm").
- • VFR vs IFR differences: Emphasis on clearances, readbacks, and mandatory reporting points to maintain separation in IMC.
- • T-38 radio setups: Overview of UHF/VHF frequencies at KSPS, including clearance delivery (e.g., 121.8 MHz) and integration with onboard comm systems.
IFR READBACK REQUIREMENTS
You must read back the following:
- • Clearance limits and route
- • Altitudes and altitude restrictions
- • Headings
- • Speeds
- • Runway assignments (takeoff and landing)
- • Transponder codes
- • Frequency changes
- • Hold short instructions
Obtaining a Pre-Filed IFR Clearance
Before you can fly IFR, you need a clearance from ATC. This lesson covers how to pick up a clearance that has already been filed. Flight plan filing itself is covered in B2002.
CLEARANCE PICKUP SEQUENCE
Listen to ATIS
Get current weather, runway, and information code (Alpha, Bravo, etc.)
Contact Clearance Delivery
State callsign, aircraft type, destination, and that you have ATIS
Copy the Clearance (CRAFT)
Write it down! Clearance, Route, Altitude, Frequency, Transponder
Read Back the Clearance
Full readback required - ATC will correct any errors
EXAMPLE: CLEARANCE REQUEST (Pre-Filed)
PILOT:
"Sheppard Clearance, BULLY54, T-38, IFR to Tinker on file, ready to copy."
ATC:
"BULLY54, Sheppard Clearance, cleared to Tinker Airport as filed. Climb and maintain 4,000, expect flight level 350 one-zero minutes after departure. Departure frequency 124.0, squawk 4521."
PILOT READBACK:
"Cleared to Tinker as filed. Climb and maintain 4,000, expect flight level 350 one-zero minutes after. Departure 124.0, squawk 4521, BULLY54."
ATC:
"BULLY54, readback correct. Contact ground 121.7 when ready to taxi."
CRAFT CLEARANCE FORMAT
C - Clearance Limit: Usually your destination airport
R - Route: SID, airways, fixes, transitions
A - Altitude: Initial + expected final altitude
F - Frequency: Departure control frequency
T - Transponder: Assigned squawk code
Picking Up Clearance on VATSIM
On VATSIM, the process is similar to real-world operations. Your flight plan should be filed through your pilot client (vPilot, xPilot, etc.) before contacting ATC.
VATSIM IFR CLEARANCE PROCESS
- 1. File your flight plan in your pilot client before connecting or shortly after
- 2. Check who's online - Look for Clearance Delivery, Ground, Tower, or Center
- 3. Contact the appropriate controller (see priority below)
- 4. Request your clearance the same way as real-world
- 5. Read back your clearance completely
WHO DO I CONTACT FOR CLEARANCE?
Contact the lowest controller in the hierarchy who is online:
EXAMPLE: VATSIM CLEARANCE (Only Center Online)
PILOT:
"Fort Worth Center, BULLY54 at Sheppard, IFR to Tinker on file, ready to copy."
ATC:
"BULLY54, Fort Worth Center, cleared to Tinker as filed. Climb and maintain 5,000, expect flight level 350 one-zero minutes after departure. Departure frequency 124.0, squawk 4532."
No ATC Online? On VATSIM, if no controller is online, you fly UNICOM (122.800). Depart VFR-style, then pick up your IFR clearance in the air when you reach controlled airspace or contact Center. File your flight plan anyway - it helps controllers when they log on!
Pop-Up IFR Clearance
A "pop-up" IFR clearance is an IFR clearance requested while already airborne, typically when you didn't file beforehand or weather deteriorates unexpectedly. This is a critical skill for military pilots.
WHEN TO REQUEST POP-UP IFR
- • Weather deteriorating below VFR minimums
- • Need to enter IMC (clouds) unexpectedly
- • Want IFR services for traffic separation
- • Returning from a training area and want an instrument approach
- • Diverting to an alternate and need IFR routing
POP-UP IFR REQUEST FORMAT
Include the following in your request:
- • Callsign and aircraft type
- • Current position (fix, radial/DME, or lat/long)
- • Current altitude
- • Destination
- • Requested altitude (optional)
- • Type of approach (if requesting)
EXAMPLE: POP-UP IFR (Weather Deteriorating)
PILOT:
"Fort Worth Center, BULLY54, T-38, request pop-up IFR to Sheppard."
ATC:
"BULLY54, Fort Worth Center, go ahead with your request."
PILOT:
"BULLY54 is 25 miles northwest of Sheppard, 8,000 feet, requesting IFR clearance to Sheppard for the ILS runway 15R."
ATC:
"BULLY54, cleared to Sheppard Airport via direct, descend and maintain 6,000. Expect vectors for the ILS runway 15R. Squawk 4507."
PILOT READBACK:
"Cleared to Sheppard direct, descend and maintain 6,000, expect vectors ILS 15R, squawk 4507, BULLY54."
EXAMPLE: POP-UP IFR (Returning from MOA)
PILOT:
"Sheppard Approach, BULLY54, flight of two T-38s, 15 miles south of ARNIE at 15,000, request pop-up IFR for recovery to Sheppard."
ATC:
"BULLY54 flight, Sheppard Approach, squawk 4521, say intentions."
PILOT:
"BULLY54 flight, squawking 4521, request radar vectors for the ILS runway 15R, full stop."
ATC:
"BULLY54 flight, radar contact, 15 miles south of Sheppard. Cleared to Sheppard Airport via direct, descend and maintain 5,000, expect vectors ILS runway 15R."
Mandatory Position Reports
Under IFR, pilots are required to make position reports at certain points. Understanding when and how to make these reports is essential for safe instrument operations.
WHEN ARE POSITION REPORTS REQUIRED?
In Radar Contact
Position reports are NOT required when ATC advises "radar contact" - ATC tracks your position on radar.
Non-Radar Environment
Position reports ARE required at all compulsory reporting points when not in radar contact (oceanic, remote areas, radar failure).
COMPULSORY REPORTING POINTS
On charts, compulsory reporting points are shown as solid triangles (▲). Non-compulsory points are shown as open triangles (△).
Compulsory
Must report (non-radar)
Non-Compulsory
Report only if requested
REPORTS REQUIRED REGARDLESS OF RADAR
Even in radar contact, you must report:
- • Vacating an altitude - "BULLY54, leaving flight level 350 for flight level 240"
- • Reaching an assigned altitude - "BULLY54, level flight level 240"
- • Unable to climb/descend at 500 fpm - Report rate capability
- • Missed approach - "BULLY54, missed approach"
- • Change in TAS - Report if ±5% or 10 knots (whichever is greater)
- • Loss of navigation/comm capability
- • Encountering weather - Unforecast conditions affecting safety
- • Safety of flight information - Any hazard to flight
POSITION REPORT FORMAT (Non-Radar)
Use the memory aid PTA-TEN:
EXAMPLE: POSITION REPORT (Non-Radar)
PILOT:
"Fort Worth Center, BULLY54, VANCE at 1423, flight level 350."
ATC:
"BULLY54, Fort Worth Center, roger."
EXAMPLE: LEAVING/REACHING ALTITUDE
ATC:
"BULLY54, descend and maintain flight level 240."
PILOT (Leaving):
"Descend and maintain flight level 240, BULLY54, leaving flight level 350."
PILOT (Reaching):
"BULLY54, level flight level 240."
Enroute and Arrival Communications
- • Enroute ATC interactions: Reporting position, requesting route changes, and handling altitude assignments or vectors.
- • Arrival procedures: Approach control for STARs, vectors to final, and handoffs to tower.
- • Navigation integration: Reporting over fixes or compulsory points per IFR rules.
EXAMPLE: HANDOFF AND CHECK-IN
CENTER:
"BULLY54, contact Sheppard Approach 124.0."
PILOT:
"Sheppard Approach 124.0, BULLY54."
--- Switch frequency ---
PILOT:
"Sheppard Approach, BULLY54, flight level 350."
ATC:
"BULLY54, Sheppard Approach, radar contact, expect vectors ILS runway 15R."
Emergency and Lost Communications
- • Emergency declarations: "Mayday" for distress, "Pan-Pan" for urgency, squawk 7700.
- • Lost comms procedures: AVE-F memory aid (Assigned, Vectored, Expected, Filed) for route/altitude selection.
- • Transponder codes: 7600 for comm failure, 7700 for emergency.
AVE-F LOST COMMS PROCEDURE
For ALTITUDE, fly the highest of:
For ROUTE, fly in this order:
EMERGENCY SQUAWK CODES
7700
Emergency
7600
Comm Failure
7500
Hijack
COMPLETION STANDARDS
Trainees will demonstrate proficiency in IFR communications through interactive role-playing, group simulations of full IFR flight comms sequences, and discussion. Trainees must:
- • Explain what IFR is, when it is required, and key differences from VFR
- • Demonstrate proper clearance request and readback using CRAFT format
- • Request a pop-up IFR clearance with all required information
- • Explain VATSIM clearance procedures and controller hierarchy
- • Identify compulsory vs non-compulsory reporting points on a chart
- • Provide a proper position report using PTA-TEN format
- • List reports required regardless of radar contact (leaving/reaching altitude, missed approach, etc.)
- • Explain AVE-F procedures per AETCMAN 11-251 and FAA standards
- • Demonstrate no critical errors in readback or etiquette during simulations
Completion: Demonstrate understanding through role-play and scenario exercises