Forced Landing in the Jabiru

On November 4, 2011 I was flying my Jabiru J250SP light sport airplane to Tyler, TX with my childhood friend Bill Berger to visit our friends John and Becky Davis. I’ve known John since second grade (1967); Bill and Becky since seventh grade. John and I roomed together in college, and I was best man at his wedding. When Bill suggested we fly down to visit, I immediately said yes.

We stopped in Springfield, MO for lunch and fuel. The Jabiru has been using a little more than the normal amount of oil lately, so I was careful to check it. I added about a half quart and we took off for Tyler.

A couple hours later, about 45 minutes from Tyler, the engine started running rough. My first reaction was to simultaneously pull up on the controls to slow to our best glide speed and look outside for a place to land. A quick glance revealed we were over the west end of a rough-looking pasture carved out of heavy woods. Assured that we had options for landing should it be necessary, I turned my attention back to the engine.


View 33.404333, -95.013167 in a larger map

There’s not a lot to do in our little airplane when the engine is running rough. There is only a throttle control, no mixture or prop levers to play with. I pulled the carb heat lever in case the problem was carburetor ice. There was no change in RPM. About then a warning light came on, indicating low oil pressure. I looked at the engine monitor and noted that cylinder 3 was significantly colder than the other five cylinders.

About then the prop came to a sudden stop and the cabin went quiet. I have often heard the stories of the sudden quiet when the engine quits, but frankly it wasn’t that startling. Our Bose noise-canceling headsets minimize engine noise to begin with, and there was still the sound of air rushing past the airplane. And frankly, I wasn’t really thinking about how noisy it was or wasn’t.

The interesting thing about the engine stopping was what it did to my state of mind. I had been somewhat panicked, trying to find a solution to a problem that I couldn’t really identify and for which I had few options even if I did know what was happening under the cowling. Once the engine stopped, the problem of fixing it was solved. I no longer was trying to solve a rough-running engine using only the throttle, carb heat, and mag switch. Instead, I was landing an airplane — something I’ve done thousands of times (successfully, no less).

I said to Bill, “OK, now we’re going to land.”

Now a lot of people are confused about what happens to an airplane when its engine quits. “Did you just dive into the ground?” No. When the engine quits, the plane becomes a glider. It flies just like it did before, but there’s no power so you can’t climb. “So you float to the ground like a parachute?” No. You just keep flying, but you can’t maintain your altitude or go up. You can only go down. It’s like your car when you run out of gas. You can still steer, and if you’re going downhill you might be able to travel quite a while before the car stops on its own. An airplane without power from the engine goes “downhill” until it hits something or you land. You can still steer right and left. You can descend faster or slower by changing the pitch (point the nose up or down) but you can’t fly level or climb (well, you can climb a little but you’ll slow down and quickly lose whatever you gained).

An airplane has an ideal glide speed. You pull back on the stick (pitch up) to slow down or push forward (pitch down) to speed up. If you slow down too much the wings won’t be able to hold the airplane up, the nose will suddenly drop, and you’ll descend quickly until you pick up enough speed for the wings to fly. If you speed up too much by pushing forward on the stick, you’ll descend faster and give up altitude, which reduces your options for a landing site. In our airplane, when you are at the ideal glide speed you’ll go about two nautical miles (2.3 statute miles) for every thousand feet you lose in altitude. This limits how far you can glide. Of course these are ideal numbers; in reality you won’t hit that perfect speed all the time and every time you turn right or left you descend faster.

I had been pressing buttons on the multifunction display to locate the nearest airport. There wasn’t much nearby. I found Mt Pleasant, TX, which was 19.2 nautical miles south. We were at 4500′ MSL over terrain that was probably 500′ MSL. That gave me only about 3-5 minutes of glide time at best, which would be about 5-8 miles (again, at best) of range. I quickly eliminated gliding to an airport as an option, without bothering to do the math. And the field you’re over is better than the one a couple miles away, so this one was going to have to do.

We were over a gravel road. It was not a gravel road like we might think of back home in Iowa, but a private road that was probably used by the ranch to reach their herds. The piece of road we were over ran south then turned east. It was surrounded by open fields covered by some kind of scattered brush and a few small trees. I turned left to go back to the north end of the road as we glided down. I punched “7700” into the transponder to indicate an emergency and made a call on 121.5 MHz, which is an emergency frequency.

“Any station monitoring, this is N57CE, 19.2 miles north northeast of Mt Pleasant, TX, 3800 feet descending, engine is out, declaring an emergency.”

