Juggling Internet Bandwidth

Working with bandwidth limitations.

This summer, I’m on the road again, working out of my RV, the “mobile mansion.” And, after dealing with crappy, overpriced Internet service at my first stop for the past three years, I decided to go it alone this year with a My-Fi.

Why My-Fi?

My-FiThe reason I picked the My-Fi (instead of setting up a mobile hotspot from my smartphone) was twofold:

  • The My-Fi unit came with better plans. There was a 3GB plan for $35 which would only cost $10/GB if I went over. I knew I’d likely go over at least a few times a year — last summer, I had an 8GB month. The other plans would have been far more costly for that overage.
  • I’m a Verizon customer and I wanted to be able to talk on the phone while using the Internet. I admit this was not a primary concern. Last year I used mobile broadband tethering from my BlackBerry and did occasionally get interrupted by a phone call while doing my Internet thing. It didn’t kill me to wait until I was done talking. After all, I spend very little time actually talking on my phone.

I should note here that I do know that the Virgin Mobile My-Fi has a plan with unlimited bandwidth. But what good is a device that doesn’t work where you are? The Virgin Mobile device doesn’t have coverage in the areas I travel to. Verizon does. That’s the same reason — or one of them, anyway — why I don’t have AT&T.

My Plans

Last summer, I was spoiled. Although I paid for Internet at my first stop, I also had free unlimited Internet access through my BlackBerry. I’d had tethering for years and was grandfathered in on a plan that offered unlimited bandwidth for only $15/month. That plan was not available for either iPhones or Android phones and I needed a step up from my BlackBerry. Turning off that plan was one of the hardest things I ever did as a techie.

Of course, my iPhone and iPad also have 3G coverage, giving me access to the Internet from either device without a Wi-Fi (or My-Fi) connection. The iPhone’s plan has unlimited 3G, which is nice. But I’ll be the first to admit that the last device I want to surf the Web with is a smartphone. For the iPad, I went with a limited plan offering only 1GB per month. The idea was that I’d do my heavy Internet lifting with my desktop or laptop computer and limit the iPad’s use to reading RSS feeds, doing a little Web surfing, and sending the odd e-mail.

My goal, of course, is to not go over any bandwidth limitations for the entire summer. And that seriously changes the way I access the Internet.

For example, right now my My-Fi is turned on and ready to access. But the AirPort (or Wi-Fi) connectivity on my computer is turned off. Why? Because my computer seems to access the Internet any time it can, sucking down my bandwidth for no apparent reason. No, I don’t have a virus or worm. But my computer does like to check in with the various services I use — MobileMe, DropBox, etc. — to see whether it should download any updates or get any files. It does anytime it’s connected. While I could disable a lot of these automatic checks, it’s a lot easier to just turn off Wi-Fi until I actually need it.

SurplusMeter

SurplusMeterYou might be wondering how I know what my computer is doing. Last summer, I picked up a Mac app called SurplusMeter. It’s kind of neat. You set it up, tell it how much monthly bandwidth you have, and what day the month starts on. You also tell it how you’re connected to the Internet. It calculates a daily allowance; the idea being that if you use less than your daily allowance, you have a surplus to use during the rest of the month. Then it runs in the background, monitoring your network access. You can launch the app at any time to see what your totals are. Here’s mine for this month, which started just a few days ago. Last night, I was in the red, so even though it’s early, today’s allocation has been partially consumed.

Now, of course, I can use as much Internet as I want per day. The idea is for the monthly total to be less than — or, ideally, exactly — 3GB. SurplusMeter helps me rein in my Internet usage so I can minimize it.

Two things to note about SurplusMeter:

  • I’m only running it on one computer. That means it’s only logging bandwidth usage on one of the four computers I have with me. (Don’t ask.) Laptop access is not being logged. This results in an understatement of total usage.
  • It logs all AirPort activity, including local network activity. That means that every time one computer talks to another — for example, to share files — that usage is also logged. This results in an overstatement of total usage.

I’m hoping these two discrepancies net each other out.

And no, it isn’t worth it to set up multiple copies and use some other file transfer method to get more precise information. All I’m interested in is ballpark numbers.

But if you do know of a better app for the task that doesn’t cost a fortune, please do let us know about it in comments.

Getting the Big Fat Files

Of course, I still have to access the Internet for things that would make a serious dent in my allowance. For example, right now I’m working on a Mac OS X 10.7 Lion book. The Developer Previews I’m using as I write are about 4GB in size. There are two problems with this, and both are pretty obvious:

  • Downloading a 4GB file over a My-Fi with a max download speed of about 1Mbps would take more than 10 hours.
  • If my monthly allowance was only 3GB, I’d exceed that with just one download.

