Browsing Posts in Accidents/Incidents

It’s that dreaded day once again. Some have asked how long I’ll keep doing this tribute. Maybe ten years afterwards was enough. But in my mind, what happened on September 11, 2001 created such a dramatic change for our industry that I can’t imagine stopping this tradition anytime soon. So once again, let us remember those who were at the center of it all. The flight crews on the four aircraft that never made it to their destinations that day certainly deserve to be remembered.

American 11 (Boston to Los Angeles)
Crashed into World Trade Center
John Ogonowski, Dracut, Mass., Captain; Thomas McGuinness, Portsmouth, N.H., First Officer; Barbara Arestegui, flight attendant; Jeffrey Collman, flight attendant; Sara Low, flight attendant; Karen Martin, flight attendant; Kathleen Nicosia, flight attendant; Betty Ong, flight attendant; Jean Roger, flight attendant; Dianne Snyder, flight attendant; Madeline Sweeney, flight attendant

United 175 (Boston to Los Angeles)
Crashed into World Trade Center
Victor J. Saracini, Lower Makefield Township, Pa., Captain; Michael Horrocks, First Officer; Amy Jarret, flight attendant; Al Marchand, flight attendant; Amy King, flight attendant; Kathryn Laborie, flight attendant; Michael Tarrou, flight attendant; Alicia Titus, flight attendant; Robert J Fangman, flight attendant

American 77 (Washington/Dulles to Los Angeles)
Crashed into the Pentagon
Charles Burlingame, Captain; David Charlebois, First Officer; Michele Heidenberger, flight attendant; Jennifer Lewis, flight attendant; Kenneth Lewis, flight attendant; and Renee May, flight attendant

United 93 (Newark to San Francisco)
Crashed in Shanksville, Pennsylvania
Jason Dahl, Colorado, Captain; Leroy Homer, Marlton, N.J., First Officer; Sandy Bradshaw, flight attendant; CeeCee Lyles, flight attendant; Lorraine Bay, flight attendant; Wanda Green, flight attendant; Deborah Welsh, flight attendant

It’s Not Actually News When a Plane’s Landing Gear Doesn’t Go DownConde Nast Daily Traveler
A United Express flight had its nose gear fail to extend earlier this week. This shouldn’t be news.

In the Trenches: Defining RolesIntuit Small Business Blog
Trying to define roles in a small business is tougher than it might seem.

Many cities lose out in Southwest-AirTran mergerUSA Today
I was interviewed about the loss of service from Southwest in smaller cities.

Even though I’m on break, I did have two articles that went live and one guest post as well.

An incredibly safe year for air travelCNN Out of the Office
I take a look at the year in review for accidents. As the title says, it was a very good year.

When Is a Nonstop Flight Not Really a Nonstop Flight?Conde Nast Daily Traveler
It’s winter and that means a lot more fuel stops are happening. Here’s why that happens.

Guest Post: What is a Travel Concierge?Bangalore Aviation
The guys at Bangalore Aviation asked me to follow up my top 10 list guest post with one about what we do at Cranky Concierge. I was, of course, happy to oblige.

This is more of a non-traditional Ask Cranky in that it’s been asked several times over the years, particularly in light of the Air France accident over the Atlantic when the thought was that the black boxes would never be found. The question? Why don’t airlines stream black box data so that they don’t have to actually find the box itself? It’s a great question, and there Ask Crankyare ways to do it. I spoke with Mark McWhirter, Business Development Coordinator at FLYHT about a product they have that does just that.

But first, let’s back up a little. What is a black box? There are actually two separate devices and neither of them are black. (It’d be a lot harder to find that way.) The Cockpit Voice Recorder (CVR) is used to record conversation in the cockpit. It doesn’t record for very long and so there isn’t a ton of history on there; it just keeps recording over itself so the most recent data is available. Then there’s the Flight Data Recorder (FDR) which takes a bunch of different data points about what the airplane is doing and stores them. Newer versions collect more data points with better info, but these also don’t record for very long.

The idea is that if something goes wrong, you won’t need to know what happened a week ago. You’ll really need to know what happened in the final moments. The most important thing about these devices is that they need to be crash-hardened so that they can survive a massive wreck, and that they do. When they pulled the black boxes off the ocean floor from that Air France wreck long after the airplane went down, and they could actually recover the data, it was a testament to how good these things are. But, doesn’t that seem strange in this day and age that the data isn’t just sent down to the ground? It’s not as easy as it might seem.

With internet access becoming more and more available, you would think that would create more opportunity for streaming the data, but reliable inflight internet is still only in a small geographic subset of the world. In many places where you’d really want to have this capability the most (over oceans, mountains, etc.), it’s not cheap to get data off the airplane using more traditional methods. At upwards of $3 to $5 a minute or so, that can get expensive quickly. That probably doesn’t make any sense, but there are better ways.

FLYHT has a product called Automated Flight Information Reporting System (AFIRS) which is actually quite smart. What is does is basically set up a recording device the plugs in and takes the feed between the aircraft and the data recorder. It stores anywhere from a week up to a month of data depending upon the aircraft, and the data can be removed at any time. This is useful for airlines that have FOQA programs and really work to analyze the data to improve safety.

The system uses the Iridium satellites to then communicate that data from anywhere in the world. On the legacy system, there would be a variety of triggers that would automatically send an alert back to base if something went wrong. These were the catastrophic types of events but normal issues that would want to be analyzed later. After Air France 447, however, there was a renewed interest in doing something more. And that’s exactly what’s happening.

