3G Heli Prep ← 3GHeliPrep.com
← Commercial lesson plans
CH.IV.B ground lesson 60–90 minutes

Communications, Light Signals, and Runway Lighting Systems

Airport and Heliport Operations · Task Task B. Communications, Light Signals, and Runway Lighting Systems

Completion Standards

Student demonstrates knowledge of all CH.IV.B items to ACS standards without reference to materials. Risk management items correctly identified. All skill elements performed to commercial ACS tolerances.

Objective

The student will demonstrate commercial-level proficiency in aviation communications, light signal recognition, and runway/heliport lighting systems by correctly selecting appropriate frequencies, transmitting using standard phraseology per the AIM and Pilot/Controller Glossary, acknowledging and complying with ATC instructions, recognizing all ATC light signals and their meanings, identifying runway status lighting systems, and explaining lost communication procedures, transponder operation, radar assistance procedures, and NTSB reporting requirements to meet the performance standards of Commercial Pilot Helicopter ACS CH.III.B.

Content

Introduction

As a commercial helicopter pilot, you will be held to professional standards in all communications. Unlike private operations where small phraseology errors might be forgiven, commercial operations demand precision, clarity, and strict adherence to standard procedures. You’re not just flying for yourself anymore—you’re representing clients, employers, and the entire profession. Every radio call reflects your professionalism.

This lesson builds on your private pilot radio skills by adding commercial-specific situations: operations at busier airports, communication with multiple ATC facilities during aerial work missions, coordination with ground crews during external load operations, and professional-level emergency procedures including when and how to declare an emergency.

Obtaining Appropriate Radio Frequencies (CH.III.B.K1)

Primary Sources for Frequency Information:

  1. Chart Supplement U.S. (formerly A/FD): Most comprehensive source for airport communications frequencies including:

    • CTAF (Common Traffic Advisory Frequency)
    • UNICOM
    • Tower frequencies
    • Ground control
    • ATIS/AWOS/ASOS frequencies
    • Approach/Departure control
    • Clearance Delivery
    • Special-use frequencies (company ops, heliport advisory)

  2. Sectional Charts: Communications boxes show:

    • Tower frequencies in blue
    • CTAF in magenta
    • ATIS frequencies
    • Star symbol (*) indicates part-time operation

  3. IFR En Route Charts: Display:

    • ARTCC frequencies in boxes
    • Remote communications outlet (RCO) frequencies
    • Flight Service frequencies

  4. NOTAM System: Critical for frequency changes, outages, or temporary procedures

  5. ATIS/AWOS/ASOS Recordings: Often include current tower/approach frequencies

  6. Flight Service Station (1-800-WX-BRIEF): Can provide frequencies when other sources unavailable

  7. ATC Direct Request: “Approach, Helicopter 12345, request frequency for XYZ Airport”

Helicopter-Specific Frequency Considerations:

14 CFR 91.129(c)(1): At towered airports, two-way radio communication must be established prior to 4 NM from the airport, up to and including 2,500 feet AGL.

Proper Radio Communication Procedures and ATC Phraseology (CH.III.B.K2)

Standard Radiotelephony Procedures (AIM Chapter 4, Section 2):

Initial Contact Format:

  1. Facility name being called
  2. Aircraft identification (full call sign on initial contact)
  3. Type aircraft (use “helicopter”)
  4. Position or altitude
  5. Request or intention
  6. ATIS code (when applicable)

Example: “Portland Tower, Helicopter November One Two Three Four Alpha, Robinson R44, hovering helipad Two, request northeast departure with information Bravo.”

Subsequent Transmissions: May use abbreviated call sign after ATC does: “Helicopter 34 Alpha”

Standard Phraseology Requirements:

Readback Requirements (AIM 4-4-7):

Must read back in full:

  1. Runway assignments
  2. Altitude assignments
  3. Heading assignments
  4. Speed restrictions
  5. Clearance to hold short of any runway
  6. Frequency changes
  7. Transponder codes
  8. Any clearance or instruction containing “HOLD” or “CLEARED”

Helicopter-Specific Phraseology:

Commercial Considerations:

When conducting aerial work or commercial operations:

ATC Light Signal Recognition (CH.III.B.K3)

14 CFR 91.125: ATC light signals have the meaning shown in the regulation. You must know these cold—not just for the checkride, but because radio failures happen.

Light Gun Signal Chart (per 14 CFR 91.125):

Color & TypeOn GroundIn Flight
Steady GreenCleared for takeoffCleared to land
Flashing GreenCleared to taxiReturn for landing (to be followed by steady green)
Steady RedSTOPGive way to other aircraft and continue circling
Flashing RedTaxi clear of runway in useAirport unsafe—DO NOT LAND
Flashing WhiteReturn to starting point on airportNot applicable
Alternating Red/GreenExercise extreme cautionExercise extreme caution

Critical Distinctions:

Helicopter Light Signal Scenarios:

During pinnacle operations to uncontrolled elevated helipads, light signals from ground personnel may coordinate landing. These are NOT official ATC signals and require pre-briefing on meaning. ATC light signals always take precedence over non-ATC signals.

When hovering taxi or air-taxiing at towered airports, maintain visual contact with tower. Light signals can be directed at hovering aircraft.

Professional Response:

If you receive light signals unexpectedly:

  1. Check your radio—did you lose comm?
  2. Acknowledge the signal appropriately
  3. Comply with the signal
  4. Once on ground, contact tower via phone to determine cause
  5. Squawk 7600 if radio failure confirmed in flight