Fortunately, I’m running Lion on a laptop. Over the years, I’ve identified some Wi-Fi hotspots with pretty fast download speeds. One is in Wenatchee, at a coffee shop, where I was able to download a 900MB file last summer in less than 12 minutes. There’s a gas station in Quincy that used to have pretty quick Wi-Fi, although I admit I haven’t tried it yet this year. And there’s a coffee shop in Quincy that might have decent speed; the only time I used it, speed was not a concern. I do know that the local library’s Internet absolutely sucks, so it’s not likely that I’ll be using it for Internet access anytime in the future.

Yesterday, while in Wenatchee, I used the coffee shop Internet to download podcasts, check for updates, get maps for ForeFlight on my iPad, and do whatever I could. If I’d stayed in Wenatchee a few more hours, I would have gotten the big file I need today. I figure I’ll try the Quincy coffee shop first and if that isn’t fast enough, I’ll try the gas station. If that’s not fast enough, it’s another trip into Wenatchee for coffee and a high-speed Internet fix.

Doing Chores with iPhone

In the meantime, I’ve been trying to use my iPhone as much as possible for small tasks such as checking e-mail and sending/receiving Twitter tweets. After all, there’s no bandwidth cap, so it just makes sense to maximize usage. For some reason, I’ve been getting a ton of spam lately — 10-20 messages a day about dieting or “male enhancement” — and it’s quick and easy to just delete these from my phone so neither my iPad nor my computers need to retrieve them.

I know this is a drop in the bucket as far as Internet usage goes, but the way I see it, every little bit helps.

Rising to the Challenge

This summer is an experiment to see how well I can limit my usage and stay within budget. I’m prepared to pay for the extra bandwidth, but I like the challenge of working within limitations. It’s a lot like trying to conserve energy by turning off lights and turning down the heat/air conditioning.

It’ll be interesting to see how I do.

Dangerous Flying: Abrupt Control Inputs

How sloppy flying could get you killed.

Recently, while flying with a 200-hour helicopter pilot, I was startled when he rather abruptly shifted the cyclic to make a turn. I didn’t say anything then because it wasn’t too abrupt (whatever that means). But when he did it again later in the flight with an even more abrupt movement, I spoke up and told him not to do it again.

Understand that we were flying a Robinson R44 Raven II, which has a rather unforgiving semi-rigid rotor system and very long rotor blades. We’re taught — or should be taught — during primary training to use smooth control inputs, especially when working with the cyclic.

I’m not a CFI and I don’t feel that I have the right to tell someone how to fly, but when a pilot does something I believe is dangerous, it’s my duty to speak up. So I did.

The trouble is, I’m not sure if he believes what I told him — that abrupt inputs are dangerous — or if he thinks I was just nitpicking his technique. (I let it go the first time partially because I didn’t want to be seen as a nitpicker.) Since so many pilots seem to read this blog to learn — or at least to get my opinions on things — I thought I’d discuss it here.

What Robinson Says

Section 10 of the R44 II Pilot’s Operating Handbook includes safety tips. Here’s the one that applies:

Avoid abrupt control inputs or accelerated maneuvers, particularly at high speed. These produce high fatigue loads in the dynamic components and could cause a premature and catastrophic failure of a critical component.

What Robinson is saying is that when you make abrupt control inputs you put stress on various aircraft components. They’re likely concerned about the rotor blades, mast, transmission, and control linkages most. This makes perfect sense.

Robinson Safety Notice SN-20, titled “Beware of Demonstration or Initial Training Flights,” includes these statements:

If a student begins to lose control of the aircraft, an experienced fight instructor can easily regain control provided the student does not make any large or abrupt control movements. If, however, the student becomes momentarily confused and makes a sudden large control input in the wrong direction, even the most experienced instructor may not be able to recover control.

And:

Before allowing someone to touch the controls of the aircraft, they must be thoroughly indoctrinated concerning the extreme sensitivity of the controls in a light helicopter. They must be firmly instructed to never make a large or sudden movement with the controls.

Of course, what worries Robinson here is that student pilots may make erroneous control inputs beyond what an instructor can fix to regain control of the aircraft.

What Worries Me More

