
Kicked off: 100 Jewish students were asked to leave an AirTran flight headed for Atlanta from New York last Monday
You probably read the headline, which made the news more because of the students’ baseless allegation that they we’re removed from their flight because they were Jewish. (Read the story: click here)
But let’s go beyond that smokescreen and look at the real issue from a pilot’s viewpoint–because it was a pilot’s responsibility to have them removed for non-compliance with crewmember instructions.
There are two issues here: electronic interference from handheld devices in flight, and equally important, compliance with federal regulations and flight crew instructions. First, let’s look at electronic devices and their possible effect on a flight.
Let’s go to the heart of the matter: landings. Why? Because this is the phase of flight during which the instrument guidance is arguably to most vital: you’re dealing with limited or practically speaking, no visibility as you attempt to land (versus taking off, when you’re climbing away from the terrain) and are therefore very dependent on your instruments for crucial guidance about pitch, roll descent rate and altitude.
Pilots are dependent upon the information gleaned from an array of very sensitive electronic signals generated both on the ground and on board, which provide critical safety and navigation parameters for an approach. Would a handheld device somewhere in the cabin affect these signals or worse, put out signals of it’s own that would interfere with aircraft systems?
Engineers say “maybe,” which is secret engineer (god love ‘em, they’ve built us some fantastic air machines) code for “we can’t rule that out.” Do you as a passenger want that “ruled out” as your flight approaches the concrete on instruments at 160 mph?
A typical counter argument we often hear is this: “Sure, fly-by-wire (meaning, no direct cables to controls but rather, electronic servos) aircraft like the Airbus could be susceptible, but your average passenger jet actually does have cable controls, which are not subject to electronic interference.”
But the problem is, even those aircraft with direct control linkage, when operating on autopilot, are then controlled by servos that are susceptible to electronic interference. A stray signal can–and has–created a spurious autopilot input and when aircraft (fly-by-wire or control cable) are within feet of the ground, that interference can be disastrous.

Big picture answer, from the pilot perspective: we work hard to eliminate all variables in the safe approach to poor ceiling and visibility landings. We HAVE to ensure the validity of the data that substitutes for our own visual cues in order to land in marginal flight conditions, or we simply can’t–or won’t–land.
Which brings us to issue number two: compliance with federal regulations and flight crew instructions. And let’s get back to the youth group in question. Complaince is a binary–you either do, or don’t. There’s no room for “we think it’s okay to have our cellphones on in flight–so we won’t comply.”
They clearly don’t understand the binary nature of compliance or more importantly, the equally black and white nature of my options as a pilot, given the circumstances: I have to ensure the flight is operated in full compliance with all federal regulations (“cell phones and personal electronic devices off for taxi-out and take-off”), just as I have to–as noted above–be confident in the integrity of the instrumentation upon which I base our ability to safely fly.
To make matters worse, albeit simpler, in today’s air travel environment, the issue of compliance is even more cut-and-dried than ever. Used to be, if we had an non-compliance issue, I could personally go back and explain the situation and gain the compliance we need to satisfy the ironclad regulatory and safety requirements mentioned above. Those days ended on September 11th, 2001. Now, pilots will by regulation (if not common sense) stay on the flight deck and simply enforce whatever the cabin crew requires to ensure compliance, period. Rule one in that dilemma is don’t take off with a problem you don’t want to handle again in the air or on landing.
There again is the simple binary: comply, or don’t fly.

Student group boarding the AirTran flight in Atlanta.
I don’t wish the kids involved in this incident anything other than better experiences in the future, although given the regulatory and safety explanations above, I can’t find it anything other than disappointing that some of them would try to make this an ethnic or racial incident.
In fact, summer time is all about student travel, often in large groups, and most are very well-behaved. I’m glad to be taking them on the first or last leg of their adventure. But maybe the primary lesson that needs to come before–and during–the educational experience is one regarding mandatory compliance with legitimate instructions: comply, or don’t fly.
And now they know why.



































































Again, auto traffic dropping off passengers approaches from the right, so passengers naturally stop at the first available space–and go to the closest security checkpoint. But there’s an identical security checkpoint on the other end of the terminal which is normally less crowded–use it!