No response. I continue my turn to the north to come back around to line up with the farm road. I repeated my call and heard a response from ATC, who was talking to another aircraft: “… tell that aircraft to contact Center on 130.2 if possible”. Without waiting for the call I tuned to 130.2 and contacted the local Air Traffic Control Center.

Listen to a recording of the ATC audio from Fort Worth Center

I gave the controller our position. He asked the ominous question, “How many souls on board?” I responded, “Two” and tried not to think about the grim “heaven’s census taker” feel that question has. Center offered to find us a nearby airport, but by this time I had eliminated the road and we had turned east to land in the open field. I said something like, “We’re only about 500 feet off the ground. We’re in a single-engine airplane and our only engine is out. We will be landing here very shortly.” He asked if there were any roads or towns nearby. I glanced at ForeFlight running on my iPad. There were three small towns in our vicinity. The biggest of these appeared to be Talco, TX. I estimated we were about five miles east-northeast of Talco. Center asked us to call them from the ground if possible and let them know the outcome.

As we got closer to the ground I noticed a row of trees and brush running perpendicular to our path. It reminded me of how vegetation might grow along a fence row. It was sparse, but it formed a straight line across the field. Even though I couldn’t see a fence there, it was reasonable to believe one might be there. I pulled up to slow us down and to hold us off the ground as long as possible, while at the same time hoping it would be enough to clear the fence. I tried to imagine what hitting a fence might feel like and decided we could probably survive it; in fact it might slow us down and keep us from running into something more solid further along our path.

I aimed for a gap in the fence-line vegetation. As we got closer it was clear there was no fence, and shortly after we cleared that line we touched down.

The sound of the wheels on the rough ground was pretty loud. Shortly after touching down we apparently struck a thorn bush with the left wing tip. It stripped the lens off our position/strobe light. We wouldn’t actually realize we did this until three days later when we noticed the missing lens while disassembling the airplane to load it on a truck. Immediately after hitting the bush, we went over a small rise and all was quiet as we were airborne again for a second or two. Then back on the ground and rolling. I thought about applying the brakes but wasn’t sure how effective they’d be and didn’t want to risk any loss of control. We fairly quickly rolled to a stop.

I looked at Bill and said something like “That was interesting!” We gave each other a high five and expressed thanks to God for a safe landing.

I tried to contact Center but apparently they couldn’t hear me due to our being on the ground. But another aircraft responded and I reported we were safe on the ground, no damage to the airplane, and no injuries. He relayed that information to Center, who asked about our position. I located the GPS coordinates on the multifunction display and reported those to the aircraft to be relayed to ATC.

We secured the airplane and got out. We were in a large pasture surrounded by trees. The ground was uneven with clumps of grass and scattered small mounds like the one we had gone over that lifted us back in the air during our landing. Some 25-30 yards beyond where we stopped, the ground became very uneven. We certainly would’ve collapsed the nose gear had we gotten into that area. We could see cows in the distance. Fortunately none of those were along our path.

We walked around the airplane and found no damage. We wouldn’t discover the missing strobe light lens until three days later. Funny how you can look at something and not see it.

I called my wife and let her know the situation. Bill called John and Becky.

Within a few minutes a Beech King Air flew over at low altitude just west of us. We assumed they were looking for us. I turned the radio back on and made a call to the “aircraft overhead” and let them know they had flown past us. He started a turn to the right and asked me to tell him when to roll out of his turn. I let him know when he was pointing right at us and then called again when he was right overhead. He said he had confirmed our GPS coordinates and was going to relay them to ATC. I gave them my cell phone number to give to authorities so they could call us if needed. ATC asked him to confirm that nobody was hurt, which he did.

John called and asked what our plans were. We discussed having him drive up to pick us up. Since nobody had arrived to “rescue” us yet, we weren’t sure where to have him meet us. Our conversation was interrupted by a call from the sheriff’s department. She asked about the location of the airplane and I tried to describe it on a map by drawing lines between nearby cities. She confirmed that they had the GPS coordinates — the trick was getting the trucks to that location. “We know where you are; we just don’t know how to get there.”

I returned to John and suggested he drive to Talco to meet us. It would take him an hour and a half to get there. We had touched down around 4:20; now it was about 4:45.

For some reason, we thought it might help if we walked to a farm house we had seen during our maneuvering to land. I left a note in the plane and we set out. After walking about 20 minutes we figured out that the house was much further away than we thought. We turned around and headed back to the plane.

