3G Heli Prep ← 3GHeliPrep.com
← Commercial lesson plans
CH.IX.B both lesson 90–120 minutes

Navigation Systems and Radar Services

Navigation · Task Task B. Navigation Systems and Radar Services

Completion Standards

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

Objective

The commercial helicopter pilot student will demonstrate comprehensive knowledge and proficient use of ground-based and satellite-based navigation systems, transponder/ADS-B equipment, and radar services to safely navigate while maintaining altitude within ±100 feet and heading within ±10°, consistent with commercial pilot privileges and ACS standards (CH.IX.B).

Content

Ground-Based Navigation Systems

VOR (VHF Omnidirectional Range)

VOR stations broadcast 360 radials outward from the station. The VOR receiver in the helicopter determines which radial the aircraft is on by comparing the variable phase signal with the reference phase signal. VORs operate on frequencies between 108.0 and 117.95 MHz.

Station Identification: Always identify the station before use by listening to the Morse code or voice identifier. Using an unidentified VOR violates 14 CFR 91.171. ATIS frequencies often interrupt VOR identifiers every 10 seconds, which is acceptable—the station is still considered identified. If the identifier is absent entirely for more than 10 seconds, the station is unreliable or undergoing maintenance.

Course Determination: Understanding TO/FROM indicators is fundamental. The TO/FROM flag indicates whether the selected course would take you TO or FROM the station, not your relationship to it. Think of it this way: “If I fly the selected course, will I go TO the station or away FROM it?”

The CDI (Course Deviation Indicator) needle deflection represents angular deviation from the selected course. At typical VOR operational distances (30-40 NM), full-scale deflection (5 dots) represents approximately 10-12° off course, or about 10-12 NM laterally. The closer you are to the station, the narrower the course width becomes—this is why tracking becomes increasingly sensitive near the station and why VORs are less suitable for precision approaches compared to GPS.

VOR Equipment Tests (14 CFR 91.171): Commercial pilots must ensure VOR equipment accuracy. Four methods exist:

  1. VOT (VOR Test Facility): Tune to published VOT frequency. CDI should center with 360 FROM or 180 TO, within ±4°.
  2. Certified Ground Checkpoint: Published in Chart Supplement. Must be within ±4°.
  3. Certified Airborne Checkpoint: Published in Chart Supplement. Must be within ±6°.
  4. Dual VOR Cross-Check (airborne): Select the same VOR on both receivers. Bearings must agree within ±4°.

Any VOR check must be logged: date, place, bearing error, signature. The regulation requires checks within the preceding 30 days for IFR operations. While VFR commercial operations don’t legally require this, professional pilots maintain IFR-capable equipment properly. A VOT displays “VOR TEST FACILITY” or similar text on sectional charts as a boxed frequency.

VOR Interference and Limitations: VORs are line-of-sight. Terrain, distance, and altitude affect reception. Service volumes are designated as Terminal (T), Low (L), or High (H) with specific altitude/distance parameters published in the Chart Supplement. Mountainous terrain causes signal reflection (multipath interference), making CDI needles erratic.

Certain atmospheric conditions, particularly high-energy radiation events, can disrupt VOR signals. Additionally, propeller modulation can create rhythmic fluctuations in the CDI—smoothing this requires mental averaging. Wind turbine farms are increasingly causing VOR interference, with NOTAMs issued for affected areas.

DME (Distance Measuring Equipment)

DME provides slant-range distance (not ground distance) to the station. Paired with VOR, it gives precise position information. DME operates by sending interrogation pulses at 1025-1150 MHz; the ground station responds on a different frequency, and your receiver calculates distance based on round-trip time.

At altitude directly over a station, DME reads altitude in nautical miles. Example: At 6,000 feet AGL over a station, DME reads approximately 1.0 NM (6,000 ft ÷ 6,076 ft/NM). This becomes significant when determining station passage.

NDB (Non-Directional Beacon) and ADF

NDΒs broadcast in the 190-535 kHz range. The ADF (Automatic Direction Finder) needle points toward the station regardless of aircraft heading. While increasingly rare, some commercial helicopter operations still use NDBs for offshore platforms or remote locations.

NDBs are susceptible to atmospheric interference, particularly thunderstorms. Precipitation static causes needle fluctuations. Coastal refraction at dawn and dusk bends signals, creating bearing errors. Night effect (skywave propagation) makes NDBs unreliable at night beyond 30-50 NM.

Satellite-Based Navigation Systems

GPS (Global Positioning System)

GPS determines position through trilateration using signals from multiple satellites. A minimum of four satellites provides 3D position (latitude, longitude, altitude). The system is incredibly accurate—typically within 10 meters laterally.

Approved GPS Uses (14 CFR 91.205): Panel-mounted IFR-approved GPS can be used for VFR and IFR navigation. Portable GPS units (tablets, handhelds) are NOT approved as primary navigation equipment for IFR but are acceptable for VFR situational awareness. Commercial pilots conducting VFR operations may use portable GPS, but must maintain pilotage and dead reckoning proficiency as primary methods.

TSO-C129/C145/C146 Equipment: These Technical Standard Orders define GPS certification levels. TSO-C129 is basic GPS. TSO-C145/C146 are WAAS (Wide Area Augmentation System)-enabled, providing significantly greater accuracy and integrity monitoring. WAAS uses ground reference stations and geostationary satellites to correct GPS errors, achieving accuracy within 3 meters laterally.

Database Management: IFR-approved GPS units use navigation databases that must be current (14 CFR 91.175 and 91.511 for 135 operations). The 28-day AIRAC (Aeronautical Information Regulation And Control) cycle governs updates. VFR-only operations don’t legally require current databases, but professional practice demands it—obstacle data, airport information, and airspace changes occur frequently.

Pilots must verify database effective dates before flight. Using an expired database for IFR is a violation. For VFR commercial operations, an expired database creates risk if airspace boundaries, frequencies, or airport data have changed.

RAIM (Receiver Autonomous Integrity Monitoring): Non-WAAS GPS receivers use RAIM to verify signal integrity by comparing satellite signals against each other. RAIM requires five satellites in view (four for position, one for checking). RAIM failure warnings indicate unreliable GPS guidance.

WAAS-enabled GPS has continuous integrity monitoring and doesn’t require separate RAIM—the WAAS network provides this function. When operating with non-WAAS GPS for IFR, pilots must check RAIM availability predictions before flight. VFR operations should still monitor RAIM status as good practice.