Appropriate Use of Transponder(s) (CH.III.B.K4)

14 CFR 91.215: Transponder required:

14 CFR 91.413: Transponders must be inspected/tested every 24 calendar months for IFR operations.

Transponder Codes and Meanings:

Mode C/Mode S Altitude Reporting:

Mode C automatically transmits pressure altitude. ATC uses this for:

ADS-B Out Requirements (14 CFR 91.225):

Required in same airspace as Mode C transponder requirement after January 1, 2020. Most modern transponders integrate ADS-B Out. Transmits:

Transponder Operating Procedures:

  1. Before Engine Start: Set to STANDBY or OFF (reduces ground clutter, prevents false targets)
  2. Before Takeoff: Set to ALT or ON mode
  3. During Flight:
    • Remain on ALT unless ATC directs STANDBY
    • Update discrete code as assigned
    • IDENT only when requested
  4. Post-Landing: Return to STANDBY or OFF

IDENT Function:

When ATC says “Ident,” immediately push IDENT button. This brightens your return for 15-20 seconds, helping controllers confirm your target during:

Helicopter Operations Considerations:

Code Switching Discipline:

When ATC assigns new code: “Helicopter 34 Alpha, squawk 4532”

Lost Communication Procedures (CH.III.B.K5)

14 CFR 91.185: Lost communications rule primarily for IFR, but VFR pilots must understand principles.

VFR Lost Communications:

If you lose two-way radio capability in VFR conditions:

  1. Squawk 7600 immediately
  2. Remain VFR and land as soon as practicable
  3. Watch for light signals if at towered airport
  4. Notify ATC after landing via telephone

At Towered Airport:

En Route VFR:

Radio Failure Versus Radio Malfunction:

Two-Way Communication Required Locations:

Helicopter-Specific NORDO Considerations:

Helicopters have options fixed-wing aircraft don’t:

IFR Lost Communications Brief (91.185):

Though you’re training for commercial VFR, know IFR lost comm basics:

Equipment Issues That Could Cause Loss of Communication (CH.III.B.K6)

Common Radio System Failures:

  1. Electrical System Failure:

    • Alternator/generator failure cuts power to radios
    • Battery provides limited backup (30-60 minutes typical)
    • Signs: Low voltage light, dimming lights, avionics flickering
    • Action: Reduce electrical load, squawk 7600 or 7700 depending on severity, land immediately

  2. Antenna Problems:

    • Damaged or disconnected antenna cable
    • Broken antenna mount (vibration, hard landing)
    • Corrosion at antenna connection points
    • Symptom: Greatly reduced range, garbled transmission/reception
    • Preflight: Visually inspect antennas for damage, security

  3. Circuit Breaker Pops:

    • Avionics master circuit breaker
    • Individual radio circuit breaker
    • Cause: Short circuit, overload, loose connection
    • Action: Do NOT immediately reset—identify cause. One reset attempt allowed after brief cooling period. If it pops again, treat as failed system.

  4. Microphone/Headset Failure:

    • Broken microphone switch
    • Damaged cord
    • Loose connections
    • Prevention: Carry backup handheld microphone
    • Test: Monitor ATIS or AWOS to verify reception; press PTT and watch for TX light

  5. Stuck Microphone:

    • Most disruptive failure—blocks entire frequency
    • Caused by: PTT switch stuck, cord pinched, weight on PTT button
    • Other aircraft hear constant carrier or open mic sounds
    • Response: If ATC says “aircraft transmitting, check stuck mic,” immediately check your PTT, cords, and headset. If it’s you, switch to backup mic or isolate the faulty device.

  6. Audio Panel Malfunction:

    • Selected wrong radio
    • Transmit/receive switch in wrong position
    • Volume turned down or muted
    • Pilot-caused “failures” are common—check settings before declaring emergency

  7. Frequency Congestion Mistaken for Failure:

    • Busy frequency = long wait for break in transmission
    • Overlapping transmissions (“stepped on”) = garbled or no reception
    • Not a failure—be patient, wait for break

Preventive Measures:

Commercial Operations Considerations:

For commercial operations (tours, aerial work, EMS):

Radar Assistance (CH.III.B.K7)

Radar Services Available to VFR Aircraft:

  1. Radar Traffic Advisories (Flight Following):

    • Workload permitting
    • Request: “Approach, Helicopter N1234A, request VFR flight following”
    • Provide: Position, altitude, destination, type aircraft
    • ATC provides: Traffic calls, safety advisories, sequencing assistance
    • 14 CFR 91.123: Once receiving ATC service, comply with instructions unless emergency or deviation necessary (then notify ATC)

  2. Radar Vectors:

    • ATC may provide heading guidance to avoid traffic, weather, obstacles
    • “Helicopter 34A, fly heading 180 for traffic”
    • You remain responsible for terrain/obstruction clearance in VFR
    • Wake turbulence advisories provided

  3. VFR-on-Top (IFR Clearance):

    • Not standard VFR radar service
    • IFR clearance allowing VFR altitude selection above clouds
    • Requires IFR rating

  4. Terminal Radar Service Areas (TRSA):

    • Depicted on sectional charts with solid black lines
    • Participation required per FAR 91.131—not optional
    • Full ATC separation provided (Class B-like service without Class B requirements)
    • Examples: Topeka, Baton Rouge

  5. Class C Service:

    • Mandatory within Class C airspace
    • Separation from IFR, sequencing for VFR
    • Workload permitting, service continues outside Class C (RADAR service provided beyond outer area)

  6. Class B Service:

    • ATC clearance required to enter
    • Positive separation from all aircraft
    • Wake turbulence advisories