During this walk I called my dad to tell him about the situation. He and I own the airplane together. We assumed the plane would have to be trucked out. I couldn’t imagine trying to explain to some guy whose only qualification was that he has a commercial drivers license how to remove the wings and load this thing on his flatbed truck. Especially since I’ve never done it and have no idea how to do it. Dad said he’d call the Jabiru factory in Shelbyville, TN and see if they had any suggestions.

At 5:25 on our way back to the airplane we saw a helicopter circling the site. It had been just over an hour since we landed. They dropped down to a few feet off the ground and apparently determined we weren’t there. I regretted leaving the plane. (Rule #1 of survival: Stay where you are and let help come to you!) He departed to the east but then came back and went west. We later learned he was trying to figure out where the rescue vehicles were and how to direct them to us.

The sheriff’s office called again and asked about our location and if we knew of any roads that would get them close to us. It occurred to me that I had my iPad with me, so I brought up the Maps application, asked it to locate us, then sent a link to that location to the sheriff at his personal email address. I don’t know if that helped any, but it sure was handy to have such devices available — and for once in my life to have an AT&T signal when I needed it.

One of the interesting things we noticed was how easy it was to know if a passing aircraft or vehicle was looking for us. Our location was so remote that anytime you heard a noise that wasn’t a cow mooing you could assume it was someone coming to find us. We heard the helicopter coming back. They landed a hundred feet or so away. It was a medical evac unit sent out to find us. Bill went over and talked to them while I finished my email.

The chopper pilot told us they had been flying back and forth trying to find a way for the fire department and sheriff deputies to find us. They told us to sit tight and wait.

As the chopper was leaving a woman drove up on an ATV. She was Joyce Wilson. Joyce’s husband Bill owns Wilson Combat (www.wilsoncombat.com) and she is the Executive Director of the International Defensive Pistol Association (www.idpa.com). She and her husband operate a ranch just northeast of our landing site. Joyce is an instrument rated pilot and owns a Cessna 182.

Joyce had received a call from someone who had heard the GPS coordinates the sheriffs department was looking for and determined they were near Joyce’s ranch. She and her ranch manager Jeffery had set out on ATVs to look for us. We later learned there was a small army of locals on ATVs scouring the area to find us. After locating us, Joyce made some calls and soon many of them had found their way to us.

At 5:59, about an hour and forty minutes after we landed, I heard a sound on the road. I looked and saw a squad car, then two, then three, then saw the fire department truck leading the way. Trailing those four vehicles were several other pickup trucks and ATVs. We told our story to each of the deputies so they could fill out their paper work. Everyone expressed their amazement that we could survive such a harrowing event.

The lead deputy insisted on calling the FAA, which Joyce and I both felt was unnecessary. This tied them up for quite a while, and nothing else was really happening. I remember saying at one point, “We either need to order up a keg and some pizzas or we need to leave.” Given how hard it was for everyone to find us, we opted for leaving. Bill and I unpacked the airplane and transferred everything to two of the sheriff’s vehicles.

As we were leaving, the FAA called and had some questions, which I answered briefly and factually. I’m still not convinced it was necessary, and was disappointed the deputy had chose to involve the federal government. He told me I couldn’t move the plane until they visited the site and said it was OK.

I told him that the locals had trouble finding us even when they knew the area. There was no way a bureaucrat from Dallas was going to be able to locate the airplane. Furthermore, there was no damage and nobody was hurt. We weren’t obligated to report what was essentially just an off-field landing. We settled on me sending him some pictures, which I said I would do after consulting my attorney. (He never asked again, so I never sent the pictures.)

Bill and I each got into a deputy’s vehicle and we drove to Talco — about five miles as the crow flies but two or three times that on the ranch roads we had to follow to get to the main road. It took 30 minutes to get to the Exxon station that is Talco, TX, where John was waiting to drive us to Tyler.

Lessons Learned

There are two psychological surprises for me. First was the sense of relief and calm that came when the engine died. The rough-running engine was more stressful than the sight of the stopped prop. Once the engine stopped, my options were narrowed to one: Landing.

The second unexpected response was the disappearance of confidence I have in the Jabiru engine. This was actually the second engine failure we’ve had. The first engine lasted about 60 hours before a piston failed. My dad discovered that problem while taking off one day. The engine just didn’t seem right, so he aborted his take-off just before lifting off. The replacement engine they sent us had experienced the same problem during its initial testing after being mounted on a new airplane. They replaced the engine on that airplane, then replaced the failed piston in the bad engine and sent it to us. They assured us the replacement was like new, but then our last “new engine” (which really was new) had failed after only 60 hours. So we’ve owned two Jabiru engines: One that failed catastrophically after 60 hours, and one that failed catastrophically after 2.5 hours and again after 480 hours. That’s an average of 180 hours between catastrophic failures. At that rate we can expect a forced landing in a cow pasture every 18 months. It’s difficult to imagine what they can do to turn what appears to be a problem engine into one in which I can have confidence.

Additionally, I have come to some resolutions with respect to flying. First is to remember to pull the checklist even though it doesn’t seem necessary. While it wouldn’t have helped me restart the engine in this case, it would’ve reminded me to turn off the fuel, mags and maybe open the doors before landing. While neither of these proved necessary (we didn’t catch fire and we didn’t bend any metal causing the doors to become jammed shut), there might have been something on there that would’ve either solved the initial problem or prevented a problem on the ground.

Second, I want to add some suggestions to the engine-out landing checklist, such as looking for civilization and landing somewhere near it. It would’ve been a little easier had I turned toward Talco so we could’ve walked to the Exxon station instead of requiring helicopters, local residents, and deputies from two counties to spend an hour looking for us. (In retrospect, however, landing options were not as plentiful to our west, toward Talco.)

Finally, I want to develop an “after a forced landing” checklist that includes instructions on how to locate your GPS coordinates (not straightforward on our system), a suggestion to do a complete “pre-flight” inspection after landing to check for damage, and a reminder to stay with the airplane no matter what your shell-shocked brain tells you about how close you are to that house you flew over.

Read about the retrieval of the airplane from the field and its trip to the repair shop.

We’ve been mentioned on the interwebz: Listen to the guys at www.uncontrolledairspace.com chat about our off-field landing: MP3 of podcast #263. Fast-forward to around 58 minutes if you’re in a hurry.

How NOT to Stream Live Video from your iPhone

Today I thought it would be cool to stream video of my run to the Internet. I was sure there was an app out there that would do it, and sure enough there is: UStream.

I installed the app and went through the process to set up an account. At the end of entering my data, it said there was already an account for my email address. That was weird; I had never downloaded this app before. I suppose it’s possible I’ve tried installing this program in the past, so I figured I’d ask it to send my password to me and I’d log in to this mysterious, already-existing account.

When I clicked the “forgot my password” link, it asked for my account ID, not my email address. I entered the most likely account ID I may have used in the past, and it told me there was no account for that ID. So I entered a second account ID I sometimes use and sure enough, it said it was sending password reset instructions to me by email.

I waited and waited for an email but it never arrived. So somewhere out there, the person with the account ID “craigr” got a mysterious email asking him to reset his password.

In the meantime I decided to log in with a different email address and was able to set up a new account. I proceeded to the next step, which was to connect my account to Facebook so it could notify my friends when I was broadcasting live video. I got the familiar “connect to Facebook” dialog and entered my Facebook login credentials. Facebook asked for my permission to share all my personal data with UStream, and I agreed. This led to a screen that said, simply, “Success”. There was one and only one button for me to push. It said “Cancel”. I waited and waited but nothing happened. I finally decided to push the Cancel button, and sure enough, it canceled my login.

After trying a couple more times I decided to do an end-run around this stupid process. I went to my iPad and logged into their website using my newly established account. Going into my settings page on the website, I enabled the option to connect to Facebook. Facebook seemed to remember I had given it permission to interact with UStream, so that all went well.

Returning to the iPhone, I exited the application and re-launched it. I tried connecting to Facebook but with no luck. The program simply doesn’t work.

I still think it would be cool to broadcast live during my run and somehow interact with people. UStream is definitely NOT the way to do it.

How Strong Passwords are LESS Secure

We all know how important it is to use strong passwords and not to re-use passwords on different sites. We’re told not to use real words, not to use the names of pets or family members, not to use our birthdates, anniversaries, or Social Security numbers, and not to use common passwords like “password”, “1234”, and “qwerty”. And yet some of the most popular passwords at many sites continue to be easily remembered names, dates, or words.

Some sites have instituted draconian policies to make sure you use a secure password. Ironically, while some of these are banks, others are discussion forums for hobbyists or the comment section of a news site. I can understand why my bank wants me to use a secure password, but the comment area of The Mooselick Times?

Recently I was setting up a temporary testing account with Apple and had this exchange with their password validator:

Password: test
“Passwords must be at least 6 and no more than 32 characters.”

Password: testing
“Passwords must be at least 8 characters.”

Password: xxxxxxxx
“Passwords must contain at least one digit.”

Password: xxxxxxx1
“Passwords cannot contain more than two consecutive identical characters.”

Password: testing1
“Passwords must contain at least one upper case letter.”

Password: Testing1
OK

The problem with this is a) this is a temporary account for testing In-App Purchasing, and the Apple site knows that. Why all the security? And b) Since I’m never going to remember “Testing1”, I have to write it down (and write about it in my blog). Anyone who finds my password list now knows my “secure” password.