Sure, there are some flimsy walls partitioning off this mess–and your mess–from the general public. And believe me, they ARE flimsy walls too–weight is fuel burn which is cost in flight. But shrewd aircraft designers rely on the ambient background noise of flight (you know: jet engines, 300 mile and an hour wind noise) to cover up your bodily noises on the can, much like the lame exhaust fan in a tiny apartment is intended as background noise so you can crank away without disgusting a cohabitant. Lesson for the wise: don’t do anything in an aircraft lav on the ground that you don’t want others to hear. Because they will, especially as they troop past on boarding, and they’ll give you that look when you step out.
Being confused with this:
But again, it’s as outdated as the prop job in the drawing above, never mind the natty dress and Pepsodent grins. Because besides the issue of today’s cramped lav (space is $, remember), there’s the detail of sanitation: it’s as clean as your average outhouse, and often smells like one. Because either you have the swirling tank of port-o-john water below, or on more modern jets, no water at all–just a non-stick coating with fragrant skid marks anyway:
So anyone who says they have joined “The Mile High Club” is either A) Lying, B) Disgusting, or C) Has lost the will to live. And here’s the dirt on option “C:” there is no supplemental oxygen in the lav.
In all probability, you’re meeting your maker like Elvis’s last public appearance: face down, pants down, toilet unflushed. Now that’s the stuff of legends, right?
At least you’ll be able to breathe no matter what demonstration of disgustingly poor judgment you’re finding necessary to pursue in the can.
What better to beat the blistering heat of a Jethroplex summer than a float in your own ce-ment pond? You bid the later-in-the-day flights and you’re senior enough to hold them. That means the morning run–helps you sit still for the 6 or 7 hours you’ll be in the air–and an early afternoon swim. Then, reality check waiting on the iPhone:
You knew that. LaGarbage today, tomorrow too–then LAX the next day. That’s your work week. Get ready.
That’s the current radar picture in the New York metro area. The stuff just north of Tom’s River will be a problem if it doesn’t move out to sea. You can tell there’s a front line between Jersey and NYC somewhere–just look at the temperature difference. Cold air slipping under warm air produces big boomers, and it doesn’t take much of that to disrupt the inbound flow to Kennedy, Newark and of course, LaGuardia. Shrug. Deal with it when you get there–but prepare for it before you take-off: more fuel.
Board 160 passengers. Preflight. Taxi out. Climb.
Radar watch is beginning to turn up signs of the frontal clash converging on the northeast. Super radar–good picture out beyond 300 miles, has it’s own GPS so it knows where all topographical features are and screens them out of the radar image. Good to be sure that what we’re seeing is nothing but weather.
Lunch? Dinner? Whatever–it’s the last food you’ll see today. Everything at LaGarbage will either be closed or out beyond security, which you don’t have time for: they’ll be clamoring to board 160 passengers outbound as soon as you get there. Speaking of which, within an hour of landing, we can get the current weather at LaGuardia and print it out:
The FMS begins its backward countdown of miles to go and upward count of vertical velocity required to satisfy the arrival restrictions. Cool?


Refiguring the approach is not a big deal. But it’s a bad sign: runway changes take time and lead to a huge backup on the ground at LaGuardia. Plus shifting winds mean unpredictable weather due to frontal passage. Alright, plan “B” is the runway 4 approach. Reprogram the FMSs, the courses and the nav radios.
More jets at the bottom of the stack are heading for Philly; we’re still sound fuel-wise. Patience.
The ugly blotches here are actually the towering cumulus we’re sinking into here:
Already have the crew strapped in, all passengers down. Actually, the bad weather is a relief in a way: everything slows down as radar separation is increased. Plus, the approach is a straight-in, precision approach rather than the hairpin visual approach that is officially called the “Expressway Visual:”
Lots more fun from a pilot standpoint, but definitely more hectic. Finally, the wide swing to finally. Configure. In the slot: altitude, airspeed, configuration, glide slope, localizer.
No time for relaxing–it all starts again in 50 minutes, outbound with another 160 passengers impatiently waiting to board. The inbound holding and the LaGarbage ground congestion has already set us behind schedule, and passengers have connections to make at DFW.