Go Back  PPRuNe Forums > Flight Deck Forums > Rumours & News
Reload this Page >

Qatar. Take-off FUBARed. Again.

Wikiposts
Search
Rumours & News Reporting Points that may affect our jobs or lives as professional pilots. Also, items that may be of interest to professional pilots.

Qatar. Take-off FUBARed. Again.

Thread Tools
 
Search this Thread
 
Old 15th Dec 2015, 00:17
  #41 (permalink)  
 
Join Date: Jul 2013
Location: USA
Posts: 6
Likes: 0
Received 0 Likes on 0 Posts
Running the numbers...

Some of the headlines suggest the aircraft came to a stop from a speed in excess of 100mph. I also saw from the video that the aircraft came to a stop basically at the displaced threshold. This got me wondering: What is a typical accelerate-stop distance for a widebody passenger jet? How does an A350 go for 30 seconds and end up at the *beginning* of a runway??

As it turns out, JFK's 22R has a 3425' displaced threshold. From the video, I counted about 32 seconds from first motion to stop, split about equally between acceleration and deceleration. Assuming textbook physics using those numbers gives an acceleration of 13.3 ft/s^2 (0.4g, which looks reasonable for a jet) and max speed of 125kts. If the actual max speed achieved was only 88kts (ref: https://twitter.com/AirlineFlyer/sta...54919339499521), that allows for some slop and lower acceleration numbers given the apparent runway used.

FWIW, my accelerate-stop distance is 2000'. And my home airport runway is *shorter* than the displaced threshold at JFK's 22R!
aa5bpilot is offline  
Old 15th Dec 2015, 06:35
  #42 (permalink)  
 
Join Date: Jan 2008
Location: Reading, UK
Posts: 15,822
Received 206 Likes on 94 Posts
Could it be this new ROPS technology?

Originally Posted by Hispeedflutr
In October some FSF guys talked about new tech invented by Airbus: Runway Overrun Protection System. Looked good on video. (See link below)
No, this wasn't ROPS in action.

As the video in your link states: "ROPS assists the flight crew during the final approach and roll-out". It's not operational during a takeoff, though the A350 FMS features a broadly similar Takeoff Surveillance function, which does what the name says in the tin.
DaveReidUK is offline  
Old 15th Dec 2015, 11:31
  #43 (permalink)  
 
Join Date: Sep 2015
Location: South a bit
Posts: 34
Received 0 Likes on 0 Posts
For the avoidance of doubt and misinformation...

The A350 has no automatic rejected take-off mode, and nor does any other aircraft that I know of. In common with other comparable types, the auto brake is normally armed for take-off and then operates IF the pilot rejects the take-off.

The ROPS function is operational only during landing. If a potential runway overrun is detected (one of the top few aviation hazards in recent years) then max auto brake will be applied if auto brake is already selected by the pilot. If auto brake has not been selected, then the system will issue warnings only.

There's some ill-informed 'automation hysteria' on this thread...

Last edited by ExV238; 15th Dec 2015 at 20:45.
ExV238 is offline  
Old 15th Dec 2015, 16:01
  #44 (permalink)  
 
Join Date: Feb 2002
Location: D(Emona)
Posts: 404
Likes: 0
Received 11 Likes on 1 Post
If I am not mistaken, you get 'xx remaining' if speed decreases more than 7 knots during takeoff rols as the system assumes you are aborting.
Dufo is offline  
Old 15th Dec 2015, 20:44
  #45 (permalink)  
 
Join Date: Sep 2015
Location: South a bit
Posts: 34
Received 0 Likes on 0 Posts
Dufo,

I'm not certain exactly what you're describing, but there's no numerical display of runway remaining during an RTO in the A350 (if that's what you mean?)
ExV238 is offline  
Old 15th Dec 2015, 21:04
  #46 (permalink)  
 
Join Date: Feb 2002
Location: D(Emona)
Posts: 404
Likes: 0
Received 11 Likes on 1 Post
I am not familiar with A350 specific system but this is from RAAS manual:


4.3.7 Distance Remaining – Rejected Take-Off Advisory




RAAS provides distance remaining advisories to provide the flight crew with position awareness during a Rejected Take-Off (RTO), refer to Figure 4-12.




4.3.7.1 Annunciation Criteria




The advisory is generated if:


Aircraft is on a runway, and


Ground speed is greater than 40 knots, and


Aircraft ground speed during the take-off roll decreases by 7 knots from its maximum, and