While this is no big deal for the testing account at Apple, it’s a big deal when it’s my bank account. I have a series of mixed alpha-numeric, non-dictionary-word, very secure passwords committed to memory that I use for my truly secure accounts. But if one of those doesn’t work at a site because it doesn’t meet their rules, I have to make up another, then write it down. Once it’s written down, it’s not secure.

At Laridian, I don’t think we put any restrictions on your password. Even though almost one thousand of you use “password” as your password, we’d rather have you be able to remember it than force you to make it unguessable then have to write it down.

Why I Run

I’ve never been one for sports or exercise, adopting as my life verse “bodily exercise profiteth little” (1 Tim 4:8a).

A while back someone asked my dad why I started running. My dad had an interesting answer. “I think he got a new phone that had a running program on it that let him track his location with GPS and keep track of his time, distance, heart rate and a bunch of other stuff. I think he started running so he could play with all that stuff.”

That’s not too far from the truth. About seven or eight years ago I started working out when my doctor put me on cholesterol and blood pressure medication. I was doing 30-45 minutes on an elliptical machine three days a week. About three years ago I was heading down to my dark basement on a beautiful spring day to work out when I thought, “why not run instead?” So I headed out the front door to see how far I could run. I ran until I got dizzy and my stomach got upset, then walked home. I got in my car and drove the same route and found I had run about three quarters of a mile.