Now, if an emergency happens, there are three ways that the mechanism can be triggered. One is automated depending upon the parameters set, the other is by the pilots in the cockpit, and the third is from the airline on the ground. If one of those is triggered, then the system will not just send an alert but will immediately begin streaming all the black box data down to the ground. Within 30 seconds, that data can be viewed in a simulation with only a slight transmission delay. Looks like this:

FLYHTStream graphic

Kind of awesome, right? At $3 to $5 a minute, it’s only a concern if all data was being streamed throughout the flight. If it’s just during an emergency, that price is peanuts and worth a lot more than that.

Great idea, huh? And who is using this? Well, it’s not widely out there yet, at least not the streaming stuff. It’s being tested on two customer aircraft right now. One is a US-based 767, but they wouldn’t tell me anything more than that. They do hope, however, that there will be more to talk about it down the line. Having this kind of information streaming makes a ton of sense, and as data coverage gets better and cheaper it will soon become a no-brainer to have a system like this if it isn’t already.

There was plenty of backlash when I wrote about the causes of the 2009 crash of Air France flight 447 into the Atlantic Ocean back in May. Many of you wanted to wait until the final report came out, but I was confident that the story had become quite clear. With the latest interim report (which I can only find in French – summary in English is here), it looks like I was right on track.

Un Airbus A330 d'Air France

Here’s what I said at the end of my last post:

Remember, the pilots were already working to pick their way through the worst of the storms. Add to that the loss of the autopilot, dozens of failure messages, and inconsistent speed readings and it seems like the answer might be simple. The pilots may have been so distracted that they forgot to do the one thing they needed to do to survive: fly the airplane. Once the final report is issued, look for training changes to come out of this and possibly even some changes in the way Airbus puts its airplane logic together.

Sure enough, the focus of the latest report is on training and puts a lot of the blame on Air France, but there is some discussion about aircraft logic as well. This has been enough for the investigators to push out safety recommendations, though not without controversy.

Throughout this 3rd interim report, a picture of normalcy is painted throughout the beginning of the flight. It was noted that when the Captain left to take his rest, he didn’t leave “clear operational instructions” and there was “no explicit task-sharing” between the two remaining pilots, but the crew composition was fine and the aircraft weight and balance was within the proper limits.

As mentioned in the last report, the crew was well aware of the weather ahead and had made course corrections to avoid the worst of it. That’s when things got ugly.

According to the report, the aircraft was flying at the “upper limit of a slightly turbulent cloud layer” when the autopilot disconnected. It’s believed that this happened because the pitot tubes froze over and that gave the aircraft incorrect speed information. When the system can’t make sense of the information it’s being fed, it shuts off autopilot and the pilots have to fly the airplane. Turbulence, however, was not a problem. The plane was perfectly flyable, but poor decision-making fed by weak training brought the airplane down.

Proper procedures were not followed for dealing with unreliable airspeed indication. To make things worse, neither of the two copilots had been trained to properly handle manual flying at high altitude. Despite the stall warning, the pilots continued to apply nose-up pressure, the opposite of what they should have done. In less than a minute, the plane went from being correctable to operating outside the design limits because of the improper recovery efforts by the pilots.

About 1 minute and 30 seconds after the autopilot disconnected, the Captain came back into the cockpit. At this point, stall warnings were going on and off and the airplane was still at 35,000 feet. Unfortunately, it was also losing 10,000 feet per minute as forward speed just disappeared. At times, the aircraft rolled from side to side as the pilots struggled to get the airplane under control. Those in the back must have felt sheer terror. The pilots never made an announcement to the passengers, and soon after, they all plunged into the Atlantic. I get goose bumps just thinking about how awful that must have been.

So after all that, what have we learned? We know the aircraft functioned properly. Were it not for the pitot tubes freezing over, this would have been a routine flight. Even when the pitot tubes failed, had the pilots been able to properly fly the aircraft manually, the passengers probably wouldn’t have even known there was an issue. Out of this, the French accident investigators have released safety recommendations that will need to be implemented by regulators in order to go into effect.

The main recommendation is around training. The idea is to make sure that all pilots have the proper training for manual flight at high altitudes, a skill which is rarely used in commercial aviation today. There is also additional training suggested around stall avoidance and recovery. Additionally, it’s suggested that the role of relief captain should be better-defined when the Captain is on rest. This way, there will be less confusion and more defined task-sharing if something goes wrong.

But the blame wasn’t solely on the training and pilots. One recommendation for aircraft manufacturers is to look at including an angle of attack indicator that pilots can see on the flight deck. There is an indicator showing the angle of the aircraft to the ground, but there isn’t one that shows the angle of the wing as compared to the direction of the air (angle of attack). That could have helped the pilots in their recovery efforts.

One recommendation not made was to revisit the way stall warnings are handled on the A330 aircraft. In fact, the pilots union at Air France is so angry about this being left out that it has decided to stop cooperating with the investigation. The on-and-off nature of the stall warning may have simply added to the confusion, and made it more difficult for the pilots to make the right moves. The investigators say that there wasn’t enough evidence to include this just yet, but it will be discussed in some form in the final report.

Regardless of what comes out in the final report, the picture is already very clear. It seems that current pilot training standards were not enough to help these pilots get out of an entirely recoverable situation. Were the Brazilians running this investigation, they probably would have already filed criminal charges against anyone they could, but the French handle this properly. Find the problem, fix the holes, and make sure that something like this never happens again.

[Photo of Sister Ship to Crashed Airplane via Flickr user Tab59|CC 2.0]



About | Directory | Shop | Awards | In the News | Ethics | Cranky Concierge
Powered by WordPress | SRS Solutions | © 2006-2013 Brett Snyder All Rights Reserved | Terms of Use | Privacy Policy