FCC is p!ssed- (Another 121.5 Thread)
#41
Gets Weekends Off
Joined APC: Oct 2016
Posts: 846
Doesn't matter, it is not an emergency. For example, the lost comm procedure only has you squawk 7600. It used to be back in olden times you squawked 7700 for one minute (an emergency) then 7600 for 15 minutes, then back to 7700. By changing this 15 or 20 years ago, they are clearly signalling it is no longer to be considered an emergency.
The FAA doesn't make policy on what is allowed on 121.5, the FCC does under 87.173. Their policy plainly says "121.500 MHz be used solely for emergency and distress purposes. The FAA continually monitors 121.500 MHz and treats any distress call received as an emergency to be investigated immediately."
Therefore controllers will be in violation for trying to locate airplanes who are not responding to their assigned frequencies, its just not an emergency.
I think they should change the rules to allow controllers to locate aircraft on 121.5 but I don't really have a say.
The FAA doesn't make policy on what is allowed on 121.5, the FCC does under 87.173. Their policy plainly says "121.500 MHz be used solely for emergency and distress purposes. The FAA continually monitors 121.500 MHz and treats any distress call received as an emergency to be investigated immediately."
Therefore controllers will be in violation for trying to locate airplanes who are not responding to their assigned frequencies, its just not an emergency.
I think they should change the rules to allow controllers to locate aircraft on 121.5 but I don't really have a say.
This is probably no longer the case in a post 9/11 world.
#42
It doesn't say you have to remain on guard to your own peril. If you need to communicate with other sources using VHF 2, then you do so. Then return to guard.
CBreezy hit it. We are required to maintain a continuous link with dispatch via ACARS or other less capable means for the very scenario you brought up. It's their job AND the crew's to maintain awareness of changing wx conditions at destinations and alternates, making changes as necessary.
Gaining SA on deteriorating weather via happenstance by overhearing information on AIRINC that happens to affect you isn't my idea of a plan. Dispatch should be doing their job but as you said, it's wise to cover one's own ass. Any competent crew should be seeking that information anyway as a matter of normal procedure, not because they get lucky on VHF 2. ACARS, ATIS, AIRINC, FSS, SATPHONE..... whatever it takes to get the information one needs to make the best decision and complete the flight safely.
If that means leaving guard to accomplish it, then so be it. Just return when you're finished. I could even agree with the decision to choose AIRINC over guard during rapidly changing wx conditions for a portion of the flight - just not as a matter of course for every flight. I doubt that's necessary with most aircraft these days equipped with ACARS. You do not have the option to disregard procedural directives and continuously monitor something else, when your aircraft comm systems allow compliance, just because you might hear something useful on another freq.
Here's a litmus test for you: Next time you get an FAA line check, would you be willing to inform the check airman of your radio plan and then use it for the whole flight? (and spare me the story about how you didn't monitor guard on your last checkride - not everyone is going to catch every error.)
#43
Gets Weekends Off
Joined APC: Dec 2010
Posts: 3,119
Is that ability defined anywhere? i.e. what defines a communication suite capable of monitoring guard?
#44
What kind of aircraft do you fly now?
If it has ACARS and two VHF capable radios like almost every transport category aircraft I've flown at three airlines, then you can monitor guard.
Even when I was on a non-ACARS 727 we were able to comply with the requirement to have a link to dispatch via SELCAL and still monitor guard. If you're trying to find a legal loophole, I think that's going to difficult considering the comm capabilities of most modern 121 aircraft.
Obviously you're going to do what you want. You clearly were unaware of this requirement and ignorance was bliss. Now you've been properly informed. Do with that info as you see fit. The directive is about as clear and unambiguous as could be hoped for from a government agency. Over and out.
Last edited by Adlerdriver; 08-14-2017 at 09:40 AM.
#45
Gets Weekends Off
Joined APC: Dec 2010
Posts: 3,119
3-18,
What kind of aircraft do you fly now?
If it has ACARS and two VHF capable radios like almost every transport category aircraft I've flown at three airlines, then you can monitor guard.
Even when I was on a non-ACARS 727 we were able to comply with the requirement to have a link to dispatch via SELCAL and still monitor guard. If you're trying to find a legal loophole, I think that's going to difficult considering the comm capabilities of most modern 121 aircraft.
Obviously you're going to do what you want. You clearly were unaware of this requirement and ignorance was bliss. Now you've been properly informed. Do with that info as you see fit. The directive is about as clear and unambiguous as could be hoped for from a government agency. Over and out.
What kind of aircraft do you fly now?
If it has ACARS and two VHF capable radios like almost every transport category aircraft I've flown at three airlines, then you can monitor guard.
Even when I was on a non-ACARS 727 we were able to comply with the requirement to have a link to dispatch via SELCAL and still monitor guard. If you're trying to find a legal loophole, I think that's going to difficult considering the comm capabilities of most modern 121 aircraft.
Obviously you're going to do what you want. You clearly were unaware of this requirement and ignorance was bliss. Now you've been properly informed. Do with that info as you see fit. The directive is about as clear and unambiguous as could be hoped for from a government agency. Over and out.
You honestly have presented a compelling argument though and you have convinced me to start monitoring the circus frequency that is 121.5. Enjoy this moment, you just won an argument on the internet.
I wonder if I can get violated for muting it when it gets crazy with the idiots and forgetting to unmute it later?
#46
It may not have helped you, but it undoubtedly saved these people's lives. https://www.bizjournals.com/seattle/...e-olympic.html
And wouldn't it be the job of the dispatcher to let you know that airplanes at your alternate aren't getting through and coordinating a different one with you?
And wouldn't it be the job of the dispatcher to let you know that airplanes at your alternate aren't getting through and coordinating a different one with you?
There's that too. I have listened to more than one airline pilot talking a lost private pilot out of a bad situation on 121.5
#47
I basically told him to circle over one of those straight central FL roads, do not get near any clouds and just land on the road if you can't (watching for wires and poles of course).
Eventually he was able to climb high enough for a radar tag before we left VHF range.
I also just heard an airline crew helping a plane with engine trouble heading for a road landing. We went out of range before hearing the final resolution, but not before hearing the multiple Guard idiots saying guuuuaaaarddd in the middle of an actual emergency.
MIA Center has several dead areas for comm. They routinely use Guard to reach aircraft. Others are low and need relays. They call on Guard.
Although the newer EPIRBs and PLB's are SAT based. Many signals pop off in isolated areas unlikely to have a Dr. in his Bonanza randomly checking his ELT.
#49
#50
I see what you did there.
It seems the worst place is between Newark and an hour south. I don't even think they are flying...more like a bunch of d-bags just yapping on a radio, either in a parked airplane, or maybe they have one in their Mom's basement.
I've handled two Mayday calls from light aircraft while flying airliners (both were engine failures). In neither case did ATC hear them.
Thread
Thread Starter
Forum
Replies
Last Post