Lost-Comm Realities

Modern electronics almost relegate lost-comm concerns to a thing of the past. But what should you do if “almost” comes to your flight?

Mark Kolber

Sunday, December 15, 2024 at 08:00 AM ET

Verified

Screenshot

Key Takeaways:

The FAA regulation §91.185 for IFR lost communications is outdated, often mandating impractical routes and altitudes (e.g., delaying approach, maintaining high altitude) that conflict with modern ATC practices and expectations.
Air Traffic Control (ATC) prioritizes pilot safety and expeditious resolution of lost comms, treating it as an emergency and expecting pilots to get down safely and efficiently, rather than strictly adhering to the regulation's delayed procedures.
Pilots are encouraged to use good judgment, as per AIM 6-4-1, to resolve lost comms situations safely and efficiently, even if it means deviating from the literal interpretation of §91.185, as ATC does not expect or want prolonged, rule-mandated delays.
In a lost comms scenario, a pilot should prioritize safe and expeditious landing, whether by diverting to a suitable airport or flying a direct approach to their destination without unnecessary delays, which aligns better with ATC's operational needs and ensures safety.

See a mistake? Contact us.

You are IFR from Republic Airport in Farmingdale, New York (KFRG), to Norwood, Massachusetts (KOWD), in your Piper Arrow. It’s IMC all the way. The clearance is a common one. Initial vectors to Bridgeport VOR (BDR), direct to Hartford VOR (HFD), then to FROSTY and WOONS intersections northwest of the Providence Class C. Although the flight should take only a bit over an hour, it is your practice to round up, so you filed 2 hours as your ETE.

Departing, you enter the clouds at 900 feet AGL. As the forecasts predict, your 7000-foot cruise altitude keeps you in a solid stratus layer. Soon after turning at Hartford, you hear nothing but static from your GTN 650. Your old KX 155 isn’t any better. Changing frequencies doesn’t help. Guard on 121.5 is silent. Nothing from nearby AWOS so it’s you and not them. Fortunately, the nav side of both units seems to be unaffected—so far. You figure maybe it will clear up. It doesn’t.