January 31, 2012 note: Since writing this, a friend on the Rotorspace site has brought the topic of Mast Rocking to my attention. Apparently, some folks think that this accident may have been caused by Mast Rocking rather than an abrupt cyclic control input. I’m not convinced. Mast rocking supposedly does not cause the main rotor blades to diverge from their normal plane of rotation. How else could the tail be cut off in flight?

But what worries me more than putting stress on components is an accident report from 2006. I read this report on the NTSB Web site not long after the accident occurred. Back then, there was no known reason why an R44 helicopter with just two people on board for a long cross-country flight should fall out of the sky with its tail chopped off, but I had my suspicions. After my recent flight with the new pilot, I looked it up again. Here’s the probable cause (emphasis added):

The Canadian certificated commercial helicopter pilot was conducting a cross-country delivery flight with a non-rated passenger occupying the copilot seat. The passenger and pilot together had previously made delivery flights from the Robinson factory to Canada. Two witnesses saw the helicopter just before it impacted the ground and reported that the tail boom had separated from the fuselage. No witnesses were identified who saw the initial breakup sequence. Both main rotor blades were bent downward at significant angles, with one blade having penetrated the cabin on the right side with a downward slicing front to rear arc. The primary wreckage debris field was approximately 500 feet long on an easterly heading. The helicopter sustained damage consistent with a high-energy, fuselage level, vertical ground impact. Detailed post accident investigation of the engine, the airframe, and the control systems disclosed no evidence of any preimpact anomalies. The removable cyclic was installed on the left side copilot’s position, contrary to manufacturer’s recommendations when a non-rated passenger is seated in the left seat. The removable pedals and collective for the left side were not installed. The cyclic controls for both the pilot’s and copilot’s positions were broken from their respective mounting points. The copilot’s cyclic grip exhibited inward crushing. The Safety Board adopted a Special Investigation Report on April 2, 1996, following the investigation into R22 and R44 accidents involving loss of main rotor control and divergence of the main rotor disk, which included a finding that the cause of the loss of main rotor control in many of the accidents “most likely stems from a large, abrupt pilot control input to a helicopter that is highly responsive to cyclic control inputs.”

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
a loss of control and the divergence of the main rotor blade system from its normal rotational path for undetermined reasons.

(A full narrative is also available.)

This is pretty much what I’d imagined. The helicopter is cruising along at 110 knots in a very boring part of the California desert. For some reason, the pilot (or his passenger, who has access to a cyclic control), jerks the cyclic one way or the other. Maybe he was trying to dodge a bird. Maybe he was goofing off or pretending to be Airwolf. Who knows? The sudden input is enough to cause the blades to diverge from their normal path. One (or both) of them dip down and chop off the tail boom. The result: two dead bodies in a 500-foot long debris field.

And this is what was going on in the back of my mind when the pilot beside me made those sudden inputs.

Anyone who has flown a Robinson helicopter can tell you how responsive the cyclic control is. It wouldn’t take much effort to knock the blades out of their path. That’s why we’re taught — or should be taught — to use smooth control inputs.

Other accident reports like this one include: CHI05CA267 and MIA00FA102 (which is a “watch this” moment).

Other Concerns

Rotorcraft Flying HandbookThere are at least two other reasons to avoid abrupt cyclic movements. You can find all these in the Rotorcraft Flying Handbook, an FAA publication that’s a must-have in any helicopter pilot’s library.

Under the “Retreating Blade Stall” heading (page 11-6):

High weight, low rotor r.p.m., high density altitude, turbulence and/or steep, abrupt turns are all conducive to retreating blade stall at high forward airspeeds.

Personally, I don’t think retreating blade stall is an issue in Robinson helicopters, except, perhaps, at high density altitudes and high speeds. But in that case, you’d be exceeding Vne.

Under the “Low G Conditions and Mast Bumping” heading (page 11-10):

For cyclic control, small helicopters depend primarily on tilting the main rotor thrust vector to produce control moments about the aircraft center of gravity (CG), causing the helicopter to roll or pitch in thedesired direction. Pushing the cyclic control forward abruptly from either straight-and-level flight or after a climb can put the helicopter into a low G (weightless) flight condition. In forward flight, when a push-over is performed, the angle of attack and thrust of the rotor is reduced, causing a low G or weightless flight condition.

You can find an account of this (with a lucky pilot and passenger) in this accident report from July 22, 2010. Indeed, the problem may have occurred during the right turn the pilot initiated — did he jerk the cyclic over as my companion had done?

Another accident report that suggests mast bumping is SEA03FA148 (which took the life of a pilot I knew).

I’m Not Just Nitpicking