Two days later I headed out again, this time with a program on my iPhone (RunKeeper, www.RunKeeper.com) that tracked my distance and time. I made it a mile before I couldn’t go farther.

I read online that it helps to run short intervals then walk for a minute or two. I started running quarter mile intervals with 2 minute walks in between and found I could cover 2-3 miles without wearing myself out.

A knee injury took me out the rest of that year (2009). I started up again the following spring and got my running intervals up to a mile and a half by the end of the summer, with total distances around 4.5 to 6 miles of running.

By now I was hooked. I enjoyed the challenge of running. Being able to track my progress on RunKeeper’s website was highly motivating. Running itself is hard and at times, boring. But it’s like the guy who was pounding his head against the wall. When asked why he did it, he replied, “Because it feels so good when I stop.” when I’m done, there’s a feeling of accomplishment.

This summer a friend told me she does the same kind of interval running, but runs 5 minutes then walks 1 minute. I switched to that method and increased my distance to about 7.3 miles.

A change in my work schedule made it more convenient for me to run on Tuesdays and Thursdays, so I added a Saturday morning run to my schedule. Three weeks ago I had a crazy idea and turned left when I should’ve gone straight and my usual 7-mile route became a 10-mile route. 10 miles wasn’t bad.

I told my friend about my weekend run and she said, “If you can run 10 you can do a half marathon (13.1 miles). So the next weekend I made another left turn and my 10-mile route became a 13.1 mile route.

The problem with running farther than you’ve ever run before is that you first have to run as far as you’ve ever run before, then you have to keep running after that. At about 11 miles I was re-thinking my decision but then I hit 12 and it seemed like a waste not to go all the way. I made it 13.1 miles in just under two and a half hours.

The following Monday, my sadistic friend said I should look for a “real” half-marathon to run. I went online and discovered the local running club was sponsoring a half-marathon the very next weekend. $36 later I was registered for my first official half-marathon, which I completed in about two hours and 23 minutes, beating the personal record I set the week before.

I told you all that so I could talk about technology. The core of the technology I carry with me is RunKeeper running on my iPhone. To that I add a pulse rate monitor from Wahoo Fitness (Www.wahoofitness.com). This provides real-time heart rate data to RunKeeper.

So that RunKeeper can calculate calories burned, it needs to know my weight. So I have a Withings WiFi-connected scale (www.Withings.com) that automatically uploads my weight and body mass index (BMI) to a website where RunKeeper can access it. This has the further benefit of tracking my weight loss without me having to create a spreadsheet and update it manually.

