First A350 Flight Out Of The US Has Aborted Takeoff

In and of itself an aborted takeoff isn’t a big deal. I’ve had several of them over the years, and even a few (fairly) high speed ones. They’re a bit more “exciting” than go arounds, but really not a big deal. When a takeoff is aborted it means the pilots know there’s enough room to stop, which is better than continuing if there’s a potential problem.

Qatar Airways flew an A350 to the US for their “pivotal announcement” this week, which would “usher in a historic moment in American aviation.” The announcement? That Qatar Airways is launching a new brand campaign. As usual, more interesting than the “announcement” itself was what Akbar Al Baker, Qatar Airways’ CEO, had to say. He’s probably the least “reserved” guy in the airline industry, and he had a lot to say.

Qatar-Airways-A350-Business-Class-30
Qatar Airways A350 business class

Qatar’s 777 incident at Miami Airport

Perhaps the most troubling was what Al Baker had to say about the Qatar Airways “incident” which happened at Miami Airport a few months back. During this incident a Qatar Airways 777 overran the runway at Miami Airport, hit the runway lights, had 90 scratches and dents, had a 46cm tear in the fuselage, and the plane lost some cabin pressure. The most concerning part? The pilots didn’t realize any of it happened until they landed in Doha 13+ hours later.

Qatar-777

The Qatari Civil Aviation Administration released their report about what happened, and put the blame squarely on the pilots. The four pilots miscommunicated terribly, and had even discussed the exact takeoff procedure during their briefing, which they didn’t end up following.

Actually, more concerning than anything else is that the airline’s CEO doesn’t take the incident seriously at all. He claimed:

  • “Such kinds of incidents happen quite often” (false)
  • “It was an instruction given to our pilot by the air traffic control, which he should have refused to accept” (false)
  • “However, he had enough runway for getting airborne and it was only an unfortunate incident” (ummm… if they had enough runway, why didn’t they take off without hitting objects on the other end of the runway?)
  • “At no time was the aircraft or the passengers put in any harms way” (that’s a real stretch)

Fortunately everyone was okay, though Al Baker’s perspective on this is troubling, in my opinion.

The irony of Qatar’s aborted A350 takeoff

Yesterday Qatar Airways operated an A350 charter back from New York JFK to Doha, which had a bunch of media people aboard. This was technically the first “passenger” A350 departure out of the US, so was a pretty big deal.

Well, on departure out of JFK the A350 had an aborted takeoff, which Zach Honig (editor of The Points Guy) captured on video:

The reason for the high speed aborted takeoff? Apparently the A350 got a signal indicating that the runway was too short and it auto-braked… at least that’s what the airline’s CCO claimed. Per the blog post:

Qatar’s Chief Commercial Officer, the highest ranking executive on the flight, came over to reassure us, explaining that an “indicator” was responsible for the abrupt abort. As I understand it, for some reason the A350 decided that our 11,000-foot runway was too short to support the takeoff, and the plane applied the brakes at full force — all on its own.

Ultimately this wasn’t a big deal (in the sense that no one was in danger), as it was clearly just a glitch in the system, and you’re always better safe than sorry. It was clearly a very “abrupt” incident, but there’s not really much which can go wrong when you abort a takeoff.

Still, there’s  something hilariously ironic about an indicator going off claiming the runway was too short (when it clearly wasn’t), while the airline’s CEO claims the runway in the Miami incident was long enough (when it clearly wasn’t).

Other interesting tidbits from the “incident,” according to Zach on Twitter:

  • Some passengers wanted to deplane, and even though they returned to the gate, the CCO wouldn’t allow them to deplane, as he wanted to save face
  • Zach was told to stop recording during the aborted takeoff… a somewhat odd request on a media flight
  • A passenger (who Zach thinks was an airline executive) came up to him and asked him to “stop Tweeting for now”

Bottom line

Like I said, an aborted takeoff isn’t really a big deal, in the sense that no one was in danger. Still, you can’t help but sort of chuckle at the irony of the reason for the aborted takeoff — an indicator going off that the runway was too short — when just two days prior the airline’s CEO denied any responsibility for their “incident” which happened for exactly that reason.