Radar Limitations with Helicopters:

Emergency Radar Assistance:

When lost, disoriented, or experiencing emergency:

  1. Establish Contact: Use any frequency if unsure (121.5 emergency monitored by most facilities)
  2. State Problem: “Mayday” (emergency) or “Pan-pan” (urgency) followed by situation
  3. Provide Information:
    • Aircraft ID, type
    • Position (best estimate, nearby landmarks, last known position)
    • Altitude
    • Heading
    • Fuel remaining
    • Souls on board
    • Pilot qualifications/experience
  4. Squawk 7700 (emergency) or 7600 (lost comm)
  5. Follow ATC Vectors: ATC will provide headings to safe landing area or toward radar-identified position
  6. DF Steer (Direction Finding): Some facilities can home in on your transmission signal—transmit for 10 seconds when requested

Minimum Safe Altitude Warning (MSAW):

ATC radar system alerts controllers when aircraft appears to be at unsafe altitude:

Helicopter Routes and Radar Service:

Standard Radar Phraseology:

NTSB Accident/Incident Reporting (CH.III.B.K8)

49 CFR 830: NTSB regulations governing accident/incident reporting.

Definitions (49 CFR 830.2):

Aircraft Accident: Occurrence between boarding and disembarkation where:

Serious Injury: Requires hospitalization more than 48 hours within 7 days of injury, fracture (except simple finger/toe/nose), severe hemorrhage/muscle/nerve/tendon damage, second/third-degree burns over 5% of body, or any internal organ injury.

Substantial Damage: Damage or failure adversely affecting structural strength, performance, or flight characteristics requiring major repair/replacement of affected component. Excludes:

Incident: Occurrence other than accident that affects or could affect safety of operations.

Immediate Notification Required (49 CFR 830.5):

Notify NTSB immediately (most expeditious means available) when aircraft accident occurs or any of these incidents:

  1. Flight control system malfunction
  2. Crewmember unable to perform duties due to injury/illness
  3. Turbine engine failure/damage (excluding compressor blade/turbine bucket damage)
  4. In-flight fire
  5. Aircraft collision in flight
  6. Property damage (other than aircraft) over $25,000
  7. Overdue aircraft believed in accident
  8. Release of all/portion of propeller blade
  9. Complete loss of information from more than 50% of cockpit displays
  10. ACAS (TCAS) resolution advisory requiring deviation when aircraft is being operated on IFR flight plan
  11. Damage to helicopter tail/main rotor systems requiring major repair/replacement
  12. Any event requiring emergency evacuation

How to Report:

Information to Provide:

  1. Aircraft identification
  2. Aircraft type
  3. Owner/operator name and address
  4. Pilot name and certificate number
  5. Date, time, location
  6. Last departure point, intended destination
  7. Number of persons aboard, injuries, fatalities
  8. Nature of accident/incident
  9. Weather conditions
  10. Pilot flight time (recent and total)

Written Report Requirement (49 CFR 830.15):

Helicopter-Specific Accident Scenarios:

Common helicopter accidents requiring NTSB notification:

Commercial Pilot Responsibility:

As PIC of commercial operations:

Precautionary Landings:

If you execute precautionary landing due to mechanical issue but no substantial damage or injury occurs, NTSB notification not required. However:

Runway Status Lighting Systems (CH.III.B.K9)

Overview:

Runway Status Lights (RWSL) are automated systems that provide runway occupancy status directly to pilots and vehicle operators via lighting, reducing runway incursions. These systems are installed at some towered airports with high traffic density.

RWSL Components:

  1. Runway Entrance Lights (REL):

    • Red in-pavement lights at taxiway/runway intersections
    • Illuminate when runway unsafe to enter
    • Located along first 1,500 feet of runway centerline where taxiway intersects
    • Alert pilots/vehicles not to enter runway

  2. Takeoff Hold Lights (THL):

    • Red in-pavement lights in double longitudinal row aligned with centerline
    • Located in runway departure position
    • Illuminate when runway unsafe for takeoff (traffic on runway, aircraft on final approach)
    • Final check before releasing brakes

  3. Runway Intersection Lights (RIL):

    • Red lights at runway/runway intersections
    • Illuminate when conflicting traffic present on intersecting runway
    • Help during intersection departures or when crossing active runway

How RWSL Works:

Pilot Procedures with RWSL (AIM 2-1-6):

When You See Red Lights:

  1. Runway Entrance (REL): Stop. Do not enter runway. Contact ATC for clarification if you believe you have clearance.

  2. Takeoff Hold (THL): Stop. Do not takeoff. Verify ATC clearance. Contact ATC if lights illuminate after receiving takeoff clearance.

  3. During Takeoff Roll: If THL illuminate after takeoff commenced and prior to rotating:

    • If sufficient runway remains: Discontinue takeoff, stop, exit runway, contact ATC
    • If insufficient runway to stop safely: Continue takeoff, notify ATC immediately after airborne

When Lights Do NOT Illuminate:

Runway Edge Light Watchers (RELW) - Removed:

Earlier RWSL versions included RELW (alternating flashing runway edge lights). These have been removed from most systems due to pilot confusion. If you see any unusual flashing edge lights, exercise increased caution and query ATC.

RWSL Limitations:

Airports with RWSL:

Check NOTAMs and Chart Supplement. Examples include:

Helicopter Operations and RWSL:

Reporting RWSL Issues:

If you observe RWSL malfunction or unexpected behavior:

Other Airport Lighting Systems (Related Knowledge):

While ACS specifically mentions RWSL, commercial pilots should understand full range of airport lighting:

Approach Lighting Systems:

Runway Lighting:

Taxiway Lighting:

Heliport Lighting:

Pilot-Controlled Lighting (PCL):

At uncontrolled airports, activate lights via radio:

Risk Management: Communication (CH.III.B.R1)

Communication Failures Create Cascading Risks:

Loss of radio communication doesn’t just mean you can’t talk to ATC—it means:

Pre-Flight Communication Risk Management:

  1. Equipment Check:

    • Test both radios (if equipped) before taxi
    • Monitor ATIS/AWOS to verify reception
    • Transmit on ground frequency to verify transmission (watch for TX light and ATC response)
    • Check headset/microphone connections secure
    • Verify backup handheld radio charged and functional (commercial operations)

  2. Frequency Planning:

    • Write down all expected frequencies before departure
    • Program frequencies into standby positions
    • Note emergency frequencies (121.5, nearest FSS)
    • Brief passenger on intercom operation (don’t block frequency)

  3. Alternative Communication Plans:

    • Cell phone available (ground coordination, not in-flight ATC substitute)
    • Company frequency available if commercial operation
    • Know how to contact FSS for relay
    • Understand light signal procedures

In-Flight Communication Risk Management:

  1. Monitor Appropriate Frequency:

    • Don’t just leave radio on—actively listen
    • Switching frequencies while navigating increases workload—do during straight/level flight
    • If frequency suspiciously quiet, verify volume and squelch settings

  2. Clarify Unclear Instructions:

    • Never assume what ATC meant—ask for clarification
    • “Say again” or “Confirm you want Helicopter 34A to…”
    • Non-standard phraseology from ATC should be questioned
    • Readback critical instructions for ATC to catch errors

  3. Maintain Situational Awareness:

    • Listen to ATC instructions to other aircraft—develops picture of traffic flow
    • Note where other aircraft are positioned
    • If ATC calls traffic and you don’t see it, tell them: “Helicopter 34A, negative contact”

  4. Cross-Check Navigation and Communication:

    • If ATC instructions seem wrong (heading toward terrain, wrong direction), query immediately
    • “Verify heading 090—that appears to be toward rising terrain”
    • ATC can make errors too—pilot responsibility to question unsafe instructions

Communication Workload Management:

High workload + complex communication = errors:

Frequency Congestion:

Busy frequencies create communication challenges:

Communication with Non-Towered Airports:

Risk Management: Deciding If and When to Declare an Emergency (CH.III.B.R2)

What Constitutes an Emergency? (AIM 6-1-1)

An emergency is a distress or urgency condition. As PIC, you declare the emergency—not ATC, not company, not passengers. 14 CFR 91.3(b) gives you authority to deviate from any regulation to the extent required to meet the emergency.

Distress vs. Urgency:

Commercial Pilot Mindset on Emergencies:

Many pilots hesitate to declare emergency due to:

Reality:

When to Declare Emergency:

Declare immediately for:

  1. Engine failure or severe malfunction: You have seconds to find landing spot
  2. Fire: In-flight fires are life-threatening urgency
  3. Structural damage: Any main rotor, tail rotor, or airframe damage affecting controllability
  4. Low fuel: When fuel exhaustion is possible before landing
  5. Lost/disoriented: When unfamiliar with area and unable to navigate safely
  6. Medical emergency: Passenger or pilot incapacitation requiring immediate landing
  7. Weather entrapment: VFR into IMC with no instrument rating or proficiency

Consider declaring for:

How to Declare:

  1. Use “MAYDAY” (distress) or “PAN-PAN” (urgency) repeated three times
  2. Identify aircraft: “Mayday, Mayday, Mayday, Helicopter November 1234 Alpha”
  3. State nature of emergency: “Engine failure”
  4. Provide essential information:
    • Position (landmarks, GPS coordinates, distance/direction from airport)
    • Altitude
    • Heading
    • Souls on board
    • Fuel remaining (time)
    • Pilot qualifications/intentions
  5. Squawk 7700
  6. Follow ATC instructions or announce intentions if no ATC contact

Example: “Mayday, Mayday, Mayday, Los Angeles Tower, Helicopter November One Two Three Four Alpha, engine failure, autorotating to golf course 2 miles south of airport, 800 feet, one person on board.”

Don’t Delay:

Every second spent debating whether to declare is a second you could be getting help:

Post-Emergency:

If you declare emergency and then resolve the issue (engine stumble corrects, weather clears, you find your position):

Commercial Operations Specific:

Legal Protection:

14 CFR 91.3(b): “In an in-flight emergency requiring immediate action, the pilot in command may deviate from any rule of this part to the extent required to meet that emergency.”

You can:

This protection applies only if you genuinely believed emergency existed and actions were necessary.

Risk Management: Use of Non-Standard Phraseology (CH.III.B.R3)

Why Standard Phraseology Matters:

Aviation radio phraseology evolved over decades to be:

Non-standard phraseology introduces risk through:

Common Non-Standard Phraseology Errors:

Non-StandardStandardIssue
”With you”[Omit]Unnecessary—ATC knows you’re there when you call
”Any traffic in the area please advise”[Omit—just listen]Encourages unnecessary transmissions
”Taking the active""Departing runway 27”Ambiguous—which runway?
”Last call""Helicopter 34A departing frequency”Unclear intention
”Over the numbers""Crossing threshold”Vague position
”Fixina” (fixing to)“Ready for departure”Slang, unclear
”Roger” (acknowledging instruction)“Wilco” or full readback”Roger” means received, not complying

When Non-Standard Phraseology is Acceptable:

  1. Emergency Situations:

    • Clarity over formality: “I need to land NOW, engine fire” beats trying to remember exact phraseology
    • Plain English acceptable when stressed

  2. Explanations/Clarifications:

    • After initial standard call, explanation can use plain language
    • “Unable due to weather” is fine
    • “Request heading change to avoid buildup” is clear

  3. VFR Position Reports at Non-Towered Fields:

    • “Helicopter 34A, entering left downwind, runway 27, Cherry Ridge”
    • “Helicopter 34A, hovering helipad 2 for northeast departure, Cherry Ridge”

Regional Variations:

Some non-standard phrases are so common they’re quasi-standard:

Use judgment—if ATC and all pilots in region use a phrase consistently, it’s functionally standard for that area. But stick to AIM phraseology when possible.

Helicopter-Specific Phraseology:

Helicopters must use clear, descriptive phraseology for unique operations:

Standard:

Non-Standard (avoid):

Commercial Pilot Standard:

As commercial pilot, you represent professionalism:

Improving Phraseology:

  1. Study Pilot/Controller Glossary (in back of AIM)
  2. Listen to LiveATC.net: Hear how professional pilots communicate
  3. Script complex calls: Write them down before transmitting
  4. Self-critique: After each flight, identify non-standard phrases you used
  5. Chair-fly communications: Practice radio calls on ground

When You Hear Non-Standard Phraseology from ATC:

Controllers sometimes use non-standard phrasing. If unclear:

Schedule

SegmentDurationActivity
Introduction & Frequencies15 minDiscuss obtaining frequencies, Chart Supplement use, sectional chart interpretation, helicopter-specific frequency considerations
Radio Procedures & Phraseology25 minReview AIM Chapter 4 procedures, standard phraseology, readback requirements, commercial-level communication expectations, practice scripting calls
Light Signals & Lost Comm15 minReview 14 CFR 91.125 light signals, demonstrate recognition, discuss lost communication procedures per 14 CFR 91.185 (VFR focus)
Transponder Operations15 minReview transponder codes, Mode C/ADS-B requirements per 14 CFR 91.215/91.225, proper operating procedures, IDENT function, code switching
Radar Services10 minDiscuss flight following, radar vectors, emergency assistance, helicopter-specific radar limitations, DF steers, MSAW alerts
NTSB Reporting10 minReview 49 CFR 830 definitions, immediate notification requirements, written report procedures, helicopter-specific accident scenarios
Runway Status Lights10 minExplain RWSL components (REL, THL, RIL), operational procedures, limitations, pilot response to red lights, relationship to ATC clearance
Risk Management Discussion15 minAnalyze communication failures, emergency declaration decision-making, non-standard phraseology risks, commercial operation considerations
Scenario-Based Training20 minPractice radio calls, lost comm scenarios, emergency declarations, light signal recognition, transponder emergencies using realistic helicopter scenarios
Practical Application & Review15 minStudent demonstrates radio procedures, explains all knowledge items, reviews completion standards
Total150 min (2.5 hrs)

Equipment

Required References:

Materials:

Visual Aids:

Recommended:

Instructor Actions

  1. Begin by asking student: “You’re approaching a Class D airport for the first time in 6 months. Walk me through every communication you’ll make from 10 miles out to parking on the ramp.” Assess current proficiency and identify gaps in knowledge or phraseology.

  2. Present Chart Supplement page for unfamiliar airport. Have student identify all available frequencies (tower, ground, ATIS, approach, UNICOM, etc.) and explain when each would be used. Discuss helicopter-specific heliport frequencies if available.

  3. Review sectional chart communication boxes. Point out part-time tower symbols (star), Class D airspace details, CTAF frequencies. Explain how to determine if tower is active or non-towered procedures apply.

  4. Demonstrate proper initial radio call structure using whiteboard: Facility name + Aircraft ID + Type + Position + Request + ATIS. Script example call together: “Portland Tower, Helicopter November One Two Three Four Alpha, Robinson R44, hovering helipad Two, request northeast departure with information Bravo.”

  5. Review AIM Chapter 4 readback requirements. Emphasize critical items requiring full readback: runway assignments, altitude assignments, hold short instructions, frequency changes, transponder codes. Explain consequences of incorrect readback (ATC will correct you).

  6. Conduct rapid-fire light signal quiz: Display each color/type combination from 14 CFR 91.125 and require immediate response of meaning for both “on ground” and “in flight” scenarios. Correct any hesitation—student must know these instantly.

  7. Discuss lost communication scenario: “You’re 15 miles from Class D airport when radio goes silent. You can’t transmit or receive. What do you do?” Walk through squawk 7600, remain VFR, watch for light signals, land as soon as practicable. Emphasize this is not license to enter Class D without communication.

  8. Demonstrate transponder operation using panel or diagram: Show STANDBY, ON/ALT, IDENT, code entry. Explain when to squawk 1200, when to use assigned discrete code, when to squawk 7600 or 7700. Demonstrate IDENT function and explain it brightens return for ~15 seconds.

  9. Review 14 CFR 91.215 and 91.225 transponder/ADS-B requirements. Use sectional chart to show Mode C veil around Class B airports (30 NM ring). Discuss why helicopters conducting aerial work at 500 feet AGL inside veil still need operating transponder.

  10. Explain radar service concept: “Flight following is workload permitting. You request it; ATC provides traffic advisories but you’re still VFR—you don’t get vectors unless you ask or they offer. Once you accept service, 14 CFR 91.123 applies—you must comply with ATC instructions.” Discuss commercial pilot responsibility to follow instructions.

  11. Present helicopter radar limitations: “You’re air-taxiing at 10 feet AGL. Will ATC radar see you?” Explain terrain masking, altitude limitations, slow-speed filtering on older radars. ADS-B improves this but position awareness still critical.

  12. Describe emergency radar assistance procedures: “You’re lost, low on fuel, and scared. What do you say on 121.5?” Walk through Mayday call structure, squawk 7700, provide position estimate (landmarks, GPS, last known), altitude, heading, fuel, souls on board. Explain DF steers if available.

  13. Review 49 CFR 830 definitions by presenting scenarios: “You’re hovering and skid collapses. Helicopter tips over, main rotor strikes ground, tail rotor damaged. Any injuries? Is this an accident?” Student must determine if substantial damage occurred and whether NTSB notification required.

  14. Explain substantial damage exclusions: “Bent fairings, dented skin, damaged landing gear—not substantial. But damage to tail rotor system requiring major repair IS substantial. Know the difference.”

  15. Walk through NTSB immediate notification requirements using 49 CFR 830.5 list. Highlight helicopter-specific: “Damage to helicopter tail or main rotor system requiring major repair or replacement” is specifically listed incident requiring immediate notification.

  16. Demonstrate NTSB notification process: “You call 844-373-9922 or nearest NTSB office. You provide aircraft ID, type, owner, pilot info, date/time/location, number of persons, injuries, nature of accident, weather, pilot flight time. Written report on Form 6120.1/2 within 10 days if accident.”

  17. Introduce Runway Status Lighting Systems using AIM 2-1-6 diagrams. Show REL (red lights at taxiway/runway intersection), THL (red lights in takeoff position), RIL (red lights at runway/runway intersection). Explain these are automatic, surveillance-based, advisory systems.

  18. Emphasize critical RWSL limitation: “Red lights illuminated = DO NOT PROCEED. But absence of red lights does NOT mean runway is clear. You still need ATC clearance. RWSL is backup safety system, not clearance indicator.”

  19. Discuss RWSL procedure during takeoff: “You’re in position, cleared for takeoff. As you add power, THL illuminate red. What do you do?” If sufficient runway to stop: discontinue takeoff, contact ATC. If insufficient runway: continue takeoff, notify ATC immediately after airborne.

  20. Review other airport lighting systems relevant to commercial operations: PAPI (red over white, you’re all right), REIL (flashing white threshold lights), runway edge lights (white), threshold (green approaching, red departing), taxiway lights (blue edge, green centerline). Helicopters use these for night operations.

  21. Explain pilot-controlled lighting at non-towered airports: Key mic 3/5/7 times within 5 seconds for low/medium/high intensity. Lights stay on 15 minutes. Demonstrate how to find PCL frequency on sectional chart and Chart Supplement.

  22. Discuss communication failure risk management: “Before every flight, test both radios on ground. Monitor ATIS to verify reception. Transmit on ground frequency to verify transmission. Carry backup handheld radio for commercial operations. Write down all expected frequencies before departure.”

  23. Analyze emergency declaration decision-making: “Many pilots hesitate to declare emergency. Why?” Discuss embarrassment, fear of FAA investigation, ‘can handle it’ mentality. Counter with: “14 CFR 91.3 gives you authority. FAA investigates accidents, not precautionary declarations. Dead pilots don’t file reports—use the system.”

  24. Present emergency declaration scenarios for student decision: “Engine running rough, still producing power. Emergency?” “Lost, unfamiliar area, 30 minutes fuel. Emergency?” “VFR, just entered clouds, no instrument rating. Emergency?” Student must decide distress (Mayday) vs. urgency (Pan-Pan) vs. no declaration.

  25. Review non-standard phraseology risks using examples: “Tower, Helicopter 34A is with you.” (Unnecessary) “Any traffic please advise.” (Creates frequency congestion) “Taking the active.” (Ambiguous—which runway?) Show proper alternatives.

  26. Demonstrate standard commercial-level radio call: “Los Angeles Tower, Helicopter November One Two Three Four Alpha, Robinson R44, 10 miles north at 1,500, inbound landing heliport with information Delta, request Class Bravo clearance.” Explain each element.

  27. Script complex radio scenario together: Student is 20 miles from Class C airport, wants flight following to Class D airport 40 miles beyond Class C. Student writes out initial call to Approach before transmitting. CFI reviews for standard phraseology, completeness, conciseness.

  28. Conduct scenario: “You’re on frequency with Tower. Suddenly you hear continuous carrier wave and garbled sounds. What’s happening and what do you do?” Explain stuck microphone, likely another aircraft, ATC will try to identify and ask them to check. If it’s you, isolate the faulty device immediately.

  29. Role-play lost communication at towered airport: Instructor plays tower using light gun. Student is on short final, sees steady green light. Student explains: “Steady green in flight means cleared to land. I’ll land, complete after-landing checklist, then call tower via phone from ramp to determine what happened.”

  30. Practice emergency declaration phraseology: “I’m going to give you emergency scenarios. You immediately make Mayday or Pan-Pan call.” Scenarios: engine failure, fuel exhaustion imminent, lost/disoriented, sick passenger, VFR into IMC. Student must say Mayday/Pan-Pan 3x, aircraft ID, nature, position, altitude, souls, fuel, intentions.

  31. Review transponder emergency procedures: “What do you squawk if you lose all radios?” (7600) “What if engine fails?” (7700) “What if you squawk 7500?” (Hijack—don’t squawk unless actual hijacking) “Can you squawk 7700 and still talk on radio?” (Yes—emergency squawk alerts ATC immediately even if you’re communicating)

  32. Discuss commercial operation communication scenarios: “You’re conducting aerial survey at 500 feet, circling stadium. What do you tell ATC?” Student must explain notification of operation type, altitude, area, duration. “Survey complete—what do you say?” Request clearance back to airport.

  33. Quiz NTSB reporting: “Hard landing, skid collapses, no damage except bent skid tube. Reportable?” (No—landing gear damage not substantial) “Wire strike, pilot laceration requiring 10 stitches, minor skin damage to fuselage. Reportable?” (Yes—serious injury definition includes hospitalization >48 hours OR other criteria; check specifics)

  34. Analyze runway status lights with helicopters: “You’re air-taxiing at 3 feet AGL toward runway. REL illuminate red. What do you do?” (Stop, contact ATC—even though hovering, RWSL may detect you or another aircraft/vehicle) “REL don’t illuminate but you see aircraft on runway. Proceed?” (NO—absence of lights doesn’t confirm clear)

  35. Summarize risk management integration: “Communication failures, emergency declarations, and non-standard phraseology all tie to one principle: clear, professional communication prevents incidents. As commercial pilot, you’re held to higher standard. Your radio work reflects your overall competence.”

  36. Conclude with completion standards preview: “During checkride, you’ll demonstrate frequency selection, standard phraseology, readback procedures, light signal recognition, transponder operation, and thorough understanding of lost comm, NTSB reporting, and RWSL. Evaluator expects commercial-level precision in all communication tasks.”