That’s the computing technology that keeps me running. But there are some other products that are essential. First, A Speed 2 hydration belt from Nathan Sports (Www.nathansports.com) lets me carry 20 oz of water or Gatorade along with a pouch full of “energy gel” packets for replenishing electrolytes (they’re what plants need) in long runs. (For runs that are ten miles or more I need more liquid so I have to plan my run to pass a water supply).

Absolutely essential are NipGuards (www.nipguards.com). Running longer than an hour or so causes a lot of nipple abrasion. Running without a shirt is not an option for me (I run past a school, and the sight of me shirtless frightens small children and some animals), so affixing a pair of NipGuards protects me from embarrassing blood-streaked shirts.

I’m currently running in Mizuno Wave Rider 14 shoes. These lightweight shoes give me a medium amount of support and cushioning without getting in the way of the normal flexing of my feet. The provide less structure than the Asics I was running in before, but are lighter and more flexible.

Other than my winter running gear, I’ve been able to find good shorts and shirts at Target. You need something that wicks moisture away and lets it evaporate, as opposed to a traditional cotton that will just hold sweat.

So yes, a lot of why I run is all the cool toys. But I can’t dismiss the feeling of accomplishment watching my times improve and distances get longer.

Fact: Verizon iPhone GPS is Grossly Inaccurate

Verizon and Apple deny there are any problems with the GPS in the Verizon iPhone. I can demonstrate this is not the case.

Today I ran a route that MapMyRun.com says is 5.06 miles.

Here is the route as recorded by RunKeeper on my AT&T iPhone 3GS: AT&T iPhone says 4.93 miles.

Here is the route as recorded by RunKeeper on my Verizon iPhone 4: Verizon iPhone says 6.3 miles.

The Verizon iPhone does a better job if you turn off its cellular data connection and WiFi. However, with cellular data turned off, I can’t use RunKeeper’s feature of reporting my position live on their website as I run, nor can I send or receive text messages. The AT&T iPhone does equally well regardless of whether its data connection and/or WiFi is turned on.

I’ve talked to the people at RunMeter and RunKeeper and had them analyze the data. It appears that Verizon favors using location data gleaned from cell towers and private WiFi access points. What you’ll notice with the Verizon map is that it appears that I run up to every cell phone tower and building that has a WiFi access point, when in fact I’m running straight down the street or trail.

Verizon denies there is a problem. I’ve talked to their tech support on at least three occasions and they have escalated the problem, but nobody has ever called back. Apple asked for supporting data but never replied after I sent it.

The proof is in: Your Verizon iPhone does not know where you are. It ignores location data from 24 geosynchronous, military-grade, high-tech satellites and favors rough triangulation based on your drunken neighbor’s badly configured wireless access point.

Bumper Sticker Christianity

One of my pet peeves is people who post trite little “Christian” sayings as their Facebook status or on Twitter. They sound really good and they’ll get about 100 “likes” from all their like-minded friends, but most of the time they’re not defensible from scripture and as a result they do little more than lead empty-headed people in the wrong direction.

The other day someone said, “You can’t be like Jesus and hate politicians”. First, there are two ways to take that. The wrong way is: “Jesus hates politicians, and there’s no way you can be like him in your hatred of politicians.” The right way is: “You can’t uphold the biblical mandate to be Christ-like while claiming to hate politicians”.

The implication is that Jesus doesn’t hate anybody, therefore if we hate politicians, we’re not Christ-like.

First, I don’t think there are many people who truly hate anyone, let alone politicians. Real hatred wishes the worst for people and would rather see them dead. While I have a long list of politicians whose policies I hate, I don’t think there are any people I truly hate.

But second, and more important, the fact of the matter is that God does hate some people. I’ll vamp for a minute while you think about that. Who does God hate? There are plenty of verses that tell us that God loves everyone, but there’s at least one verse where God talks about people he hates.

Give up? How about Proverbs 6:16-19

16There are six things the LORD hates,
seven that are detestable to him: 17haughty eyes,
a lying tongue, hands that shed innocent blood, 18a heart that devises wicked schemes, feet that are quick to rush into evil, 19a false witness who pours out lies and a person who stirs up conflict in the community.

So I responded that I only hate the wicked schemers and the ones who stir up conflict. My friend reminded me that Proverbs 6 puts judging in God’s hands, which is true, but it wasn’t the question. The question is, can we hate and be Christ-like. My argument was simple:

God hates schemers and conflict-stirrers; I hate schemers and conflict-stirrers; therefore I am like God; Jesus is God; therefore I am like Jesus. QED.

My point isn’t so much that God hates people so we should too, but rather that we need to think before we toss out nice-sounding trivialities as if they are scripture. Christianity isn’t that simple. It requires some thought and can’t be reduced to a bumper sticker.

Life as a Sport Pilot

These days I’m flying as a “private pilot exercising sport pilot privileges”.

To get a private pilot certificate, one is required to pass a medical exam every 2-3 years, depending on age. A while back I had some heart problems that resulted in two cardiac stents. Of course the FAA panicked, convinced I was going to have a heart attack and crash into the White House. Ironically, before I had the stents I was more likely to have a heart attack, yet I was flying legally. Now that the problem is resolved the FAA gets concerned. Go figure.

I waited the requisite six months then submitted all my medical records and got my medical certificate approved. Then in May 2011 my cardiologist made the mistake of mentioning “sleep study” on his office notes. He wanted me to be tested for sleep apnea.

Let’s talk about sleep apnea. People with this problem stop breathing in the middle of the night. As a result, their oxygen levels drop and they wake up with bad headaches. They also don’t get all the sleep they need, so they tend to fall asleep while watching TV, driving, or — as you might’ve guessed — flying. I had none of these symptoms. I never wake up gagging. I never fall asleep while watching a movie or TV. I never fall asleep in church. I never fall asleep while driving or flying. But because it was mentioned in the doctor’s office notes, the FAA was going to panic. So I didn’t bother re-testing for my medical certificate.

Instead, I did a sleep study. The minimum number of events per hour that qualifies as “mild sleep apnea” is five. That is, you can stop breathing every fifteen minutes and nobody worries. But if you stop breathing every twelve minutes, you can’t fly an airplane. My score was 11.4. Higher than five, but still considered “mild”.

So now I use a CPAP (actually a BiPAP) machine when I sleep. It is a mask connected to an air pump that increases the air pressure over my nose and mouth. The “Bi” in BiPAP means it is bi-level. It increases the air pressure a lot when I breath in, less when I breath out. The machine actually counts my apnea events. I’m down to less than two per hour.

Symptomatically there is no difference. I still get about the same amount of sleep every night. I still stay awake while watching TV and movies. I still stay awake while driving and flying. I still have no headaches when I wake up. So several thousand dollars later I’m no more safe to fly than I was before, but the FAA is happy. I haven’t yet submitted my medical data for re-certification, but I will.

In the meantime, I can still fly but with fewer privileges. The FAA lets me drop from “private pilot” to “sport pilot” privileges, since I don’t have a medical certificate. So I can only fly in specially designated “light sport airplanes” that weigh no more than 1320 lbs and go no faster than 120 kts. I can’t fly at night or in the clouds, even though I’m instrument rated. I can’t fly above 10,000 feet even though I have a high-altitude endorsement and 300 hours flying pressurized aircraft. I can’t fly multi-engine airplanes even though I have a multi-engine rating.

This works out just fine. My current airplane is a Jabiru J250-SP, which is a light sport airplane I own with my dad. While I’ve flown my twin-engine Baron 58P from Boston to Seattle and San Diego to Atlanta at altitudes up to about 23,000 feet, I’ve also flown the Jabiru to those places and more. It just takes longer and you have to go around, rather than over, the mountains.

One of these days I’ll get my records together and re-apply for my medical certificate. In the meantime, assuming I don’t fall asleep or have a heart attack, I’ll be flying low and slow and enjoying the view.

PocketBible 2 for iOS

We’re just about to release an update to PocketBible for the iPhone/iPad. This version adds some often-requested enhancements and some new features that you probably didn’t even know you needed.

First, we’ve added the ability to select any text and copy it to the clipboard (what the iPhone calls the “pasteboard”). You’d think this would’ve been a standard feature of the program from a long time ago, but since we wrote our own HTML rendering code, it all had to be implemented by hand — including the cool magnifying glass that shows you what you’re touching as you select text and the lollipop-shaped “drag handles” that let you expand the selection.

Next, the multi-paned user interface was enhanced to allow you to represent each pane as a tab. This lets you easily jump from a Bible to a commentary and back by just selecting a tab. This feature was further augmented with the ability to open all your books in one operation. Your books will open in five tabs/panes labelled “Bibles”, “Commentaries”, “Dictionaries”, “Devotionals”, and “Other”. If you don’t have any books in a particular category, that tab/pane is not shown.