GPS Limitations: GPS signals are relatively weak and susceptible to interference. Military jamming exercises (published via NOTAM) can deny GPS service in large areas. Solar storms disrupt satellite signals. Urban canyons and terrain masking block satellite reception. Pilots must maintain proficiency in pilotage and dead reckoning as backup methods.

GPS provides “nice-to-know” information but can become a distraction. Continuously staring at the GPS display while ignoring outside visual references defeats VFR principles. Think of GPS as confirmation, not replacement, of pilotage skills.

Radar Assistance to VFR Aircraft

ATC Radar Services

ATC radar provides two primary services to VFR aircraft: traffic advisories and safety alerts. These services are workload-permitting—IFR aircraft have priority. Understanding this prevents complacency.

Radar Limitations: Primary radar detects aircraft by reflected radio waves but shows only position, not altitude. Secondary radar (beacon) interrogates transponders to obtain altitude and identification. Radar coverage is line-of-sight and altitude-dependent. Low-altitude operations, particularly in mountainous terrain, often operate below radar coverage.

Radar updates occur every 4.8 seconds in terminal areas and up to 12 seconds in en route environments. At 120 knots groundspeed, a helicopter travels 0.4 NM between updates—targets can move significantly before the controller sees the update.

VFR Flight Following: Requesting traffic advisories from Approach Control or Center enhances safety. Controllers provide traffic calls (“Traffic, 2 o’clock, 3 miles, altitude indicates 2,500”) workload permitting. The phraseology “altitude indicates” means Mode C reported altitude, which may be inaccurate due to altimeter setting differences or equipment errors.

Pilots must understand that receiving flight following doesn’t relieve responsibility for see-and-avoid (14 CFR 91.113). Controllers may not call all traffic—they’re not required to for VFR aircraft, and they may not see targets without transponders or below radar coverage.

Communication Procedures: Initial contact includes full callsign, position, altitude, and request. Example: “Seattle Approach, Helicopter 123AB, 15 miles south of Renton at 1,500, request flight following to Olympia.” Controllers respond with a discrete transponder code and may provide altimeter setting and initial traffic advisories.

When transitioning between sectors, controllers automatically hand you off. Pilots acknowledge frequency changes and check in with the new controller using full callsign. When terminating service, controllers say “Radar service terminated, squawk VFR, frequency change approved.” Acknowledge and switch to 1200.

Radar Approaches (PAR/ASR): While rare in the civilian world, military bases occasionally provide ASR (Airport Surveillance Radar) approaches to civil aircraft in emergencies. The controller issues heading and altitude instructions. This is not a common service but represents the highest level of radar assistance available.

Transponder and ADS-B Systems

Transponder Modes

All transponders in US airspace must be Mode C or Mode S equipped (14 CFR 91.215). Mode S is required for ADS-B Out compliance.

Transponder Regulations (14 CFR 91.215): Transponders with Mode C/S are required:

Transponder Codes:

Never accidentally set 7500, 7600, or 7700—controllers immediately respond, potentially scrambling resources. If you accidentally squawk 7700, immediately contact ATC and explain.

Transponder Altitude Reporting Accuracy: Mode C reports pressure altitude in 100-foot increments. Regulations require altitude reporting accurate within ±125 feet (14 CFR 91.217). Pilots must ensure the altimeter setting in the encoding altimeter matches current setting—failure to update creates altitude reporting errors. When ATC says “altitude indicates 2,800,” but you’re at 3,000, suspect an altimeter setting error or equipment malfunction.

ADS-B (Automatic Dependent Surveillance-Broadcast)

ADS-B Out became mandatory January 1, 2020, in airspace where transponders are required (14 CFR 91.225). ADS-B broadcasts GPS-derived position, altitude, velocity, and callsign without requiring ground interrogation. This improves traffic situational awareness and enables services like TIS-B (Traffic Information Service-Broadcast) and FIS-B (Flight Information Service-Broadcast).

ADS-B Out Requirements: Aircraft must have TSO-C166b (1090ES) or TSO-C154c (978 UAT) equipment. Helicopters typically use 978 UAT systems. The system broadcasts:

ADS-B In: While not required, ADS-B In receivers display traffic and weather information on compatible displays (EFBs, panel-mounted units). TIS-B provides radar-tracked traffic to ADS-B In equipped aircraft. FIS-B provides weather products (NEXRAD, METARs, TAFs, winds aloft, NOTAMs, AIRMETs/SIGMETs).

ADS-B Limitations: The system depends on GPS integrity. Loss of GPS means loss of ADS-B Out, potentially violating equipment requirements for certain airspace. Additionally, ADS-B In traffic displays only show aircraft broadcasting ADS-B Out or tracked by radar and uplinked via TIS-B. Not all traffic appears—aircraft without electrical systems, gliders, ultralights, and some older aircraft won’t be displayed.

Risk Management: Automation Management

Over-Reliance on Automation: Moving-map GPS displays create compelling “video game” presentations. Pilots staring at screens miss traffic, obstacles, and terrain outside. The commercial pilot must discipline themselves: brief glances at GPS, sustained attention outside.

Ryan Dale’s rule: “Spend 10% of your scan inside, 90% outside.” GPS should confirm what you already know from pilotage, not replace looking at the sectional chart draped over your knee.

Task Prioritization: Aviate, navigate, communicate remains the priority sequence. Fiddling with GPS settings while maneuvering low-level is poor decision-making. If navigation requires extensive input (re-routing, waypoint entry), climb to a safe altitude, slow down, or land to complete the task. Commercial operations demand this discipline.

Loss of Situational Awareness: Automation induces complacency. Following GPS “magenta line” guidance without crosschecking against chart-derived pilotage creates vulnerability when systems fail. Ask continuously: “Where am I? Where am I going? How will I know when I’m there?” Answer these questions using outside references, not just electronic confirmation.

Distraction Management: GPS units, EFBs, and ADS-B In traffic/weather displays generate information overload. Resist the urge to investigate every feature during flight. Pre-flight experimentation with equipment prevents in-flight distraction. During commercial operations (aerial photography, patrol, tours), workload increases dramatically—navigation must become second nature, not a task demanding continuous attention.

Risk Management: Navigation System Limitations

