FlyerTalk Forums - View Single Post - FAQ : Reason for flight delay or cancellation - 2024 edition
Old Apr 10, 2024 | 9:32 am
  #683  
Sigwx
 
Join Date: Dec 2012
Posts: 3,727
Originally Posted by Whitstabubble
Hi everyone, I would be really grateful if someone wouldn't mind pulling the delay reason in Expertflyer for BA603 (SAW-LHR) on 9 April 2024 (yesterday).

Flight was delayed by almost 3 hours leaving SAW. The flight crew confirmed that this was not weather related but due to a series software malfunction/update failure. However, upon coming into land we were sent on a go-around as the previous aircraft hadn't quite clear the runway which added another 10 minutes or so taking it beyond 3 hours.

Would be really interested on how BA codifies this delay, seeing the overall delay was caused by a miix of operational and ATC (?) reasons.

Thanks in advance as always.
Originally Posted by IMH
EF is showing both ZO and ZY. With luck one of our experts will have something more specific.

(EF also shows LANDED 2131 and ARRIVED 2136. The latter is the same time BA's status page shows, i.e. just under three hours late.
The aircraft involved started its day in LIN and operated BA561 which had a 39 minute delay due to restricts that occur on self manoeuvring stands. It landed 16 minutes late and arrived 21 minutes late.

It then operated BA602 but needed to have a TCAS equipment change out due to a fault. 2:50 of delay is due to scheduled maintenance, the technical defect and have to go and get spares and then fit them. Only 1 minute of delay was allocated to the late inbound aircraft. All of that delay meant BA602 was given a take off time of 1204UTC and pushed back at 1141 in order to achieve that, some 2:51 minutes late. It got Airborn at 12:08 and had a planned flight time of 3:26. This gives an estimated touchdown time of 15:34 UTC but it didn’t bit better than the plan and touched down at 15:23 and arrived at 15:31, some 2:56 late.


BA 603 - Reactionary delay minutes 2:51 and a passenger services issue had 7 minutes attached. The take off time issued by ATC was 1638UTC and it pushed back at 16:28UTC, take off was at 16:43 and the planned flight time was 3:39. Estimated would therefore be 20:22. Actual touchdown was at 20:31 and parking on stand at 20:36UTC vs 1735UTC. Doors opening would have been a few minutes later still.

There are no ATC delayed allocated bar one minute on the BA602.
Sigwx is offline