For those who take notes in the expanded toolbox, you’ve been frustrated by the fact that expanding the toolbox covers any open books beneath it. As a result it can be hard to both follow the Bible text and take notes (or preach from your notes). We’ve modified the behavior of the toolbox so that it switches you into tabbed mode if you’re not already there, then moves the current book out of the way of the toolbox. Now your Bible can be displayed in a narrow column above, below, or to either side of your notes. Very nice.

Two major new features are introduced in version 2. First is what we call “Autostudy”. By simply selecting a verse (or a word), you can quickly get a report showing everything your library has to say about that verse/word. While Autostudying a verse, you’ll see that verse in all your selected Bibles, the verse with Strong’s numbers if you have one of our Bibles that contains Strong’s numbers, definitions of every word in the verse from your selected dictionaries, definitions of all the Strong’s numbers in the verse from your selected Strong’s dictionaries, and all the cross-references for the verse from the Treasury of Scripture Knowledge. You can select which books and Bibles are used by this feature and in what order the material appears.

When Autostudying a word, you’ll see how many times it occurs in each of your Bibles, what Greek or Hebrew Strong’s words are translated to that word, and the definition of those Strong’s words and the selected word from your dictionaries.

Autostudy reports can be browsed in PocketBible, saved to PocketBible’s public folder (and from there transferred to your desktop computer through iTunes), copied to the clipboard, or printed to an AirPrint-compatible printer.

Finally, PocketBible now has the ability to speak any Bible or reference book you own. Simply purchase a voice (eight voices in two languages are available) using In-App Purchasing in PocketBible or at our website, then select the text you want to read. You control the volume and can even have PocketBible read while your iPod music plays in the background. You can set PocketBible to start reading at a particular verse and just keep going until you tell it to stop, or give it a specific passage to read.

The basic PocketBible program with the same features as the current version (1.4.7) will be free. The advanced features described above will be available for a nominal fee, either as an In-App Purchase or at a lower price at our website.

Tax the Rich!

The “tax the rich” fallacy: If we tax the top 0.1% of taxpayers ($1.8 million and above) at 100%, the net new revenue to the government would be $640 billion. Obama is currently spending $8.8 billion per day. So if we CONFISCATE 100% of the income of the super-rich, we could keep Obama afloat for 73 days. Raising taxes to solve a SPENDING problem is a fool’s errand.

Hebrews 4:12 and “The Word of God”

Recently, a Facebook friend posted a comment about Hebrews 4:12:

For the word of God is quick, and powerful, and sharper than any twoedged sword, piercing even to the dividing asunder of soul and spirit, and of the joints and marrow, and is a discerner of the thoughts and intents of the heart.

His assertion was that the “word of God” in this verse refers to Jesus, and not to the Bible as he had previously been led to believe. That prompted this response from me:

The “Word of God” is not a synonym for the Bible or the scriptures: In Lk 3:2 the Word of God came to John; he did not receive a Bible. In Lk 5:1 Jesus was preaching and the crowds were listening to the Word of God; he was not reading the Bible to them. In Acts 4:31 the disciples spoke the Word of God; they were not reading the Bible. In Acts 6:7 the Word of God kept on spreading; they were not distributing Bibles. In Acts 8:14 the apostles in Jerusalem heard that Samaria had received the Word of God; they weren’t talking about a shipment of Bibles. In Acts 11:1 the Gentiles received the Word of God; they did not receive BIbles. I could go on.

Paul defines the “Word of God” in Colossians 1:26ff as “the mystery which has been hidden from the past ages and generations, but has now been manifested to His saints… which is Christ in you, the hope of glory.” The “Word of God” is the message that God has for his creation. Specifically, it is the Gospel; more generally it is whatever God has to say — whether it was recorded in the Bible or not.

Jesus Christ is the physical manifestation of the Word of God (John 1:1-4,14). I imagine your interpretation of 4:12 is coming from 4:13, which refers to “Him”, and 4:14 goes on to talk about Jesus. I don’t know that 4:12 is specifically talking about Jesus or if it says that the Word of God is the tool/sword that Jesus uses to divide soul and spirit, joints and marrow, thoughts and intents, during the process of judging. But I know for sure that the “Word of God” in Heb 4:12 is not our 66-book Bible, because it is never used with that meaning anywhere in scripture.