Student Actions

  1. Identify all available frequencies for assigned airport using Chart Supplement and sectional chart, explaining when each frequency is used and how to determine tower operating hours.

  2. Script initial radio call to towered airport approach facility, incorporating all required elements (facility name, aircraft ID, type, position, request, ATIS code) using standard phraseology from AIM.

  3. Demonstrate proper readback technique by reading back instructor-provided ATC instructions, including runway assignments, altitude assignments, hold short clearances, and transponder codes, using exact phraseology.

  4. Immediately state meaning of each ATC light signal (steady green, flashing green, steady red, flashing red, flashing white, alternating red/green) for both “on ground” and “in flight” conditions without reference to notes.

  5. Explain lost communication procedures for VFR flight, including squawk code (7600), navigation intentions (remain VFR, land as soon as practicable), light signal monitoring, and post-landing ATC notification requirements.

  6. Demonstrate transponder operation by explaining when to use STANDBY vs. ALT modes, how to enter assigned codes, when to squawk 1200/7600/7700, and proper IDENT function use.

  7. Describe complete procedure for requesting VFR flight following, including initial contact phraseology, information provided to ATC, and pilot responsibilities once service is established (14 CFR 91.123 compliance).

  8. Explain radar service limitations for helicopters operating at low altitudes, including terrain masking, radar coverage gaps, and why ADS-B improves but doesn’t eliminate position awareness responsibility.

  9. Demonstrate emergency declaration by making proper Mayday call for instructor-provided scenario, including all essential information (aircraft ID, nature of emergency, position, altitude, souls on board, fuel remaining, intentions).

  10. Determine whether instructor-provided scenarios meet 49 CFR 830 definitions of “accident,” “incident,” or neither, and explain immediate notification requirements and written report procedures.

  11. Distinguish substantial damage from non-substantial damage in helicopter scenarios (e.g., bent fairings vs. main rotor system damage requiring major repair) using 49 CFR 830.2 definitions.

  12. Explain all three Runway Status Lighting System components (REL, THL, RIL), describe when each illuminates, and state proper pilot response to red lights both on ground and during takeoff roll.

  13. Describe complete pilot-controlled lighting procedure, including frequency selection, number of mic clicks for each intensity level, and duration lights remain illuminated.

  14. Identify non-standard phraseology in instructor-provided radio transmissions and provide standard phraseology alternatives using AIM and Pilot/Controller Glossary references.

  15. Analyze communication failure risk management by listing preflight checks (radio testing, backup equipment, frequency planning) and in-flight procedures (monitoring, clarification of unclear instructions, alternative communication means).

  16. Explain decision-making process for emergency declarations, including distress (Mayday) vs. urgency (Pan-Pan) criteria, legal protections under 14 CFR 91.3(b), and why pilots should not hesitate to declare when safety requires assistance.

  17. Describe complete NTSB notification procedure, including 24-hour response center number (844-373-9922), information to provide, and timeline for written report (Form 6120.1/2 within 10 days of accident).

  18. Demonstrate knowledge of 14 CFR 91.215 and 91.225 transponder and ADS-B requirements by identifying on sectional chart where Mode C transponder is required (Class A, B, C, above Class B/C, above 10,000 MSL excluding below 2,500 AGL, Mode C veil).

  19. Script radio communications for complex scenario provided by instructor (e.g., transitioning Class C airspace en route to Class D airport, requesting flight following, frequency changes, airport advisory, taxi instructions) using entirely standard phraseology.

  20. Explain helicopter-specific communication considerations, including use of “helicopter” in call sign, position reporting terms (hovering, air-taxiing, surface taxiing), external load operation coordination, and aerial work notifications to ATC.

  21. Respond to instructor’s role-played ATC communications, demonstrating proper acknowledgment techniques, correct readback of critical instructions, and appropriate questions when instructions are unclear or appear unsafe.