VOR Limitations: Aging VOR infrastructure is being decommissioned under the FAA’s VOR MON (Minimum Operational Network) program. Remaining VORs provide emergency navigation capability but are spaced wider apart. Station passage becomes more difficult to identify with DME if stations are 75+ NM apart. VOR accuracy degrades with distance—CDI sensitivity decreases, making course tracking less precise beyond 50-60 NM.

GPS Limitations and Failure Modes: GPS signal loss occurs more frequently than pilots realize. Causes include:

When GPS fails, the screen typically displays “LOI” (Loss of Integrity) or similar warnings. Non-WAAS units show “RAIM NOT AVAILABLE.” Pilots must immediately transition to pilotage/dead reckoning or, if IMC, execute lost communications procedures.

Partial Failures: GPS may degrade without complete failure. Position “jumps” (sudden incorrect position updates) indicate problems. Groundspeed displays fluctuating wildly suggest signal issues. Trust your heading indicator and chart over a malfunctioning GPS.

Risk Management: Loss of Navigation Signal

Immediate Actions:

  1. Maintain aircraft control (helicopter attitude, altitude, airspeed/rpm)
  2. Continue last known heading
  3. Increase scan outside—identify landmarks
  4. Crosscheck compass and heading indicator
  5. Refer to paper chart
  6. If available, switch to backup navigation source (second VOR, backup GPS)

VOR Signal Loss Indications: Red “OFF” flag appears, CDI and TO/FROM indicators disappear, or needle becomes erratic. Station identifier absent confirms loss. Do not attempt to navigate using unreliable signals.

GPS Signal Loss Indications: Most units display explicit warnings (“GPS NAV LOST” or “LOI”). Position freezes (lat/long stops updating). Groundspeed may freeze or display dashes. Some units revert to “dead reckoning mode” using last known position and track—this degrades rapidly in accuracy.

Recovery Procedures: Revert to pilotage. Look outside, identify landmarks, mark position on chart. Use time-speed-distance calculations. Contact ATC for assistance if needed—they can provide headings and position estimates using radar. For commercial operations, consider diverting to a nearby airport to resolve the problem rather than continuing with degraded navigation capability.

Risk Management: Electronic Flight Bag (EFB) Use

EFB Categories:

Most helicopters use Type A or B EFBs. ForeFlight, Garmin Pilot, and similar applications provide georeferenced charts, weather, airport information, and weight/balance calculations.

EFB Limitations:

Battery Life: Tablets die unexpectedly. Carry backup battery packs or ensure aircraft USB/power available. Never depart without paper chart backup for the route—when the tablet dies over unfamiliar terrain, you’re left with pilotage only, which is difficult without a chart.

Overheating: Direct sunlight causes tablets to shut down thermally, particularly in summer. Mount tablets out of direct sun or use cooling systems. Thermal shutdowns occur without warning—the screen goes black. Restarting takes several minutes, during which you’re navigating without electronic assistance.

Software Glitches: Apps freeze, crash, or display incorrect information. ForeFlight has occasionally displayed aircraft position incorrectly due to GPS errors. Crosscheck GPS-derived position against pilotage constantly.

Database Currency: EFB databases require periodic updates (subscription-based). Expired databases show outdated airspace, frequencies, airport information, and obstacles. Professional pilots maintain current databases. Check effective dates before every flight.

Distraction: EFBs offer weather radar overlays, traffic displays, terrain awareness, weight/balance calculators, document storage, and more—all accessible in flight. This creates distraction. Discipline yourself: briefed information stays briefed. Don’t investigate new weather or re-calculate weight/balance while maneuvering. Land first.

EFB Best Practices:

Maintenance of Aircraft Control During Navigation Tasks

Commercial pilots must maintain altitude within ±100 feet and heading within ±10° while performing navigation tasks (CH.IX.B). This requires scan discipline and task management.

Scan Technique: Integrate navigation system monitoring into standard helicopter scan pattern: attitude → altimeter → heading → VSI → navigation system → outside → repeat. Navigation systems receive brief glances (1-2 seconds maximum), not sustained attention.

Altitude Control: Anticipate altitude deviations before they occur. If focused on GPS waypoint entry, altitude often wanders. Set altitude alerters (if available) to provide warnings. When complex navigation tasks arise (frequency changes, waypoint modifications, course intercepts), increase altitude awareness and trim helicopter to minimize control inputs.

Heading Control: Heading discipline suffers during navigation workload. Turbulence and distraction combine to create heading deviations. Combat this by checking heading indicator every 5-10 seconds during navigation tasks. If heading wanders beyond ±5°, stop the navigation task, correct heading, then resume.

Schedule

SegmentDurationActivity
Introduction5 minObjective statement, lesson overview, relevance to commercial operations
Ground-Based Navigation30 minVOR principles, equipment, identification, tests, regulations, DME, NDB/ADF limitations
Satellite-Based Navigation25 minGPS principles, equipment certification, databases, RAIM, limitations
Radar Services15 minVFR flight following, traffic advisories, communication procedures, limitations
Transponder and ADS-B20 minModes, regulations, codes, ADS-B Out/In, TIS-B, FIS-B, limitations
Risk Management Discussion20 minAutomation management, distractions, task prioritization, signal loss, EFB use
Practical Demonstration30 minUse onboard GPS/VOR equipment, demonstrate intercepts, tracking, station passage
Skill Practice30 minStudent practices navigation system use, course intercepts, communication with ATC
Evaluation and Debrief15 minReview performance, address deficiencies, preview next lesson
Total3.0 hours

Equipment

Required References:

Training Materials:

Visual Aids:

Facilities:

Instructor Actions

  1. Begin with objective statement and relevance: “Today we’re covering navigation systems and radar services, ACS task CH.IX.B. This builds on your private pilot knowledge but adds commercial-level precision and professionalism. You’ll use these systems on every commercial flight—tours, EMS, patrol, utility work—so deep understanding isn’t optional. We’ll cover VOR, GPS, transponders, ADS-B, and radar services, then practice using our helicopter’s equipment. By the end, you’ll navigate confidently, maintain altitude within ±100 feet and heading within ±10° during navigation tasks, and handle system failures without panic.”

  2. Explain VOR fundamentals using diagrams: Draw a VOR station with radials extending outward. “VOR broadcasts 360 radials. Your receiver determines which radial you’re on by comparing two signals—variable phase and reference phase. The result is displayed as radials FROM the station, 0-360°. When you select a course on the OBS, you’re asking, ‘Which way to this course, and am I going TO or FROM the station if I fly it?’”

  3. Demonstrate TO/FROM logic with examples: Use the whiteboard to show aircraft positions. “Aircraft north of the station, OBS set to 180°. The FROM flag shows because flying 180° takes you FROM the station. Needle centered because you’re on the 360° radial, which is the 180° course FROM. Now set OBS to 360°. TO flag appears, needle centers—flying 360° takes you TO the station. The flag doesn’t tell you where you are; it tells you where the course leads.”

  4. Discuss CDI needle sensitivity: “CDI full-scale deflection is roughly 10° off course. At 30 miles, that’s 10 nautical miles laterally. Close to the station, that same 10° represents a much narrower corridor—maybe half a mile. This is why tracking becomes twitchy near the station. Don’t chase the needle; make small heading corrections and let the needle settle.”

  5. Cover VOR equipment tests thoroughly: “14 CFR 91.171 requires VOR checks within 30 days for IFR. You’re training commercially, so treat your equipment like IFR-capable. Four methods: VOT gives you 360 FROM or 180 TO within ±4°. Ground checkpoint, ±4°. Airborne checkpoint, ±6°. Dual VOR cross-check, ±4°. Log every check: date, place, bearing error, signature. Find a VOT—they’re published on sectionals as a boxed frequency—and practice this.”

  6. Explain VOR limitations clearly: “VORs are line-of-sight. Mountains block signals. Distance and low altitude reduce reception. Atmospheric interference happens. Propeller modulation causes needle fluctuations—your brain averages it out. Wind farms now disrupt VORs; NOTAMs announce affected areas. VOR MON means fewer stations, wider spacing. Stations are disappearing; GPS is the future, but VORs remain your backup when GPS fails.”

  7. Demonstrate DME operation: “DME shows slant-range distance—not ground distance—using radio pulse round-trip timing. Directly over the station at 6,000 feet AGL, DME reads 1.0 NM because 6,000 feet equals roughly one nautical mile. At distance, slant-range error becomes negligible. DME paired with VOR gives you precise position: radial and distance. Mark it on your chart; you’ve got a solid fix.”

  8. Introduce GPS principles using trilateration diagram: “GPS uses trilateration—not triangulation—with satellite signals. Four satellites minimum: three for 2D position, fourth for altitude and timing correction. GPS accuracy is phenomenal, typically within 10 meters. WAAS improves this to 3 meters laterally by correcting errors using ground stations. Your panel GPS or tablet GPS uses these signals to show position, groundspeed, track, and course guidance.”

  9. Explain GPS equipment certification: “TSO-C129 is basic GPS. TSO-C145/C146 is WAAS-enabled. Panel-mounted IFR GPS meets these standards. Your iPad? Not certified for IFR, but perfectly legal for VFR situational awareness. Databases must be current for IFR (28-day AIRAC cycle). For VFR commercial work, an expired database is risky—airspace changes, obstacle data, frequencies update constantly. Professional pilots keep databases current.”

  10. Discuss RAIM in detail: “Non-WAAS GPS uses RAIM to check signal integrity by comparing satellite signals. Requires five satellites: four for position, one for verification. RAIM failure means unreliable GPS—don’t trust it. WAAS GPS has continuous integrity monitoring, so RAIM isn’t separately required. Monitor for ‘LOI’ or ‘RAIM NOT AVAILABLE’ warnings. When they appear, revert to pilotage immediately.”

  11. Address GPS limitations and vulnerabilities: “GPS signals are weak and easily jammed. Military exercises (published NOTAMs) deny GPS service over large areas—hundreds of miles sometimes. Solar storms disrupt satellites. Urban canyons and terrain block reception. GPS is amazing, but it’s not infallible. Maintain pilotage proficiency. GPS confirms what you see outside, not the other way around.”

  12. Explain radar services and limitations: “ATC radar provides traffic advisories workload-permitting. VFR flight following is a service, not a right—IFR aircraft have priority. Radar updates every 4.8 seconds in terminal areas, 12 seconds en route. At 120 knots, you move 0.4 NM between updates. Controllers may not see all traffic—targets without transponders, low-altitude traffic below radar coverage, or aircraft masked by terrain won’t appear. You’re still responsible for see-and-avoid under 14 CFR 91.113.”

  13. Demonstrate proper communication procedures: Use the radio (or simulate). “Initial contact: ‘Seattle Approach, Helicopter 123 Alpha Bravo, 15 miles south of Renton at 1,500, request flight following to Olympia.’ Controller responds with squawk code, altimeter, possible traffic. Acknowledge clearly: ‘Helicopter 23 Alpha Bravo, squawk 4521, altimeter 30.12.’ On frequency changes: ‘Seattle Approach, Helicopter 23 Alpha Bravo, level 1,500.’ When terminated: ‘Helicopter 23 Alpha Bravo, radar service terminated, squawk VFR, frequency change approved.’ You respond: ‘23 Alpha Bravo, squawk 1200, good day.’”

  14. Cover transponder modes and regulations: “Mode A: code only. Mode C: code plus altitude. Mode S: code, altitude, unique 24-bit address enabling ADS-B and data link. Mode C minimum required under 14 CFR 91.215 in Class A, B, C, above 10,000 MSL in Class E (excluding below 2,500 AGL), and inside Mode C veils—30 NM rings around Class B primary airports, surface to 10,000 MSL.”

  15. Emphasize transponder code discipline: “1200 is VFR. 7500 is hijack. 7600 is lost comms. 7700 is emergency. Never fat-finger 7500—controllers scramble resources instantly. If you accidentally squawk 7700, immediately contact ATC: ‘Approach, 23 Alpha Bravo, inadvertent 7700 squawk, no emergency.’ Altitude reporting must be accurate within ±125 feet per 14 CFR 91.217. If ATC says your altitude is off, suspect altimeter setting error or equipment malfunction.”

  16. Explain ADS-B Out and In thoroughly: “ADS-B Out became mandatory January 1, 2020, in transponder-required airspace (14 CFR 91.225). Your helicopter broadcasts GPS position, altitude, velocity, callsign—no ground interrogation needed. TSO-C154c (978 UAT) or TSO-C166b (1090ES) required; helicopters typically use 978 UAT. ADS-B In receives traffic (TIS-B) and weather (FIS-B) on your display—iPad, panel-mounted, whatever. Not all traffic appears: aircraft without ADS-B Out, no electrical systems, or outside radar/ADS-B coverage won’t show. Don’t rely solely on ADS-B traffic displays.”

  17. Discuss automation management risks: “GPS moving-map displays are hypnotic. You stare at the screen, miss traffic, obstacles, terrain. Ryan Dale’s rule: 10% scan inside, 90% outside. GPS confirms pilotage; it doesn’t replace it. If entering waypoints, climbing, slowing, or landing is safer than heads-down button-pushing in the weeds. Aviate, navigate, communicate—that order always.”

  18. Address task prioritization and distraction: “Commercial operations add workload: passengers talking, cameras running, external loads swinging. Navigation must become automatic—brief glances, immediate comprehension. Pre-flight all GPS settings. Don’t experiment in flight. Resist investigating new weather, rerouting, or calculating weight/balance while flying low. Climb, slow, or land first.”

  19. Explain loss of situational awareness risks: “Following the magenta line without crosschecking chart position creates vulnerability. When GPS fails, you’re lost unless you’ve maintained pilotage awareness. Ask constantly: ‘Where am I? Where am I going? How will I know?’ Answer using outside references first, GPS confirmation second. If you can’t answer without GPS, you’ve lost situational awareness—land and reset.”

  20. Cover signal loss procedures in detail: “GPS fails more often than expected. ‘LOI’ or ‘RAIM NOT AVAILABLE’ warnings appear. Position freezes. Groundspeed displays dashes. Immediate actions: maintain helicopter control, continue last heading, increase outside scan, identify landmarks, reference paper chart, switch to backup nav if available. VOR failure shows red OFF flag, erratic needle, missing identifier. Never navigate using failed equipment. Contact ATC for assistance if needed—they can provide position estimates and headings using radar.”

  21. Discuss EFB use, limitations, and best practices: “Your iPad is a Type A or B EFB—portable, not certified. Incredible capability: georeferenced charts, weather overlays, traffic, terrain awareness, weight/balance, document storage. Also incredible distraction and failure potential. Batteries die. Screens overheat in sun and shut down. Apps crash. Databases expire. Carry paper chart backup always. Dim screen to reduce distraction and extend battery. Update databases regularly. Pre-brief all needed features before flight. Don’t investigate new information while maneuvering.”

  22. Demonstrate onboard navigation equipment in the helicopter: Walk to the helicopter with the student. “This is our GPS unit [point to panel]. Power on, wait for satellite acquisition. See ‘GPS NAV’—we’re ready. This is our VOR receiver [point to unit]. Tune Seattle VOR 116.8, identify the Morse code [listen together]—‘SEA’ in Morse. Twist the OBS; watch TO/FROM flag and needle. Our transponder here [point]—squawk code, mode selector. Ensure Mode C or S selected. ADS-B Out status light shows green; we’re broadcasting.”

  23. Demonstrate course intercept and tracking: “We’re currently on the 180° radial FROM Seattle VOR, 25 miles. I want to intercept the 160° radial inbound. I’ll turn to intercept heading 340° [turn helicopter]. Watch the needle: right of center, moving left. As the needle centers, I’ll turn to track 340° [demonstrate]. Needle centered, FROM flag shows, tracking inbound. This is a 20° intercept angle; a 45° intercept is more aggressive for parallel courses. You’ll practice both.”

  24. Demonstrate station passage: “Approaching the station, watch DME count down: 3 miles, 2, 1. CDI becomes increasingly sensitive—don’t chase it. At station passage, TO/FROM flag flips FROM to TO, or disappears momentarily. Needle swings rapidly. If we’re directly over the station, DME reads our altitude in nautical miles. There—flag flipped, needle swung. We’ve passed the station. Select outbound course 250°, turn to intercept, track outbound.”

  25. Demonstrate GPS navigation: “Our GPS is set for direct-to Paine Field. Current position shows here [point to screen], destination here, magenta line is desired track. We’re 0.2 miles right of course; CDI needle shows right deflection. I’ll turn left 10° to intercept. As the needle centers, I’ll correct heading to track. Groundspeed, ETE, and bearing to waypoint all displayed. Verify this against chart position—see, we’re crossing this lake [point to chart and outside reference], which matches our GPS position. Crosscheck constantly.”

  26. Demonstrate loss of GPS signal recovery: Simulate GPS failure (turn off GPS or simulate screen failure). “GPS failed—screen blank. Immediate actions: maintain control, note last heading, look outside for landmarks. I see that ridge [point], and this town [point]. Mark position on chart here [show]. Continue on heading 090° toward destination. Calculate time remaining: 20 miles at 90 knots is 13 minutes. I’ll contact ATC for assistance [simulate call]: ‘Seattle Approach, Helicopter 23 Alpha Bravo, GPS failure, request position estimate and vectors.’”

  27. Demonstrate proper ATC communication during flight following: Simulate radio calls. “We’ll request flight following. ‘Seattle Approach, Helicopter 123 Alpha Bravo, 10 miles south of Boeing Field at 1,500, request flight following to Olympia.’ Controller responds [simulate]: ‘Helicopter 123 Alpha Bravo, Seattle Approach, squawk 4532, altimeter 30.15.’ We respond: ‘Helicopter 23 Alpha Bravo, squawk 4532, 30.15.’ Controller calls traffic [simulate]: ‘Helicopter 23 Alpha Bravo, traffic 2 o’clock, 5 miles, altitude indicates 2,000.’ We respond: ‘23 Alpha Bravo, looking.’ Always acknowledge traffic calls even if you don’t spot the traffic.”

  28. Assign student practice tasks: “Now it’s your turn. Tune Seattle VOR, identify it, and set up to intercept the 200° radial inbound using a 45° intercept. Once established, track inbound, maintaining altitude within ±100 feet and heading within ±10°. Call out station passage. Then use the GPS to navigate direct to Renton, tracking the course within 0.5 NM. I’ll monitor and provide feedback.”

  29. Monitor student performance closely: Observe the student’s scan, course interception technique, altitude/heading control, and communication. Provide real-time feedback: “Good intercept angle—45° is aggressive enough. Watch your altitude; you’re 150 feet high—bring it back within 100. Needle’s centering; start your turn to intercept the course. Good, tracking inbound. Call station passage when the flag flips.”

  30. Introduce failures during practice: Simulate GPS signal loss or VOR failure (cover the display or turn off equipment). “Your GPS just failed—what do you do?” Evaluate the student’s immediate actions: maintains control, continues heading, looks outside, references chart, communicates. Provide feedback: “Good, you maintained control and went immediately to pilotage. Next time, announce your intentions—tell me what you’re doing so I know your plan.”

  31. Debrief performance thoroughly: After practice, review each element. “You intercepted the radial correctly, tracked within tolerances, and identified station passage. Altitude control was good—within ±50 feet most of the time. Heading wandered once to 15° off when you were tuning the GPS; that exceeded the ±10° standard. Fix: pause navigation tasks, correct heading, then resume. GPS navigation was solid—stayed within 0.5 NM of course throughout. When I simulated GPS failure, you handled it well: maintained control, reverted to pilotage, and communicated. That’s exactly right.”

  32. Address deficiencies specifically: If the student struggled: “Your altitude control needs work—you exceeded ±100 feet multiple times while focused on the GPS. Practice split-scan: quick glance at GPS, longer scan of flight instruments and outside. Trim helps—reduce control inputs during navigation tasks. Let’s practice altitude-hold while performing a GPS direct-to entry before next lesson.”

  33. Connect to commercial pilot responsibilities: “Commercial operations demand precision. Tours, EMS, patrol—you’re navigating while managing passengers, mission tasks, and external pressures. Navigation must be second nature. These systems enhance safety and efficiency, but only if you use them correctly and maintain manual navigation skills as backup. Today’s lesson builds the foundation for complex commercial missions.”

  34. Preview the next lesson: “Next lesson, we’re covering pilotage and dead reckoning. You’ll navigate an entire cross-country using chart, compass, and clock—no GPS, no VOR. This reinforces backup skills for when electronics fail. We’ll calculate groundspeed, fuel consumption, and ETAs manually. It’s old-school, but it’s what saves you when the magic boxes die.”