Aircraft is on the last half of the runway (default) or a specified distance from the runway end.


RAAS will provide distance remaining advisories as detailed in section 4.2.4. When the ground speed decreases below 40 knots, these advisories will terminate.


Dufo is offline  
Old 15th Dec 2015, 21:48
  #47 (permalink)  
 
Join Date: Jun 2002
Location: Wor Yerm
Age: 68
Posts: 4
Likes: 0
Received 0 Likes on 0 Posts
Excluding the technical and operational aspects of this event, asking/ordering journalists to stop using cameras, whether allowed or not is a pointless thing to do. The first job of cabin crew is to ensure the safety of the passengers. Their time might have been better spent thinking about how to execute an evacuation. And let's remember, the culture of a company is expressed in the actions of its employees. The world in which we now live is recorded in detail. Nothing we say or do will stop that and it is naive in the extreme to think otherwise. Therefore, to avoid harsh judgement by social media, make sure you have a practical and common sense approach to dealing with the inevitable problems we face doing our job. A good start might be to stop your senior executives saying that serious events like over-runs are a common event. So unless we can uninvent things, let's learn how to deal with the world as it is.

PM
Piltdown Man is offline  
Old 15th Dec 2015, 22:46
  #48 (permalink)  
 
Join Date: Sep 2015
Location: South a bit
Posts: 34
Received 0 Likes on 0 Posts
Dufo,

Ah, OK.

No, not in A350. Airport Nav Function and ROW/ROPS are broadly similar equivalents, but no voice call-outs of runway remaining during RTO.
ExV238 is offline  
Old 17th Dec 2015, 16:02
  #49 (permalink)  
 
Join Date: Oct 2004
Location: Los Angeles
Age: 61
Posts: 223
Likes: 0
Received 0 Likes on 0 Posts
Quote,

"The TORA did not take into account the extra distance of the displaced threshold."

If that was the case, I'm curious as to why this didn't show up during the take-off performance calculations since they would use the same database.
Astra driver is offline  
Old 17th Dec 2015, 23:16
  #50 (permalink)  

Only half a speed-brake
 
Join Date: Apr 2003
Location: Commuting not home
Age: 46
Posts: 4,321
Received 3 Likes on 3 Posts
Because it is not the same database.
FlightDetent is offline  
Old 18th Dec 2015, 06:01
  #51 (permalink)  
 
Join Date: Aug 2013
Location: PA
Age: 59
Posts: 30
Likes: 0
Received 0 Likes on 0 Posts
The root cause of the event was a CODING ERROR in the Jeppesen Airport Map Database.
This was a Jeppesen error.
The TORA did not take into account the extra distance of the displaced threshold.
In RNP procedure design, I am constantly dealing with the errors in the different navdatabases, on every cycle. Waypoint locations, runway endpoint locations/elevations, etc.

Now that there is an ac that tracks runways length, I am certain that many, many more errors in these databases will be uncovered. Similar to RNP, the navdatabase information wasn't really used, and errors went unnoticed. I have seen may runway lengths that are complete bull****.

I found it really irritating that the runway endpoint in the database, according to FAA standards, is not measured at the threshold, but at the physical end of the runway pavement, leading to many errors in navigation when looking at TCH and the waypoint. (just like the displaced TCH at PSP, which are significant. Look at the NOTAMS, still do not reflect the DT)

The ac now have the ability, with the new systems to track and automate many functions. This will cause many problems in the short term, just as with the data for RNP, as the data has never been used, checked, nor vetted.

It will be necessary for many agencies to get off whatever they have been riding and do their jobs...

Back to the issue...

I guess my question would be, why does the error show up after roll, not prior to?
underfire is offline  
Old 18th Dec 2015, 06:12
  #52 (permalink)  
 
Join Date: Feb 2001
Location: The Winchester
Posts: 6,555
Received 5 Likes on 5 Posts
why does the error show up after roll, not prior to?
How does the system know you're going to actually "roll" on the runaway you are aligned with..until you actually roll? (Actually that's just reminded me of an old Isaac Asimov story)....

I'm guessing the designers don't want the system triggering a nuisance warning every time the aircraft is on a "short runway" that's being used deliberately, at low speed, perhaps as part of a taxi route.

FWIW some of the caution/warning features on the RAAS on our Boeing are inhibited until you reach 40kts ground speed for exactly that reason.

Last edited by wiggy; 18th Dec 2015 at 09:40.
wiggy is offline  

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.