Completion Standards

The student demonstrates understanding of communications, light signals, and runway lighting systems by meeting the Commercial Pilot Helicopter ACS standards for Task CH.III.B:

Knowledge (Oral Evaluation):

  1. Explains how to obtain appropriate radio frequencies using Chart Supplement, sectional charts, IFR charts, NOTAM system, ATIS/AWOS/ASOS recordings, Flight Service, and direct ATC requests, including helicopter-specific frequency considerations for heliports, offshore operations, and aerial work coordination (CH.III.B.K1).

  2. Describes proper radio communication procedures per AIM Chapter 4, including initial contact format (facility name, aircraft ID, type, position, request, ATIS code), standard phraseology from Pilot/Controller Glossary, readback requirements for runway/altitude/heading assignments and hold short clearances, number pronunciation, and helicopter-specific phraseology for hovering, air-taxiing, and commercial operations (CH.III.B.K2).

  3. Immediately and accurately recognizes all ATC light signals per 14 CFR 91.125 (steady green, flashing green, steady red, flashing red, flashing white, alternating red/green) for both on-ground and in-flight conditions, explains proper acknowledgment methods (rock wings day / flash lights night), and describes scenarios when light signals would be used (CH.III.B.K3).

  4. Explains appropriate transponder use per 14 CFR 91.215 and 14 CFR 91.225, including when transponder/Mode C/ADS-B required (Class A/B/C, above 10,000 MSL, Mode C veil), standard codes (1200 VFR, 7500 hijack, 7600 lost comm, 7700 emergency), operating modes (STANDBY, ALT), IDENT function, and code switching procedures (CH.III.B.K4).

  5. Describes VFR lost communication procedures including squawk 7600, remain VFR and land as soon as practicable, watch for light signals at towered airports, avoid Class B/C/D if possible, post-landing ATC notification via telephone, and explains difference between complete failure vs. receiver-only or transmitter-only failures (CH.III.B.K5).

  6. Identifies equipment issues causing communication loss including electrical system failure, antenna damage, circuit breaker pops, microphone/headset failure, stuck microphone, audio panel malfunction, and frequency congestion, explaining preventive measures (preflight inspection, backup equipment, electrical system monitoring) and appropriate responses to each failure type (CH.III.B.K6).

  7. Explains radar assistance available to VFR aircraft including flight following procedures, radar vectors, emergency assistance via 121.5, DF steers, MSAW alerts, and describes helicopter-specific radar limitations (low altitude, terrain masking, slow speed, hovering) and how ADS-B improves but doesn’t eliminate position awareness requirements (CH.III.B.K7).

  8. Describes NTSB accident/incident reporting per 49 CFR 830, including definitions of aircraft accident (death, serious injury, or substantial damage), serious injury (hospitalization >48 hours, fractures, severe hemorrhage/burns/organ damage), substantial damage (excluding engine-limited damage, bent fairings, dented skin, landing gear damage), immediate notification requirements (nearest NTSB office or 844-373-9922), information to provide (aircraft ID, type, owner, pilot, date/time/location, persons/injuries, nature, weather, pilot time), and written report timeline (Form 6120.1/2 within 10 days of accident) with helicopter-specific examples (tail rotor strikes, dynamic rollover, hard landings, LTE, wire strikes, external load incidents) (CH.III.B.K8).

  9. Explains Runway Status Lighting Systems (RWSL) per AIM 2-1-6, including three components (REL - red lights at taxiway/runway intersection, THL - red lights at departure position, RIL - red lights at runway intersections), how system works (automatic, surveillance-based, advisory only), proper pilot response to red lights (stop, do not enter/takeoff, contact ATC), procedure if THL illuminate during takeoff roll (stop if sufficient runway / continue and notify ATC if insufficient stopping distance), limitations (lights advisory only, do not replace ATC clearance, absence of red lights does not confirm runway clear), and airports where RWSL installed (CH.III.B.K9).

Risk Management (Oral Evaluation and Scenario Discussion):

  1. Demonstrates risk management related to communication by explaining preflight procedures (test both radios, monitor ATIS for reception check, transmit on ground frequency, verify backup handheld radio for commercial ops, write down expected frequencies), in-flight procedures (actively monitor appropriate frequency, clarify unclear instructions, maintain situational awareness by listening to other traffic, cross-check navigation with communication, manage work

Want the complete lesson plan library as a downloadable Word document?

Download the Free CFI Lesson Plan Binder