Student Actions

  1. Listen actively during ground instruction: Take notes on VOR principles, GPS operation, transponder regulations, ADS-B requirements, radar services, and risk management items. Ask clarifying questions immediately: “If RAIM fails, does that mean GPS position is wrong?” or “What’s the difference between TIS-B and FIS-B?”

  2. Participate in whiteboard examples: When the instructor draws VOR radials or demonstrates TO/FROM logic, work through examples. “If I’m southwest of the station and select 045° on the OBS, what flag shows?” Think through the logic before the instructor answers.

  3. Study FAR references: Read 14 CFR 91.171 (VOR checks), 91.215 (transponder), 91.217 (altitude reporting accuracy), 91.225 (ADS-B), and AIM Chapter 1 Section 1 (navigation aids). Highlight key points: VOR check tolerances, transponder-required airspace, ADS-B equipment standards.

  4. Examine navigation equipment on the helicopter: Identify VOR receiver, GPS unit, transponder, and ADS-B status indicators. Power on the GPS and observe satellite acquisition. Tune a VOR station, listen to the identifier, and practice twisting the OBS to observe TO/FROM flag changes. Ask: “How do I know if this VOR receiver passed its 30-day check?”

  5. Demonstrate VOR tuning and identification: Tune Seattle VOR 116.8 (or applicable local VOR). Listen for “SEA” Morse code identifier or voice announcement. Verify the identifier matches before using the station. Explain: “I’ve identified Seattle VOR by Morse code. The identifier matches the frequency published on the chart.”

  6. Set up a VOR course intercept: Select the desired radial on the OBS. Determine intercept heading (30-45° depending on distance from course). Turn to intercept heading and monitor CDI needle movement. As the needle centers, turn to the inbound/outbound course heading and track. Maintain altitude within ±100 feet and heading within ±10°.

  7. Track a VOR course accurately: Once established on course, make small heading corrections (±5°) to keep the CDI needle centered. Avoid chasing the needle—make a correction, wait for the needle to respond, then assess. Account for wind drift by adjusting heading slightly into the wind. Maintain altitude within ±100 feet throughout.

  8. Identify station passage correctly: Call out station passage when the TO/FROM flag flips or disappears, CDI needle swings rapidly, and DME (if available) reaches minimum or reads altitude in nautical miles. Explain: “TO/FROM flag just flipped from TO to FROM, and the needle swung—we’ve passed the station.”

  9. Demonstrate GPS direct-to navigation: Enter a destination waypoint (airport or landmark). Activate direct-to function. Observe the magenta line, bearing, distance, and ETE on the display. Turn to intercept the desired track. Monitor CDI or course deviation display, making heading corrections to track within 0.5 NM of course. Maintain altitude within ±100 feet and heading within ±10° while navigating.

  10. Crosscheck GPS position against pilotage: While using GPS, continuously verify position using outside landmarks and chart. Example: “GPS shows us crossing this lake; I see the lake outside. Chart position matches.” If GPS position seems incorrect, trust pilotage first and investigate GPS anomalies.

  11. Use the transponder correctly: Set the assigned squawk code accurately. Ensure Mode C or Mode S is selected. Verify altitude readout displays (if available on the unit). When ATC assigns a new code, read back the code and set it immediately. If ATC reports altitude discrepancy, check altimeter setting and consider equipment malfunction.

  12. Respond to simulated signal loss immediately: When the instructor simulates GPS or VOR failure, execute proper procedures: maintain aircraft control, note last known heading, increase scan outside, identify landmarks, mark position on chart, consider backup navigation (switch to VOR if GPS failed, or vice versa), communicate situation to ATC or instructor. Demonstrate situational awareness by explaining position and intended navigation method.

  13. Practice communication procedures with ATC (simulated or actual): Request flight following using proper format: “Seattle Approach, Helicopter 123 Alpha Bravo, 15 miles south of Renton at 1,500, request flight following to Olympia.” Acknowledge instructions clearly: “Helicopter 23 Alpha Bravo, squawk 4532, altimeter 30.15.” Respond to traffic advisories: “23 Alpha Bravo, looking for traffic.” Execute frequency changes: “23 Alpha Bravo, leaving your frequency.” Acknowledge radar service termination: “23 Alpha Bravo, squawk 1200, good day.”

  14. Maintain altitude and heading tolerances during navigation tasks: While performing GPS entries, VOR tuning, or communicating with ATC, maintain altitude within ±100 feet and heading within ±10°. Trim the helicopter to minimize control inputs. If altitude or heading deviates beyond tolerances, stop the navigation task, correct the deviation, then resume.

  15. Demonstrate proper EFB use: Use the EFB (iPad/tablet) to display georeferenced chart, verify aircraft position, check airport information, and brief weather. Demonstrate discipline: brief glances only, no sustained attention on the screen. If entering a waypoint or investigating weather requires extended screen time, announce intention to pause flight duties or request the instructor to take controls. Keep paper chart accessible as backup.

  16. Ask questions throughout practical demonstration: When uncertain about a procedure, indication, or regulation, ask immediately. Examples: “Why is the CDI so sensitive near the station?” or “What does this ‘RAIM NOT AVAILABLE’ warning mean?” or “How do I know if my ADS-B Out is working?”

  17. Self-critique performance during debrief: Honestly assess your performance. “I let altitude wander to 150 feet high when I was setting up the GPS, and my heading went 15° off when tuning the VOR—both exceeded standards. I need to pause navigation tasks and correct flight parameters before continuing.” This demonstrates self-awareness and commitment to improvement.

  18. Identify personal risk management strategies: Explain how you’ll manage automation reliance, distractions, and task prioritization during commercial operations. Example: “I’ll spend more time outside than on the GPS. I’ll pre-brief all GPS waypoints so I’m not heads-down programming in flight. If passengers distract me, I’ll climb to a safer altitude before dealing with them.”

  19. Review ACS standards for this task: Study CH.IX.B knowledge, risk management, and skill elements. Confirm understanding: “I need to use an airborne electronic navigation system, determine position, intercept and track a course, recognize station passage, handle signal loss, use proper ATC communication, and maintain altitude ±100 feet and heading ±10°. Did I demonstrate all of these?”

  20. Prepare for next lesson: Review pilotage and dead reckoning techniques. Study time-speed-distance calculations, fuel burn planning, and chart interpretation. Practice measuring courses and distances on a sectional chart. Mentally prepare to navigate without GPS or VOR—pure manual navigation using chart, compass, and clock.