The attempt to restrict media coverage on a media flight is also sort of funny. I’ll give the flight attendant the benefit of the doubt in saying he should stop filming (since it’s possible they were preparing for an evacuation), but if he was told to stop Tweeting at a later point, well, there’s no excuse for that…

What an airline!

Conversations (32)
The comments on this page have not been provided, reviewed, approved or otherwise endorsed by any advertiser, and it is not an advertiser's responsibility to ensure posts and/or questions are answered.
Comment as a member

Membership is free and takes no more information than commenting as a guest. Earn status points for good contributions, and see fewer ads as your status grows.

Type your response here.

If you'd like to participate in the discussion, please adhere to our commenting guidelines. Anyone can comment, and your email address will not be published. Register to save your unique username and earn special OMAAT reputation perks!

  1. Loading comments…
Recent Comments
The latest from the OMAAT community.

The comments on this page have not been provided, reviewed, approved or otherwise endorsed by any advertiser, and it is not an advertiser's responsibility to ensure posts and/or questions are answered.

Johannes Bols Guest

Years after the aborted take off. What I come away from this with is astonishement that there were passengers who requested to leave the aircraft and they were refused? Sod that! There's a leetle trick I know that would force those tossers to let me off the plane. Cabin crew know what it is, and I'm not giving it away here. But it works every time.

0
‼ 0
Tom Gordon Guest

Refused to go back to the gate? I would have told the CCO that if I wasn't deplaned immediately I would call the police to make a complaint about false imprisonment, after which I would call the New York Times. That would have seized his attention.

0
‼ 0
Peter New Member

As a self-admitted amateur in this area, I find @B Palmer (and a few commenters on TPG) to be the most plausible. As someone who works in the tech industry, I have a hard time believing that the FMS can engage an auto-brake function and automatically override the pilot's controls at such a critical moment of flight. Whether the A350 threw up a "Runway Too Short" message based on @islandflyer's theory or the pilot saw the Threshold Markings and thought he had pulled a "QR MIA", the reality is that we may never know. Regardless, this points to what a few others have said - it is very concerning that QR can't be honest with the public. What else might they be covering up?

0
‼ 0
B Palmer Guest

As a pilot who has trained on the A350, I can tell you that the Takeoff Surveillance function, which would issue a "Runway Too Short" message is NOT tied to the autobrakes. There is a similar function that operates on landing (after nosewheel down and spoilers up) that can apply maximum autobrakes if the autobrakes are already active and it is determined that a runway overrun is likely. There are two modes to the warning on takeoff. One prior to takeoff power application, and another after takeoff power application. The calculations compare predicted liftoff distance and runway remaining. After takeoff power application, the prediction uses actual data, instead of pilot-entered data. : The FMS computes the liftoff distance based on the following data: ‐ The aircraft weight (the TOW or the GW) ‐ VR and V2 ‐ The flaps setting ‐ The T.O thrust ‐ The anti-ice setting ‐ The pack setting. plus altitude, temperature, and runway slope. When the engines are set to takeoff power: ‐ The FMS uses the runway length of the current runway based on the current position of the aircraft. The runway length is the runway length stored in the navigation database. ‐ The FMS computes the runway takeoff shift based on the current aircraft position. The ADIRS provides the current aircraft position. The autobrakes activate, if armed for takeoff (as they normally are) when the crew retards the thrust lever when above 72 knots, which sends a spoiler-deploy signal, which triggers the autobrakes. Incidentally, the runway-too-short message is inhibited above 80 knots. They do not automatically activate as a result of the Runway Too Short message. Possibly, the Runway Too Short message was issued in error, and the crew followed the procedure for the alert (abort the takeoff). Had they been on a different runway than that entered in the FMS, they would also have received a "NOT ON FMS RUNWAY" warning.

0
‼ 0
Al Guest

@mark - LOL IKR. It makes me cringe every time.

0
‼ 0

Save posts to read later

Saving posts is a member feature. Become an OMAAT member to build a reading list you can come back to from any device.

Become a member
Meet Ben Schlappig, OMAAT Founder
5,883,136 Miles Traveled

43,914,800 Words Written

47,187 Posts Published