November 22, 20187 yr 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 November 22, 20187 yr by ckyliu ckyliu, proud supporter of ViaIntercity.com. i5 12400F, 32GB, RTX4070, more in "About me" on my profile.
November 22, 20187 yr 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
November 22, 20187 yr 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 | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
November 22, 20187 yr 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 November 22, 20187 yr by Kevin_28 was going to delete, but someone already posted a response, so might as well keep it.
November 22, 20187 yr 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
November 22, 20187 yr 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 BradleyBeech 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 12 and MSFS2020 🙂 System specs: Windows 11 Pro 64-bit, Ubuntu Linux 20.04 i7-13700KF Gigabyte Z790 RTX-4060-Ti , 32GB RAM 1X 2TB M2 for X-Plane 12, 1x256GB SSD for OS. 1TB drive MSFS2020
Archived
This topic is now archived and is closed to further replies.