Completion Standards

The lesson is complete when the student demonstrates proficient knowledge and skill in navigation systems and radar services, meeting all CH.IX.B ACS standards:

Knowledge Standards:

  1. Ground-Based Navigation: The student explains VOR principles, including radial orientation, TO/FROM flag logic, CDI needle sensitivity relative to distance, and station passage identification. The student describes VOR equipment check requirements (14 CFR 91.171): VOT (±4°), ground checkpoint (±4°), airborne checkpoint (±6°), dual VOR cross-check (±4°), and logging procedures (date, place, bearing error, signature). The student identifies VOR limitations: line-of-sight, distance/altitude constraints, atmospheric interference, propeller modulation effects, terrain masking, wind turbine interference, and VOR MON decommissioning impacts. The student explains DME slant-range operation and position-fixing using radial/distance. The student describes NDB/ADF operation, limitations (thunderstorm interference, coastal refraction, night effect), and decreasing prevalence.

  2. Satellite-Based Navigation: The student explains GPS trilateration principles (minimum four satellites for 3D position), typical accuracy (10 meters lateral, 3 meters with WAAS), and certification standards (TSO-C129 basic, TSO-C145/C146 WAAS). The student describes navigation database requirements (28-day AIRAC cycle for IFR, currency for commercial VFR professionalism), database effective date verification, and subscription management. The student explains RAIM (requires five satellites, integrity checking, “RAIM NOT AVAILABLE” warnings) versus WAAS continuous integrity monitoring. The student identifies GPS limitations: weak signals, military jamming (NOTAM’d), solar storms, terrain/building masking, urban canyon effects, and partial failure modes (position jumps, frozen data). The student differentiates panel-mounted IFR GPS (certified) from portable GPS/EFB (VFR situational awareness only, not approved as sole navigation source for IFR).

  3. Radar Services: The student explains ATC radar operation (primary radar detects position, secondary radar interrogates transponders for altitude/ID), update rates (4.8 seconds terminal, 12 seconds en route), and coverage limitations (line-of-sight, altitude-dependent, terrain masking). The student describes VFR flight following procedures: requesting service with full callsign/position/altitude/destination, receiving discrete squawk code, acknowledging traffic advisories, frequency changes during handoffs, and service termination. The student explains that radar services are workload-permitting, IFR aircraft have priority, and pilots retain see-and-avoid responsibility under 14 CFR 91.113 regardless of radar service use. The student identifies radar limitations: not all traffic visible (non-transponder equipped, below coverage, terrain masked), controller workload affects service quality, and updates lag real-time aircraft movement.

  4. Transponder and ADS-B: The student describes transponder modes: Mode A (code only), Mode C (code plus pressure altitude), Mode S (code, altitude, 24-bit address enabling ADS-B/TIS). The student explains 14 CFR 91.215 transponder requirements: Class A, B, C airspace; Class E above 10,000 MSL (excluding below 2,500 AGL); within 30 NM Mode C veil (surface to 10,000 MSL). The student identifies standard codes: 1200 (VFR), 7500 (hijack), 7600 (lost comms), 7700 (emergency), and explains consequences of inadvertent emergency code selection. The student explains altitude reporting accuracy requirement (±125 feet per 14 CFR 91.217) and troubleshooting altitude discrepancies (altimeter setting errors, equipment malfunction). The student describes ADS-B Out mandate (14 CFR 91.225, effective January 1, 2020, required in transponder-required airspace), TSO standards (TSO-C154c for 978 UAT, TSO-C166b for 1090ES), broadcast data elements (GPS position, pressure altitude, velocity, callsign, emitter category). The student explains ADS-B In capabilities: TIS-B (radar traffic uplinked to ADS-B equipped aircraft), FIS-B (weather products: NEXRAD, METARs, TAFs, winds aloft, NOTAMs, AIRMETs/SIGMETs). The student identifies ADS-B limitations: dependence on GPS integrity, incomplete traffic picture (non-ADS-B aircraft only visible if radar-tracked and uplinked via TIS-B), no display of non-electrical aircraft (gliders, ultralights, older aircraft).