The point of all this is that I’m really not just nitpicking a fellow pilot with limited flight time. He performed a maneuver which I consider dangerous and I have all this information to back me up. It’s important for him — and for others who might not know any better — to avoid abrupt control inputs.

Robinson helicopters aren’t capable of safely performing aerobatic maneuvers. Don’t fly them as if they are.

Update, March 17, 2012: Here’s another example of an accident likely caused by an abrupt control input. This one resulted in mast bumping.

Travel Insanity

Too many miles, too little time.

I’m just recovering from a crazy week with too much travel in too short a time span.

Our Flight Path

Our flight path, recorded on my iPad with GPSTrack. Can you tell where we did some scud running?

It all started last Saturday, when I flew with two companions from Phoenix, AZ to Wenatchee, WA by helicopter in one day. It was almost 11 hours of flight time with mostly very brief stops for fuel. Although I had very little stick time — one of my companions did almost all the flying — I was still alert and able to fly at a moment’s notice.

It got a little tense when we had to do some scud-running in Oregon that lasted far longer than I like to be spending scud running — as if I like it at all. It never got dangerous, but more than a few times, I began scouting the remote hillsides around us, looking for a place to set down and wait it out. I was very glad when the terrain finally descended, dumping us in an area where we could get back on course.

We spent the night in Wenatchee and I parted company with my travel companions, leaving them to catch an early flight to Seattle while I took care of other things locally.

Sunday was relatively restful. I needed to reposition the helicopter to Quincy, WA, where I’d be spending part of my summer. That was just a 15-minute flight. Then I spent some time socializing at Ferguson Flying Services, where my helicopter is parked in Quincy, and the Colockum Ridge Golf Course, where my RV would be parked soon. Then a friend/client picked me up and drove me the 5 miles to his winery in town, where I spent the afternoon socializing with him, his family, and the folks who came for wine tasting. A nice, mellow afternoon.

But at 4:15, the craziness started again. I got a lift to Wenatchee Airport, where I caught a flight to Seattle with a connecting flight to Phoenix. My husband picked me up there at about 10:30 PM. Overnight at our Phoenix condo.

Monday morning, bright and early, we were on our way back up to Wickenburg. I spent the day finishing up some work on a chapter of my book and then packing. It wasn’t until nearly 9 PM that night that we were done and pulling the RV out of the hangar where it lives most of the year. We left it parked in front for the night.

Welcome to NevadaAt 6:45 AM, I was in the driver seat of the truck with Alex the Bird in the seat beside mine. We were starting a 1,295-mile drive from Wickenburg, AZ to Quincy, WA. My goal was to make Jackpot, NV that first day — a distance of 725 miles. I spent most of those miles on Route 93, a two-lane road with speed limits up to 70 miles per hour. There was no traffic and certain stretches of the road were straight and flat as far as the eye could see. We made Jackpot before nightfall. After dinner n the casino, I spent the night in the RV with Alex in comfort — in the casino parking lot.

My Rig, in Jackpot, NVThe next morning, I woke at 6:15, which is late for me. Anxious to get on the road, I rushed around making my coffee and Alex’s breakfast and then buttoning up the RV for another day on the road. It wasn’t until after I topped off the fuel tank across the street from the casino that I realized it was an hour earlier; that part of Nevada is on Mountain Daylight Time. So I got a very early start. I left Route 93 behind in Twin Falls, ID, and hopped on I-84. The route was mountainous and the truck sucked diesel at an alarming rate as I struggled to maintain speed up hills. I left the interstate just past Pendleton and got back on smaller, traffic-free back roads to head north. After 10 miles on I-70 and the last five miles through familiar farmland, I rolled into the parking lot at the Colockum Ridge Golf Course RV Park just after 3 PM.

My Route

My route, as captured by GPSTrack on my iPhone.

I was fortunate to have had good weather all the way. Towing 13,000 pounds of fifth wheel RV on wet pavement is no fun — as I learned last year. It was just starting to rain when I finished hooking up my utilities at 4 PM.

Do I need to say how exhausted I was? I’d snacked my way from Wickenburg to Quincy, eating only snacks on my low-carb diet: jerky, almonds, and cheese sticks. The only real meal I’d had was at the casino in Jackpot. My digestive system was a mess for the next two days.

And of course, I developed a bad cold, which I think I’m just coming out of now.

But on the bright side of this, I managed to get all my assets in position for the first half of the cherry drying season. I set up my RV office and yesterday I managed to knock off another chapter of the book I’m working on. I’m also in the area early enough to set up helicopter tours and wine tasting trips with the local wineries.

