Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm going on a long flight tomorrow, and would like to be able to use my laptop during the journey.

Wireless devices like WiFi and bluetooth interfere with airplanes instruments, and shouldn't be used on flights.

If my laptop does not have a physical rf-kill switch, is it sufficient to just ensure that the relevant modules do not get loaded?

If so, is that always safe, or does it vary between different hardware?

My particular situation, is a Samsung NC10 netbook. Atheros 5k wireless hardware. Debian sid with kernel 2.6.30-1-686. However, I think it'd be interesting to know the answer to this question for the general case; not just my specific case.

share|improve this question
"Interference" they've always said. And then, curiously, Airtran starts offering in-flight Wi-Fi... – hyperslug Jul 31 '09 at 18:54
...and Ryanair allow in-flight mobile phone calls. However, as I'm hurtling through the sky in a big metal tube, thirty thousand feet above the endless blue waters of the Atlantic, I'll err on the side of caution :) – SpoonMeiser Jul 31 '09 at 19:04
It always was purely speculative. Its just that your really don't want any "extra" airliners falling out of the sky... I am curious to know what (if any) testing and modifications Airtran did with the avionics before they started. – dmckee Jul 31 '09 at 19:04

Modern airplanes are no longer susceptible to the low powered interference these devices emit but the aeronautics agencies would rather be safe than sorry. So they are unwilling to change the rules. I would not worry too much about it. If you want to err on the side of caution disabling the driver should be sufficient.

For the wireless adapter type:

for i in `find /sys -name "rf_kill" ; do echo 1 > $i ; done

Then to turn it back on:

for i in `find /sys -name "rf_kill" ; do echo 0 > $i ; done

Courtesy of Not sure if this works for Bluetooth devices as well.

You could also try looking in the BIOS to see if it can be disabled from there. This may be a simpler solution.

The Discovery show "Myth Busters" did a segment on this very issue. They ran tests on very old aeronautics equipment they had isolated using a Faraday cage. They found that modern cell phones did cause enough interference to adversely affect the equipment.

They even convinced the FAA to allow them to test a grounded plane. All the aeronautics instruments were sufficiently shielded and they found no interferience even with a high powered transmitter.

share|improve this answer
The rf_kill malarky is different to unloading the module. 'find /sys -name "rf_kill"' doesn't find anything on my laptop, so unloading the module is the only option I believe I have. Does using rf_kill do anything that unloading modules does not? – SpoonMeiser Jul 31 '09 at 19:53
Hmm, is it possible there is a newer module? Initial support for rfkill was added to the ath5k driver back in January. Rfkill is the preferred way to ensure turning off the radio in Linux. There's no consistency among hardware vendors. Some turn the radio on as soon as there is power and the driver simply manages the device. – Kenneth Cochran Jul 31 '09 at 20:38
I know there's been work done, but I don't believe that it has made its way into the main kernel yet. – SpoonMeiser Jul 31 '09 at 21:49
rfkill as a standard mechanism for all drivers was added with kernel 2.6.31. It's accessed through a tool aptly named rfkill. See and . For older kernels, the mechanism to disable WiFi, bluetooth etc. is different for each driver (hence the rfkill system). – sleske Jun 7 '10 at 22:48

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.