Risk Management Standards:

  1. Automation Management: The student explains risks of over-reliance on GPS/automation: loss of pilotage skills, heads-down navigation, missed traffic/obstacles/terrain. The student articulates the “10% inside, 90% outside” scan discipline for GPS/EFB use. The student describes strategies to prevent automation complacency: GPS confirms pilotage (not replaces it), continuous crosscheck of GPS position against chart and outside landmarks, maintaining manual navigation proficiency as backup.

  2. Task Prioritization and Distraction Management: The student explains “aviate, navigate, communicate” priority sequence and demonstrates application: stopping navigation tasks to correct altitude/heading deviations first. The student identifies distraction sources: GPS programming, EFB features (weather, traffic, weight/balance), passenger interactions, mission tasks (photography, external loads). The student articulates mitigation strategies: pre-briefing all GPS/EFB settings before flight, climbing to safe altitude or landing before performing complex navigation tasks, delegating non-essential tasks during critical phases.

  3. Loss of Situational Awareness: The student explains how “magenta line” following without chart crosschecking creates vulnerability when systems fail. The student demonstrates continuous self-questioning: “Where am I? Where am I going? How will I know when I’m there?” answered using outside references first, GPS confirmation second. The student articulates recovery from disorientation: maintain aircraft control, note heading, identify landmarks, mark position on chart, contact ATC for assistance if needed.

  4. Navigation System Limitations: The student identifies specific VOR limitations (aging infrastructure, VOR MON wider spacing, accuracy degradation beyond 50-60 NM, signal unreliability near thunderstorms) and GPS limitations (jamming, solar storms, masking, partial failures with position jumps or frozen data). The student explains appropriate system selection based on phase of flight, backup navigation availability, and system health monitoring.

  5. Signal Loss Recognition and Response: The student describes GPS failure indications (“LOI,” “RAIM NOT AVAILABLE,” position freeze, groundspeed dashes/freeze, dead reckoning mode activation) and VOR failure indications (red OFF flag, CDI/TO-FROM disappearance, needle erratic behavior, identifier absent). The student demonstrates immediate actions for signal loss: maintain aircraft control, continue last known heading, increase outside scan, identify landmarks, reference paper chart, switch to backup navigation source if available, contact ATC for position/heading assistance. The student explains why unreliable navigation signals must never be used for navigation (“If the flag’s not right, the course ain’t right”).

  6. EFB Use and Limitations: The student identifies EFB failure modes: battery depletion, thermal shutdown in sunlight, software crashes, GPS position errors, database expiration. The student explains mitigation strategies: carry backup battery, mount EFB out of direct sun, maintain current databases, carry paper chart backup for planned route. The student demonstrates EFB discipline: brief glances only, pre-briefed features only (no in-flight experimentation), pause flight duties before extended screen time, dim screen to reduce distraction and extend battery.