It’s been a rough week, but now I’m settled in. It feels good to be at my home away from home.

Pelicans

Absolutely prehistoric looking.

Back early in May, I finished up a week in Ventura, CA, where was I updating my Twitter course for Lynda.com. Although Twitter’s feature set didn’t change much since I recorded the second version of course in April 2010, the interface has. The course really needed an update to bring it back into sync with the way the service looks. It should be published shortly. If you have any interest in Twitter, I hope you’ll check it out.

A Backstory

High-Flying PelicanThe folks at Lynda.com put authors up in an area hotel. The first few times I came out here, they put me in a Holiday Inn Express near Ventura Harbor. I really liked my room, which was on the first floor with big windows overlooking the marina. There was a lot of life there — people walking, birds flying, boats, dogs, joggers.

Then, a little over a year ago, they switched to a hotel in Oxnard. Admittedly, it was a nicer facility with better accommodations for us. The rooms were little L-shaped suites roughly the same size as the Holiday Inn’s, but more modern and upscale. And the Internet service was about 5000% better. (Okay, so maybe I exaggerate, but it was better.)

Trouble is, it also lacked everything I liked about the Ventura Harbor place. The place was condo-like, with square 2-story buildings, each having eight units. The windows were small. There were balconies, but no reason to sit on them — and no furniture to sit on. The place was heavily wooded and it seemed dark and dank, like an unpleasant rainforest that was constantly shedding leaves and branches all over the property.

So on this last trip, I asked to stay at the Holiday Inn again. And the nice folks at Lynda.com booked my room there.

The Pelicans

High-Flying PelicanWhich brings me to the pelicans.

It’s odd that I don’t remember them, but they must have been here all along. They fly over the marina every evening, scouting the water between the boats for fish foolish enough to swim close to the surface. When the see their prey, they tuck their wings and dive, landing in the water with a great splash. They bob to the surface, often busy swallowing a fish.

Pelicans are absolutely prehistoric looking. I mean seriously — what other bird looks more like a pterodactyl?

I spent one afternoon after work walking around the marina, settling down in a spot where I could wait to photograph them. Unfortunately, I didn’t bring the appropriate equipment. All I had with me was my 16-85mm lens, which is a great multi-purpose lens but a pretty crappy lens for photographing wildlife. My 70-300mm lens was home. So was my monopod and my tripods.

Pelican Over WaterIn other words, I wasn’t properly equipped.

Still, I made the best of it. What you see here are among my best shots, taken late in the afternoon as the sun was sinking low on the horizon. One thing I learned that afternoon is that pelicans don’t like to dive when someone is standing nearby with a camera. Ah, if only I had my long lens and monopod! Next trip. (If you’re a Lynda.com subscriber, please do give my courses lots of positive feedback so I can some back and record more; next time, I’ll bring that lens.)

The shots here are the best I took that afternoon. Please pardon the ugly watermark, but I’m really sick of seeing my work on other people’s websites without attribution.

Enjoy.

More Blog Posts…Soon

Still very busy, getting ready to relocate, but the end is near.

First of all, you need to understand that I really do like writing in this blog. It makes me feel good to post something each morning as I enjoy my morning coffee. Whether it’s a poorly disguised rant or a detailed account of my latest helicopter trip, it feels good to get the words out and share them with others. I am, after all, a writer at heart and writers need to write.

And that’s actually what I’m doing. I’m working on a revision to a 600+ page book and am about 3/4 finished. There’s a very tight deadline — one I’m not sure I’m going to make this time (don’t tell my editor) — and I’ve been working my ass off on it, getting very burned out in the process. I’m not complaining; this one book earns a whole year’s income so it’s worth what I put into it. But it does leave me too tired and burned out to write in this blog — and not really enough time to do it right anyway.

But the end is near! I’ll soon be repositioning my helicopter and RV to Washington State for the summer. (My house-sitter is already installed to care for the fish and backyard birds and keep an eye on things.) Once there, I’ll finish up the book and have a lot more time for other projects, including some videos and, of course, this blog.

Between now and then, I’ll be making two trips from Phoenix to Washington. On one, I’ll be a passenger in my own helicopter for a day or two. On the other, I’ll be driving my “rig” on a two to three day journey through Arizona, Nevada, Idaho, and Washington. On both trips, I won’t be writing about computers. So I expect to have a clear enough head to share some stories about the trips. Maybe some photos, too. With both hands free in the helicopter, I’ll have no trouble taking photos.

So bear with me just a little longer. New blog posts will come soon. I promise.