Jump to content

Sign in to follow this  
vc10man

Enter the wrong Flex Temp.........and near catastrophe

Recommended Posts

Thanks for highlighting my error after I'd edited my post to correct it.... I got in to my head the original post referred to Dublin, hence me thinking it came under the IAA rather than AAIB. I do have reasonable knowledge of the boundaries and major settlements within the United Kingdom and its constituent nations, and those of the Irish Republic, I just made an embarrassing misreading.

Thanks for the link Stephen, better than going off some dubious journalism! Somewhat surprised the crew didn't go for TOGA until after rotation, despite recognising the problem far earlier.

Edited by ckyliu

ckyliu, proud supporter of ViaIntercity.com. Find my spec and settings in "About me" on my profile.

support1.jpg

Share this post


Link to post

If you read the official report, it talks a lot about developing a Take-off Performance Monitoring System and explain why the working groups said it was not possible. Since I am definitely not a science guy and therefore fail to understand that(my bad!), can someone (who read the report) explain why it wasn't possible? You have the data: t/o weight, use-able runway length, qnh, N1 value, etc... Is it difficult to develop a software which will say "Hey with this acceleration rate you wont be able to hit VR (or V2) by the time you reach the end of runway, once the take off roll starts?


Ahmet Can

Share this post


Link to post

From the report: " The aircraft’s FMC did not have the capability to alert the flight crew to the fact that they had entered the incorrect OAT into the FMC, although this capability existed in a later FMC software standard available at the time."

So the solution to this problem looks pretty simple from where I sit...update the FMC software!

 


Bob Scott | AVSIM Forums Administrator | AVSIM Board of Directors

ATP Gulfstream II-III-IV-V

System: i9-10900K @ 5.2GHz on custom water loop, ASUS Maximus XII Hero, 32GB GSkill 3600MHz CAS15, eVGA 2080Ti XC Ultra, Samsung 55" JS8500 4K TV@30Hz, 5xSamsung SSD, eVGA 1KW PSU, 1Gbps internet

SB XFi Titanium, optical link to Yamaha RX-V467, Polk/Klipsch 6" bookshelf spkrs, Polk 12" subwoofer, 12.9" iPad Pro, PFC yoke/throttle quad/pedals with custom Hall sensors, Coolermaster HAF932 case, Stream Deck XL button box

Share this post


Link to post

Forgive me for my potential lack of understanding, but it looks like the pilots failed in at least two important points, inputting the wrong temp in the fmc and not monitoring their N1 gauge during the take off roll. Stating that it only gave them 60% of the require takeoff power is quite a big discrepancy to not notice at some level, regardless of whether they did the calculations or not. Sure a 5-10% off is understandable but 40%, especially for pilots who have many hours in that flight deck?

Edited by Kevin_28
was going to delete, but someone already posted a response, so might as well keep it.

Share this post


Link to post
10 minutes ago, Kevin_28 said:

Forgive me for my potential lack of understanding, but it looks like the pilots failed in at least two important points, inputting the wrong temp in the fmc and not monitoring their N1 gauge during the take off roll. Stating that it only gave them 60% of the require takeoff power is quite a big discrepancy to not notice at some level, regardless of whether they did the calculations or not. Sure a 5-10% off is understandable but 40%, especially for pilots who have many hours in that flight deck?

The actual N1 was about 81% -- a little low but perhaps not entirely unreasonably so (and only about 10% N1 less than the actual required setting of about 90% N1).

The "60%" figure AFAIK is based on an estimation of the actual thrust output (i.e. in lbf) (which is obviously non-linear with N1). 


Simon Kelsey

sig_FSLBetaTester.jpg

 

Share this post


Link to post
1 hour ago, w6kd said:

So the solution to this problem looks pretty simple from where I sit...update the FMC software!

 

That's what they did in the end 🙂
 


Jude Bradley
Beech Baron: Uh, Tower, verify you want me to taxi in front of the 747?
ATC: Yeah, it's OK. He's not hungry.

X-Plane 11 and P3D v5 hotfix 2  🙂

System specs: Windows 10  Pro 64-bit, i9-9900KF  Gigabyte Z390 RTX-2070, 32GB RAM  1X 1TB M2 for X-Plane 11, 1x 500GB SSD for P3Dv5, 1x256GB SSD for OS. Alpha-tester for FS2020

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    28%
    $7,170.00 of $25,000.00 Donate Now
×
×
  • Create New...