Skill Standards:

  1. Airborne Electronic Navigation System Use: The student demonstrates proficient operation of the helicopter’s installed GPS and/or VOR equipment. For VOR: tunes correct frequency, identifies station via Morse code or voice, selects desired course on OBS, interprets TO/FROM flag and CDI needle correctly. For GPS: enters destination waypoints, activates direct-to or flight plan navigation, interprets bearing/distance/ETE displays, monitors course deviation (CDI or highway-in-the-sky display). The student operates transponder correctly: sets assigned squawk codes accurately, ensures Mode C/S selected, monitors altitude reporting (if display available).

  2. Position Determination: The student accurately determines aircraft position using navigation systems. For VOR/DME: identifies radial (using TO/FROM and OBS setting) and distance, plots position on chart. For GPS: reads latitude/longitude or references GPS position against georeferenced chart display, crosschecks position against outside landmarks and paper chart. Position determination accuracy: within 1 NM of actual position under normal conditions.

  3. Course Intercept and Tracking: The student intercepts a VOR radial or GPS course using appropriate intercept angles (30-45° depending on distance from course and proximity to station/waypoint). The student tracks the course accurately, maintaining CDI needle within ±1 dot (VOR) or within 0.5 NM of course (GPS) during stabilized tracking. The student makes timely heading corrections for wind drift, demonstrating smooth course tracking without excessive heading changes or needle chasing.

  4. Station/Waypoint Passage Recognition: The student accurately identifies VOR station passage: TO/FROM flag flip or momentary disappearance, CDI needle rapid swing, DME minimum or reading altitude in nautical miles. The student verifies passage by announcing: “Station passage now—flag flipped FROM to TO, needle swung.” For GPS waypoint passage: the student recognizes waypoint alert, distance counting to zero, course/bearing changes if navigating a multi-leg flight plan, and announces: “Waypoint passage, Paine Field, switching to next leg.”

  5. Navigation Signal Loss Recognition and Action: When navigation signal is lost (simulated or actual), the student immediately recognizes the failure (GPS “LOI” warning, VOR OFF flag, CDI/TO-FROM disappearance, identifier absent, erratic indications) and takes appropriate action: maintains aircraft control first, continues last known heading, increases outside scan, identifies landmarks and marks position on chart, switches to backup navigation source (if available), communicates situation to ATC or instructor (“GPS signal lost, reverting to pilotage, continuing on heading 090°”). The student does not attempt to navigate using unreliable signals.

  6. Communication Procedures with Radar Services: The student demonstrates proper ATC communication for VFR flight following: initial request includes full callsign, position, altitude, destination; acknowledges squawk code and altimeter setting accurately; responds to traffic advisories (“23 Alpha Bravo, looking” or “traffic in sight”); executes frequency changes promptly with check-in on new frequency; acknowledges service termination. All communications are clear, concise, and professional. The student copies complex instructions correctly and reads back clearances/instructions accurately.

  7. Altitude and Heading Maintenance During Navigation Tasks: Throughout all navigation system operation (VOR tuning, GPS programming, course intercepts/tracking, communication with ATC), the student maintains altitude within ±100 feet of assigned altitude and heading within ±10° of assigned or desired heading. If altitude or heading deviates beyond these tolerances, the student recognizes the deviation, pauses the navigation task, corrects flight parameters to within tolerances, then resumes navigation. This demonstrates proper task prioritization and scan discipline consistent with commercial pilot standards per ACS CH.IX.B.

Evaluation Criteria:

The student meets CH.IX.B completion standards when they:

Completion is demonstrated when the student performs all tasks safely, competently, and consistently within ACS standards for commercial pilot operations (CH.IX.B) without instructor intervention.

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

Download the Free CFI Lesson Plan Binder